Routing emails destination using the [email protected] email format
I am currently setting up a program to allow me to easily make new email routings and would like to have my destination emails use Gmails + tagging to help more easily discern which address the email was originally sent to. My issue is that Cloudflare is reading [email protected] as a different email from [email protected] and is trying to send a new verification email, which I can deal with, but I am not receiving that verification email and so I cannot verify it and so my email routing rule can not work until I find a way to resolve this issue.
My first question would be if anyone knows if what I am trying to do is even possible using Cloudflares system?
15 Replies
It sounds like you're talking about that you want the tagging on the final destination address?
So you're trying to verify the following final destination addresses:
1.
[email protected]
2. [email protected]
3. [email protected]
And here you're only the verification email on one of them, but not the other(s)?Yes, I am not receiving any verification emails for the others
Is there any pattern in it?
Did you successfully receive any verifications, when the address had the
+?Not as yet
To both questions
Wait sorry, I misread your examples, these would be more accurate of my situation
[email protected]
[email protected]
[email protected]
All my destinations use the same base but have different prefixes
in this case only for [email protected] do I receive a verification emailAh yeah, I was just testing the individual tags - as they at least used to work perfectly fine.
So I can confirm that individual tags are still working perfectly fine regarding the verification.
For this one, I would suspect that each broken account, e.g.
[email protected] (from [email protected]), and [email protected] (from [email protected]) may have ended up in a suppression list.
?login-helpThese links may help, but they only work when logged out. You can always use an Incognito Window or a Private Window to ensure you're logged out.
If you know the email: https://dash.cloudflare.com/forgot-password
If you know the email and have 2FA or email delivery issues: https://dash.cloudflare.com/login-help
If you don't know the email: https://dash.cloudflare.com/forgot-email
Follow link #2, regarding "email delivery issue", for
test@ and othertest@, and indicate that you have problems receiving emails on that email address.
(And ask them to check the suppression list)Awesome, I'll make sure to do that! I'll post here with my results. Thanks for the help!
It looks like the link you're referring to is only for login issues. I'm not sure it would be the right resource for this issue
It is the only direct way that there is, with an option of "
I cannot receive emails from Cloudflare to this address".
The verification emails for the Email Routing goes the same way out, as the account verification emails, - so if you're registering a Cloudflare account (or attempting to verify one), that has the test@ and/or othertest@ email address, it will be the exact same issue.
?supportTo contact Cloudflare Support about an issue, please visit the Support Portal and fill in the form on the portal. After submission, you will receive confirmation over email.
Some issues, such as Account or Billing related issues, cannot be solved by the community.
Any plan level (including Free plans) can open tickets for Account, Billing or Registrar ticket categories. Make sure to select the correct category to ensure it goes to the right place.
For more information on the methods by which you can contact Support for your plan level, see Contacting Cloudflare Support - Cloudflare Docs
If you prefer, you can also take the route of that, and create a ticket in the Account category.
Okay. I found the source of the issue and it was me being stupid
I thought the tagging went
[email protected] but it's actually supposed to be [email protected] so I just had it flipped
Thank you @DarkDeviL very much for you time and help. Sorry that I ended up wasting it with such a simple mistakeYou're welcome! And no worries, happy to hear that it got resolved in the end. 🙂