From r-spirit at sproxy03.hi-ho.ne.jp Fri Aug 22 19:04:55 2003 From: r-spirit at sproxy03.hi-ho.ne.jp (r-spirit@sproxy03.hi-ho.ne.jp) Date: Sat Aug 23 06:34:42 2003 Subject: [meta-sig] Voice Message (170479694618661) Message-ID: <0HK00094WJW723@sproxy03.hi-ho.ne.jp> ------ name ------ Anonymous Friend ------ address ------ Secret ------ message ------ Add expressive voice and music to your websites and emails. Use this new marketing tool in your business or just for fun!. Click the following link to listen to your message: http://voice-email.vze.com/?id=223297967731 Local Time: 2003/8/22/18:4 From barry at python.org Tue Aug 26 03:19:20 2003 From: barry at python.org (Barry Warsaw) Date: Mon Aug 25 22:19:21 2003 Subject: [meta-sig] New email package SIG Message-ID: <1061864324.12874.22.camel@anthem> Now that the email package is standard in Python, I want to retire the (misnamed) mimelib project at SourceForge. I think this project has served us well, but it's time to move things back into the regular Python flow. To that end, I've essentially disabled as much of the public info for the project as possible. However, there's still work to be done, specifically on a version 3.0 of the API, which will buff off the last of the rough edges, integrate Anthony's new parser, etc. Sounds like a perfect mission for a SIG to me! So I'm proposing a formal email-sig@python.org. I've actually already created the mailing list, and unless there are no objections, I'd like to make this a formal SIG. We can't actually remove the mimelib-devel mailing list, but I suggest we all ignore it, except for archival purposes. I intend to be the SIG shepherd, along with Jason Mastaler (nice of me to volunteer you, eh? :). It's mission is to design and implement email package 3.0 in time for Python 2.4, fixing the things described above while maintaining backward compatibility if at all possible. I'd like for this SIG to expire the day Python 2.4 is released, but who knows when that will happen. :/ So let's say this SIG expires one year from now -- September 2004, with possible extensions as necessary. All in favor? All opposed? -Barry From guido at python.org Mon Aug 25 21:54:03 2003 From: guido at python.org (Guido van Rossum) Date: Mon Aug 25 23:54:10 2003 Subject: [meta-sig] New email package SIG In-Reply-To: Your message of "25 Aug 2003 22:18:44 EDT." <1061864324.12874.22.camel@anthem> References: <1061864324.12874.22.camel@anthem> Message-ID: <200308260354.h7Q3s3703221@12-236-84-31.client.attbi.com> > Now that the email package is standard in Python, I want to retire the > (misnamed) mimelib project at SourceForge. I think this project has > served us well, but it's time to move things back into the regular > Python flow. To that end, I've essentially disabled as much of the > public info for the project as possible. > > However, there's still work to be done, specifically on a version 3.0 of > the API, which will buff off the last of the rough edges, > integrate Anthony's new parser, etc. Sounds like a perfect mission for > a SIG to me! > > So I'm proposing a formal email-sig@python.org. I've actually already > created the mailing list, and unless there are no objections, I'd like > to make this a formal SIG. We can't actually remove the mimelib-devel > mailing list, but I suggest we all ignore it, except for archival > purposes. > > I intend to be the SIG shepherd, along with Jason Mastaler (nice of me > to volunteer you, eh? :). It's mission is to design and implement email > package 3.0 in time for Python 2.4, fixing the things described above > while maintaining backward compatibility if at all possible. I'd like > for this SIG to expire the day Python 2.4 is released, but who knows > when that will happen. :/ So let's say this SIG expires one year from > now -- September 2004, with possible extensions as necessary. > > All in favor? All opposed? > -Barry Aye, sir! --Guido van Rossum (home page: http://www.python.org/~guido/) From jason at mastaler.com Tue Aug 26 01:03:49 2003 From: jason at mastaler.com (Jason R. Mastaler) Date: Tue Aug 26 02:27:56 2003 Subject: [meta-sig] Re: New email package SIG References: <1061864324.12874.22.camel@anthem> Message-ID: Barry Warsaw writes: > I intend to be the SIG shepherd, along with Jason Mastaler (nice of > me to volunteer you, eh? :). No problem. Glad to help. From anthony at interlink.com.au Tue Aug 26 19:11:06 2003 From: anthony at interlink.com.au (Anthony Baxter) Date: Tue Aug 26 04:11:41 2003 Subject: [meta-sig] Re: [mimelib-devel] New email package SIG In-Reply-To: <1061864324.12874.22.camel@anthem> Message-ID: <200308260811.h7Q8B6n7014079@localhost.localdomain> >>> Barry Warsaw wrote > So I'm proposing a formal email-sig@python.org. > All in favor? All opposed? +1 from me (unsuprisingly :) -- Anthony Baxter It's never too late to have a happy childhood. From sdrees at sdrees.de Tue Aug 26 11:45:15 2003 From: sdrees at sdrees.de (Stefan Drees) Date: Tue Aug 26 04:45:20 2003 Subject: [meta-sig] Re: [mimelib-devel] New email package SIG In-Reply-To: <200308260811.h7Q8B6n7014079@localhost.localdomain> References: <1061864324.12874.22.camel@anthem> <200308260811.h7Q8B6n7014079@localhost.localdomain> Message-ID: <20030826084515.GA10535@knoten.biz> On Tue, Aug 26, 2003 at 06:11:06PM +1000 - a wonderful day - Anthony Baxter wrote: > > >>> Barry Warsaw wrote > > So I'm proposing a formal email-sig@python.org. > > All in favor? All opposed? > > +1 from me (unsuprisingly :) +1 from me (in case anyone cares ;) All the best, Stefan Drees. -- Stefan Drees, sdrees@python.net, www.sdrees.biz Fingerprint = 516C C4EF 712A B26F 15C9 C7B7 5651 6964 D508 1B56 From barry at python.org Thu Aug 28 02:43:13 2003 From: barry at python.org (Barry Warsaw) Date: Wed Aug 27 21:43:15 2003 Subject: [meta-sig] New SIG: email-sig Message-ID: <1062034958.998.19.camel@anthem> After unanimous consent on the meta-sig and mimelib-devel lists, I've gone ahead and created the new email-sig. See http://www.python.org/sigs/email-sig for details. This SIG's mission is to design and implement version 3.0 of the email package for Python 2.4. Please use this SIG instead of the mimelib-devel list from now on. -Barry