Email Forwarding: 554 5.7.1 : Relay access denied

Website, Application, Performance DNS & Network
1

What is the name of the domain?

codeandcraft .co .uk

What is the error number?

n/a

What is the error message?

Message not delivered Your message couldn’t be delivered to hello @ codeandcraft .co .uk because the remote server is misconfigured. See the technical details below for more information. The response from the remote server was: 554 5.7.1 : Relay access denied

What is the issue you’re encountering

Emailing routing issue. Domain is with Namecheap. I’ve successfully set up email forwarding in Cloudflare to my gmail account from a custom email address: ian@ I’ve added a second custom email address, hello@ but when I click verify email in Gmail settings I get an email message from mailer -daemon @ googlemail. com to say Delivery Status Notification (Failure) Message not delivered Your message couldn’t be delivered to hello @ codeandcraft .co .uk because the remote server is misconfigured. See the technical details below for more information. The response from the remote server was: 554 5.7.1 : Relay access denied. I’ve tried a number of times but keep getting the same error. There’s lots of posts about this error but nothing that relates to it happening on a second instance of the same custom domain.

What steps have you taken to resolve the issue?

I’ve tried creating a second app password in Google for the second custom email address.
I’ve tried turning the catch all address on in Cloudflare Email Routing settings.
Dmarc and SPF are set up.

What feature, service or problem is this related to?

Mail records

What are the steps to reproduce the issue?

Send verification email from Gmail Settings > Accounts & Imports > Send Mail As

Screenshot of the error

CleanShot 2024-12-23 at 15.43.16@2x.png
CleanShot 2024-12-23 at [email protected]1476×1090 64.5 KB

2

What SMTP server are you trying to use as your outbound relay when you are configuring Gmail to Send as your custom email?

I notice you have an include mechanism in your SPF record that contains _spf.google.com. That is unlikely to do anything useful for you, as your domain email is not going to be relayed by a mailserver in that IP space. You will want to use an include mechanism provided by your outbound email provider.

1 Like
3

Thanks for your reply.

I’m using smtp.gmail.com

I have followed this guide:

It works perfectly for the first email I set up but the second one (using the same method and only changing the first part of the email) causes the error message.

4

It’s working now. I hadn’t tried it again before writing the last post so looks like it just needed some time to update I guess (it’s five days since I last tried it).

Emails now sending and being received correctly.

1 Like
5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.