Re: [Mailman-Users] Membership search changes?

2014-10-31 Thread Mark Sapiro
On 10/31/2014 07:32 AM, Jim Popovitch wrote:
 
 Did something change recently with Membership searches in mm-2.1.18-1?
  It seems that the search text no longer searches the complete
 subscriber list, rather only the selected (i.e. A, B, C, D, etc)
 grouping.  I searched the bug reports and didn't see any thing
 related.


Nothing changed as far as I can tell. The search still works globally
for me on my production server which actually runs the 2.2 branch +
additional local mods. My development boxes don't have enough list
members to test.

If the number of search results is = admin_member_chunksize, the
results are all on one page with no 'alphabet' header. If the number of
search results is  admin_member_chunksize, the results will be broken
by first character with a header like the full list. Selecting a first
letter should continue to display only members that match the search.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
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/archive%40jab.org


Re: [Mailman-Users] Membership search changes?

2014-10-31 Thread Jim Popovitch
On Fri, Oct 31, 2014 at 1:44 PM, Mark Sapiro m...@msapiro.net wrote:
 On 10/31/2014 07:32 AM, Jim Popovitch wrote:

 Did something change recently with Membership searches in mm-2.1.18-1?
  It seems that the search text no longer searches the complete
 subscriber list, rather only the selected (i.e. A, B, C, D, etc)
 grouping.  I searched the bug reports and didn't see any thing
 related.


 Nothing changed as far as I can tell. The search still works globally
 for me on my production server which actually runs the 2.2 branch +
 additional local mods. My development boxes don't have enough list
 members to test.

 If the number of search results is = admin_member_chunksize, the
 results are all on one page with no 'alphabet' header. If the number of
 search results is  admin_member_chunksize, the results will be broken
 by first character with a header like the full list. Selecting a first
 letter should continue to display only members that match the search.

Hi Mark,

Hmm.  If I set admin_member_chunksize  than subscribers then global
search works.  If admin_member_chunksize  subscribers, search only
works on the selected (or default) chunk.  I have a moderately
modified mailman system so it's probably something not working
correctly after recent patches.

Thanks anyways,

-Jim P.
--
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/archive%40jab.org


Re: [Mailman-Users] MM3/Delivery Problem

2014-10-31 Thread Guillaume Libersat
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-develop...@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.15...@mailman.ulists.org smtp to t...@ulists.org
 for 1 recips, completed in 0.0919508934021 seconds
 Oct 30 15:34:36 2014 (1387)
 20141030143436.1389.15...@mailman.ulists.org post to t...@ulists.org
 from test-requ...@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=gliber...@unisson.co, size=718, nrcpt=1 (queue active)
 Oct 30 15:34:36 mailman postfix/lmtp[2526]: CEF7719628BC:
 to=t...@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-boun...@ulists.org to the list member?


-- 
http://sigill.org

--
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/archive%40jab.org


Re: [Mailman-Users] MM3/Delivery Problem

2014-10-31 Thread Barry Warsaw
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/archive%40jab.org