up vote 0 down vote favorite
share [g+] share [fb]

Problem with the exchange 2003 server at our company users can send and receive mail from and to each other. receiving external mail (ex. from hotmail) doesn't work, sending to an external mail addres does work.

I should mention we did do a DNS transfer yesterday

link|improve this question
1  
Test your email server here: mxtoolbox.com/index.aspx – Nixphoe Aug 12 '11 at 17:03
1  
During this DNS transfer, did the MX record for your domain get transferred and correctly configured? – xeon Aug 12 '11 at 17:03
yes I phoned our provider and he checked our records, they were transfered correctly – Jens Aug 12 '11 at 17:09
could there be some sort of delay on this? – Jens Aug 12 '11 at 17:10
I tested on a site called hq42 and got this codesending MAIL FROM tester@IP.IP.IP.IP response: 550 5.1.0 domain literals not allowed Your server may not configured to accept "domain literals". Refusal of "domain literals" like tester@IP.IP.IP.IP is a violation of RFC-822 Section 6.2.3 sending: MAIL FROM: postmaster@smtp.telenet-ops.be response: 250 2.1.0 sender ok sending: RCPT TO mymail@domain.be response: 550 5.1.1 recipient rejected: Relay access denied sending: QUIT Closing socket...socket closed code – Jens Aug 12 '11 at 17:21
feedback

2 Answers

up vote 0 down vote accepted

Your error regarding "domain literals" comes from the configuration of your mailserver. I imagine that this was intentional and you don't ever expect mail to be sent to user@ip.ip.ip.ip anyway. It is obvious that your mailserver is talking.

Your provider is simultaneously the right and wrong person to verify your records. Assuming you use their servers, what they see is the most up-to-date information. It is likely that older information is cached in other places, or the chain pointing to your server is incomplete -- major domain servers might not be pointing to your nameserver, for example.

To test that the mailserver is acting correctly while the DNS system isn't, I suggest putting a hosts entry on a mailserver and then sending mail from that. Otherwise, do some directed-digging of DNS records: dig example.com @10.1.2.3. Check for all the different types of records you need along the chain (NS @ a .com server, A and MX at your server...).

link|improve this answer
I think the server is fine. so I should just wait till the caches get updated? – Jens Aug 12 '11 at 17:41
I think you should verify. It may be a cache issue, or it may be a bad update. Get access to an external box (ramp up an Amazon EC2 instance for .20 cents an hour or something) and ensure that things are behaving as expected. – Jeff Ferland Aug 12 '11 at 17:43
feedback
up vote 1 down vote

What DNS changes did you make?

This is likely an issue with the changed records not being correct - you'll need to verify that MX records exist for the domain, and that they point to valid A records for the SMTP server(s).

link|improve this answer
I tested on a site called hq42 and got this sending: MAIL FROM tester@IP.IP.IP.IP response: 550 5.1.0 domain literals not allowed Your server may not configured to accept "domain literals". Refusal of "domain literals" like tester@IP.IP.IP.IP is a violation of RFC-822 Section 6.2.3 sending: MAIL FROM: postmaster@smtp.telenet-ops.be response: 250 2.1.0 sender ok sending: RCPT TO mymail@domain.be response: 550 5.1.1 recipient rejected: Relay access denied sending: QUIT Closing socket...socket closed – Jens Aug 12 '11 at 17:16
"Relay access denied" means that your server is rejecting the message. Did your DNS name actually change, instead of just moving the same name to a new provider? Or, have permissions settings been modified recently on your SMTP receive connector? – Shane Madden Aug 12 '11 at 17:44
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.