Hello zorvek,
Which DNS server are you using ?
Could you confirm the DNS you are using are able to found address of the MX for the domain ?
Regards.
Main Topics
Browse All TopicsI am running Windows Server 2003 and have set up POP and SMTP services so that mail can be sent from an ASP.net application. Mail goes out as desired except to some specific domains. The error generated is:
Reporting-MTA: dns;www.domain.com
Received-From-MTA: dns;ip-0AF85675
Arrival-Date: Sat, 31 Oct 2009 17:33:01 -0700
Final-Recipient: rfc822;xxxxx@comcast.net
Action: failed
Status: 4.4.7
I've enabled logging from the SMTP service but can't find any log files.
I suspect that the recipient's email service does not like what I have set up - perhaps it's a security or authentication problem?
Any ideas?
Kevin
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>ipconfig /all
DNS Servers . . . . . . . . . . . : 172.16.0.23
>nslookup -type=mx comcast.net
Server: ip-172-16-0-23.ec2.interna
Address: 172.16.0.23
Non-authoritative answer:
comcast.net MX preference = 5, mail exchanger = mx1.comcast.net
comcast.net MX preference = 5, mail exchanger = mx2.comcast.net
comcast.net MX preference = 5, mail exchanger = mx3.comcast.net
comcast.net MX preference = 5, mail exchanger = mx4.comcast.net
comcast.net MX preference = 5, mail exchanger = mx1a.comcast.net
comcast.net MX preference = 5, mail exchanger = mx1b.comcast.net
comcast.net MX preference = 5, mail exchanger = mx2a.comcast.net
comcast.net MX preference = 5, mail exchanger = mx2b.comcast.net
Kevin
Seems you don't have resolution problem to send a mail to comcast
Could you type :
telnet mx1.comcast.net 25
And see if the connexion is immediatly closed with a message like :
554 IMTA22.westchester.pa.mail
>telnet mx1.comcast.net 25
554 IMTA19.westchester.pa.mail
more DNSBLs, see http://help.comcast.net/co
Connection to host lost.
Kevin
You know why you can't sent email to this domain now : http://help.comcast.net/co
Are you able to use a smarthost with you application ? The SMTP server of your ISP for example ?
You're blacklisted at SORBS-SPAM :
http://www.mxtoolbox.com/S
Also, you may ask comcast to add your domain or ip to its whitelist.
You can try commercial too : http://www.nber.org/REASON
Interesting...problem is that I have installed my own SMTP and POP services. It's an Amazon S3 service running Windows Server 2003. Unfortunately I am not really qualified to do this but I am the only dude on the team who has any technical skills. The rest of the guys are marketing and sales and are essentially useless :-)
Can you help me ensure my SMTP configuration is set up in a way that prevents blacklisting?
Kevin
I don't know Amazon S3. I found this documentation, part 8 is interesting : http://www.bristle.com/Tip
If I can do more, don't hesitate
Ugh!
http://voices.washingtonpo
At least I know what is going on now!
Thanks.
Kevin
Business Accounts
Answer for Membership
by: khashayar01Posted on 2009-11-04 at 12:10:13ID: 25743396
try telnettng to the destination domain from your server and sending it manually to see what the error message says