On 20 Aug 2016, at 18:51, Zhiliang Hu <hu(_at_)animalgenome(_dot_)org> wrote:
I have a simple recipe to forward mails to a small list like in:
:0 c
* ^(To|Cc):.*sound-project(_at_)my(_dot_)institute(_dot_)edu
* ? formail -X"From " -xFrom: -xSender: -xReply-To: -xResent-From: \
| /var/private/.bin/multigram -b1 -m -l 28668 /my/path/sound.list.txt
{
:0 fwh
| formail -I "Reply-To: sound-project(_at_)my(_dot_)institute(_dot_)edu"
:0A
! `cat /my/path/sound.list.txt`
}
It works fine forwarding mails, except that the forwarded mails all are
missing from their header section "Content-type: multipart" lines like:
Content-type: multipart/alternative;
boundary="B_3487949262_366283"
and instead this is seen in the header:
Content-type: text/plain;
charset="UTF-8"
Since the boundary info is missing the multiparts of a mail body are all
displayed as plain text.
I am not sure what happened, or wrong with my recipe. I hope I won't have to
come up something to capture the "Content-type: ... boundary" lines to insert
back to the header ;-) Any advice please?
Content-type is not one of he headers you are extracting and sending to your
pipe, so of course it is not included.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail