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

[MM3-users] Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 10:37, Eggert Ehmke via Mailman-users wrote: > Hello Steve, > I really would appreciate to get some help on the withlist command. I really like to program python, but this interface is not at all intuitive. I also find it strange to do administrative tasks in a programming language. In this special case, I believe it should be possible to work on the display names in Postorius in the member settings. You can update user display names in Postorius via the Users tab at the top of the page, but it would be a tedious, one at a time process, and I don't think you can modify address display names in Postorius and those are the ones `mailman members` displays. I just posted a mailman shell (aka withlist) interaction at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Try that. > I also find it strange to do administrative tasks in a programming language. Understood, but there are a couple of things at work here. One is that this particular task is a one-off the correct the result of a bug, but perhaps more significantly, mailman developers (at least me) are comfortable with `withlist` (it's been around since MM 2.1) and if I can do it that way, it reduces the motivation to make something more friendly for the normal admin. Unfortunately doing things easily that way requires a lot of specialized knowledge of Mailman internals, so most admins need help with 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, 5 months

[MM3-users] Re: Mailman3 Docker persmission denied

by Mark Sapiro

On 1/6/25 13:09, Commander456 wrote: > Hello everyone, > > I recently installed the mailman-core Docker image (Version 0.5) and tried to create a list using the mailman commands inside the container. I used the --notify argument but doesn't receive any mail (I'm the list owner), However, inside the mailman.log I get the following error: > > Jan 06 20:54:25 2025 (156) Uncaught runner exception: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' > Jan 06 20:54:25 2025 (156) Traceback (most recent call last): > File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 164, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/site-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > ^^^^^^^^^^^^^^^^^^^^ > PermissionError: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' > Jan 06 20:54:25 2025 (156) Skipping and preserving unparseable message: 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8 Did you run `mailman create` as user `mailman`? Also did the command print a `Created mailing list:` message? In any case, it looks like the list was created and the command generated the notification which was queued in the virgin queue as 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck, but then virgin runner was unable to read it, but if there was no `Failed to unlink/preserve backup file:` message in the log the file should have been moved to /opt/mailman/var/queue/bad/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.psv. What is ownership and permissions of that file, and what is the user running the various runners? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Mailman3 Setup

by Mark Sapiro

On 6/11/22 06:02, George R. Kasica wrote: > Mark: > > These all reference the virtual environment setup, which is fine if I need to go with that. I’ve already installed the components etc. As a “standard installation. Do you know of a good doc that would help me set up in a non-container environment – just the native OS – Ubuntu 20.04 LTS. I virtualenv is not a "container", at least in the sense of a Docker container. It is just a way of isolating an environment from various OS things and vice versa. You do not need to install in a virtualenv. You can follow the procedure for installing in a virtualenv and just omit the bits about creating and activating the virtualenv However, if you do not install in a virtualenv, you are vulnerable to OS package updates breaking things. For example, installation of Mailman core installs SQLAlchemy <1.4 because Mailman core is not currently compatible with SQLAlchemy >=1.4. If an OS package upgrade installs SQLAlchemy >=1.4, that will break your Mailman installation. > If I need to go with a virtual environment, do I need to uninstall what I have out there and what’s the best way to get all the added bits out? You actually don't need to remove anything because whatever is installed in the virtualenv will be what's used when the virtualenv is active. However, any Mailman specific stuff installed systemwide will not be used and is just wasted space and could be uninstalled. -- 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: Mailman issues after re-boot

by Mark Sapiro

On 9/16/23 5:29 AM, Paul Rubin wrote: > *I need to know what to remove, how to correctly update, etc., That said > the two scripts appear to be very similar:* > > mail:/opt/mailman # head /usr/bin/mailman > > #!/usr/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' > __requires__ = 'mailman==3.3.4' > import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( This is no good because it uses the system Python and won't have the venv's site-packages in its path. > mail:/opt/mailman # head /opt/mailman/venv/bin/mailman > #!/opt/mailman/venv/bin/python3 > # -*- coding: utf-8 -*- > import re > import sys > from mailman.bin.mailman import main > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) > sys.exit(main()) > mail:/opt/mailman # This one is good because it uses the venv python3 and thus uses site-packages from the venv. > *Given the two years since the last reboot I also tried following * > https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was > running the latest* > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web Thin may be part of the issue. The above may not upgrade dependencies as needed. You may need the `--upgrade-strategy eager` option. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On 11/6/19 9:18 AM, josh(a)caluette.com wrote: > I just setup a new Mailman 3 server using maxking/docker-mailman from GitHub. I got everything working just right including changing the footer template for messages. However, when trying to set anything in a Welcome template, I am encountering these same errors. > > I have confirmed that the mailman-core container is able to download the template via curl using the http://mailman-web:8000/ api URL and gets the correct text, but anytime I try to mass subscribe, it fails with the errors that Brian had provided and I get an HTTP 500 error. > > If I remove the Welcome template, then I can do mass subscribe just fine. > > Here are the logs: > > Nov 06 17:10:13 2019 (29) deque: > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 384, in _make_request > six.raise_from(e, None) > File "<string>", line 2, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 380, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1331, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 297, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 258, in _read_status > line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1") > File "/usr/lib/python3.6/socket.py", line 586, in readinto > return self._sock.recv_into(b) > socket.timeout: timed out Have you set POSTORIUS_TEMPLATE_BASE_URL appropriately in your settings_local.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/27/21 3:48 PM, Ruth Ivimey-Cook wrote: > > It is also possible to Alter existing databases and tables, but with one > catch: the maximum table row length is reduced, so some tables will need > to be adjusted (e.g. converting varchar(255) to varchar(230)). This is misleading. The maximum row length depends on the actual data stored in the row. The sum of the various column size limits for VARCHAR and other columns can well exceed the maximum row size as long as the sum of the lengths of the actual data stored in the row does not. The significant issue is all these limits are bytes, not characters, so in the worst case, a VARCHAR(255) column can only store 85 3-byte utf8 encoded unicodes or 63 4-byte utf8mb4 encoded unicodes, but this too is misleading an most strings contain single byte encodings with some 2 or 3 byte encodings and maybe at most one or two 4-byte encodings. Furthermore, the problem issues are essentially limited to emojis and possibly other 4-byte encoded symbols in email subject headers and bodies. Bodies are a TEXT field and the data are stored separately and do not affect the row size and subjects are defined with a maximum length of 512 bytes which should be sufficient. None of the data stored in rows is at all likely to exceed the maximum row length, even with a lot of 4-byte encodings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Mark Sapiro

On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ… although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Mailman recovery test did not go as planned

by Mark Sapiro

On 8/9/22 07:19, Stephen J. Turnbull wrote: > > You don't do it with HyperKitty (I'm pretty sure you can export mboxes > from HyperKitty, but I don't think it would be timely, you have to do > it by hand). The sample archiver (which you can enable in mailman.cfg > IIRC, haven't done it in a while) would make the mbox files directly > from the core at the same time that they are sent to HyperKitty. It's > possible to have both HyperKitty and the sample archiver enabled at > the same time. The `sample archiver` is actually called the prototype archiver and it is typically enabled by default. The messages are stored in maildir format in Mailman's var/archives/prototype/ directory in sub-directories with names of the list posting addresses. You would need to convert maildir to mbox format to import to hyperkitty. A simple script to do this is ``` #!/usr/bin/python3 """Run this with the list posting address as it's argument.""" import os import sys from mailbox import mbox, Maildir MDIR = '/path/to/mailman/var/archives/prototype/' MBOX = '/path/to/output_directory' if len(sys.argv) != 2: print(f'Usage: {sys.argv[0]} list_posting_address', file=sys.stderr) sys.exit(1) mdir = Maildir(os.path.join(MDIR, sys.argv[1]), create=False) mlbox = mbox(os.path.join(MBOX, sys.argv[1]), create=True) for msg in mdir: mlbox.add(msg) mdir.close() mlbox.close() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Time Zone Problem In Postorius

by Mark Sapiro

On 1/12/22 7:34 PM, Alan So wrote: > I notice that the template was updated to add the code. However, I still observe an issue. > > If the correct hold date is: 2022-01-13 10:16 GMT+8 or 2022-01-13 02:16 GMT > If I select my time zone as Asia/Hong_Kong, it is displayed as Jan. 13, 2022, 2:16 a.m. > If I select time zone as GMT, it is displayed as Jan. 12, 2022, 6:16 p.m. > > There is a shift of -8 hours when displaying the time in Postorius. I cannot find the detail of the held message from database tables yet. Not sure how the hold date was stored at this moment. As you note later, the hold time is stored in UTC. It should be rendered in Postorius held message view in the timezone that you have set in your user-profile. The timezone conversion is in Django. It is defined in the template as ``` {{ msg.hold_date|datetime_parse|localtime|date:"DATETIME_FORMAT"}} ``` where msg.hold_date is the time in UTC. I think the issue is that while msg.hold_date in in UTC, it is a naive datetime.datetime object (see https://docs.djangoproject.com/en/4.0/topics/i18n/timezones/#interpretation…) so if your Django setting for TIME_ZONE is Asia/Hong_Kong it is interpreted as UTC +0800 so that subtracts 8 hours and then conversion to your profile timezone if Asia/Hong_Kong adds 8 hours back. I think if you set `TIME_ZONE = 'UTC'` you will get the behavior you expect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Recently redeployed mailman3 and then received huge amount of subscription disabled notification emails

by Mark Sapiro

On 10/12/24 1:44 AM, francesd919--- via Mailman-users wrote: > Hi everyone, > > I recently redeployed our mailman3 server. As the owner for one of our mailing lists, I received a huge amount of subscription disabled notification emails. > These emails mentioned that the subscription was disabled due to bounce score. > Furthermore, we received a few emails from our subscribers saying that they have functioning email addresses and not sure why there were bounces and that their subsctiptions had been disabed. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > I have some questions: > > 1. Why do mailman mass send out subscription disabled notification emails to admins after it's been redeployed? > 2. I have "Bounce disable warnings" set to 3 and "Bounce disabled warnings interval" set to 7d. How come there are still so many emails seem to be disabled but not unsubscribed? Hence we receiving so many subscription disabled notification emails. > 3. What could have cuased functioning emails to bounce and therefore being disabled? The answer to all those is you upgraded from a Mailman core version prior to 3.3.1. Prior to that, bounces were recorded in the database but not processed. when you upgraded, they all got processed at once. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… which includes a `mailman shell` interaction to re-enable all the subscriptions disabled by bounce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

Search results for query "sapiro"