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

[MM3-users] Re: Unknown attribute: process_bounces

by Mark Sapiro

On 5/18/21 1:29 AM, xlefloch--- via Mailman-users wrote: > Hello, > > I've upgraded my Mailman installation from those versions: > mailman==3.2.2 > postorius==1.2.4 > mailmanclient==3.2.2 > > To those ones: > mailman==3.3.0 > postorius==1.3.3 > mailmanclient==3.3.2 > > I'm having issues in Postorius in the settings section: Unknown attribute: process_bounces. > When i'm printing the settings list for the concerned list retrieved by the REST API, i'am missing all the parameters related to the management of bounces. In the "mailinglist" table of the Mailman database, i have the columns managing these parameters. > > Anyone have any ideas? Postorius 1.3.3 requires Mailman core >=3.3.1 How did you upgrade?. If this was a package upgrade, your packager has produced an incompatible set of components. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 2/12/25 15:39, Christian via Mailman-users wrote: > I followed instructions provided here. Well, I rebooted the server and I'm > getting the same error again at the web page of > > "Mailman REST API not available. Please start Mailman core." > > I again found locks in /opt/mailman/mm/var/locks . Once I removed them I > could start mailman. > > Perhaps I made a boo boo. I want mailman to start without locks upon reboot. If Mailman is properly shut down, it shouldn't leave locks. How did you reboot? If your /etc/systemd/system/mailman3.service file contains an appropriate ExecStop, reboot via a `reboot` or `shutdown -r` should stop Mailman appropriately. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: Templates and docker-mailman

by Mark Sapiro

On 03/20/2018 02:13 PM, jwhathaway(a)locklaw.com wrote: > > /opt/mailman/core/var/templates/site/en/list:member:generic:footer > > But this is not being honored by the mailman container. I have restarted all of the containers. Is there something else I need to do? That's only one place the template is looked for. The search is first list, then domain then site. So the search will be first in /opt/mailman/core/var/templates/list/<list-id>/en/ followed by /opt/mailman/core/var/templates/domains/<domain>/en/ followed by /opt/mailman/core/var/templates/site/en/ and the first list:member:regular:footer or list:member:generic:footer found is what will be used for regular deliveries and the first list:member:digest:footer or list:member:generic:footer found is what will be used for digest deliveries. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Triaging message non-receipt

by Mark Sapiro

On July 13, 2018 12:11:13 PM PDT, Eric Abrahamsen <eric(a)ericabrahamsen.net> wrote: >All messages are correctly archived in hyperkitty. smtp.log always >shows >"for 5 recips", even for the messages that the two users aren't >getting. >These two users only ever miss messages sent by the other. > .... > >Is there any way to get a better sense of where things are going wrong? >Turn up the logging verbosity? Send test messages? Get more >diagnostics? Mailman has delivered the messages to the outgoing MTA and can't tell you any more. Mailman 3 bounce processing is broken. Look in the MTA logs for more. One possible issue is DMARC, but if you aren't applying DMARC mitigations, that should affect all messages from the Yahoo user to the Gmail user. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

6 years, 10 months

[MM3-users] Re: Hyperkitty archives - new list not archived

by Mark Sapiro

On 12/11/18 11:04 AM, vaarcilal(a)eafit.edu.co wrote: > Thanks! Now a well rendered page from Hyperkitty is shown. Big header: "Page not found". In red: "This page either doesn't exist, or it moved somewhere else." Is this normal since the list is new and it has no messages? > > The cron jobs seems to be OK. It has been like this for 2 hours. Here are the last logs from syslog: Have the 'hourly' cron jobs run? The hourly new_lists_from_mailman job should make the list available in HyperKitty even if there are no posts. You could also try manually running django-admin runjob new_lists_from_mailman If that fixes it, there may be some issue with how cron is running these jobs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Getting Archives to work - new setup on Ubuntu 18.04 (with mailman3-full pkg)

by Mark Sapiro

On 1/3/19 9:40 AM, kelly.close(a)lrewater.com wrote: > > The error message says HyperKitty failure on https://udfcd-lists.org/mailman3/hyperkitty/api/mailman/urls. I'm not sure if that's a clue or not - I can see the Authorization Required message at that address, to be sure. I looked into the referenced .py file at the line numbers referenced, and I can see the lines of code referenced in the error message, but I don't know why they are failing. I suspect I don't have a key or password or some other credential set properly in some file...but where? What do you have in your Django settings for MAILMAN_ARCHIVER_FROM -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 6/12/19 2:54 AM, Michael Sage wrote: > Hi, > I came across this really useful guide (posted to the list earlier). It has all gone really well and mailman 3 is installed. However, I have an issue, when I go to login using Postorius, I get the login page when I enter my credentials the page appears to hang and eventually goes to a Error 500 page. This totally hangs all of the mailman 3 web interface (but not apache). I then have to reboot the server to even get back to the login page. This seems like something I've seen reported before, but I can't find it now. Is anything logged in the various Mailman, Django, Apache logs? -- 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: 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

4 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

1 year, 8 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

5 years, 7 months

Search results for query "sapiro"