Betr.: Re: Notice to ruleset not being read - MS 4.78.15-1

[Ed Bruce]

Amelein at dantumadiel.eu wrote:
> >>> Op 8-9-2009 om 16:24 is door Julian Field 
> <MailScanner at ecs.soton.ac.uk> geschreven:
> That is not from MailScanner itself, but from the hourly cron job which
> calls /usr/sbin/processing_messages_alert. You are quite correct that
> this script is incapable of handling rulesets.
> I'm not overly convinced that is worth fixing as it's quite a lot of
> work for a tiny gain.
> The easy thing would be to just default to the "localpostmaster" setting
> if it finds a ruleset. That would probably be better than the current
> situation.
>
> Try the attached (compresssed) script instead of
> /usr/sbin/processing_messages_alert.
> Remember to make it executable! ("chmod +x
> /usr/sbin/processing_messages_alert").
>
> On 08/09/2009 15:06, Amelein at dantumadiel.eu wrote:
> > Just got another mail which it tried to send to filename at fqdn
> > <mailto:filename at fqdn>
> > the contents of the message is:
> > --
> > Archive:
> > Number of messages: 1
> > Tries Message Last Tried
> > ===== ======= ==========
> > 6 5210725B3.AC562 Tue Sep  8 12:15:58 2009
> > --
> > MailScanner
> > --
> > If I remember correctly this  message triggered a crash loop
> > protection earlier because of a configuration error I hadn't
> > discovered till putting the server into the actual e-mail stream, I
> > had forgotten to update the language conf and it was looking for
> > something which wasn't in there.
> > -
> > Arjan
>
> Jules
>
> -- 
> Julian Field MEng CITP CEng
> www.MailScanner.info
> Buy the MailScanner book at www.MailScanner.info/store
>
> Need help customising MailScanner?
> Contact me!
> Need help fixing or optimising your systems?
> Contact me!
> Need help getting you started solving new requirements from your boss?
> Contact me!
>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> No go on that, same mails .. so I just hardcoded the e-mail addresses 
> in the file to be done with it.
> That just leaves the question on when it will stop reporting that 
> problem mail :-)
>  
> -
> Arjan
It appears to have worked for me. I no longer get the bounced email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20090908/861cb74e/attachment.html