[Mimedefang] Huge messages causing "try again later"
sysadmin at omsoft.com
sysadmin at omsoft.com
Wed Feb 25 16:06:27 EST 2004
I did add md_syslog lines, and the scanning never took longer than 1 second,
which I thought was odd. I added a "start" message before the while loop and a
"stop" message after it. I am assuming that whatever buffer holds messages to
syslog is getting flushed after every message is sent, but I suppose that could
be wrong.
The delay reported by sendmail is always over 2 minutes:
---
Feb 25 12:33:23 hostname sm-mta[16913]: [ID 801593 mail.info]
i1PKVLKq016913: from=<user at domain>, size=19861502,
class=0, nrcpts=1, msgid=<msgid>, proto=ESMTP, daemon=MTA,
relay=relay.domain.ext [xxx.xxx.xxx.xxx]
Feb 25 12:35:33 hostname mimedefang[23627]: [ID 847421 mail.error]
Error from multiplexor: ERR Filter timed out - check
filter rules or system load
Feb 25 12:35:34 hostname sm-mta[16913]: [ID 801593 mail.info]
i1PKVLKq016913: to=<user at domain>, delay=00:04:13,
pri=19891502, stat=Please try again later
---
I have added the size check for the Novarg checking code, I will see if that
changes anything.
Thanks,
Lucas
On 25 Feb 2004 at 13:54, Michael Sims wrote:
> Paul Whittney wrote:
> > I noticed you've got my "experimental code" for the novarg virus in
> > there
> [...]
> An easier way to see how long the filter ran is to check the delay= equate
> that sendmail logs on the same line with the recipient status. For example:
>
> Feb 18 10:55:47 mx sendmail[15980]: i1IGqapX015980: to=<user at example.com>,
> delay=00:03:10, pri=4723633, stat=Please try again later
More information about the MIMEDefang
mailing list