I could probably just informally replace the needed files if they can
"plug in" to 2.1.9, if that's easier than creating a patch. I won't
have time until next week to try it out, but I'd be glad to if it helps!
-Thanks, Joe
Barry Warsaw wrote:
> On Dec 5, 2006, at 9:12 AM, Joe Peterson wrote:
>
>> I do not have Mailman 2.2 installed on my mail server (I am at 2.1.9),
>> so I cannot try it out immediately, but I will keep this in mind,
>> and I
>> *think* it is a way to solve the issue I have, especially if LMTP
>> would
>> be better to use even for my non-mailman virtuals anyway (I'll play
>> around with this).
>
> Mailman 2.2 isn't near production ready yet, however I could imagine
> someone back porting the LMTP support into Mailman 2.1 --
> unofficially. I don't want to officially support it for Mailman 2.1,
> but it would be a fairly contained set of patches so it could be
> added to the contrib directory or some such.
>
> -Barry
>
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
