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

[MM3-users] Re: MM3 does not receive gmail-Members!

by Mark Sapiro

On 4/24/23 1:58 PM, Paul Brenner wrote: > Hallo > I need help! > My MM3 sends mails via a list. However, no mails arrive at all gmail > recipients. > These mails also do not end up in the spam or junk folders. > What do I have to do? If you have access to the outgoing MTA logs, what do they show about mail to these gmail recipients? Without access to these logs, you can set Process Bounces and Notify owner on bounce increment both to Yes in Postorius -> Bounce Processing and you should receive notices when mail is reported as undeliverable. These notices or the log entries should give a reason for non-delivery. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Message shows up individually but not in the thread

by Mark Sapiro

On 11/04/2017 01:19 AM, Marvin Gülker wrote: > Am 03. November 2017 um 12:35 Uhr -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: >> Are you running all of Django's periodic tasks? > > They are running. This is the excerpt from /etc/crontab: ... > Obviously, mailman-suite is installed at /home/mailman/mailman-suite and > owned by user 'mailman', with the actual Django project in the > subdirectory 'mailman-suite_project', just as cloned from the Git > repository. The only difference from the official guide here is that I > took the liberty to place Mailman into two virtualenvs (a Python2 one > for the Django project, and a Python3 one for Mailman-Core*). > > There are no errors reported with this in /var/log/cron.log. And before > you ask, the task queue is running as well. The uWSGI config has this: > > # Setup the django_q related worker processes. > attach-daemon = ./manage.py qcluster > > And the qcluster process shows both up in the process list and is > happily logging away in the uWSGI log. There is a possibly related issues at <https://gitlab.com/mailman/hyperkitty/issues/151> and some older ones at <https://gitlab.com/mailman/hyperkitty/issues/131> and <https://gitlab.com/mailman/hyperkitty/issues/149>. I'm sorry I can't offer more help than that at this point. > * It'd be great if the mailman-suite was moved to Python 3 at some > point. That way one wouldn't need two separate virtualenvs. We're working on moving Postorius and HyperKitty to MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Importing mbox files into hyperkitty since date

by Mark Sapiro

On 6/20/19 3:08 AM, andrew.bernard(a)gmail.com wrote: > Well, reading the hyperkitty command source code, looks like it uses dateutil.parser, which shoudl read pretty much any date format (?). > > This is what happens: > > $ django-admin hyperkitty_import -v 2 -l jackrail(a)list.jackrail.org --since "2010-01-01 00:00Z" /tmp/jackrail(a)list.jackrail.org-2019-07.mbox > > CommandError: No such file: 00:00Z This appears to be a bug in Django's BaseCommand class which somehow separates '--since "2010-01-01 00:00Z"' into '--since 2010-01-01' and '00:00Z' despite the quotes. As a workaround, you can use '--since "2010-01-01/00:00Z"' which doesn't contain the problematic whitespace and which is acceptable to dateutil.parser.parse(). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: mailman import21

by Mark Sapiro

On 10/11/20 7:41 AM, Brian Carpenter wrote: > Does the import21 script also import custom templates? No. > Are these custom > templates contained in the config.pck file? No. They are in the same MM 2.1 directory as the config.pck, but in a sub-directory for the language code, i.e. lists/LISTNAME/LC/ > Are there any known issues > with the importing of mm2 templates into a mm3 environment? The replacements are different. i.e., things like %(email)s and %(listname)s become $user_email and $short_listname. Also, there are some MM 2.1 templates that have no MM 3 equivalent. Also, things like message and digest headers and footers that are MM 2.1 list attributes that are templates in MM 3, although import21 tries to handle those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Question about "envelope-from" header

by Mark Sapiro

On 9/12/23 10:45 PM, Stephen J. Turnbull wrote: > Stephen Daniel writes: > > > Will bounce processing still work? > > I think so. Pretty sure bounce processing on the bouncing side > doesn't care who the envelope sender is, it is based on the RFC 822 > sender, which is the Sender header field if set and the From field if > Sender is not present. Actually, I think all modern MTAs will return DSNs (bounces) to the envelope sender (MAIL FROM address)[1] which for list mail is the, possibly VERPed, listname-bounces address. If this is altered to a different address, bounce processing won't work. [1] See https://www.rfc-editor.org/rfc/rfc5321.html#section-4.4 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/23/24 13:23, Gerald Vogt wrote: > > I don't quite understand the relevance of the user accessing the > localhost tcp port. Any local user can do that. I am trying to duplicate what Mailman does in an attempt to find the issue. > I can access the template content with > > curl > http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… > > as well as > > curl > http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… > > as any user on the mailman server. How about ``` curl -A 'python-requests/2.32.3' http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… ``` as the Mailman user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: Python 3.13 compatibility

by Mark Sapiro

On 1/23/25 14:08, peter--- via Mailman-users wrote: > > Hi Folks, > I'm running the Debian-packaged mailman3 (version 3.8) which is a > little behind the current 3.9 release ... > Debian is now shipping Python 3.13 in 'sid'. > > https://docs.python.org/3/whatsnew/3.13.html#id4 > says: > Remove the ability to use Path objects as context > managers. This functionality was deprecated and has had no > effect since Python 3.9. (Contributed by Barney Gale in > gh-83863.) > > As a result, I'm hitting tracebacks from many operations where > pathlib.Path objects are used as context managers, like this one: This is https://gitlab.com/mailman/mailman/-/issues/1190 fixed for Mailman 3.3.11 by https://gitlab.com/mailman/mailman/-/merge_requests/1309 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 12/30/22 03:25, Jan Eden via Mailman-users wrote: > > On minor issue: All user names with > non-ASCII characters appear with quoted-printable encoding (e.g. > =?utf-8?q?J=C3=BCrgen?=). Is there a way to output UTF-8 instead of QP? I just created https://gitlab.com/mailman/mailman/-/issues/1048 for this. I think this patch ``` --- a/src/mailman/commands/cli_members.py +++ b/src/mailman/commands/cli_members.py @@ -104,10 +104,10 @@ def display_members(ctx, mlist, role, regular, digest, if nomail is not None: if member.delivery_status not in status_types: continue - if email_only: + if email_only or not address.display_name: print(address.original_email, file=outfp) else: - print(formataddr((address.display_name, address.original_email)), + print(f'{address.display_name} <{address.original_email}>', file=outfp) ``` (line may be wrapped) will fix it. -- 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: Postorius web issues after upgrading mailman 3

by Mark Sapiro

On 10/19/21 2:33 AM, Tibor Molnar wrote: > /var/lib/mailman3/web/static/hyperkitty > > /usr/local/lib/python3.8/dist-packages/hyperkitty/static/hyperkitty If you examine the source of your HyperKitty pages that have the issue, what do you see for the hrefs in the `<link rel="stylesheet"` tags in the <head> section. Also, I don't know if it is significant or not, but https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade says to run ``` (venv) $ mailman-web compress (venv) $ mailman-web collectstatic ``` I always run those in the other order. I suggest you do mailman-web collectstatic --clear mailman-web compress (or whatever your django admin command is) in that order and see if that helps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Turned on archiving and it is not working

by Mark Sapiro

On 6/9/22 12:47, bob B via Mailman-users wrote: > Mark, > > Thanks, So how do I check the version of mailman-hyperkitty? I thought that was the HyperKitty version 1.3.5. that was displayed in the web interface, but I assume that mailman-hyperkitty is something different? Yes. mailman-hyperkitty is a shim between Mailman core and HyperKitty. Your mail message has `` File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message` ``` The fact that it is line 154 says it is 1.1.0. You need to upgrade mailman-hyperkitty. I don't know how to do that in your Docker container. If you can run pip ``` pip install --upgrade mailman-hyperkitty ``` should do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Search results for query "sapiro"