Bernd Wurst writes:
Hallo.Am Samstag, 30. Dezember 2006 17:51 schrieb Sam Varshavchik:> Is there any reason for this limitation? Yes, it's a technical limitation. In some situations, after filtering is complete Courier may decide to rewrite the message's MIME headers and MIME encoding. The message gets parsed internally before filters get invoked. If the filter changes the contents of the message, the starting and the ending positions of the individual MIME sections in the message will now be different, and the message will be corrupted.Thank you for the explaination.Is there a plan for removing this limitation? To me, it seems like it shouldn't be too hard, if courier would do it's mime-processing completely either before or after filter invocation but not reading before and rewriting afterwards. :)
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.
pgpZDC4TTWnSk.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
