Re: [Mailman-Developers] Should we move to Bazaar?
Hi all, Sorry that I can't say anything nice on this thread but my feelings on this distributed somthing :-P is just the same as Mark's. Currently, I am extremely busy on everyday duties and difficult to find time to code. I will be able to spare more time for mailman when the cemester ends in July. I will catch up any change in the version control system then. So please feel free to select anything better. Mark Sapiro wote: > Barry Warsaw wrote: >> I propose that no matter which way we go (Mercurial, Bazaar or >> something else), we convert only the trunk. Let's leave the stable >> 2.1 branch on SF under Subversion, but do all new development in the >> dvcs. It will be a bit more painful to commit fixes across both >> branches (sorry Mark, Tokio!) but that will probably be the case >> fairly soon anyway, as it's unavoidable that the trunk is going to >> diverge (<3.0 cough>). > > > I'm just now trying to catch up on this thread. Mostly, I have nothing > to contribute because I have no experience with any dvcs. > > That said, for me personally, I don't mind learning something new. It's > one of the underlying reasons why I'm here in the first place. And > while its always nice to have a pain free way to get from A to B, the > pain can be managed if B is a clear improvement. > -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-Users] [Fwd: TypeError: us-asciiwith python2.4 and mailman 2.1.8-1 (debian)]
Mark Sapiro wrote: > Tokio Kikuchi wrote: > >> Hi developers, >> >> This particular problem is caused by a bug in email 4.0.1 package which >> was fixed in the most recent subversion repository. >> http://svn.python.org/view/python/trunk/Lib/email/message.py?rev=54333&r1=50840&r2=54333 >> >> Maybe it's time to think of next bug fix release of mailman 2.1.10 as >> soon as the email 4.0.2(?) is out. > > > But Mailman 2.1.x ships with and should be installed with the email > 2.5.x branch, so unless this bug was also introduced and subsequently > fixed in that branch as well, it shouldn't affect a properly installed > Mailman. > Oh yes, you're right, Mark. I was too much involved in mailman 2.2 which will be shipped with email 4.0.x. Perhaps, we should make warning against package distributers that 'misc' directory (pythonlib) in the mailman source tree can't be omitted. BTW, I'm looking forward to see email 4.0.2 out. ;-) -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-Users] [Fwd: TypeError: us-ascii with python2.4 and mailman 2.1.8-1 (debian)]
Hi developers,
This particular problem is caused by a bug in email 4.0.1 package which
was fixed in the most recent subversion repository.
http://svn.python.org/view/python/trunk/Lib/email/message.py?rev=54333&r1=50840&r2=54333
Maybe it's time to think of next bug fix release of mailman 2.1.10 as
soon as the email 4.0.2(?) is out.
Justin Warren wrote:
> Hi folks,
>
> I hit the same sort of problem as a couple of other people apparently
> have, eg:
>
> http://mail.python.org/pipermail/mailman-users/2006-November/054246.html
>
> I hit this when Mailman attempts to send digests.
>
> I thought I'd tracked the issue to the way Charset is used within
> Mailman/Scrubber.py, on line 193 (some modifications by me to print
> debug output):
>
> charset = None
>
> lcset = Utils.GetCharSet(mlist.preferred_language)
>
> print "getting charset for preferred language:", repr(lcset)
>
> lcset_out = Charset(lcset).output_charset or lcset
>
> print "lcset_out is:", repr(lcset_out)
>
> Which yields:
>
> getting charset for preferred language: 'us-ascii'
> lcset_out is: u'us-ascii'
>
> It appears that Charset returns a unicode string for
> its .output_charset, which python2.4 email.Message.set_charset() does
> not recognise as a string, and it isn't a Charset either, so a TypeError
> is raised.
>
> I don't know enough about why .output_charset is being used, or why it
> is unicode, but it seems that changing line 193 to read:
>
> lcset_out = Charset(lcset) or lcset
>
> would prevent this error.
>
> However, something else is also returning a unicode string, since after
> changing Scrubber, you end up with this error:
>
> Traceback (most recent call last):
> File "/usr/lib/mailman/cron/senddigests", line 94, in ?
> main()
> File "/usr/lib/mailman/cron/senddigests", line 86, in main
> mlist.send_digest_now()
> File "/var/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now
> ToDigest.send_digests(self, mboxfp)
> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in
> send_digests
> send_i18n_digests(mlist, mboxfp)
> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 339, in
> send_i18n_digests
> mcset = msg.get_content_charset('')
> File "/usr/lib/python2.4/email/Message.py", line 805, in get_content_charset
> charset = unicode(charset, 'us-ascii').encode('us-ascii')
> TypeError: decoding Unicode is not supported
>
> I haven't worked out what this other thing is as yet.
>
> Alternately, patching email/Message.py (line 803) to ignore a charset
> that is a unicode string seems to work, but is probably fragile or
> broken in other ways:
>
> # charset character must be in us-ascii range
>
> try:
>
> if not isinstance(charset, unicode):
>
> charset = unicode(charset, 'us-ascii').encode('us-ascii')
>
> except UnicodeError:
>
> return failobj
>
> I hope this helps someone more knowledgable about Mailman to work out
> what the underlying problem is.
>
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8184] trunk/mailman/Mailman
Hi Barry, [EMAIL PROTECTED] wrote: > Revision: 8184 > http://svn.sourceforge.net/mailman/?rev=8184&view=rev > Author: bwarsaw > Date: 2007-03-29 22:09:36 -0700 (Thu, 29 Mar 2007) > > Log Message: > --- > api_lock(): When locking the MailList object, tell the SQLAlchemy session to > expire the object. This way, when the MailList attributes are next accessed, > the ORM will reload them from the database, getting any new values possibly > set in other processes. > > This works better than trying to use always_refresh=True on the mapper, or > trying to do a reload() because both of those approaches blow away locks. I'm > not sure why this, but I suspect that it's because the identity map is handing > us back a different object, rather than invalidating the object's attributes. > > Modified Paths: > -- > trunk/mailman/Mailman/database/dbcontext.py > trunk/mailman/Mailman/testing/test_handlers.py > > Modified: trunk/mailman/Mailman/database/dbcontext.py > === > --- trunk/mailman/Mailman/database/dbcontext.py 2007-03-27 06:35:12 UTC > (rev 8183) > +++ trunk/mailman/Mailman/database/dbcontext.py 2007-03-30 05:09:36 UTC > (rev 8184) > @@ -129,6 +129,7 @@ > > # Higher level interface > def api_lock(self, mlist): > +self.session.expire(mlist) > # Don't try to re-lock a list > if mlist.fqdn_listname in self._mlist_txns: > return > Wow! Fix is so simple. I've done a test with this using two terminals: terminal A terminal B $ bin/withlist test$ bin/withlist test >>> m.description u'' >>> m.Lock() >>> m.description = 'test' >>> m.Save() >>> m.Load() >>> m.description u'' >>> m.Unlock() >>> m.Lock() >>> m.description u'test' Mere Load() can't refresh the list attributes but needs Lock() to get them. A few problem remains like decorating the message where OutgoingRunner is used. This runner don't update the database so it doesn't use Lock() but only Load(). We should fix them to use Lock() (and Unlock()) to reload data. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] How can I reload mlist data from SA database
> We must be sure that always_refresh=True don't break the lock.
>
No good. Can't get lock at all.
$ bin/withlist test
Loading list [EMAIL PROTECTED] (unlocked)
The variable 'm' is the test MailList instance
>>> m.Lock()
>>> m.Locked()
False
>>> m.Save()
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/mailman/Mailman/MailList.py", line 576, in Save
self.__lock.refresh()
File "/usr/local/mailman/Mailman/LockFile.py", line 187, in refresh
raise NotLockedError('%s: %s' % (repr(self), self._read()))
NotLockedError: : None
>>>
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] How can I reload mlist data from SA database
Barry Warsaw wrote: > Hi Tokio, > > I wonder if we shouldn't just be adding always_refresh=True to the > mappers? I can't get to the SQLAlchemy site atm to provide a reference. I can't access the sqlalchemy site either now. But, I tested my code with two terminals using bin/withlist seeing if I can see a change in one in another. What is odd was that if I used only session.refresh() in Load(), the locks are broken. We must be sure that always_refresh=True don't break the lock. -- Tokio Kikucih, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] How can I reload mlist data from SA database
Barry Warsaw wrote: > On Mar 27, 2007, at 4:22 AM, Tokio Kikuchi wrote: > >> I've submitted a patch to address this problem on SF patch area >> because I'm not confident whether to check this in the svn. I hope >> you have time to review and write a better patch. > > Hi Tokio, > > Thanks... what's the patch #? > - -Barry http://sourceforge.net/tracker/index.php?func=detail&aid=1688957&group_id=103&atid=300103 Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] How can I reload mlist data from SA database
Hi again, Barry Warsaw wrote: >> testing 2.2 code on my PC. What is curious about the LMTP/HTTP >> interfaces with SQLAlchemy based database is that changes commited in >> LMTP/HTTP sessions cannot be reflected on the other sessions. If I >> subscribe an address via HTTP then it cannot be unsubscribed from LMTP >> and vise versa, until I restart the runners. Perhaps we need a reload >> mechanism but I don't know how to implement it. > > I think I've noticed a similar problem. I think it has to do with > concurrency between processes using SQLAlchemy. As you said, it > seems like we need an explicit "reload" but I'm really hoping that > that's just because we're not doing something right. I haven't had > time to figure it out yet, or to contact the SA mailing list to get > their feedback. We definitely need to address that issue before we > get too far down the SA road. I've submitted a patch to address this problem on SF patch area because I'm not confident whether to check this in the svn. I hope you have time to review and write a better patch. Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8181] trunk/mailman/Mailman
Hi, > I noticed that current trunk is failing three tests: > > test_no_multipart_mixed_charset > test_scrub_image > test_scrub_text I was using the latest svn of email. :-) BTW, I can't create a new list in my fresh installation. # bin/newlist test Traceback (most recent call last): File "bin/newlist", line 48, in main() File "bin/newlist", line 39, in main status = sys.modules[module_name].main() File "/usr/local/mailman/Mailman/bin/newlist.py", line 101, in main parser, opts, args = parseargs() File "/usr/local/mailman/Mailman/bin/newlist.py", line 92, in parseargs if opts.password_scheme.lower() not in passwords.SCHEMES: AttributeError: 'module' object has no attribute 'SCHEMES' -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8181] trunk/mailman/Mailman
Hi Barry,
> I noticed that current trunk is failing three tests:
>
> test_no_multipart_mixed_charset
> test_scrub_image
> test_scrub_text
>
> Can you check to see if those are failing for you?
I've confirmed sucess (colinux/debian python2.4) but check them more, on
different environments.
>
> Also I was wondering about the latest change to passwords.py:
> Earlier, I was using s.encode('utf-8') to ensure that we had an 8-bit
> string for the hash function. I'm wondering if you prefer str()
> over .encode('utf-8') here and if so, what the reason is?
I was just re-entering the last patch but there may remain older data in
my installation. I'll check it in a fresh install and make correction.
If 'rest_group' is a hashed password, it should be in the ascii range
but we are going to allow plain password which I fogot.
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] Problem with format=flowed patch
Mark Sapiro wrote: > I don't think your suggestion is correct. What I am trying to do is get > the format= and delsp= parameters from only the first text/plain part > in the message. Often, this will be the only part in which case it > doesn't matter. Sorry that I misunderstood. It was a little bit too early in the morning to start working. ;-) (6AM Japan) I've almost done with this 'format=flowed' patch and others for Scrubber.py and Decorate.py for the trunk. I'll commit them after adding some more test codes. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Problem with format=flowed patch
Hi Mark,
I was working this patch on the trunk.
I think the indent level of this part in Scrubber.py should be
if charset is None:
charset = part.get_content_charset(lcset)
+format = part.get_param('format')
+delsp = part.get_param('delsp')
Sorry if I misunderstand.
Mark Sapiro wrote:
> I have been working on a fix for the problem of Mailman's dropping
> format=flowed from Content-Type: headers. There is a bug report and a
> patch at
> <https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&group_id=103>.
>
> The patch to Scrubber.py has just been revised (revised patch is
> attached to the above tracker item).
>
> Scrubber would throw an exception when processing a message with no
> text/plain part. If you are using a prior version of this patch,
> please get the current version to avoid this problem.
>
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] How can I reload mlist data from SA database
Barry, >> Other than that, I think I've checked with i18n plain text message >> deliveries for both regular and digest. Still to go are mime >> multipart >> messages and archives. >> >> I've also added a comment on Testing Mailman 2.2 wiki page how to test >> run the 2.2 code. > > Thanks, and I saw your recent patches. One thing we should be extra > careful about is to include unit tests for anything we fix. I really > want to improve our test suite so having test that cover the things > you change are really important. I'm also trying to be very diligent > about keeping the test suite working. Eventually I'd like to > integrate our stuff with one of the Python community buildbots. Ok, I will try to contribute test codes as well as the i18n fixes in the main codes. BTW, I realized I might have messed code and some tests fail. Do you want password scheme to be called by ENUM or TAG. I saw the default scheme in Defaults.py is string and changed to be called by TAG but it made test_passwords.py to fail. I think we can change the test code like so: class TestPBKDF2Passwords(TestPasswordsBase): scheme = 'pbkdf2' Thoughts? > > Thanks, and I hope you haven't wasted your entire spring vacation > waiting for me to respond! :) Never mind. The new semester starts in April. :) -- Tokio Kikuchi [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
[Mailman-Developers] How can I reload mlist data from SA database
Hi Barry, Since we at Japanese universities are in Spring vacation, I started testing 2.2 code on my PC. What is curious about the LMTP/HTTP interfaces with SQLAlchemy based database is that changes commited in LMTP/HTTP sessions cannot be reflected on the other sessions. If I subscribe an address via HTTP then it cannot be unsubscribed from LMTP and vise versa, until I restart the runners. Perhaps we need a reload mechanism but I don't know how to implement it. Other than that, I think I've checked with i18n plain text message deliveries for both regular and digest. Still to go are mime multipart messages and archives. I've also added a comment on Testing Mailman 2.2 wiki page how to test run the 2.2 code. Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] My new job
Congratulations, Barry! I'm very happy to hear that you can spend more time on Mailman. I also learned by quick search that Canonical is founded by this nice guy. :) http://en.wikipedia.org/wiki/Mark_Shuttleworth Barry Warsaw wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello everyone, > > I just wanted to drop a quick note to let you know that I have > started working for Canonical, the folks who distribute Ubuntu Linux > and develop the Launchpad service for distributed open source > development. > > I'm quite excited to be working for Canonical. They are a Python and > Zope shop, very open source friendly, and based on Linux, so I'm > working in an environment that's both familiar and fun. They're also > a distributed company, without traditional offices, but with many > folks working all over the world. They're also hiring . :) > > While this is good for Barry (and hopefully good for Canonical :), I > know you're thinking, "what does this mean for Mailman?" Well, I'm > glad you asked! > > Part of my official duties will be to integrate Mailman with > Launchpad so as to enable more powerful communication patterns among > members of a distributed development team. While I won't be > spending /all/ of my time on Mailman, it will be getting some > official love. I hope that this will help move the current > development branch closer to a release some time later this year. > Other than that, not much will really change. Mailman is and will > always be released under the GPL, and it will continue to be a GNU > project. > > If you have any questions or concerns, please send them directly to > me. I will attempt to answer them as best I can, and if there are > common themes, I'll post updates here. > > Thanks for your support and keep on delivering with Mailman! > > - -Barry > > Here are some related links: > > http://www.canonical.com > http://www.ubuntu.com > http://launchpad.net > > P.S. I'll be at PyCon this year so if you're coming too, please say hi! > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (Darwin) > > iQCVAwUBRcUTb3EjvBPtnXfVAQIQKgP/XFVeeDBn6QVXkE9oK1YJxyrLZZET5GxT > TAvTJgfndkcWPuUpbC5D6hcpDNa6sfIgJnR3enoW7MgKpOAtIXTuXqPpNiFMBVT2 > qUhlDHhwYzdJWWyzI/oXGRvt0lMqqA69Iu7A6DAKrgksBB128V/mYxTfv8BPmF4W > uASb/9MkmAQ= > =h+IQ > -END PGP SIGNATURE- -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Pickles begone
Hi Fil, Fil wrote: > tried to modify the list options thu the web ui and got > > SQLError: (OperationalError) attempt to write a readonly database 'UPDATE > "List data" SET bounce_processing=? WHERE "Listdata".list_id = ?' [0, 2] Who and what is the owner and permission of data/mailman.db. Are you accessing web ui via wsgi (HTTPRunner) or classic cgi? > > > I haven't tried yet to convert an older list to the new system. > > > -- Fil -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Postfix/virtual-mailman not compatible when using dedicated destination (like "localhost")
Sorry, I forgot to reply-all. > The other thing is that you'll get the individual -subqueue entries > if you don't want to use LMTP_ONLY_DOMAINS (presumably because you > can't create a separate subdomain for your lists). Right? Yeah, right. :-) LMTP_ONLY may be a little bit confusing because you can bypass this by /etc/postfix/virutal. MOSTLY_LMTP_DOMAINS ? -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Postfix/virtual-mailman not compatible when using dedicated destination (like "localhost")
Hi, Joe Peterson wrote: > > http://www.qnan.org/~pmw/howtos/mailman-virtuals.html > In mailman-2.2, Postfix.py is considerably patched from the current version, especially making use of LMTP interface. New configuration output is summarized in http://mail.python.org/pipermail/mailman-developers/2006-November/019307.html (you should convert back ' at ' -> '@') In this model, your '@localhost' corresponds to '@dom1.example.com' and all your list and personal maiboxes are to 'dom2.example.com'. You need no individual listname(-subqueue) destination in aliases/virtual/transport files. Only one line dom2.example.com lmtp:localhost:8025 in transport file. You only have to manage /etc/postfix/virtual for personal accounts. Is this suffice your needs? > I've submitted patches for Mailman before, and I'd be glad to do one > again, but I wanted to ask: > > 1) Do you see benefit to adding a variable that would define this > right-hand-side domain (e.g. "localhost") for virtual-mailman? > > 2) What is a good name for the variable? (POSTFIX_VIRTUAL_DESTINATION?) -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8100] trunk/mailman/Mailman/MTA/Postfix.py
Hi,
After all, you are right, Barry.
Tokio Kikuchi wrote:
>>> - if config.USE_LMTP immediately after ALIASFILE add/remove; we need
>>> to keep alias settings because postfix rejects as unknown if
>>> not present.
>> I haven't tried this diff yet, but are you sure that you need the
>> alias settings if you've got a transport_maps setting? I thought
>> that I tested using fully qualified alias names in the transport map
>> and not needing alias file entries unless you wanted site-wide or
>> across-all-domain aliases, e.g. [EMAIL PROTECTED]
>
> Well, I'm testing on debian/postfix-2.1.5, which may be old, but the
> postfix returns 550 if I set up with transport map only. But,
> additional test on my site revealed that using virtual map resulted in
> pipe command and not lmtp. :-( I'll test it more on this weekend.
>
I've committed in trunk and here is the basic configuration for Postfix
virtual host environment. We need no indivual entries for transport
file. You may have to run bin/genaliases if LMTP_ONLY_DOMAINS is
updated though.
Postfix configuration
main.cf
+-
|# dom1 is the main hostname.
|# dom2 is not here
|mydestination = dom1.example.com
|# You need aliases for noreply address
|alias_maps = hash:/etc/aliases
|hash:/usr/local/mailman/data/aliases
|# for persons in dom2 domain
|virtual_alias_maps = hash:/etc/postfix/virtual
|# everything else is in transport
|transport_maps = hash:/usr/local/mailman/data/transport
+-
/etc/postfix/virtual
+-
|# if you want to deliver to a real person in dom2
|[EMAIL PROTECTED] dom2user
+-
/usr/local/mailman/data/aliases
+-
|noreply: /usr/local/mailman/data/owner-bounces.mbox
+-
/usr/local/mailman/data/transport
+-
|# This file is automatically generated
|[EMAIL PROTECTED] local:noreply
|... etc.
|# dom2 is for mailman only (except in /etc/postfix/virtual)
|dom2.example.com lmtp:localhost:8025
|# list transports follow.
|[EMAIL PROTECTED] lmtp:localhost:8025
|... etc.
+-
etc/mailman.cfg (Defaults.py)
+-
|USE_LMTP = Yes
|add_runner('LMTPRunner')
|add_domain('dom2.example.com', 'www2.example.com')
|LMTP_ONLY_DOMAINS = ['dom2.example.com']
|# Use this domain only for mailman mailing list.
|# You should write postfix 'virtual' file for other persons
|# in this domain.
+-
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8100] trunk/mailman/Mailman/MTA/Postfix.py
>> - if config.USE_LMTP immediately after ALIASFILE add/remove; we need >> to keep alias settings because postfix rejects as unknown if >> not present. > > I haven't tried this diff yet, but are you sure that you need the > alias settings if you've got a transport_maps setting? I thought > that I tested using fully qualified alias names in the transport map > and not needing alias file entries unless you wanted site-wide or > across-all-domain aliases, e.g. [EMAIL PROTECTED] Well, I'm testing on debian/postfix-2.1.5, which may be old, but the postfix returns 550 if I set up with transport map only. But, additional test on my site revealed that using virtual map resulted in pipe command and not lmtp. :-( I'll test it more on this weekend. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8090] trunk/mailman/Mailman
Hi Barry, > >>> E.g. when I try to use r8090 via the Apache ScriptAlias path, I end >>> up getting three slashes between the host and the 'mailman' prefix. >> Oops, I'll try restore ScriptAlias. > > Cool, thanks. I may commit a few changes in this area, but I'll try > not to mess you up too much ;). I was wrong in writing wsgi_app.py at SCRIPT_NAME CGI environment variable. It was not merely the name of the script but the script path. Now the script can be accessed by /listinfo, /mailman/listinfo, or even /mailman/blah/listinfo etc. etc. You can now write httpd.conf like so: ProxyPass /mailman/ http://localhost:2580/mailman/ By this, we can use the same SCRIPT_NAME (or script path) for both wsgi backend and apache frontend. We might be able to get rid of the HTTP_REFERER and '../' things from our code but I've only checked in thus far. Please check and test it. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8090] trunk/mailman/Mailman
> Hi Tokio, > > I'm not so sure about this change. It breaks the ability to access > the web page urls by both the wsgi path and the apache ScriptAlias > path at the same time. I've tried to make sure that worked because > it's pretty useful for debugging. Well, I was inclined to abolish ScriptAlias (CGI) method because of SGUI complexities. ;-) > > I'm trying to keep the principle that all internal web page urls are > relative, which is why we currently try to figure out the prefix to > the script and then reproduce that in the cookie path (see > SecurityManager.py). I've also been thinking about trying to get rid > of mlist.web_page_url (I don't much like hard coding that in the > list's data). > > I understand that we'll need absolute paths in the email > notifications, and I've read the note about not exposing wsgi_app > interface to the internet. I'm not sure I agree with the latter > though, and besides, I'd like us to be as flexible as possible for > wsgi integration. I think we should try to find some other way to do > the email notification urls and keep GetScriptURL() returning > relative paths. > Like VirtualHostMonster in Zope? > E.g. when I try to use r8090 via the Apache ScriptAlias path, I end > up getting three slashes between the host and the 'mailman' prefix. Oops, I'll try restore ScriptAlias. > > - -Barry -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Problem with new configuration.Configuration.load()
Mark Sapiro wrote: > If the new configuration.Configuration.load() method is given a > configuration file argument which is a non-existent file, it will > silently fall back to loading mm_cfg.py. > > I think it should remember whether a filename argument is passed and > complain if the passed file doesn't exist. > +1 BTW, should we all move to new config sheme ? Then, should we make some upgrade script in Mailman/versions.py ? -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Converting mm_cfg to config in mmshell scripts
Mark Sapiro wrote: > Several of the mmshell scripts in Mailman/bin in the SVN trunk have not > been converted from mm_cfg to the new config scheme, given a > -C/--config option, etc. > > I have done, but not checked in a few. If nobody claims this job, I'll > do the rest and check them in. > +1 -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] HTTPRunner.py
Hi, > I checked in a bunch of updates to the web interface that should make > things run better under wsgi. It's still not perfect, but most of the > links (which are now relative) should work. I haven't tried it under > traditional cgi yet (just wsgiref) so I may have broken things there. > > If you give it a try, let me know how it goes! Thank you for the hard work, but now I have to enter admin password every time I click on the admin categories. I use apache ProxyPass under http://server/mailman/admin and the cookie specifies its path as /admin which is different from the current path as viewed from the browser through the reverse proxy. :-( -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
[Mailman-Developers] HTTPRunner.py (was Re: LMTPRunner.py)
Barry Warsaw wrote: > Actually, something that emf mentioned a while ago: we should adapt > the current web interface to WSGI and then perhaps use > wsgiref.simple_server(): > > http://www.python.org/doc/current/lib/module-wsgiref.simpleserver.html Hi, I've checked in HTTPRunner.py using this simple server and wsgi_app.py for wrapping mailman cgi in wsgi environment. I fear I may be doing wrong things but it should be a proof that right things can be done. There are some glitches in admin authentication interfaces: e.g., if I want to enter password in http://server/mailman/admin/listname, then I'm redirected to http://server/admin/admin/listname. Authentication at http://server/mailman/admin/listname/general works but the redirected URL becomes http://server/mailman/admin/listname/admin/listname/general. > > Of course, this comes with Python 2.5, but I believe is available as > a distutils package for Python 2.4. The advantage is not only that > we can do away with the setgid stuff, but that our web interface > (even if nothing else is rewritten) can be dropped into any WSGI > compliant framework. In theory. I haven't actually tried any of > that yet, but currently that's the directly I'm thinking 2.2 should > move to. > > (But yes, that does probably mean we could include a > wsgiref.simple_server()-based runner of sorts, although that's going > to be a bit of a misnomer :) > > - -Barry > Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] LMTPRunner.py
Hi Barry,
>
> I took a look at LMTPRunner.py today, and it looked pretty good. I
> don't think it was quite RFC 2033 compliant though. One thing it
> needed to do was return a status code for every RCPT TO recipient.
>
I've looked over that part. ;-)
> Take a look at r8050. I've fixed the status codes and also done a
> bunch of other refactoring. Note that I haven't yet tried to hook
> this up to a real Postfix (or other LMTP client), but it seems to do
> the right thing when you telnet to localhost:8025. Give it a try and
> let me know what you think. I plan on testing Postfix integration,
> perhaps tomorrow.
It's working just fine on my test environment.
>
> This definitely shows a lot of promise. I will probably hold off on
> updating the MaildirRunner for now, to see how far we can take LMTP
> delivery, and whether an smtpd.py-based server can hold up. Great work!
>
Now wonder if we can put a MailmanHTTPRunner(Server) in mailman-2.2.
This should completely get rid of the setgid problem in the installation.
I've tested putting this script in /usr/local/mailman ()
directory and get my browser pointing to
http://server:8000/Mailman/Cgi/listinfo.py. Unfortunately, the
BaseHTTPServer in the Python distribution is based on syncronous
TCPServer, thus it cannot handle simultaneous connections. There are
threading and forking TCPServers in the SocketServer module and we may
be able to use them to compose a customized Mailman HTTP Server.
-
import paths # Put paths.py in /usr/local/mailman directory
import BaseHTTPServer
import CGIHTTPServer
from Mailman.configuration import config
config.load()
class MailmanHTTPRequestHandler(CGIHTTPServer.CGIHTTPRequestHandler):
have_fork = 0
have_popen2 = 0
have_popen3 = 0
cgi_directories = ['/Mailman/Cgi']
def test(HandlerClass=MailmanHTTPRequestHandler,
ServerClass=BaseHTTPServer.HTTPServer):
CGIHTTPServer.test(HandlerClass, ServerClass)
if __name__ == '__main__':
test()
-
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] pipe-to-prog/maidir/lmtp performance
Hi, Barry Warsaw wrote: > > When you feel confident about your lmtp implementation, go ahead and > check it in (probably in Mailman/bin/lmtp.py with hooks for mmshell > - -- or I can do the latter). I think at this early date we should > make both LMTP and Maildir delivery possible, then we'll try to get > real-world feedback from users as to which we should ultimately > recommend. > I've commited it as LMTPRunner.py because it should be restarted by mailmanctl. >How much work is your LMTP > implementation doing when it receives the message? It does the same thing as MaildirRunner does, although it doesn't do saving the misdirected messages but only to report them in error log. > If that's the case, there's some common constant amount of work being > done and I'm just wondering how efficient the LMTP part will be. My impression is that it is almost the same as Maildir delivery. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
[Mailman-Developers] pipe-to-prog/maidir/lmtp performance
Hi, > An smtpd.py based LTMP server could > provide an interesting proof of concept though. I've almost finished writing this primitive LMTP server. Here is a result of experiment of posting 100 messages to a list and measuring arriving/leaving times on my laptop coLinux (Debian) with Postfix-2.1.5/Python2.4. Time recording is based on the message header and mail.log, so it is a very rough experiment. MTA:In MTA:Out MM:Out sec program: first 08:56:49 08:56:51 08:56:53 4 last 08:56:54 08:57:27 08:57:38 44 sec 5 36 49 maildir: first 08:48:13 08:48:14 08:48:16 3 last 08:48:19 08:48:19 08:48:29 10 sec 65 16 lmtp: first 09:12:26 09:12:26 09:12:27 1 last 09:12:31 09:12:32 09:12:41 10 sec 56 15 With the current default method of invoking mailman post program and pipelineing takes 49 seconds for the last 100th message to reach the list member (a local user), while maildir and lmtp interface reduce this time to 15 or 16 seconds. You can also see most of the difference occured in MTA's In and Out, which means execution of mailman post program is the most heavy load. Also, maildir and lmtp passing of message from MTA to mailman is a relatively small task than the processing the list message like cooking headers and appending footers and all like those. Conclusion: Maildir or LMTP will not likely be a bottleneck. Cheers, -- Tokio Kikuchi [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8041] trunk/mailman/Mailman
Barry Warsaw wrote: > Other than that, we'd need a reliable standards-compliant LMTP server > written in Python (and no, smtpd.py- or Twisted-based versions are > not acceptable ;). Why no smtpd.py ? There is a MailmanProxy Object in the code which was written by you, Barry. Any SMTP server can become a LMTP server IIRC. http://docs.python.org/lib/node624.html -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8043] trunk/mailman/Mailman
Hi Barry and all, I've checked in this patch today. Barry, please fix or backout them if you don't like them. It looked like that MaildirRunner.py couldn't deal with the list name like 'mailman-users', so I rewrote it with a primitive method instead of using the re module. One problem: I manage a list called '[EMAIL PROTECTED]'; this can't go well with this method. Isn't it time to get rid of the -admin address in mailman-2.2? ;-) [EMAIL PROTECTED] wrote: > Revision: 8043 > http://svn.sourceforge.net/mailman/?rev=8043&view=rev > Author: tkikuchi > Date: 2006-09-28 00:54:21 -0700 (Thu, 28 Sep 2006) > > Log Message: > --- > Here are the patches needed in order to create new lists on my test > installation. I've tested four cases of combination of > POSTFIX_STYLE_VIRTUAL_DOMAINS (Any/None) and USE_MAIL_DIR (Yes/No). > Also, I've added POSTFIX_VIRTUAL_SEPARATOR = '_at_' for unique mapping of > local part in the virtual-mailman/aliases files. > > Modified Paths: > -- > trunk/mailman/Mailman/Defaults.py.in > trunk/mailman/Mailman/MTA/Postfix.py > trunk/mailman/Mailman/MailList.py > trunk/mailman/Mailman/Queue/MaildirRunner.py -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-Users] OS X & Mailman & Python
> In summary my preferences would be: > > Mailman 2.1.x supported on Python 2.3, 2.4, and 2.5. Drop support > for Python 2.1 and 2.2. We've done this accidentally in Mailman > 2.1.9, so let's make it official. > > Mailman 2.2 supported on Python 2.4 and 2.5. +1 -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8041] trunk/mailman/Mailman
[EMAIL PROTECTED] wrote:
> Revision: 8041
> http://svn.sourceforge.net/mailman/?rev=8041&view=rev
> Author: bwarsaw
> Date: 2006-09-25 00:53:58 -0700 (Mon, 25 Sep 2006)
>
> Log Message:
> ---
> Another milestone: you can now post to lists. Converted the following to use
> the new configuration object: admin, admindb, bounces, confirm, inject, join,
> leave, owner, post, request, unshunt, version.
>
> Also change MailList.GetScriptURL() to return the list's fully qualified name
> in links.
>
I've tested a bit.
Postfix.py: got duplicate warning while creating virtual-mailman.
Shouldn't we include hostname in aliases? Otherwise, true virtual
hosting breaks.
MailList.py: got error when name is None. Looks like full_path is
[EMAIL PROTECTED] order. Is this name + '@' + self.host_name?
I needed this patch to create new lists:
[EMAIL PROTECTED]:~/src/svn.trunk$ svn diff Mailman
Index: Mailman/MTA/Postfix.py
===
--- Mailman/MTA/Postfix.py (revision 8041)
+++ Mailman/MTA/Postfix.py (working copy)
@@ -142,8 +142,9 @@
print >> fp, '# CREATED:', time.ctime(time.time())
# Now add all the standard alias entries
for k, v in makealiases(mlist):
+fqdnaddr = '[EMAIL PROTECTED]' % (k, hostname)
# Format the text file nicely
-print >> fp, mlist.fqdn_listname, ((fieldsz - len(k)) * ' '), k
+print >> fp, fqdnaddr, ((fieldsz - len(k)) * ' '), k
# Finish the text file stanza
print >> fp, '# STANZA END:', listname
print >> fp
Index: Mailman/MailList.py
===
--- Mailman/MailList.py (revision 8041)
+++ Mailman/MailList.py (working copy)
@@ -287,14 +287,17 @@
os.path.join(config.LOCK_DIR, name or '') + '.lock',
lifetime=config.LIST_LOCK_LIFETIME)
# XXX FIXME Sometimes name is fully qualified, sometimes it's not.
-if '@' in name:
-self._internal_name, self.host_name = name.split('@', 1)
-self._full_path = os.path.join(config.LIST_DATA_DIR, name)
-else:
-self._internal_name = name
-self.host_name = config.DEFAULT_EMAIL_HOST
-self._full_path = os.path.join(config.LIST_DATA_DIR,
- self.host_name + '@' + name)
+ if name:
+if '@' in name:
+self._internal_name, self.host_name = name.split('@', 1)
+self._full_path = os.path.join(config.LIST_DATA_DIR, name)
+else:
+self._internal_name = name
+self.host_name = config.DEFAULT_EMAIL_HOST
+self._full_path = os.path.join(config.LIST_DATA_DIR,
+ self.host_name + '@' + name)
+ else:
+ self._full_path = ''
# Only one level of mixin inheritance allowed
for baseclass in self.__class__.__bases__:
if hasattr(baseclass, 'InitTempVars'):
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8036]trunk/mailman/Mailman/loginit.py
Mark, > > The problem with calling config.load() from loginit is I think it will > override the loading of a alternate config which may have been > specified as a command line option for those commands that support it > (at least the ones that do logging too). > Looks like you are right. I've backed out the last change. Well, I installed coLinux on my lap top and was testing if I can debug mailman while travelling. ;-) -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Patches in mandriva package
>> http://sourceforge.net/tracker/index.php? >> func=detail&aid=1556858&group_id=103&atid=300103 >> >> I think I will commit in the Release-2.1-maint branch and include >> in the >> 2.1.9 final release. I appreciate anyone can review the patch. > > Let's wait for 2.1.10, because otherwise we're really going to need > another release candidate and another week or so of testing. Oh, yes. I understand. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] Patches in mandriva package
Hi, Sorry that I was unable to respond. Barry Warsaw wrote: > On Sep 9, 2006, at 10:09 AM, Guillaume Rousse wrote: > >> I'd like to use this occasion to drop a maximum of patches we still >> have: >> - is 2.1.9 still vulnearble to CVE-2005-3573 ? I didn't found any >> reference to it in the release notes, and the patch [1] still apply > > This is the first I've seen of this CVE, but it sounds like bugs that > have been addressed in the email package. This is mentioned in the NEWS of version 2.1.7. - A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has been solved in Mailman 2.1.6, there may be more cases where ToDigest.send_digests() can block regular delivery. We put the send_digests() calling part in a try/except clause and leave a message in the error log if something happened in send_digests(). Daily call of cron/senddigests will provide more detail to the site administrator. Therefore, 2.1.9 is also not vulnerable. CVE-2005-3573 is a false (delayed) alert. -- Tokio Kikuchi [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [7965] branches/Release_2_1-maint/mailman
Hi Barry, Barry Warsaw wrote: > On Aug 4, 2006, at 8:21 AM, [EMAIL PROTECTED] wrote: > >> Revision: 7965 >> Author: tkikuchi >> Date: 2006-08-04 05:20:33 -0700 (Fri, 04 Aug 2006) >> ViewCVS: http://svn.sourceforge.net/mailman/?rev=7965&view=rev >> >> Log Message: >> --- >> Language files update. New languages: Arabic, Vietnamese. >> > > Hi Tokio! Were you planning on porting these changes to the trunk, > or should I? > I think I've done it. Shall I start releasing process of 2.1.9 this month? I think I can do it because our university entered in the summer vacation. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] SoC: status update
emf wrote: > http://wiki.list.org/display/DEV/Summer+of+Code > > Gentlebeings, > > I have updated the summer of code page above to indicate my current > progress and record the synthesis of the opinions I have received so far. > > Thank you for the excellent feedback you've provided so far; don't be > shy about continuing, either here or on the wiki. > > ~ethan fremen Hi Ethan, Since you are working on Web Interface, I have an important suggestion/request on the charset we use. I think we should use 'UTF-8' exclusively on WUI. We can eliminate many problems we have on current web pages including the pipermail archive, while current language-charset database should be retained for email message usage. Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ ___ 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
[Mailman-Developers] logger umask
Hi,
I think our new logger should set group writable to the new logs. I
tried a fresh install and get cgi error after mailmanctl start /
mailmanctl errot after cgi execution, vice versa.
The patch should look like this:
Index: Mailman/loginit.py
===
--- Mailman/loginit.py (revision 7892)
+++ Mailman/loginit.py (working copy)
@@ -103,6 +103,8 @@
# There was also a 'debug' logger, but that was mostly unused, so
instead
# we'll use debug level on existing loggers.
#
+# First set umask because both mailman/www write logs
+oumask = os.umask(002)
# Start by creating a common formatter and the root logger.
formatter = logging.Formatter(fmt=FMT, datefmt=DATEFMT)
log = logging.getLogger('mailman')
@@ -120,6 +122,8 @@
_handlers.append(handler)
handler.setFormatter(formatter)
log.addHandler(handler)
+# restore original umask
+ os.umask(oumask)
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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
Re: [Mailman-Developers] Problems with Vietnamese translation
Hi Mark, > > I tested this and it seems to work fine whether or not mailman.po has a > space after the '#:'. > > Tokio, > > Do you think we should go ahead and commit this on the trunk? > Thanks for this patch. I've committed this on the trunk slightly differently, though. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [7858] trunk/mailman
Brad Knowles wrote: > At 11:59 PM -0400 2006-04-23, Barry Warsaw wrote: > > >> One thing we may have to do though is set the log file encoding. What >> do you think about that? > > > Log file encoding? I'm not sure I understand what you mean. I > can think of a few different ways that could be interpreted, and I > don't know for sure that any of them are the meaning you intended to > convey. > > Could you clarify and/or elaborate? > Well, it should be a mess. :-( Consider mailman get a spam from a foreign country and caused an error. Mailman may complain UnicodeDecodeError and spew an excerpt containing unknown charset string. This is certainly not printable if there is no encoding which means only us-ascii is accepted for the log file. Even if you determine the charset for your language (eg. euc-jp for japanese), you still get error for a chinese spam. It may be useful if the log output use 'replace' feature of encode() method. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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
Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [7858] trunk/mailman
Hi Barry, I had some hours playing with the new svn trunk. (I was a little bit busy because our academic year begins April.) [EMAIL PROTECTED] wrote: > Revision: 7858 > Author: bwarsaw > Date: 2006-04-16 21:08:17 -0700 (Sun, 16 Apr 2006) > ViewCVS: http://svn.sourceforge.net/mailman/?rev=7858&view=rev > > Log Message: > --- > - Convert all logging to Python's standard logging module. Get rid of all > traces of our crufty old Syslog. Most of this work was purely mechanical, > except for: I get this for a fresh install of svn trunk. You may have old install remained, if you haven't experienced this. % bin/mailmanctl start Traceback (most recent call last): File "bin/mailmanctl", line 112, in ? from Mailman.Logging.Syslog import syslog ImportError: No module named Logging.Syslog Also, if you send SIGHUP to reopen the logs, only the last reopen messages is recorded because each runners try to reopen the log file. We may have to restart qrunners if mailmanctl receive SIGHUP and it has started new log files. We may also utilize the backupCount feature for log rotation (intruducing LOG_BACKUP_COUNT in Defaults.py). > > 1) Initializing the loggers. For this, there's a new module > Mailman/loginit.py (yes all modules from now on will use PEP 8 > names). We can't call this 'logging.py' because that will > interfere with importing the stdlib module of the same name (can > you say Python 2.5 and absolute imports?). > > If you want to write log messages both to the log file and to > stderr, pass True to loginit.initialize(). This will turn on > propagation of log messages to the parent 'mailman' logger, which > is set up to print to stderr. This is how bin/qrunner works when > not running as a subprocess of mailmanctl. > > 2) The driver script. I had to untwist the StampedLogger stuff and > implement differently printing exceptions and such to log/error > because standard logging objects don't have a write() method. So > we write to a cStringIO and then pass that to the logger. > > 3) SMTPDirect.py because of the configurability of the log messages. > This required changing SafeDict into a dict subclass (which is > better than using UserDicts anyway -- yay Python 2.3!). It's > probably still possible to flummox things up if you change the > name of the loggers in the SMTP_LOG_* variables in mm_cfg.py. > However, the worst you can do is cause output to go to stderr and > not go to a log file. > > Note too that all entry points into the Mailman system must call > Mailman.loginit.initialize() or the log output will go to stderr > (which may occasionally be what you want). Currently all CGIs and > qrunners should be working properly. > > I wish I could have tested all code paths that touch the logger, but > that's infeasible. I have tested this, but it's possible that there > were some mistakes in the translation. > > - Mailman.Bouncers.BounceAPI.Stop is a singleton, but not a class > instance any more. > > - True/False code cleanup, PEP 8 import restructuring, whitespace > normalization, and copyright year updates, as appropriate. > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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
[Mailman-Developers] RELEASED: Mailman 2.1.8
On behalf of the development team, I'm pleased to announce the release of GNU Mailman 2.1.8. In this release, we have fixed a cross-site scripting security bug in the previous release (CVE-2006-1712), integrated a new version of email library (email-2.5.7), and added bounce processing supports for number of sites and MUAs. It is highly recommended that all sites using 2.1.7 and before should update to this release. Mailman is free software for managing email mailing lists and e-newsletters. For more information, see: http://mailman.sourceforge.net/ For links to download the Mailman 2.1.8 source tarball, see: http://sourceforge.net/project/showfiles.php?group_id=103 (Note that uploading to the mirror sites may be delayed.) -- Tokio Kikuchi ___ 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
[Mailman-Developers] Released: Mailman 2.1.8 release candidate
Hi all, Mailman 2.1.8rc1 was released for the final test of 2.1.8. Important: This is not only a release candidate but also include a fix for a cross-site scripting bug found in 2.1.7. All sites running previous versions are adviced to upgrade to 2.1.8(rc1). I am going to release the final by the next weekend if nothing serious happens. Please download it from Sourceforge file area: http://sourceforge.net/project/showfiles.php?group_id=103 Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.8rc1 (07-Apr-2006) Security - A cross-site scripting hole in the private archive script of 2.1.7 has been closed. Thanks to Moritz Naumann for its discovery. Bug fixes and other patches - Bouncers support added: 'unknown user', Microsoft SMTPSVC, Prodigy.net and several others. - Updated email library to 2.5.7 which will encode payload into qp/base64 upon setting. This enabled backing out the scrubber related patches including 'X-Mailman-Scrubbed' header in 2.1.7. - Fix SpamDetect.py potential hold/reject loop problem. - A warning message from email package to the stderr can cause error in Logging because stderr may be detached from the process during the qrunner run. We chose not to output errors to stderr but to the logs/error if the process is running under mailmanctl subprocess. - DKIM header cleansing was separated from Cleanse.py and added to -owner messages too. - Fixes: Lose Topics when go directly to topics URL (1194419). UnicodeError running bin/arch (1395683). edithtml.py missing import (1400128). Bad escape in cleanarch. Wrong timezone in list archive index pages (1433673). bin/arch fails with TypeError (1430236). Subscription fails with some Language combinations (1435722). Postfix delayed notification not recognized (863989). 2.1.7 (VERP) mistakes delay notice for bounce (1421285). show_qfiles: 'str' object has no attribute 'as_string' (147). Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off (1275856). Miscellaneous - Brad Knowles' mailman daily status report script updated to 0.0.16. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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
[Mailman-Developers] Released: Mailman 2.1.8b1
Hi Mailman-Users, -Developers and -i18ners, Mailman 2.1.8b1 was released for beta test. Talks are going around on the start of 2.2 after the release of 2.1.8 the final of 2.1-maint branch. I really want to call this final than beta but we should take careful steps. Please download it from Sourceforge file area: http://sourceforge.net/project/showfiles.php?group_id=103 Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.8b1 (23-Mar-2006) Bug fixes and other patches - Bouncers support added: 'unknown user', Microsoft SMTPSVC, Prodigy.net and several others. - Updated email library to 2.5.7 which will encode payload into qp/base64 upon setting. This enabled backing out the scrubber related patches including 'X-Mailman-Scrubbed' header in 2.1.7. - Fix SpamDetect.py potential hold/reject loop problem. - A warning message from email package to the stderr can cause error in Logging because stderr may be detached from the process during the qrunner run. We chose not to output errors to stderr but to the logs/error if the process is running under mailmanctl subprocess. - DKIM header cleansing was separated from Cleanse.py and added to -owner messages too. - Fixes: Lose Topics when go directly to topics URL (1194419). UnicodeError running bin/arch (1395683). edithtml.py missing import (1400128). Bad escape in cleanarch. Wrong timezone in list archive index pages (1433673). bin/arch fails with TypeError (1430236). Subscription fails with some Language combinations (1435722). Postfix delayed notification not recognized (863989). 2.1.7 (VERP) mistakes delay notice for bounce (1421285). show_qfiles: 'str' object has no attribute 'as_string' (147). Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off (1275856). Miscellaneous - Brad Knowles' mailman daily status report script updated to 0.0.16. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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
[Mailman-Developers] Mailman 2.1.8a1 (was Released: Mailman 2.1.7a1)
Ops! Sorry for the typo in the subject. :-( Tokio Kikuchi wrote: > Hi Developers and i18ners, > > Mailman 2.1.8a1 was released for alpha test and i18n translations. > Unfortunately, SF file upload is currently down, so I've put up the tar > ball and the GPG signature on my Japanese Mailman site. > > gzipped tar file ... http://mm.tkikuchi.net/mailman-2.1.8a1.tgz > GPG signature ... http://mm.tkikuchi.net/mailman-2.1.8a1.tgz.sig > > And, here is the excerpts from NEWS file. > > Cheers, > > Tokio > --- > Here is a history of user visible changes to Mailman. > > 2.1.8a1 (10-Mar-2006) > > Bug fixes and other patches > > - Bouncers support added: 'unknown user', Microsoft SMTPSVC, Prodigy.net > and several others. > > - Updated email library to 2.5.7 which will encode payload into > qp/base64 > upon setting. This enabled backing out the scrubber related patches > including 'X-Mailman-Scrubbed' header in 2.1.7. > > - Fix SpamDetect.py potential hold/reject loop problem. > > - A warning message from email package to the stderr can cause error > in Logging because stderr may be detached from the process during > the qrunner run. We chose not to output errors to stderr but to > the logs/error if the process is running under mailmanctl subprocess. > > - DKIM header cleansing was separated from Cleanse.py and added to > -owner messages too. > > - Fixes: Lose Topics when go directly to topics URL (1194419). > UnicodeError running bin/arch (1395683). edithtml.py missing import > (1400128). Bad escape in cleanarch. Wrong timezone in list archive > index pages (1433673). bin/arch fails with TypeError (1430236). > Subscription fails with some Language combinations (1435722). > Postfix delayed notification not recognized (863989). 2.1.7 (VERP) > mistakes delay notice for bounce (1421285). show_qfiles: 'str' > object has no attribute 'as_string' (147). > > Miscellaneous > > - Brad Knowles' mailman daily status report script updated to 0.0.16. > > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Released: Mailman 2.1.7a1
Hi Developers and i18ners, Mailman 2.1.8a1 was released for alpha test and i18n translations. Unfortunately, SF file upload is currently down, so I've put up the tar ball and the GPG signature on my Japanese Mailman site. gzipped tar file ... http://mm.tkikuchi.net/mailman-2.1.8a1.tgz GPG signature ... http://mm.tkikuchi.net/mailman-2.1.8a1.tgz.sig And, here is the excerpts from NEWS file. Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.8a1 (10-Mar-2006) Bug fixes and other patches - Bouncers support added: 'unknown user', Microsoft SMTPSVC, Prodigy.net and several others. - Updated email library to 2.5.7 which will encode payload into qp/base64 upon setting. This enabled backing out the scrubber related patches including 'X-Mailman-Scrubbed' header in 2.1.7. - Fix SpamDetect.py potential hold/reject loop problem. - A warning message from email package to the stderr can cause error in Logging because stderr may be detached from the process during the qrunner run. We chose not to output errors to stderr but to the logs/error if the process is running under mailmanctl subprocess. - DKIM header cleansing was separated from Cleanse.py and added to -owner messages too. - Fixes: Lose Topics when go directly to topics URL (1194419). UnicodeError running bin/arch (1395683). edithtml.py missing import (1400128). Bad escape in cleanarch. Wrong timezone in list archive index pages (1433673). bin/arch fails with TypeError (1430236). Subscription fails with some Language combinations (1435722). Postfix delayed notification not recognized (863989). 2.1.7 (VERP) mistakes delay notice for bounce (1421285). show_qfiles: 'str' object has no attribute 'as_string' (147). Miscellaneous - Brad Knowles' mailman daily status report script updated to 0.0.16. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-Users] any info onthisreportedexploit?
Mark Sapiro wrote: >>Mark Sapiro wrote: >> >> >>>++ if not t[7]: >>>++ t = t[:7] + (1,) +t[8:] >> >>On second thought, that should be >> >> if t and not t[7] >> t = t[:7] + (1,) +t[8:] > > > I seem to be having a lot of trouble with this. Make that > > if t and not t[7]: > t = t[:7] + (1,) +t[8:] > > I changed the patch including this one. Please check it again. https://sourceforge.net/tracker/index.php?func=detail&aid=1419490&group_id=103&atid=300103 -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-Users] any info on this reported exploit?
Mark Sapiro wrote: > Tokio Kikuchi wrote: > >>We may have to patch against this email package parsedate bug. >>I've just uploaded a patch on SF tracker. Please someone review this >>before I commit in the CVS (this weekend, maybe). > > > I have looked at the patch in the tracker. > > Caveat: I haven't tested anything - this is just based on my reading. > > I think the patch is good. The issue I see is that Scrubber.py may not > currently be doing the right thing if parsedate() returns None. > > Consider the attached patch for Scrubber.py in addition to the patch in > the tracker. Well, the logic may be unclear but calculate_attachment_dir() tries again to guess the real date of message arrival because it may be called from bin/arch. I think the code should be cleaned up but since we are now dealing with the email parsedate bug and it should be safe to limit our patch to this purpose. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-Users] any info on this reportedexploit?
Mark Sapiro wrote: > Tokio Kikuchi wrote: > >>We may have to patch against this email package parsedate bug. >>I've just uploaded a patch on SF tracker. Please someone review this >>before I commit in the CVS (this weekend, maybe). >>https://sourceforge.net/tracker/?func=add&group_id=103&atid=300103 > > > Above URI is not correct :-( > > See > <https://sourceforge.net/tracker/index.php?func=detail&aid=1419490&group_id=103&atid=300103> > Oops, sorry! :-P -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-Users] any info on this reported exploit?
Tokio Kikuchi wrote: >> http://www.securityfocus.com/bid/16248/discuss >> GNU Mailman Large Date Data Denial Of Service Vulnerability >> GNU Mailman is prone to a denial of service attack. This issue affects >> the >> email date parsing functionality of Mailman. (snip) >> 06.3.18 CVE: CVE-2005-4153 (snip) > > Mailman-2.1.7 is not vulnerable to this issue. > We may have to patch against this email package parsedate bug. I've just uploaded a patch on SF tracker. Please someone review this before I commit in the CVS (this weekend, maybe). https://sourceforge.net/tracker/?func=add&group_id=103&atid=300103 Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Put admin_member_chunksize in GUI
Mark Sapiro wrote: > Is there any reason to not put admin_member_chunksize in the GUI? > > It doesn't do the job requested in > <http://sourceforge.net/tracker/index.php?func=detail&aid=782436&group_id=103&atid=350103>, > but it helps. > > Is there a fear that some unsuspecting list owner will set it too big? > No reason, maybe. But, I just don't want to add a new language catalog entry and re-generate whole .po files for 2.2 now. :-( -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Scrubber mungs quoted-printable revisited.
Hi Mark,
Mark Sapiro wrote:
> Recently, I looked in more detail at the actual set_payload() method in
> the email library and I have at least a vague understanding of the
> problem. The problem and my understanding are reported at
> <http://sourceforge.net/tracker/?func=detail&aid=1409455&group_id=5470&atid=105470>.
> I have suggested a patch there which I call a 'Hint at possible fix'.
> This patch could be applied in Scrubber.py.
>
It's nice that the problem was tracked down. Thank you!
> The patch to Scrubber.py would add to the end of the
>
> def replace_payload_by_text(msg, text, charset):
>
> definition making the whole definition
>
> def replace_payload_by_text(msg, text, charset):
> # TK: This is a common function in replacing the attachment and the
> main
> # message by a text (scrubbing). Also, add a flag indicating it
> has been
> # scrubbed.
> del msg['content-type']
> del msg['content-transfer-encoding']
> msg.set_payload(text, charset)
> msg['X-Mailman-Scrubbed'] = 'Yes'
> if msg.get('content-transfer-encoding') == 'quoted-printable':
> cset = msg.get_charset()
> if cset:
> msg._payload = cset.body_encode(msg._payload)
> msg._charset = None
>
I'm rather uneasy with _varname attribute is manupulated everywhere in
the application code. Maybe we should override the email.Message
behaviour by overriding in Mailman.Message. Also I will add 'base64' in
encoding check and back out the patches related to the 'X-Mailman-Scruber'.
>
> The advantage to doing this in Scrubber.py and unconditionally setting
> the decode flag for subsequent get_payload() calls is it makes the
> whole process insensitive to whether or not or when Python email bug #
> 1409455 is fixed. If the bug is fixed, the payload will be encoded and
> msg.get_charset() above will return None so the payload won't be
> encoded a second time. The additional code above can be removed at
> some point after we're sure the email library used by Mailman is fixed.
>
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] [ mailman-Bugs-1416853 ] Jan 14 change toHandlers/SpamDetect.py isincomplete
Mark Sapiro wrote: > Tokio Kikuchi wrote: > >>OK, Barry. I've come up with this patch (for the current CVS). >>If its OK, I want to start up for the release of 2.1.8a1. > > > > The pass through of the 'hold' action if the message is to -owner seems > right to me, but discarding instead of rejecting a 'reject' action if > the message is to -owner seems wrong. Well, then it should be passed. Rejection makes it another loop of rejection notices if an initial poster forges the From: address as list-owner. Yes, I tested this. Nothing could stop this if the mailman qrunner wasn't stopped. (Maybe growing size of rejection notice would hit the MTA limit.) > > I think we should not change the disposition for a 'reject' action. The > rule can be for lots of purposes, not just spam and if the owner has > configured the rule to reject the message, I don't think we should > discard it just because it is to -owner and not to the list. > > I have one idea for 2.1.8a1 before we wrap it up. I'll address that in > a separate post. > OK. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [ mailman-Bugs-1416853 ] Jan 14 change to Handlers/SpamDetect.py isincomplete
Barry Warsaw wrote:
> That seems right to me. It doesn't make any sense to hold a message
> ultimately destined for the list owner or moderator because those are
> the people who have to approve the message (what? so they can then read
> it again in their inbox?).
>
> If in response to a certain spam designation the owner destined message
> is discarded, that's fine. But it shouldn't be held, and rejecting spam
> is almost always a bad idea.
OK, Barry. I've come up with this patch (for the current CVS).
If its OK, I want to start up for the release of 2.1.8a1.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: SpamDetect.py
===
RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/SpamDetect.py,v
retrieving revision 2.3.2.11
diff -u -r2.3.2.11 SpamDetect.py
--- SpamDetect.py 14 Jan 2006 10:11:19 - 2.3.2.11
+++ SpamDetect.py 28 Jan 2006 02:01:34 -
@@ -102,15 +102,6 @@
if mo:
# we've detected spam, so throw the message away
raise SpamDetected
-# Before we go to header_filter_rules, we exclude internally generated
-# owner notification from checking, because 1) we collect headers from
-# all the attachments but this will cause matching the filter rule again,
-# and 2) list owners may want to check header name / value pair like
-# 'Precedence: bulk' which is also generated by mailman. Both will
-# cause loop of holding owner notification messages if the action is
-# set to 'hold'.
-if msgdata.get('toowner') and msg.get('x-list-administrivia') == 'yes':
-return
# Now do header_filter_rules
# TK: Collect headers in sub-parts because attachment filename
# extension may be a clue to possible virus/spam.
@@ -132,9 +123,18 @@
if action == mm_cfg.DISCARD:
raise Errors.DiscardMessage
if action == mm_cfg.REJECT:
+if msgdata.get('toowner'):
+# Don't send rejecting message if addressed
+# to '-owner'. We just discard here.
+raise Errors.DiscardMessage
raise Errors.RejectMessage(
_('Message rejected by filter rule match'))
if action == mm_cfg.HOLD:
+if msgdata.get('toowner'):
+# Don't hold '-owner' addressed message. We just
+# pass it here but list-owner can set this to be
+# discarded on the GUI if he wants.
+return
hold_for_approval(mlist, msg, msgdata, HeaderMatchHold)
if action == mm_cfg.ACCEPT:
return
___
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-users%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
Re: [Mailman-Developers] [Mailman-Users] Problems with uuencoded attachments
Barry Warsaw wrote:
> On Mon, 2006-01-16 at 09:25 +0900, Tokio Kikuchi wrote:
>
>
>>In usual mailman qrunner execs, stderr is logged into logs/errors. It
>>is the additional tee_to_real_stderr in LogStdErr() setting which wants
>>to print the error into real stderr.
>>
>>Isn't it safe to put the tee_to_real_stderr value 0 in bin/qrunner script ?
>
>
> Ideally, tee_to_real_stderr would be !AS_SUBPROC (i.e. tee when not
> running qrunner under mailmanctl). That would have to be done in main()
> after processing the command line arguments.
>
Yeah, I noticed that too and played around. How about this patch.
I assumed running qrunner independently is for debugging purpose and
quit redirecting stderr into logs/error.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: qrunner
===
RCS file: /cvsroot/mailman/mailman/bin/qrunner,v
retrieving revision 2.9.2.1
diff -u -r2.9.2.1 qrunner
--- qrunner 27 Aug 2005 01:40:16 - 2.9.2.1
+++ qrunner 16 Jan 2006 01:58:49 -
@@ -66,6 +66,9 @@
runner is required unless -l or -h is given, and it must be one of the names
displayed by the -l switch.
+
+Note also that this script should be started up from mailmanctl as a normal
+operation. It is only useful for debugging if it is run separately.
"""
import sys
@@ -84,8 +87,6 @@
# Flag which says whether we're running under mailmanctl or not.
AS_SUBPROC = 0
-LogStdErr('error', 'qrunner', manual_reprime=0)
-
def usage(code, msg=''):
@@ -212,6 +213,10 @@
if len(runners) == 0:
usage(1, _('No runner name given.'))
+# Before we startup qrunners, we redirect the stderr to mailman syslog.
+if AS_SUBPROC:
+LogStdErr('error', 'qrunner', manual_reprime=0, tee_to_real_stderr=0)
+
# Fast track for one infinite runner
if len(runners) == 1 and not once:
qrunner = make_qrunner(*runners[0])
___
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-users%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
Re: [Mailman-Developers] [Mailman-Users] Problems with uuencoded attachments
Barry Warsaw wrote:
> On Jan 14, 2006, at 9:59 PM, Tokio Kikuchi wrote:
>
>
>>Mark Sapiro wrote:
>>
>>
>>
>>>>File "/usr/lib/python2.3/uu.py", line 139, in decode
>>>> sys.stderr.write("Warning: %s\n" % str(v))
>>>>File "/usr/lib/mailman/Mailman/Logging/MultiLogger.py", line 45,
>>>>in write
>>>> _logexc(logger, msg)
>>>>File "/usr/lib/mailman/Mailman/Logging/Utils.py", line 22, in
>>>>_logexc
>>>> sys.__stderr__.write('Logging error: %s\n' % logger)
>>>>IOError: [Errno 32] Broken pipe
>>
>>>I think this could be fixed by changing
>>>"/usr/lib/mailman/pythonlib/email/Message.py", line 223 from
>>>uu.decode(StringIO(payload+'\n'), sfp)
>>>to
>>>uu.decode(StringIO(payload+'\n'), sfp,
>>>quiet=True)
>>
>>
>>There should be other chances that Python builtin modules spew
>>warnings to sys.stderr. How about this patch for Logging/Utils.py
>>to write these messages into syslog facility.
>
>
> The only problem is that currently Mailman does not use the syslog
> module, and I'm uncomfortable with adding it for this one situation
> (are there others?). We should definitely be passing the quiet flag
> to uu.decode(), but OTOH maybe we should also be testing whether
> sys.__stderr__ is detached and then redirecting that to logs/errors?
>
In usual mailman qrunner execs, stderr is logged into logs/errors. It
is the additional tee_to_real_stderr in LogStdErr() setting which wants
to print the error into real stderr.
Isn't it safe to put the tee_to_real_stderr value 0 in bin/qrunner script ?
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] [Mailman-Users] Problems with uuencoded attachments
Mark Sapiro wrote:
File "/usr/lib/python2.3/uu.py", line 139, in decode
sys.stderr.write("Warning: %s\n" % str(v))
File "/usr/lib/mailman/Mailman/Logging/MultiLogger.py", line 45, in write
_logexc(logger, msg)
File "/usr/lib/mailman/Mailman/Logging/Utils.py", line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 32] Broken pipe
I think this could be fixed by changing
"/usr/lib/mailman/pythonlib/email/Message.py", line 223 from
uu.decode(StringIO(payload+'\n'), sfp)
to
uu.decode(StringIO(payload+'\n'), sfp, quiet=True)
There should be other chances that Python builtin modules spew warnings
to sys.stderr. How about this patch for Logging/Utils.py to write these
messages into syslog facility.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: Utils.py
===
RCS file: /cvsroot/mailman/mailman/Mailman/Logging/Utils.py,v
retrieving revision 2.2.2.1
diff -u -r2.2.2.1 Utils.py
--- Utils.py27 Aug 2005 01:40:16 - 2.2.2.1
+++ Utils.py15 Jan 2006 02:50:11 -
@@ -16,12 +16,25 @@
import sys
import traceback
+import syslog
+import StringIO
+
+syslog.openlog('mailman', syslog.LOG_PID, syslog.LOG_MAIL)
def _logexc(logger=None, msg=''):
-sys.__stderr__.write('Logging error: %s\n' % logger)
-traceback.print_exc(file=sys.__stderr__)
-sys.__stderr__.write('Original log message:\n%s\n' % msg)
+try:
+sys.__stderr__.write('Logging error: %s\n' % logger)
+traceback.print_exc(file=sys.__stderr__)
+sys.__stderr__.write('Original log message:\n%s\n' % msg)
+except IOError:
+syslog.syslog(syslog.LOG_INFO, 'Logging error: %s\n' % logger)
+tbio = StringIO.StringIO()
+traceback.print_exc(file=tbio)
+syslog.syslog(syslog.LOG_INFO, tbio.getvalue())
+tbio.close()
+syslog.syslog(syslog.LOG_INFO, 'Original log message:\n%s\n' % msg)
+
def LogStdErr(category, label, manual_reprime=1, tee_to_real_stderr=1):
___
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-users%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
Re: [Mailman-Developers] Serious Archiving problem in 2.1.7
Thank you Mark. It looks like we reached the same conclusion.
One note: I prefer to use unicode() than decode() because the latter is
not supported in Python 2.1 and looks like fuzzy in declaring unicode
string (or else).
Mark Sapiro wrote:
> Tokio Kikuchi wrote:
>
>>At my first glance, it will only work for english lists in which the
>>replace parameter _(' at ') is the same both in unicode and ascii.
>>
>>I'll try to test and generate i18n patch today.
>
>
>
> I see the point. Unfortunately I only tested English and French and in
> French, _(' at ') translates to ' at '. Here is my suggestion for a
> revised patch (tested with en, es, fr and ja - I can't read the
> Japanese, but it 'looks' OK):
>
> --- f:/Mailman/mailman-2.1.7/Mailman/Archiver/HyperArch.py
> 2005-12-30 10:50:07.0 -0800
> +++ f:/test-mailman/Mailman/Archiver/HyperArch.py 2006-01-04
> 18:21:50.75000 -0800
> @@ -569,16 +569,21 @@
> if d['_message_id']:
> headers.append('Message-ID: %(_message_id)s')
> body = EMPTYSTRING.join(self.body)
> -if isinstance(body, types.UnicodeType):
> -body = body.encode(Utils.GetCharSet(self._lang), 'replace')
> +# MAS: Coerce the body to Unicode and replace any invalid
> characters.
> +langcset = Utils.GetCharSet(self._lang)
> +if not isinstance(body, types.UnicodeType):
> +body = body.decode(langcset, 'replace')
> if mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS:
> otrans = i18n.get_translation()
> try:
> i18n.set_language(self._lang)
> body = re.sub(r'([-+,.\w]+)@([-+.\w]+)',
> - '\g<1>' + _(' at ') + '\g<2>', body)
> + '\g<1>' + unicode(_(' at '), langcset)
> + + '\g<2>', body)
> finally:
> i18n.set_translation(otrans)
> +# MAS: Return body to character set of article.
> +body = body.encode(langcset, 'replace')
> return NL.join(headers) % d + '\n\n' + body + '\n'
>
> def _set_date(self, message):
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] Serious Archiving problem in 2.1.7
> At my first glance, it will only work for english lists in which the
> replace parameter _(' at ') is the same both in unicode and ascii.
>
> I'll try to test and generate i18n patch today.
>
Done.
I'll commit it in the CVS if no problems.
I really hate to read code in the Archiver directory. :-(
We'd rather develope new archiver from scratch for 2.2 (or 3.0). New
design should be in XHTML/CSS/UTF-8.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] Serious Archiving problem in 2.1.7
Barry Warsaw wrote: > On Wed, 2006-01-04 at 08:58 -0800, Mark Sapiro wrote: > > >>The purpose of this post is twofold. First, I would like independent >>review of the patch, as I still don't fully understand the reason for >>the error in all cases and the i18n implications. > > > I'll try to find some time to do this, if Tokio doesn't get to it first. Yeah, I'll look at it NOW. :-) > > >>Second, other than committing the patch to CVS, is there a mechanism >>for making it more widely visible. > > > Yes; we can make the patch available on the website and announce it on > mailman-announce. > > -Barry -- 菊地時夫 tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ 〒780-8520 高知大学理学部情報科学教室 ___ 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-users%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
Re: [Mailman-Developers] Serious Archiving problem in 2.1.7
Tokio Kikuchi wrote:
>>
>>>The purpose of this post is twofold. First, I would like independent
>>>review of the patch, as I still don't fully understand the reason for
>>>the error in all cases and the i18n implications.
>>
>>
>>I'll try to find some time to do this, if Tokio doesn't get to it first.
>
>
> Yeah, I'll look at it NOW. :-)
At my first glance, it will only work for english lists in which the
replace parameter _(' at ') is the same both in unicode and ascii.
I'll try to test and generate i18n patch today.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] RELEASED Mailman 2.1.7
John W. Baxter wrote: > > Shouldn't Mark Shapiro be recognized in the ACKNOWLEDGEMENTS file now? > Yes. Mark Sapiro _is_ in the ACKNOWLEDEMENTS. I've just added his name in top page of the http://mailman.sourceforge.net/ It'll appear in list.org and gnu mirror sites later. I just want to say my thanks to Mark again now, and I thank you all for your cooperation. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] RELEASED Mailman 2.1.7
I'm pleased to announce the release of GNU Mailman 2.1.7. This is a significant release, which includes security enhancement fixes, a new language (ia: Interlingua) support, a couple of new features, and many bug fixes. Mailman is free software for managing email mailing lists and e-newsletters. This release enhances the fixes for CAN-2005-0202 and CVE-2005-3573 which were fixed in mailman release 2.1.6, and reduces the chance of list admin privilege abuse. Because of these and other fixes, it is highly recommended that all sites update to 2.1.7. For more information, see: http://mailman.sourceforge.net/ For links to download the Mailman 2.1.7 source tarball, see: http://sourceforge.net/project/showfiles.php?group_id=103 Best regards and a happy new year! -- Tokio Kikuchi ___ 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-users%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
[Mailman-Developers] Mailman 2.1.7rc1 (was Re: [Mailman-Users] Released: Mailman 2.1.7b1)
Oops, Sorry for the typo in the message title. I mean Released: Mailman 2.1.7rc1 Release Candidate Tokio Kikuchi wrote: > Hi all, > > I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for > the violation of file name extension convention because I made a small > mistake when tagging the release number. I will be releasing 2.1.7 > final by December 31 if there is no problem. > > Please download it from SF or: > http://mm.tkikuchi.net/mailman-2.1.7rc1.tar.gz > > Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] [Mailman-Users] Released: Mailman 2.1.7b1
Hi all, I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for the violation of file name extension convention because I made a small mistake when tagging the release number. I will be releasing 2.1.7 final by December 31 if there is no problem. Please download it from SF or: http://mm.tkikuchi.net/mailman-2.1.7rc1.tar.gz Cheers, Tokio --- 2.1.7rc1 (24-Dec-2005) Security - The fix for CAN-2005-0202 has been enhanced to issue an appropriate message instead of just quietly dropping ./ and ../ from URLs. - A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has been solved in mailman-2.1.6, there may be more cases where ToDigest.send_digests() can block regular delivery. We put the send_digests() calling part in try - except clause and leave a message in the error log if something happened in send_digests(). Daily call of cron/senddigests will notify more detail to the site administrator. - List administrators can no longer change the user's option/subscription globally. Site admin can change these only if mm_cfg.ALLOW_SITE_ADMIN_COOKIES is set to Yes. - Script tag is disallowd in edithtml script. - Since probe message for the disabled users may reach unexpected persons, the password was excluded from sendProbe() and probe.txt. Note that the default value of VERP_PROBE has been set to `No' from 2.1.6., thus this change doesn't change the default behavior. New Features - Always remove DomainKey (and similar) headers (1287546) from messages sent to the list. - List owners can customize content filter behavior as not to collapse multipart/alternative to its first content. This allows HTML part to pass through after other content filtering is done. Internationalization - New language: Interlingua. Bug fixes and other patches - Defaults.py.in: SCRUBBER_DONT_USE_ATTACHMENT_FILENAME is set to True for safer operation. - Fix Scrubber.py mungs quoted-printable bug with introducing 'X-Mailman-Scrubbed' header for marking that the payload is scrubber-munged. The flag is referenced in ToDigest.py, ToArchive.py, Decorate.py and Archiver. Similar problem in ToDigest.py where the plain digest is generated is also fixed. - Fix Syslog.py to write quopri encoded message when it fail to write 8-bit characters. - Fix MTA/Postfix.py to check aliases group permission in check_perms and fix mailman-install document on this matter (1378270). - Fix private.py to go to the original URL after authorization (1080943). - Fix bounce log score messages to be more consistent. - Fix bin/remove_members to accept no arguments when both --fromall and --file= options are specified. - Change cgi-bin and mail wrapper "group not found" error message to be more descriptive of the actual problem. - Apply the list's ban_list to address changes and admin mass subscribe and invite and to confirmations/approvals of address changes, subscriptions and invitations. - Decode quoted-printable and base64 encoded parts before passing to HTML_TO_PLAIN_TEXT_COMMAND (1367783). - Remove Approve: header from post - treat as Approved: (1355707). - Stop removing line following Approve(d): line in body of post (1318883). - Remove Approve(d): from all text/* parts in addition the initial text/plain part. It still must be the first non-blank line in the first text/plain part or it won't be found or removed at all (1181161). - Log post in post log with true sender, not listname-bounces (1287921). - Correctly initialize and remember the list's default_member_moderation attribute in the web list creation page (1263213). - Add PEP263 charset in config_list output (1343100). - header_filter_rules get lost if accessed directly and needed authenti- cation by login page (1230865). - Obscure email when the poster doesn't set full name in 'From:' header. - Take preambles and epilogues into account when calculating message sizes for holding purposes (Mark Sapiro). - Logging/Logger.py unicode transform option (1235567). - bin/update crashes with bogus files (949117). - Bugs and patches: 1212066/1301983 (Date header in create/remove notice) ___ 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-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.p
Re: [Mailman-Developers] [Mailman-Users] filename too long error - stopping list
Hi Michael,
You can set Scrubber.py not to use the orginal filename in the message
by adding followin line in mm_cfg.py (mailman-2.1.6 and above).
SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = True
Developers,
May be we should set this default in Defaults.py.in in the next release
of 2.1.7. Thoughts?
Michael Rasmussen wrote:
> Resolved. The digest keeps a seperate mbox file at
> {MMDIR}lists/LISTNAME/digest.mbox removing the email from that location
> was the solution to my immediate problem.
>
> This does expose a DOS attack potential for MM lists. The too long
> attachment name needs to be handled in a more graceful manner.
>
> Michael Rasmussen wrote:
>
>>Update:
>>
>>I've found the offending message and purged it from the list archives,
>>purged it from the shunt files, and purged it from everywhere I could
>>find it.
>>
>>Yet the problem persists. So I'm looking for the temp file/mail area
>>where the file that contains this attachment may be found.
>>
>>
>>Michael Rasmussen wrote:
>>
>>>I have a list that was sent a file with an attachement with too long a
>>>name. (See error below) now all mail to the list is being shunted.
>>>
>>>the filename listed does not exist on my system. There is no file on my
>>>system with that name.
>>>The directory
>>>/var/lib/mailman/archives/private/rca-l/attachments/20051207/3d04c3a4 is
>>>empty.
>>>
>>>What do I need to do to resolve this problem?
>>>
>>>== Error message =
>>>Dec 22 06:08:46 2005 (2233) Uncaught runner exception: [Errno 36] File name
>>>too long:
>>>'/var/lib/mailman/archives/private/rca-l/attachments/20051207/3d04c3a4/iso-8859-1QThe_surface_of_the_SunA0_The_sun_has_a_rigid_iron_surfaceiso-8859-1Q_located_under_the_photosphere_that_is_revealed_by_satelliiso-8859-1Qte_imagery.A0_The_solar_surface_sits_beneath_the_suns_viiso-8859-1Qsible_photosphere_and_is_electrically_active..obj'
>>>Dec 22 06:08:46 2005 (2233) Traceback (most recent call last):
>>> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
>>>self._onefile(msg, msgdata)
>>> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
>>>keepqueued = self._dispose(mlist, msg, msgdata)
>>> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
>>> _dispose
>>>more = self._dopipeline(mlist, msg, msgdata, pipeline)
>>> File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
>>> _dopipeline
>>>sys.modules[modname].process(mlist, msg, msgdata)
>>> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in process
>>>send_digests(mlist, mboxfp)
>>> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in
>>> send_digests
>>>send_i18n_digests(mlist, mboxfp)
>>> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in
>>> send_i18n_digests
>>>msg = scrubber(mlist, msg)
>>> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 265, in process
>>>url = save_attachment(mlist, part, dir)
>>> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 447, in
>>> save_attachment
>>>fp = open(path, 'w')
>>>IOError: [Errno 36] File name too long:
>>>'/var/lib/mailman/archives/private/rca-l/attachments/20051207/3d04c3a4/iso-8859-1QThe_surface_of_the_SunA0_The_sun_has_a_rigid_iron_surfaceiso-8859-1Q_located_under_the_photosphere_that_is_revealed_by_satelliiso-8859-1Qte_imagery.A0_The_solar_surface_sits_beneath_the_suns_viiso-8859-1Qsible_photosphere_and_is_electrically_active..obj'
>>>
>>>Dec 22 06:08:46 2005 (2233) SHUNTING:
>>>1135258825.4376719+99568bcc1187c910d48aae8b9ae8f68ed3aa643b
>>>
>>>== Error message =
>>>--
>>>Michael Rasmussen, Portland Oregon
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
[Mailman-Developers] Released: Mailman 2.1.7b1
Hi all, I've just released Mailman 2.1.7b1 for beta test and i18n translations. I'm tempted to jump into RC because the 2.1-maint branch is so stable and 2.1.7 is mainly for bug fixes, but we need more translations before the final release. Please download it from SF or: http://mm.tkikuchi.net/mailman-2.1.7b1.tgz Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.7b1 (20-Dec-2005) Security - The fix for CAN-2005-0202 has been enhanced to issue an appropriate message instead of just quietly dropping ./ and ../ from URLs. - A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has been solved in mailman-2.1.6, there may be more cases where ToDigest.send_digests() can block regular delivery. We put the send_digests() calling part in try - except clause and leave a message in the error log if something happened in send_digests(). Daily call of cron/senddigests will notify more detail to the site administrator. - List administrators can no longer change the user's option/subscription globally. Site admin can change these only if mm_cfg.ALLOW_SITE_ADMIN_COOKIES is set to Yes. - Script tag is disallowd in edithtml script. - Since probe message for the disabled users may reach unexpected persons, the password was excluded from sendProbe() and probe.txt. Note that the default value of VERP_PROBE has been set to `No' from 2.1.6., thus this change doesn't change the default behavior. New Features - Always remove DomainKey (and similar) headers (1287546) from messages sent to the list. - List owners can customize content filter behavior as not to collapse multipart/alternative to its first content. This allows HTML part to pass through after other content filtering is done. Internationalization - New language: Interlingua. Bug fixes and other patches - Fix Scrubber.py mungs quoted-printable bug with introducing 'X-Mailman-Scrubbed' header for marking that the payload is scrubber-munged. The flag is referenced in ToDigest.py, ToArchive.py, Decorate.py and Archiver. Similar problem in ToDigest.py where the plain digest is generated is also fixed. - Fix Syslog.py to write quopri encoded message when it fail to write 8-bit characters. - Fix MTA/Postfix.py to check aliases group permission in check_perms and fix mailman-install document on this matter (1378270). - Fix private.py to go to the original URL after authorization (1080943). - Fix bounce log score messages to be more consistent. - Fix bin/remove_members to accept no arguments when both --fromall and --file= options are specified. - Change cgi-bin and mail wrapper "group not found" error message to be more descriptive of the actual problem. - Apply the list's ban_list to address changes and admin mass subscribe and invite and to confirmations/approvals of address changes, subscriptions and invitations. - Decode quoted-printable and base64 encoded parts before passing to HTML_TO_PLAIN_TEXT_COMMAND (1367783). - Remove Approve: header from post - treat as Approved: (1355707). - Stop removing line following Approve(d): line in body of post (1318883). - Log post in post log with true sender, not listname-bounces (1287921). - Correctly initialize and remember the list's default_member_moderation attribute in the web list creation page (1263213). - Add PEP263 charset in config_list output (1343100). - header_filter_rules get lost if accessed directly and needed authenti- cation by login page (1230865). - Obscure email when the poster doesn't set full name in 'From:' header. - Take preambles and epilogues into account when calculating message sizes for holding purposes (Mark Sapiro). - Logging/Logger.py unicode transform option (1235567). - bin/update crashes with bogus files (949117). - Bugs and patches: 1212066/1301983 (Date header in create/remove notice) ___ 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-users%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
Re: [Mailman-Developers] Scrubber mungs Quoted Printable
Hi Mark,
I've just committed my patch to this problem in 2.1 CVS branch. I used
this example and looks OK for both with and without
Content-Transfer-Encoding header.
Mark Sapiro wrote:
> The following is a transcript of a Python interactive session that
> illustrates the above problems with set_payload() and get_payload().
> This session is with Python 2.4.1, but exactly the same behavior
> occurs with 2.3.4 and 2.4.2.
>
> Python 2.4.1 (#1, May 27 2005, 18:02:40)
> [GCC 3.3.3 (cygwin special)] on cygwin
> Type "help", "copyright", "credits" or "license" for more information.
>
>>>>import email
>>>>
>>>>msg = email.message_from_file(open('plain2.eml'))
>>>>
>>>>print msg
>
>>From nobody Mon Nov 28 09:18:41 2005
> From: "Mark Sapiro" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: HTML - all
> Date: Sun, 27 Nov 2005 09:02:33 -0800
> MIME-Version: 1.0
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> How about just a line of stuff with some and a few words.
>
> X=91**2 (x is 91 squared)
>
>
>>>>del msg['content-type']
>>>>del msg['content-transfer-encoding']
>>>>msg.set_payload(str(msg.get_payload()), 'iso-8859-1')
>>>>
>>>>print msg
>
>>From nobody Mon Nov 28 09:18:41 2005
> From: "Mark Sapiro" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: HTML - all
> Date: Sun, 27 Nov 2005 09:02:33 -0800
> MIME-Version: 1.0
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
>
> How about just a line of stuff with some =3D=3D=3D=3D and a few words.
>
> X=3D91**2 (x is 91 squared)
>
>
>>>>print msg.get_payload()
>
>
> How about just a line of stuff with some and a few words.
>
> X=91**2 (x is 91 squared)
>
>
>>>>print msg.get_payload(decode=1)
>
>
> How about just a line of stuff with some == and a few words.
>
> X`**2 (x is 91 squared)
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] Encoding problem: Mailman bails during "Administrative requests"
ncanny.net admin(10012): REQUEST_URI: /mailman/admindb/wsa-talk admin(10012): HTTP_ACCEPT: text/xml, application/xml, application/xhtml+xml, text/html;q=0.9, image/png, image/jpeg, image/gif;q=0.2, text/plain;q=0.8, text/css, */*;q=0.1 admin(10012): GATEWAY_INTERFACE: CGI/1.1 admin(10012): REMOTE_PORT: 33142 admin(10012): HTTP_ACCEPT_LANGUAGE: en-us admin(10012): CONTENT_TYPE: application/x-www-form-urlencoded admin(10012): HTTP_ACCEPT_ENCODING: gzip,deflate,compress,identity admin(10012): UNIQUE_ID: Q5yWc8CoZOEAACbkeKA admin(10012): PATH_INFO: /wsa-talk == TRACEBACK END -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ Index: Syslog.py === RCS file: /cvsroot/mailman/mailman/Mailman/Logging/Syslog.py,v retrieving revision 2.3.2.1 diff -u -r2.3.2.1 Syslog.py --- Syslog.py 27 Aug 2005 01:40:16 - 2.3.2.1 +++ Syslog.py 15 Dec 2005 02:42:57 - @@ -55,7 +55,12 @@ # It's really bad if exceptions in the syslogger cause other crashes except Exception, e: msg = 'Bad format "%s": %s: %s' % (origmsg, repr(e), e) -logf.write(msg + '\n') +try: +logf.write(msg + '\n') +except UnicodeError: +# Python 2.4 may fail to write 8bit (non-ascii) characters +import quopri +logf.write(quopri.encodestring(msg) + '\n') # For the ultimate in convenience __call__ = write ___ 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-users%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
Re: [Mailman-Developers] Spam/Scam button
Hi, Dale Newfield wrote: > On Tue, 13 Dec 2005 19:38:46 -0600 "Brad Knowles" > <[EMAIL PROTECTED]> wrote: > >> Where would this button exist? Who would use it, and how? > > "forward it to a pre-specified email address." Not only is this suggestion > appropriate for this list, but I also think I recall a previous discussion > where the idea was hashed out. I would be willing to bet there's a patch > to implement it, because I think the result of the previous discussion was: > "Good idea, but too big a new feature for a patch-level release. Provide a > patch and people that want it can use it." > I think you are talking about: http://sourceforge.net/tracker/index.php?func=detail&aid=1008865&group_id=103&atid=300103 Hopefully, we will be back to the MAIN CVS tree for the development of mailman-2.2 after the release of 2.1.7. This should be the chance that the patch is integrated in the 2.2 release. Regards, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Released: Mailman 2.1.7a1
Hi Developers and i18ners, Mailman 2.1.7a1 was released for alpha test and i18n translations. Here is excerpts from NEWS file. I thank Mark Sapiro for significant contributions in bug-fixes and document/message brushups. Please fetch it from SF download sites or from http://mm.tkikuchi.net/mailman-2.1.7a1.tgz Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.7a1 (13-Dec-2005) Security - The fix for CAN-2005-0202 has been enhanced to issue an appropriate message instead of just quietly dropping ./ and ../ from URLs. - A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has been solved in mailman-2.1.6, there may be more cases where ToDigest.send_digests() can block regular delivery. We put the send_digests() calling part in try - except clause and leave a message in the error log if something happened in send_digests(). Daily call of cron/senddigests will notify more detail to the site administrator. - List administrators can no longer change the user's option/subscription globally. Site admin can change these only if mm_cfg.ALLOW_SITE_ADMIN_COOKIES is set to Yes. - Script tag is disallowd in edithtml script. - Since probe message for the disabled users may reach unexpected persons, the password was excluded from sendProbe() and probe.txt. Note that the default value of VERP_PROBE has been set to `No' from 2.1.6., thus this change doesn't change the default behavior. New Features - Always remove DomainKey (and similar) headers (1287546) from messages sent to the list. - List owners can customize content filter behavior as not to collapse multipart/alternative to its first content. This allows HTML part to pass through after other content filtering is done. Internationalization - New language: Interlingua. Bug fixes and other patches - Fix MTA/Postfix.py to check aliases group permission in check_perms and fix mailman-install document on this matter (1378270). - Fix private.py to go to the original URL after authorization (1080943). - Fix bounce log score messages to be more consistent. - Fix bin/remove_members to accept no arguments when both --fromall and --file= options are specified. - Change cgi-bin and mail wrapper "group not found" error message to be more descriptive of the actual problem. - Apply the list's ban_list to address changes and admin mass subscribe and invite and to confirmations/approvals of address changes, subscriptions and invitations. - Decode quoted-printable and base64 encoded parts before passing to HTML_TO_PLAIN_TEXT_COMMAND (1367783). - Remove Approve: header from post - treat as Approved: (1355707). - Stop removing line following Approve(d): line in body of post (1318883). - Log post in post log with true sender, not listname-bounces (1287921). - Correctly initialize and remember the list's default_member_moderation attribute in the web list creation page (1263213). - Add PEP263 charset in config_list output (1343100). - header_filter_rules get lost if accessed directly and needed authenti- cation by login page (1230865). - Obscure email when the poster doesn't set full name in 'From:' header. - Take preambles and epilogues into account when calculating message sizes for holding purposes (Mark Sapiro). - Logging/Logger.py unicode transform option (1235567). - bin/update crashes with bogus files (949117). - Bugs and patches: 1212066/1301983 (Date header in create/remove notice) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-i18n] A better way of doing templates?
Barry Warsaw wrote: > On Thu, 2005-11-24 at 10:44 +0900, Tokio Kikuchi wrote: > > >>How about adding current templates into pot/po and pickup and generate >>language templates during "make install." I don't know if it could be >>done at all but I will look at it this weekend. > > > I see that this is checked in, which I guess means that the idea is > working well for you. Cool! Yeah! ;^) > If we're going to generate all the > template files at build time, I suppose we should remove all those files > (and the directories?) from CVS. It's generally not a good idea to > check in files that are generated during the build process. What do you > think? I'm going to do this as a next step soon. >>As regards the whole translation process, I've already submitted a patch >> to select languages when configuring. This should help separating the >>translations from the main developement code base. >>http://sourceforge.net/tracker/index.php?func=detail&aid=1298355&group_id=103&atid=300103 > > > Very cool. I've also heard requests to reduce the tarball size by > separating the languages out into separate downloads. Does anybody > think that's worth doing? This has also been checked in. I'm going to try hack the release script to separate the languages from the main tarball. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Scrubber mungs Quoted Printable
Hi Mark,
I once used this patch for japanese mailman: This re-generation was
rejected by Barry because this may impose heavy load (?). This hack
should simplify the charset gotcha just below the patched lines. Or, we
may have to introduce a new variable to keep watch if the payload is
decoded or not in email.Message.Message class. IMHO, mailing list
messages should be in plain text without attachments and those who
attach should pay (the load) for it.
--- Scrubber.py.origThu Dec 1 10:01:45 2005
+++ Scrubber.py Thu Dec 1 10:13:17 2005
@@ -28,6 +28,7 @@
from cStringIO import StringIO
from types import IntType, StringType
+from email import message_from_string
from email.Utils import parsedate
from email.Parser import HeaderParser
from email.Generator import Generator
@@ -313,6 +314,9 @@
Url : %(url)s
"""), lcset)
outer = False
+# Re-generation of message instance from stringfied one.
+# This should normalize the payloads.
+msg = message_from_string(msg.as_string())
# We still have to sanitize multipart messages to flat text because
# Pipermail can't handle messages with list payloads. This is a
kludge;
# def (n) clever hack ;).
Mark Sapiro wrote:
> Mark Sapiro wrote:
>
>>I think the fix for the current problem is the following patch -
>>
>>--- mailman-2.1.6/Mailman/Handlers/Scrubber.py
>>+++ mailman-mas/Mailman/Handlers/Scrubber.py
>>@@ -376,9 +376,8 @@
>># Now join the text and set the payload
>>sep = _('-- next part --\n')
>>del msg['content-type']
>>-msg.set_payload(sep.join(text), charset)
>>del msg['content-transfer-encoding']
>>-msg.add_header('Content-Transfer-Encoding', '8bit')
>>+msg.set_payload(sep.join(text), charset)
>>return msg
>
>
> I still think this is the correct fix, but it turns out there are some
> tricky issues here that I believe come down to an error in the
> set_payload() method.
>
> Under certain circumstances, in particular when charset is 'iso-8859-1',
>
> msg.set_payload(text, charset)
>
> 'apparently' encodes the text as quoted-printable and adds a
>
> Content-Transfer-Encoding: quoted-printable
>
> header to msg. I say 'apparently' because if one prints msg or creates
> a Generator instance and writes msg to a file, the message is
> printed/written as a correct, quoted-printable encoded message, but
>
> text = msg._payload
> or
>
> text = msg.get_payload()
>
> gives the original text, not quoted-printable encoded, and
>
> text = msg.get_payload(decode=1)
>
> gives a quoted-printable decoding of the original text which is munged
> if the original text included '=' in some ways.
>
> This is a problem for Mailman because if Scrubber is processing
> individual messages, the 'apparently' quoted-printable message gets
> passed ultimately to SMTPDirect which calls Decorate, and Decorate
> does msg.get_payload(decode=1) when adding the header and/or footer
> and can mung the message in the process.
>
> There is also an issue with archiving when the archiver gets a
> multipart message which is subsequently flattened by Scrubber.
>
> The following is a transcript of a Python interactive session that
> illustrates the above problems with set_payload() and get_payload().
> This session is with Python 2.4.1, but exactly the same behavior
> occurs with 2.3.4 and 2.4.2.
>
> Python 2.4.1 (#1, May 27 2005, 18:02:40)
> [GCC 3.3.3 (cygwin special)] on cygwin
> Type "help", "copyright", "credits" or "license" for more information.
>
>>>>import email
>>>>
>>>>msg = email.message_from_file(open('plain2.eml'))
>>>>
>>>>print msg
>
>>From nobody Mon Nov 28 09:18:41 2005
> From: "Mark Sapiro" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: HTML - all
> Date: Sun, 27 Nov 2005 09:02:33 -0800
> MIME-Version: 1.0
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> How about just a line of stuff with some and a few words.
>
> X=91**2 (x is 91 squared)
>
>
>>>>del msg['content-type']
>>>>del msg['content-transfer-encoding']
>>>>msg.set_payload(str(msg.get_payload()), 'iso-8859-1')
>>>>
>>>>print msg
>
>>From nobody Mon Nov 28 09:18:41 2005
> From: "Mark Sapiro" <[EMAIL PROTECTED]>
> To: [EMAIL PROTE
Re: [Mailman-Developers] A better way of doing templates?
Hi, Barry Warsaw wrote: > Jordi Mallach brings up a good point on the rosetta-users mailing list, > in response to my queries there. > > Rosetta doesn't really work with non-po files, so the fact that we have > templates that need translating will cause us some grief. Well, even > more grief than it has over the years. ;) > > Does anybody have any good ideas for handling this in the Mailman 2 > tree? How about adding current templates into pot/po and pickup and generate language templates during "make install." I don't know if it could be done at all but I will look at it this weekend. As regards the whole translation process, I've already submitted a patch to select languages when configuring. This should help separating the translations from the main developement code base. http://sourceforge.net/tracker/index.php?func=detail&aid=1298355&group_id=103&atid=300103 -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] XMLRPC Patch
Hi, Joshua Ginsberg wrote: > Barry et al. -- > > Does anybody have any feedback on this patch? Is it something that can > be committed? Thanks! Will you please upload the patch to the SF tracker? Then, much more people can test the XMLRPC feature before commiting in the CVS. As the past discussions on this list suggest, there will be no more new feature in 2.1.x series but bug fixes, This should be integrated in 2.2 or 3.0. BTW, I had Sun RPC cracked, then vulnerable Windows RPC. So, I'm rather skeptical about RPC things. Yeah, I know it's different but ... :-( -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Sibling list
JC Dill wrote: > Stephen J. Turnbull wrote: > >>>>>>>"Tokio" == Tokio Kikuchi <[EMAIL PROTECTED]> writes: >> >> >>Tokio> - Is the terminology 'sibling' appropriate? >> >>I hesistate to give it a +1 because I know I think differently from >>most people, but FWIW I *did* guess what it does from that name. > > > Ditto. > Just to add a note. I picked up this word from Squid Web Proxy server's configuration. http://squid.visolve.com/squid/squid24s1/glossary.htm#sibling -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Sibling list
Hi Developers, I've just uploaded a new patch to enable 'sibling list' feature in mailman non-digest delivery. I'd like to get feedback from develpers on this feature, particularly on the naming ... sibling. ;-) https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1347962&group_id=103 Here are excerpts from the patch tracker. - Sibling lists are other mailing lists on this site whose members are excluded from regular delivery if those list addresses appear in To: or Cc: header. - The list addresses should be witten in full mail address format (e.g. [EMAIL PROTECTED]). Do not specify the list address mutually in the sibling list configuration page or those doubled members won't get message. TBD: - Is the terminology 'sibling' appropriate? - Need more comments in the processing code (CalcRecips.py). -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Patch: Select language(s) when install
Hi Developers, I've uploaded a patch to select languages when installing mailman. Here is a excerpt from SF tracker: --- Subject: [ mailman-Patches-1298355 ] Select language(s) when install Date: Wed, 21 Sep 2005 22:35:37 -0700 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_id=103 Initial Comment: While the number of translated languages is growing, most users are using only a few languages. With this patch, the site admin can select his/her required languages by an option to the configure script by `--with-languages' and can considerably reduce the install size. This patch is for 2.2.0a0 (most recent CVS as of writing) but also applicable to 2.1.6 except that you may have to regenerate configure script by invoing autoconf command. Patch usage: % cd mailman (src directory) % patch -p0 < /path/to/install_selected_language.patch.txt Configure usage: % ./configure --with-languages="ja fr" ... en+ja+fr % ./configure --with-languages="" ... all available languages % ./configure all available languages % ./configure --with-languages="none" ... English only Japanese and Korean codecs are no longer installed by `make install' but availability is checked during the configure run and urge to install if they are absent when CJK languages are included in the language list. I hope skilled developers can review this patch before I check in to the CVS. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Mal Formed MIME post leakedthrough to list
Hi,
Mark Sapiro wrote:
> I looked a bit at the documentation of the email library and based on
> that, I think what may have happened is when the parser saw the first
> "end of subpart boundary" which looked the same as the outer "end of
> part boundary", it took it as the end of the outer part and treated
> the rest as an epilogue. Hold.py does the following to compute message
> size:
>
> if mlist.max_message_size > 0:
> bodylen = 0
> for line in email.Iterators.body_line_iterator(msg):
> bodylen += len(line)
>
> but the body_line_iterator() method may skip the epilogue.
>
I think we can write more intuitive and robust code like this:
if mlist.max_message_size > 0:
bodylen = len(msg.as_string().split('\n\n',1)[1])
> Also, I think MimeDel.py will leave the epilogue in the message.
I will look at it closer.
>
> Interestingly, both Thunderbird 1.5b1 and MS Outlook Express 6 seem to
> parse the message as intended, but Mutt 1.4.1i sees it more like
> Mailman does.
>
> If there's no answer on the list, I intend to keep at it, but not for
> the next week as I will be away.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
[Mailman-Developers] Mailman 2.X CVS MAIN is back
Hi Developers, I've done backporting the changes in Release_2_1-maint into the MAIN branch which was not updated more than a year and this has caused confusion for the people who want to try CVS checkout. For I was a little bit tired of maintaining two branches (or of the pressure to do so) I want to check in to the MAIN branch only hereafter, although some serious security bug fix (if any) should be committed in the 2.1 branch. I believe the MAIN CVS checkout is now ready to be tested but plese let me know if you notice something. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-Users] header_filter_rules possible bug
Hi,
I think you are right! I have to make warning when checking in because
this may cause incompatible behavior for already installed other
patterns. :-(
Iain Pople wrote:
> Hi,
>
> I have noticed some unexpected behaviour with header_filter_rules.
>
> I wanted to reject messages with an empty subject line so i came up
> with the following regex:
>
> ^subject:\s*$
>
> However it wasn't working as desired. After delving around in the
> SpamDetect.py code i noticed that the re.search call is not using
> MULTILINE mode. So the headers are treated as one long string and ^
> would only match the beginning of the string.
>
> Is this the desired behaviour? To me it makes more sense that it
> should use multiline mode.
>
> i.e.:
>
> --- SpamDetect.py.bak 2005-08-02 15:56:42.08327 +1000
> +++ SpamDetect.py 2005-08-02 17:33:59.698226000 +1000
> @@ -127,7 +127,7 @@
> for pattern in patterns.splitlines():
> if pattern.startswith('#'):
> continue
> -if re.search(pattern, headers, re.IGNORECASE):
> +if re.search(pattern, headers, re.IGNORECASE|re.MULTILINE):
> if action == mm_cfg.DISCARD:
> raise Errors.DiscardMessage
> if action == mm_cfg.REJECT:
> @@ -137,3 +137,4 @@
> hold_for_approval(mlist, msg, msgdata,
> HeaderMatchHold)
> if action == mm_cfg.ACCEPT:
> return
>
> --
> Iain Pople
> Systems Programmer
> University of Melbourne
>
> --
> Mailman-Users mailing list
> Mailman-Users@python.org
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe:
> http://mail.python.org/mailman/options/mailman-users/tkikuchi%40is.kochi-u.ac.jp
>
> Security Policy:
> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
>
>
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] Bad info in http://www.list.org/faq.html
Hi, I've just updated on sourceforge. http://mailman.sourceforge.net/faq.html Mark Sapiro wrote: > The FAQ at http://www.list.org/faq.html and mirrors contains > > VERP_PASSWORD_REMINDERS = 1 VERP_PERSONALIZED_DELIVERIES = 1 > VERP_DELIVERY_INTERVAL = 1 VERP_CONFIRMATIONS = 1 > > This should say > > > OWNERS_CAN_ENABLE_PERSONALIZATION = Yes > > -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] please update list.org/devs.html IRC channel listing
Hi, Jim Tittsler wrote: > I believe <http://www.list.org/devs.html> should be updated to change > the IRC network name from openprojects.net to freenode.net. > I've just updated on sourceforge. http://mailman.sourceforge.net/devs.html > > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] version mismatch?
Barry Warsaw wrote:
> On Wed, 2005-07-20 at 12:16, Ian Eiloart wrote:
>
>
>>Am I right in thinking this means that I need to downgrade my python
>>version to make this work?
>
>
> No, but apparently does mean that you'll have to rebuild the codec
> extensions that come with Mailman. I /think/ if you run Mailman's
> config.status and then run make install again (against Python 2.4.1 of
> course) you should be golden.
Or, you may have to clear the previously installed codec modules by
% rm -rf /pythonlib/{japanese,korean}
then run make install again.
>
> Let us know if that works and I'll update the release notes.
>
> -Barry
>
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
___
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-users%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
Re: [Mailman-Developers] content filtering bug (text/html and text/plain in multipart emails)
Hi again, Michael Dunlap wrote: > Hello, > > I've been reading the archives and it looks as if the problem of having > content filtering on and passing multi-part emails (plain and html) > isn't really solvable. One email to the users list summarizes the > problem this way: > > > >>There is a basic design decision in content filtering that makes this >>difficult. Namely, after filtering, only the first remaining sub-part >>from a multipart/alternative part is retained. >> >>What this means in practice is if you want to allow both text/plain >>parts and text/html parts, the only way to get html to the list is to >>insure that the MUA (e-mail client) that creates the post creates an >>html only message, not a multipart/alternative message with both >>text/plain and text/html sub-parts. >> >>If you want Mailman content filtering to pass the html part from a >>multipart/alternative post, the only way to do this is to disallow >>text/plain and require everyone to post html, or to turn off content >>filtering and allow everything. > > > My question is two parts. One, is there a work-around available, and > two is this a "feature" which the developers intend to fix? > I've just checked in my patch to fix this. It introduces a new attribute 'collapse_alternatives' in the maillist object. You will need to run 'bin/update -f' after upgrading your installation to the latest CVS. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] content filtering bug (text/html andtext/plain in multipart emails)
Hi, Barry Warsaw wrote: > On Fri, 2005-07-01 at 20:04, Mark Sapiro wrote: > > >>2). I'm not a Mailman developer, and I can't speak for anyone's intent, >>but a patch which makes the above conditional on a new list attribute, >>updates Mailman/Gui/ContentFilter.py to maintain and document the new >>attribute and updates Mailman/MailList.py to set the default value >>(current behavior) for new and migrated lists, might be accepted. > > > Definitely. I don't remember exactly why we ended up with this behavior > unconditionally, but I agree now that it probably should be optional. > > Care to work out a patch? > Anyone done this already? I'm going to do this as a part of my lecture (Anatomy of Mailman) for our MS course students tommorow. :-) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] unicode traceback
Jeroen Ruigrok/asmodai wrote: > -On [20050704 20:21], Jeroen Ruigrok/asmodai ([EMAIL PROTECTED]) wrote: > >>Find attached a suggested patch which I think should solve this issue. > > > Did someone have any time yet to look at this? Because I think this kind of > small bug would warrant a 2.1.7 release even. > Sorry that I couldn't respond sooner. Will you please upload your patch to the SourceForge patch trancker and assign to me (tkikuchi)? -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-Users] ValueError: unpack list of wrong size
Hi, Daniel Lyons wrote: > Tokio, > > I came across your message to the mailman users list from a year ago. I > just received a "ValueError: unpack list of wrong size" error in > Mailman, and I wanted to give you the offending message in case you are > still the maintainer of Scrubber.py. > > The offending message is attached. > Looks like the offending line was this: Content-Disposition: inline; filename*0="Today's Headlines- C.I.A. Is Reviewing Its Security Policy for R"; filename*1="ecruiting Translators.jpg" Note that RFC2231 encoding specifies "'" as a special character for delimiting charset'lang'content. The sender's MUA should have encoded "'" as "%27". See: http://www.faqs.org/rfcs/rfc2231.html Of course, Mailman and Python email package should be robust for such violation. I need more time to fix this. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Search members bug?
Barry Warsaw wrote: > version we release (Tokio, we'll put off updating the GPL notices too). Agreed. And, sorry for the many typos I've committed. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Mailman-Users] subject_prefix multiplication
Barry Warsaw wrote: > On Fri, 2005-05-13 at 05:05, Brad Knowles wrote: > >>At 12:41 AM -0400 2005-05-13, Barry Warsaw wrote: >> >> >>> Thanks for the quick heads up. I think I just fixed it. At least I >>> /hope/ so, 'cause I'm going to bed. ;) >> >> So far as I know, we had been running a plain-jane 2.1.6rc3 >>installation on this machine. Is the fix for the subject line >>duplication going to be included in 2.1.6rc4, or at least the final >>2.1.6-REL? > > > Yes. And I emailed Tokio last night (well, a few hours ago which for me > included the briefest of naps :) that I think we'll need one more > release candidate. I'll probably spin that today, er, in a few hours. > > -Barry I believe I could finally fix the bug and commited in CVS. IMHO, python re.escape() should escape special characters only -- I can't find '%' in special character list in the manual. -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Patch for Mail Archive mirroring
Hi folks, Jeff Marshall wrote: > I have submitted a patch to SourceForge for consideration. > > Feature: > - New third party archiving option that uses The Mail Archive. I've reading your discussions and kept silent but recently urged to say something here. You may think this timing is the last chance that this patch is included in the main cvs but there are many other patches which are waiting in the SF patch area and maintained by the respective original authors. Incluing in the main CVS means we, Barry and I, are resposible in maintenace of the feature and I am not moved toward accepting the resposibility. I'd say "no" for merging into CVS now. Of course, Barry may have different opinion. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] [Fwd: [ mailman-Bugs-1188133 ] CGI group id not properly tested]
Thank you John! I've updated the bug tracker. Mr. Mottram also changed his page after a little discussion with me. John Dennis wrote: > On Sat, 2005-04-23 at 06:53 +0900, Tokio Kikuchi wrote: > >>Hi Developers, >> >>There is a rumor that mailman security check is not proper and >>recommending patch to void our security check. Can someone write >>a refutation to this article? (In a fluent English of course ;-) > > >>Bugs item #1188133, was opened at 2005-04-22 15:58 >>Message generated for change (Tracker Item Submitted) made by Item Submitter >>You can respond by visiting: >>https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1188133&group_id=103 > > > I believe Geoff Mottram may be confused with how mailman's security > works. > (snip) > Note: I have only responded to this list, I have not updated the > original bug posting. > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] [Fwd: [ mailman-Bugs-1188133 ] CGI group id not properly tested]
Hi Developers, There is a rumor that mailman security check is not proper and recommending patch to void our security check. Can someone write a refutation to this article? (In a fluent English of course ;-) Original Message Subject: [ mailman-Bugs-1188133 ] CGI group id not properly tested Date: Fri, 22 Apr 2005 07:58:37 -0700 From: SourceForge.net <[EMAIL PROTECTED]> Reply-To: mailman-developers@python.org To: [EMAIL PROTECTED] Bugs item #1188133, was opened at 2005-04-22 15:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1188133&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Graham Klyne (grahamk) Assigned to: Nobody/Anonymous (nobody) Summary: CGI group id not properly tested Initial Comment: [I tried to send this to mailman-developers, but my message was discarded] I've just downloaded and installed the latest mailman 2.1.6rc1 and encountered a CGI permissions problem (running with Apache 2.0 on Scientific Linux 3.04), for which a patch is described in: http://minaret.biz/tips/mailman.html (briefly, replace getgid with getegid in common.c) Applying this patch resolves the problem I was experiencing. Is there any reason this isn't applied in the mailman distribution? #g -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1188133&group_id=103 ___ Mailman-coders mailing list Mailman-coders@python.org http://mail.python.org/mailman/listinfo/mailman-coders -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Mailman 2.1.6 2nd release candidate
Hi all, Afrer the release of RC1, we had a couple of reasons to delay the final, including a move of FSF office in the end of this month which are to be included in all the copyleft notices in the files. I will also become busy on my paid duties and the final release of 2.1.6 may not occur by the middle of May. :-< So, we have much time to test or translate this 2nd release candidate for the final 2.1.6. http://sourceforge.net/project/showfiles.php?group_id=103 or http://mm.tkikuchi.net/mailman-2.1.6rc2.tgz Cheers, -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Mailman 2.1.6 release candidate up
Sorry that I forget to add the download pointer; http://sourceforge.net/project/showfiles.php?group_id=103 or http://mm.tkikuchi.net/mailman-2.1.6rc1.tgz Hi all, Now we are on the last stage before the final release of 2.1.6. After the release of 2.1.6b5, we've got translation updates from the language champions including Leona for zh_CN (Chinese, China). Hopefully, I will be able to release the 2.1.6 final within a week. Cheers, -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Mailman 2.1.6 release candidate up
Hi all, Now we are on the last stage before the final release of 2.1.6. After the release of 2.1.6b5, we've got translation updates from the language champions including Leona for zh_CN (Chinese, China). Hopefully, I will be able to release the 2.1.6 final within a week. Cheers, -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] Mailman 2.1.6 beta 5 released
Bryan Fullerton wrote: Yay, upgraded. :) Is the bug you mentioned below filed on SF? No. Just wondering what the issue is, and specifically if this will fix a problem I've seen with SpamAssassin-tagged mail leaking through to my mailman@ list despite a header_filter_rule that really should be blocking it... but haven't had time to double-check everything is setup properly here before reporting it as a bug. Sorry for the inconvenience. The shame is on me. While applying my patch, by hand, to collect subpart headers, I might have something out of mind and an intermediate version has gone out. I am going to give some seminar on the security of mailman this weekend in Tokyo and while preparing my presentation I wanted to check the new feature. Then, the bug is there! You can check what was wrong using diff in CVS. http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/SpamDetect.py?r1=2.3.2.2&r2=2.3.2.3 -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
[Mailman-Developers] Mailman 2.1.6 beta 5 released
Hi, Sorry for the delay of 2.1.6 but a serious bug was found in the previous beta releases. I put a final beta release before jumping up to the release candidate. The bug is related to 'Privacy -> SPAM filter -> header_filter_rules'. So, I want all of you, who have had brave souls to upgrade 2.1.6 beta and who use this feature, to upgrade again to 2.1.6 beta 5. The tarball is placed at http://mm.tkikuchi.net/mailman-2.1.6b5.tgz # Sorry but it looks like I have not access to the file releases on SF. -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
Re: [Mailman-Developers] SMTPDeliver.py still can't do MTA VERP?
Hi, Dan Mick wrote: Barry Warsaw wrote: On Fri, 2005-02-18 at 00:07, Dan Mick wrote: a long long *long* time ago now, I made a small hack to SMTPDeliver.py to add options to the sendmail connection EHLO, to enable VERP generation in the MTA (so that the sending system didn't have to send N messages to the MTA to accomplish VERP, but rather let the MTA deal with it). For Postfix, this is as simple as adding the XVERP option. I still don't see any facility for doing this in a generic way; has anyone addressed the problem, and if so can someone point me at the solution?.. There's this: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=731100&group_id=103 but I haven't looked at the details of it. -Barry Yup, that's essentially what I did (except slightly nicer as it's configurable in mm_cfg.py). Any chance of getting this into A Mailman Near You? I think I can integrate it into 2.2 which I am going to work on after the 2.1.6 release which is now in final stage. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ ___ 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-users%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
