Regular Visitor
•
2 Messages
Outbound email no longer working
My email has been working fine for quite a while (at least a year since the last problem). Suddenly (sometime within the last week) my postfix demon can't connect. I'm getting authentication failures. It's as though my username changed for no reason. I don't know which username or password combination I should be using now (I do know what worked 2 weeks ago).
Note that the XXX content has been redacted for privacy/security purposes. Also note, I've redacted the STARTTLS stuff, but it is using it.
Oct 30 22:18:04 anon postfix/smtp[2924]: > smtp.comcast.net[96.114.157.81]:587: EHLO localhost
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 250-resomta-po-12v.sys.comcast.net hello [XX.XX.XX.XX], pleased to meet you
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 250-HELP
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 250-AUTH LOGIN PLAIN XOAUTH2
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 250-SIZE 36700160
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 250-ENHANCEDSTATUSCODES
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 250-8BITMIME
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 250 OK
Oct 30 22:18:05 anon postfix/smtp[2924]: match_string: smtp_sasl_mechanism_filter: login ~? login
Oct 30 22:18:05 anon postfix/smtp[2924]: match_string: smtp_sasl_mechanism_filter: plain ~? login
Oct 30 22:18:05 anon postfix/smtp[2924]: match_list_match: PLAIN: no match
Oct 30 22:18:05 anon postfix/smtp[2924]: match_string: smtp_sasl_mechanism_filter: xoauth2 ~? login
Oct 30 22:18:05 anon postfix/smtp[2924]: match_list_match: XOAUTH2: no match
Oct 30 22:18:05 anon postfix/smtp[2924]: server features: 0x102b size 36700160
Oct 30 22:18:05 anon postfix/smtp[2924]: maps_find: smtp_sasl_password_maps: smtp.comcast.net: not found
Oct 30 22:18:05 anon postfix/smtp[2924]: maps_find: smtp_sasl_password_maps: hash:/etc/postfix/sasl_passwd(0,lock|fold_fix|utf8_request): smtp.comcast.net:587 = XXX:XXXX
Oct 30 22:18:05 anon postfix/smtp[2924]: smtp_sasl_passwd_lookup: host `smtp.comcast.net' user `XXX' pass `XXX'
Oct 30 22:18:05 anon postfix/smtp[2924]: starting new SASL client
Oct 30 22:18:05 anon postfix/smtp[2924]: name_mask: noanonymous
Oct 30 22:18:05 anon postfix/smtp[2924]: smtp_sasl_authenticate: smtp.comcast.net[96.114.157.81]:587: SASL mechanisms LOGIN
Oct 30 22:18:05 anon postfix/smtp[2924]: > smtp.comcast.net[96.114.157.81]:587: AUTH LOGIN
Oct 30 22:18:05 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 334 VXNlcm5hbWU6
Oct 30 22:18:05 anon postfix/smtp[2924]: xsasl_cyrus_client_next: decoded challenge: Username:
Oct 30 22:18:05 anon postfix/smtp[2924]: xsasl_cyrus_client_get_user: XXXX
Oct 30 22:18:05 anon postfix/smtp[2924]: xsasl_cyrus_client_next: uncoded client response XXXX
Oct 30 22:18:05 anon postfix/smtp[2924]: > smtp.comcast.net[96.114.157.81]:587: XXXX
Oct 30 22:18:06 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 334 UGFzc3dvcmQ6
Oct 30 22:18:06 anon postfix/smtp[2924]: xsasl_cyrus_client_next: decoded challenge: Password:
Oct 30 22:18:06 anon postfix/smtp[2924]: xsasl_cyrus_client_get_passwd: XXXX
Oct 30 22:18:06 anon postfix/smtp[2924]: xsasl_cyrus_client_next: uncoded client response XXXX
Oct 30 22:18:06 anon postfix/smtp[2924]: > smtp.comcast.net[96.114.157.81]:587: XXXX
Oct 30 22:18:06 anon postfix/smtp[2924]: < smtp.comcast.net[96.114.157.81]:587: 535 5.7.0 ...authentication rejected (LS)
Accepted Solution
jhoopDen
Regular Visitor
•
2 Messages
4 years ago
I didn't think anyone was looking at this, but now that I see others are... I found a solution. It appears Comcast decided to change my username to something I'd never heard of before with no warning. I was eventually able to hunt it down in my profile under:
https://customer.xfinity.com/#/settings/security#username-password
I take the value shown under username, tack on @comcast.net. I use the same password that I log into the xfinity portal and the above userid to send email now.
In case anyone is still wondering, here is the relay host line for my postfix config:
relayhost = smtp.comcast.net:587
Note, the easiest way to troubleshoot that I found was to install thunderbird, and then try various combinations of accounts and passwords until I was able to download my Comcast email. That same combo worked to authenticate to the SMTP gateway above.
Good luck
0
0
devroute
New Poster
•
2 Messages
4 years ago
Same problem for me. Was working just fine for a long time and now get "authentication rejected" though I know I am using the right username and password. It has not changed and I can still login to my account with the credentials.
0
RMMM_XF
Frequent Visitor
•
7 Messages
4 years ago
Yes. There are other posts about the same issue, which it appears many people are experiencing. I got through with an agent at Comcast today, but they did not acknowledge the problem. (They told me I should contact the tech support of my email client.)
When I told them I would need to drop Comcast internet if they would not address the issue, they promptly transferred me to the billing department to cancel my Comcast internet account. It appears that they really had non concern whether I remained a customer or got the service they are supposed to provide.
It puts me in a bad situation because at the moment, the only real alternative at my address is CenturyLink, which is no better than Comcast and possibly worse. Fortunately, within 2 years, there will be at least 3 strong competitors in my area, so I won't have to live with CenturyLink forever and will certainly never have to go back to Comcast.
For anyone who's interested, I'd like to start an off-line discussion about ways we could financially damage Comcast to get their attention. If enough of us show interest, I think it's very doable.
0
janismurph
Contributor
•
30 Messages
4 years ago
after unchecking the security box for third party access, I cant send any mail from OUTLOOK. So that didnt help at all
0
0
XfinitySPAAbuse
Official Employee
•
103 Messages
4 years ago
Hello, after review of your uids it does not appear the third-party client access function is enabled. Please review steps in the link below to resolve your issue.
https://www.xfinity.com/support/articles/third-party-email-access
0
0
janismurph
Contributor
•
30 Messages
4 years ago
OK, I did it- now lets see what happens this afternoon. Unfortuneatly I am leaving for PHILA this afternoon at 3, but if it happens, it should happen by 1 or 2. fingers crossed. Thanks for the easy fix.
Janis
0
0
janismurph
Contributor
•
30 Messages
4 years ago
ok, this is the latest, now that I disable the check mark allowing third party access. I cant GET any mail. getting an error message that your email serv rejected your login, Verify usere name and password for acct. The server resonded ERRAUTH less secure auth dissabled
0
0
arcreigh
New Poster
•
2 Messages
4 years ago
I too have begun noticing this.
From my debug on postfix comcasts smtp gateway is rejecting plain / login authentication with a
535 5.7.0 authentication rejected message. the smtp server is now offering a new xoauth2 mechanism however we are not provided with a way to obtain a client ID / secret to be able to make use of this authentication mechanism. This may be the death of using comcasts smtp servers for outbound email via postfix which is quite unfortunate as this has worked for many years for me and came in quite handy when I worked on SMTP servers for the government my home postfix was used to learn how to configure DKIM/DMARC/SPF. I have opened a new ticket with comcast regarding this very issue and hope to hear back from them soon. Unfortunately my entire street is having sporadic network issues on TOP of this recent publicly undocumented unannounced change to comcasts smtp servers I am NOT impressed with comcast as of late.
Their customer support has absolutely NO bennefit to those who are technically sound and frequently results in calls lasting several hours just to get to a higher tier of support.
This problem needs an answer from comcasts SMTP team, if this is in an effort to block those of us who have home email servers from being able to use them that would not surprise me. But the timing of this is just terrible many IT professionals are now working from home and need their home labs to be in a functioning state as they may not have access to a lab environment at work.
0
0
arcreigh
New Poster
•
2 Messages
4 years ago
All,
I found a resolution to this. The comcast employee was not very thorough in his answer but it is the right answer. For those of us that have home email servers we may never login to our comcast email.
We now need to login at least ONCE a year. Under the comcast web email account settings there is a security tab. We need to make sure that the 3rd party box is checked. After some testing I have concluded that email is now flowing as it should. Why this wasn't announced I have no clue.
Upon my initial tests it appeared that comcast may be moving to xoauth2. This still may be the case but for now we are still able to use plain/login auth mechanisms in postfix as long as the above criteria are satisfied. Kind of a pain that we need to login once a year. But that is what we now must do.
0
devroute
New Poster
•
2 Messages
4 years ago
Yep confirmed here as well. The other day I signed into email which I never use and about a day later it started working again. They should count sent mail authetications as keeping the account alive, otherwise we are going to have to login routinely.
0
0
janismurph
Contributor
•
30 Messages
4 years ago
cant this problem be fixed by Comcast.? Are they able to help you? I don't have all the expertise that you have and I dont know how i can fix this problem with Comcast and Outlook. I can send mail thru web mail, and Its Intermittent. I can send mail during the day until 1pm, then i cant until 7pm. Its the weirdest thing. I am hoping comcast can fix my problem.
thank you
0
0