Disable reverse PTR check in Zimbra and force accept from invalid domains

6,277

Solution 1

I believe this is a postfix error. Have a look in the Zimbra Admin under Global Settings MTA and double check the protocol and DNS check settings that you're using. You may have to relax the fully qualified domain name requirement or disable DNS lookups.

I've never had to solve this problem so I can't be sure that this is what's causing your problem. But that's where I'd start.

EDIT: Just had another thought. Verify that your Zimbra server has functional DNS. It's possible the name resolution isn't working which could manifest itself in this manner.

Solution 2

clear Client's IP address (reject_unknown_client) in zimbra global settings

Share:
6,277

Related videos on Youtube

ewwhite
Author by

ewwhite

Updated on September 18, 2022

Comments

  • ewwhite
    ewwhite almost 2 years

    I've moved an older Sendmail/Dovecot system to a Zimbra community edition system. I need to be able to receive messages from certain standalone Linux hosts that may not have valid A records or proper reverse DNS entries established (e.g. AT&T is the ISP or systems sitting on a consumer-level ISP). Establishing the reverse DNS or setting a SMARTHOST is not an option.

    The error I get in zimbra.log is:

    zimbra postfix/smtp[2200]: DB83B231B53: to=<root@host_name.baddomain.com>, relay=none, delay=0.07, delays=0.06/0/0/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for name=host_name.baddomain.com type=A: Host not found

    How can I override this? Is this more of a Postfix issue or is it Zimbra?

    edit - The problem seems to be with an underscore in the hostname of the server. So it's a problem with root@host_name.baddomain.com. Again, how can I override this in Zimbra?

  • ewwhite
    ewwhite about 13 years
    Question has been updated with additional info...