SA times out

[Julian Field]

DAve wrote:
> Julian Field wrote:
>>
>>
>> Kai Schaetzl wrote:
>>> Julian Field wrote on Wed, 02 Apr 2008 16:45:54 +0100:
>>>
>>>  
>>>>>>  but perhaps a feature request could be a
>>>>>> CLI switch to specify the message ID so MS only scans the particular
>>>>>> message(s) that you're interested in observing.
>>>>>>           
>>>>> Good idea. I'll take a look. Would a single ID do?
>>>>>       
>>>> All done. It will be in the next release.
>>>>     
>>>
>>> Ahm, Julian, now that I have used the MS debugging feature a few 
>>> times I think being able to grab a single ID may be nice, but not 
>>> really helpful for a production machine. I have to disable at least 
>>> MS if I want to debug (otherwise it would "steal" the queue files) 
>>> and usually this is not done within a few seconds, but takes at 
>>> least five minutes or more, maybe repeatedly. It would be nice if I 
>>> could specify an alternative queue directory, so I can run a 
>>> MailScanner instance in parallel to the production daemon and debug 
>>> files from that directory while the normal sendmail/MS operation 
>>> isn't affected. I think this would be much more helpful than 
>>> specifying a certain ID.
>>>   
>> You can stop MailScanner completely, then restart the incoming 
>> sendmail (or whatever MTA you use) so that you are providing email 
>> service to your users. Then run MailScanner on the particular ID you 
>> want to test it with. Then when you are happy, resume normal operation.
>> Stop everything and start incoming MTA:
>>    service MailScanner stop
>>    service MailScanner startin
>> Run it on 1 id:
>>    MailScanner --debug --id=<message-id>
>> Start up everything normally
>>    service MailScanner restart
>>
>> Should solve the problem for you. Saves me writing more code :-)
>
> In my case, in the time it took to run debug four times I gained 400 
> messages in the queue. I don't get much time to ponder the results. 
> What I did this week was dump the output to file and then alternate 
> which of the servers I stopped MS on so as to spread the downtime.
>
> I am considering pushing a VMWare install up on the network and then 
> installing roundhouse, just for testing with future upgrades. Which is 
> arguably the smart option.
milter-bcc is a simple solution that roundhouse, much faster to setup. 
You just put in a mailertable entry for the recipient you bcc to, can be 
any domain name you make up. That's what I do (except I didn't know 
about milter-bcc at the time so use a home-grown version of it written 
in a few lines of Perl).

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc


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