On Wed, Feb 12, 2014 at 02:21:04PM +0000, Viktor Dukhovni wrote:
> > 127.0.0.1 is YOUR MACHINE NOT A REMOTE CLIENT.
>
> Perhaps the OP's amavis is misconfigured to accept remote SMTP clients
> without access control:
>
> Feb 11 16:40:42 hera5 amavis[32622]: (32622-04) Passed CLEAN
> {RelayedOpenRelay}, [72.9.103.50]:5850 [72.9.103.50]
> <bounce+a=ACCOUNT2-c=021114CHRISFAULKNERE-e=criterion=apollo3....@am0.net>
> -> <[email protected]>, Queue-ID: 886561514D8,
> Message-ID: <[email protected]>,
> mail_id: mf2_uVscaH5z, Hits: -1.901, size: 7991,
> queued_as: 174F71553D7, 2445 ms
>
> If 72.9.103.50 is a remote IP address, then the OP has misconfigured
> amavis to listen on remotely visible IP addresses and to accept
> mail from remote SMTP clients.
>
> Perhaps that's what the "RelayedOpenRelay" bit is about in the log
> entry. The fact that Amavis then uses a local "HELO" name is not
> surprising.
>
> The fix is to not aim the amavis shotgun at foot.
Except that in this case (sorry about noise), the message origin
was local:
Feb 11 16:40:42 hera5 postfix/smtp[4726]: 886561514D8:
to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024,
delay=3.5, delays=1.1/0.01/0/2.4, dsn=2.0.0, status=sent
(250 2.0.0 from MTA(smtp:[127.0.0.1]:10025):
250 2.0.0 Ok: queued as 174F71553D7)
So the OP has to track down the origin of queue-id 886561514D8.
--
Viktor.
