On Sat, 2 Nov 2019, Andreas Schamanek wrote:
:0 hw | (formail -I "X-Loop: my-email@my-domain" \ -I "Subject: Problems with ....."; \ cat - notify.moderators.txt) \ | sed 's/FROMA/'"$FROMA"/g | sed 's/SUBJET/'"$SUBJE"/g \ | $SENDMAIL -oi $LSTMATNR
Everything works fine except that at the end of the notification mail body text, one line of miltipart body separater get appended, like this one: --_000_DB6PR05MB34312B252CB0D273BA34B81A8E610DB6PR05MB3431bxrp_--
I wonder how does this single line from the body get there?
I had my procmail process the sample message you provided with the above rules (after removing the "-"), and sure enough it did not produce a separator. However, I now realize that you are generating broken messages because you keep the headers of the original message but you exchange the body with notify.moderators.txt. If the original message, like the sample you provided, is a multipart/* MIME message its Content-Type header might confuse whatever processes the generated message (i.e. $SENDMAIL etc.) because it includes a separator that is nowhere to be found in the body.
Thank you for your time figuring this out. I think you are right. Essentially this recipe is only to send a separate note upon certain situations, thus I dropped using "formail" to forge a mail header, and tested "echo" to make (new) mail headers which works out fine. Thanks again! ZL