message-processing db notifications
MailScanner at ecs.soton.ac.uk
Wed May 6 20:42:28 IST 2009
On 06/05/2009 15:18, David Lee wrote:
> Julian: An observation, relatively minor, about the new message
> processing database...
> There is an associated hourly cron job 'processing_messages_alert'
> which sends notifications using the 'Notices To' setting of
> This happens even if the config file says 'Send Notices = no'. And
> that doesn't seem right.
> Historically, these notification settings were originally concerned
> with virus processing but are now, in effect, being deployed beyond
> that original scope.
> I can see two reasonably straightforward resolutions:
> 1. Adjust comments in MS.conf to include expanded scope.
> 2. Consider different sets of notification definitions for different
> classes of events: e.g. existing set 'as-is' for viruses; a new set
> for the message-db; (then another new set for the next feature,
> The first is very easy for you to implement, but imposes a "one size
> has to fit all" behaviour. The second allows a site to tailor
> different notification levels for different classes of events. (Might
> some sort of 'ruleset'-like capability assist?)
How about I just make it test to see if "Send Notices = yes" instead,
and not send the message if it's set to "no"?
> P.S. We have now rolled out "4.76.24-3" on the majority of our
> gateways and it is going well. Thanks.
Great, thanks for letting me know! :-)
Julian Field MEng CITP CEng
Buy the MailScanner book at www.MailScanner.info/store
Follow me at twitter.com/JulesFM
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.
More information about the MailScanner