On Wed, 21 Aug 2002, Andy Isaacson wrote:
> Perhaps it's the equals signs in the List- headers that Mailman puts on
> the message. If that's the case, then you two should not have trouble
No. I read other mailing lists run by Mailman with List- headers (lots of
gnome and gtk lists, for example).
> reading the message that I'm delivering to you directly, but will have
> trouble with the message that gets delivered to the list.
I read both of them perfectly :)
> Alternatively, it might be the ISO coding of the From: address, in which
> case this message won't be problematic at all.
> In any case, this is just further evidence that Pine is irretrievably
> broken, and you should switch to Mutt instead. :)
Yes :) But I can't be bothered to learn Yet Another More or Less
Turing-Complete Configuration Language. I want something that Just Works,
which is why I use Pine in the first place. I'd like to reserve my
hacking skills for kernels, compilers and virtual machines, thank you.
> AFAIK, quoted-printable only uses the equals sign to escape characters,
> so if you look at the raw mailbox, there must be equals signs in there
> somewhere that are messing it up. I've intentionally avoided putting
> any in this message, as a debugging aid.
Well... there are quoted-printables in the places where Pine barfs. It is
usually something like spaces at the end of lines, which (for some reason)
So, the raw message has lots of lines ending with =20 and Pine handles the
first few just fine and then barfs very suddenly (if they occured during a
quoted part of a message and special colours are used for quoting, Pine
doesn't reset the colours, so everything has a strange colour until they
get reset by something).
I don't think the fault lies anywhere but with Pine -- and the day
something tells me how to make mutt pretend it is pine without giving me a
headache will be the day I switch.