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:] That's been kicked around before - it would seem to be a lot more efficient than resubmitting all the time, but the fact that it hasn't happened yet makes me wonder how much of a bear that option must be... If it's not that BAD, but just a low priority , maybe Sam could provide a few helpful hints to people who want to take that on - would there be an objection to including the feature if it were made? 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
