|
@nehbit | |||||
|
Which will get all inbound email coming from Gmail inadvertently marked as spam. Because Gmail is sending you messages with IPs that don't match allowed IP ranges. The emails say "if not from these IP ranges, it's fake".
But they're not. Somebody didn't think this through.
|
||||||
|
||||||
|
Burak Nehbit
@nehbit
|
28. stu |
|
Today in unintended-consequences land: If you send an email from Gmail to a SMTP server hosted on Google Cloud Platform ... it will send over an internal, private IP, not from the public Gmail IPs.
So the SPF check will fail on those emails since SPF is a sender IP check.
1/2
|
||
|
|
||
|
Andrew Ayer
@__agwa
|
28. stu |
|
That's astonishing. What happens if your VPC subnet uses the same address range as Gmail?
|
||
|
|
||
|
Burak Nehbit
@nehbit
|
28. stu |
|
¯\_(ツ)_/¯
I’m not ruling out the possibility that I might be making a mistake, but this is a very simple setup, there is not much space to make a mistake.
|
||
|
|
||
|
Perry Lorier
@isomer
|
28. stu |
|
Huh. Interesting. I used to work on some of the ip lb infrastructure. Which IP(s) do you see as the source address here? I'll see if I can pass it along to the team responsible.
|
||
|
|
||
|
Осман Иванов
@OsmanKuzucu
|
28. stu |
|
sadly this isn’t new. this has been the case for the last year (at least that was when I first encountered this problem). In some cases the e-mails won’t even appear in the mailbox. It’s just sad that such huge company can’t fix such small problems
|
||
|
|
||
|
Benedict Lau ⛔
@LauBenedict
|
28. stu |
|
Wouldn't this happen like... all the time?
|
||
|
|
||
|
Meng Weng Wong
@mengwong
|
28. stu |
|
You’d think SPF libraries could add a failover range to rescue the private addresses. Bypasses should be hardcodable.
|
||
|
|
||