7 ms·

Is this a Gmail issue or a G Suite issue? You'd think they're similar but they haven't been in my experience. G Suite spam filtering has always sucked for me an

Is this a Gmail issue or a G Suite issue? You'd think they're similar but they haven't been in my experience. G Suite spam filtering has always sucked for me and others I know. I've gotten completely legitimate replies classified as spam from completely normal and legitimate people in the same domain as far back as 2013, if not earlier. In the case of someone else I know this happened to, it was an extremely critical email that got classified as spam. P.S. If any Gmail folks are here: There's a bug in Gmail/G Suite that might as well be equivalent to marking an email as spam, since it prevents you from seeing emails: last time I checked, the "Important" section of Priority Inbox seemed to sort based on the timestamp of the most recent important email in the conversation, not the most recent email in the conversation. So if a subsequent email comes that isn't Important, the conversation doesn't pop up to the top -- so if it's not on your screen already, you don't see it as unread.

shereadsthenews 8y ago
A lot of large enterprises using GSuite route their mail through external systems that provide various dubious services and which often screw up the spam classification by having dirty VIPs or being open spam relays etc. Perhaps your organization was infected by such a thing. Otherwise having a threaded message or a sender in your address book is a virtually guaranteed saving throw against spam classification.
- mehrdadn 8y ago
  You made me go back and check the email I had in mind. I'm not sure to be honest. What I do see is that it soft-failed SPF: > Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning {user@domain} does not designate {IP} as permitted sender) So I guess you can use that to blame the domain owner, but I feel like the fact that it was a reply to my own email should've been enough to allow it through? Moreover, there are other emails around that time that weren't replies but still softfailed SPF, and they were still let through.
  - shereadsthenews 8y ago
    Your domain needs to: include:_spf.google.com ... in order to send outbound mail from Gmail effectively. Many people don’t realize that Gmail sends mail to itself over SMTP, not some special magic protocol, and it doesn’t exempt itself from SPF checks and whatnot.
    - mehrdadn 8y ago
      They seem to have put up that SPF record now, so I can only presume they weren't aware of this at the time.

shereadsthenews 8y ago

A lot of large enterprises using GSuite route their mail through external systems that provide various dubious services and which often screw up the spam classification by having dirty VIPs or being open spam relays etc. Perhaps your organization was infected by such a thing. Otherwise having a threaded message or a sender in your address book is a virtually guaranteed saving throw against spam classification.

mehrdadn 8y ago
You made me go back and check the email I had in mind. I'm not sure to be honest. What I do see is that it soft-failed SPF: > Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning {user@domain} does not designate {IP} as permitted sender) So I guess you can use that to blame the domain owner, but I feel like the fact that it was a reply to my own email should've been enough to allow it through? Moreover, there are other emails around that time that weren't replies but still softfailed SPF, and they were still let through.
- shereadsthenews 8y ago
  Your domain needs to: include:_spf.google.com ... in order to send outbound mail from Gmail effectively. Many people don’t realize that Gmail sends mail to itself over SMTP, not some special magic protocol, and it doesn’t exempt itself from SPF checks and whatnot.
  - mehrdadn 8y ago
    They seem to have put up that SPF record now, so I can only presume they weren't aware of this at the time.