//  home   //  advanced search   //  news   //  categories   //  sql build chart   //  downloads   //  statistics
 ASP FAQ 
Home
ASP FAQ Tutorials

   8000XXXX Errors
   Alerts
   ASP.NET 2.0
   Classic ASP 1.0
      COM / ActiveX Components
      Forms
      General Topics
      Date/Time Routines
      Email Scripts & Info
      Files/Directories & FSO
   Databases
   General Concepts
   Search Engine Optimization (SEO)

Contact Us
Site Map

Search

Web
aspfaq.com
tutorials.aspfaq.com
classicasp.aspfaq.com

ASP FAQ Tutorials :: Classic ASP 1.0 :: Email Scripts & Info :: Why is e-mail to certain domains being rejected?


Why is e-mail to certain domains being rejected?

Whether you're using CDO, XP_SMTP_SendMail, or a 3rd party COM object to send mail, you may have experienced this problem. Your mail works some of the time — but doesn't work either when the mail is intended for your own domain, or it only works when the mail is intended for your own domain. Here are some things to check that will hopefully help resolve the issue. Many of these suggestions will require some input, and possibly some work, from your network and/or Exchange administrator.
  • Make sure that the FROM address associated with your messages is a valid address on your domain. Check your SMTP logs, the event log, and the drop / badmail folders. You might find something like this: 
     
    The server rejected the sender address. The server response was: 501 5.1.8 Domain of sender address <foo>@<blat>.com does not exist
     
    Even if you don't see this message, it might be that Exchange or your SMTP server are willing to just forward along mail from any address if the destination is outside of your network, but will only retain internal mail if the sender address is valid. 
     
  • Make sure DNS is not an issue. For example, depending on how your network is set up, the SMTP relayer within your domain may be unable to externally resolve yourdomain.com. You might also check that if you are using an external SMTP server, that your firewall or proxy is not somehow blocking mail that is going out and coming back in. 
     
  • If mail only works when sent to your domain, it might be that your firewall or proxy is blocking such mail from leaving your network (e.g. the firewall might be blocking outbound traffic on port 25, in general or only from specific machines). 
     
  • If you are using an Exchange server, make sure that it has not disabled all external relaying regardless of sender address. Check with your Exchange administrator for potential permissions, firewall, proxy, or domain-based issues. Consider using the local SMTP server instead of forwarding on to Exchange for processing. 
     
  • If you are using the SMTP virtual server within IIS, make sure that you have not set an explicit include/exclude list. In Internet Services Manager, right-click the SMTP server, hit Properties, and on the Access tab, check Connection... and Relay... 
     
    Also, consider configuring IIS to use a remote SMTP server as a "smart host" relayer, instead of handling all the mail internally. See the Delivery tab, Advanced. For further information, see KB #293800 for Windows 2000, and KB #324272 and KB #816121 for Windows Server 2003. 
     
  • If Exchange or your SMTP server are set to try local delivery and then forward on to an external SMTP relayer for addresses that aren't in your domain, make sure that the external relayer does not require SMTP authentication. If so, you may need to handle this correctly — see Article #2026 for a code sample that uses CDO.Message to send to an SMTP server that requires outgoing authentication. 
     
  • Another option to bypass problems from within your network is to forward all mail to an external SMTP server, such as your ISP. This will avoid problems with a local SMTP server, and Exchange server configurations... but if you can't get outbound on port 25, you'll have to fix that issue first. 
     
  • For information on testing your SMTP service in Windows 2000, see KB #286421. To test SMTP services in Windows Server 2003, see KB #323350.
We hope that this information is useful. If you know of other potential workarounds, please let us know.

Related Articles

Can I get CDO messages to return a read receipt?
Can I use a remote SMTP server with CDONTS.NewMail?
How do I alter the priority / importance of an e-mail message?
How do I prevent my links from wrapping in an e-mail?
How do I put carriage returns into an e-mail?
How do I send e-mail from ASP?
How do I send e-mail from SQL Server?
How do I send e-mail in HTML format?
How do I send e-mail with CDO?
How do I validate an e-mail address?
Should I use form action=mailto: to mail the results of a form?
Where can I get more details about configuring / using CDO?
Why can't ASP handle 80,000 e-mails?
Why do CDONTS messages end up in the badmail folder?
Why do I get 8000900F errors?
Why do I get 80040108 errors?
Why do I get 8004020A errors?
Why do I get 80090020 errors?
Why do I get C00402CE / C00402C7 errors?
Why does CDO.Message give 800C000D errors?
Why does CDO.Message give me 8004020F errors?
Why does CDO.Message give me 80040213 errors?
Why does CDO.Message give me 80040222 errors?
Why does my CDONTS mail hang out in the queue or pickup folders?

 

 


Created: 12/13/2003 | Last Updated: 12/14/2003 | broken links | helpful | not helpful | statistics
© Copyright 2006, UBR, Inc. All Rights Reserved. (353)

 

Copyright 1999-2006, All rights reserved.
Finding content
Finding content.  An error has occured...