Mailman 3 October 2014 - Mailman-coders

[Bug 1091586] [NEW] Frequent OperationalError: database is locked with sqlite
by Aurélien Bompard 26 Nov '14

26 Nov '14

Public bug reported: I'm seeing frequent locking errors with SQLite on the current version of mailman3 from bzr. Here's an example traceback : Traceback (most recent call last): File "/srv/dev/mailman/bin/runner", line 9, in <module> load_entry_point('mailman==3.0.0b2-', 'console_scripts', 'runner')() File "/srv/dev/mailman/mailman3/mailman/src/mailman/bin/runner.py", line 253, in main runner.run() File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 96, in run filecnt = self._one_iteration() File "/srv/dev/mailman/mailman3/mailman/src/mailman/core/runner.py", line 173, in _one_iteration config.db.commit() File "/srv/dev/mailman/mailman3/mailman/src/mailman/database/base.py", line 77, in commit self.store.commit() File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/store.py", line 122, in commit self._connection.commit() File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 126, in commit self.raw_execute("COMMIT", _end=True) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 322, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/srv/dev/mailman/lib/python2.6/site-packages/storm-0.19-py2.6-linux-x86_64.egg/storm/database.py", line 371, in _check_disconnect return function(*args, **kwargs) sqlite3.OperationalError: database is locked It happens during the normal processing of Mailman, not while using the API (to my knowledge), so it seems different from bug #856004. I can reproduce this easily by letting Mailman work for some time. After the locking error, new messages are stuck in var/queue/pipeline: $ ls var/queue/* var/queue/archive: var/queue/bad: var/queue/bounces: var/queue/command: var/queue/digest: var/queue/in: var/queue/lmtp: var/queue/nntp: var/queue/out: var/queue/pipeline: 1355781960.9870529+18f0acdf07aab616f793ecf76acfa1994e62b3a9.pck 1355799347.787621+213f3a6a971717ad1ba27f3d56b65767747a45da.pck 1355814973.8623891+4e66eeadef9b8c9ae99e4ed022c6c93f5af75c05.pck 1355782349.546113+ee14cb323574b647d9014f742e3f505e388d553e.pck 1355800543.460628+c455625c1ad86a5a77c9c515fcb6d555ba439b19.pck 1355815808.8860879+ca3fb5f45999e47c92756489daa951672ba4304d.pck 1355792739.8787439+19973fbcf763f036655aa0a7d477231246afdfbd.pck 1355802301.7830889+7989a3199c7eb491b65176937c0c1658cca9d46d.pck 1355820018.1813829+5005ded04da3574a7f3cd7472c9d635c577b6c32.pck 1355794764.597765+6cf379ad16c948117bb65f0aed0b3c230268ffd2.pck 1355803681.7455051+52d185cdcaecaf883bd43f375f5253567f5cd568.pck 1355822188.0491021+6a3cab9831d03b4f94475f745fa508c5126116b4.pck 1355794889.8323901+e14e25e342ec59709266040d830d7e12be2a1261.pck 1355805362.052228+422e573a6117edb7aae1acf9150ac58c210cedba.pck 1355822293.2363911+627f13dd2121bcb0f1916bc0448cc3b8adc9ad1f.pck 1355795937.2442579+62193d05ee80c6a22213cf2ff211c135fb7d38d9.pck 1355807374.9844501+8de57ab53819fac59d64705bcc56f86899d22634.pck 1355798662.8335559+554da4e7690e116e6fabee5764ac69829dc25685.pck 1355808273.143533+ed1acbf580c596ed921e062ece575877f0c9304b.pck var/queue/rest: var/queue/retry: var/queue/shunt: 1355776302.1302171+c657867b33bf6e37554ff83ee26f4096a77c1114.pck var/queue/virgin: And I need to restart mailman to make it process them again. The locked caused the message to be shunted. I'll attach the mailman.log file, where you'll see many "database is locked" errors, happening on different requests. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1091586 Title: Frequent OperationalError: database is locked with sqlite To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1091586/+subscriptions

2 8

[Bug 1236297] [NEW] Unicode errors with PostgreSQL and RawStr fields
by Aurélien Bompard 26 Nov '14

26 Nov '14

Public bug reported: When using PostgreSQL as a database, it's impossible to set the moderator_password field of a mailing list, which is of type RawStr. To be precise, it's possible to set it, but getting it back from the database after a commit will cause a TypeError with the message: "Expected str, found <type 'unicode'>" as if PostgreSQL always returned unicode on TEXT fields and Storm did not convert them to bytestrings. I get no errors on an SQLite database. I don't know if the problem comes from Mailman or Storm. I have written a python script to reproduce it, see the attached file. There are comments, it should be easily readable. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Attachment added: "test-mm-storm-unicode.py" https://bugs.launchpad.net/bugs/1236297/+attachment/3864008/+files/test-mm-… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1236297 Title: Unicode errors with PostgreSQL and RawStr fields To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1236297/+subscriptions

2 5

[Bug 1230130] [NEW] The mailinglist interface specifies the "administrative" attribute instead of "administrivia"
by Aurélien Bompard 25 Nov '14

25 Nov '14

Public bug reported: In the IMailingList interface, there is an "administrative" attribute which is said to control "administrivia" checks. But apparently, in the model and in the code, this attribute is called "administrivia", as in Mailman 2.1. Unless I'm missing something, the interface attribute should be renamed. ** Affects: mailman Importance: Undecided Status: New ** Tags: easy mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1230130 Title: The mailinglist interface specifies the "administrative" attribute instead of "administrivia" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1230130/+subscriptions

1 1

[Merge] lp:~barry/mailman/falcon into lp:mailman
by Barry Warsaw 15 Nov '14

15 Nov '14

Barry Warsaw has proposed merging lp:~barry/mailman/falcon into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~barry/mailman/falcon/+merge/230913 Port from restish to falcon for the REST API framework. This currently depends on an unmerged falcon pull request: https://github.com/racker/falcon/pull/307 -- https://code.launchpad.net/~barry/mailman/falcon/+merge/230913 Your team Mailman Coders is requested to review the proposed merge of lp:~barry/mailman/falcon into lp:mailman.

2 1

[Merge] lp:~glibersat/postorius/i18n-french into lp:postorius
by Guillaume Libersat 03 Nov '14

03 Nov '14

Guillaume Libersat has proposed merging lp:~glibersat/postorius/i18n-french into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~glibersat/postorius/i18n-french/+merge/240066 - french translation catalog ; - a few addition of "trans" tags in templates to allow the remaining strings to be translated ; - use gettext_lazy instead of gettext in forms.py so the translation mecanism is really working. I've made small commits without mixing template/code/translation tasks. You can generate the i18n catalogs using "django-admin.py compilemessages". -- https://code.launchpad.net/~glibersat/postorius/i18n-french/+merge/240066 Your team Mailman Coders is requested to review the proposed merge of lp:~glibersat/postorius/i18n-french into lp:postorius.

3 5

[Merge] lp:~raj-abhilash1/mailman/sqlalchemy into lp:mailman
by Abhilash Raj 01 Nov '14

01 Nov '14

Abhilash Raj has proposed merging lp:~raj-abhilash1/mailman/sqlalchemy into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~raj-abhilash1/mailman/sqlalchemy/+merge/235329 Replace storm with sqlalchemy. -- https://code.launchpad.net/~raj-abhilash1/mailman/sqlalchemy/+merge/235329 Your team Mailman Coders is requested to review the proposed merge of lp:~raj-abhilash1/mailman/sqlalchemy into lp:mailman.

2 1

[Bug 1386602] [NEW] Mailman web interface fails after upgrade to 2.1.18-1
by Nic Fox 29 Oct '14

29 Oct '14

Public bug reported: Upgraded mailman on Ubuntu 12.04 LTS server from v2.1.14 (I think), to 2.1.18-1 following the instructions here: http://wiki.list.org/pages/viewpage.action?pageId=17891606 Configure, make and install commands all ran OK. Web interface reports the following error with STEALTH_MODE = 0 in scripts/driver: Bug in Mailman version 2.1.18-1 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 85, in run_main immediate=1) File "/var/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/var/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ self.__get_f() File "/var/lib/mailman/Mailman/Logging/Logger.py", line 68, in __get_f 1) File "/usr/lib/python2.7/codecs.py", line 881, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' Python information: Variable Value sys.version 2.7.3 (default, Feb 27 2014, 20:00:17) [GCC 4.6.3] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE __utma=83584454.2092742145.1350180395.1396266401.1405737127.25; __utmz=83584454.1350180395.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); SESS66092fc5dc377f03ded7c51bfd9b9869=dqj5gm2muqn616htqlrrb5kh96 SERVER_SOFTWARE Apache/2.2.22 (Ubuntu) SCRIPT_NAME /cgi-bin/mailman/admin SERVER_SIGNATURE <address>Apache/2.2.22 (Ubuntu) Server at anumc.org.au Port 80</address> REQUEST_METHOD GET PATH_INFO /anumc-comm SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0 HTTP_CONNECTION keep-alive SERVER_NAME anumc.org.au REMOTE_ADDR 122.49.203.186 PATH_TRANSLATED redirect:/index.php SERVER_PORT 80 SERVER_ADDR 106.187.102.76 DOCUMENT_ROOT /web/anumc/drupal5/base PYTHONPATH /var/lib/mailman SCRIPT_FILENAME /usr/lib/cgi-bin/mailman/admin SERVER_ADMIN webmaster@localhost SCRIPT_URI http://anumc.org.au/cgi-bin/mailman/admin/anumc-comm HTTP_HOST anumc.org.au SCRIPT_URL /cgi-bin/mailman/admin/anumc-comm HTTP_CACHE_CONTROL max-age=0 REQUEST_URI /cgi-bin/mailman/admin/anumc-comm HTTP_ACCEPT text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 49687 HTTP_ACCEPT_LANGUAGE en-US,en;q=0.5 HTTP_ACCEPT_ENCODING gzip, deflate ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1386602 Title: Mailman web interface fails after upgrade to 2.1.18-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1386602/+subscriptions

2 4

Re: [Question #256265]: How do I make a list that Members can't Respond-All to?
by Mark Sapiro 28 Oct '14

28 Oct '14

Question #256265 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/256265 Mark Sapiro posted a new comment: Manfred Hampl's suggestion in comment #2 will work if you set the list's Privacy options ... -> Recipient filters -> require_explicit_destination to No, but configuring the list as in the FAQ at <http://wiki.list.org/x/3YA9> is still preferable in my opinion as it will actually prevent unwanted posts regardless of how they are generated. -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0

Re: [Question #256265]: How do I make a list that Members can't Respond-All to?
by Manfred Hampl 28 Oct '14

28 Oct '14

Question #256265 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/256265 Manfred Hampl proposed the following answer: I have no experience with mailman, but I think this should be valid for all mail systems: If you put the group address into the "bcc:" field, every member in that list should receive the mail, but should not see the names of the other recipients, and should not see the name of the address list. So "respond to all" for them does not send mails to everyone. Depending on the mail system, you might have to put one name (your own one?) into the "to:" field, to meet a potential check that the "to:" field must not be empty. -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0

Re: [Question #256265]: How do I make a list that Members can't Respond-All to?
by Mark Sapiro 27 Oct '14

27 Oct '14

Question #256265 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/256265 Status: Open => Answered Mark Sapiro proposed the following answer: See the FAQ at <http://wiki.list.org/x/3YA9> for information on configuring an announcement/newsletter/one-way type of list. -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0