Re: [ SOLVED ] Re: A bit off-topic: problems with sending to a Gmail user
On 2022-10-19 07:43, Cameron Simpson wrote: > On 17Oct2022 21:19, Tim Chase wrote: > >I found that I had to both set my SPF for the sending-server (in > >my case, my VPS is the sender, rather than outsourcing to a smart-host > >elsewhere), > > I tried that for us, but some places reject email from our cloud server, > which is an AWS VM. So the home server runs outbound mail for some/all > things through the ISP smart host. Some IP ranges (particularly cloud-service instances which spin up & down and may have different hosts appearing at the same IP addres) also have trouble. For mine, I had the instance running (on the same IP) for a year or two before I decided to move my mail functionality there, so I knew it didn't have a history of recently spamming other hosts. Similarly, home ISP ranges are also often rejected because the rDNS resolves to something auto-generated rather than the actual domain-name. Just in case you're looking for other tilt-bits that might be used when rejecting messages. -tkc
Re: [ SOLVED ] Re: A bit off-topic: problems with sending to a Gmail user
On 17Oct2022 21:19, Tim Chase wrote: I found that I had to both set my SPF for the sending-server (in my case, my VPS is the sender, rather than outsourcing to a smart-host elsewhere), I tried that for us, but some places reject email from our cloud server, which is an AWS VM. So the home server runs outbound mail for some/all things through the ISP smart host. And, regrettably, our phones kind of inherently use their telco/ISP smart host. (Hmm, maybe wireguard would let us securely use the AWS host as a smart host). Cheers, Cameron Simpson
Re: [ SOLVED ] Re: A bit off-topic: problems with sending to a Gmail user
On 2022-10-18 08:07, Cameron Simpson wrote: > On 17Oct2022 09:48, Matthias Apitz wrote: > >As more and more of my mails, also to friends could not reach them > >@google.com, I studied the DNS record for SPF a bit and came up with > >this single line in my DNS: > > > >@ TXT v=spf1 ip4:178.254.4.101 include:unixare.de -all > > I've just read up on this and have added an include for the ISP we often > send through. I'll be interested to see if delivery to gmail.com improves > for me - my own symptom is usually that they shunt my messages to spam/junk > instead of bouncing them, so this may well not help me. I found that I had to both set my SPF for the sending-server (in my case, my VPS is the sender, rather than outsourcing to a smart-host elsewhere), and I need to set up DKIM (putting my server's public key in DNS, and then signing outbound mail) to get the best results with Gmail. Otherwise, things kept ending up in Spam -- even when I was sending to my test Gmail account and the sender (me) was a known contact in the Gmail account, and back-and-forth replies had all the right in-reference-to headers set properly. I haven't yet messed with DANE, but SPF+DKIM seems to be enough to make Gmail less grumpy. Gmail is a bit fastidious, rejecting messages overzealously. But they're the 800lb gorilla in the game. -tkc
Re: [ SOLVED ] Re: A bit off-topic: problems with sending to a Gmail user
On 17Oct2022 09:48, Matthias Apitz wrote: El día sábado, marzo 12, 2022 a las 11:12:49a. m. +, Claus Assmann escribió: On Fri, Mar 11, 2022, Stefan Hagen wrote: > > > 550-5.7.26 This message does not have authentication > > > information or fails to > Authenticated in this context means, you don't have SPF / DKIM / DMARC set up. [,,,] As more and more of my mails, also to friends could not reach them @google.com, I studied the DNS record for SPF a bit and came up with this single line in my DNS: @ TXT v=spf1 ip4:178.254.4.101 include:unixare.de -all and all is fine now. Thank you! I've just read up on this and have added an include for the ISP we often send through. I'll be interested to see if delivery to gmail.com improves for me - my own symptom is usually that they shunt my messages to spam/junk instead of bouncing them, so this may well not help me. But I was unaware of "include" before now. Cheers, Cameron Simpson
[ SOLVED ] Re: A bit off-topic: problems with sending to a Gmail user
El día sábado, marzo 12, 2022 a las 11:12:49a. m. +, Claus Assmann escribió: > On Fri, Mar 11, 2022, Stefan Hagen wrote: > > > > > 550-5.7.26 This message does not have authentication information or > > > > fails to > > > Authenticated in this context means, you don't have SPF / DKIM / DMARC set > > up. > > [more off-topic/rant] > Isn't it nice how Google et.al. enforce things which are > neither mandatory nor really useful to "fight spam"? > All the spam I get at $WORK is from gmail and it has passed > all of those "requirements" -- but the "investment"/"loan"/... > spam/scams are not filtered at all by Google themselves > (hey, why should they do outbound spam filtering? it cost them money > and why should they care? it's not like anyone important would block > gmail -- but Google rejects mail coming to them due to bogus reasons). > > "Solution": ask gmail users to switch to other services which do > not have so many "false positives". > > PS: maybe there is an option in gmail for users to whitelist senders > from whom they want to receive mail? As more and more of my mails, also to friends could not reach them @google.com, I studied the DNS record for SPF a bit and came up with this single line in my DNS: @ TXT v=spf1 ip4:178.254.4.101 include:unixare.de -all and all is fine now. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub Schluß mit dem (Wirtschafts-) Krieg gegen Rußland! Schluß mit den Sanktionen! Druschba / Дружба mit Rußland statt NATO-Krieg gegen Rußland!
