hey, i'm not that good with all these settings. i can send emails using thunderbird but i cant recei

hey, i'm not that good with all these settings. i can send emails using thunderbird but i cant receive any. if i try to send a mail it says the mail cannot be found or cannot receive emails at the moment. i dont know how to fix this, please help

SSelfieh hey, i'm not that good with all these settings. i can send emails using thunderb...

Hello, I’m Allie!•11/13/23, 8:20 AM

Email Routing doesn't allow you to send Emails(via SMTP), only receive them, if that is what you mean.

SelfiehOP•11/13/23, 8:20 AM

yeah, sending is not a problem at all. i just cant receive them.

SSelfieh yeah, sending is not a problem at all. i just cant receive them.

Hello, I’m Allie!•11/13/23, 8:21 AM

Just to make sure, are you logged in to your third-party email provider?

SelfiehOP•11/13/23, 8:22 AM

yes i am.

SSelfieh yes i am.

Hello, I’m Allie!•11/13/23, 8:22 AM

Do the emails appear in your WebMail?

SelfiehOP•11/13/23, 8:23 AM

i dont have webmail sadly. i have a domain that came with an email.

SelfiehOP•11/13/23, 8:24 AM

thats why i use thunderbird

SelfiehOP•11/13/23, 8:26 AM

i was receiving emails, but could not send them due to my DNS settings. i changed them and now i can send but cannot receive any.

Danny•11/13/23, 6:48 PM

Hi everyone! I'm trying to use the Brevo API to send an email when someone sends me one. I'm attempting to use their api, but when i do i get the error " Uncaught TypeError: superagent.agent is not a constructor"

Danny•11/13/23, 6:48 PM

I'll try just a normal fetch, but just reporting this here

Uuwinx why so strict? <:hmm:883740792382959626>

itsmatteomanf•11/14/23, 8:57 PM

Because those are the e-mail standard requirements...

Original message was deleted

Dubz•11/14/23, 10:28 PM

You mean catch-all? smart

CChaika hm the Settings Page says if the domain is disabled, subdomains won't work eithe...

Dubz•11/14/23, 10:30 PM

Yeah that doesn't make sense. Unless Cloudflare is explicitly stopping it, that shouldn't be a thing..?

Original message was deleted

kian•11/15/23, 3:16 PM

I would have thought a wildcard MX record would do that - I just doubt Cloudflare would let you set it up with Email Routing

kian•11/15/23, 3:16 PM

Wildcards are weird, and don't really work in the way most people expect them to.

Original message was deleted

Chaika•11/15/23, 3:16 PM

not too stupid lol, I do the same thing, but just use wildcard MX. Just have to be careful

Chaika•11/15/23, 3:17 PM

Yea rn it just doesn't let you create a wildcard subdomain

Original message was deleted

Chaika•11/15/23, 3:33 PM

Why?

Chaika•11/15/23, 3:33 PM

The way it is right now your catch-all affects all subdomains

Chaika•11/15/23, 3:33 PM

If they just let you add a wildcard subdomain, it would just work

Chaika•11/15/23, 3:33 PM

People in the past have hacked around that and manually created stuff and got it working, it's just not supported or recommended

Chaika•11/15/23, 3:35 PM

yea, just have to be a bit careful about that

Chaika•11/15/23, 3:35 PM

I use myname@companyname.mysite.com, which is almost always going to be fine/not conflict with anything

Chaika•11/15/23, 3:35 PM

well that's part of the DNS Specification

Chaika•11/15/23, 3:36 PM

it wouldn't break anything, your MX just wouldn't be served

Chaika•11/15/23, 3:36 PM

eeh I think it's something to keep in mind but not really of worry

Chaika•11/15/23, 3:37 PM

I use companyname as the subdomain for email like I said in my example, so I'd probably never hit anything

Chaika•11/15/23, 3:37 PM

You could also just buy an entire domain just to use for email

Chaika•11/15/23, 3:37 PM

and you often add subdomains that would conflict with the email subdomains you would use?

Chaika•11/15/23, 3:38 PM

I mean it really depends on how you are using them

Chaika•11/15/23, 3:39 PM

but yea, wildcards in general can be tricky

Chaika•11/15/23, 3:40 PM

depending on what you're doing, you might also get hit by the fact a subdomain existing stops the recursion entirely

Chaika•11/15/23, 3:40 PM

i.e

MX
cookies CNAME
free.cookies -> wouldn't have the MX, having the cookies label stops the wildcard from recursing any further

Chaika•11/15/23, 3:41 PM

Alternatively you could also use that to your advantage and do something like *.e.example.com MX*.e.example.com MX and then use subdomains of it to send mail to, unlikely you'd ever accidentally create a record and block it there

Original message was deleted

Chaika•11/15/23, 3:42 PM

lol yea I have a domain I have a wildcard http route for and just add exceptions for each subdomain I want to use

Chaika•11/15/23, 3:42 PM

a pain though

Uuwinx yep, bad example. I've used that as an expression – 😣 to get the "pattern" in t...

DarkDeviL•11/15/23, 3:45 PM

This somehow reminds me of once when I renewed a domain name, the money were charged and everything, ... but still, the domain went away, as if it had never been renewed...

The renewal didn't go through from the registrar to the registry, due to special characters in the one of the contact emails (registrant, admin, tech, billing), that made the registry see it as an invalid mail and refuse actions on the domain name.

The registrar then (initially) wanted me to pay a hefty restoration / redemption fee to "fix" it and return the domain to my account...

Original message was deleted

DarkDeviL•11/15/23, 3:55 PM

But easily solvable: For any records that you have, that already exist, simply create the corresponding MX records again:

Since

www.ryder.example. AAAA 100::

www.ryder.example. AAAA 100::

is not going to be inheriting the MX for www and below, you just add them "again" like this, to "fix" it:

www.ryder.example. MX mail.ryder.example.
*.www.ryder.example. MX mail.ryder.example.

www.ryder.example. MX mail.ryder.example.
*.www.ryder.example. MX mail.ryder.example.

Final result:

*.ryder.example. MX mail.ryder.example.
www.ryder.example. AAAA 100::
www.ryder.example. MX mail.ryder.example.
*.www.ryder.example. MX mail.ryder.example.

*.ryder.example. MX mail.ryder.example.
www.ryder.example. AAAA 100::
www.ryder.example. MX mail.ryder.example.
*.www.ryder.example. MX mail.ryder.example.

Original message was deleted

digeratidave•11/15/23, 6:47 PM

Ryder isnt a catch-all basically *@anthing.com? Thats what I am using it for.

Ddigeratidave Ryder isnt a catch-all basically *@anthing.com? Thats what I am using it for.

DarkDeviL•11/15/23, 7:01 PM

That's the most traditional way, yes.

DarkDeviL•11/15/23, 7:02 PM

You can however do *@*.example.com*@*.example.com, assuming your provider supports it.

Ddigeratidave Ryder isnt a catch-all basically *@anthing.com? Thats what I am using it for.

Chaika•11/15/23, 7:07 PM

he wants it to include all subdomains too (well, as much as a wildcard dns record can)

Dubz•11/16/23, 12:46 AM

My only question is, is this really necessary, or did you just mistakenly think it was a good idea years ago and are now dealing with the consequences? Lol

CChaika he wants it to include all subdomains too (well, as much as a wildcard dns recor...

digeratidave•11/16/23, 12:51 AM

looks like they even have a warning for it

Catch-all address
Enable the catch-all address to set an action for all other email addresses in user.com.
Catch-all rule only applies on the zone-level domain, you can’t create catch-all rule for each of your subdomain.

Hyps•11/20/23, 3:05 PM

Anyone familiar with a routing status stuck on Syncing.

My email routes have been functioning for well over a year. Suddenly one of my domains is stuck “syncing” for about 15 hours.

HJP•11/27/23, 1:09 AM

Hello, anyone has the issue with email-routing? The destination address has been verified and using normally but now suddenly we got error of "Error: destination address not verified""Error: destination address not verified"

hey, i'm not that good with all these settings. i can send emails using thunderbird but i cant recei

Similar Threads

Similar Threads

Similar Threads