RE: [Declude.JunkMail] Update- Declude NOT being seen

[Kevin Bilbee]

Title: Update- Declude NOT being seen

Or just use automation that does not require the SMTP process to be restarted.

 

We have seen emails with no Declue headers but verry rarly. We never stop and restart the SMTP unless there is a problem or update. As a matter of fact since 7.15 I have not restarted my SMTP unless there was an update to Imail.

 

We are working on an automation scheme that will use a database and stats from the log files to reorganize the filters and create a private DSNBL on our dns servers so we do not have to use the Imail Kill file and continually restart the Imail SMTP process. It is only on papaer at this time.

 

 

Kevin Bilbee

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Kami Razvan
Sent: Tuesday, December 23, 2003 4:50 AM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] Update- Declude NOT being seen

Hi;

With Scott's help I finally think the reason Declude is not being seen in our case, in rare occasions, is understood.

It just happened that we found a trend that matched exactly our update cycle for the filters.

In our system we have an auto-update of filters from our database to the IMail directory.  In the update process we copy all the filters to the filter directory and copy the Kill list to the IMail directory.  Then (here is the problem..) we stop the SMTP and then start the SMTP all in one batch file.

This is done every other hour at 1/2 past the hour.

All spams that were not having Declude headers were somehow showing a x:30 in their time stamp..

So..

It seems like if an email is being processed and during the SPAM processing by IMail one stops the SMTP then all bets are off and the email will be delivered.

Lesson learned: Too much automation could be hazardous to your spam fighting system. :)

Regards,
Kami