<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Noel,<br><br>--- On <b>Sun, 20/6/10, Noel Butler <i><noel.butler@ausics.net></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Noel Butler <noel.butler@ausics.net><br>Subject: Re: Problems with the latest 4.80.7-1 MS<br>To: "MailScanner discussion" <mailscanner@lists.mailscanner.info><br>Received: Sunday, 20 June, 2010, 8:07 AM<br><br><div id="yiv141902067">
On Sat, 2010-06-19 at 14:59 -0700, Michael Mansour wrote:
<blockquote type="CITE">
<pre>Hi,<br><br>I've just upgraded one of my mail servers to this version, and running a MailScanner --lint gives me hundreds of these errors:<br><br>Could not read file /deleted.content.message.example.com.au.txt at /usr/lib/MailScanner/MailScanner/Config.pm line 2851<br>Syntax error in line 1 of ruleset file /etc/MailScanner/rules/deleted.content.message.report.rules at /usr/lib/MailScanner/MailScanner/Config.pm line 2798<br><br>and the ruleset file is simply:<br><br>To: <a rel="nofollow" ymailto="mailto:*@example2.com.au" target="_blank" href="mailto:*@example2.com.au">*@example2.com.au</a> %report-dir%/deleted.content.message.example.com.au.txt<br><br>I have multiple reports configured so there hundreds more of these type of errors on the lint.<br><br>If I revert back to the older MS 4.79.11, things work fine again.<br><br>Any ideas?<br><br></pre>
</blockquote>
<br>
Hrm, do you use inline spam warning txt? have you ever found that when it addresses the recipients on hit messages, it addresses everyone of them like a large CC in the message (I see this since kernel announce msgs were tagged.) but in the envelope To header there's only the actual recipient.<br>
<br>
rather strange, oh well... its only been complained about on my private domain, not the commercial servers (as far as i know) if many more complain we'll cease to use this feature.<br>
</div></blockquote>I don't use the inline spam warning no. I'm not sure what that would have to do with the error above, but it turned out that the variable in the ruleset was the problem.<br><br>I'm downgrading back to the earlier version.<br><br>Thanks.<br><br>Michael.<br></td></tr></table><br>