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

[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, 3 months

[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

2 years

[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

3 years

[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, 10 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, 2 months

[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

2 months, 2 weeks

[MM3-users] Re: Problems with New MM3 Installation

by Mark Sapiro

On 5/11/21 7:13 AM, mm3(a)steele.com wrote: > I have found work around for the settings issue but continue to have an issue with archiving new messages. New messages are stuck here; > > mailman3/mm/var/archives/prototype/[listname]@[domain]/new They aren't `stuck` there. That is where they are archived by the prototype archiver. This is separate from HyperKitty. > I have added this to my mailman.cfg: > > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /usr/local/mailman3/mailman-hyperkitty.cfg > > And created the "/usr/local/mailman3/mailman-hyperkitty.cfg” as such: > > base_url: http://localhost/archives/ > api_key: [key that matches “MAILMAN_ARCHIVER_KEY” in my settings.py] > > Some documentation says that the url should be "http://localhost/hyperkitty/ but url generates a page not found error on my setup while the archives are available at the “archives” url. > > But, now that I think about it, "localhost" doesn't make sense here because I am virtual hosts and "localhost" will probably just connect to the first virtual host rather than the mailmanweb virtual host. > > Any advice on what do do here? Set base_url: in /usr/local/mailman3/mailman-hyperkitty.cfg to a url that will reliably access HyperKitty, probably the same base URL that a user with a web browser would use. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens > in /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) > Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during _handle_client() > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Bulk update of members' moderation settings

by Mark Sapiro

On 11/18/21 12:37 PM, Alex King via Mailman-users wrote: > I imported a list from mailman 2.1 using > https://docs.mailman3.org/en/latest/migration.html. > > It happens that emergency moderation was set on the mailman 2.1 list, > and this has resulted in all members having Moderation set to Hold. I > now want to change that to Default Processing for all members. > > Is there a way to achieve that in bulk without clicking through the > members options for each member in Postorius? I don't understand how this happened. The mailman 2.1 list's emergency setting should hsave been imported as the emergency setting of the Mailman 3 list and should not affect individual member's moderation at all. However, to set the moderation action for all members of a list to default processing You can do something like this in mailman shell ``` bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> from mailman.interfaces.action import Action >>> for member in m.members.members: ... member.moderation_action = Action.defer ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Alias Domains in postfix_domains wrong way around?

by Mark Sapiro

On 10/24/20 10:34 AM, Hans-Martin Mosner wrote: > > Is my understanding correct that postfix_domains should have the true (externally visible) domains as keys, and values > that basically don't matter, or should it have both the real domains and their alias names as keys? With such a > convoluted setup, my brain twists a little. I'm not sure what's going on in your case. I have two separate servers that use alias domains, and for both of them, the postfix_domains file lists the alias domain as the key and the real domain as the value. This works fine with the Postfix settings ``` transport_maps = hash:/path-to-mailman/var/data/postfix_lmtp relay_domains = hash:/path-to-mailman/var/data/postfix_domains virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap ``` Is this what you have? Note that the address should be remapped from list@true_domain to list@alias_domain by virtual_alias_maps prior to checking relay_domains. Perhaps you have some other unusual thing in your Postfix configuration. What does `postconf -n` report? This is what I see in the mail log for a typical delivery ``` Oct 18 13:30:44 example postfix/lmtp[13745]: 108CA1F8A03: to=<list(a)x.example.org>, orig_to=<list(a)example.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.08, delays=0.05/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) ``` where example.org is the true domain and x.example.org is the alias domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Search results for query "sapiro"