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?
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
-----BEGIN PGP SIGNED MESSAGE-----
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
-----END PGP SIGNATURE-----