Mailman 3 January 2007 - Mailman-Developers

Self-Approve Link in Member-Only error messages
by Joachim Breitner Jan. 29, 2007

Jan. 29, 2007

Hello, a lot of mailing lists have posting only available to members just to prevent spam. For these lists there should be an option that adds a link to the „Your message is held...“ notification that will allow the message to go through, just like the link to delete it, or the check in the subscription handshake. This would reduce work for the list administrator and be more friendly to the casual poster. In http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407530 it was argued that spammers would then soon start to learn to „click“ this link. I disagree though that this feature will indeed open the gates to spammers: If they figure out how to activate a link in a confirmation message, they will figure out how to subscribe anyways. Alternatively, a message to a members-only mailing list could automatically trigger a subscribe challenge that, if acted upon, not only subscribes the sender, but also approves the held-back message. What do you think? Greetings, Joachim -- Joachim "nomeata" Breitner mail: mail(a)joachim-breitner.de | ICQ# 74513189 | GPG-Key: 4743206C JID: joachimbreitner(a)amessage.de | http://www.joachim-breitner.de/ Debian Developer: nomeata(a)debian.org

3 5

Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8135] trunk/mailman/Mailman/database/listdata.py
by Barry Warsaw Jan. 6, 2007

Jan. 6, 2007

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Excellent, thanks! I'm /really/ going to have to figure out schema migration soon. ;) - -Barry On Jan 6, 2007, at 12:05 AM, tkikuchi(a)users.sourceforge.net wrote: > Revision: 8135 > http://svn.sourceforge.net/mailman/?rev=8135&view=rev > Author: tkikuchi > Date: 2007-01-05 21:05:11 -0800 (Fri, 05 Jan 2007) > > Log Message: > ----------- > Add post_id in list data schema. > > Modified Paths: > -------------- > trunk/mailman/Mailman/database/listdata.py > > Modified: trunk/mailman/Mailman/database/listdata.py > =================================================================== > --- trunk/mailman/Mailman/database/listdata.py 2007-01-05 22:01:43 > UTC (rev 8134) > +++ trunk/mailman/Mailman/database/listdata.py 2007-01-06 05:05:11 > UTC (rev 8135) > @@ -122,6 +122,7 @@ > Column('pass_mime_types', > PickleType), > Column('password', > Unicode), > Column('personalize', > Integer), > + Column('post_id', > Integer), > Column('preferred_language', > Unicode), > Column('private_roster', > Boolean), > Column('real_name', > Unicode), > > > This was sent by the SourceForge.net collaborative development > platform, the world's largest Open Source development site. > _______________________________________________ > Mailman-checkins mailing list > Mailman-checkins(a)python.org > Unsubscribe: http://mail.python.org/mailman/options/mailman- > checkins/barry%40python.org > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) iQCVAwUBRZ8xhnEjvBPtnXfVAQI8lgP/fcECyyIqebtaQDH0ruz+DKrd+PMVuTkv Y4TF8V8GKyqECIy1AatIU85lxQ0+DprDrOQ3IucyutjgGG697AmvBgW7fqPFuYT3 BvnmXCce71bv5JKfsmXomWHrcMjGn25E/hABLuMrs+NJnQPmx55S10yyFM+YdUL5 2zQfB8rhz9k= =9xnf -----END PGP SIGNATURE-----

1 0

Pickles begone
by Barry Warsaw Jan. 5, 2007

Jan. 5, 2007

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm about to merge my SQLAlchemy branch to the trunk. I'm happy enough with where this is going to commit to this approach going forward. I wrote about it a bit in a news article on wiki.list.org and I'll try to elaborate there when things settle down. This stuff could definitely use more testing, but the web u/i and sending mail through the system work for me. If you're using the trunk regularly now, you will notice that there's no migration path yet for moving from the pickle-based storage to SQLAlchemy based storage. This is what the import/export scripts are for. You notice though that only bin/export is written yet. bin/import is tops on my list after the merge. I've also committed bin/export.py to the Mailman 2.1 branch. This will be how you migrate MM2.1 lists to the MM trunk. Our next release of MM2.1 will have this, so my plan for migration will be to install the latest 2.1.x (x > 9), run bin/export.py, then feed the resulting XML to the trunk's bin/import. For now, you can start from scratch with bin/newlist or creating a list through the web. From there the trunk should look and act just like you're used to. As always, let us know what you find. I'm eager to fix problems quickly. Please don't use the SF bug tracker for problems you encounter on the trunk. It would also be interesting to know if you try a SQLAlchemy backend other than SQLite. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRZWUFHEjvBPtnXfVAQIEJwP/WkB2jY3Ww2YR96oDejC/ZSSWwbct8ENb k/kpcoYm9V2ra36WUiHt0pfFLyhMk0pRXtBh/oScooLiZJu9AA2wnD046I5AJZLt 5DS+YJI2B5c4pn4pO80w5JeAUgQfiYIhafs6u/Oy3fDzag6Rp698Dt/Bv62V8Mly hteE9Iu8xcs= =plDI -----END PGP SIGNATURE-----

5 12