Sam Varshavchik wrote: > Gordon Messmer writes: > >> Sam, you've mentioned before that refactoring the code to run filters >> after rewriting the message would be difficult, but wouldn't you just >> need to move the "run_filter" block of code later in >> SubmitFile::MessageEnd? That would give filters access to the >> COMCTLFILE_MSGSOURCE line and other information written by >> SubmitFile::closectl, and also potentially allow filters to rewrite >> message bodies more easily. > > I have to think about this. I don't want to make such a drastic change > now, but after I cut the next release I'll make a note to make this > change, and see if it breaks anything.
Why not both? I.e. _add_ a block of code rather than _move_. We already have 'filters' and 'allfilters', so we could add more directories for read/write filters. That way, any filter using the new directories will know how it should install and behave. I'm not sure there is any advantage in keeping readonly filters when we'll have the new ones. If there is, we can live with many modes forever. If not, the old modes can be purged after a few releases, when any consequences are clear. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
