> > I am really missing a filtertab something like "out.tab", > > trigged on outbound messages only. Davide, is there any thoughts > > about implementing a feature like this ? > > The filter architecture will be changed shortly.
Davide: Since you're rearchitecting the filter system, perhaps you'd give some thought to an added feature that Thomas and I have been discussing. Thomas' Scope filter was developed in an effort to reduce the number of times that XMail would have to marshal resources to launch a filter application from the commandline. By using a separate daemon to process requests, and calling that daemon via a socket, his Scope system shows some performance gains. I've recently written a C++ application similar to Thomas' except that it uses http to call an external server like a web server running ASP, PHP or a servlet process. The one drawback that I perceive is again, the fact that you have to marshall resources to initiate the mini http client, and pass it the parameters you want, etc. through an external process. It would be nice if in addition to the existing filter system of loading in directives for commandline initiated processes from a file, if there were a way to use a configuration file at startup of XMail to load a module that has the ability to open a socket to an external daemon, hand off a message for processing and wait for a response. A socket process that is based on vanilla TCP/IP and one that uses the http protocol are two modules that are worth considering. I'd be happy to send my existing http code to you for possible inclusion in the 1.12 corpus. Rob - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
