3 ms·

I moved a Gsuite client to Zoho because once or twice a week, an email from one person at the custom domain to another person in the same custom domain (company

I moved a Gsuite client to Zoho because once or twice a week, an email from one person at the custom domain to another person in the same custom domain (company) would have their direct email get put into spam in Gmail. You would really think that Google would whitelist emails within the same custom domain which is paying for Gsuite service. Maybe that has changed, but it was definitely a problem 5 years ago. And we're not talking about an email which had some copy/paste of spam, we're talking about a one or two line sentence giving an instruction or asking a question to a colleague.

xjia 4y ago
https://support.google.com/a/answer/2368132 https://support.google.com/a/answer/2368132 > Bypass spam filters for internal senders Is this what you are looking for?
- thelittleone 4y ago
  Shocked that an article is required to explain what should be solved in the product.
  - sbuk 4y ago
    It is solved by the product. You tick a box, and internal mail is bypassed. The issue here is that developers and IT folk seem to think that email is easy because the know IT. Email is a complex, and old protocol that has many nuances and, believe it or not, phishers are smart; end users are naive, and often reckless. Spammers, be they benign or otherwise, can be incredibly lazy too, but don't think for one second that you, as a postmaster, are cleverer than they are. Spam and phishing are getting harder to beat. Businesses like Proofpoint, Cisco and Mimecast, along with the likes of Google and Microsoft, are investing heavily in trying to beat these guys, but the reality is that they are always at least two steps ahead.
    - thelittleone 4y ago
      Check box or not, my point is this should be default behaviour, I.e., don't mark same domain as spam, and instead make that an option to enable. Drives me nuts having to leave a UI to google (ironically) the issue to find a doc to enable a check box.
      - sbuk 4y ago
        At scale, that’s not an option. If you have external services that send mail to your Workspace tenant, there is a risk of compromise to the sending service, especially if it is outside of your control. The sending service could have SPF records that permit sending mail on your behalf. That mail needs to be scanned. There is also the threat from bad actors inside your perimeter. Sure if you’re a small operation, or using Workspace as a personal mail host, this may seem like overkill, but I can assure you that the majority of orgs that use Workspace (it a business too after all) would prefer the status quo.
- malshe 4y ago
  Don’t know about GP but this is what I was looking for. Thanks!
77pt77 4y ago
Google's own emails about expense reimbursements were systematically flagged as SPAM on gmail and they knew it. They still didn't care at all!

xjia 4y ago

https://support.google.com/a/answer/2368132 https://support.google.com/a/answer/2368132 > Bypass spam filters for internal senders Is this what you are looking for?

thelittleone 4y ago
Shocked that an article is required to explain what should be solved in the product.
- sbuk 4y ago
  It is solved by the product. You tick a box, and internal mail is bypassed. The issue here is that developers and IT folk seem to think that email is easy because the know IT. Email is a complex, and old protocol that has many nuances and, believe it or not, phishers are smart; end users are naive, and often reckless. Spammers, be they benign or otherwise, can be incredibly lazy too, but don't think for one second that you, as a postmaster, are cleverer than they are. Spam and phishing are getting harder to beat. Businesses like Proofpoint, Cisco and Mimecast, along with the likes of Google and Microsoft, are investing heavily in trying to beat these guys, but the reality is that they are always at least two steps ahead.
  - thelittleone 4y ago
    Check box or not, my point is this should be default behaviour, I.e., don't mark same domain as spam, and instead make that an option to enable. Drives me nuts having to leave a UI to google (ironically) the issue to find a doc to enable a check box.
    - sbuk 4y ago
      At scale, that’s not an option. If you have external services that send mail to your Workspace tenant, there is a risk of compromise to the sending service, especially if it is outside of your control. The sending service could have SPF records that permit sending mail on your behalf. That mail needs to be scanned. There is also the threat from bad actors inside your perimeter. Sure if you’re a small operation, or using Workspace as a personal mail host, this may seem like overkill, but I can assure you that the majority of orgs that use Workspace (it a business too after all) would prefer the status quo.
malshe 4y ago
Don’t know about GP but this is what I was looking for. Thanks!

77pt77 4y ago

Google's own emails about expense reimbursements were systematically flagged as SPAM on gmail and they knew it. They still didn't care at all!