https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8314
Bill Cole <billc...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |billc...@apache.org
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Bill Cole <billc...@apache.org> ---
This looks like a configuration problem between Postfix and SpamAssassin's
spamd daemon. If you are going to check messages that large (NOT RECOMMENDED)
you need to set much higher timeouts for spamd. Postfix may also need its
timeouts for milter calls adjusted.
Because spamd is timing out, the message is never actually checked and so
there's no way for SpamAssassin to do anything to the message. The only way to
mark such messages is in whatever you are using to connect Postfix to spamd.
For example, in the MIMEDefang milter, the sizes of messages are checked before
trying to have SpamAssassin do the check, and the milter can make a log entry
and/or add a header to the ones which are too big.
SA is not designed to analyze very large messages. It is much better today than
it was in previous versions, but I am not sure that there is any way to handle
messages over about 20MB within the standard SMTP timeout of 600s at
end-of-data (which is more than many SMTP clients ts actually tolerate.)
--
You are receiving this mail because:
You are the assignee for the bug.
