Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/28/2017 06:11 AM, Henrik Rasmussen wrote: > Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' > Sep 25 07:20:57 2017 (35) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/usr/local/lib/python3.6/site-packages/mailman/core/pipelines.py", line 53, in process > handler.process(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 174, in process > mlist, msgdata, subject, prefix, prefix_pattern, ws) > File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 72, in all_same_charset > chunks.append(chunk.decode(charset)) > AttributeError: 'str' object has no attribute 'decode' > Sep 25 07:20:57 2017 (35) SHUNTING: 1506324057.584686+a13cc47dc1027a0cfb00c892396b3ba7efabb3dc This is <https://gitlab.com/mailman/mailman/issues/359> It is fixed in the current source by <https://gitlab.com/mailman/mailman/commit/e92359323cda1fb118415c2ccb6967979…>. > In addition, the log contains other trace backs that might or might not associate to this problem: > > Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) > Sep 24 21:11:28 2017 (34) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/connection.py", line 84, in sendmail > results = self._connection.sendmail(envsender, recipients, msgtext) > File "/usr/local/lib/python3.6/smtplib.py", line 855, in sendmail > msg = _fix_eols(msg).encode('ascii') > UnicodeEncodeError: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) > Sep 24 21:11:28 2017 (34) SHUNTING: 1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66 This may be a bug. The msgtext argument in 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed to be a string containing only ascii characters. I'm interested in what's in Mailman's var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. You may be able to print the contents with Mailman's bin/mailman queue var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck There shouldn't be raw unicodes like \udcea in the text of the message, but we should defend against that anyway. > Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' Same as above. > Sep 25 09:19:58 2017 (30) deque: do_confirm_verify > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 420, in _step_send_confirmation > raise StopIteration > StopIteration This is normal. It is not an issue. > Sep 26 09:21:07 2017 (36) deque: > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 217, in _step_sanity_checks > MemberRole.member) > mailman.interfaces.member.AlreadySubscribedError: sender(a)foo.bar is already a MemberRole.member of mailing list listname(a)listserver.foo.bar This appears to be an attempt to subscribe someone who's already a member. This should have resulted in an appropriate message to the attempted subscriber. > Sep 26 13:32:29 2017 (30) Uncaught runner exception: > Sep 26 13:32:29 2017 (30) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/command.py", line 196, in _dispose > mlist, msg, msgdata, parts, results) > File "/usr/local/lib/python3.6/site-packages/mailman/commands/eml_confirm.py", line 53, in process > mlist).confirm(token) > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 540, in confirm > PendableUnsubscription.PEND_TYPE) > AssertionError I'm not sure about this one. a message has been sent to the LISTNAME-confirm address to confirm a subscription or unsubscription. The confirmation token exists but is neither a pending subscription or unsubscription token. > Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message > g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write > msg.replace_header('content-transfer-encoding', munge_cte[0]) > File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header > raise KeyError(_name) > KeyError: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312 As I said in a prior reply, this is <https://gitlab.com/mailman/mailman/issues/256>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: Topics - Tags

by Mark

On 2024-03-23 06:36, Mark Sapiro wrote: > On 3/21/24 21:10, Mark wrote: >> Hi, >> >> I'm reading the docs on "Message tagging" >> (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) >> as saying shell access is needed to: (a) enable topics, and (b) write >> the keywords. >> >> In Mailman 2 there is an Admin web UI for "Topics". Is there such a >> web UI that can be enabled in Mailman 3 so that the list owners can >> create topics (tags) in their lists? > > > At this point, topics are not exposed in REST. Managing them via > Postorius first requires updating the REST API to read and set the > topic attributes and then updating Postorius to display/set them. > > Further, there is currently no implementation for list member topics > of interest either in Mailman core or the REST API. I.e., there is no > way for a list member to indicate topics of interest. > Thank you for this information Mark. Best, Mark

2 years, 6 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/20/22 07:54, Rainer Herbst wrote: > > The user suggested that the problem is caused by a line containing only > > "-- " somewhere in the text, but I can not confirm this. This is very unlikely. A very large portion of the mail processed at Mailman sites has "-- " in it because that is the conventional "start of .signature" marker, and much of that is multipart and even signed nowadays, yet we've never seen a problem with it. > > Please find enclosed the refused mail (anonymized). > > That message has no defects. In particular, it has no Content-Transfer-Encoding in the header of any multipart part, which is the defect reported before. I guess there's no list of defects either in the returned message or in the MTA logs? It seems strange that the message has no Received headers. Is this normal for aip.de address to aip.de address mail? Or is it a sent file copy of the sender or something like that? Steve

4 years, 5 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/12/2016 09:26 PM, Barry Warsaw wrote: > On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: > >> It is the intent that Postorius will eventually expose all these >> settings. We're not there yet. At present you could possibly do this by >> interacting with mailmanclient, although I'm not certain the settings are >> exposed there. > > I'm not sure if they're exposed in mailmanclient, but they are exposed in the > core's REST API, on the member resource. It's the `delivery_mode` attribute > and it takes as legal values one of 'regular', 'plaintext_digests', > 'mime_digests', and 'summary_digests' (IOW, the enum item names for the > DeliveryMode enum). They are exposed in mailmanclient and are used in postorius. They can be found in the users personal subscription settings https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > Cheers, > -Barry > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

10 years, 5 months

[MM3-users] Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 18:05 schrieb Mark Sapiro: > On 8/27/20 8:07 AM, Sebastian Hagedorn wrote: >> >> Right now everything is running as root (except for Apache). I realized >> too late that I should've used a mailman user. Could that be the reason >> for the issue? > > Since you have determined it was a browser issue, that probably isn't > the reason, but running Mailman as root is a bad idea in general for > security reasons. Thanks, I'm aware, and I'm not going to on a production system. This installation is just a trial run. > I don't know if it's relevant or not, but I have just recently had > issues with Firefox not working properly on two different (not mailman) > web sites, and these issues were fixed by clearing cookies and cached > data from the affected sites and restarting Firefox. I can confirm that that worked in my case as well.

6 years, 1 month

[MM3-users] Re: Mailman not able to process "big" requests

by Darren Smith

Our installation at https://lists.rootsweb.ancestry.com has around 33,000 lists and somewhere around 1.5 million members. We have lists with 5,000+ members. Note that I haven't tried any mass subscriptions. When we upgraded from mailman 2 to mailman 3, we used the old .pck files and ran the import on each of the lists. It did take about 6 weeks to do the full import all 33,000 lists. I'm not joking. As for sending messages - there isn't any problem sending that many messages out, but then we are also not trying to subscribe list members at the time. We are, though, in the process of importing the old archives from our old mailman 2 system. This doesn't seem to affect the rest of the system. We have seen some inefficiencies in the new system, such as the front page of postorius - loading all of the information for 200 lists (if the user set the "lists per page" to 200) was bringing down the system. We have our own metadata system to be able to search for lists by state/region/surname (ours is a genealogy mailing list system), so we had to replace the front page with our own "find a list" functionality. The other main problem was the page where a user can see what lists they subscribe to. That page was also a denial of service if the user had several hundred lists they are subscribed to. And for a genealogy mailing list system, this is common. We have actually ended up creating our own API layer (only accessible on the local machine) and make certain calls to it for the most painful of the issues. One of these days (when we get a moment to breathe) we are going to post some of our changes to the project so that we can ditch our own API and just use the internal REST API. To be fair, the inefficiencies are not necessarily with mailman or the rest API itself - but with Postorius making hundreds of calls to load a single page. Though if the API supported loading multiple lists at once instead of having to load them serially, that might help as well. So while we have not seen any timeout issues on the call to mass subscribe users, we HAVE found several other calls that are effectively a denial of service and have gotten around them ourselves, with plans to contribute to the project in the near future. -Darren On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/24/2018 12:36 AM, Abhilash Raj wrote: > > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: > > >> We also have a problem with sending out emails to "large" (>50) groups, > >> as they seem to not getting sent out at all. Do you have any idea what > >> the problem here could be? > > > > Which MTA are you using? What do you see in mailman's logs and MTA's > logs? > > > > I haven't seen this kind of problem before with Mailman 3. This very > list is hosted using Mailman 3 and I believe has more than 50 subscribers. > > > Nor have I seen this issue. This list currently has 158 non-digest > members. There are several @python.org Mailman 3 lists with over 100 > non-digest members including the active yt-users(a)python.org list with > 301 members, and I have gotten no reports of an issue like this. > > Also, there are over 600 lists at <https://lists.fedoraproject.org/>, > and I don't think this is an issue there either. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 5 months

[MM3-users] Re: cache files?

by Dave McGuire

On 7/12/21 10:45 PM, Mark Sapiro wrote: >> Hi folks. I'm seeing quite a few .css files, thousands of them >> totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. >> Some of them date back to when I set up the mm3 instance a few years ago. >> >> Is this expected, or am I missing a cron job or something to clean >> them up? > > This is not expected. I don't see it on the instances I manage. > > In the `static` directory, I see > ``` > $ du -h -d 1 > 1.7M ./admin > 12K ./facebook > 68K ./django_extensions > 4.0K ./browserid > 68K ./django-mailman3 > 2.6M ./postorius > 12K ./paintstore > 1.6M ./rest_framework > 5.2M ./hyperkitty > 404K ./CACHE > 12M . > $ find -type f|wc > 401 401 18253 > ``` > > I think when you run the Django admin `collectstatic` command, you need > to specify the `--clear` option. Interesting, I know nothing of that command. Is that something that should be run periodically? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

5 years, 3 months

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 19:33, Mark Sapiro wrote: > On 8/6/21 10:28 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > >> Thanks. Now it's no showing errors (and nothing at all) but >> apparently it does nothing. The non mebers of the list (the few that >> remains: I've been deleting one at a time from the web) aparently >> still are there.. >> >> Knowing the correct procedure will ease me to try tomorrow with a >> clean head. > > It doesn't report anything, and if you don't commit() or exit with > control-D, any changes will be rolled back. I think I did a typpo. (forgot to add "()" after the "commit" sentence). And exit with quit() maybe not helps. I've done it exactly as you wrote it and it worked like a charm. Thank you very very much > > What does > > list(m.nonmembers.members) > > show before doing the unsubscribe() and commit() and then what after? >

5 years, 2 months

[MM3-users] Re: Is logging.subscribe working in /etc/mailman.cfg?

by Alan So

Mark Sapiro wrote: > On 12/11/18 2:11 AM, ktso(a)cuhk.edu.hk wrote: > > I have put the following in /etc/mailman.cfg and restart mailman. An > > empty file can be created but nothing can be logged when admin or non-member > > subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in > > mailman.log and smtp.log. Thanks. > > > > [logging.subscribe] > > path: subscribe.log > > level: debug > > The above is correct. As far as not seeing things in the log, very > little is logged in the subscribe log. Only (un)subscription requests > held for moderator approval and moderator approval of held unsubscribes > but not subscribes. > > In other words, unless your list's subscription police includes > 'moderate' nothing will be logged in subscribe.log. It looks like there is only a subscription policy but no unsubscription policy. I can't find anything even by exporting the settings using Python mailman client. Is it correct?

7 years, 10 months

[MM3-users] Re: Mailman web interface / uwsgi

by Jan Eden

On 2022-11-26 22:59, Mark Sapiro wrote: > > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > > files when using the virtualenv installation instructions > > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, > not mailman-web. If you want, you could put mailman-hyperkitty.cfg in > /etc/mailman3/ by putting > ``` > configuration: /etc/mailman3/mailman-hyperkitty.cfg > ``` > in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really > belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. I see. But the mailman.cfg is placed in /etc/mailman3, and this file also belongs to the core, doesn't it? In any case, I changed the configuration parameter for [archiver.hyperkitty] as you suggested and all settings are in one place now. I will post two more questions to this list today, and promise to stop spamming you afterwards. :) Thanks again, Jan

3 years, 10 months

Search results for query "sapiro"