'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Gmail SMTP Error 550-5.7.26 Authentication Failure
Question details
Users are experiencing email delivery rejections from Gmail, receiving an SMTP Error 550-5.7.26 due to unauthenticated senders and failed DKIM or SPF checks.
- Product
- Gmail / Microsoft 365 Exchange
- Device & OS
- not provided
- Scenario
- Sending emails to Gmail addresses from a custom domain, third-party application, or multifunction device.
- Observed behavior
- Gmail rejects the outgoing email and returns a Non-Delivery Report (NDR) citing Error 550-5.7.26, indicating that the email is unauthenticated and fails the domain's DMARC, SPF, or DKIM policies.
Ensure you have administrative access to your domain's DNS hosting provider and your email service admin portal (such as the Microsoft 365 Exchange Admin Center) before attempting to modify authentication records.
Configure SPF and DKIM Records for Your Domain
Setting up accurate Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) records is mandatory to pass Gmail's strict authentication checks and prevent email rejection.
Major email providers like Google have enforced strict email authentication rules. If your domain sends an email without proper cryptographic signatures or authorized IP addresses, Gmail will block it.
You must publish the correct TXT and CNAME records in your domain's DNS settings.
Determine whether your sending domain uses Microsoft 365, Google Workspace, or another SMTP relay service to find the exact SPF value required for your domain.
Log into your DNS hosting provider and add or update a TXT record for SPF. For Microsoft 365, this typically includes 'v=spf1 include:spf.protection.outlook.com -all'.
Generate a DKIM key pair in your email admin center (e.g., Microsoft 365 Defender portal) and publish the provided CNAME or TXT records in your DNS settings to enable cryptographic signing.
Wait up to 24-48 hours for the new DNS records to propagate globally across the internet before sending test emails to a Gmail address.
Run a Message Trace in Microsoft 365
If your domain uses Microsoft 365, running an extended message trace helps identify the exact application, device, or routing issue failing the authentication.
Improve Your Productivity with WPS Office
While troubleshooting email delivery issues and configuring complex DNS settings, you still need a reliable office suite to manage your IT reports, server configurations, and business documents. WPS Office is a lightweight, highly compatible alternative to Microsoft Office that is completely free to use.
- 1. Download WPS Office: Go to the official WPS Office website and download the free installer tailored for your operating system.
- 2. Install the Suite: Run the setup file and follow the straightforward on-screen prompts to install the software on your device.
- 3. Manage your files: Open WPS Office to view, edit, and organize your spreadsheets, reports, and Microsoft Office documents with seamless compatibility.
Frequently Asked Questions
What does Gmail SMTP Error 550-5.7.26 mean?
This error signifies that Gmail has rejected your incoming email because the sending domain failed necessary authentication checks. Gmail strictly requires all external senders to authenticate their emails using SPF or DKIM protocols to prevent spam, phishing, and spoofing.
How long does it take for SPF and DKIM changes to take effect?
DNS changes typically take anywhere from a few minutes up to 48 hours to propagate fully across the internet. If you have just updated your SPF or DKIM records, you may need to wait for this propagation period before Gmail successfully validates and accepts your emails again.
Can a multifunction printer cause SMTP Error 550-5.7.26?
Yes. If a scanner, multifunction printer, or third-party web application sends emails using your domain name without routing through your authenticated SMTP server, the emails will fail SPF and DKIM checks, resulting in this specific Gmail rejection error.
How do I check if my domain's DKIM is working correctly?
You can send a test email to a free DKIM testing service online, or use diagnostic tools like MXToolbox. Perform a DKIM lookup using your domain name and DKIM selector to verify that the public key is correctly published and readable in your DNS settings.
