[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1508
  • Last Modified:

Delivery status : Failed. Message could not be delivered to domain .521

Hello, I was wondering if an expert could help me out?
One of my clients at example.com which i am hosting her exchange email.
janedoe@example.com
Is experiencing bounce backs from certain clients of HERS.
When they email her they get a bounce back error of

"This is a delivery status notification, automatically generated by MTA mx02.testmail.ca on Regarding recipient(s) : janedoe@example.com Delivery status : Failed. Message could not be delivered to domain .521; ***.***.***.*** does not accept mail MTA Response :521 The original message headers are included as attachment."


Any information would be greatly appreciated.
Thanks!

Nate
0
ottcomputing
Asked:
ottcomputing
1 Solution
 
Rsilva98Commented:
can you give more detailed error?
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
What is the Exchange server your hosting on ? Exchange Version ?
What is the client version ?
Can any other user or test account on the Hosted server email her ?
Is she the only user on that domain ? if not can you check her setting with other user and ensure that its good
Is her Domain as Accepted Domain and is that a part of email address as well

- Rancy
0
 
ssk_2k3Commented:
sounds like external domain server will not accept email from a domain without an
SPF record. So please convey the respective domain admin to make SPF record.

Also try to do MXlookup to remote domain to verify that you are pointing to correct DNS server. At some cases the remote domain might made some changes and your relay server may not aware due to DNS cache . So need to cleanup DNS cache from your side to correct this issue.

-Suresh
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
ottcomputingAuthor Commented:
Hi there,  I'll answer a few questions:

Our Exchange Server version: 2010 SP3

Nobody else is reporting issues of missing mail yet.

There are 50 users on the domain.

If our EHLO or HELO response is our internal domain, could some domains refuse to send mail to it?
0
 
Simon Butler (Sembee)ConsultantCommented:
The EHLO response has nothing to do with the sending of the email.
You have hashed out the IP address - what address is it? Is it the correct address of your server?

The error you have posted isn't an Exchange error, I usually see this when DNS records aren't setup correctly and there is an MX record going somewhere else, or the MX record has a problem and the remote servers try to send to the root of the domain, which is hosted elsewhere.

Simon.
0
 
ottcomputingAuthor Commented:
Well.. I decided that I would install DYN's Mail Relay service so that MX is taken care of offsite.  I think maybe using a CNAME as the MX may have been the issue.
0
 
ottcomputingAuthor Commented:
The problem ended up being CNAME as MX.  Some mailservers don't like this so I took my above solution and used it.
0
 
ottcomputingAuthor Commented:
The problem ended up being CNAME as MX.  Some mailservers don't like this so I took my above solution and used it.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now