[{"data":1,"prerenderedAt":675},["ShallowReactive",2],{"\u002Fblog\u002Fcloudflare-email-forwarding":3,"\u002Fblog\u002Fcloudflare-email-forwarding-surround":665},{"id":4,"title":5,"authors":6,"badge":12,"body":14,"date":653,"description":654,"extension":655,"image":656,"meta":658,"navigation":659,"path":660,"seo":661,"stem":662,"updatedAt":663,"__hash__":664},"posts\u002Fblog\u002Fcloudflare-email-forwarding.md","Cloudflare Email Forwarding: Setup and Fixes When It Fails",[7],{"name":8,"to":9,"avatar":10},"Rares Serban","\u002Fabout",{"src":11},"\u002Fimages\u002Frares-serban.jpg",{"label":13},"Guide",{"type":15,"value":16,"toc":634},"minimark",[17,26,29,34,60,64,144,151,154,163,236,240,247,257,266,276,280,295,363,366,370,380,393,412,416,419,514,520,523,527,534,545,561,572,576,588,592,597,606,610,613,617,620,624,627,631],[18,19,20,21,25],"p",{},"Cloudflare email forwarding is free and takes a few minutes: onboard your domain, verify the inbox you want mail delivered to, and add a rule that sends an address like ",[22,23,24],"code",{},"hello@yourdomain.com"," there. Two conditions before you start. The domain has to use Cloudflare DNS, and forwarding only receives. Mail comes in to hello@, but nothing goes out as hello@. Answering as the address is a separate problem, and I get to it further down.",[18,27,28],{},"People land on this topic for one of two reasons: they want it set up, or they set it up, sent a test, and nothing arrived. This guide covers both, using the dashboard as it looks in October 2026 and the live records of a domain I forward through Cloudflare.",[30,31,33],"h2",{"id":32},"where-forwarding-lives-in-the-2026-dashboard","Where forwarding lives in the 2026 dashboard",[18,35,36,37,44,45,49,50,53,54,59],{},"Cloudflare now groups Email Routing, the forwarding feature, with Email Sending under one product called Email Service. Email Sending has been in public beta since April 16, 2026 (",[38,39,43],"a",{"href":40,"rel":41},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Fchangelog\u002Fproduct\u002Femail-service\u002F",[42],"nofollow","Email Service changelog","). So the dashboard path is now ",[46,47,48],"strong",{},"Compute > Email Service > Email Routing",", and the docs sit under ",[22,51,52],{},"developers.cloudflare.com\u002Femail-service\u002F",", starting with the ",[38,55,58],{"href":56,"rel":57},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Femail-service\u002Fget-started\u002Froute-emails\u002F",[42],"Route emails"," guide (last updated June 9, 2026). Tutorials written before the move may show menus and doc links that no longer match your screen. The steps below use the current ones.",[30,61,63],{"id":62},"how-to-set-up-forwarding-to-gmail-or-outlook","How to set up forwarding to Gmail or Outlook",[65,66,67,90,104,138],"ol",{},[68,69,70,73,74,77,78,81,82,85,86,89],"li",{},[46,71,72],{},"Onboard the domain."," Go to Compute > Email Service > Email Routing, select ",[46,75,76],{},"Onboard Domain"," and pick a domain from your account. Cloudflare adds three kinds of records to the root: MX records that send incoming mail to Cloudflare, an SPF TXT record (",[22,79,80],{},"v=spf1 include:_spf.mx.cloudflare.net ~all","), and a DKIM TXT record at ",[22,83,84],{},"cf2024-1._domainkey",". Select ",[46,87,88],{},"Done",". On Cloudflare DNS the change usually takes 5 to 15 minutes, though it can take up to 24 hours.",[68,91,92,95,96,99,100,103],{},[46,93,94],{},"Add the inbox you read as a destination."," Under ",[46,97,98],{},"Destination Addresses",", enter your Gmail or Outlook address and submit it. Cloudflare emails that address; open the message and select ",[46,101,102],{},"Verify email address",". Destination addresses belong to the account, so one verified Gmail can serve every domain in that Cloudflare account.",[68,105,106,109,110,113,114,117,118,121,122,125,126,129,130,133,134,137],{},[46,107,108],{},"Create the routing rule."," Select the domain, open the ",[46,111,112],{},"Routing Rules"," tab and select ",[46,115,116],{},"Create routing rule",". For ",[46,119,120],{},"Email pattern",", type the local part (",[22,123,124],{},"hello",") and pick the domain. Set ",[46,127,128],{},"Action"," to ",[46,131,132],{},"Send to an email",", choose your verified address as ",[46,135,136],{},"Destination",", and save.",[68,139,140,143],{},[46,141,142],{},"Test it from a different account."," More on why in the checklist below.",[18,145,146],{},[147,148],"img",{"alt":149,"src":150},"Cloudflare email forwarding Routing rules tab for beyondfolder.com: active custom-address rules with destinations redacted, catch-all set to Drop and disabled","\u002Fimages\u002Fcloudflare-email-forwarding-rules.png",[18,152,153],{},"On beyondfolder.com every custom address is an active rule, and the catch-all is left off with its action set to Drop.",[18,155,156,157,162],{},"A few details from Cloudflare's page on ",[38,158,161],{"href":159,"rel":160},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Femail-service\u002Fconfiguration\u002Femail-routing-addresses\u002F",[42],"routing rules and addresses"," (updated October 15, 2026) save a lot of guessing later:",[164,165,166,172,178,192,213],"ul",{},[68,167,168,171],{},[46,169,170],{},"A rule stays disabled until its destination is verified."," If you skipped the verification email, the rule exists but does nothing. Deleting a destination address also disables every rule that points to it.",[68,173,174,177],{},[46,175,176],{},"Duplicate patterns don't stack."," With two rules for the same address, only the one shown first in the dashboard list handles mail. One pattern, one rule.",[68,179,180,183,184,187,188,191],{},[46,181,182],{},"The catch-all rule catches typos."," It's optional, and off in the example above. Turn it on and mail to any address at the domain gets handled, so a customer who types ",[22,185,186],{},"ifno@"," instead of ",[22,189,190],{},"info@"," still reaches you. It also catches everything sent to addresses you never set up.",[68,193,194,197,198,201,202,205,206,208,209,212],{},[46,195,196],{},"Plus addressing is off by default."," Enable subaddressing under ",[46,199,200],{},"Settings"," and ",[22,203,204],{},"hello+news@yourdomain.com"," matches the ",[22,207,124],{}," rule. A rule written for the exact ",[22,210,211],{},"hello+news@"," address still takes precedence.",[68,214,215,218,219,222,223,201,226,229,230,235],{},[46,216,217],{},"Dots count."," Unlike Gmail, Cloudflare treats ",[22,220,221],{},"."," as a normal character in patterns, so ",[22,224,225],{},"jo.smith@",[22,227,228],{},"josmith@"," are two different addresses (",[38,231,234],{"href":232,"rel":233},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Femail-service\u002Freference\u002Fpostmaster\u002F",[42],"Postmaster",").",[30,237,239],{"id":238},"what-a-real-zone-looks-like","What a real zone looks like",[18,241,242,243,246],{},"My company domain, ",[22,244,245],{},"beyondfolder.com",", receives through Cloudflare forwarding. This is what DNS over HTTPS (Cloudflare's 1.1.1.1) returned on 2026-10-18, with the DMARC report address redacted and some unrelated site verification records left out:",[248,249,254],"pre",{"className":250,"code":252,"language":253},[251],"language-text","beyondfolder.com.          86400 IN NS emily.ns.cloudflare.com.\nbeyondfolder.com.          86400 IN NS lloyd.ns.cloudflare.com.\nbeyondfolder.com.          300 IN MX 3 route1.mx.cloudflare.net.\nbeyondfolder.com.          300 IN MX 72 route2.mx.cloudflare.net.\nbeyondfolder.com.          300 IN MX 93 route3.mx.cloudflare.net.\nbeyondfolder.com.          300 IN TXT \"v=spf1 include:_spf.mx.cloudflare.net include:zohomail.eu ~all\"\n_dmarc.beyondfolder.com.   300 IN TXT \"v=DMARC1; p=quarantine; rua=mailto:[redacted]@dmarc-reports.cloudflare.net\"\nupdates.beyondfolder.com.  300 IN MX 10 inbound.postmarkapp.com.\n","text",[22,255,252],{"__ignoreMap":256},"",[18,258,259,260,265],{},"The nameservers are Cloudflare's, which is the precondition for all of this. The apex has the three Cloudflare MX records and nothing else, so no old provider is competing for mail. The detail people get wrong is SPF: there is one record, holding Cloudflare's include and Zoho's side by side. Cloudflare's ",[38,261,264],{"href":262,"rel":263},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Femail-service\u002Fconfiguration\u002Fdomains\u002F",[42],"domain configuration"," doc says the same thing: merge existing SPF into a single record, make sure only one exists, and stay under SPF's limit of 10 DNS lookups. If merging pushes you over, drop includes you no longer need.",[18,267,268,269,272,273,275],{},"The DMARC policy is ",[22,270,271],{},"p=quarantine",", which tells receivers to treat unauthenticated mail claiming to be from ",[22,274,245],{}," as suspect. The last line is a subdomain with its own MX, which I come back to in the section on moving off forwarding.",[30,277,279],{"id":278},"the-limits-that-matter","The limits that matter",[18,281,282,283,288,289,294],{},"From Cloudflare's ",[38,284,287],{"href":285,"rel":286},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Femail-service\u002Fplatform\u002Flimits\u002F",[42],"Limits"," page (updated September 25, 2026) and the ",[38,290,293],{"href":291,"rel":292},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Fregistrar\u002Ffaq\u002F",[42],"Registrar FAQ",", as of October 2026:",[296,297,298,311],"table",{},[299,300,301],"thead",{},[302,303,304,308],"tr",{},[305,306,307],"th",{},"What",[305,309,310],{},"Limit",[312,313,314,323,331,339,347,355],"tbody",{},[302,315,316,320],{},[317,318,319],"td",{},"Routing rules per domain",[317,321,322],{},"200",[302,324,325,328],{},[317,326,327],{},"Destination addresses per account",[317,329,330],{},"200, shared across every domain in the account",[302,332,333,336],{},[317,334,335],{},"Destinations per rule",[317,337,338],{},"1 (more needs a Worker that forwards once per destination)",[302,340,341,344],{},[317,342,343],{},"Inbound message size",[317,345,346],{},"25 MiB; larger messages are rejected",[302,348,349,352],{},[317,350,351],{},"DNS",[317,353,354],{},"The domain must use Cloudflare DNS",[302,356,357,360],{},[317,358,359],{},"Domains registered at Cloudflare Registrar",[317,361,362],{},"Always on Cloudflare nameservers",[18,364,365],{},"The last row is easy to miss. If you bought the domain through Cloudflare Registrar, you can't point it at other nameservers. You can delegate a subdomain to another provider, or transfer the domain to a different registrar, but the apex stays on Cloudflare DNS while it's registered there.",[30,367,369],{"id":368},"cloudflare-custom-email-domain-what-you-actually-get","Cloudflare custom email domain: what you actually get",[18,371,372,373,375,376,379],{},"A Cloudflare custom email address is an address that forwards, nothing more. There's no mailbox behind ",[22,374,24],{},": the mail lives in the Gmail or Outlook inbox it was forwarded to. There's no Sent folder for it. And you can't send from it. Cloudflare's ",[38,377,234],{"href":232,"rel":378},[42]," page says it plainly: when you reply to a forwarded message, the reply goes out from your destination address, like your personal Gmail, not from hello@.",[18,381,382,383,387,388,392],{},"Cloudflare does have a way to send as your domain now, but it's built for code. Email Sending has been in public beta since April 16, 2026, runs on the Workers paid plan, and as of October 2026 its changelog shows no general availability date. I went through how it works and what it leaves out in ",[38,384,386],{"href":385},"\u002Fblog\u002Fcloudflare-email-routing-send-email","the guide to sending email through Cloudflare",". If what you actually want is to read a message and answer it as hello@, that's a different problem, and ",[38,389,391],{"href":390},"\u002Fblog\u002Fcloudflare-email-routing-reply","replying as your domain when Cloudflare only forwards"," covers the options.",[18,394,395,396,401,402,406,407,411],{},"The classic workaround, Gmail's \"Send mail as\" with an outside SMTP server, has an end date. Google says Gmail will stop sending mail from third-party addresses in January 2027, and that new Send-as setups may be restricted during the Q3 to Q4 2026 transition (",[38,397,400],{"href":398,"rel":399},"https:\u002F\u002Fsupport.google.com\u002Fmail\u002Fanswer\u002F17101213",[42],"Google",", checked 2026-10-18). If you rely on it today, read ",[38,403,405],{"href":404},"\u002Fblog\u002Fgmail-send-as-alternative","what to use instead of Gmail Send As"," before it stops. None of this is Cloudflare-specific, by the way: every forwarding tool has the same shape, and ",[38,408,410],{"href":409},"\u002Fblog\u002Femail-forwarding-service","what an email forwarding service does and where it stops"," walks through the rest of the field.",[30,413,415],{"id":414},"cloudflare-email-forwarding-not-working-the-checklist","Cloudflare email forwarding not working: the checklist",[18,417,418],{},"Work down the list in order. The first item is the most common false alarm.",[65,420,421,441,447,463,473,483,502,508],{},[68,422,423,426,427,430,431,434,435,440],{},[46,424,425],{},"You tested from the inbox you forward to."," You set ",[22,428,429],{},"hello@"," to forward to your Gmail, then sent a test from that same Gmail. Cloudflare's ",[38,432,58],{"href":56,"rel":433},[42]," guide tells you to send from a different account, because some providers discard messages that appear to come from the account they're delivered to. ",[38,436,439],{"href":437,"rel":438},"https:\u002F\u002Fsupport.dnsimple.com\u002Farticles\u002Femail-forwarding-not-working-gmail\u002F",[42],"DNSimple"," describes Gmail doing exactly that, with no bounce, and the message doesn't show up anywhere, not even in Spam. Send the test from a second account before you change anything else.",[68,442,443,446],{},[46,444,445],{},"The destination isn't verified."," Open Destination Addresses. If your inbox shows as pending, the rule is disabled. Send the verification email again from that page and click the link.",[68,448,449,452,453,458,459,462],{},[46,450,451],{},"The sender has neither SPF nor DKIM."," Since July 3, 2025, Cloudflare rejects incoming mail that doesn't pass at least one of the two (",[38,454,457],{"href":455,"rel":456},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Fchangelog\u002Fpost\u002F2025-06-30-mail-authentication\u002F",[42],"changelog","). Mail that fails the sender's own DMARC policy is rejected too (",[38,460,234],{"href":232,"rel":461},[42],"). The fix is on the sender's side.",[68,464,465,468,469,472],{},[46,466,467],{},"The sender's IP is on a block list."," Cloudflare rejects mail from addresses on realtime block lists with an error like ",[22,470,471],{},"554 \u003CIP> found on one or more RBLs (abusixip)",". That error goes back to the sending server, not to you. MxToolbox will check an IP against the common lists.",[68,474,475,478,479,482],{},[46,476,477],{},"A strict DMARC sender lands in Spam, or doesn't arrive."," Forwarded mail reaches Gmail from Cloudflare's servers, not the sender's, so the sender's own SPF no longer matches, and DMARC needs SPF or DKIM to pass for the From domain. Cloudflare works around it in three ways: it rewrites the envelope sender with SRS so SPF passes at the destination (the From header stays untouched), it adds an ARC chain recording the original authentication results, and it adds two DKIM signatures, one for ",[22,480,481],{},"email.cloudflare.net"," and one for your domain. Cloudflare still lists restrictive DMARC policies as a known limitation that can make forwarded mail fail. If it's landing in Gmail Spam, mark it Not spam or create a filter for the sender, as DNSimple suggests.",[68,484,485,488,489,492,493,496,497,501],{},[46,486,487],{},"Two SPF records, or MX records from your old provider."," Look up your apex. More than one ",[22,490,491],{},"v=spf1"," record needs merging into one. Any MX that isn't ",[22,494,495],{},"*.mx.cloudflare.net"," is a leftover from your previous email provider, and Cloudflare's docs say plainly that Email Routing can't share a domain with external mail servers. Remove it. To check, paste the domain into the ",[38,498,500],{"href":499},"\u002Ftools\u002Fmx-record-checker","MX record checker",": it lists every MX host and flags a mix of providers, like Cloudflare next to Google Workspace.",[68,503,504,507],{},[46,505,506],{},"The message is over 25 MiB."," Anything larger is rejected before forwarding, so a big attachment test proves nothing about your rules.",[68,509,510,513],{},[46,511,512],{},"Where to look."," The Email Routing activity log for the domain is the first place to check after a test send. If the test isn't listed there, the problem sits before Cloudflare: DNS, MX, or the sending server. If it is listed, the message reached Cloudflare, so read its Result column. A message Cloudflare passed on shows as Forwarded, as in the screenshot below, so anything else in that column tells you where it stopped. One more thing to know: Email Routing doesn't forward non-delivery reports to the original sender, so a message can fail without anyone getting a bounce.",[18,515,516],{},[147,517],{"alt":518,"src":519},"Cloudflare email forwarding activity log for beyondfolder.com over the last 24 hours, every result Forwarded, subjects and senders redacted","\u002Fimages\u002Fcloudflare-email-forwarding-activity-log.png",[18,521,522],{},"On beyondfolder.com, every message in the last 24 hours shows Forwarded in the Result column.",[30,524,526],{"id":525},"moving-off-forwarding-without-losing-mail","Moving off forwarding without losing mail",[18,528,529,530,533],{},"At some point you may want the domain's mail to go somewhere other than a forward. Cloudflare's ",[38,531,264],{"href":262,"rel":532},[42]," doc has two rules that decide how that goes.",[18,535,536,537,540,541,544],{},"First, the MX, SPF and DKIM records Email Routing adds to the root are ",[46,538,539],{},"Locked",". You can't edit or delete them under DNS > Records until you unlock them in Email Routing's Settings. Second, disabling Email Routing deletes every record it added, ",[46,542,543],{},"including ones you unlocked and edited to point at another provider",". Cloudflare still treats an edited record as its own, so it goes too.",[18,546,547,548,553,554,556,557,560],{},"Cloudflare's order for a switch is: unlock the routing records, add the new provider's records alongside them, verify the new setup, then remove the old records or disable Email Routing. One thing the doc doesn't spell out is which MX wins while both sets exist. Sending servers try the lowest preference number first (",[38,549,552],{"href":550,"rel":551},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc5321.html#section-5.1",[42],"RFC 5321, section 5.1","). On ",[22,555,245],{},", Cloudflare's ",[22,558,559],{},"route1"," sits at 3, so a new provider's MX at 10 would get nothing until the Cloudflare MX records are gone. Check your own numbers rather than assuming the new one takes over. After you disable, query the zone again and recreate anything that vanished; a merged SPF record is the first one I'd check.",[18,562,563,564,567,568,221],{},"The other way out is to leave the apex on forwarding and put a subdomain on the new service. That's what the ",[22,565,566],{},"updates.beyondfolder.com"," line in the zone above is, and I wrote up how it works in ",[38,569,571],{"href":570},"\u002Fblog\u002Femail-on-subdomain","running email on a subdomain",[30,573,575],{"id":574},"where-mailyond-fits","Where Mailyond fits",[18,577,578,579,583,584,221],{},"If you receive at a couple of addresses and you're happy reading them in Gmail, Cloudflare's forwarding is free and does that job well. Keep it. Look at the checklist above again, though: forwarding is a relay with two hops, from the sender to Cloudflare and from Cloudflare to Gmail, and each hop has its own reasons to reject a message or hide it. When you connect a domain to Mailyond, its MX points at the inbox itself. Postmark receives the mail and delivers it into Mailyond, so there's no second hop to rewrite the sender or fail a strict DMARC policy. Mail that arrives lands in your Inbox or your Spam folder, where you can see it and move it back, instead of being blocked before you know it existed. Replies go out as the address that received the mail, hello@ included, signed with your domain's DKIM key. Each domain takes one 5-minute DNS setup with 3 records, and a subdomain works the same way if the apex should stay on Cloudflare. As of October 2026, ",[38,580,582],{"href":581},"\u002F#pricing","Basic"," is $10 a month for up to 5 domains and Agency is $40 a month for up to 30, and Basic comes with a 7-day free trial. ",[38,585,587],{"href":586},"\u002Fsignup","Connect your first domain",[30,589,591],{"id":590},"faq","FAQ",[593,594,596],"h3",{"id":595},"is-cloudflare-email-forwarding-free","Is Cloudflare email forwarding free?",[18,598,599,600,605],{},"Yes. Email Routing is available on the Workers Free plan with unlimited inbound mail, according to Cloudflare's ",[38,601,604],{"href":602,"rel":603},"https:\u002F\u002Fdevelopers.cloudflare.com\u002Femail-service\u002Fplatform\u002Fpricing\u002F",[42],"Email Service pricing"," page (updated June 9, 2026). What needs the Workers Paid plan is sending to arbitrary recipients through Email Sending.",[593,607,609],{"id":608},"can-i-use-it-without-moving-my-dns-to-cloudflare","Can I use it without moving my DNS to Cloudflare?",[18,611,612],{},"No. Cloudflare requires the domain to use Cloudflare DNS. If you can't move the whole domain, you can't use it for the apex.",[593,614,616],{"id":615},"can-i-reply-or-send-from-a-forwarded-address","Can I reply or send from a forwarded address?",[18,618,619],{},"Not through forwarding. Replies to forwarded mail go out from your destination inbox, not from the custom address. You need a separate service that sends as your domain, and Gmail's Send-as option for third-party addresses ends in January 2027.",[593,621,623],{"id":622},"how-many-addresses-can-i-forward","How many addresses can I forward?",[18,625,626],{},"Up to 200 routing rules per domain, and you can turn on the catch-all rule for addresses you haven't set up. Each rule forwards to one verified destination, and an account can hold up to 200 destination addresses, shared across all its domains.",[593,628,630],{"id":629},"why-does-my-test-email-never-arrive","Why does my test email never arrive?",[18,632,633],{},"Most often because it was sent from the same inbox it forwards to, which Gmail may discard silently. Send from a different account, then check that the destination is verified and look in the Email Routing activity log for the test.",{"title":256,"searchDepth":635,"depth":635,"links":636},2,[637,638,639,640,641,642,643,644,645],{"id":32,"depth":635,"text":33},{"id":62,"depth":635,"text":63},{"id":238,"depth":635,"text":239},{"id":278,"depth":635,"text":279},{"id":368,"depth":635,"text":369},{"id":414,"depth":635,"text":415},{"id":525,"depth":635,"text":526},{"id":574,"depth":635,"text":575},{"id":590,"depth":635,"text":591,"children":646},[647,649,650,651,652],{"id":595,"depth":648,"text":596},3,{"id":608,"depth":648,"text":609},{"id":615,"depth":648,"text":616},{"id":622,"depth":648,"text":623},{"id":629,"depth":648,"text":630},"2026-10-18","Set up Cloudflare email forwarding to Gmail or Outlook in the 2026 dashboard, the limits that matter, and why a forwarded test email never shows up.","md",{"src":657},"https:\u002F\u002Fimages.pexels.com\u002Fphotos\u002F4065876\u002Fpexels-photo-4065876.jpeg?auto=compress&cs=tinysrgb&h=650&w=940",{},true,"\u002Fblog\u002Fcloudflare-email-forwarding",{"title":5,"description":654},"blog\u002Fcloudflare-email-forwarding",null,"ZqXc_LkGdJ8QVGtnl1VOes5b0KveOfbN40btmo4c5UU",[666,671],{"title":667,"path":668,"stem":669,"description":670,"children":-1},"Business Email Cost Per Domain in 2026: $2 to $84 a Year","\u002Fblog\u002Fbusiness-email-cost-per-domain","blog\u002Fbusiness-email-cost-per-domain","Business email costs $2 to $84 per domain a year. Google Workspace, Microsoft 365 and Purelymail compared. The catch: replies and app sending cost extra.",{"title":672,"path":390,"stem":673,"description":674,"children":-1},"Cloudflare Email Routing Can't Reply: Here's the Fix","blog\u002Fcloudflare-email-routing-reply","Replying to email forwarded by Cloudflare Email Routing sends from your personal Gmail. Why Send-As now fails DMARC, and how to reply from your domain.",1792519482859]