Sam Varshavchik [EMAIL PROTECTED] wrote: > No -- the problem that prevents this from working is that by that time > the message's MIME structure is already parsed. If, suddenly the > message's contents change, the pre-parsed offsets of various MIME > entities in the message will result in a corrupted message, should > Courier choose to rewrite it.
Can't Courier just determine whether the message file was modified, and if so, re-read and re-parse the message? That should avoid any performance problems for backward compatible behavior (i.e. for non-modifying filters). [Mitch says:] Another hack I played with a while back (which may still work on current versions was to edit a PREEXISTING header - thereby preserving the structure... that is sometimes enough for people - you make sure all messages are created with a header "X-My-Header: XXX" and then as needed you rewrite it to "X-My-Header: No_" or "X-My-Header: Yes" - note they are the same length, so it doesn't screw up the structure byte offsets... Just in case that helps... m/ ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
