So for about 3 weeks my users have been complaining about higher levels of 
SPAM.  Just a few minutes ago I discovered the issue was an ID10-T problem on 
my part.  I was working on a new web service that sent out mail.  I was having 
problems with this so I went in to Smartermail and enabled the SMTP 
authentication bypass for a range of IP addresses.  So it turned out that I 
included the IP address of my upstream filter (Alligate) in the bypass range.  
For about 3 weeks Declude has been marking messages, and passing each message 
to SmarterMail, which then reset the SPAM weight to 0 on every message....  

The good news is that I have spent a significant amount of time updating and 
tuning Declude so I am expecting a significant reduction in end-user SPAM now.

Reply via email to