Hallo. Am Samstag, 30. Dezember 2006 18:56 schrieb Sam Varshavchik: > See, it's a matter of efficiency. Rather than receiving a message, saving > its contents into a file, and then rereading the file again to parse the > message, the message is parsed on the fly, as it is being received and > saved into its file. Which means that the parsing part happens pretty much > before everything else happens.
Ok, I understand. So reformatting the MIME-part before filter invocation would cost some performance (because this doesn't need to be done if a filter revokes the message), right? And you want to pass the unmodified received message to the filter, too, I suppose. I would suggest two possible solutions and it would be cool if you state your opinion. It's just brainstorming, maybe it's nonsense. :) 1. The filter system could be extended to support additional filters that are called after reformatting and are r/w. 2. The filter system could be extended to support additional return codes for acceptance. E.g. code 201 would mean "re-parse the message, it has been modified", while 200 leaves the processing untouched as it is for now. cu, Bernd -- Der Vorteil der Klugheit besteht darin, daß man sich dumm stellen kann. Umgekehrt ist das wesentlich schwieriger. - Kurt Tucholsky
pgpIWd9jZZTGs.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
