MailScanner no longer scanning mail

[Alex Broens]

On 5/3/2007 4:47 PM, Jody Cleveland wrote:
> On 5/3/07 8:36 AM, "Alex Broens" <ms-list at alexb.ch> wrote:
> 
>> Opps - pressed wrong key - sent too fast!
>>
>> assuming postfix is correctly configured for MailScanner - queue path &
>> permissions
>>
>> shot in the dark:
>>
>> try setting:
>>
>> MailScanner.conf
>>
>> # 5 for only one CPU
>> Max Children = 10
>>
>> # set to 10 if you have only one CPU
>> Queue Scan Interval = 13
>>
>> Max Unscanned Bytes Per Scan = 100m
>> Max Unsafe Bytes Per Scan = 50m
>> Max Unscanned Messages Per Scan = 5
>> Max Unsafe Messages Per Scan = 5
> 
> My, how the floodgates have opened!
> 
> That took care of it. And, now, MS is whittling away at the queue.
> 
> With that said, why would those changes fix it? Is there something with the
> new version that changed something with that?

glad to hear your MS is purring again

afaik, it comes to a point that if MS' threads doesn't get enough air 
between checking for msgs to process, they race to catch the same msg, 
and msgs get processed over and over again, till a msg has been 
processed a few hundred times and then finally delivered to the MTA.

I've seen this happen with older versions, under a default config, as 
well so I don't think it has anything to do with th MS version - more a 
configuration/tuning thing.

You'll need to play around with the threads and msgs per scan settings 
till you get the right balance for your hardware/traffic/bandwidth 
requirements.



Alex