Page 1 of 1

my default gateway is causing a 4.7.1 rejection on all inbound

Posted: 13 Mar 2019 01:44
by 2Old4This
I'm trying to set up version 3.0.2.6, using my old system as a template (EFA, but years old and not updated).

I changed the NAT on my firewall to direct incoming mail to the new EFA device and I'm getting the following error on ALL incoming emails:

NOQUEUE: reject: RCPT from unknown[10.5.4.244]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [10.5.4.244]; from=<return@spammer.com> to=<me@mydomain.com> proto=ESMTP helo=<spammer.com>

10.5.4.244 is my default gateway--the internal IP of my firewall.

I understand this is supposed to be a rDNS issue, but how could I be getting this with my firewall?

Thanks in advance

Re: my default gateway is causing a 4.7.1 rejection on all inbound

Posted: 13 Mar 2019 02:21
by 2Old4This
Sorry I forgot to include the next lines of the log, which might be necessary:

RCPT from unknown[10.5.4.244]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [10.5.4.244]; from=<return@spammer.com> to=<me@mydomain.com> proto=ESMTP helo=<spammer.com>
disconnect from unknown[10.5.4.244] ehlo=2 starttls=1 mail=1 rcpt=0/1 quit=1 commands=5/6
postfix/smtpd[2792]: connect from unknown[10.5.4.244]
postfix/smtpd[2792]: warning: unknown[10.5.4.244]: SASL LOGIN authentication failed: authentication failure

Re: my default gateway is causing a 4.7.1 rejection on all inbound

Posted: 13 Mar 2019 08:33
by henk
A search on google will show quite some topics on this issue

Code: Select all

site:forum.efa-project.org Client host rejected: cannot find your reverse hostname
just take a look at : viewtopic.php?t=3317

Re: my default gateway is causing a 4.7.1 rejection on all inbound

Posted: 14 Mar 2019 23:32
by 2Old4This
henk wrote: 13 Mar 2019 08:33 A search on google will show quite some topics on this issue

Code: Select all

site:forum.efa-project.org Client host rejected: cannot find your reverse hostname
just take a look at : viewtopic.php?t=3317
Sorry... I googled and even saw the thread you cite, but for some reason concluded it wasn't the fix. I looked at the files again and I had not made the changes. When I did, that fixed the problem. Thanks for your help.