Skip to content
Microsoft (Outlook.com and Microsoft 365) · permanent error

535 5.7.142: HVE: OAuth token about to expire

The OAuth access token an application used to authenticate to HVE was close to expiring, so Exchange Online rejected it.

Microsoft
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
535 5.7.142
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.
What the server says
535 5.7.142 XOAUTH2 authentication failed. Token will expire soon.

What it means

HVE accounts can authenticate with OAuth through XOAUTH2. Exchange Online rejects an access token that is close to expiration and returns 535 5.7.142. The client must request a new token and retry authentication. Microsoft's advice is to make sure the session time does not exceed the token's expiry time, and to obtain a fresh token whenever possible.

Common causes

  • The application reused an access token near the end of its lifetime.
  • A long-running SMTP session started with a token that would expire during the session.

How to fix it

  1. 01Request a new OAuth token and retry authentication.
  2. 02Refresh tokens before they near expiry rather than waiting for a failure.
  3. 03Keep each SMTP session shorter than the remaining token lifetime.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 535 5.7.143HVE: OAuth token expired.The application tried to authenticate to HVE with an OAuth access token that had already expired.MicrosoftPermanent
  2. 535 5.7.144HVE: app lacks the right API permissions.The OAuth token came from an app registration whose API permissions do not allow it to use HVE, so authentication failed.MicrosoftPermanent
  3. 535Authentication credentials invalid.The server rejected the login because the username, password or token is wrong or not sufficient for this account, so no mail is sent.StandardPermanent

All 111 Microsoft codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer