efa-project.org

We use EFA primarily as a outgoing smarthost to make sure our email server and some other hosted solutions don't get compromised and start sending out spam. It has caught a few compromised accounts for us.

Since the 3.0.2.2 upgrade earlier today, it's refusing mail from the email server with a 4.7.1 Client Host Rejected, cannot find your reverse hostname

I am sending email off an internal class C address (192.168.x.x) on the same subnet as EFA that has been cleared to relay
I don't want to whitelist the host as I want SPAM outbreaks to be caught.

Is there something obvious I'm missing that's led to this error in 3.0.2.2?

>>>Michael

I am new to all this CentOS / postfix stuff, but did glean enough off other posts to find the line:

smtpd_client_restrictions = permit_sasl_authenticated, reject_rbl_client zen.spamhaus.org, reject_unknown_reverse_client_hostname

in /etc/postfix/main.cf

removing reject_unknown_reverse_client_hostname got things moving again...
Works for me as the EFA only accepts specific relay traffic I define.

It is being much slower since the update too, though....

Caught this issue yesterday myself. It has been removed from the update and only included in new builds. It is a good thing to have, but it will break existing deployments.