Jerrad wrote:
> Hmm, on a hunch I just discovered that somehow the call to mhstore
> in mime-add-hook's for loop is the trigger... of course that's the
> raison d'etre of the script :-/
Try feeding mhstore from a file instead of a message, something like:
FILE=`mhpath $MSG`
for PART in `mhstore -file $FILE 2>&1 |
instead of:
> for PART in `mhstore $MSG 2>&1 |
And similar with mhfixmsg. When fed from files, the programs don't
update sequences.
David
_______________________________________________
Nmh-workers mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/nmh-workers
