Re: [Mailman-Developers] USE_ENVELOPE_SENDER is not flexible enough

2002-01-30 Thread Stephen J. Turnbull
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes: BAW> BAW> Mailman shall rule THE WORLD! BAW> Take a number, man. (See .sig.) -- University of TsukubaTennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (29

Re: [Mailman-Developers] USE_ENVELOPE_SENDER is not flexible enough

2002-01-30 Thread Barry A. Warsaw
> "SJT" == Stephen J Turnbull <[EMAIL PROTECTED]> writes: > "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes: BAW> Mailman shall rule THE WORLD! SJT> Take a number, man. (See .sig.) | What are those straight lines for? "XEmacs rules." Hard to argue with that, seein

Re: [Mailman-Developers] Re: [Mailman-Announce] Once again, fame and fortune can beyours

2002-01-30 Thread Barry A. Warsaw
Welcome Terri! > "TO" == Terri Oda <[EMAIL PROTECTED]> writes: >> Of course, I'm a musician[1] not an artist, so I need your >> help. TO> I'm a musician too (well, more so than artist) but at 16x16 I TO> can at least blame the medium. :) Here's a first attempt. TO> ht

Re: [Mailman-Developers] Re: [Mailman-Announce] Once again, fameand fortune can be yours

2002-01-30 Thread John W Baxter
Barry said: >Very cool, thanks. You can see what it looks like in context on this >page: > >http://mail.python.org/mailman-21/listinfo Barry, Playground may not be quite ready. Replying to the confirmation message for Playground led to the following bounce: This message was created automa

Re: [Mailman-Developers] Re: [Mailman-Announce] Once again, fameand fortune can be yours

2002-01-30 Thread Barry A. Warsaw
> "JWB" == John W Baxter <[EMAIL PROTECTED]> writes: JWB> Barry, Playground may not be quite ready. You're right. I don't quite have the Exim config file set up quite right for the production MM2.0.x and experimental MM2.1 installs to co-exist. (I've emailed a plea for help to Nigel M

[Mailman-Developers] reply-to setting per user

2002-01-30 Thread Marc MERLIN
(following up a private discussion on having mailman allow users to decide if they want reply-to munging or not, not the list master) > Another thought is to not do the munging in CookHeaders.py, but to > defer it to later in the delivery process. If you could wedge it into > SMTPDirect.py it

Re: [Mailman-Developers] USE_ENVELOPE_SENDER is not flexible enough

2002-01-30 Thread Jason R. Mastaler
[EMAIL PROTECTED] (Barry A. Warsaw) writes: > It probably would be best to add a method get_author() which > returned a list of (From_, From:, Sender:) for comparison Alright, I've added a get_author() method to Mailman.Message which returns a list containing the From:, unixfrom, Reply-To:, and

Re: [Mailman-Developers] load balancing with mailman.

2002-01-30 Thread Marc MERLIN
On Tue, Jan 29, 2002 at 02:40:56PM -0500, Barry A. Warsaw wrote: > MM> Barry: With the new qrunner infrastructure, does qrunner still > MM> need to lock the lists during delivery? If qrunner doesn't > MM> modify config.db anymore, could it open config.db read only? > > Remember that

[Mailman-Developers] RE: Mailman developer?

2002-01-30 Thread Damien Morton
We can use GIFs, but we cant use the LZW compression option. As the GIFs we produce will be small, this is hardly a problem. At any rate, any of GIF, PNG or JPEG will do. The advantage of using encryption rather than hashing is that the email renderer needs to know nothing about the system excep