You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by km...@apache.org on 2013/01/11 18:35:03 UTC
svn commit: r1432178 - /spamassassin/trunk/spamc/spamc.pod
Author: kmcgrail
Date: Fri Jan 11 17:35:02 2013
New Revision: 1432178
URL: http://svn.apache.org/viewvc?rev=1432178&view=rev
Log:
Small cleanup that EX_TOOBIG is never used for spamd per bug 5412
Modified:
spamassassin/trunk/spamc/spamc.pod
Modified: spamassassin/trunk/spamc/spamc.pod
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamc/spamc.pod?rev=1432178&r1=1432177&r2=1432178&view=diff
==============================================================================
--- spamassassin/trunk/spamc/spamc.pod (original)
+++ spamassassin/trunk/spamc/spamc.pod Fri Jan 11 17:35:02 2013
@@ -295,7 +295,7 @@ Example:
=head1 EXIT CODES
By default, spamc will use the 'safe fallback' error recovery method. That
-means, it will always exit with an exit code if C<0>, even if an error was
+means, it will always exit with an exit code of C<0>, even if an error was
encountered. If any error occurrs, it will simply pass through the unaltered
message.
@@ -322,6 +322,10 @@ follows:
EX_PROTOCOL 76 remote error in protocol
EX_NOPERM 77 permission denied
EX_CONFIG 78 configuration error
+
+ * The EX_TOOBIG error level is never used. If spamc receives a message
+ that is too big, the exit code will be 0.
+
EX_TOOBIG 98 message was too big to process (see --max-size)
=head1 SEE ALSO