Link to home
Start Free TrialLog in
Avatar of lenkne
lenkne

asked on

Unable to send e-mail to one specific domain

I've looked all over EE for the answer to this one with no luck.  We are not able to send e-mail to one specific domain which I will call domain.com.  When sending an e-mail, an Undeliverable message comes back immediately:

Your message did not reach some or all of the intended recipients.

      Subject:      Test Message from United Seminary
      Sent:      11/27/2006 9:29 AM

The following recipient(s) could not be reached:

      person@domain.com on 11/27/2006 9:29 AM
            There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
            <mail.unitedseminary.edu #5.5.0 smtp;550 - Requested action not taken: relaying denied>

This message is immediate and generated by our Exchange server.  People from this domain are able to send e-mail into us.  I've checked and neither of us are blacklisted.

Any ideas?
ASKER CERTIFIED SOLUTION
Avatar of dskillin
dskillin

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If it is a single domain, have you called them up to find out why they are bouncing your messages? Actually asking them might be quicker and will allow you to find the solution.

Simon.
Avatar of Ehab Salem
Fully agree with Sembee. contacting the recipient admin is the first step. Ask them also which RBL they are using.
Avatar of lenkne
lenkne

ASKER

Both responses got us pointed to the source of the problem.  It was a DNS issue with our ISP because the receiving domain had hosted their e-mail with the same ISP as us, but recently moved to another.  Our ISP had not cleaned up their DNS.  Using the tools Sembee suggested and dskillin pointing out the MX record in the log was our ISP, not ours put it all in place.    

Thanks!