--Sam Varshavchik wrote on 24.02.03 19:53 -0500: >>> I suppose I'll look at what needs to be changed to allow filter to >> safely >>> modify the message. That's a long term project, though. >> >> Hi, Sam. >> >> My amavis-ng perlfilter is having this same problem when adding headers. >> Has there been any progress on allowing filters to modify the spool file >> yet, or at least some API to have courier include header info? > > No. I am not working on this area at the moment.
I am currently inserting X-Spam: at the top of the message from the value of either BLOCK2 or the returned text of maildropfilter (the per-user api), another patch within courierdeliver will drop such marked messages into the Spam-folder, to be automatically purged after 30 days just like the Trash. this allows each user individually: a) configure the extend of filtering, select the set of dnsbl, and of course other nice things like Spamassassin and DCC. b) configure wether the message gets rejected at rcpt-to or delivered into the Spam-folder for inspection c) receive detailled daily logs about their rejected messages d) whitelist by sender, receipient and remote-host The first part was not that difficult and does not modify the spool, delivery into the Spam-folder has not been done yet. If someone wants to assist I'll setup a project at Sourceforge for that but some ideas of this might as well integrated into courier ;) Roland ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
