If you attempt to send an email through an email client, website plugin, script, or scanner and receive an error stating 554 5.7.1: Relay access denied, 530 5.7.1 Authentication required, or 503 5.7.1 Need to authenticate first, your outgoing message was rejected because the mail server did not receive valid SMTP authentication credentials (or the target domain is not configured to accept mail on that server).
Common Error Variations
Depending on your mail client or server setup, this issue appears as:
554 5.7.1 <recipient@example.com>: Relay access denied530 5.7.1 Authentication required(returned bysmtp.purelymail.comon port465or587when a client tries to send without authenticating first)503 5.7.1 Need to authenticate first(returned on port25if a client attempts to relay mail to an external domain without authenticating)535 5.7.1 Purelymail is not configured to accept mail for this domain(returned when delivering inbound mail to a domain that is not registered on Purelymail or whose Deliver Mail To mode is set to External server (MX))
Why This Happens
An open relay is a mail server that allows anyone on the internet to send email to external domains without logging in. Open relays are immediately exploited by spammers and blocked across the internet.
To protect email deliverability:
- Outbound Sending Requires Authentication: When you connect to
smtp.purelymail.comto send mail to an external address, you must authenticate with a full Purelymail email address (user@yourdomain.com) and password (or an App Password). - Missing Outgoing Credentials: Several email clients (especially Apple Mail on iOS) mark outgoing SMTP credentials as "Optional" in their setup screens. If left blank, the client attempts to send without logging in, and the server rejects the message.
- Unconfigured or Send-Only Domain (
535 5.7.1): If an external server tries to deliver inbound mail tomailserver.purelymail.comfor a domain whose Deliver Mail To setting is set to External server (MX) (or a domain not added to Purelymail), Purelymail refuses the message.
How to Fix It
1. Enable Outgoing SMTP Authentication in Your Email Client
Verify that your email client is configured to authenticate on smtp.purelymail.com (Port 465 with SSL/TLS or Port 587 with STARTTLS) using Normal Password authentication and your full email address:
- iPhone & iPad (Apple Mail): Go to Settings > Apps > Mail > Mail Accounts > [Your Account] > Account Settings > Outgoing Mail Server (SMTP) > smtp.purelymail.com. Even though iOS labels Username and Password as "Optional", you must enter your full email address and password. See How to Set Up Purelymail on iPhone and iPad.
- Mozilla Thunderbird: Under Account Settings > Outgoing Server (SMTP), set Authentication method to Normal password and enter your full email address. See How to Set Up Mozilla Thunderbird.
- Microsoft Outlook & macOS Apple Mail: Check "My outgoing server (SMTP) requires authentication" in Outlook, or verify your outgoing server credentials in macOS Mail. See How to Set Up Microsoft Outlook and Apple Mail on macOS.
- All Other Clients: Review Server Settings: IMAP, SMTP, POP3, and ManageSieve Protocols.
2. Configure Website Plugins, Scanners & Scripts (WordPress, Printers, Apps)
If you are configuring a website contact form, WordPress SMTP plugin, scanner, or backend script:
- SMTP Host:
smtp.purelymail.com - Port:
465with SSL/TLS (recommended) or587with STARTTLS - SMTP Authentication: Enabled / Yes
- Username: Your full Purelymail email address (e.g.,
notifications@yourdomain.com) - Password: Your mailbox password, or a Send Email Only (SMTP) App Password
- From Address: Must belong to a domain owned by your account (see Error: 530 5.7.1 "You are not authorized to send mail as...").
3. Verify Custom Domain Delivery Mode (`535 5.7.1`)
If incoming mail to your custom domain is bouncing with 535 5.7.1 Purelymail is not configured to accept mail for this domain:
- Log into the Purelymail Account Admin portal, open Domains (purelymail.com/manage/domains), and click on your domain.
- Ensure Deliver Mail To is set to Purelymail (not External server (MX)) and click Save. See Custom Domain Delivery Modes: Purelymail vs. Relay vs. External server (MX).
Still Need Help?
If you've followed these steps and are still running into trouble, check our Purelymail Support guide.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article