Mailman 3 February 2015 - Mailman-Developers

Willing to Contribute
by Himanshu Mishra Feb. 11, 2015

Feb. 11, 2015

Hi, My name is Himanshu Mishra. I am a first year undergrad student at Indian Institute of Technology Kharagpur, India. I'm pursuing Mathematics and Computing. I want to contribute to GNU Mailman as a GSoC 2015 student. Please help me get started. How can I setup the developing environment? Where is the souce code hosted?

1 0

When a user is deleted, is the uid record intentionally not deleted?
by Andrew Stuart Feb. 10, 2015

Feb. 10, 2015

I notice that when a user is deleted, the uid record remains. Is this because there is a bug in which the uid should be deleted but is not? or is this intentional behaviour to prevent the uid from being recreated as a duplicate? My testing code does large numbers of creations and deletions of users so the deleted uid records are building up.

2 5

User id - integer or UUID?
by Andrew Stuart Feb. 10, 2015

Feb. 10, 2015

I have read previous discussion here about format of user_id https://mail.python.org/pipermail/mailman-developers/2014-October/024024.ht… That’s fine, I understand the issues. The question is, I am storing user ids and it’s not clear to me if I should be storing them as INTs as returned by the REST API or converting back to UUID? It’s important to get right now because Im going to use the same approach everywhere. thanks

2 4

REST API delete user function does not delete every 2nd linked address
by Andrew Stuart Feb. 9, 2015

Feb. 9, 2015

(you’ll need to widen your message window to see this clearly) The following series of curl commands creates a user with an email address of ‘z(a)example.xn--org-to0a, and then links 10 additional addresses to z(a)example.org curl -X POST --data "email=z(a)example.org&display_name=z" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users curl -X POST --data "email=z1(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z2(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z3(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z4(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z5(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z6(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z7(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z8(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z9(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z10(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses A sqlite3 dump of the database shows the following in the addresses table: INSERT INTO "address" VALUES(11,'z(a)example.org',NULL,'z',NULL,'2015-02-08 10:50:37.241724',5,17); INSERT INTO "address" VALUES(12,'z1(a)example.org',NULL,'',NULL,'2015-02-08 10:52:08.928901',5,19); INSERT INTO "address" VALUES(13,'z2(a)example.org',NULL,'',NULL,'2015-02-08 10:52:36.308978',5,20); INSERT INTO "address" VALUES(14,'z3(a)example.org',NULL,'',NULL,'2015-02-08 10:52:43.947229',5,21); INSERT INTO "address" VALUES(15,'z4(a)example.org',NULL,'',NULL,'2015-02-08 10:52:49.598934',5,22); INSERT INTO "address" VALUES(16,'z5(a)example.org',NULL,'',NULL,'2015-02-08 10:52:54.406450',5,23); INSERT INTO "address" VALUES(17,'z6(a)example.org',NULL,'',NULL,'2015-02-08 10:52:59.295078',5,24); INSERT INTO "address" VALUES(18,'z7(a)example.org',NULL,'',NULL,'2015-02-08 10:53:04.892381',5,25); INSERT INTO "address" VALUES(19,'z8(a)example.org',NULL,'',NULL,'2015-02-08 10:53:10.497119',5,26); INSERT INTO "address" VALUES(20,'z9(a)example.org',NULL,'',NULL,'2015-02-08 10:53:16.450507',5,27); INSERT INTO "address" VALUES(21,'z10(a)example.org',NULL,'',NULL,'2015-02-08 10:53:24.021368',5,28); All good at this stage. No problems. The following curl command deletes user ‘z(a)example.xn--org-to0a curl --verbose -X DELETE --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org Strangely, a sqlite3 dump of the database now shows the following in the addresses table: INSERT INTO "address" VALUES(12,'z1(a)example.org',NULL,'',NULL,'2015-02-08 10:52:08.928901',NULL,19); INSERT INTO "address" VALUES(14,'z3(a)example.org',NULL,'',NULL,'2015-02-08 10:52:43.947229',NULL,21); INSERT INTO "address" VALUES(16,'z5(a)example.org',NULL,'',NULL,'2015-02-08 10:52:54.406450',NULL,23); INSERT INTO "address" VALUES(18,'z7(a)example.org',NULL,'',NULL,'2015-02-08 10:53:04.892381',NULL,25); INSERT INTO "address" VALUES(20,'z9(a)example.org',NULL,'',NULL,'2015-02-08 10:53:16.450507',NULL,27); So 6 of the addresses that should have been deleted were deleted, but 5 remain. The linked address deletion seems to be skipping addresses for some reason.

2 4

Interested in contributing to Mailman
by Ankush Sharma B.Tech. Electronics Engg, IIT(BHU), Varanasi (U.P.), INDIA Feb. 8, 2015

Feb. 8, 2015

Hi everyone, I am Ankush Sharma from India, currently an undergrad at IIT-BHU,Varanasi. I am a python aficionado and a die hard linux fan. I love to spent my time automating things on the web. Apart from that, I delivered a talk at PyCon India 2014 about *powering apps with gesture control using python programming language *[1]*. *I have earlier experience of working with SMTP libraries of python and SMTP protocol while developing makemymails.com, finalists of India zone for the Google Cloud Developer Challenge-2014. I found mailman quite interesting. I have already set up the development environment for the Mailman core and Postorius; thanks to @maxking and other devs for reaching out at IRC. Currently, I am going through the codebase and the mail archives. The idea list for this year's GSOC program is quite versatile and I would love to suggest any other ideas. The idea of having a mailman client written in Javascript is a good project to work on. I have noticed a few things but it would be better to go through the whole architecture, docs and archives before pointing them out. Looking forward to contributing to Mailman through this year's GSOC program. Thanks, Ankush Sharma Btech Part-III IIT-BHU,Varanasi-221005 GITHUB : github.com/black-perl [1] in.pycon.org/funnel/2014/208-python-the-eyes-of-real-world-computer-applica…

1 0

Mailman 2.1.19 release
by Mark Sapiro Feb. 7, 2015

Feb. 7, 2015

I am pleased to announce the second release candidate for Mailman 2.1.19. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features since 2.1.18-1, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. Associated with those changes are many things that have i18n impacts including new and modified strings in the message catalog, a new adminaddrchgack.txt template and a minor change to the admindbdetails.html template. I strongly encourage anyone with an interest in translations of Mailman to get this release and help with updating the translations. There are also bug fixes. See the attached README for more details. The differences between this and the first 2.1.19 candidate are the following. The subscribe_auto_approval feature in the first candidate has been augmented to accept @listname to auto approve members of another list. (LP: #1417093) Organization: headers are unconditionally removed from posts to anonymous lists and a bug involving ANONYMOUS_LIST_KEEP_HEADERS has been fixed. (LP: #1419132) The admindb interface display of a held message body has been fixed to not stop in the middle of a multi-byte character and not fail to convert to the display character set message bodies with invalid characters. (LP: #1415406) Additionally, and the main reason for this second candidate, Mailman's character set for both Romanian and Russian has been changed to utf-8. (LP: #1418735) and (LP: #1418448). This may be disruptive in that following this change, some archive pages and some list attributes for lists whose preferred_language is one of those two languages may not display correctly. Archives can be fixed by running 'bin/arch --wipe' for the affected lists, but list attributes will probably have to be fixed manually. I hope the benefits of this change will outweigh the pain, and I encourage anyone with Romanian or Russian Language lists to try this release and report your experience. It may be possible to fix at least some list attributes programmatically as part of the version update process. I plan to release the final 2.1.19 release at the end of February, and it would be good to have as many i18n updates as possible by then. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, please see: http://www.list.org http://www.gnu.org/software/mailman http://mailman.sourceforge.net/ Mailman 2.1.19rc2 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 1

Is there a way to delete an unlinked/orphaned address via the REST API?
by Andrew Stuart Feb. 6, 2015

Feb. 6, 2015

After unlinking an address from a user, there is an address in the addresses table that is orphaned - i.e. it does not have a linked user. This is the expected behaviour (I think) - that’s fine, no problems at this point. However, I can’t see a way to delete these addresses via the REST API. Does one exist? Should it exist? Perhaps so - without it there’s no way to delete orphaned email addresses. thanks as

2 1

Re: [Mailman-Developers] "Address already exists" when creating users, but it creates a new user anyway
by Andrew Stuart Feb. 6, 2015

Feb. 6, 2015

After a bit of deep cave diving into the code I suspect it’s this in model/usermanager.py This function appears to create a user before it checks to see if the address exists, with the result that multiple users are created when the address already exists. @implementer(IUserManager) class UserManager: """See `IUserManager`.""" def create_user(self, email=None, display_name=None): """See `IUserManager`.""" user = User(display_name, Preferences()) if email: address = self.create_address(email, display_name) user.link(address) return user this seems to fix the problem - but please don’t trust my solution - needs verification. @implementer(IUserManager) class UserManager: """See `IUserManager`.""" def create_user(self, email=None, display_name=None): """See `IUserManager`.""" if email: address = self.create_address(email, display_name) user = User(display_name, Preferences()) if email: user.link(address) return user On 5 Feb 2015, at 7:59 am, Barry Warsaw <barry(a)list.org> wrote: On Feb 05, 2015, at 07:23 AM, Andrew Stuart wrote: > To get the source I do: > > bzr branch lp:mailman > > Is this the correct way? > > I’m using Python 3.4 Yep, exactly so. Thanks. I'll give it a go tonight. -B

2 1

Security - XSS JavaScript and SQL injection in Mailman, Postorius and Hyperkitty
by Andrew Stuart Feb. 5, 2015

Feb. 5, 2015

Does the code of Mailman 3, Hyperkitty and Postorius do anything to address concerns around SQL and JavaScript injections, either from inbound emails or via the fields coming in via web interface or REST API? thanks

2 1

"Address already exists" when creating users, but it creates a new user anyway
by Andrew Stuart Feb. 4, 2015

Feb. 4, 2015

In the commands below you can see that I start by getting a list of users, it returns "total_size": 1 I then execute a POST to the REST API multiple times. Each time it says “Address already exists”, and then getting a list of users says total_size": 2 Is this the way its intended to work or a bug? thanks as ubuntu@server01:~$ ubuntu@server01:~$ curl --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users {"entries": [{"password": "$6$rounds=109794$l/9MF2/dD7xSnoLD$6j3t0chh/UCnq61b3myleUaoHJEe4gNcidViWVR8kebKwU5oIVZ0ogsDiD7kgVr2V26zy8PaSfC5uQSY6rC0G1", "self_link": "http://localhost:8001/3.0/users/282607068158551958257628859360097200763", "user_id": 282607068158551958257628859360097200763, "http_etag": "\"7d81842c0a54679d42049c7eb25d64d2fd658b1a\"", "created_on": "2015-02-01T08:17:27.577221"}], "total_size": 1, "http_etag": "\"ae06e3745039c38b8a5c33d8bb468ba538fbb88a\"", "start": 0}ubuntu@server01:~$ ubuntu@server01:~$ ubuntu@server01:~$ curl -X POST --data "email=mailmanadmin(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users Address already exists: mailmanadmin@example.orgubuntu@server01:~$ ubuntu@server01:~$ ubuntu@server01:~$ curl --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users {"entries": [{"password": "$6$rounds=109794$l/9MF2/dD7xSnoLD$6j3t0chh/UCnq61b3myleUaoHJEe4gNcidViWVR8kebKwU5oIVZ0ogsDiD7kgVr2V26zy8PaSfC5uQSY6rC0G1", "self_link": "http://localhost:8001/3.0/users/282607068158551958257628859360097200763", "user_id": 282607068158551958257628859360097200763, "http_etag": "\"7d81842c0a54679d42049c7eb25d64d2fd658b1a\"", "created_on": "2015-02-01T08:17:27.577221"}, {"self_link": "http://localhost:8001/3.0/users/92205393033160387796290186916038781151", "user_id": 92205393033160387796290186916038781151, "http_etag": "\"d44893d5fd8dccb797d19372c068d24b3d45dde9\"", "created_on": "2015-02-01T08:18:30.658821"}], "total_size": 2, "http_etag": "\"7060713ada4dbbbc97a8da2f1c3545f41c0878af\"", "start": 0}ubuntu@server01:~$ ubuntu@server01:~$ ubuntu@server01:~$ curl -X POST --data "email=mailmanadmin(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users Address already exists: mailmanadmin@example.orgubuntu@server01:~$ ubuntu@server01:~$ ubuntu@server01:~$ curl --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users {"entries": [{"password": "$6$rounds=109794$l/9MF2/dD7xSnoLD$6j3t0chh/UCnq61b3myleUaoHJEe4gNcidViWVR8kebKwU5oIVZ0ogsDiD7kgVr2V26zy8PaSfC5uQSY6rC0G1", "self_link": "http://localhost:8001/3.0/users/282607068158551958257628859360097200763", "user_id": 282607068158551958257628859360097200763, "http_etag": "\"7d81842c0a54679d42049c7eb25d64d2fd658b1a\"", "created_on": "2015-02-01T08:17:27.577221"}, {"self_link": "http://localhost:8001/3.0/users/92205393033160387796290186916038781151", "user_id": 92205393033160387796290186916038781151, "http_etag": "\"d44893d5fd8dccb797d19372c068d24b3d45dde9\"", "created_on": "2015-02-01T08:18:30.658821"}, {"self_link": "http://localhost:8001/3.0/users/276766536585189861964818785630123864804", "user_id": 276766536585189861964818785630123864804, "http_etag": "\"edf93f04566715b1afaeaee0368bc2101aa0d8b3\"", "created_on": "2015-02-01T08:19:03.900670"}], "total_size": 3, "http_etag": "\"49ffe8ac58d624c250ec6af339f4cab609f4e138\"", "start": 0}ubuntu@server01:~$ ubuntu@server01:~$

2 4