TS3103: Mac OS X v10.6: Unable to receive POP mail after updating to 10.6.2
Learn about Mac OS X v10.6: Unable to receive POP mail after updating to 10.6.2Q: Able to send mail and it goes to the send folder, but mail does not actually go anywhere. Sent several test emails to myself and t ... Able to send mail and it goes to the send folder, but mail does not actually go anywhere. Sent several test emails to myself and the vanish. No error message received. more
-
All replies
-
Helpful answers
-
Mar 15, 2013 1:41 PM in response to Johnnyd18by MrHoffman,Launch the Connection Doctor tool (Mail.app Window > Connection Doctor), and post what is reported by that after purging any personally-identifying information.
-
Mar 15, 2013 2:01 PM in response to Johnnyd18by Johnnyd18,Connesction and Login to Server Succeeded is what it says. Been saying that all along, but the email is never received - even ones I send to myself on the same server. I have no problem on the other email accounts like gamial, seems to be isolated to outbound emails on Comcast.
Thanks for the reply!
-
Mar 16, 2013 4:33 AM in response to Johnnyd18by MrHoffman,★HelpfulI'm going to assume that bypassing the Comcast and moving to your own domain served from a different commercial hosting provider is not an option. (That approach usually has better support.)
There are various reasons servers will drop mail, or will not forward mail, or the mail forward from the servers will get dropped. That logging and that information is not generally visible to a client of the mail servers, unfortunately.
There's either something wrong with the Comcast servers, or your setttings differ between your OS X system and your iOS devices.
Does mail sent to yourself on the Comcast servers with your Comcast email address get received, or does everything sent from OS X to that mail server disappear?
With OS X, make certain that the selected SMTP server is the appropriate one for Comcast, as an account entry on OS X can have various mail servers, ports and SSL/TLS or not. (You're probably aware that there are two separate passwords and two separate connections — the receive path via POP or IMAP and the send/SMTP path — with each account, but it's worth verifying the settings. It's unfortunately easy to get the SMTP servers settings tangled as they're fairly well hidden in most account setups.)
One common brute-force option is to delete and re-add the entry. Remove the POP/IMAP account and the SMTP server account, then clear out any of remaining passwords that might lurk in the Keychain for the POP/IMAP receive server and SMTP server send path, then re-add the account in Mail.app.
-
Mar 16, 2013 9:43 AM in response to Johnnyd18by Johnnyd18,I used the "brute Force" method after trying everything else. It worked and then when I added my signature to the preferences for the email - it stopped workinh. I deleted the signature which I copied from another account I have and made a new signature for theis account and it seems to be working.
Thanks for the tips - liiks like there may have been some type of conflict with the signature from the other account and outgoing email from the Comcast account.