SendGrid mail parsing doesn’t show up but I think that is because they use their own domains, correc
SendGrid mail parsing doesn’t show up but I think that is because they use their own domains, correct?
UThe ones you have that start with numbers arent valid dkim keys as they dont have v=DKIM1;
!Is there any way i can get mails manually? I really need a mail but i am not getting it.
HWdym? Cloudflare doesn’t store your emails, so they are delivered as they arrive
Dyou can tell we're using sendgrid for inbound parsing, e.g.
dig sendgrid.ai.moda MXmx.sendgrid.net.I have
3600
SYou can pretty much send emails with cloudflare workers using mailchannels.
SThe Cloudflare Blog
MailChannels has created an email sending service specifically for Cloudflare Workers that removes all the friction associated with sending emails
▓Is it possible to send attachments as well?
MYes
▓ooh any guides on how to do this?
S?
JHi 
! Does anyone know how Email Workers
! Does anyone know how Email Workers message.setReject()
Osolved. Turns out i forgot to enable nodejs_compat, causing the worker to crash.
Tdoes mailchannel still works with cloudflare workers?
Tim getting 500 Internal Server Error
SYes it does, but you do need a Domain Lockdown record. https://community.cloudflare.com/t/introducing-mailchannels-domain-lockdown/523913
Cloudflare Community
TL;DR To lock your domain name down to a specific Workers account, create a TXT record on a subdomain called _mailchannels and set the value to v=mc1 cfid=yourworker.workers.dev. After this record is published, MailChannels will reject all email messages sent from your domain that do not originate from your Cloudflare Workers account. Bolsteri...
TThank you for showing me the way!
CAll emails that get sent to Workers, that don't error the worker out, show as Dropped, regardless if they are forwarded in the worker or not. They still reach the worker though
CTail (the worker) & debug
Chmm, should be delivery failed if it errored
CWhatever you see in tail is right though (and if wasn't obvious before, emails do show as events in tail). It might just be that the failures are too recent to show in the summary, it's delayed a bit
Cweird, it was "other" in the past iirc and "Delivery failed" for status. Eitherway, yea it's just an issue with your worker you have to fix, the mail is at least reaching it
Cignore that, that's most likely just a random bot visting your worker trying to call it over http
Cthe event body in tail should contain the details of an email, not an http request
Cbecause for that worker, it can't find a fetch() in your worker
Cemail workers need a email() handler, your worker has both? or
Cok that doesn't have a fetch() handler, so that makes sense why that error occured. New Workers get certitficates made for them, which show in CT Logs, which bots scan, so you get quite a bit of bot traffic trying to do http requests to your email worker which fail due to it not having a fetch() handler
Cthe error is unrelated to the fetch in your email handler
CMaybe it helps to explain, normal workers are structured like this:
Email Workers are not special, other then just having a fetch handler, they still get certificates and the default worker.dev endpoint for them, and thus refer to what I said above about bots/etc
Email Workers are not special, other then just having a fetch handler, they still get certificates and the default worker.dev endpoint for them, and thus refer to what I said above about bots/etc
Cyea makes sense, fun bots
Cstart tail and then send an email, and you should see an email event in your tail log, with the event body being an email rather then a request
