NOTE: emailed support as well.
We upgraded Exclaimer on 1/30/06. We have had problems with certain senders not getting messages through. Can't confirm that this started happening right after the upgrade because message tracking wasn't enabled. With Exchange message tracking enabled we have found that these messages trigger event-id 1026 (advanced queue failed to deliver message). Yesterday we had 888 of these events. Most of them were spam, but some were legit email.
We've confirmed that the problem is Exclaimer. We noticed that SOME of the messages not getting through w/ the Exchange 1026 (advanced queue failed to deliver message) event had a subject line of "tonight" so I used my external account to send a message w/ tonight in the subject and another with test. Test gets through, tonight does not and it has the 1026 Exchange event-id.
We tried changing the bottom rule for anti-spam, "detection center-spam," to mark, and had it mark with SPAM on the front of the subject. I also am archiving incoming messages to a mailbox. Once we did that we could see many SPAM... subject lines, but my tonight subject still did not get through. Doesn't even show up in the archive mailbox.
I turned anti-spam completely off and ALL of my messages from my outside account got through, even with tonight in the subject.
Therefore, something in the anti-spam rules above detection center - spam is stopping this because of the subject line(?). Note, some of the other subject lines getting blocked are: Re: news, inventory, mops and brooms, Re:email, Fw: Arthur, work, fyi, etc. Many different sender domains too. Doesn't make a lot of sense.