I am running Mailman 2.1.9. I have a list where one posting has a
"Subject:" line:
Change in Procedure for Computers on list with possible Antivirus Problems
The next posting in the thread has:
Change in Procedure for Computers on list with possible AntivirusProblems
A subsequent p
Barry Finkel writes:
> I am running Mailman 2.1.9. I have a list where one posting has a
> "Subject:" line:
>
> Change in Procedure for Computers on list with possible Antivirus
> Problems
>
> The next posting in the thread has:
>
> Change in Procedure for Computers on lis
Barry Finkel wrote:
>I am running Mailman 2.1.9. I have a list where one posting has a
>"Subject:" line:
>
> Change in Procedure for Computers on list with possible Antivirus
> Problems
>
>The next posting in the thread has:
>
> Change in Procedure for Computers on list with possible An
Barry Finkel writes:
> > I am running Mailman 2.1.9. I have a list where one posting has a
> > "Subject:" line:
> >
> > Change in Procedure for Computers on list with possible Antivirus
> > Problems
> >
> > The next posting in the thread has:
> >
> > Change in Procedure for Compute
Barry Finkel wrote:
>
>"Stephen J. Turnbull" <[EMAIL PROTECTED]> replied:
>
>>Can you post a copy of the "raw" header as received by Mailman and as
>>sent by Mailman?
>
>I am not sure I have this information. What I see (and posted) from
>the list .mbox file - is that what was received by Mailman
Barry Finkel writes:
>> I am running Mailman 2.1.9. I have a list where one posting has a
>> "Subject:" line:
>>
>> Change in Procedure for Computers on list with possible Antivirus
>> Problems
>>
>> The next posting in the thread has:
>>
>> Change in Procedure for Compute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry Finkel wrote:
>
> Below are pieces of two messages. I have the original message
> from the archives of the sender followed by the relevant lines of
> the list .mbox file (including line numbers).
>
> ===
Mark Sapiro writes:
> But, the fact remains that there are many commonly used MUAs that drop a
> whitespace character in unfolding and there's not much we can do about that.
I wonder if they're better with RFC 2047. That is, suppose we
rendered
Subject: Pretend this is a long field
as
Subje