Forum

The source code is shipped with each extension. The extension, though it has a file suffix of .xpi, is just a zip file of the source. I haven't even bundled the source into .jar files internally! So just open the .xpi file with a zip reader, and the source is there. This is really the best sample of how to do custom filters as well (I wrote the backend code to support this, as well as the extension.)

I don't believe it would be very hard to add a custom filter action to send a particular email. I imagine that you could store a standard reply in, say, a .eml file, and the filter action would be to reply to the From: field of the message with the email selected in a file. Is that what you would like? The filter action would provide a field to select the email to use as the source of the reply.

The usual language used for Mozilla extensions is javascript, not java. But the language is the easy part. You really need to have a good understanding of basic Mozilla concepts like XUL and XPCOM, plus be able to navigate through the mail code base to see how to do things. There is a plan to add a more easily understood package called STEEL to the Thunderbird product to make it easier to write extensions, but that code has not been released yet even in the development versions. The code to do what you need is probably only about 10 lines of code beyond the generic code for a new custom filter action, but it will take awhile to figure out those 10 lines of code.

I'll do another release of FiltaQuilla about the time that TB beta2 is released (which should be in about 4 weeks). I'll try to add a few newly requested filter actions at that time, such as yours. No promises though, I'll spend a couple of hours on it and if I can do it in that amount of time, I will.

rkent