Delivery receipts rarely work with Exchange 2010 & ASSP Anti-Spam as a gateway

I hope someone can help me.

I have rolled out an install of ASSP. All is generally working quite well now, although it is a very comprehensive product, and has been a bit of a learning curve.

I have one significant issue which is causing me a headache still. When a user requests a delivery receipt, occasionally they get one, but most the time they don't. Read receipts don't seem to be a problem.

Unfortunately, delivery receipts seem to be extremely important to the various users at my firm, and I'm getting lots of complaints. I'm guessing that ASSP is dropping delivery receipts, although I'm not sure - excuse my ignornace but I've never had a full understanding of how delivery receipts are generated and processed, so would welcome some more insight.

Our configuration is as so:

Internet -> ASSP -> Exchange 2010 -> Email Client

Email Client -> Exchange 2010 -> ASSP -> Microsoft SMTP Service -> Internet

If any one can make suggestions, I'd be truly grateful. N.B. Read receipts seem to be working fine.

Many thanks in advance :D
Who is Participating?
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.

Just check the log files. Most anti spam programs will soft block NDR type of incoming emails and DR's are often used as a form of spam.

One of the rule sets (grey blocking or fix up) will be blocking them. Failing that, post your log files so we can see if we can pin point them.
bluemercuryAuthor Commented:
Hi hardwire.
Many thanks for your post. I thought the same thing, but unfortunately can't find anything within ASSP that relates to receipts, NDRs, etc. Additionally, I have the whole system in 'test mode' at the moment, so whilst it is learning to detect what is spam or not, it should be letting everything in through the door, including delivery receipts. It should also be sending me a copy of all detected spam, which it does to some extent (I am getting copies of most spam to the email account, but unfortunately not everything seems to be getting through; only about 95%).
I like the look of ASSP in terms of what I've read, but it is a pig to configure! Any further ideas or possible links you've stumbled across (or anyone else) would be hugely appreciated.
Thanks for taking the time to reply :)
bluemercuryAuthor Commented:
After spending two days going through all settings, I came to the conclusion that what I wanted to do simply wasn't possible.
I suddenly had a realisation as to how I could get around the problem though. My only reason for sending out via the Anti-Spam proxy is so that the Whitelist continues to be built up. I realised I could do this via a different method - a transport rule.
I created a second SMTP connector on the Exchange 2010 server to route all general email out on to the web (instead of to ASSP). This got back the ability to get delivery receipts.
With my other existing SMTP connector (which was using a bespoke port number, and directly send email back to the Anti-Spam proxy) I changed the domains it routed mail for to the localised domain 'assp.local' only.
I then created a tranport rule which blind carbon copied all email that left the firm to whitelist@assp.local (the address to register email addresses on to the white list with the ASSP system). I also turned off notifications to the recipients that these emails were bcc'd to ASSP, so that they didn't get a report back for every email they sent.
The end result is that it works a treat - our whitelist continues to build, senders get their delivery receipts, and recipients have no idea about the email that goes to ASSP to instruct it. It seems to me that this is as effective as using ASSP as the outbound SMTP proxy.
I thought I'd post all this incase someone has the same problem, and needs a solution! Transport rules were available from Exchange 2007 onwards, so I would imagine the same can be achieved with this release as well.
Hardwire; many thanks for your post - I don't think there was a direct solution as such, but turning this whole thing on its head this method seems to have worked pretty well. Many thanks for trying to make helpful pointers with the existing way I was trying to do it.

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
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

From novice to tech pro — start learning today.