Email glossary · Practical guide
SMTP AUTH: authenticate the submission connection
SMTP AUTH authenticates a client to a submission service. Depending on the provider and client, it can use different supported mechanisms; it is not synonymous with a main account password.
Reviewed · Examples are illustrative
Who this helps: Readers checking a term before making an outreach or mailbox decision.
Meaning and common confusion
A provider may support OAuth for SMTP while still controlling whether SMTP AUTH is enabled for an organization or mailbox. The protocol setting and credential method are separate checks. An OAuth consent success does not prove the endpoint will accept authenticated submission.
Worked example
This is a synthetic illustration, not a customer result or a live configuration to copy.
OAuth token: available
SMTP AUTH policy: disabled
Outcome: the transport workflow still cannot proceed as configured
Review policy with the responsible administrator instead of changing a DNS record.Checks to make
- Identify the exact authentication mechanism in use.
- Check applicable organization and mailbox settings.
- Confirm the application supports the provider's permitted method.
Next step and limits
Use Microsoft's SMTP AUTH guide for that provider's policy layers. Do not broadly weaken security defaults to repair one application without an authorized security decision and appropriate alternative controls. Zintara cannot override provider policy.
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Microsoft SMTP AUTH disabled: inspect the effective mailbox policy →
- Microsoft 365 SMTP AUTH with OAuth: check protocol and permission separately →