I have captured a bad message. It seems innocuous; it's from me at a
host in my domain, to me, basically
From: g...@foo.lexort.com
To: g...@lexort.com
and has a body "foo", no DKIM headers, just Received, Subject,
Message-Id.
Processing this with my normal config results in the timeout.
I
On Wed, 3 Nov 2021, Bill Cole wrote:
The most common reason for SA to hit its internal timeout is the combination
of a rule with a pattern that can generate a large number of backtracks while
scanning (exponential or factorial order) and a message which causes such
backtracking. Typically that
On 2021-11-02 at 19:15:33 UTC-0400 (Tue, 02 Nov 2021 19:15:33 -0400)
Greg Troxel
is rumored to have said:
I have a systeem with postfix and spamassassin 3.4.6 via spamd. It's
been generally running well. I noticed mail from one of my other
systems timing out and 471, and that caused me to loo
Bill Cole writes:
> It would generally be a bad idea to increase the Postfix timeout, as
> that passes the problem back upstream as senders will generally time
> out at 300s as well.
>
> So, add '--timeout-child=295' to your spamd arguments if you want to
> make spamd timeout faster than Postfix
On 2021-11-02 at 19:15:33 UTC-0400 (Tue, 02 Nov 2021 19:15:33 -0400)
Greg Troxel
is rumored to have said:
I have a systeem with postfix and spamassassin 3.4.6 via spamd. It's
been generally running well. I noticed mail from one of my other
systems timing out and 471, and that caused me to loo
> postfix is waiting 300s
> SA thinks it can spend 300s processing
> postfix gives up 1s before SA is done
The default spamd child timeout is 300s.
The default postfix content milter timeout is 300s.
Each is a reasonable choice, but really postfix's timeout should be
longer.
I set in postf
On 15-Mar-2010, at 06:45, Mark Martinec wrote:
>
> add 'add_header all Timing _TIMING_'
> to your config file, which will insert this same timing breakdown information
> into a header section of a checked mail.
Ah, thanks, I think I will do that. I do not really want to go trolling through
someo
LuKreme,
> Running spamd (SA-3.3.0) under FreeBSD 6.2 I see frequent timeout errors
> and message. When these occur, the mailserver seems to stop responding for
> seconds:
>
> 04:18:19 mail spamd[67527]: (__alarm__ignore__(141359))
> 04:18:58 mail spamd[67527]: check: exceeded time limit, skippi
LuKreme wrote on Sun, 14 Mar 2010 19:04:22 -0600:
> Anything I can do to further trouble shoot this or eliminate these timeout
> errors?
Process the same message with spamc again. Does it take that long again?
Kai
--
Get your web at Conactive Internet Services: http://www.conactive.com
From: Art Greenberg
Date: Mon, 9 Nov 2009 17:58:48 -0500 (EST)
Lately I'm seeing a fairly consistent timeout for checks sent to pyzor and
razor2 by SA. Up until a couple of days ago this was a very rare
concurrence. Seems odd that both of these would have this trouble at the
10 matches
Mail list logo
