Comcast smtp ?
vining
Posts: 4,368
Today I created a couple secondary email accounts for a customer with Comcast Cable internet service. Now I've done this several times with several providers and I don't recall ever having so much trouble. The secondary accounts all worked from my PC logging in and sending/receiving emails but using the same username and password in i!-EquipmentMonitorOut I would get this:
Line 75 "Smtp Receive-535 5.7.0 ...authentication rejected,"
After several different attempts with out success I looked at line 64 "AUTH LOGIN PLAIN CRAM-MD5" and figured maybe they switched to MD5 encryption. I then spent the next hour re-writing the code to provide MD5 encryption instead of the base 64 and tried it again with out any success. The MD5 ecryption worked fine but I still got "Smtp Receive-535 5.7.0 ...authentication rejected" as shown on line 75 above. I then started googling SMTP and other related crap and I noticed "Receive-334 VXNlcm5hbWU6 & Receive-334 UGFzc3dvcmQ6" in several examples and figured, well that's a coincidence and decided to run those strings through a base 64 decoder and found out they were base 64 encrytions of "username:" & "password:" So now I'm back to base 64 encryption and removed the MD5 stuff. I couldn't really find any meaning behind the "AUTH LOGIN PLAIN CRAM-MD5" while googling but figured if they send me base 64 encryptions they must expect base 64 in return just as the module was written.
The only thing I hadn't tried was the primary username & password so after all this I decided to give it a shot and it worked with out a problem. Go figure!
In the above snippets I removed the actually base 64 encrypted strings so viewers can't run them through decoders and get the valid username and password but why the heck does just the promary email user/pass work and not the 3 or 4 secondary accounts I tried? I can't figure the logic or reasoning why this would be the case. Is this new or have I been just using primary user/pass in the past?
Any ideas?
Line 75 "Smtp Receive-535 5.7.0 ...authentication rejected,"
59 (21:59:29):: Smtp ONLINE, Line-<840> Line 60 (21:59:29):: Smtp Receive-220 OMTA07.emeryville.ca.mail.comcast.net comcast ESMTP server ready, Line-<896> Line 61 (21:59:29):: SMTP Sending-EHLO NetLinx, Line-<617> Line 62 (21:59:29):: Smtp Receive-250-OMTA07.emeryville.ca.mail.comcast.net hello [24.2.208.239], pleased to meet you, Line-<896> Line 63 (21:59:29):: Smtp Receive-250-HELP, Line-<896> Line 64 (21:59:29):: Smtp Receive-250-AUTH LOGIN PLAIN CRAM-MD5, Line-<896> Line 65 (21:59:29):: Smtp Receive-250-SIZE 15728640, Line-<896> Line 66 (21:59:29):: Smtp Receive-250-ENHANCEDSTATUSCODES, Line-<896> Line 67 (21:59:29):: Smtp Receive-250-8BITMIME, Line-<896> Line 68 (21:59:29):: Smtp Receive-250-STARTTLS, Line-<896> Line 69 (21:59:29):: Smtp Receive-250 OK, Line-<896> Line 70 (21:59:29):: SMTP Sending-AUTH LOGIN, Line-<617> Line 71 (21:59:29):: Smtp Receive-334 VXNlcm5hbWU6, Line-<896> Line 72 (21:59:29):: SMTP Sending-"base64 encrypted username", Line-<617> Line 73 (21:59:29):: Smtp Receive-334 UGFzc3dvcmQ6, Line-<896> Line 74 (21:59:29):: SMTP Sending-"base64 encrypted password", Line-<617> Line 75 (21:59:31):: Smtp Receive-535 5.7.0 ...authentication rejected, Line-<896> Line 76 (21:59:31):: Exiting TCP Read thread - closing this socket for local port 23 Line 77 (21:59:31):: CIpEvent::OffLine 0:23:1 Line 78 (21:59:31):: Smtp OFFLINE, Line-<847>
After several different attempts with out success I looked at line 64 "AUTH LOGIN PLAIN CRAM-MD5" and figured maybe they switched to MD5 encryption. I then spent the next hour re-writing the code to provide MD5 encryption instead of the base 64 and tried it again with out any success. The MD5 ecryption worked fine but I still got "Smtp Receive-535 5.7.0 ...authentication rejected" as shown on line 75 above. I then started googling SMTP and other related crap and I noticed "Receive-334 VXNlcm5hbWU6 & Receive-334 UGFzc3dvcmQ6" in several examples and figured, well that's a coincidence and decided to run those strings through a base 64 decoder and found out they were base 64 encrytions of "username:" & "password:" So now I'm back to base 64 encryption and removed the MD5 stuff. I couldn't really find any meaning behind the "AUTH LOGIN PLAIN CRAM-MD5" while googling but figured if they send me base 64 encryptions they must expect base 64 in return just as the module was written.
The only thing I hadn't tried was the primary username & password so after all this I decided to give it a shot and it worked with out a problem. Go figure!
313 (22:06:31):: Smtp Send Line 314 (22:06:31):: Smtp Connecting-smtp.comcast.net:25 on 23 Line 315 (22:06:31):: Memory Available = 20225848 <91048> Line 316 (22:06:32):: Connected Successfully Line 317 (22:06:32):: CIpEvent::OnLine 0:23:1 Line 318 (22:06:32):: Smtp ONLINE, Line-<840> Line 319 (22:06:32):: Smtp Receive-220 OMTA05.emeryville.ca.mail.comcast.net comcast ESMTP server ready, Line-<896> Line 320 (22:06:32):: SMTP Sending-EHLO NetLinx, Line-<617> Line 321 (22:06:32):: Smtp Receive-250-OMTA05.emeryville.ca.mail.comcast.net hello [24.2.208.239], pleased to meet you, Line-<896> Line 322 (22:06:32):: Smtp Receive-250-HELP, Line-<896> Line 323 (22:06:32):: Smtp Receive-250-AUTH LOGIN PLAIN CRAM-MD5, Line-<896> Line 324 (22:06:32):: Smtp Receive-250-SIZE 15728640, Line-<896> Line 325 (22:06:32):: Smtp Receive-250-ENHANCEDSTATUSCODES, Line-<896> Line 326 (22:06:32):: Smtp Receive-250-8BITMIME, Line-<896> Line 327 (22:06:32):: Smtp Receive-250-STARTTLS, Line-<896> Line 328 (22:06:32):: Smtp Receive-250 OK, Line-<896> Line 329 (22:06:32):: SMTP Sending-AUTH LOGIN, Line-<617> Line 330 (22:06:32):: Smtp Receive-334 VXNlcm5hbWU6, Line-<896> Line 331 (22:06:32):: SMTP Sending-"base64 encrypted username", Line-<617> Line 332 (22:06:32):: Smtp Receive-334 UGFzc3dvcmQ6, Line-<896> Line 333 (22:06:32):: SMTP Sending-"base64 encrypted password", Line-<617> Line 334 (22:06:32):: Smtp Receive-235 2.7.0 ... authentication succeeded, Line-<896> Line 335 (22:06:32):: SMTP Sending-MAIL FROM: <customer.email.address@comcast.net>, Line-<617> Line 336 (22:06:33):: Smtp Receive-250 2.1.0 <customer.email.address@comcast.net> sender ok, Line-<896> Line 337 (22:06:33):: SMTP Sending-RCPT TO: <my.email.address@msn.com>, Line-<617> Line 338 (22:06:33):: Smtp Receive-250 2.1.5 <my.email.address@msn.com> recipient ok, Line-<896> Line 339 (22:06:33):: SMTP Sending-DATA, Line-<617> Line 340 (22:06:33):: Smtp Receive-354 enter mail, end with "." on a line by itself, Line-<896> Line 341 (22:06:33):: SMTP Sending Message, Line-<486> Line 342 (22:06:33):: SMTP Sending File-RSSWeather_Return.txt, Line-<547> Line 343 (22:06:33):: SMTP Sending-$0D$0A., Line-<617> Line 344 (22:06:33):: Smtp Receive-250 2.0.0 m26Y1Z00B5ASnQ88R26ZeP mail accepted for delivery, Line-<896> Line 345 (22:06:33):: SMTP Sending-QUIT, Line-<617> Line 346 (22:06:33):: Exiting TCP Read thread - closing this socket for local port 23 Line 347 (22:06:33):: Smtp Receive-221 2.0.0 OMTA05.emeryville.ca.mail.comcast.net comcast closing connection, Line-<896> Line 348 (22:06:33):: CIpEvent::OffLine 0:23:1 Line 349 (22:06:33):: Smtp OFFLINE, Line-<847>
In the above snippets I removed the actually base 64 encrypted strings so viewers can't run them through decoders and get the valid username and password but why the heck does just the promary email user/pass work and not the 3 or 4 secondary accounts I tried? I can't figure the logic or reasoning why this would be the case. Is this new or have I been just using primary user/pass in the past?
Any ideas?
0
Comments