mail to postermaster account after exim upgrade - problem?

[Jeff-C]

After the exim upgrade, I see that dnsreport.com reports:

ERROR: One or more of your mailservers does not accept mail to postmaster@mydomain.com. Mailservers are required (RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1) to accept mail to postmaster.

mydomain.com's postmaster response:
>>> RCPT TO:<postmaster@mydomain.com>
<<< 550-"The recipient cannot be verified. Please all recipients of this message
550 to verify they are valid."

Is this a problem that should be corrected, or intentional by design in the new exim RPMs?

[Website Rob]

Normally, that error refers to Domain literals -- or using an IP address -- for postmaster. If it is not working for the Domain name then most likely the 'catch-all' is not being used and no address/forwarder was setup for postmaster.

So, set one up and the problem will go away. Dont' worry about the error msg. for an IP address as most people don't accept any eMail sent to an IP address anyway.

[Jeff-C]

Thanks very much Rob,

So I need to setup a postmaster@ email alias/forwarder under each individual account? Is there a way to do it more easily (server-wide all at once) to comply with the standard instead of for each individual account?

[Website Rob]

It only needs to be done for accounts that are not using the 'catch-all' eMail which is default setup. If it is turned off or not used and a worry, then an address or forwarder needs to manually be setup for each account.

It could be done using a custom made script if you want to go that route, but the manual method, although slower, is probably quicker & easier.

[bmcpanel]

I dont think that is the answer. My guess is the problem involves a "hyphen" in the actual domain name. Is that correct Jeff C?