RE: [sniffer] Spam Messages held in the Bad Message Queue Mdaemon/Sniffer

[Bryan Busséy]

Usually I have found this to be due to a rule in the Content Filter.  One of the nice features about MDaemon logging is that every function has its own log.  If you check your Content-Filter log for the date/time of that message, it will tell you why it was rejected.  If it is not in the Content-Filter log, check the Spam-Blocker log next and then the All log as a last resort.   bb   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Jim Matuska Sent: Tuesday, August 23, 2005 4:30 PM To: sniffer@SortMonster.com Subject: [sniffer] Spam Messages held in the Bad Message Queue Mdaemon/Sniffer Since switching to Mdaemon/Sniffer from Imail/Declude/Sniffer I have been seeing quite a few message (right now about 500) stuck in the bad message queue.  Most of these messages have failed a good deal of spam tests, but not all the messages.  I'm not sure why exactly these are being held.  I am receiving postmaster messages that the user is unknown, but the account does exist and in most cases works fine (I have been unable to recreate this problem myself, but at any given time I see 500 messages going between the bad queue and the retry queue until they timeout and are sent to the postmaster account.    Has anyone ran into this?  Any thoughts?   Jim Matuska Jr. Computer Tech2, CCNA Nez Perce Tribe Information Systems [EMAIL PROTECTED]