SMTP block for outgoing emails on iCloud, Yahoo, and Gmail using Apple Mail on MacOS

Beginning in mid‑January, Apple Mail on my Mac lost the ability to send outgoing email across all configured accounts. Because the failure affects three unrelated providers (iCloud, Yahoo, Gmail), the issue is not account‑specific, not tied to a single service, and not caused by user‑side settings. The pattern instead points to a network‑level SMTP authentication block or provisioning failure affecting outgoing mail authorization.

During troubleshooting, Apple Mail consistently produced SMTP authentication errors, including:

• “Cannot send message using the server [server name]. The server did not accept the password.”
• “Authentication failed because the password or authentication method is incorrect.”
• “The SMTP server is offline.” even though the server was reachable and incoming mail continued to work.

In addition, Apple Mail displayed symptoms that occur when the underlying SMTP authorization chain cannot refresh:

• Duplicate or outdated SMTP server entries appeared and could not be removed.
• The correct outgoing server would appear grayed out or revert to an older entry.
• Removing and re‑adding accounts did not resolve the issue because the SMTP token chain was not refreshing.

These symptoms are not caused by local configuration. They are consistent with a network‑level block or provisioning error preventing proper SMTP handshake and token renewal.

As part of the troubleshooting process, I deleted and re‑added all of my email accounts (Yahoo, Gmail, and iCloud) and allowed macOS to rebuild both the IMAP and SMTP configurations from scratch. I also deleted and re‑added the outgoing SMTP servers manually.

Despite this complete rebuild:

• The same SMTP authentication failures persisted.

• The same “server did not accept the password” errors continued.

• The same inability to refresh SMTP tokens remained.

This confirms that the issue is not caused by local configuration, corrupted settings, or user error. A full account and server rebuild should have resolved any device‑side issue, but it did not.

During our troubleshooting, the pattern of failures (including the inability of three unrelated providers to authenticate outgoing mail, the repeated “server did not accept the password” errors, and the inability of macOS to refresh SMTP tokens) matched the behavior of an SMTP block on the line or account.

This type of block would directly interfere with:

• SMTP authentication
• Token refresh
• Outgoing mail authorization
• Device‑level credential validation

This is not something a user can fix, nor something caused by Apple Mail. It requires review and correction within Xfinity’s provisioning or authentication systems.

I am requesting escalation to a technical group with the authority and expertise to address SMTP authentication‑chain and provisioning failures, including the block identified during troubleshooting. Specifically, I need:

• Removal of any network‑level or account‑level SMTP blocks affecting outgoing mail authorization or token renewal.
• Verification that my account is correctly provisioned for third‑party email clients on macOS, including outgoing mail.
• Confirmation that no internal filters, flags, or outdated authentication profiles are preventing proper SMTP handshake.
• Coordination with engineering to reset or rebuild the authentication profile associated with my account if necessary.
• Direct communication from a supervisor or technical specialist who can explain the findings and corrective actions.