http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3838
------- Additional Comments From [EMAIL PROTECTED] 2006-02-15 04:12 -------
This seems ot be related to 4445. Observations there should be considered, as
well. Here is a new observation that will require some really exhaustive and
mind numbing log reading to prove false (from an email to Daryl.)
I went back over 4445 also. And I started looking at the logs again
both during an episode and after. This raised a really "stupid"
question. I'd have to really comb the logs to figure out in detail
if there is a counter indication. It SEEMS like the problem may come
in, for Loren and me, if fetchmail goes out and finds new mail to
queue while a previous batch is still being processed. I don't see
this processing overlap with fetchmail and spamd at times the
PerMsgStatus error message happens. At the moment mail takes, on the
average, about 3 to 4 seconds to complete spamd processing. There seem
to be times if day when there are BIG bursts of messages followed by
relative sanity the rest of the day.
So far that's the best observation I have that I've not posted before.
"A message added to the user's incoming queue while spamd is still processing
old messages leads to the hit."
Although it's on the output side rather than input side of the mail
intake process I do note we're using "mbox" format for our system here.
/-> spamc/spamd ->\
fetchmail -> procmail---------------> /var/spool/<mbox files>
(Yes, some mails skip spamd for size or specific list reasons.)
{^_^} Joanne
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
