13 ms·
Don't send to Gmail over IPv6
- willis936 4y ago(2020) There is a comment saying it's still true in March 2022.
- ldiracdelta 4y agoPhew!! Glad he isn't lying with that title.
- telmich 4y agoThe article has nothing to do with IPv6.
- bri3d 4y agoThe whole point of the article is that Google's sender identity scoring system is more strict when the sending IP is an IPv6 one. That's a pretty clear cut link to IPv6, no?
- bragr 4y agoGoogle is really strict in general about these kinds of things. I had to go a few rounds with my VPSes before emails from them would consistently not end up in spam, but looking at the headers I'm mostly using IPv6 so I don't draw the conclusion "don't use IPv6" just "if you have IPv6, which is more likely than not now, be careful and read the docs"
- telmich 4y agoLet me rephrase: the whole article is equally valid for IPv4. Being more or less strict is a claim the article makes without proof. And as far as my experience goes, there is no difference. So standing by it: the article has nothing to do with IPv6 per se.
- m348e912 4y agoHuh? I'm not even sure how you came to that conclusion. Gmail is probably tougher on mail servers using IP6 addresses because they're plentiful and I suspect spammers were having a field day setting up temporary mail relays forcing google to play whack-a-mole. I used to run my own email server years ago but spam and spam protection measures have made it time consuming and annoying. I'll leave it to the professionals.
- jeffbee 4y agoGmail has stricter requirements for v6 because they assume if you are using v6 then they can leave aside all the bozotic baggage they allow for legacy v4. In particular, your sending IP must have a PTR record and the name in that PTR record must have a AAAA record containing that address. This is mentioned in the 550 message, but I guess people don't read the logs.
- Filligree 4y ago> Gmail has stricter requirements for v6 because they assume if you are using v6 then they can leave aside all the bozotic baggage they allow for legacy v4. In particular, your sending IP must have a PTR record and the name in that PTR record must have a AAAA record containing that address. This is, in fact, quite difficult to convince your ISP they should do.
- jeffbee 4y agoRound-trip DNS consistency is pretty basic and my ISP provides it by default. Note that I didn't say your ISP has to delegate to you, or that your PTR record needs to match your EHLO or anything of that nature.
- vajrabum 4y agoAre IPv6 numbers not available from your local registry at low or no cost? Or in these late days must you rent them? Or is this just a problem of people not wanting or knowing how to run BGP so they can control their own fate?
- buro9 4y agoThis isn't specific to Google, but IP reputation was used heavily for IPv4... but there either isn't enough reputation for IPv6 or the systems haven't yet scaled to make sense of it (what works for the IPv4 address space doesn't necessarily work for the IPv6 address space, i.e. storing and looking up reputation and the slow changes in IPv4 ownership and the rapid burn-through of IPv6 ownership). What people on IPv6 are getting is one of two things: 1) Harsher defaults or 2) No reputation system applied. In the case of Google for email, it appears that it's harsher defaults.
- onphonenow 4y agoMy guess is that the defaults are designed to block a similar amount of spam if possible? Most major mail providers have access to one or more ipv4 addresses. This allows for reputation + it's a bit more wasteful to burn through ipv4 blocks on spam campaigns. ipv6 address are plentiful, so you can burn through them on a spam campaign.
- nybble41 4y agoIPv6 addresses are more plentiful. However, you don't assign reputation to an individual IPv6 address but rather to an IPv6 network prefix (a /64, or even /60). That gives roughly the same granularity as a single public IPv4 address: one ISP subscriber.
- onphonenow 4y agoFalse, the cost of a prefix is MUCH MUCH lower if you are looking to spam via ipv6. Total prefixes are 18,446,744,073,709,551,615
- nybble41 4y agoNaturally there are far more IPv6 /60s than IPv4 /32s. As a spammer, though, you don't get to pick just any /60 prefix you want—it has to be allocated to you.
- tenebrisalietum 4y agoSo what if we just change email to work like this: Mail server will not let incoming messages through unless you've first A) sent a message to that domain AND B) received a reply that doesn't look like an error or bounce. Yes, you'll have to send an email somewhere with little to no content to initiate reception of things like invoices, password resets, and monitoring emails. Is that such a bad thing? Yes, spammers will desperately try to get you to send an email, any email, to their domain, or cybersquat on common typos. These problems might have easier and better solutions than letting tech giants takeover a formerly open Internet protocol that anyone should have the ability to use.
- mgoetzke 4y agoHow would the first mail come through ?
- zerocrates 4y agoThey're saying you, the would-be recipient of later messages, would have to initiate by sending a message.
- Closi 4y agoYeah, but then the other persons mailbox will reject you because they haven’t messaged you yet.
- bombcar 4y agoYeah, if every single mail server worked that way, you couldn't ever get off the ground.
- Closi 4y agoWell I guess you could base it on some sort of reputation system…
- W0lf 4y agoThat sounds a lot like the idea from Peter Huth’s Mail-Terror-Blocker PRO, a theater drama studied guy that happened to become an _internet expert_ by accident here in Germany back in the 2000s. Unfortunately, his program failed in the most hilarious ways and quickly became a joke in the usenet groups back in the day.
- bhauer 4y agoThe annoying thing about the major email services (Gmail, Outlook, et al) using reputation as a key input in their spam prevention algorithms is that they don't handle reputation in a way sympathetic to small and hobbyist mail server operators at all. Google and Microsoft have the computation and data storage resources to forever record how much spam they've received from the mail servers operated by any given small company or hobbyist. If a domain's authoritative mail servers have a history of never sending spam, when that company or hobbyist (for any reason) has to switch hosting providers and gets a new IP address, Google/Microsoft should recognize that the domain, and its referenced mail servers, has never been malicious. But instead, the majors treat a new IP address for a long-established domain as entirely new to the internet and assign it zero, or even negative, reputation. And they don't care to address this because, well, why care about hobbyists and the rare small company insolent enough to try to self-host email?
- hamburglar 4y agoIndeed, although I think there is a little more rationale than simply not caring. The hobbyist/small mail server is historically more likely to go unpatched and pwnage is more likely to go unnoticed, so it’s unfortunately a good defensive move to penalize them reputationally by default. PS yahoo is the worst for assuming poor reputation from a sender. In my experience they just introduce massive delivery delays at the drop of a hat even when the sender has a stellar reputation.
- bhauer 4y ago> The hobbyist/small mail server is historically more likely to go unpatched and pwnage is more likely to go unnoticed, so it’s unfortunately a good defensive move to penalize them reputationally by default. But to reiterate my earlier point: Google and Microsoft have the computational and storage capacity to have a detailed history of all domains' authoritative mail servers behavior. They will know whether a domain has a history of patch negligence. No, I think the far simpler explanation is that they just don't bother tracking reputation by domain. Or if they do, it's largely overshadowed by the weight given to IP-based reputation.
- CodeWriter23 4y ago1-5 mandatory for standing up a mail server on IPv4 ijs
- alaricus 4y agoDon't use Gmail. Here are some better alternatives: https://proton.me/ https://proton.me/ https://tutanota.com/ https://tutanota.com/
- rflrob 4y agoIt’s one thing to advocate not using Gmail for your own mail, and another entirely to advocate not sending any mail to gmail accounts from your own mail server, which is what TFA is really covering.
- robjan 4y agoI get deliverability issues when sending from Protonmail
- Vladimof 4y agoCan you search your mail on tutanota yet? Also I wish they would have chose a different name...
- nimbius 4y agoSPF dkim and dmarc aren't exclusive to ipv6. I think what the author is bemoaning is just how exhaustive the requirements are to send to one of googles cloistered mailservers in the first place. check senderbase and the rbls, you might be there too if you're on a less gilded cloud provider like oracle or ibm. in general new mailservers take some TLC to repair the IP space you're given before providers will trust it.
- upofadown 4y agoI don't know why everyone lets Gmail off the hook like this. Let's face it, Gmail is broken and has been for some time. It is time to move on.
- Avamander 4y agoPeople have said that for a decade now. Any specific reasons why you're saying this?
- gorgoiler 4y agoOne in N of their IPv6 relays is also way more fussy than the others. What’s even better for causing frustrating debugging sessions than nebulous spam fighting rules? Intermittently implemented rules. Google’s borglike embrace of email is a sad thing for The Internet that slipped quietly by before it was too late.
- andix 4y agoIt’s totally understandable why a lot of mail providers require correct DNS, rDNS, SPF and DKIM. This is standard in 2022. And DMARC is also not hard to implement, it’s just a DNS record.
- zippergz 4y agoDNS is not the hard part of DMARC. It’s identifying ALL of the legitimate sources of mail from your domain, and keeping up as they change. Easy enough for a hobbyist, but often challenging for even small business.
- andix 4y agoJust relay all the mails via your main mailserver and you’re done.
- djbusby 4y agoI've got two. One primary, corp email system (out/in) and then a second forward-hub for systems to send mails through. This way one doesn't accidentally bang up the other
- throw0101a 4y ago> DNS is not the hard part of DMARC. It’s identifying ALL of the legitimate sources of mail from your domain, and keeping up as they change. The e-mails from your domain should only come from IT-run systems/services. If other departments want to sent e-mail setup a sub-domain or a get a secondary/marketing/communications domain(s).
- deleted 4y ago[deleted]
- hdjjhhvvhga 4y agoI remember that was the first thing I used to do on my mail servers, ever before DKIM etc. Why? I have no idea and I will never know. Is sending email via IPv6 important to me? No. Is mail delivery important to me? Yes. Why is Google such a bad player in this field? Because in spite of having the biggest email network they don't want to allocate relevant resources to handle spammers properly. In other words, they are OK with false negatives, that is us. For this reason, I'm fine with this ugly workaround.
- timcavel 4y ago
- pcdoodle 4y agoGmail is not Email We were lucky enough to have a product idea that sold out immediately after some coverage on a few tech sites (A tiny hardware product for nerds). Trying to update our customers, we sent out an email to about 500 people via Shopify, the spot the little guys use to do eCommerce. No links in the email at all, just a text based update that we’re here and working hard to keep up with demand. Ever since then, every email we send to a gmail user (including friends and family) get’s bounced. It’s not even in their spam box! We have since added google dns txt records and via something they call postmaster tools and we still can’t get emails out. Just text, no links, no phone number, just a product update from a small company. Gmail is not Email anymore.
- Avamander 4y agoThere is not a single provider out there that won't punish you for sending bulk email out of the blue. It's unfortunate you found out like that, but you should try a new domain and let the old one cool down.
- jeffbee 4y agoGmail does not ever "bounce" mail for spam reasons. It either temp-fails the SMTP conversation with a 4xx error code, or it delivers it, to the Inbox or to Spam as indicated. If Shopify is transforming a temp-fail into a non-delivery receipt, that's their problem, and yours, but nothing to do with Google.
- ale42 4y agoHave a small mail server, pretty low-volume (max bursts are 40-50 messages to Gmail, global volume to it is around 100 messages per week), delivering to gmail over IPv6. (Note: DMARC, DomainKeys and SPF all implemented) Mails are delivered reliably and have zero problems with it. Had man more issues with Yahoo, Hotmail and Apple, all of which only accept mail over IPv4.
- istillwritecode 4y agooutlook.com is even worse. If you bring up a mail server, you have to apply to them for permission to send them email. Doesn't matter that you have DKIM, SPF, DMARC, or that the domain is 25 years old. They don't care - you must apply through a process that ironically sends email that isn't DKIM certified in their response.
- slim 4y agoI would be grateful if you explained the proces. Would you? I have trouble with sending emails to outlook.com
- kazinator 4y agoDon't send to Gmail over IPv6. .... Unless you're a kooky spammer re-sending a captured YouTube terms-of-service-change e-mail to the inbox of some Gmail user who bears no relation to the original recipient of that e-mail. Then, hey, you have no issues with delivery. https://news.ycombinator.com/item?id=31577087 https://news.ycombinator.com/item?id=31577087
- rascul 4y agoAre there any VPS providers who try and help with mail delivery? Perhaps by actively watching for and shutting down spammers, or investigating and taking action when one of their IP addresses show up on a blocklist? Or something else?
- Uptrenda 4y agoThere should be an amendment to the email protocol that routes emails to inboxes if they were paid for by some user-configurable amount. Cryptocurrency would be ideal for this unironically because its basically an open protocol (yeah I know the hacker news crowd hates cryptocurrency but whatever.)
- lathiat 4y agoYep, we've firewalled off the gmail IPv6 mail servers for quite a long time at a small but very long running Web/Mail host (since 2007).