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

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Mark Sapiro

On 10/28/20 1:20 AM, Torge Riedel wrote: > > - I have logrotate configured for daily rotate (which includes a > 'systemctl reload mailman') > - I have the cron jobs configured for mailman-web The mailman-web crons don't affect this. Only crons that run a `mailman` command could. > So it could be that cron jobs for mailman-web are running at the same > time when mailman-core is asked to reload after log rotation. Could this > lead to a race condition? > > But as you said: A 'reload' should not update the files. What does your systemd mailman.service script contain for ExecReload? What crons run at the time of the anomalous timestamps? -- 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

[MM3-users] Re: How to let mailman log every single email that it sends out?

by Mark Sapiro

On 9/8/23 12:41, Mohsen Masoudfar wrote: > > I'm curious about the configuration required to have Mailman record logs for every individual email it sends. I see that it sends to the entire list, but I'm interested in obtaining log entries for each email sent to every individual subscriber on the list. > How can I access this information? > > Is it a postfix setting, or a Mailman3 setting? > I have checked /var/log/mail.log and all the logs under /var/log/Mailman3/* > Mailman is running on Ubuntu 18.3 You should see the information about the mail being sent an delivered to recipient MX servers in /var/log/mail.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, 7 months

[MM3-users] Re: Manual setup - permissions

by Mark Sapiro

On 9/22/19 2:11 AM, Tobias Hachmer via Mailman-users wrote: > > Now, running the scheduled tasks (which run from user+group "nginx") for > django I ran into permission problems, because the nginx user can't > access/write to the needed files in /opt/mailman3/core/... > > If anyone of you is able to read ansible tasks, this is how I set this > up via ansible: > https://github.com/freifunk-mwu/ansible-ffmwu/blob/mail/roles/service-bundl… > > I would appreciate any hints how to run the different peaces of mailman3 > with the correct user/groups/permissions. Set up everything as user:group mailman3:mailman3. I.e., chown -R mailman3:mailman3 /opt/mailman3/web and set the uwsgi service to drop privileges to user+group "mailman3". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: search this list searches more then just this list

by Mark Sapiro

On 1/15/24 08:25, Marco van Tol wrote: > > Hi, thank you for your message. I dug into what we have, and found this: > > ``` > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > ``` I have tested and I can confirm that with two lists in the same domain named `test` and `x-test` and with Whoosh as the backend searching the `test` list returns hits from both lists, but with Xapian as the backend, only hits from the `test` list are returned. Apparently when Whoosh is given a list name like `test(a)example.com` it finds hits from all lists whose names contain `test(a)example.com`. This is not the case with Xapian. -- 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: Mailman3 on AlmaLinux 9 - Python3.9 errors

by Mark Sapiro

On 7/18/24 7:58 AM, willie.castillo(a)caemilusa.com wrote: > Not sure what's going on here. This is the output of the "mailman3 info". What am I doing wrong? > > $ /usr/bin/mailman3 info > Traceback (most recent call last): ... > alembic.script.revision.ResolutionError: No such revision or branch '2156fc3f6f7d' The `mailman3` command is trying to run all the alembic migrations as part of initialization and is failing with this error. Thus, it never gets to the point of actually doing what you ask. What is the version_num in the alembic_version table in the database? I.e., ``` SELECT version_num FROM alembic_version; ``` and what does ``` ls /usr/lib/python3.9/site-packages/mailman/database/alembic/versions/ and grep -r 2156fc3f6f7d /usr/lib/python3.9/site-packages/mailman/database/alembic/versions/ ``` give? -- 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: Can't remove footer(s)

by Mark Sapiro

On 10/02/2018 12:14 AM, Henrik Rasmussen wrote: > I have a problem removing the footer(s) from a list imported from MM2.1. I have been testing by entering my message in Hyperkitty (the list forum). > > I an aware about the double footer issue[1], and I am aware that footers are cached, but I have removed the footer files according to [2], run Mailman shell according to [3], restarted the Mailman (Mailman core, Mailan web, Postgres database and postfix). > > Did I miss something in order to remove the footers? Removing the files won't work because Mailman will fall back the the built-in footer. You have to create empty files. The easiest thing is just to 'cp /dev/null' to the footer files created by import21 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Installing MM3 via pip fails…

by Mark Sapiro

On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > I followed the instructions at > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > As soon as I get to the Django part things get hairy. It seems Django requires > something that was removed from it. What exactly is the issue? I just tried following the doc starting at <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> and doing everything through (venv)$ python3 manage.py runserver and I encountered no issues. One possibility is the Ubuntu 18.04 box on which I did this already had ruby-sass and python3-dev globally installed. sudo apt install ruby-sass sudo apt install python3-dev Did you install these? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 4/30/20 1:25 PM, john_warland(a)hotmail.com wrote: > I came across this same error and solved it doing some googling and came across this statement. > > in main.cf: > local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp > > change it to: > local_recipient_maps = > > It fixed the immediate issue but I do not know enough to say why. Hope someone can elaborate on this. Setting local_recipient_maps = disables all local recipient checks. If you don't want to do that, you need to specify whatever the current or default setting is in addition, e.g. local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/var/data/postfix_lmtp See <http://www.postfix.org/LOCAL_RECIPIENT_README.html> We need to update the docs for that setting. -- 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: unknown encoding: windows-874

by Mark Sapiro

On 5/13/20 5:00 PM, Mark Dadgar wrote: > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > > LookupError at /hyperkitty/api/mailman/archive > unknown encoding: windows-874 HyperKitty is trying to archive a message which has declared the charset of one or more parts as windows-874 (a variant of iso-8849-11, latin/Thai). Python doesn't recognize windows-874 as known charset. You can probably find the message in var/archives/hyperkitty/spool/. As long as it's there, HyperKitty will keep retrying. You can move it aside, and if it looks like something you actually want to archive, you might be able to fix it, but that's tricky. The file in var/archives/hyperkitty/spool/ is I think a pickled email message object. You can view it with `mailman qfile`, but editing is tricky. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Mark Sapiro

On 12/6/21 11:20 PM, Stefan Bauer wrote: > Unfortunately i need this, as the postfix is listening on all interfaces > and we have the policy to enforce TLS only. Nothing special in the logs: > > Dec 07 08:14:14 2021 (12303) Using agent: <mailman.mta.bulk.BulkDelivery > object at 0x7fbc29b1c4a8> > Dec 07 08:14:14 2021 (12303) Connecting to localhost:25 There should be a `Dec 07 08:14:14 2021 (12303) Starttls` entry here. > Dec 07 08:14:14 2021 (12303) envsender: v-test-bounces@domain, recipients: > ['recipient(a)own.domain'], size(msgtext): 5809 ... > > Is my mailman version maybe too old for this setting? > > I'm running GNU Mailman 3.1.1 (Between The Wheels) Yes, it's too old. STARTTLS support was added in Mailman 3.3.0 -- 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

Search results for query "sapiro"