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

[MM3-users] Re: Weird behavior with Outlook and any MM3 List

by Mark Sapiro

On 11/1/23 09:42, Thomas Ward via Mailman-users wrote: > I'm seeing some *really* odd behavior with Mailman 3 and Microsoft Outlook clients (even Outlook Web Access). > > When messages come in with a subject prefix, of any way shape or form, Microsoft Outlook seems to *completely strip* the prefixes from any "reply" sent, which could be problematic. > > While the "In-Reply-To" header is still intact and such, Microsoft just seems to 'strip' prefixes from subject lines and that causes a problem in some cases. > > Has anyone observed this behavior before? If so, have you found any workarounds? This is a Microsoft/Outlook issue. As you note at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… this is just the way Outlook displays the message subject. I know of now way around this, but I don't use Microsoft MUAs. Does Outlook also strip the prefix from replies? This probably wouldn't matter for replies to the list as the list will add it back, but might be an issue for other direct recipients. Presumably, Outlook is looking at the [] around the prefix. You might try either dropping the brackets or using something else such as _My-List_ instead of [MyList]. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 11/30/22 08:41, Jan Eden via Mailman-users wrote: > > Changing the PATH value to a full path (/opt/mailman/fulltext_index) > and restarting mailman-web generates a different error: Yes, it should be a full path. >> ERROR 2022-11-30 16:38:37,953 1028315 django.request Internal Server Error: /archives/list/testing@lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest >> Traceback (most recent call last): >> File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner >> response = get_response(request) >> File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response >> response = wrapped_callback(request, *callback_args, **callback_kwargs) >> File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner >> return func(request, *args, **kwargs) >> File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 454, in reattach_suggest >> sugg_thread = msg.object.thread >> AttributeError: 'NoneType' object has no attribute 'thread' This says that searching the archive for this list for messages matching the current message subject returns None. It is probably a bug that we don't test for this, but what exactly are you doing? See the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for the only way I've been able to create an error like this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Strange URL in error message

by Mark Sapiro

On 7/17/24 11:47 PM, waps(a)tantalus.jena.thur.de wrote: > Hi Mark, > thanks for your patience. But now I get a little spinning wheel on the archive site, 3 "Error 500" in the Browser console and /var/log/mailman3/web/mailman-web.log shows repeatedly the error: > > ERROR 2024-07-18 08:34:38,261 1760 django.request Internal Server Error: /mailman3/hyperkitty/list/latex-team(a)latex-project.org/posted-to > Traceback (most recent call last): ...> File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 435, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > Since the archive is still quite empty and we have only one mailing lis, it would not be a big loss if it could resettet. But how I can do the, without resettinh the member data? Could it be that the Sqlite interface is not as stable as one the the "real databases"? As a superuser, you can go to /mailman3/hyperkitty/list/latex-team(a)latex-project.org/ and delete the archive. This will not delete the mailing list, and an empty archive will eventually be recreated, and new posts will be archived. Regarding the issue, see https://gitlab.com/mailman/hyperkitty/-/issues/504. Ensure that cron is running the Django hourly, daily, etc. tasks and that qcluster is running. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Mark Sapiro

On 6/18/21 3:34 AM, Shashikanth Komandoor wrote: > Thank you Mark for your immediate response. > > The below are the tracebacks I could find in the mailman log. > > *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: > expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback > (most recent call last): File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in > _one_iteration self._process_one_file(msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in > _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in > _dispose process(mlist, msg, msgdata, pipeline) File > "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in > process handler.process(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line > 59, in process addrs = getaddresses(msg.get_all(header, [])) File > "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = > COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str > instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: > 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* This is https://gitlab.com/mailman/mailman/-/issues/881 which is fixed by https://gitlab.com/mailman/mailman/-/merge_requests/841 which will be in Mailman 3.3.5 when it's released. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: There are currently no mailing lists!?

by Mark Sapiro

On 7/22/24 11:05, Christian via Mailman-users wrote: > I recently upgraded Debian 10 'buster' and when I logged in to Postorius in > the browser I got the ' Mailman REST API not available. Please start Mailman > core' message. So I started it up from the command line doing 'sudo -u > mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded > > Starting Mailman's master runner > Generating MTA alias maps > mailman@lists: > > Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists' > in my browser I get the message ' There are currently no mailing lists.' > Meanwhile their archives exist. Are the lists actually gone or ? I suspect the lists are not gone. I suspect mailman core is not using the correct database. I also note you started mailman core with sudo -u mailman /opt/mailman/mm/venv/bin/mailman start -f Are you using the Debian packages or did you install Mailman following https://docs.mailman3.org/en/latest/install/virtualenv.html Assuming the latter, what do the following show? sudo -u mailman /opt/mailman/mm/venv/bin/mailman lists sudo -u mailman /opt/mailman/mm/venv/bin/mailman info In particular does `mailman info` report the correct path to mailman.cfg and the appropriate database? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

[MM3-users] Re: bounce_score_threshold control

by Mark Sapiro

On 2/24/23 08:08, Tibor Molnar wrote: > > I have recently started receiving these mails from the system. First it was frighting me out that people's account got disabled, but actually nothing has happened, nobody got disabled. I however looking to figure out how can I control or change settings for this particular mechanism. Please advise me. > > emailname(a)example.it's subscription has been disabled on listname(a)domain.eu due to their bounce score > exceeding the mailing list's bounce_score_threshold. I'm not sure what you are looking at, but when you receive that message, it means the user's Delivery status has been set to Disabled by Bounces and the user will be sent `Bounce disable warnings` (default 3) warnings at intervals of `Bounce disabled warnings interval` (default 7 days) and if nothing is done the user will then be removed from the list. The notice you received, at least since Mailman 3.3.5, should contain a copy of the bounce DSN so you can determine if this user's address is actually undeliverable. Settings that control this are in the Postorius admin UI under Bounce Processing. The only other control is in mailman.cfg in the [mta] section where you can set `verp_probes: yes` See the docs at https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman 3 on Ubuntu 18.04

by Mark Sapiro

On 12/9/18 12:53 PM, Odhiambo Washington wrote: > On Sun, 9 Dec 2018 at 22:37, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> The nginx logs generally aren't too useful. Both Mailman core and Django >> write logs. Core's log is probably in var/log/mailman.log where is >> defined in mailman.cfg as var_dir. Django's log is defined in Django's >> settings in the LOGGING setting. >> > > Which file contains Django's settings? See <http://docs.list.org/en/latest/pre-installation-guide.html#django-knowledge>. >>> Ultimately I need to figure out: >>> 1. How the mailman queue runners are started and stopped >> >> mailman start >> > > Why not systemctl mailman start?? Just wondering, as that is what I am > seeing is common in Ubuntu. > Does this make the components start after a reboot? 'mailman start' is the command that starts Mailman. When you install Mailman, you typically create an init, upstart or systemd script to enable 'systemctl mailman start'. Presumably the Ubuntu mailman3-full package installs such scripts for Mailman and other components that need to be started at boot, but I'm not that familiar with this package. >>> 2. Migrate s few lists from Mailman2 to this Mailman3 >> >> mailman import21 >> <django management> hyperkitty_import >> > > Please show me where that is documented. I have to pull my lists from an > old machine to this new one. Those commands have --help options. There is also some documentation at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/import.h…> and <https://hyperkitty.readthedocs.io/en/latest/install.html#importing-the-curr…>. All of our formal documentation is at <http://docs.list.org/en/latest/>. > So, when you talk about Django settings, you are referring to mailman.cfg > file??? :-) No. I am talking about a file often named settings.py and which my in turn import a file named something like settings_local.py. See my first answer above. > I have spent all my weekend till now, trying to figure all this out. Life > seems a little easier with mm2.x .... I expect some of that is just what you're familiar with, but yes, Mailman 3 is more complex than Mailman 2.1 just as Mailman 2.1 is more complex than a Bcc: list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: "Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all'

by Mark Sapiro

On 05/28/2017 12:40 PM, Simon Liebold via Mailman-users wrote: > I didn't find a 'delete message' button. But "Delete this thread" went > straight to the 500. Both, Hyperkitty and django-mailman are up-to-date > with master. 'Delete this message' is in the 'message' view. "Delete this thread" is in the 'thread' view. > ERROR 2017-05-28 13:04:14,496 29835 django.request Internal Server > Error: > /hyperkitty/list/simsimmer@lists.simonliebold.de/thread/4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM/delete > Traceback (most recent call last): > File > "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/core/handlers/exception.py", HyperKitty requires Django<1.11. The comment in the requirements in setup.py implies this is only a django-haystack requirement "Django>=1.8", # Don't upgrade to 1.11 until django-haystack supports it: # https://github.com/django-haystack/django-haystack/pull/1499 "Django<1.11", but since it works for me with Django 1.10, you might want to try that. ... > File > "/opt/mailman/venv-2.7/local/lib/python2.7/site-packages/Django-1.11rc1-py2.7.egg/django/forms/models.py", > line 1168, in __deepcopy__ > result.queryset = self.queryset.all() > AttributeError: 'NoneType' object has no attribute 'all' In particular, this looks like Django 1.11 bug <https://code.djangoproject.com/ticket/27975>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

On 10/11/2018 03:48 AM, Henrik Rasmussen wrote: > > Before running /usr/bin/docker exec mailman-core mailman digests --periodic --verbose > > Every 2.0s: ls -l;grep "Test 20181011" digest.mmdf;tail /var/log/mailman/core/smtp.log Thu Oct 11 12:23:32 2018 > > -rw-rw---- 1 100 nogroup 103433 Oct 10 14:36 digest.1.7.mmdf > -rw-rw---- 1 100 nogroup 155540 Oct 11 11:29 digest.1.8.mmdf > -rw-rw---- 1 100 nogroup 104002 Oct 11 12:21 digest.mmdf ... > After running /usr/bin/docker exec mailman-core mailman digests --periodic --verbose > > Every 2.0s: ls -l;grep "Test 20181011" digest.mmdf;tail /var/log/mailman/core/smtp.log Thu Oct 11 12:44:45 2018 > > total 372 > -rw-rw---- 1 100 nogroup 103433 Oct 10 14:36 digest.1.7.mmdf > -rw-rw---- 1 100 nogroup 155540 Oct 11 11:29 digest.1.8.mmdf > -rw-rw---- 1 100 nogroup 104002 Oct 11 12:21 digest.1.9.mmdf The mailman digests --periodic command renames the digest.mmdf file to (in this case) digest.1.9.mmdf and then queues an entry in the digest queue for DigestRunner to actually build the digests from the digest.1.9.mmdf file, send them and remove the digest.1.9.mmdf file. Something is going wrong in this process in DigestRunner. Is DigestRunner running? Is there anything in Mailman's digest or shunt queues? Is there anything logged in Mailman's 'mailman' log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Importing users and mas settings "Moderation Action"

by Mark Sapiro

On 5/19/22 06:17, bob B via Mailman-users wrote: > I imported email lists and users to version 3 from version 2. One of my lists all the users are set to 'Hold for moderation" for "Moderation Action". I assume this is because they were set to moderation on mailman 2? Correct. > But if I mass subscribe users via the Gui in mailman 3 then their default "Moderation Action" is set to "none" so I assume it follows list default, is that a correct assumption? Yes. > I believe there is no way to import mass users and set their "Moderation Action" at the same time is this correct? Wasn't that possible in mailman 2? That's correct, and that was also the case in Mailman 2.1 . > is there a way to change all their user's "Moderation Action" for a list in bulk? You could do it with `mailman shell`, but not in Postorius. > So it looks like for any users I mass subscribe, "Moderation Action" will be set to "none" and if I want to change that I have to do it manually for each user? If you are a list owner whose only access is via Postorius, that's correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Search results for query "sapiro"