<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:Amelein@dantumadiel.eu">Amelein@dantumadiel.eu</a> wrote:
<blockquote cite="mid:4AA68A700200008E00010E19@10.1.0.206" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.5848" name="GENERATOR">
>>> Op 8-9-2009 om 16:24 is door Julian Field
<a class="moz-txt-link-rfc2396E" href="mailto:MailScanner@ecs.soton.ac.uk"><MailScanner@ecs.soton.ac.uk></a> geschreven:<br>
<table style="margin: 0px 0px 0px 15px; font-size: 1em;"
bgcolor="#f3f3f3" border="0">
<tbody>
<tr>
<td>
<div
style="border-left: 1px solid rgb(5, 5, 5); padding-left: 7px;">That
is not from MailScanner itself, but from the hourly cron job which <br>
calls /usr/sbin/processing_messages_alert. You are quite correct that <br>
this script is incapable of handling rulesets.<br>
I'm not overly convinced that is worth fixing as it's quite a lot of <br>
work for a tiny gain.<br>
The easy thing would be to just default to the "localpostmaster"
setting <br>
if it finds a ruleset. That would probably be better than the current <br>
situation.<br>
<br>
Try the attached (compresssed) script instead of <br>
/usr/sbin/processing_messages_alert.<br>
Remember to make it executable! ("chmod +x <br>
/usr/sbin/processing_messages_alert").<br>
<br>
On 08/09/2009 15:06, <a class="moz-txt-link-abbreviated" href="mailto:Amelein@dantumadiel.eu">Amelein@dantumadiel.eu</a> wrote:<br>
> Just got another mail which it tried to send to filename@fqdn <br>
> <a class="moz-txt-link-rfc2396E" href="mailto:filename@fqdn"><mailto:filename@fqdn></a><br>
> the contents of the message is:<br>
> --<br>
> Archive:<br>
> Number of messages: 1<br>
> Tries Message Last Tried<br>
> ===== ======= ==========<br>
> 6 5210725B3.AC562 Tue Sep 8 12:15:58 2009<br>
> -- <br>
> MailScanner<br>
> --<br>
> If I remember correctly this message triggered a crash loop <br>
> protection earlier because of a configuration error I hadn't <br>
> discovered till putting the server into the actual e-mail stream,
I <br>
> had forgotten to update the language conf and it was looking for <br>
> something which wasn't in there.<br>
> -<br>
> Arjan<br>
<br>
Jules<br>
<br>
-- <br>
Julian Field MEng CITP CEng<br>
<a class="moz-txt-link-abbreviated" href="http://www.MailScanner.info">www.MailScanner.info</a><br>
Buy the MailScanner book at <a class="moz-txt-link-abbreviated" href="http://www.MailScanner.info/store">www.MailScanner.info/store</a><br>
<br>
Need help customising MailScanner?<br>
Contact me!<br>
Need help fixing or optimising your systems?<br>
Contact me!<br>
Need help getting you started solving new requirements from your boss?<br>
Contact me!<br>
<br>
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654<br>
Follow me at twitter.com/JulesFM and twitter.com/MailScanner<br>
<br>
<br>
-- <br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br>
<br>
</div>
</td>
</tr>
</tbody>
</table>
<div style="background-color: rgb(255, 255, 255);"><br>
No go on that, same mails .. so I just hardcoded the e-mail addresses
in the file to be done with it.</div>
<div style="background-color: rgb(255, 255, 255);">That just leaves
the question on when it will stop reporting that problem mail :-)</div>
<div style="background-color: rgb(255, 255, 255);"> </div>
<div style="background-color: rgb(255, 255, 255);">-</div>
<div style="background-color: rgb(255, 255, 255);">Arjan<br>
</div>
</blockquote>
It appears to have worked for me. I no longer get the bounced email.<br>
</body>
</html>