Are you completely sure that it's procmail that's doing the munging?
Yes, after sendmail received the message as a BCC to another
mailbox, everything is right. This one surely is munged as well,
cause it already ran through the .procmailrc ;o)
I'm not sure I understand that first sentence. How do you know the
message was fine inside sendmail? Did you look at the queue file?
Well, I send the message to a BCC (another account, where it
arrived all right (looking with vi into the mailbox itself),
the one that came back from the maillinglist and your answer
surely ran through the procmail on my main account and
they were munged.
How about this: can you make the message availible via ftp? If there's
an actual bug in procmail then I would like to track it down, but that
requires a test case.
Will do later, but the last mail I did send you, bounced, because
your sendmail did not allow me sending mail to you :o(
Is there something wrong with the calling parameters in sendmail.cf:
Mlocal, P=/usr/local/bin/procmail, F=lsDFMAw5:/|@qSPfhn9, S=10/30,
R=20/40,
...
Looks good. The one other sendmail.cf variable to check would be
EightBitMode. If the problem message is not declared as 8bit data with
the proper MIME headers then sendmail may munge it depending on the
setting of the EightBitMode option. Also undeclared MIME data is not
always handled correctly by mail readers (for one, they have no way to
select a character set).
Well sendmail.cf says
# strip message body to 7 bits on input?
O SevenBitInput=
# 8-bit data handling
O EightBitMode=pass8
Is that ok ?
Kind regards, Frank
--
Dipl.-Inform. Frank Gadegast
mailto:frank(_at_)gadegast(_dot_)de
PHADE Software - PowerWeb http://www.powerweb.de
Leibnizstr. 30, 10625 Berlin, Germany fon/fax: ++ 49 30 3128103
======================================================================