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

[MM3-users] Re: Flooded non-members with "prvs=<number>=<mail>"

by Mark Sapiro

On 12/22/24 04:35, Torge Riedel via Mailman-users wrote: > > I checked the non-members list of all my mailman3 lists and found a lot > entries like "prvs=<number>=<mail>", the <mail> is always an address > from @freenet.de > > A quick research mentions something related to bouncing and that such > mails should be blocked/filtered. But no further details. > > Can you give a hint where I need to change what to block such mails and > avoid that such entries floods the non-members list? If these are in fact bounces, the mta at freenet.de is sending bounce DSNs to the list address instead of (or possibly in addition to) the list-bounces address which is the envelope sender of the mail from Mailman. This behavior is wrong, but it is beyond your control. If you can identify a pattern in the From: address that would match these and only these mails, you could probably configure the incoming MTA to discard them. E.g., for Postfix, see https://www.postfix.org/header_checks.5.html You might think of using Mailman's Header filters to discard the messages, but this won't keep the nonmembers from being created as the creation happens before any of those checks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Debian 12 postfix errors: "warning: connect to transport private/lmtp: Connection refused" and "status=deferred (mail transport unavailable)"

by Mark Sapiro

On 4/7/25 12:00, Philip Bondi wrote: > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: 127.0.0.1 > lmtp_port: 9024 Why are you setting this? Testing uses port 9024 to avoid conflicts, but the default port 8024 should be used for production. > [799] # postconf -n ... > virtual_mailbox_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp Why do you have this? It may well be the issue. > ebill(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-bounces(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-confirm(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-join(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-leave(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-owner(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-request(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-subscribe(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > ebill-unsubscribe(a)systemdatabase.ca lmtp:[127.0.0.1]:9024 > > [797] # telnet localhost 9024 > Trying ::1... > Connection failed: Connection refused > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > 220 shackleton12.systemdatabase.ca GNU Mailman LMTP runner 2.0 > QUIT > 221 Bye > Connection closed by foreign host. It looks like you can connect to port 9024 in this way. However I recommend removing `lmtp_port: 9024` from your mailman.cfg and rerunning `mailman aliases` to regenerate the postfix maps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 5/7/19 6:19 AM, Henrik Rasmussen wrote: > Having set the Filter content to Yes - regardless of other setting in the "Alter Messages" tab, make a HTML message come out empty. I can replicate this on my test list. I don't understand the question? Are you asking why the log contains "invalid FilterAction: discard. Treating as discard"? If so, that's a bug. See <https://gitlab.com/mailman/mailman/issues/592>. If you are asking why the message is empty after filtering and discarded, It is presumably because it is a text/html message as opposed to a multipart/alternative message with text/plain and text/html alternative parts. > I have tried debugging by changing each setting one-by-one and sending the user's mail, but no change makes the mail come out with a content. However setting "Filter content" to "no" makes the mail come out okay. There are list attributes filter_types and pass_types (also filter_extensions and pass_extensions, but those probably aren't relevant here) which affect this and which aren't exposed in Postorius. See <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/filterin…> for more info of content filtering. Presumably, the combination of filter_types and pass_types is not allowing text/html. You need to examine these settings in mailman shell, e.g. list(m.pass_types) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by Mark Sapiro

On 12/8/20 9:05 AM, matthew(a)alberti.us wrote: > > From what I've been reading, it seems like Mailman3 expects > the mysql database to use UTF8 encoding. It appears, by default, that when > using the docker-mailman containers, that the character set is set to > latin1. This may explain why there are lots of import errors, and maybe also > why there are a lot of errors when threads are deleted in hyperkitty's UI. > > > > Is it the case that UTF8 is the preferred character set? I > also saw some threads indicating that maybe utf8mb4 is more preferred. I'd > like to try to change the character_set on the database, if that is > advisable. You want the MySQL encoding for the Mailman database to be utf8mb4. If not, as Ruth says, you will have issues with 4-bute utf-8 encodings. See <https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec…> > Also, is Hyperkitty 1.3.4 officially released? I see that the > list.org instance is using it, but the latest announce I've seen is for > 1.3.3. No, it is not. lists.mailman3.org and mail.python.org both run the HEADs of the GitLab branches so they are generally ahead of the latest releases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: after upgrade: OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode

by Mark Sapiro

On 1/31/24 08:02, Hans Mayer via Mailman-users wrote: > > > Dear All, > > recently I did a system os upgrade debian 11.8 -> 12.4 / bullseye -> > bookworm > > This did also upgrade Mailman3 version 3.3.3 -> 3.3.8 as a used the > packages which came with Debian OS. > > Initially after the upgrade I had some troubles with the MM3 services to > start, but I fixed this. > > Now almost everything is running. Only the Archives are not working. Issues with the Debian poackage should be reported to Debian. See <https://wiki.list.org/x/12812344>. > The browser shows a server error, when I look at the mailman-web.log I see > > ERROR 2024-01-31 15:14:14,403 2699563 django.request Internal Server > Error: /mailman3/hyperkitty/ > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", > line 84, in _execute > return self.cursor.execute(sql, params) > File > "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", > line 423, in execute > return Database.Cursor.execute(self, query, params) > > sqlite3.OperationalError: no such column: > hyperkitty_mailinglist.archive_rendering_mode You need to run the Django admin (however that's spelled in the debian mailmanweb package) `migrate` command (and probably others, e.g., `collectstatic`, `compress`, `compilemessages`). -- 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: Welcome message template errors

by Mark Sapiro

On 4/21/24 19:15, Mark wrote: > > And the site-owner receives an email with ... > > ==== > Internal Server Error: /mailman3/lists/ > DoesNotExist at /mailman3/lists/ > Site matching query does not exist. > Request Method: GET > Request URL: http://<REDACTED-PUBLIC-IPv4-ADDRESS>/mailman3/lists/ The above means you have to add <REDACTED-PUBLIC-IPv4-ADDRESS> to the list of ALLOWED_HOSTS in your Django settings, but see below. > Django Version: 4.2.11 > Python Executable: /opt/mailman/venv/bin/python3 > Python Version: 3.11.2 > ... etc ... > === > > Regarding the second line in the email - my thinking is that it should > be looking in "/opt/mailman/mm/var/lists" and not "/mailman3/lists/". It's talking about the path in the URL, not a path in the file system. > The error doesn't occur if the is no custom "Welcome message" template - > ie. the user is sent the default welcome message. I think you must be setting the custom template via Postorius and your Django setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. It should be set to the scheme and host you use to access Postorius. I.e, if you normally access Postorius via something like https://example.com/mailman3 set POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' It is probably now set as POSTORIUS_TEMPLATE_BASE_URL = 'http://<REDACTED-PUBLIC-IPv4-ADDRESS>' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: templates

by Mark Sapiro

On 5/5/23 15:27, Christian via Mailman-users wrote: > Okay I sent a test message this morning and subscribers are reporting they > did not receive it. The smtp.log shows 'smtp to > degrowcali(a)lists.ccalternatives.org for 25 recips, completed in > 3276.275292634964 seconds' (see below) > I alone received it however and it is listed in the archive. Below is the > excerpt from smtp.log. Two of my 5 lists are exhibiting this behavior, while > 2 other lists are working normally. Please advise. Thank you. That message says Mailman delivered the message for 25 recipients to the outgoing MTA. If only one recipient received it, you first need to check the outgoing MTA's logs to see whether the message was delivered to the recipient's mail servers or not. Those logs should indicate that either the message was delivered to each recipient's first hop mail server or not. If not, there should be a reason why in the logs. If the message was delivered, it could have been rejected by an MTA further down stream in which case a DSN message should be returned, but possibly not for days, or it could have been delivered to the user's spam/bulk/junk/promo/whatever folder or silently discarded. Do your list's do bounce processing? If so, what's in Mailman's bounce.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark Sapiro

On 6/21/24 22:04, Mark wrote: > > At ~04:50 I posted an email to the list. The message was delivered to > members and archived. > > Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> Probably because (in Postorius) Settings->Digest->Enable Digests is No > Then, as "mailman", I ran "mailman digests --periodic" manually and got > the same error (as expected since there is nothing there) ... > > $ /opt/mailman/venv/bin/mailman digests --periodic > Traceback (most recent call last): ... > FileNotFoundError: [Errno 2] No such file or directory: > '/opt/mailman/mm/var/lists/<LISTID>/digest.mmdf' -> > '/opt/mailman/mm/var/lists/<LISTID>/digest.6.3.mmdf' This error should not occur if there is no digests.mmdf. It only does occur because you have set Digest size threshold to 0 under the assumption that 0 means unlimited which it doesn't. If you don't want digests sent on size, you need to set Digest size threshold to a very large number. I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid throwing the exception, but setting the threshold to 0 is still wrong as it will cause a digest to be sent on every post. If the Enable Digests setting is Yes, then the lack of digests needs more investigation. -- 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: Unknown templates being used

by Mark Sapiro

On 2/14/21 5:44 AM, Tom Stoddard wrote: > I'm a list owner who has recently (within the last week) had my lists > migrated from mailman 2 to mailman 3. The UI that we are using is > Affinity. So you should be getting your support from EMWD. > I've reviewed all of the list templates and begun to customize > some of them. My issue is that I'm receiving messages that don't match > any of the templates. Here is an example of one that I just received > this morning. (The x's are inserted by me. The actual message provided > valid addresses.) > > The xxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. > > > Held Subscriptions: > User:xxxxxxxxxx@gmail.com > > Please attend to this at your earliest convenience. That message is not built from a template. It comas from the `mailman notify` command which currently says ```> def _send_notice(mlist, count, detail): > """Creates and sends the notice to the list administrators.""" > subject = _('The {} list has {} moderation requests waiting.').format( > mlist.fqdn_listname, count) > # XXX This should be a template. > text = _("""The {} list has {} moderation requests waiting. ``` I.e., we know it should be a template, but it currently isn't. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Can't import from Mailman 2.1

by Mark Sapiro

On 2/22/26 14:53, Paul Tomblin via Mailman-users wrote: > I set up a new Mailman site using 3.3.10, and copied over my files from my old mailman site (using 2.1.34). I created a new domain, and a new list, and tried to import the settings from the old pickle file using mailman import21 pt-test(a)browncroftna.org /var/tmp/var.lib.mailman/lists/pt-test/config.pck (in the virtual environment shell) but I get the following error > File "/usr/lib/python3.13/contextlib.py", line 528, in enter_context > raise TypeError(f"'{cls.__module__}.{cls.__qualname__}' object does " > f"not support the context manager protocol") from None > TypeError: 'pathlib._local.PosixPath' object does not support the context manager protocol There is a compatibility issue between Mailman <=3.3.10 and Python 3.13. See <https://gitlab.com/mailman/mailman/-/issues/1190> and <https://gitlab.com/mailman/mailman/-/merge_requests/1309>. This patch will fix your issue. ``` --- a/src/mailman/utilities/i18n.py +++ b/src/mailman/utilities/i18n.py @@ -114,8 +114,7 @@ def search(resources, template_file, mlist=None, language=None): languages.append(language) languages.reverse() # The non-language qualified $template_dir paths in search order. - templates_dir = str(resources.enter_context( - files('mailman').joinpath('templates'))) + templates_dir = str(files('mailman').joinpath('templates')) paths = [templates_dir, os.path.join(config.TEMPLATE_DIR, 'site')] if mlist is not None: # Don't forget these are in REVERSE search order! ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 days, 12 hours

Search results for query "sapiro"