[ maybe this should be an enhancement request or filed against documentation ] My goal is to copy the original message, modify the original, forward this modified message. I have a rule in matcherrc that triggers on From then copy "#mh/Mailbox/specialback" "execute" myprog %F then forward 5 "someemail@email.invalid" then move "#mh/Mailbox/special" myprog reduces the message body to a maximum of N chars and writes the new message to disk I am trying to forward the modified message but the original is forwarded instead of the modified message. Should I use different commands or is this not possible?
Actually, it's a question so should have been sent via the mailing list or asked on IRC and not here at all. See the FAQ: http://claws-mail.org/faq/index.php/Filtering_and_Processing_of_Messages#Can_a_filter_modify_the_contents_of_a_message.3F
The FAQ says "None of the built-in filters modify the contents of a message," I wasn't trying to do that. And the FAQ uses a SpamAssassin example to show how to modify a message but the message is not modified so the example is wrong. I think the bug or feature that I am up against is that the forward mechanism only works on in-memory messages. spamc just asks spamd to deliver a decision is it spam or not. Returning 1 or 0 from test. Is this a bug or non-existant feature? Does forward act on the message on disk or an in-memory message? It seems broken to me but maybe I misunderstand this behavior.
I closed this as INVALID because you are not reporting a bug or requesting a feature but are opening a discussion. This is not the place for a discussion. Anyway, the reason that the original is forwarded (rather than the modified version) is because your 'myprog' is broken. Even if it were not broken, it would not work in the way you expect. Please don't re-open this. For ways to open a discussion see http://www.claws-mail.org/MLs.php
Interesting approach to handling issues. This is a discussion of a bug or broken feature. If my program is broken why would it matter. Claws doesn't act on the file on disk and myprog only modifies the on disk file. You didn't at the least acknowledge that the docs are wrong that you pointed to for support of your assertion and point to a bug you filed against the docs. At least acknowledge that claws is broken here and update the docs with a real example that allows modifying a message and forwarding it along. Seeing the claws team stick their head in the sand on so many issues is not a good sign for this software.
(In reply to comment #4) > Interesting approach to handling issues. > This is a discussion of a bug or broken feature. Look, Marvin, I've tried to make it plain for you that this is not the place to chat. I've showed you where discussion should take place, but you seem insistent to make up your own rules. > If my program is broken why would it matter. Claws doesn't act on the file > on disk and myprog only modifies the on disk file. But it /does/ act on the file on disk, this is why I say your myprog is broken. > You didn't at the least acknowledge that the docs are wrong that you pointed > to for support of your assertion and point to a bug you filed against the > docs. That's the FAQ. I thought it would give you enough of a hint, but clearly not. > At least acknowledge that claws is broken here and update the docs with a > real example that allows modifying a message and forwarding it along. No, it's your 'myprog' which is broken. > Seeing the claws team stick their head in the sand on so many issues is not > a good sign for this software. No-one is sticking their head in the sand. Each (non-)issue you've raised has been addressed. But you can take it as a sign of whatever you want.