Reply
Contributor
Posts: 6
Registered: ‎09-11-2008
Accepted Solution

MobileMe, iMail, and Comcast

Wow--I really need some help. Ever since I signed up for MobileMe and tried to set up my account, my iMail does not work. Before MobileMe, sometimes my mail would not be delivered, so I thought MobileMe would improve things. Guess not. Neither Comcast nor Apple has been helpful.

 

Now I've tried to go back to just Comcast without MobileMe. Comcast rejects my password, so I can't send any mail out (I can get mail in). SmartZone works, but I don't like it. Any suggestions?

 

Here's just some of the "details" from Connection Doctor from today when I tried to connect using my smtp Comcast account, gmail account, or MobileMe account.

 

Thanks for ANY help you can give me!

 

flenzo

 

 

 

WROTE May 16 08:54:30.311 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700EHLO [192.168.1.107]
READ May 16 08:54:30.312 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90220 asmtpout018.mac.com -- Server ESMTP (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010))
READ May 16 08:54:30.331 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30250-mx.google.com at your service, [68.48.73.56]250-SIZE 35882577250-8BITMIME250-STARTTLS250 ENHANCEDSTATUSCODES
WROTE May 16 08:54:30.355 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560CAPA
READ May 16 08:54:30.377 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700250-omta15.westchester.pa.mail.comcast.net hello [68.48.73.56], pleased to meet you250-HELP250-AUTH LOGIN PLAIN250-SIZE 15728640250-ENHANCEDSTATUSCODES250-8BITMIME250 OK
WROTE May 16 08:54:30.404 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90EHLO [192.168.1.107]
WROTE May 16 08:54:30.424 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30STARTTLS
READ May 16 08:54:30.448 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560+OK Capability list followsTOPUSERUIDLSTLSEXPIRE 31 USER.
WROTE May 16 08:54:30.475 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700AUTH PLAIN  (*** 32 bytes hidden ***)
READ May 16 08:54:30.497 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90250-asmtpout018.mac.com250-8BITMIME250-PIPELINING250-CHUNKING250-DSN250-ENHANCEDSTATUSCODES250-EXPN250-HELP250-XADR250-XSTA250-XCIR250-XGEN250-XLOOP DC576CA7D8AB97FD0ED5D26FB1A6887A250-STARTTLS250-AUTH PLAIN LOGIN250-AUTH=LOGIN PLAIN250-ETRN250-NO-SOLICITING250 SIZE 0
READ May 16 08:54:30.523 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30220 2.0.0 Ready to start TLS
WROTE May 16 08:54:30.551 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560USER flenzo
WROTE May 16 08:54:30.602 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90STARTTLS
READ May 16 08:54:30.658 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560+OK
READ May 16 08:54:30.694 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90220 2.5.0 Go ahead with TLS negotiation.
WROTE May 16 08:54:30.711 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560PASS ************
WROTE May 16 08:54:30.784 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30EHLO [192.168.1.107]
READ May 16 08:54:30.825 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30250-mx.google.com at your service, [68.48.73.56]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH250 ENHANCEDSTATUSCODES
WROTE May 16 08:54:30.854 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30AUTH PLAIN  (*** 52 bytes hidden ***)
READ May 16 08:54:31.026 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560+OK server ready
WROTE May 16 08:54:31.058 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560QUIT
WROTE May 16 08:54:31.081 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90EHLO [192.168.1.107]
READ May 16 08:54:31.086 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:mail.comcast.net -- port:995 -- socket:0x11ec57030 -- thread:0x1164a5560+OK sz0063.wc.mail.comcast.net closing connection
READ May 16 08:54:31.178 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90250-asmtpout018.mac.com250-8BITMIME250-PIPELINING250-CHUNKING250-DSN250-ENHANCEDSTATUSCODES250-EXPN250-HELP250-XADR250-XSTA250-XCIR250-XGEN250-XLOOP DC576CA7D8AB97FD0ED5D26FB1A6887A250-AUTH PLAIN LOGIN250-AUTH=LOGIN PLAIN250-ETRN250-NO-SOLICITING250 SIZE 0
WROTE May 16 08:54:31.207 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90AUTH PLAIN ****************************
READ May 16 08:54:31.242 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30535-5.7.1 Username and Password not accepted. Learn more at                   535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 x61sm2355168yhn.48
WROTE May 16 08:54:31.267 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.gmail.com -- port:587 -- socket:0x11ecb3bc0 -- thread:0x115876a30QUIT
READ May 16 08:54:31.304 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90235 2.7.0 PLAIN authentication successful.
WROTE May 16 08:54:31.330 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:smtp.me.com -- port:25 -- socket:0x11ec73190 -- thread:0x11db39b90QUIT
READ May 16 08:54:31.555 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700535 5.7.0 ...authentication rejected (2)
WROTE May 16 08:54:31.585 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700QUIT

 

Web Page Expert
BethKatz
Posts: 6,160
Registered: ‎11-14-2006

Re: MobileMe, iMail, and Comcast


flenzo wrote:

Wow--I really need some help. Ever since I signed up for MobileMe and tried to set up my account, my iMail does not work. Before MobileMe, sometimes my mail would not be delivered, so I thought MobileMe would improve things. Guess not. Neither Comcast nor Apple has been helpful.

 

Now I've tried to go back to just Comcast without MobileMe. Comcast rejects my password, so I can't send any mail out (I can get mail in). SmartZone works, but I don't like it. Any suggestions?

 

Here's just some of the "details" from Connection Doctor from today when I tried to connect using my smtp Comcast account, gmail account, or MobileMe account.

 

Thanks for ANY help you can give me!

 

flenzo

 

 

...

READ May 16 08:54:30.377 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700250-omta15.westchester.pa.mail.comcast.net hello [68.48.73.56], pleased to meet you250-HELP250-AUTH LOGIN PLAIN250-SIZE 15728640250-ENHANCEDSTATUSCODES250-8BITMIME250 OK
......


READ May 16 08:54:31.555 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700535 5.7.0 ...authentication rejected (2)
WROTE May 16 08:54:31.585 [kCFStreamSocketSecurityLevelNegotiatedSSL]  -- host:smtp.comcast.net -- port:465 -- socket:0x11dba6980 -- thread:0x116eb5700QUIT

 


Could you please check that you have only one smtp.comcast.net account? You have one early in the list that seems to be fine and one later in the list that gets rejected. 

 

Go to Mail / Preferences / Accounts and choose one. At the bottom is Outgoing Mail Server. On the pop-up list, choose Edit SMTP server list and see what's there.

Networking Expert
Baric
Posts: 24,238
Registered: ‎07-28-2003

Re: MobileMe, iMail, and Comcast

Looks to me like the userid and password you have stored for smtp.comcast.net is invalid or corrupt.  The conversation is normal until your login was rejected.  I would go into the smtp.comcast.net setting and reset the userid and password (remember the password is case sensitive).  Also, you userid is NOT your email address, it's just the userid portion of the address, ie. whatever is BEFORE @comcast.net.

 

You also need to check your Gmail userid and password, although its rejection contains more specific information along with a link to unlock your account if necessary.  The link basically says the same, check your stored userid and password in your client settings and make sure you don't check for new mail more often than every 10 minutes.

Contributor
Posts: 6
Registered: ‎09-11-2008

Re: MobileMe, iMail, and Comcast

Under smtp accounts, it says there are Comcast, gmail, and MobileMe accounts and no duplicates of any of those.

Contributor
Posts: 6
Registered: ‎09-11-2008

Re: MobileMe, iMail, and Comcast

That took care of the problem! Thanks. And thanks over and over again!

 

But I'm not clear what happens when I use gmail, an IMAP, with Comcast, a POP, so I can use MobileMe in iMail with Comcast. All my mail comes in via Comcast, but goes out via gmail? How can it come in via Comcast?  

Networking Expert
Baric
Posts: 24,238
Registered: ‎07-28-2003

Re: MobileMe, iMail, and Comcast

Glad you got it working.

 

Just to clarify, it's not iMail, it's Mail or Mac Mail. IMail is a business oriented email server for Windows, has nothing to do with Apple or Macs.

 

As for how they all work together, they really don't interact with each other.  Mac Mail is simply an email client and it will check each account that is defined for new messages.  Each is kept in their own folders on the hard drive if a POP account, or you will see a view of the folders on the server if an IMAP account.  You can pick the individual inboxes in the left hand pane.  If you have an IMAP account defined, it's folders show up at the bottom of the pane after the On My Mac and RSS stuff.

 

Each defined account is assigned to use one of the defined SMTP servers.  It's most common to use the Gmail SMTP server with sending messages from your Gmail address, etc.  That SMTP association is eaxctly where Beth pointed you at, for each account you simply pick one server in that list.  Now when you send a message, in the New Message dialog there is a From dropdown list right underneath the Subject field.  If you want to send a message from your GMail userid, simply select it here.  When you send, it will use the SMTP server defined for your Gmail account.  It also remembers the last one you have selected, so when you come in again, it's the same selected account until you change it.

 

When you reply or forward a message you received in a particular account, that account is automatically used to send the reply or forward so you don't have to set it manually.  You can change that if you like to any of your defined accounts, but that's purely up to you.

 

And just because you are using Comcast as your Internet connection, your Gmail and MobileMe messages are still coming from those systems, you are simply using your Comcast service as a transport conduit, the Comcast email servers are not involved at all unless you check them explicitly.  Think of the Internet and your Comcast service as a network of roads and servers as buildings on those roads.  Some of those buildings are owned by Comcast, like their email servers and web servers, and many others are not, like the Google Gmail server or Apple's MobileMe servers.  To get to each of these buildings you have to drive over the Comcast owned roads, and other roads owned by other ISP's.  Comcast does not restrict you from what you are using the road for (in most cases), so you can use any email system you want, and simply ignore the Comcast buildings if you so desire.

 

Many of us have and use multiple email systems.  For example, I use many of the same systems you use, Comcast, Gmail, and Mobile Me, a Yahoo Rocketmail account, as well as other more restricted systems.  These are all setup in Mac Mail.  I really like the Unread messages smart mailbox, it combines all unread messages from all accounts in one place so I don't have to visit each and every Inbox to see what's there.  If you have only one email account setup, some of these features are of no use, but to all those others who use email extensively on multiple systems, they are very, very useful.

Contributor
Posts: 6
Registered: ‎09-11-2008

Re: MobileMe, iMail, and Comcast

Thank you, Baric, for taking the time to explain all that to someone who is really in the dark about all this. 

 

If I understand you correctly, if I want to use only my MobileMe mail (and not my Comcast mail program), I do not have Comcast set as either my incoming or outgoing mail in Mac Mail's preferences? But then do I have my gmail as my outgoing and incoming mail program in Mac Mail because it is POP?

 

In other words, would you kindly give me the settings I need to use for sending and receiving MobileMe mail on my Comcast account? 

 

And, since you know these things, would you tell me why folks who have a Verizon mail account cannot receive any of my mac Mail sent via my Comcast account? It's consistent--it never fails. However, they can receive my mail from Comcast's Smart Zone, but not using mac Mail. Any explanation?

 

Thanks again for your help.

Networking Expert
Baric
Posts: 24,238
Registered: ‎07-28-2003

Re: MobileMe, iMail, and Comcast

You can have as many accounts setup in Mac Mail as you want, whether they be Gmail, MobileMe, Comcast, Hotmail, or whatever.  If you don't want to setup your Comcast email account, then great, that's your choice.  I would recommend you do, however, and at least check that mailbox (Comcast Primary userid) once a week or so, because that's where Comcast will send service oriented emails.  Sometimes they are important...

 

I'll just point you at setup instructions for Gmail and MobileMe since they have nothing to do with Comcast.  Each email provider has their own servers and preferred ports.  Wtih Gmail you have the choice of POP or IMAP, Google supports both access methods and you decide which to use when you setup that individual account in Mac Mail.

 

Setting up MobileMe email on your Mac

 

Other ways to access Gmail

 

As for your messages not getting through, do you mean messages sent through the Comcast SMTP server?  If so, I would recommend you post your exact problem with details in the Email Help forum (as this isn't a Mac specific issue).  Blocked and dropped messages are a real problem these days because every provider uses different rules and criteria and it's very easy to run afoul of these rules in unexpected ways.  Verizon especially is know to have a very quick trigger finger on blocks, but it might just as well be Comcast's fault.  For example, many people have this kind of trouble when a message is sent that contains a URL or has a sig that contains a URL that points at a place known for spamming.  Certain blogging sites have this trouble, like blogspot which is known to be involved in spamming or as a spam conduit.  So when Comcast or another provider sees a message with a problematic URL, the message gets dropped as spam, even though that particular message isn't.  Guilt by association ;-(.