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

[MM3-users] Re: Join a Mailman 3 list?

by Mark Sapiro

On 6/2/25 10:55, Cathryn McGuire wrote: > Hi, > > We’re currently hosted by EMWD who upgraded the Mailman 2 cPanel/Python and have been unable to resolve the issues we’re experiencing. > > We would like to join a Mailman 3 list to see how it all looks and works. > > Do you have any recommendation? Welcome to the mailman-users(a)mailman3.org list. As far as your EMWD migration from cPanel Mailman 2.1 to Mailman 3 is conerned, I think you'll find little if any change as far as email posting to the list and email from the list is concerned, but EMWD has their own proprietary web UI for list management and archiving, so the web UI at EMWD is quite different from that for this list. I'm not sure if we can help with the issues you're having, but if you tell us what they are, we can try. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

[MM3-users] Re: Cannot Install Web UI

by Mark Sapiro

On 10/31/25 11:35, dap1--- via Mailman-users wrote: > All those links return a 404 error. As for the logs, oddly nothing is being logged: > > <venv>$ ls -l > total 0 > -rw-rw---- 1 mailman mailman 0 Oct 19 11:07 bounce.log > -rw-rw---- 1 mailman mailman 0 Oct 19 11:07 debug.log > -rw-rw---- 1 mailman mailman 0 Oct 19 11:07 mailman.log > -rw-rw---- 1 mailman mailman 0 Oct 19 11:07 plugins.log > -rw-rw---- 1 mailman mailman 0 Oct 19 11:07 smtp.log > > Maybe that is a clue. If your gunicorn.conf contains accesslog = "/opt/mailman/mm/var/logs/access.log" errorlog = "/opt/mailman/mm/var/logs/error.log" as recommended at https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-guni… and there is no /opt/mailman/mm/var/logs/error.log file, gunicorn isn't running. Also, the fact that mailman.log is empty says mailman core isn't running. Either that or your logs are elsewhere. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: out queue backlog and delivery rate

by Mark Sapiro

On 3/25/22 16:17, dancab(a)caltech.edu wrote: > > Mail delivery is continuing at a snails pace and it is now 4 hours behind. > > I noticed that the system isn't overloaded either via CPU or Memory. It's just slowly "working on it". > > Are there rate limits that can be tuned for Mailman queues such as the "out" queue? Could this be IO related somehow? I'd expect there to be a CPU spike in that case. There are things that can be done. One big performance killer is MTA recipient checks during SMTP from Mailman. Look too at the various hits at <https://wiki.list.org/?action=fullsearch&value=performance&titlesearch=Titl…>. These are written for older Mailman, but the MTA advice is relevant. One thing you can do is enable an alternate SMTPD port in the MTA with minimal checking and configure Mailman to use that port. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Remove PDF attachents

by Mark Sapiro

On 3/4/20 7:42 AM, Eduardo Costa via Mailman-users wrote: > Hello, > > How do I configure the list to remove attachments of type pdf and others. You need to set the list's filter_types and or pass_types. For example, to filter out everything except HTML and plain text, collapse alternative parts and convert remaining HTML to plain text, you would set filter_content = True collapse_alternatives = True convert_html_to_plaintext = True pass_types = ['multipart', 'text/plain', 'text/html'] The first 3 of these can be set in Postorius -> Settings -> Alter Messages, but the last has to be set in mailman shell as in $ /opt/mailman/mm/bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell m. The variable 'm' is the list(a)example.com mailing list >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Mark Sapiro

On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Problem with list creation

by Mark Sapiro

On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > We increased timeout in mailman.cfg > ``` > [gunicorn] > workers: 4 > timeout: 900 > ``` This doesn't do it. In order to pass configuration settings to the REST gunicorn servers, you need to put in mailman.cfg ``` [webservice] configuration: /path/to/gunicorn.cfg ``` and then put settings like these ``` [gunicorn] workers: 4 timeout: 900 ``` in /path/to/gunicorn.cfg. Some settings, but only hostname, port and workers can be put in mailman.cfg, but in the [webservice] section, not in a [gunicorn] section. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/gunicorn.…> for more detail. > And we increased timeout in nginx > > ``` > http { > > # MODIF UNICORN > proxy_connect_timeout 300s; > proxy_read_timeout 300s; > # MODIF UNICORN > > ``` nginx is not involved. These are not proxied requests through nginx. They are requests to Mailman's REST API which use a separate gunicorn server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: where is manage.py for migration?

by Mark Sapiro

On 11/26/20 6:50 AM, Dan Langille wrote: > Hello, > > I am following https://docs.mailman3.org/en/latest/migration.html and I'm trying to "Migrate the list archives from Mailman 2 to Mailman 3 by running the following command": > > [mailman@mailman ~]$ python manage.py hyperkitty_import -l biking(a)lists.example.org /usr/local/mailman/archives/private/biking.mbox > python: can't open file 'manage.py': [Errno 2] No such file or directory > > Is the documentation correct? I cannot locate manage.py in the code: That refers to the Django manage.py script. It's name and location depends on how you installed Postorius and HyperKitty. Have you installed those and set up a Django project? There are sample manage.py files in both postorius/example_project/ and hyperkitty/example_project/ as well as mailman-suite/mailman-suite_project/, however, depending on how things are installed, the Django admin interface could be named manage.py, django-admin or something else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 2/2/23 18:19, Allan Hansen wrote: > Mark, > > I can see your argument here, but if a 'Disabled by bounce' subscription is enabled, it would require just looking at that particular subscription and set the bounce count to 0, so that the next bounce (before staleness) does not disable it again. We are talking about two different issues here. One issue is not resetting the bounce score to zero when (or before) a disabled by bounce user's delivery is enabled. This is https://gitlab.com/mailman/mailman/-/issues/1061 and I'm working on it. The other issue is not resetting the user's bounce score when it goes stale as opposed to when another bounce is received and the score is stale. Other than the fact that one might be misled by seeing a non-zero bounce score which is stale, there are no other issues from waiting for a bounce to reset a stale score. -- 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: [migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite

by Mark Sapiro

On 10/20/23 14:04, Wikinaut wrote: > I also solved this issue. > How? > > By adding columns to two tables in the database mailman3web: > > alter table hyperkitty_mailinglist add column archive_rendering_mode varchar(255) default null; > alter table socialaccount_socialapp add column `provider_id` varchar(200) NOT NULL; > alter table socialaccount_socialapp add column `settings` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL CHECK (json_valid(`settings`)); The proper fix is just to run `mailman-web migrate`. See https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… You should also run that and `mailman-web collectstatic` `mailman-web compress` and `mailman-web compilemessages` any time you do any kind of update. See https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-… et. seq. Running `mailman-web migrate` at this point may fail because of the changes you made manually. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: 120 gmail users removed from lists !

by Mark Sapiro

On 10/24/23 11:51 AM, info(a)joergschulz.de wrote: > Am 24. Oktober 2023 um 18:07 schrieb "Yvan ♞" <elemac(a)free.fr>: > >> >> I add an SPF entry on my web hosting, domain name: "v=spf1 mx ptr >> include:_spf.google.com -all" and it seems to fix the problem. >> > Smart. As I understand above statement, it allows the google servers to send out emails for your domain. Not sure you want that. But you're right, mailman will eventually pick up the -all for the google addresses and apply the DMARC mitigation to google originating messages. Is this assumption correct? Wrong. Mailman in conditionally applying DMARC mitigations considers only the DMARC policy if any of the From: domain. Whether or not an outgoing message might be rejected for DMARC policy or any other reasons has no automatic effect on the application of DMARC mitigations to subsequent messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

Search results for query "sapiro"