Search  
   
Browse by Category
 
Netfirms 24/7 Support .: EMAIL .: D. Troubleshooting .: Why can't I send email?

Why can't I send email?

There may be a few reasons why you are unable to send email:

1. Ensure that your outgoing mail server on your POP client is pointing to smtp.yourdomain.com (where yourdomain.com is your domain name) on port 587 with "My (SMTP) Server Requires Authentication" configured. For instructions on how to configure your POP client, browse to
Configure POP settings

NOTE: Verizon customers should be aware that their ISP is securing their network and restricting SMTP access - Port 25 on Verizon is no longer supported: http://voices.washingtonpost.com/securityfix/2009/02/verizon_to_implement_spam_bloc.html. This is the case for many other ISP's as well. Please check with your ISP for further details.

2. Some ISP's do not allow their customers to send E-mail out using a third party SMTP server. Our most recent research has revealed that the following ISP's require their customers to use their own ISP's SMTP servers: Earthlink, Comcast, Sympatico, AT&T, Charter Communications, NetZero/Juno, MSN, and RCN.

If your ISP doesn't allow you to send E-mail out using a third party SMTP server, we recommend that you contact them directly to verify their SMTP server settings.

During our most recent research, we were able to identify the following SMTP server addresses:

Earthlink: smtpauth.earthlink.net (To verify, visit
http://www.earthlink.net)
Comcast: smtp.comcast.net (To verify, visit
http://www.comcast.com)
Sympatico: smtp1.sympatico.ca or smtp8.sympatico.ca (To verify, visit
http://www.sympatico.ca)
AT&T: mailhost.att.net (To verify, visit
http://www.att.net)
Netzero: smtp.netzero.com (To verify, visit
http://www.netzero.net)
Charter Communications: smtp.charter.net (To verify, visit
http://www.charter.com)
MSN: smtp.email.msn.com (To verify, please check with your MSN provider)
RCNL: smtp.rcn.com (To verify, visit
http://www.rcn.com)
BellSouth.net: mail.bellsouth.net (To verify, visit
http://www.bellsouth.net)
Cox.net: smtp.east.cox.net (CT, FL, GA, LA, NC, OH, RI, VA); smtp.central.cox.net (KS, NE, OK, UT, West TX); smtp.west.cox.net (AZ, CA, NV); smtp.cox-internet.com (for @cox-internet.com customers
in AR, ID, LA, MI, East TX, Tyler). Port 587 may also be required for SMTP. To verify, visit
http://www.cox.net
Rogers: May require port 587 for smtp. To verify, visit http://www.rogers.com
AOL: May require port 587 for smtp. To verify, visit http://www.aol.com.

IMPORTANT: If using port 587, please ensure that you configure your POP client for "My Outgoing mail server (SMTP) requires authentication".

3. Please ensure that your domain name is fully registered and that it has not expired.

If you haven't registered your domain yet, please browse to https://controlpanel.netfirms.comlogin and follow the steps below:

(i). Login into the members control panel
(ii). Click "Domains"
(iii). Follow the onscreen prompts to register a new domain name

If your domain is already registered with Netfirms, please browse to
https://controlpanel.netfirms.com and follow the steps below:

(i). Login into the members control panel
(ii). Click on the Billing/Renewal tab
(iii). Click the renew button next to your domain
(iv). Renew your domain and complete the process

If your domain was registered through another registrar, you have two options:

(i). If your domain registrar has not yet released the domain name, you may need to renew your domain name with your domain registrar
(ii). Or if they have released the domain name, you can register the domain name with Netfirms as a “new” domain name

4. If you are trying to send to a Hotmail, Yahoo, Gmail or other externally hosted account and the emails are not being delivered to the respective inbox, please check the spam, junk or bulk folder.

For instance:

(i) If your forwarding address is a hotmail account, please check the sensitivity of the Junk E-Mail Filter. Hotmail says that "...at Enhanced and Exclusive levels, wanted messages are occasionally identified as junk e-mail. Check the junk e-mail folder regularly to make sure wanted e-mail has not been moved there."

(ii) If your forwarding address is a yahoo account, please go to the Bulk folder and check if Yahoo's SpamGuard is turned on. Yahoo says that "...While we make our best efforts to deliver solicited commercial and non-commercial email directly to your inbox, a non-spam message may be delivered to your Bulk folder on occasion. For this reason, we recommend that the recipient check this folder periodically to ensure important messages are not missed."

5. If your POP mail client is timing out before the emails are sent out, please click here for instructions on how extend the time-out configuration in your POP mail client (eg. Outlook, Outlook Express)

6. Verify if the computer you are trying to send email from is running the Norton Antivirus program. Norton AntiVirus Email Scanning could be having an adverse effect on sending and receiving your email. Please click here for instructions on how to send emails using POP mail client with Email scanning disabled from Norton Antivirus.

7. Verify that the computer you are trying to send email from is not running a firewall that may be interfering with SMTP traffic on port 25 or port 587. Ensure that if you are behind a firewall or proxy server that your firewall or proxy server is not blocking FTP on port 25 and 587. For information about disabling firewalls, click here.

NOTE: As an alternative to checking your mail using a POP client we suggest that you use Netfirms Webmail available from anywhere in the world at any time from: http://webmail.yourdomain.com (where yourdomain.com is your registered domain hosted at Netfirms) when you are working remotely.

8. If your email messages are being sent but being bounced back with the following error: "Reason: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)" error mean when an email message bounces back to the sender?", click here.


How helpful was this article to you?


.: Powered by Lore 1.5.6
Visit Netfirms.com Web Hosting | Copyright © 1998 - 2009 Netfirms, Inc. All Rights Reserved.