fqdn Protocol Check issue

[bhwong]

Some of our customers are complaining that they can't receive any emails from some of their clients. So I proceed to disabled the protocol checks for unqualified (non fqdn) senders and domains in Zimbra configuration.

Ideally, Zimbra should check the sender's domain and verify if this domain MX record match with the email server that it is coming from. But I suspect that Zimbra only check if the sender's domain match with the email server that it is coming from instead.

If this is the case, then we will encounter many senders getting rejected because most senders with their own domain but hosted their emails with their ISP will have their MX records pointing to their ISP MX instead of their own domain MX.

Does anyone has any idea which method does Zimbra used to verify fqdn (Fully qualified domain name)?

[phoenix]

Originally Posted by bhwong

Ideally, Zimbra should check the sender's domain and verify if this domain MX record match with the email server that it is coming from. But I suspect that Zimbra only check if the sender's domain match with the email server that it is coming from instead.

There are many broken mail servers out there and using those checks is not likely to block real MX mail. For further information I'd suggest reading the relevant postfix documentation: Postfix Configuration Parameters

[bhwong]

This is really weird. I asked the client to email both our customer test account I have created and to my account, both are hosted together on the same Zimbra Server. I can receive the email but not my customer test account. What could be the possible cause???

[phoenix]

Originally Posted by bhwong

This is really weird. I asked the client to email both our customer test account I have created and to my account, both are hosted together on the same Zimbra Server. I can receive the email but not my customer test account. What could be the possible cause???

Have a look in the log files to find some details.