Dan Mosedale wrote: > This sounds like good stuff. I hope you'll stay tuned here, as I'm > hoping to post a straw-man filtering plugin interface in the > not-too-distant future, and it'd be good if it could accomodate the sort > of thing you're writing.
sounds grand. I'm hoping that when when you design filtering plug-in interface you can accommodate two quirks for me. The first one is based off of the fact that I'm handicapped. I nuked my hands by too many hours on the keyboard and now I'm dependent on speech recognition to 80 percent of my work. As a result, I only write code in Python because all the other languages are just too ugly to deal with when you start using speech recognition to speak the code. My wish is that you will make it relatively easy to either invoke Python directly from the filter plug-in architecture or, make it easy to use something like XML RPC as a way of calling "foreign" services. That way, you can write the plug-in interface in whatever language you want and I can handle the services in any way that makes my hands happy. The second is more directly related to the camram needs. On inbound mail, I need to get the message "before" anybody else. I need access to mailboxes so I can move messages into and out of jail. I need to be able to completely consume a message and have everyone else downstream not even know what it was there. I also need to be able to send a message from the filter. On the outbound side, it would be nice if I had the ability to queue up messages and generate stamps for each message in background and only sending the message after all stamps have been generated. Failing that, I'll need to hold up the user interface and give them some feedback while generating stamps. in any case Dan, I'm looking forward to your strawman proposal.
