We've been having this problem recently, and in each case the subscriber
(two so far) has used Blackberry to send the post. We would like to find a
solution, too, because even though the posts look fine in the archives and
when sent individually, they wreak havoc in the digests. At first we
thought it was basically a line-wrap problem, but the headers include
these lines: 

1) Comments: RFC822 error: <W> TO field duplicated. Last occurrence 
was retained.                                                       
                                                                    
2) Content-Transfer-Encoding: base64                                

So now we're assuming that it's the base64 encoding that's the problem.

It also seems to happen only when the sender replies to a message, not
when he composes a new message.

I'm not sure if this is your same problem, Stephen, but if your problem
posts are also sent via Blackberry, then maybe we can find a solution.

Jane Lyle
co-owner, Copyediting-l

On Thu, 3 Mar 2005, H. Stephen Wright wrote:

> I periodically have subscribers complaining that some posts are unreadable.
>  In all of these cases, the messages look fine in the archives and in my
> e-mail program (Novell GroupWise).  However, some subscribers say they are
> seeing lines of code that look like this:
> 
> QmFkIEVkdWNhdGlvbiBpcyBhbiBleGNlbGxlbnQgZmlsbSBub2lyLiAgSXQgYWxzbyBoYXMg
> YW4gZXhjZWxsZW50ICAKc291bmR0cmFjayBieSBBbGJlcnRvIElnbGVzaWFzLiAgSWdsZXNp
> YXMnIHNjb3JlIGlzIHZlcnkgcmVtaW5pc2NlbnQgb2YgIEJlcm5hcmQgCkhlcnJtYW5uLiAg
> 
> Is there something that I as listowner can do about this, or is this
> something that is dependent on subscribers' e-mail clients?  I checked the
> LSTOWN-L archives and see that this problem was mentioned in December, but I
> couldn't find a definitive answer.
> 
> Stephen Wright
> Principal Owner, FILMUS-L
> 
> 
>