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

[MM3-users] Re: Howto: Mass import of nonmembers in several lists?

by Mark Sapiro

On 1/10/22 4:00 AM, Paul Paulchen wrote: > > So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. > I thought so, because the import21 command did this as well when we migrated to mailman3. You could script it with `mailman shell`. If you really want this, I'll help. > I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. > But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! You can't without modifying the code. > Hope I explained my case properly. I appreciate your responds! Thanks in advance. My question is why do you want to add these nonmembers. The only thing gained by adding a nonmember is the ability to set the nonmember's moderation action to other than the default, and you can handle that with the legacy * these non-members settings which take priority over the nonmember's moderation action anyway. Note that if a nonmember posts to a list, she will automatically be added to the list as a nonmember with default moderation action if she isn't one of the list's nonmembers already. -- 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: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/26/20 10:45 AM, Shashikanth Komandoor wrote: > Thank you Mark. > > What you have said is right.. > > I found a list with two "hyperkitty" records in the listarchiver in the > database. I had removed the list and recreated it and now I found it is > working fine. The recreated list is having only one record. OK, but that's not a reasonable way to fix this in general. You can just remove the `extra` record using a direct database query which is probably the least disruptive way to fix this. > After searching the links you provided I found there is just a work around > but not the precaution to be taken for not getting the duplicate record. > > Can you say what might be the reason for this duplication? If I need to > provide any details, please let me know. As noted in the threads I referenced, we don't know the cause. Yours is the first report of this issue with the `hyperkitty` archiver. In all the other reports, the duplicate archiver has been `mhonarc`. If it happens again and you know the exact sequence of events that led to it, i.e. what was done with the list between the last time it worked and when it stopped working, that might give us clues, but currently we are at a total loss to understand how this happens. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mark Sapiro

On 6/17/23 17:02, Mike Wertheim wrote: > I set `remove_dkim_headers: yes` in the [mta] section of mailman.cfg. > > I'm seeing a bunch of these errors in the logs: > 2023-06-17 18:57:11 1qAbMA-005Y7W-HP ** mike.wertheim(a)gmail.com > <mailto:mike.wertheim@gmail.com> R=dnslookup_single_domain > T=remote_smtp_single_domain H=alt2.gmail-smtp-in.l.google.com > <http://alt2.gmail-smtp-in.l.google.com> [172.253.62.26]: SMTP error > from remote mail server after end of data: 550-5.7.26 Unauthenticated > email from gmail.com <http://gmail.com> is not accepted due to > domain's\n550-5.7.26 DMARC policy. Please contact the administrator of > gmail.com <http://gmail.com> domain\n550-5.7.26 if this was a legitimate > mail. Please visit\n550-5.7.26 > https://support.google.com/mail/answer/2451690 > <https://support.google.com/mail/answer/2451690> to learn about the\n550 > 5.7.26 DMARC initiative. > w13-20020a05622a190d00b003fde5babbf5si1170418qtc.14 - gsmtp Your issue is mail From: the gmail.com domain to the list and sent to gmail users is being bounced because it fails DMARC. I.e. Gmail applies a DMARC policy of p=reject to mail From: gmail.com even though it's published DMARC policy is p=none. You need to apply DMARC mitigations to this mail. Unfortunately, this requires setting DMARC Mitigate unconditionally to Yes. Mailman 2.1 has a feature to apply DMARC mitigation to messages From: specific domains regardless of any domain specific DMARC Policy. Unfortunately this hasn't been implemented in Mailman 3 yet. I just filed https://gitlab.com/mailman/mailman/-/issues/1084 for that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: How to keep virtualenv install secure?

by Mark Sapiro

On 11/7/24 01:31, Lichtinger, Bernhard wrote: > Hi, > > I am looking for some advice: If we use the virtualenv install method, how does one keep track of security updates for all the installed dependencies? > > I can think of: > - Upgrade regularly all installed packages inside the virtualenv. This might break mailman3 if there are incompatible updates. You can do in the venv ``` pip install --upgrade --upgrade-strategy eager mailman psycopg2-binary mailman-web mailman-hyperkitty ``` I'm not sure if this will update dependencies if there are no updates to the named package, but in any case, incompatibilities should be avoided because if a newer version of a dependency in incompatible, the dependency should be pinned to a compatible version in the project's requirements. > - Try to track all dependencies and check if there are security updates published. This might be impossible to achieve. It shouldn't be too difficult to script this. ``` Get the output from `pip freeze` in the venv for each line split it on `==` into PACKAGE and VERSION get https://pypi.org/rss/project/PACKAGE/releases.xml find the first <title>VERSION</title> and compare that VERSION to the VERSION from `pip freeze` ``` This won't tell you if the newer version is a security update, but it will tell you which packages have newer versions. > - Security updates are so rare, we do not need to bother. ;) For the Mailman dependencies, this is probably true. -- 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: Approve an email

by Mark Sapiro

On 12/26/22 12:08, Lars Bjørndal wrote: > Hi, list! > > I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and > postorius-1.3.6-2.fc36.noarch installed. with the command > > sudo -u mailman mailman3 create <listname> > > I was able to create a list. > > I'm not able to find out how to setup and configure the postorius > package. There's no mailman-web command. See <https://docs.mailman3.org/projects/postorius/en/latest/>. I don't know how you invoke the Django management command in the postorius-1.3.6-2.fc36.noarch package. It could be manage.py or django-admin or something else. > Hyperkitty will not installed du to a dependency conflict, but I dont > need archiving for the list. > > Here comes my quesitons: > > - What's the easiest way to approve an email sent to the list? Approving held messages via email requires Mailman core >= 3.3.5. See <https://gitlab.com/mailman/mailman/-/issues/169> Thus, the easiest way is via Postorius. > - How can I configure the list to accept messages also from non members? Set the list's default_nonmember_action to Action.defer. This can be done via Postorius, mailman shell or the REST API. > - How can I setup postorius to work on Fedora? I have django-admin, but > I'm not sure where to go. See the Postorius docs at https://docs.mailman3.org/projects/postorius/en/latest/setup.html#installat… to get started. (replace `python manage.py` with `django-admin`) -- 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: 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

3 years, 7 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

1 year, 7 months

[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

4 years, 2 months

[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

2 years, 11 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

6 years, 9 months

Search results for query "sapiro"