On Sat, Jun 22, 2019 at 09:01:28PM +1000, Russell Coker wrote:
We are currently having problems where mail Andrew
sends to luv-main gets
blocked by localhost.
# postconf -d|grep mynet
mynetworks = 127.0.0.0/8 10.10.10.0/24 [::1]/128 [2a01:4f8:140:71f5::]/64
Below are the relevant log entries. It seems that ::1 is not being accepted
as an exclusion for spam checks, from the above you can see that ::1 is in
mynetworks and from the attached main.cf you can see that permit_mynetworks is
before other checks. Any ideas as to what the problem might be and why it
only seems to affect Andrew's mail?
To clarify, what happens is that outbound mail from the list server is sent to
localhost and the Postfix instance on localhost is rejecting it.
From the attached master.cf you can see that
localhost is excluded from
SpamAssassin and ClamAV checks.
Jun 18 16:21:47 itmustbe postfix/cleanup:
CADE6B0AD: reject: header
From: achalmers--- via luv-main <luv-main(a)luv.asn.au> from localhost[::1];
from=<luv-main-bounces(a)luv.asn.au> to=<rjh+luv(a)cita.utoronto.ca> proto=ESMTP
helo=<itmustbe.luv.asn.au>: 5.7.1 550 Message rejected Mail from a likely spam
That's not a standard postfix rejection message, so it's coming from something
else - perhaps one of your smtpd milters?
googling for the error message text (in quotes) doesn't come up with anything,
so it doesn't seem to be a common error message - it's probably a custom rule.
try grepping for ""Mail from a likely spam domain" in your postfix &
etc config files..
What domain is the mail coming from? has that domain somehow got itself onto
BTW, the fact that the message even gets a postfix queue id means that postfix
has, at some stage, accepted the message. messages rejected during the initial
smtpd session get tagged with NOQUEUE in the logs instead of a queue id. which
means that it's unlikely to have anything to do with the ::1 address.
Try examining the entire chain of events for a single message - i.e. grep for
the postfix queue ID, e.g. 'grep CADE6B0AD: /var/log/mail.log'.
This may show other related IDs that need to be grepped for if the message is
passed to an external filter and then back into postfix (this is pretty normal
on my postfix box, because I use amavisd as a content_filter, but I don't know
if you'd see the same using a milter).
(i wrote a perl script years ago to do a two-pass search for mail.log entries.
give it a search regexp such as an email address and it'll find all the queue
ids in the log matching that, then it'll grep for those queue ids in the log.
you can find it at http://taz.net.au/postfix/scripts/mailgrep.pl
. try it with
something like: 'mailgrep.pl -s "from=<achalmers@"
craig sanders <cas(a)taz.net.au>