For those who don't track mhonarc, from the mhonarc list. Looks very
interesting...
>
> One thing that may be of interest to users is I have developed
> a mail archiving system that using Procmail, MHonArc, and Namazu
> to easily manage mail archives for multiple lists. Features will
> in
Since I upgraded to have iso_xxx compliant subjects, I notice that most
emails go through with TWO spaces after the usual subject_prefix, on all
lists. I don't really mind, but just wanted to mention it.
-- Fil
___
Mailman-Developers mailing list
[E
> Since I upgraded to have iso_xxx compliant subjects, I notice that most
> emails go through with TWO spaces after the usual subject_prefix, on all
> lists. I don't really mind, but just wanted to mention it.
Precisely, here's how it happens :
"Subject: =?iso-8859-1?q?=5Bspip-dev=5D_?="
On Saturday, April 13, 2002, at 06:13 , Fil wrote:
>> Since I upgraded to have iso_xxx compliant subjects, I notice that most
>> emails go through with TWO spaces after the usual subject_prefix, on
>> all
>> lists. I don't really mind, but just wanted to mention it.
>
> Precisely, here's how it
> "Ben" == Ben Gertzfield <[EMAIL PROTECTED]> writes:
Ben> I think the email.Header package I wrote is doing the wrong
Ben> thing here.
Yup.
Ben> Either we need represent the whole thing as one or more
Ben> encoded-words, or we need to be super anal about whitespace
Ben>
On Saturday, April 13, 2002, at 02:59 , Stephen J. Turnbull wrote:
> Ben> Either we need represent the whole thing as one or more
> Ben> encoded-words, or we need to be super anal about whitespace
> Ben> between encoded-words and non- encoded-words.
>
> The latter. What are you going