Emails from one domain rejected as spam

All emails from one specific domain are being rejected by Exchange 2016 server with the following error:
host said: 554 Spam email. Email Session ID: {XXXXXXXXXXXXXXXXXX} (in reply to end of DATA command)

I have added the domain to the safe senders list but the problem persists.

The rejected domain is not black listed on any list.
ivolachAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tim PhillipsWindows Systems AdministratorCommented:
Try this command: Set-ContentFilterConfig -BypassedSenderDomains [DomainToBeWhitelisted.com]

Example for multiples: Set-ContentFilterConfig -BypassedSenderDomains microsoft.com,woshub.com,gmail.com
Example for one e-mail address: Set-ContentFilterConfig -BypassedSenders safesender@gmail.com

I don't know if this is different than "safe senders" though.
ivolachAuthor Commented:
That is the command I have used to add them to safe senders list.
It now appears that all emails coming from gmail are getting the same "treatment"
Tim PhillipsWindows Systems AdministratorCommented:
oh, are you trying to whitelist @gmail.com?  That seems like a bad idea since there are lots of gmail spam accounts out there.
Run this to see what your whitelist already has: get-ContentFilterConfig
look for this section for e-mails: "BypassedSenders"
look for this section for domains: "BypassedSenderDomains"

This may shed light on what is going on.  First, what is in there?  The specific e-mail you care about or the whole domain or neither?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Dr. KlahnPrincipal Software EngineerCommented:
Agree with Tim.  Before whitelisting anything, you need to find out what the problem is.  Domains can change hands, computers can be infected, a rogue user may try to blacken the company's reputation.

Find out why the emails are being rejected and then address that, one, specific problem.
ivolachAuthor Commented:
I am not trying to whitelist gmail.
We have a partner hosting his domain email on google and I am trying to whitelist his domain xxxx.com
when I run the BypassedSenderdomain the only domain on that list is the xxx.com I have a problem with
Tim PhillipsWindows Systems AdministratorCommented:
in the reject e-mail does it confirm that Exchange is blocking it?  Like any reference to Microsoft Exchange?  I'm wondering if it is being blocked by a different spam filter (like maybe you are using a service and didn't realize it?  Like Mimecast, etc.)
ivolachAuthor Commented:
It seems to be a little convoluted:
The Checkpoint firewall was sort of blocking the messages as spam, but regardless the messages were transferred to the exchange server where they were shown on the log as 'socket error' but the reply to the sender was spam error 554.
Tim PhillipsWindows Systems AdministratorCommented:
hmmm, might want to either use Checkpoint to filter e-mail or Exchange.  This double spam filter thing is adding confusion.  Sounds like Checkpoint saw the e-mail and sorta "marked it" or "flagged it" and sent it on over to Exchange?  Then whatever Checkpoint did to it made Exchange send back the 554 e-mail to the sender?  

"socket error" makes it sound like Exchange never got the e-mail though.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ivolachAuthor Commented:
I agree, and have disabled the firewall spam filter.
The confusing part is that the "socket error" showed up on the exchange log.
Tim PhillipsWindows Systems AdministratorCommented:
So was there anything else you needed?
ivolachAuthor Commented:
After disabling the Checkpoint firewall spam filter, Everything is working now.

Not quite sure why would Checkpoint block all emails from the particular domain but, all is good now. :-)
Thanks,
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.