Verify any claim · lenz.io
“Mailgun configured with a Gmail account does not permit third-party email clients, including Apple Mail, to send email through that configuration.”
The conclusion
The evidence does not support a blanket prohibition on sending from Apple Mail or other third-party clients. Gmail permits supported clients using OAuth, and Apple Mail can also use Mailgun's SMTP service with appropriate credentials. Legacy password authentication and restrictions on presenting Gmail addresses through external services may block particular setups, but they do not establish a general ban.
Caveats
- Low confidence conclusion.
- Gmail's retirement of legacy password authentication does not prohibit third-party clients that support OAuth.
- Gmail anti-spoofing and sender-identity rules may prevent some Gmail-address configurations even when SMTP access works.
- Several Mailgun-specific examples come from dated or nonauthoritative community and vendor sources.
Fact-check inside the tools you already use
Connect Lenz to ChatGPT, Claude, or WhatsApp and check a claim mid-conversation.
Or create a free account to bookmark this verification and run your own checks.
Sources
Ranked by source quality and relevance
Google Workspace accounts no longer support less secure apps, third-party apps, or devices that ask you to sign in to your Google Account with your username and password. You must use OAuth to let these apps and devices access your account. Third-party email apps that are no longer supported include Microsoft Outlook and the mail app on iOS and macOS.
Google Workspace accounts no longer support less secure apps, third-party apps, or devices that ask you to sign in to your Google Account with your username and password. You must use OAuth to let these apps and devices access your account. Third-party email apps that are no longer supported include Microsoft Outlook and the mail app on iOS and macOS.
Google has implemented a stricter policy (p=quarantine), disallowing email spoofing. This means that sending from a Gmail sender address is now restricted exclusively to Gmail mail, preventing unauthorized use.
Your users might want to send and receive mail from other email clients, for example Microsoft Outlook or Apple Mail. This document has steps for admins and users to set up Gmail with another mail client.
Your users might want to send and receive mail from other email clients, for example Microsoft Outlook or Apple Mail. This document has steps for admins and users to set up Gmail with another mail client.
You are reading this article as you are using Apple Mac Mail and need to configure it for use with mailgun SMTP.
Beginning in July of 2015, I've been unable to send mail using the Mailgun SMTP server using Mac Mail. … I tried sending with swaks and was successful, though I had to change the password provided by Mailgun's example.
For sending, I used Gmail’s ‘Send mail as’ feature, configuring it with Mailgun’s SMTP settings.
Can you add domains to Mailgun, create SMTP records, add these settings to GMail/Outlook/Apple Mail and use as normal mail accounts?
Continue your research
Verify a related claim next.
Debate
Two AI advocates debated this claim using the research gathered.
Argument for
Google's official Workspace guidance states that third-party clients using Gmail username-and-password authentication are no longer supported and expressly identifies the iOS/macOS mail app, while requiring OAuth instead (Sources 1 and 2). Mailgun further states that Gmail sender addresses are restricted exclusively to Gmail mail to prevent unauthorized use (Source 3), so a Mailgun configuration based on a Gmail account cannot serve as a sending route for third-party clients such as Apple Mail.
The Proponent misapplies Sources 1 and 2, which address only Google Workspace bans on password-based less-secure apps rather than Mailgun SMTP relay or OAuth-capable setups, and overreads Source 3's anti-spoofing note as a blanket ban on third-party clients. Official setup guides in Sources 4 and 5 plus working Mailgun-to-Apple-Mail and Gmail “Send mail as” configurations in Sources 6 and 8 show that third-party clients remain able to send through such a configuration.
Argument against
The claim is false because Source 6 (jucra.com) explicitly documents configuring Apple Mac Mail to send via Mailgun SMTP, and Sources 4 and 5 (knowledge.workspace.google.com and support.google.com) provide official steps for admins and users to set up Gmail with third-party clients including Apple Mail. Source 8 (community.latenode.com) further confirms sending works by pairing Gmail's “Send mail as” with Mailgun's SMTP settings, so third-party clients are not barred from that configuration.
The Opponent conflates configuring Apple Mail directly with Mailgun SMTP (Source 6, a low-authority hosting knowledge-base article) and configuring Gmail itself in a third-party client; Sources 4 and 5 describe the latter and therefore do not establish that Apple Mail may send through a Mailgun configuration based on a Gmail account. Source 8 concerns Gmail's own “Send mail as” feature rather than third-party-client sending, while Google expressly excludes the iOS/macOS mail app when it authenticates with Gmail credentials absent OAuth (Sources 1 and 2) and Mailgun states Gmail sender addresses are restricted to Gmail mail (Source 3).
Panel Review
3 reviewers assessed the evidence and the arguments.
Reviewer 1 — The Logic Examiner
The evidence shows that Google Workspace accounts no longer support less secure apps (like Apple Mail) using username/password authentication, requiring OAuth instead (Sources 1, 2). However, Sources 4 and 5 explicitly state that Gmail can be set up with third-party clients like Apple Mail, and Source 6 shows Apple Mail can be configured with Mailgun SMTP, meaning the claim that Mailgun configured with a Gmail account 'does not permit' third-party clients is overly broad and false, as it only restricts non-OAuth authentication.
Reviewer 2 — The Source Auditor
The claim conflates two distinct configurations: (a) Apple Mail authenticating directly to Gmail's SMTP servers with a username/password, which Google (Sources 1, 2 — official Google support pages) has indeed deprecated in favor of OAuth, and (b) using Mailgun as a relay 'configured with a Gmail account' (e.g., via domain verification or Gmail's 'Send mail as' feature), which Sources 6, 8, and 9 show is a distinct, commonly-used setup where Apple Mail or other clients send through Mailgun's own SMTP credentials rather than Gmail's password auth, so Google's OAuth requirement is irrelevant to it. Mailgun's own help article (Source 3) discusses DMARC/spoofing restrictions on the 'From' header, not a technical block on third-party clients relaying through Mailgun, so the most relevant and authoritative sources (Mailgun's own documentation plus practical configuration guides) do not support a blanket claim that third-party clients cannot send via Mailgun-Gmail configurations; the claim is therefore mostly false, though the underlying confusion about Google's password-auth deprecation gives it a kernel of truth in a narrow scenario.
Reviewer 3 — The Precision Analyst
The claim's absolute phrasing that Mailgun configured with a Gmail account "does not permit" third-party clients including Apple Mail to send is stronger than the evidence licenses: Sources 1–2 restrict only password-based less-secure apps (requiring OAuth), Source 3 limits Gmail-address spoofing to Gmail itself, while Sources 4–6 and 8 document workable third-party/Apple Mail and Mailgun SMTP or "Send mail as" setups. As worded the claim therefore overgeneralizes partial authentication and anti-spoofing limits into a blanket ban that the evidence does not support.
Panel summary
Official Google guidance confirms that Gmail supports third-party clients, including Apple Mail, when supported authentication such as OAuth is used. It also shows that restrictions target legacy username-and-password authentication rather than third-party clients generally. Mailgun-related configuration guides indicate that clients can send through Mailgun SMTP credentials, although several supporting guides are dated or nonauthoritative. Logically and technically, the claim conflates Gmail authentication requirements and sender anti-spoofing rules with a complete prohibition. Its absolute wording is therefore largely unsupported, while retaining a narrow kernel of truth for obsolete authentication methods or noncompliant Gmail sender configurations.