The problem is now fixed... I don't really know what happened but it seems it was related to sqlite3 and database locking.

Thanks for helping, if I manage to find what really happened, I'll file a bug report.

Cheers,

Guillaume

Le 30/10/2014 20:13, Mark Sapiro a écrit :

On 10/30/2014 07:48 AM, Guillaume Libersat wrote:

...

We're running a mailman 3.0.0b at ulists.org and so far it was working quite well. Since a few days, email delivery seems to be broken, but only for the posts, not bounces. When someone subscribes, he gets the welcome message. When someone posts, nothing is delivered. Same when posting from hyperkitty.

I'll note a few things below, but this list is mostly still oriented towards Mailman 2.1. The MM 3 folks pay much more attention to the mailman-developers@python.org list and the #mailman irc channel on freenode.net.

...

Here's what happens when en email is sent to a list:

On the MM3 side:

Oct 30 15:34:36 2014 (1387) 20141030143436.1389.15086@mailman.ulists.org smtp to test@ulists.org for 1 recips, completed in 0.0919508934021 seconds Oct 30 15:34:36 2014 (1387) 20141030143436.1389.15086@mailman.ulists.org post to test@ulists.org from test-request@ulists.org, 1177 bytes

This says the post was sent to 1 recipient. If there's nothing in Mailman's smtp-failure log, it was accepted by the outgong MTA.

...

and on the smtp side:

Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC: from=glibersat@unisson.co, size=718, nrcpt=1 (queue active) Oct 30 15:34:36 mailman postfix/lmtp[2526]: CEF7719628BC: to=test@ulists.org, relay=127.0.0.1[127.0.0.1]:8024, delay=0.14, delays=0.0 6/0.04/0/0.04, dsn=2.0.0, status=sent (250 Ok) Oct 30 15:34:36 mailman postfix/qmgr[7675]: CEF7719628BC: removed

This is the incoming post being delivered to Mailman. We already know that succeeded.

...

Any idea of what I should check?

What is in the outgoing MTA logs for the post from test-bounces@ulists.org to the list member?

Awesome! Do you think it will be easy to migrate from an existing sqlite database to a postgres one through SQLAlchemy? I tried to do it manually a few days ago... and it took me such a longgggg time writing ah-hoc scripts for almost nothing (the database is not really usable). I'm really interested in testing the new backend if you need testers :)

Cheers,

Guillaume

Le 31/10/2014 19:55, Barry Warsaw a écrit :

On Oct 31, 2014, at 07:47 PM, Guillaume Libersat wrote:

...

The problem is now fixed... I don't really know what happened but it seems it was related to sqlite3 and database locking.

Thanks for helping, if I manage to find what really happened, I'll file a bug report.

Very soon (perhaps this weekend) I will land the port to SQLAlchemy as our ORM layer for MM3 in the trunk. This is based on great work by Abhilash and Aurelien. There have been some reports of SQLite locking problems in MM3 and it will be interesting to see whether the port from Storm to SA will fix that.

Cheers,

-Barry

Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/glibersat%40sigill.org