Re: [Mailman-Users] Fwd: Uncaught runner exception
Am 18.03.2019 um 17:06 schrieb Mark Sapiro: > On 3/18/19 2:29 AM, Lothar Schilling wrote: >> Exception in fixAuthor: D▒rthe Hinz - Fl▒chtlingsrat Nds. >> Mar 18 08:33:51 2019 (23745) lowercase value: >> 'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff' >> Mar 18 10:06:50 2019 (23745) Exception in fixAuthor: Philipp Millius >> (Fl▒chtlingsrat THR e.V.) >> Mar 18 10:06:50 2019 (23745) lowercase value: >> 'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf8\xf9\xfa\xfb\xfc\xfd\xfe\xff' > which is iso-8859-1 encoding of > 'abcdefghijklmnopqrstuvwxyzµßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýþÿ' and which > is the problem. > > I don't know why in testing string.lowercase does not return the above > string, but in the Python that's running ArchRunner, and presumably the > rest of mailman, string.lowercase has that value. This is what needs to > be fixed. The first step is possibly to do > > locate string.py There is just one /usr/lib64/python2.6/string.py yielding lowercase = 'abcdefghijklmnopqrstuvwxyz'. > And then look at all the ones you find to see which defines lowercase > that way and then figure out why the Python that runs Mailman uses that > one rather that the ones you see in testing. > > Also, > > which -a python points to /usr/bin/python as it is supposed to. > > may help find things. As your fix makes for the mails being archived maybe we should leave it at that. Thank you very much anyway for your patient helping me. -- 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] Fwd: Uncaught runner exception
On 3/20/19 5:31 AM, Lothar Schilling wrote: > > There is just one > > /usr/lib64/python2.6/string.py > > yielding > > lowercase = 'abcdefghijklmnopqrstuvwxyz'. You could try one more thing. Run Mailman's bin/withlist -i ... >>> from string import lowercase >>> lowercase (response) >>> import string >>> string (response) and see if that returns the extended lowercase and where it says lowercase comes from. -- Mark Sapiro The 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] Delivery errors and spam grading
Jim Dory writes: > On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull < > turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > (You probably should also disable the Digestable option in > > [Digest options] When I wrote this, I was thinking of a new list, in the context of personalization as a hack to limit the number of recipients per session. The point was to prevent users from setting their subscriptions to digest. As far as I know, there is no personalization of digest messages, so opting for digest would (theoretically) defeat personalization used to force one message per session operation. I don't know of any reason why digests would increase the probablity of either a bounce or being considered spam in and of themselves. > [Would disabling digestable] prevent issues like this? As others mentioned, it won't affect those specific issues. Both relate to the content of the post, not the rate or mode of multiple deliveries to the same host. Of course if the digest contains other posts, the recipients lose those too, but that's a choice we prefer to leave up to the subscriber herself. > if I were to disable it now, what happens to those members who are > using that option? I assume they just start automatically receiving > non-digest messages, but figured I should ask. That's a decision for the administrator. Our rationale for defaulting to no mail in this case is that people who select digest have explicitly opted for a small number of messages, and would likely be more annoyed by an unexpectedly large number of messages than by missing messages (which they can read in the archives in most cases). YMMV on that judgment -- of course, I suppose many would expect automatic switching to non-digest mode as you did -- but that's our rationale for a default to non-delivery. -- 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
