Supported Sieve Extensions....

Question

I have not been able to find a definitive list of supported Sieve filter extensions. In particular, I am looking for an extension that will let me replace or rewrite a particular header in the message (specifically, the subject line of the message). The RFC lists just the basic actions, and the admin guide mentions a few related to Spamassasin functionality, but from reading the forums it seems that at least "addheader" is supported.
Has anyone here had any experience using sieve filters to replace the subject line of a message? The "addtag" command will let me modify the subject line, but does not let me replace the subject in its entirety, which is what I need to do. I've found lots of proposed RFCs for sieve extensions, including "deleteheader" and "editheader" but the best answer I have found so far regarding messag server support for them is "we try to support what is in the RFC", which is somewhat vauge to me.
Is there a command I can run that will list all the supported sieve commands?
Thansk in advance for any help!
BTW - I am running this version of MS:
bash-3.00$ sudo /apps/msg_inst_dir/SUNWmsgsr/sbin/imsimta version
Sun Java(tm) System Messaging Server 6.2-7.05 (built Sep 5 2006)
libimta.so 6.2-7.05 (built 12:18:44, Sep 5 2006)
SunOS uslcsec05 5.10 Generic_118833-02 sun4u sparc SUNW,Sun-Fire-280R

Answer 1

Hi,
Thanks for the info, I'll look into the milter stuff
to see if that may give me a better fit in a future
revision. The milter plugin should prove to be very powerful. Recent updates to the pre-release 6.3 code (which I really hope make it into the release version) now provides support for basically all of the milter email actions including:
- Add headers (SMFIR_ADDHEADER)
- Change body chunks (SMFIR_REPLBODY)
- Add recipients (SMFIR_ADDRCPT)
- Remove recipients (SMFIR_DELRCPT)
- Change or delete headers (SMFIR_CHGHEADER)
- Quarantine message (SMFIR_QUARANTINE)
Writing a milter server (the MTA is the milter 'client') is pretty straight-forward if you have any C-code experience. There are any number of examples on the internet that you could work with.
You right about the pipe channel, I realized after my
last posting that combing sieve with a pipe channel
would be a more lightweight way to go, and I am
mostly done with my current implementation of that
now. This is good approach. Sieve should be used to cut down on the messages to be processed as it is light-weight and fast, and then the pipe channel can handle the rest of the actual 'heavy lifting'.
Are there any tips you might have regarding the
scalability of sieve or the pipe channel? Do you
know if every message that goes out to the pipe
channel spawns a new process? Yes it does. Which is why you need to limit the messages that end up in the pipe channel to just those that you need to end up there.
I vaugely recall there
were some options for throttleing the number of
messages processed in a given time frame, would that
be the best way to make sure I don't kill my server
if some clown in the HR department decides to blast
out a few thousand messages at once? 8-)The pipe channel can queue up messages. You can limit the number of 'jobs' by using a job pool (defined in job_controller.cnf file and set in imta.cnf).
thanks again for your help and advice, I really
appreciate it.Good luck with your project. It is always interesting to hear how customers are using the product.
Regards,
Shane.