@Mac.com email addresses not sending from Mail App on Mojave

Discussion in 'macOS Mojave (10.14)' started by blacksurf, Oct 30, 2018.

  1. blacksurf macrumors member

    Joined:
    Sep 6, 2007
    Location:
    UK
    #1
    Anyone else experienced this? I have a (old I know) @mac.com email address. I can receive emails to this address quite happily - along with its matching @icloud.com email. However from the Mail App in Mojave any message I send from @mac.com gets stuck in the outbox.

    Sending from @icloud.com works fine.

    Thoughts? Or has Apple started blocking @mac.com?
     
  2. pullfocus, Oct 30, 2018
    Last edited: Oct 30, 2018

    pullfocus macrumors 65816

    pullfocus

    Joined:
    Sep 17, 2009
    Location:
    LA, CA
    #2
    Noticed this yesterday.

    Occasional hangs, getting asked to "select server" on outgoing mail. Connection doctor not able to log in to smtp.
    Mac address here, too.
    I can't imagine they's just stop allowing its use without notifying anyone.
     
  3. LuisN macrumors regular

    Joined:
    Mar 30, 2013
    Location:
    Torres Vedras, Portugal
    #3
    No problem here
     
  4. hbruss macrumors member

    hbruss

    Joined:
    Nov 15, 2013
  5. arkitect macrumors 603

    arkitect

    Joined:
    Sep 5, 2005
    Location:
    Bath, United Kingdom
  6. joedec macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #6
    Same issue, fails on mac.com its always with SMTP Server p45-smtp.mail.me.com. Yesterday it rejected my email address, today it's timing out also. Logged a service request, iCloud mail has free support BTW. They're "working on it", however the support people don't fully grasp SMTP. I just hope someone on the backend gets it.
     
  7. pullfocus macrumors 65816

    pullfocus

    Joined:
    Sep 17, 2009
    Location:
    LA, CA
    #7
    Talked to Apple Support. iCloud engineering is looking into it, as they've gotten multiple reports of this issue.
    iCloud web client seems to work fine. At least on my end.
     
  8. joedec macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #8
    Thanks! Its good its being looked into, I was hoping there would be enough critical mass to move this forward. Are you failing on the same SMTP server? Just curious.
     
  9. pullfocus macrumors 65816

    pullfocus

    Joined:
    Sep 17, 2009
    Location:
    LA, CA
    #9
    I'll have to double check.

    I have two mac.com addresses and the other one seems t be doing fine. Which is odd.
     
  10. joedec macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #10
    --- Post Merged, Oct 30, 2018 ---
    Seems they’re having trouble with aliases in general. The only address I have that works every single time is my actual Apple ID. The others work intermittently.
     
  11. EdwardC macrumors regular

    EdwardC

    Joined:
    Jun 3, 2012
    Location:
    Georgia
    #11
    Same here as of 10-30-18 14:08 eastern.
     
  12. vjl323 macrumors regular

    Joined:
    Sep 7, 2005
    Location:
    Western North Carolina
    #12
    Same issue here with macOS 10.11 - connections to server p43-smtp.mail.me.com timing out. Worked fine at 8:10am eastern, but since about 11am eastern, no outgoing mail is possible from @mac.com
     
  13. pullfocus macrumors 65816

    pullfocus

    Joined:
    Sep 17, 2009
    Location:
    LA, CA
    #13
    Checked in with Apple Support. Seems they are aware of it being a system-wide issue.

    I did mention they may want to update the system status page to reflect, well...anything.
     
  14. EdwardC macrumors regular

    EdwardC

    Joined:
    Jun 3, 2012
    Location:
    Georgia
    #14
    No doubt, that was the first thing I checked as well.
     
  15. pullfocus macrumors 65816

    pullfocus

    Joined:
    Sep 17, 2009
    Location:
    LA, CA
    #15
    For what it's worth, the icloud web client seems to having no issues. I've been using that until this all gets sorted.
     
  16. grumpzzz macrumors newbie

    Joined:
    Oct 30, 2018
    Location:
    Belgium
  17. arkitect macrumors 603

    arkitect

    Joined:
    Sep 5, 2005
    Location:
    Bath, United Kingdom
    #17
    Hmmmm. Looks like I was being complacent. This evening I am having problems.
    Blah… :(
     
  18. artfossil macrumors 65816

    artfossil

    Joined:
    Oct 5, 2015
    Location:
    Florida
    #18
    Me too.

    Personally, I'm putting it down to demonic possession. :)
     
  19. joedec macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #19
    Looks like they solved the SMTP issue. I can send from @mac.com aliases, and its quick.
     
  20. blacksurf thread starter macrumors member

    Joined:
    Sep 6, 2007
    Location:
    UK
    #20
    Just tried it now and it seems to be working quite happily - sending to myself @mac.com from @mac.com. So guess whatever it was might now be fixed!
     
  21. joedec, Nov 28, 2018
    Last edited: Nov 29, 2018

    joedec macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #21
    Well they did it again, exact problem as last time, I cannot send email from an alias.

    Logged a new ticket this morning. FYI, Apple asked for the previous Support Case ID, I assumed they would have a record, they didn't. So I guess going forward its best to archive the Support Case ID.

    11/29/2018 11:30 PST - resolved
     
  22. vjl323 macrumors regular

    Joined:
    Sep 7, 2005
    Location:
    Western North Carolina
    #22
    That's surprising they had no record of the support case from one month ago! I'd assume that every appleID has attached support cases to it, so a CSR can quickly pull up prior support cases. Very odd they don't do that - I can't see that being a privacy issue, but maybe they do?
     
  23. joedec, Dec 1, 2018
    Last edited: Dec 1, 2018

    joedec macrumors 6502

    joedec

    Joined:
    Jul 25, 2014
    Location:
    Cupertino
    #23
    Apple support said they attach the Support ID to the device serial number. Of course both these tickets were iCloud service, its a mystery what device the previous ticket was charged to, I have quite a few, some in warranty, some not.

    Edit * The CSR was just *uninformed*, I just noticed if you look at the iOS Support App they list Recent History which includes all these calls. The first one was not assigned to any device serial number, its listed as Apple ID/iCloud. So the record was there all along!
     

Share This Page

22 October 30, 2018