TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Use a custom domain to send emails with Gmail using Cloudflare email routing

166 点作者 Gadiguibou超过 2 年前

13 条评论

ignoramous超过 2 年前
One can in fact send emails from Workers with their Cloudflare-registered domain name through MailChannels [0]. We use it to send <i>MagicLinks</i> [1]. And intend to impl DKIM signing, soon [2].<p>[0] <a href="https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;sending-email-from-workers-with-mailchannels&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;sending-email-from-workers-with-...</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;celzero&#x2F;otp&#x2F;blob&#x2F;f6bb5593c5173a284417863806ad6d5a57b19539&#x2F;src&#x2F;core&#x2F;magic.js#L105-L132" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;celzero&#x2F;otp&#x2F;blob&#x2F;f6bb5593c5173a2844178638...</a><p>[2] <a href="https:&#x2F;&#x2F;mailchannels.zendesk.com&#x2F;hc&#x2F;en-us&#x2F;articles&#x2F;7122849237389" rel="nofollow">https:&#x2F;&#x2F;mailchannels.zendesk.com&#x2F;hc&#x2F;en-us&#x2F;articles&#x2F;712284923...</a>
评论 #33668041 未加载
评论 #33675757 未加载
评论 #33666523 未加载
评论 #33668564 未加载
rdsubhas超过 2 年前
I&#x27;ve tried this. Most of my emails land in either &quot;Promotions&quot; or &quot;Updates&quot;, or worse – Spam.<p>If you really want your emails to be delivered to most recipients Inbox – I would not recommend this.<p>To validate – please go to <a href="https:&#x2F;&#x2F;www.mail-tester.com" rel="nofollow">https:&#x2F;&#x2F;www.mail-tester.com</a> – in 15 seconds it will evaluate and print your email score (you send it a dummy email). The main thing I see with using free gmail as a custom domain proxy SMTP is: It does not do DKIM (email signatures) except for @gmail.com or google workspace accounts. This reduces the sender score by a LOT.<p>Edit: The same is also true with forwardemail.net or any &quot;incoming&quot; email routing (free or paid). Because incoming email is just one step of using a custom domain. The main thing is the &quot;Outgoing&quot; email server. Unless outgoing email has full DKIM support for your custom domain, your emails are going to struggle reaching the recipient.
评论 #33679966 未加载
amatecha超过 2 年前
I went the opposite direction and am now paying for Proton and have set up my domains there. For me personally, a better approach than increasing my reliance on a second cloud service (Cloudflare) while continuing to benefit the original (Google) and experience its extreme degree of privacy invasion. This might not be the perfect solution, but for me it&#x27;s definitely a step in the right direction, even if I move onto something else later.<p>Further, considering I am regularly inexplicably blocked from accessing websites because they use Cloudflare &quot;protection&quot; (which doesn&#x27;t like OpenBSD + Firefox strict privacy setting), and considering their recent conduct, there&#x27;s zero way I&#x27;d ever consider using Cloudflare&#x27;s services regardless of potential usefulness. Not to mention giving up even more control of the internet to these &quot;superpowers&quot; seems like a terrible idea for everyone&#x27;s sake, IMO.
评论 #33666409 未加载
Arcuru超过 2 年前
All these articles really need to clearly layout the downside. You can&#x27;t send emails as the custom domain. At best, your emails will say &quot;sent by x@gmail.com on behalf of officialdomain.org&quot;
评论 #33666982 未加载
zfa超过 2 年前
Can someone with more knowledge on this subject explain if there&#x27;s a technical reason Cloudflare can&#x27;t &#x27;properly&#x27; MITM the inbound email.<p>That is you have your MX records pointing to `mx.example.com` in your example.com zone config, and enable the Cloudflare proxying of it (usual orange cloud in the UI).<p>Now, once it&#x27;s proxied, Cloudflare returns the IP of <i>their</i> mailserver instead of yours on public lookup, just as they do when returing the IP of a proxied webserver.<p>So this Cloudflare MX server gets your mail, and then as it knows your &#x27;real&#x27; MX server it connects to that server and delivers it to you, maybe adding some header or other on the way.<p>I don&#x27;t like the fact they use bog-standard forwarding as it necessitates messing with your SPF records, getting crazy forwarding headers and having to navigate ARC etc.<p>There just seems to be a cleverer way to do this than just do what everyone else does, and they&#x27;re generally ahead of the curve technically. Must be something I&#x27;m missing.
评论 #33668999 未加载
评论 #33672170 未加载
评论 #33668506 未加载
evolve2k超过 2 年前
I see the use case as being for all my side project domains.<p>After doing stuff like this for years, I’ve ended up going to Migadu, unlimited domains for under $100 year (cheapest plan is $19&#x2F;yr for almost unlimited domains)<p><a href="https:&#x2F;&#x2F;www.migadu.com" rel="nofollow">https:&#x2F;&#x2F;www.migadu.com</a><p>The Missing Email Service For Domains
doctoboggan超过 2 年前
I’ve tried various versions of this and have always had deliverability issues. Never tried with Cloudflare though.<p>Can anyone who has done this exact setup report on their experience with deliverability?
评论 #33665405 未加载
评论 #33667638 未加载
评论 #33668350 未加载
评论 #33668746 未加载
评论 #33667159 未加载
zeusly超过 2 年前
There&#x27;s also <a href="https:&#x2F;&#x2F;forwardemail.net" rel="nofollow">https:&#x2F;&#x2F;forwardemail.net</a> which I really love
评论 #33670410 未加载
RileyJames超过 2 年前
Interesting setup. I use <a href="https:&#x2F;&#x2F;forwardemail.net" rel="nofollow">https:&#x2F;&#x2F;forwardemail.net</a> for this use case. It’s certainly easier to setup, and it’s cheap ($18 for 6 months).<p>It means I have email setup for all my side&#x2F;small projects and spare domains, all forwarding to the few active inboxes I keep.
评论 #33675836 未加载
jacooper超过 2 年前
Or you can just use full email aliasing service, like Simplelogin.io which is included with Proton Unlimited.
sethd超过 2 年前
I love Cloudflare and really want to use this but I need the ability to route to multiple (2-3) destinations. :)
sideproject超过 2 年前
I do something similar with a tool I made &amp; use<p><a href="https:&#x2F;&#x2F;newsy.co" rel="nofollow">https:&#x2F;&#x2F;newsy.co</a><p>It works great. I don&#x27;t use Cloudflare email routing service but use something else. But I did a manual test with Cloudflare and it worked really well (thinking of changing it actually).
saagarjha超过 2 年前
This seems far more complicated than it had to be? My email (saagar@saagarjha.com) is backed by a personal Gmail account. When I receive mail my domain registrar has some aliases set up to catch it and forward it to my Gmail inbox. When I send mail it goes through an alias: <a href="https:&#x2F;&#x2F;support.google.com&#x2F;domains&#x2F;answer&#x2F;9437157" rel="nofollow">https:&#x2F;&#x2F;support.google.com&#x2F;domains&#x2F;answer&#x2F;9437157</a>. No need to set up a mailserver at all.
评论 #33666773 未加载