During the last two weeks I have noticed that 2-3 mails (out of 30-40)
logwatch mails from internal hosts has been blocked by spamhaus.org:

   ----- The following addresses had permanent fatal errors -----
<foo.bar@dahl-stamnes.net>
    (reason: 553 5.3.0 Your mail server (myserver.dahl-stamnes.net) belongs
to a known spammer - rejected! (See http://www.spamhaus.org))

   ----- Transcript of session follows -----
.... while talking to chewbacca.dahl-stamnes.net.:
>>> MAIL From:<root@myserver.dahl-stamnes.net>
<<< 553 5.3.0 Your mail server (myserver.dahl-stamnes.net) belongs to a
known spammer - rejected! (See http://www.spamhaus.org)
501 5.6.0 Data format error


The internal hosts all use the mailer that receive mails from internet, as a
smart relay. And all the internal hosts use 192.168.x.x addresses.

How can this be explained?

-- 
J�rn Dahl-Stamnes
http://www.dahl-stamnes.net/dahls/

The main thing: do not test your own hosts. It's a waste of time, and there=
 is no benefit since you always want mail from them.

Also: fix the error message. Spamhaus listing does not always mean the host=
 *belongs* to a known spammer, but only that it has been used to send spam.=
 It might be a compromised host that belongs to a legit organization. And w=
hen referring end users to Spamhaus, you should give the IP, not just the n=
ame, since for all but the DBL, they need the IP to see the Spamhaus record=
..

Joseph Brennan
Columbia University I T