Search the Community
Help & Support Forums
- Business Internet & Ethernet
- Active Core
- Cloud Solutions
- Billing & Customer Service
- Business Phone
- Business TV
- Think Tank
- Welcome Community
Hi ... I can log in to my business account but not the email account ... both my pc and iphone can no longer access email ...
Hi gecko164 and welcome to the business support forums. I would like t...
Hi gecko164 and welcome to the business support forums.
I would like to help with your email issue. We do prefer to keep the conversation here for documentation purposes. Could you please remove your phone number from your public post? I would like to keep your information secure. Please also private message me your full address, phone number on the account and your name.
I know there's some sort of "Comcast Email Migration". But I only use IMAP with Thunderbird and I don't use Outlook. According to the e-mails Comcast has sent me over the last two months, if I don't use Outlook, I don't have to do anything:
"If you do not use Outlook to read your emails, please disregard this notice." I did ignore the messages and That is NOT true!
As of Tuesday morning 12/19/2017, Comcast disabled the outgoing SMTP server that I had been using - smtp.ch3.comcast.net. Now I can receive emails, but I can NOT send out email. I spent an hour on the phone this morning, and got them to set up my Office365 Business Essentials account. I now have the username and password set up for the outgoing mail server, but it doesn't work. I get the message "Login to smtp.office365.com failed". Then the dialog box says "Please verify that your Outgoing server (SMTP) settings are correct and try again".
I have spent a long time doing various Google searches to figure out why it is failing, but so far no success.
Was wondering if anyone could help me with an issue I'm having setup up sendmail in linux. What I'd like to do is be able to send emails from my home to my outlook.com personal email address. I've setup sendmail the best that I could but am seeing the folwoing error come up when I try to send an email to the SMTP server using my comcast business credentials:
stat=Deferred: 403 4.7.0 TLS handshake failed.
I have installed a cert that I've signed using my own self-signed CA... I hope I don't need to get a comerical SSL cert to be able to send emails to myself. Can anyone shed some light on what I need to go look for? I'm fairly technically adept but I'm lost when it comes to email Please let me know if I can provide more useful information.
Test Mail Output:
joe@torrent:/usr/local/share/ca-certificates$ echo "Subject: test" | /usr/lib/sendmail -v email@example.com
firstname.lastname@example.org... Connecting to [127.0.0.1] via relay...
220 torrent.markgraf.us ESMTP Sendmail 8.14.4/8.14.4/Debian-4.1ubuntu1; Mon, 27 Apr 2015 23:09:58 -0700; (No UCE/UBE) logging access from: localhost(OK)-localhost [127.0.0.1]
>>> EHLO torrent.markgraf.us
250-torrent.markgraf.us Hello localhost [127.0.0.1], pleased to meet you
250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN
250 2.0.0 Verbose mode
220 2.0.0 Ready to start TLS
>>> EHLO torrent.markgraf.us
250-torrent.markgraf.us Hello localhost [127.0.0.1], pleased to meet you
250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN PLAIN
250 2.0.0 Verbose mode
>>> MAIL From:<email@example.com> SIZE=14 AUTHfirstname.lastname@example.org
250 2.1.0 <email@example.com>... Sender ok
>>> RCPT To:<firstname.lastname@example.org>
250 2.1.5 <email@example.com>... Recipient ok
354 Enter mail, end with "." on a line by itself
050 <firstname.lastname@example.org>... Connecting to smtp.w14d.comcast.net. port 587 via relay...
050 220 businessclass.comcast.net ESMTP mail service ready
050 >>> EHLO torrent.markgraf.us
050 250-omta02.potomac.co.businessclass.comcast.net hello [126.96.36.199], pleased to meet you
050 250-AUTH LOGIN PLAIN
050 250-SIZE 30000000
050 250 OK
050 >>> STARTTLS
050 220 Go ahead
050 <email@example.com>... Deferred: 403 4.7.0 TLS handshake failed.
250 2.0.0 t3S69wIn004992 Message accepted for delivery
firstname.lastname@example.org... Sent (t3S69wIn004992 Message accepted for delivery)
Closing connection to [127.0.0.1]
221 2.0.0 torrent.markgraf.us closing connection
Apr 27 23:08:41 torrent sendmail: t3S68fKo002487: from=joe, size=14, class=0, nrcpts=1, msgid=<201504280608.t3S68fKo002487@torrent.markgraf.us>, relay=joe@localhost
Apr 27 23:08:41 torrent sm-mta: STARTTLS=server, relay=localhost [127.0.0.1], version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-GCM-SHA384, bits=256/256
Apr 27 23:08:41 torrent sendmail: STARTTLS=client, relay=[127.0.0.1], version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-GCM-SHA384, bits=256/256
Apr 27 23:08:41 torrent sm-mta: t3S68fpm002488: from=<email@example.com>, size=306, class=0, nrcpts=1, msgid=<201504280608.t3S68fKo002487@torrent.markgraf.us>, proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1]
Apr 27 23:08:41 torrent sm-mta: STARTTLS=client, error: connect failed=0, SSL_error=5, errno=0, retry=-1
Apr 27 23:08:41 torrent sm-mta: ruleset=tls_server, arg1=SOFTWARE, relay=smtp.w14d.comcast.net, reject=403 4.7.0 TLS handshake failed.
Apr 27 23:08:41 torrent sm-mta: t3S68fpm002488: to=<firstname.lastname@example.org>, ctladdr=<email@example.com> (1000/1000), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30306, relay=smtp.w14d.comcast.net. [188.8.131.52], dsn=4.0.0, stat=Deferred: 403 4.7.0 TLS handshake failed.
Hi Comcast_john, As the log above indicates the authenication wouldn't happen until T...
As the log above indicates the authenication wouldn't happen until TLS is established. I do however have my comcast business credentials in the auth portion of sendmail config. Bottom line is that the SMTP server doesn't like TLS handshake from linux. Don't know why and there is no indication from my end why the connection is terminated other than it's the handshake. I am going to assume that it's an issue with self signed certs but that is just a guess.
The solution that is now working for me is to disable TLS for sendmail. Less secure but it works. Wish I knew why TLS bombs out on the SMTP server's side.
For anyone that this might help- add thsi line to your /etc/mail/access config file to disable TLS:
I just created a new email user like I've done dozens of times before. I gave the new user his temporary password and when he tries to login he gets this error message...
"We're Sorry... This Link Has Expired
For security purposes, you must activate your account in order to sign in. For details on how to activate your account, please refer to the activation email you received. If you are unable to locate your activation email, please contact a manager of this online account to request another invitation."
Where is the activation email sent to? The new email account that he can't login to? I can't find an activation email anywhere and my new user can't login to his email account. Please help.
One of my coworkers reported that whenever he sends an email to a new vendor he gets an undeliverable stating "The e-mail address you entered couldn't be found..." listing the error in the subject line. Everything works from his personal Gmail account.
He forwarded me an email from his Gmail account. I clicked on the vendor's email address in that email and sent an email to hm. I also received the undeliverable. I have also typed in the email address and gone to their website an clicked on the email address on the site and got the same result.
To make matters more confusing, I sent him an email from my home Comast account and he received it. However, he replied and I never received it nor is it in my Spam folder.
I've seen references to this being an issue with the Contact or an auto-complete entry being corrupted. This email is not in my Contacts nor does it auto-complete when I start typing. I've seen references to this online.
Hi Fitops_BillS. Can you post the full bounce back message that your are receiving? &nbs...
Hi Fitops_BillS. Can you post the full bounce back message that your are receiving? This should contain both the send/receive email addresses and routing path info. This will help in determining the cause of the failures.
See below: Delivery has failed to these recipients or groups: firstname.lastname@example.org (mblo...
Delivery has failed to these recipients or groups:
email@example.com (firstname.lastname@example.org) The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: W14HUB-CH2-D3.W14D.comcast.net
email@example.com #550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##
Original message headers:
Received: from W14MBX-CH2-D2.W14D.comcast.net ([169.254.2.106]) by W14HUB-CH2-D3.W14D.comcast.net ([172.28.150.20]) with mapi id 14.03.0224.002; Mon, 15 Jun 2015 12:13:34 -0500Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: William Shaffer <firstname.lastname@example.org>To: "email@example.com" <firstname.lastname@example.org>Subject: email testThread-Topic: email testThread-Index: AdCnjps2k0O0gOwXQCuHSh0O6UXOHQ==Date: Mon, 15 Jun 2015 12:13:33 -0500Message-ID: <3618378DC423AB4E850E88875E2CD46304204D@W14MBX-CH2-D2.W14D.comcast.net>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach:X-MS-TNEF-Correlator: <3618378DC423AB4E850E88875E2CD46304204D@W14MBX-CH2-D2.W14D.comcast.net>MIME-Version: 1.0X-Originating-IP: [184.108.40.206]
I've tried this on several computers over 2 differnt version of Winwows in both Edge and Chrome and I get the same result. Whenever I click on the little paperclip to add an attachment, there's this weird overlay effect and you can't click the button to add the attachment. Needless to say, this drives me up the wall.
Looks like this...
Hello all, I reached out to the portal team to see if there are any updates on thi...
I reached out to the portal team to see if there are any updates on this. In the mean time I'm able to add attachments when I log in using IE instead of Chrome.
I was also able to add attachments when I use the light version in Chrome.
trying to change display name on my business email acct
It would appears servers changed withot notification to w14d.comcast.net. Trying to reconfigure outlook mac and ms clients. but autodiscover still going to hmc1.comcast.net. Even doing manual overrides ro point to server is not always working.
We can access OWA vis new URL
I can see the changes in our dns settings but new autodiscover is not responding to pings.
Why wernt we given a heads up to these changes.
So this upgrade you all did to the exchange server broke 57 working outlook configurations, an...
So this upgrade you all did to the exchange server broke 57 working outlook configurations, and you changed the webmail address to owa so everyone favorites also no longer worked. No notice provided to us the PAYING customer of this major change, and like ZERO help from comcast in getting it fixed. I dont want to here you dont support outlook, you broke it so now get me some help and get it fixed.
(edited for account security)
This o365 migration has been my worst experience in 20 years in IT. The cord was simply pulled on our previous email server. We got the accounts moved to the new platform but none of our contacts, old emails, or calendars have been migrated. When I call the migration line they essentially tell me to just wait some undefined period of time--as if that will do any good. Of course nothing happens, and its an hour on hold each time I have to call in, to not be helped each time I call. After an entire day without email access it is now day 3 without our old emails and no one can answer me for status. I have been promised an escalation two days in a row, and no surprise I never receive a call back. This is a joke, absolutely zero respect for my time or business. HOW DO I GET AHOLD OF SOMEONE WHO A) CARES AND B) HAS SOME ABILITY TO HELP ME?????
I am beyond frustrated and need an escalation to someone who can get this done, I have way too many hours into this fiasco.
We have used Outlook 2007, then 2010 and then 2013 (as part of Office 365) since available to connect to our comcast hosted exchange accounts.
All have functioned flawlessly until comcast upgraded their Exchange servers to Exchange 2010 from Exchange 2007 at the end of last week.
I can connect android devices with ActiveSync using the new server address in DNS settings, but can't connect with Outlook 2013 from either of two laptops running Win 8.1 Pro. The web Outlook access functions normally.
The autodiscover type account creation in Outlook fails, with "unable to make encrypted connection to server, hit ... to proceed with unencrypted connection" or similar error.
Manual creation of the email account done through the control panel fails, as no connection to the server can be made.
I called comcast tech support, and was told that only Outlook 2010 was supported, and that they were told not to provide any tech support for Outlook, and they recommended that I try Outlook 2010.
The 32 bit Outlook 2010 that I downloaded from comcast installed, but couldn't successfully connect, either.
Microsoft TechNet or Office.com search indicates that they only recommend that one version of Outlook be installed on a system.
What is the problem? Outlook 2013 is compatible with Exchange Server 2010, just as it was with 2007.
This has wasted a large amount of time, and I would appreciate some assistance in resolving this problem.
Have also tried deleting the existing Outlook profiles on each system. An IMAP account from the ISP I have at home (charter, which splits our city with comcast), but not the exchange account can be added back, with the same errors noted above.
One way to use autoconfigure in Outlook that has changed is to do the following: . 1) Launch Outl...
One way to use autoconfigure in Outlook that has changed is to do the following:
1) Launch Outlook
2) hold down the Ctrl key and right mouse click on the Outlook icon in the systray (Outlook icon in lower right next to the date/time)
3) Select "Test E-mail AutoConfiguration"
4) Provide the email and password for the Outlook that you are configuring
5) Uncheck everything except "Use AutoDiscover"
6) Click Test
This should fix your configuration assuming that server was setup correctly.
BTW Comcast outsouces its Exchange installation. I never could get in touch with anyone at Comcast that had any Exchange administration background. I was escalated to tier 2.5 and could never get anyone to call me back.
I too same problem - 1. What is your domain name? CJS.comcastbiz.net 2. Can you access the webmail?...I too same problem - 1. What is your domain name? CJS.comcastbiz.net 2. Can you access the webmail? yes 3. Have you tried create a new Outlook profile on different computer? yes, new computer just purchased and office 365 will not connect to the exchange server.
I am also having the same problems with Outlook 2013 since I installed it in May. I thought ...
I am also having the same problems with Outlook 2013 since I installed it in May. I thought I had a workaround by setting up on the old POP server, but only a few emsils are coming through. Technical support is non-responsive.
I found this post while searching on migrating from Comcast exchange server to office 365. &...
I found this post while searching on migrating from Comcast exchange server to office 365.
I have given up on Comcast exchange support. I recieved same response from tier 2 support, We do not support Outlook.
I pay for an exchange server from comcast and you provide Outlook client for me to download and connect to your server but you do not support that sceanario.
Our mail works very slowly but our calender wont update on the server when making apointment in Outlook 2010 or 2013.
I discovered that the DNS settings for the autodiscovery for our domain is not configured correctly. Left message with tier 2 support with this information and never heard back and they closed the ticket.
I long for the days wehn my calender on my phone was updated with my desktop calender. Apparently that impossible for comcast fix.
I am also not able to set up Outlook 2013 except using IMAP protocol. I checked my DNS setting and ...
I am also not able to set up Outlook 2013 except using IMAP protocol. I checked my DNS setting and I removed some of the old references to the hmc1 server and replaced with the new server data. At this time, I am still stuck with the same situation.
We are experiencing the same issue. As soon as upgrade was complete we were unable to connect...
We are experiencing the same issue. As soon as upgrade was complete we were unable to connect to exchange. Attempted to create new profile, add a new mailbox and the only option Autodiscover returned was imap when we need full exchange connectivity. Here are our server settings (minus the email address). If you are unable to fix the autodiscover issue quickly, can you please provide a set of instructions for manually entering the settings?User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36The required version of Silverlight is installed: YesRequired version of Silverlight: 2.0.31005.0Outlook Web App experience: PremiumUser language: English (United States)User time zone: (UTC-08:00) Pacific Time (US & Canada)Exchange mailbox address: /o=W14C/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=2727234c2Host address: http://webmail.w14c.comcast.net/owaVersion: 220.127.116.11Host name: webmail.w14c.comcast.netExchange Client Access server name: W14CAS-WC-C8.w14c.comcast.netExchange Client Access server .NET Framework version: 2.0.50727.5472Client Access server operating system version: Microsoft Windows NT 6.1.7601 Service Pack 1Client Access server version: 18.104.22.168Client Access server platform: 64bitMailbox server name: W14MBX-WC-C1.w14c.comcast.netMailbox server Microsoft Exchange version: 22.214.171.124Client Access server operating system language: en-USClient Access server language: en-USClient Access server time zone: (UTC-05:00) Eastern Time (US & Canada)Other Microsoft Exchange server roles currently installed on the Client Access server:Authentication type associated with this Outlook Web App session: KerberosPublic logon: NoInternal POP setting:Server name: WCpop.w14c.comcast.netPort: 110Encryption method: TLSInternal IMAP setting:Server name: WCimap.w14c.comcast.netPort: 143Encryption method: TLSCustom Forms: loadedSegmentation settings: fffffffeefc177bfRestricted functionality settings: fffffffeefc177bf