This smells like someone's antispam is being a little aggressive.
The email headers will show that the email has come from user @ companyA, but will appear to come from the email server for companyB.
If companyC is looking at the header information and possibly scoring on the source server as well, then it may be scored too high.
I agree with Red, if Message Tracking shows that the message was delivered to companyC then the problem is with them - despite what they may say about not blocking the message. It hits their server and is delivered correctly, it is out of your hands.
Simon.
Main Topics
Browse All Topics





by: redseatechnologiesPosted on 2006-09-18 at 22:00:41ID: 17549229
Hi Exchange_Admin,
I am sure Sembee or someone else will jump in for you anyway, but I thought I would post with something I thought of while reading this.
If the message is actually arriving at companyb.com (as shown by message tracking) then surely the problem isnt yours, right? What does their message tracking show?
One thing that jumped out is that the message is actually going to be addressed to MYDOMAIN.COM, even when being forwarded to COMPANYB.COM - you know what I mean? the message will be addressed to yourdl@mydomain.com - which may be adding to the confusion at the other end.
What spam server do they have, have they ANY logs? Once again, if message tacking says it is gone, it should show up in a log somewhere at the other end
I suppose you could test this theory by creating a test user@mydomain.com, which is delivering a copy to admin@companyb.com - see if THAT goes through
-red