<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
Each day we get a few of these messages pile up in the postfix mail
queue:<br>
<br>
# mailq<br>
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------<br>
3AA2983A65 4682 Fri Mar 22 05:25:13 <a class="moz-txt-link-abbreviated" href="mailto:postmaster@host1.domain.com">postmaster@host1.domain.com</a><br>
(lost connection with 127.0.0.1[127.0.0.1] while sending end of data
-- message may be sent more than once)<br>
<a class="moz-txt-link-abbreviated" href="mailto:first.last@domain.com.au">first.last@domain.com.au</a><br>
<br>
E40C283F8F 4095 Fri Mar 22 10:39:42 <a class="moz-txt-link-abbreviated" href="mailto:postmaster@host2.domain.com">postmaster@host2.domain.com</a><br>
(lost connection with 127.0.0.1[127.0.0.1] while sending end of data
-- message may be sent more than once)<br>
<a class="moz-txt-link-abbreviated" href="mailto:first.last@domain.com.au">first.last@domain.com.au</a><br>
<br>
and then:<br>
<br>
E40C283F8F 4095 Fri Mar 22 10:39:42 <a class="moz-txt-link-abbreviated" href="mailto:postmaster@host1.domain.com">postmaster@host1.domain.com</a><br>
(delivery temporarily suspended: lost connection with
127.0.0.1[127.0.0.1] while sending end of data -- message may be
sent more than once)<br>
<a class="moz-txt-link-abbreviated" href="mailto:first.last@domain.com.au">first.last@domain.com.au</a><br>
<br>
<br>
The above messages that are being sent are simply daily "logwatch"
emails sent from our internal physical hosts. The hosts are email
filtering hosts, so report on various bad/spam URL's etc within
their content.<br>
<br>
All other hosts with logwatch reports (that aren't email filtering
hosts) have no trouble sending emails to the
<a class="moz-txt-link-rfc2396E" href="mailto:first.last@domain.com.au">"first.last@domain.com.au"</a> Kolab3 account, which is expected as they
don't contain any "bad URL" content.<br>
<br>
After extensive internet searches, the "lost connection" and
"delivery temporarily suspended" errors from postfix are very
generic errors with many and diverse root causes. In our case, we
believe the root cause is specifically related to amavisd not being
able to scan the emails because of the spam URL's contained in them.<br>
<br>
We don't need amavisd on the Kolab3 server at all (all our scanning
is done on other dedicated machines), and have tried disabling
amavisd in /etc/postfix/main.cf by commenting out:<br>
<br>
content_filter = smtp-amavis:[127.0.0.1]:10024<br>
<br>
then restarting postfix, running "postfix flush" but to no avail,
the "lost connection" messages happen immediately after attempting
the flush. <br>
<br>
The only thing we can do is delete them from the postfix queue, but
the new emails get re-queued the very next day.<br>
<br>
We've also tried whitelist our domain in amavisd by adding the line:<br>
<br>
@whitelist_sender_maps = (['.domain.com']);<br>
<br>
adjusting the line:<br>
<br>
$mynetworks<br>
<br>
to define our internal network, and restarting amavisd, then
attempting a postfix flush. To no avail.<br>
<br>
Policy bank:<br>
<br>
$policy_bank{'MYNETS'} = { # mail originating from @mynetworks<br>
originating => 1, # is true in MYNETS by default, but let's
make it explicit<br>
os_fingerprint_method => undef, # don't query p0f for internal
clients<br>
};<br>
<br>
is also set.<br>
<br>
We really don't want amavisd on the Kolab server, it's unnecessary
in our setup.<br>
<br>
How can we:<br>
<ol>
<li>effectively disable amavsid from the Kolab3 server?</li>
</ol>
Thanks. <br>
<br>
Michael.
</body>
</html>