Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
View | Details | Raw Unified | Return to bug 506598
Collapse All | Expand All

(-)swaks-20130209.0.orig/doc/ref.pod (-20 / +20 lines)
Lines 824-906 Link Here
824
824
825
=over 4
825
=over 4
826
826
827
=item 0
827
=item C<0>
828
828
829
no errors occurred
829
no errors occurred
830
830
831
=item 1
831
=item C<1>
832
832
833
error parsing command line options
833
error parsing command line options
834
834
835
=item 2
835
=item C<2>
836
836
837
error connecting to remote server
837
error connecting to remote server
838
838
839
=item 3
839
=item C<3>
840
840
841
unknown connection type
841
unknown connection type
842
842
843
=item 4
843
=item C<4>
844
844
845
while running with connection type of "pipe", fatal problem writing to or reading from the child process
845
while running with connection type of "pipe", fatal problem writing to or reading from the child process
846
846
847
=item 5
847
=item C<5>
848
848
849
while running with connection type of "pipe", child process died unexpectedly.  This can mean that the program specified with --pipe doesn't exist.
849
while running with connection type of "pipe", child process died unexpectedly.  This can mean that the program specified with --pipe doesn't exist.
850
850
851
=item 6
851
=item C<6>
852
852
853
Connection closed unexpectedly.  If the close is detected in response to the 'QUIT' swaks sends following an unexpected response, the error code for that unexpected response is used instead.  For instance, if a mail server returns a 550 response to a MAIL FROM: and then immediately closes the connection, swaks detects that the connection is closed, but uses the more specific exit code 23 to detail the nature of the failure.  If instead the server return a 250 code and then immediately closes the connection, swaks will use the exit code 6 because there is not a more specific exit code.
853
Connection closed unexpectedly.  If the close is detected in response to the 'QUIT' swaks sends following an unexpected response, the error code for that unexpected response is used instead.  For instance, if a mail server returns a 550 response to a MAIL FROM: and then immediately closes the connection, swaks detects that the connection is closed, but uses the more specific exit code 23 to detail the nature of the failure.  If instead the server return a 250 code and then immediately closes the connection, swaks will use the exit code 6 because there is not a more specific exit code.
854
854
855
=item 10
855
=item C<10>
856
856
857
error in prerequisites (needed module not available)
857
error in prerequisites (needed module not available)
858
858
859
=item 21
859
=item C<21>
860
860
861
error reading initial banner from server
861
error reading initial banner from server
862
862
863
=item 22
863
=item C<22>
864
864
865
error in HELO transaction
865
error in HELO transaction
866
866
867
=item 23
867
=item C<23>
868
868
869
error in MAIL transaction
869
error in MAIL transaction
870
870
871
=item 24
871
=item C<24>
872
872
873
no RCPTs accepted
873
no RCPTs accepted
874
874
875
=item 25
875
=item C<25>
876
876
877
server returned error to DATA request
877
server returned error to DATA request
878
878
879
=item 26
879
=item C<26>
880
880
881
server did not accept mail following data
881
server did not accept mail following data
882
882
883
=item 27
883
=item C<27>
884
884
885
server returned error after normal-session quit request
885
server returned error after normal-session quit request
886
886
887
=item 28
887
=item C<28>
888
888
889
error in AUTH transaction
889
error in AUTH transaction
890
890
891
=item 29
891
=item C<29>
892
892
893
error in TLS transaction
893
error in TLS transaction
894
894
895
=item 32
895
=item C<32>
896
896
897
error in EHLO following TLS negotiation
897
error in EHLO following TLS negotiation
898
898
899
=item 33
899
=item C<33>
900
900
901
error in XCLIENT transaction
901
error in XCLIENT transaction
902
902
903
=item 34
903
=item C<34>
904
904
905
error in EHLO following XCLIENT
905
error in EHLO following XCLIENT
906
906

Return to bug 506598