Cloudflare Developers•3y ago

Routing rules (all disabled now)

WuppieOP•11/8/23, 11:37 AM

Destination addresses

WuppieOP•11/8/23, 11:38 AM

Settings

WuppieOP•11/8/23, 11:38 AM

That is most of the information as far as I can see - or is there something else that might be useful?

WuppieOP•11/8/23, 11:39 AM

This is the bounce/refuse message when using an external mail to test (outlook)

WWuppie This is my setup in Plesk

DarkDeviL•11/8/23, 11:40 AM

Assuming the blurred out domain is

example.com

example.com

, ... is the records@example.comrecords@example.com on this Plesk screenshot

WWuppie Routing rules (all disabled now)

DarkDeviL•11/8/23, 11:40 AM

100% identical to the "Custom address" here, which would also say records@example.comrecords@example.com?

DarkDeviL•11/8/23, 11:41 AM

Or are they different domains?

WuppieOP•11/8/23, 11:41 AM

All same domain - and I copy paste and double verified them (by searching the text from one to the other)

DarkDeviL•11/8/23, 11:41 AM

That would be the actual problem.

DarkDeviL•11/8/23, 11:42 AM

You have configured Cloudflare to handle messages (MX records) for

example.com

example.com

DarkDeviL•11/8/23, 11:42 AM

Cloudflare gets an email message, and wants to pass it on to

example.com

example.com

, since

example.com

example.com

's MX are Cluodflare, Cloudflare will re-try over and over, to deliver to itself.

WuppieOP•11/8/23, 11:42 AM

huh...

WuppieOP•11/8/23, 11:42 AM

interesting, I did not understand that correctly

DarkDeviL•11/8/23, 11:43 AM

You would have to change e.g. your Plesk configuration to handle mails for e.g. @internal.example.com@internal.example.com instead.

DarkDeviL•11/8/23, 11:43 AM

So Cloudflare records@example.comrecords@example.com forwards to records@internal.example.comrecords@internal.example.com, where internal.example.cominternal.example.com would be on your Plesk.

WuppieOP•11/8/23, 11:44 AM

I assumed cloudflare would take over the email delivery, and then still send it to info@domain.com and I could open it in my plesk mailbox

WuppieOP•11/8/23, 11:45 AM

Because as I understand it Cloudflare itself is not a mailbox

DarkDeviL•11/8/23, 11:45 AM

Cloudflare takes care of receiving from the public, but would need somewhere to pass it over to.

DarkDeviL•11/8/23, 11:45 AM

If you're there trying to pass it over to itself - you got (endless) loop.

WuppieOP•11/8/23, 11:45 AM

Mmm yeah I am starting to understand ghehe

WuppieOP•11/8/23, 11:46 AM

Think this could be quite easily detected during the Cloudflare setup - might be a nice UI improvement. As it should not allow these addresses to be the same?

WuppieOP•11/8/23, 11:46 AM

OK I think I see what you mean

WuppieOP•11/8/23, 11:46 AM

And how woudl this work with internal emails, f.e. from server (wordpress) to receivers?

WuppieOP•11/8/23, 11:47 AM

They would use Cloudflare email servers - and I can still use the original email address for that

DarkDeviL•11/8/23, 11:48 AM

The place where Email Routing is interesting, would be if you already got john.doe@example.comjohn.doe@example.com (and

example.com

example.com

) running on an expensive provider. However, in order to add your secondary @example.net@example.net as alias with them, your expensive provider charges $$$ to do that.

Here, you can add Cloudflare Email Routing, to handle @example.net@example.net, and then pass it's messages over to your already existing john.doe@example.comjohn.doe@example.com, at no extra cost.

WWuppie Think this could be quite easily detected during the Cloudflare setup - might be...

DarkDeviL•11/8/23, 11:49 AM

I'd +1 on that one. With the custom address and destination being 100% identical, a warning could indeed be useful in the UI.

DarkDeviL•11/8/23, 11:49 AM

Regading e.g. the internal / server messages, it would depend on the set up there though.

DarkDeviL•11/8/23, 11:50 AM

Typically, and most simple, it would then be sending the messages as if it were records@internal.eaxmple.comrecords@internal.eaxmple.com.

WuppieOP•11/8/23, 11:50 AM

So it would need to be seperate domains, it cannot be simple the first part that is different?

DarkDeviL•11/8/23, 11:50 AM

But it would (depending on what runs as the backend) be possible to do advanced routing rules there too, that would replace it with e.g. records@example.comrecords@example.com.

WuppieOP•11/8/23, 11:51 AM

I cannot setup in plesk info2@domain.com
and use cloudflare for info@domain. com and forward it to info2?

WuppieOP•11/8/23, 11:51 AM

I am assuming that would still loop - but i am not yet seeing it

DarkDeviL•11/8/23, 11:51 AM

Nope, not if @domain.com@domain.com is the 100% same domain for both info@ and info@.

DarkDeviL•11/8/23, 11:52 AM

You have no ways of controlling (or guaranteeing) that the one goes to Cloudflare, and the other goes to your Plesk in that way.

WuppieOP•11/8/23, 11:52 AM

ah yes because that mailserver is DNS-configured

WuppieOP•11/8/23, 11:52 AM

I see I see..

WuppieOP•11/8/23, 11:53 AM

Think I am starting to understand- thanks so much DarkDevil

DarkDeviL•11/8/23, 11:54 AM

https://community.cloudflare.com/t/routing-mail-to-own-server-with-same-name/483830

https://community.cloudflare.com/t/want-to-use-both-godaddy-and-cloudflare-forwording-email-service/522316

https://community.cloudflare.com/t/cloudflare-email-routing-exchange-online-custom-domain/530695

DarkDeviL•11/8/23, 11:54 AM

Those threads (which I've been involved in

) explains something similar, especially the first goes in dept about the above "work around", with e.g. @internal.example.com@internal.example.com.

WuppieOP•11/8/23, 11:58 AM

I originally thought it would be a good idea- as using my internal mail server was exposing my IP address can throwing a warning in Cloudflre

WuppieOP•11/8/23, 11:58 AM

DarkDeviL•11/8/23, 11:58 AM

Is https://community.cloudflare.com/t/rejected-reason-unknown/577851, which seem very similar, a thread that you created?

DDarkDeviL Is <https://community.cloudflare.com/t/rejected-reason-unknown/577851>, which se...

WuppieOP•11/8/23, 11:58 AM

Nop thats not me..

WWuppie I originally thought it would be a good idea- as using my internal mail server w...

DarkDeviL•11/8/23, 12:00 PM

You would have to live with these non-Proxied warnings for any non-HTTP traffic, such as e.g. mail servers.

DarkDeviL•11/8/23, 12:02 PM

You can however take some security by obscurity way, and replace the "internal" part from the "@internal.example.com" example above could be some very long and random string.

DarkDeviL•11/8/23, 12:03 PM

A such approach would however (also) complicate your outbound stream from your Plesk, as it would somehow have to rewrite / remove it when sending messages out as well.

DarkDeviL•11/8/23, 12:03 PM

I wouldn't play around with such stuff myself, and just live with the warning.

WuppieOP•11/8/23, 12:57 PM

Thank you once more DarkDevil, really appreciate all your input

WWuppie Thank you once more DarkDevil, really appreciate all your input

DarkDeviL•11/8/23, 1:04 PM

You're welcome

DDarkDeviL Is <https://community.cloudflare.com/t/rejected-reason-unknown/577851>, which se...

DarkDeviL•11/8/23, 1:07 PM

@CFORED Seems like the mentioned thread is actually yours.

The above information / posts may therefore be useful to you.

Routing rules (all disabled now)

Similar Threads

Similar Threads

Similar Threads