I am going to implement an app I have almost completed. The app will work like this.
1) Read the files in the hold folder for the previous day 2) Sort the email by recipient 3) Send the recipient an email containing the subject, from address, tests it was held on, and a http link to recover the email If the user clicks the link to recover the email they will be taken to an IIS app and the message will be moved back into the spool folder. It will also notify the postmaster account that an email was recovered supplying to the postmaster the full message source. I thing having the users decide weather or not to recover the email that has been held is more appropriate than my admins making that decision. Besides who has the time to go through every held message every day. There will be a config GUI and you can set the processor priority while it is going through the hold folder to Highest, AboveNormal, Normal, BelowNormal, Lowest. There is a GUI for configuring and a command line for scheduling. It also has a junk mail log summary feature that will parse through 1 or multiple log files. For example you could schedule it to run for the last 7 days and send you am email with the stats. You could create another config file and have it summarize the prior day and have that emailed to you. If any one is interested in testing the app please let me know off list and I will notify you when it is ready. It is written in C#. Kevin Bilbee [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Markus Gufler > Sent: Tuesday, July 01, 2003 4:45 AM > To: [EMAIL PROTECTED] > Subject: [Declude.JunkMail] enhanced HOLD action > > > Hi Scott, > > Would it be possible to enhance the hold action with the ability to move > the message file to another folder that /spool/spam ? > > I see more advantages with this function: > > 1.) We can move messages > 200% of our hold weight directly to our > /spool/spam/hold folder without the need to review them all. At the > moment we've some reasons to not delete the message on a certain weight. > We keep all hold messages for 14 days before a daily sched. task delete > the oldest files. > > 2.) If HOLD can also have a special switch (or maybe a new action > "KEEP") we can copy message-files that has 90-99% of our hold value. > This messages should be delivered but we can also review what happens > close below the hold value. For sure it's not a setting to keep all the > time but I mean this could by very usefull for fine tuning the own > configuration. > > 3.) Probably in future we can introduce a new range between "warn" and > "hold" that moves suspiciuos messages to the /spool/spam/wait folder. > Then we can call declude.exe with a special switch (-checkwait X) as a > scheduled task and declude "re-tests" files older then X minutes in the > hope that certain RBL-DBs has added the source in their lists. > > Maybe I suggest nothing new here... > > What about other suggestions: > -Andy's CONFIDENCE test > -In Declude Virus a FORGEDSENDER_INFOTEXT variable. > > Markus > > > > --- > [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
