[Email-SIG] fixing the current email module

[Glenn Linderman]

On approximately 10/8/2009 4:20 PM, came the following characters from 
the keyboard of Mark Sapiro:
> Glenn Linderman wrote:
>   
>> However, there are definitely mailing lists that don't do that.  Google 
>> Groups is one example that doesn't collapse, and always prepends the 
>> headers in front of Re:.  Seems like all the Python lists do the 
>> collapsing (I wonder why! :) )  Other lists don't do prepending (I think 
>> the RFCs recommend not prepending in Subject, actually), of the others 
>> I'm subscribed to, that prepend, some collapse and some don't.
>>     
>
>
> You seem to be forgetting the case where the encoded subject already
> contains the prefix, or do you not care if the subject just continues
> to grow with Re:'s and repeated prefixes?
>   

Mark,

Please read the last two paragraphs of my message you replied to, two or 
three more times.  Here they are again for reference.

> And don't forget removing the prior prepended text before adding the 
> new prepended text.
>
> Actually, as long as the prepended text is ASCII, all that work can be 
> done on the encoded value.  When it is not ASCII, it may still be 
> separated and recognizable.  Still that logic is more complex than 
> decoding, handling as Unicode, and encoding.... when it works.  Just 
> pointing out that there is more than one way to do things... 

-- 
Glenn -- http://nevcal.com/
===========================
A protocol is complete when there is nothing left to remove.
-- Stuart Cheshire, Apple Computer, regarding Zero Configuration Networking