Same email processed 268 times!

[Julian Field]

If anyone can narrow this down to a particular message, this would 
_really_ help. I can't reproduce the problem at the moment, so I can't 
fix it. Though 4.51.5 exhibited this quite badly which 4.51.6 fixed.

Max Kipness wrote:
> Is this some kind of bug? I have my high-score set to store. As I last resort I guess I could send to /dev/null, but I'm hoping there is some other solution.
>
> Thanks,
> Max
>
> On Mon, 3 Apr 2006 15:28:31 -0500, "Mike Kercher" <mike at vesol.com> wrote:
>   
>> I've seen the same thing before on ONE of many servers.  My solution was
>> to set my High Scoring Spam Action to forward to /dev/null.  If I set
>> the action to delete, some messages would get processed over and over
>> again until the system came to it's knees.
>>
>> Mike
>>
>>
>>     
>>> -----Original Message-----
>>> From: mailscanner-bounces at lists.mailscanner.info
>>> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf
>>> Of Max Kipness
>>> Sent: Monday, April 03, 2006 2:55 PM
>>> To: mailscanner at lists.mailscanner.info
>>> Subject: Same email processed 268 times!
>>>
>>>
>>> Hello -
>>>
>>> I've been trying desperately to figure out why my MailScanner
>>> queues are so large and cpu is pegged at 100%. When looking
>>> through the log I finally figured out what part of the
>>> problem might be. Some messages are being processed hundreds
>>> of times. I grepped for one messagaes and was processed 268
>>> times, so basically I see this (the repetitive part):
>>>
>>> Apr  3 09:08:31 xxx MailScanner[19835]: Spam Actions: message
>>> k33E61uc020656 actions are store Apr  3 09:10:11 xxx
>>> MailScanner[21099]: RBL checks: k33E61uc020656 found in
>>> SBL+XBL
>>> Apr  3 09:10:11 xxx MailScanner[21099]: SpamAssassin cache
>>> hit for message
>>> k33E61uc020656
>>> Apr  3 09:10:11 xxx MailScanner[21099]: Message k33E61uc020656 from
>>> 218.144.251.15 (jonah.rivas_yx at mo
>>> en.com) to xxx.com is spam, SBL+XBL, SpamAssassin
>>> (score=28.338, required 6,
>>> BAYES_99 3.50, DATE_IN_
>>> FUTURE_12_24 2.77, DCC_CHECK 2.17, DIGEST_MULTIPLE 0.77,
>>> FORGED_RCVD_HELO 0.14, MIME_BASE64_NO_NAME 0.22 ,
>>> MIME_BASE64_TEXT 1.89, PYZOR_CHECK 3.70, RATWARE_NAME_ID
>>> 4.10, RAZOR2_CF_RANGE_51_100 0.50, RAZOR2_CF_ RANGE_E4_51_100
>>> 1.50, RAZOR2_CHECK 0.50, RCVD_IN_DSBL 2.60, RCVD_IN_NJABL_DUL
>>> 1.95, RCVD_IN_SORBS_DUL 2.
>>> 05)
>>>
>>> This has repeated 268 times with only an increment of a few
>>> seconds in the time.
>>>
>>> Other messages, including non-spam seem to function just fine
>>> and are processed once.
>>>
>>> I'm using the latest MailScanner, SA, DCC, Pyzor. This is a
>>> new build from a week ago, so something I guess could be
>>> configured wrong.
>>>
>>> Thanks,
>>> Max
>>> --
>>> Thanks,
>>>
>>> Max
>>>
>>> --
>>> MailScanner mailing list
>>> mailscanner at lists.mailscanner.info
>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>>
>>> Before posting, read http://wiki.mailscanner.info/posting
>>>
>>> Support MailScanner development - buy the book off the website!
>>>
>>>       
>> --
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the website!
>>     

-- 
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.