Comments on: Can’t send SMTP Email? http://www.globalspex.com/2009/09/22/cant-send-smtp-email/ Web and Graphic Designers Thu, 10 Jun 2010 04:51:15 +0000 hourly 1 By: admin http://www.globalspex.com/2009/09/22/cant-send-smtp-email/comment-page-1/#comment-35 admin Mon, 19 Oct 2009 20:12:45 +0000 http://www.globalspex.com/wordpress/?p=60#comment-35 Hi searchnetmedia. I appreciate the comment and follow-up. It's been a struggle as each ISP changes its SMTP policy. Then to add to the problem, they almost hide their smtp information deep in their support pages. Hi searchnetmedia. I appreciate the comment and follow-up. It’s been a struggle as each ISP changes its SMTP policy. Then to add to the problem, they almost hide their smtp information deep in their support pages.

]]> By: SearchNetMedia http://www.globalspex.com/2009/09/22/cant-send-smtp-email/comment-page-1/#comment-34 SearchNetMedia Sat, 17 Oct 2009 01:47:25 +0000 http://www.globalspex.com/wordpress/?p=60#comment-34 Thanks for the info. This was a real frustration today, but we got it solved. I would like to add something. Comcast gave us a new password and said "they reset the account". This along with what you describe above change from Port 25 to Port 587 for the outgoing server is also important (thanks to ComcastGeorge) on twitter. If you are using a non-comcast email address and your own domain...and your incoming is say info@myowndomain.com (and using your own user name and password) for incoming servers, you still need to check "my server needs authentification" under the Outgoing Mail Server under the Server tab in Account (mail) - Properties. Then, next to that checked box to the right is SETTINGS button. click that and put in your comcast user name and password. Then it worked. So, in summary you need a user name and password for the incoming server (if using a non-comcast email address), and another user name and password (your Comcast ones) for the smpt.comcast.net Outgoing Mail Server. The last two year you could just send outgoing mail through smtp.comcast.net without authenticating, but it appears no more. We were told by Comcast early in the day that it was a Microsoft Outlook Express problem. We downloaded Mozilla Thunderbird (which is like Outlook Express) and we had the same problem there. It appears that Comcast Engineering changed this outgoing mail process and forgot to tell Customer Support. Thanks for the info. This was a real frustration today, but we got it solved. I would like to add something. Comcast gave us a new password and said “they reset the account”. This along with what you describe above change from Port 25 to Port 587 for the outgoing server is also important (thanks to ComcastGeorge) on twitter. If you are using a non-comcast email address and your own domain…and your incoming is say info@myowndomain.com (and using your own user name and password) for incoming servers, you still need to check “my server needs authentification” under the Outgoing Mail Server under the Server tab in Account (mail) – Properties. Then, next to that checked box to the right is SETTINGS button. click that and put in your comcast user name and password. Then it worked. So, in summary you need a user name and password for the incoming server (if using a non-comcast email address), and another user name and password (your Comcast ones) for the smpt.comcast.net Outgoing Mail Server.

The last two year you could just send outgoing mail through smtp.comcast.net without authenticating, but it appears no more. We were told by Comcast early in the day that it was a Microsoft Outlook Express problem. We downloaded Mozilla Thunderbird (which is like Outlook Express) and we had the same problem there. It appears that Comcast Engineering changed this outgoing mail process and forgot to tell Customer Support.

]]>