level9tech
asked on
Exchange Server not accepting all emails
I am having trouble with my exchange server receiving email. Some outside mail comes in, some is rejected. AOL doesn't seem to work at all, Yahoo! does, other .orgs don't, but some .nets do.
No ryhme or reason really. There are a lot, over 50, messages in the Queue. If I restart the Exchange Services I am worried I might have a bigger problem. Any advice.
No ryhme or reason really. There are a lot, over 50, messages in the Queue. If I restart the Exchange Services I am worried I might have a bigger problem. Any advice.
ASKER
This is the error senders are getting:
5.1.0 - Unknown address error 553-'sorry, relaying denied from your location
5.1.0 - Unknown address error 553-'sorry, relaying denied from your location
That is not an Exchange message.
Is that your senders or external senders?
You need to be really clear who is getting the messages.
Does your email come in directly or through another provider? What about outbound email?
Simon.
Is that your senders or external senders?
You need to be really clear who is getting the messages.
Does your email come in directly or through another provider? What about outbound email?
Simon.
ASKER
Incoming participants are receiving the error message (senders outside of the domain). Internally we have no trouble sending mail out. Our email comes in directly.
Have you run the test I outlined above to confirm that all is well? The message is not an Exchange message, so something else is responding to inbound email.
Simon.
Simon.
ASKER
FAIL: Acceptance of postmaster address
ERROR: One or more of your mailservers does not accept mail to postmaster@****.com. Mailservers are required (RFC82 6.3, RFC112 5.2.7, and RFC28 4.5.1) to accept mail to postmaster.
smtp.secureserver.net's postmaster response:<br /> >>> RCPT TO:<postmaster@****.com><b
ERROR: One or more of your mailservers does not accept mail to postmaster@****.com. Mailservers are required (RFC82 6.3, RFC112 5.2.7, and RFC28 4.5.1) to accept mail to postmaster.
smtp.secureserver.net's postmaster response:<br /> >>> RCPT TO:<postmaster@****.com><b
ASKER
Mail server host name in greeting:
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
smtp.secureserver.net claims to be host pre-smtp32-02.prod.mesa1.s
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
smtp.secureserver.net claims to be host pre-smtp32-02.prod.mesa1.s
ASKER
The postmaster address is the only failure under the mail category...
ASKER
FAILED: MX A lookups have no CNAMEs
WARNING: One or more of your MX records points to a CNAME. CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are:
smtp.secureserver.net.->sm
WARNING: One or more of your MX records points to a CNAME. CNAMEs are prohibited in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are:
smtp.secureserver.net.->sm
ASKER
Any idea what MX A lookups are and if they are affecting us?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you have messages in the queues, that is sending email.
The end domain (.net, .org etc) doesn't have any bearing on the delivery of email.
AOL are very picky about who they accept email from.
I would suggest that you start with putting your domain in to dnsreport.com and see if it flags any errors in the mail server section.
Simon.