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

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Mark Sapiro

On 7/24/20 10:34 AM, Shashikanth Komandoor wrote: > Hi Team, > > Today, I found an error message like "Multiple rows were found > for one_or_none()" when a hold message is approved for a list. Until > yesterday the mails were accepted and delivered fine. We have seen this issue before. See <https://gitlab.com/mailman/mailman/-/issues/657>. There are also multiple threads on it in the archive, e.g., <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. We don't know how it happens, but the issue is that the `listarchiver` table in the database has multiple `mhonarc` entries for the same `mailing_list_id`. You can see the problem with the query select * from listarchiver where name = 'mhonarc'; There will be two entries with the same `mailing_list_id` and deleting one of them will fix this and you can run `mailman unshunt` to reprocess the shunted messages. The above referenced issue contains a script that can be run to remove the extra entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by Mark Sapiro

On 12/9/20 6:39 PM, matthew(a)alberti.us wrote: > > For core, the connection string seems to accept a tailing > "?charset=utf8&use_unicode=1" per > https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So > for core, maybe just updating the connection string to include > "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the > recommend encoding... maybe that should be updated? I'm in the process of doing that update. > Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is > recommended, and it needs to be explicitly identified in the database > settings for BOTH core and web, and probably somehow at database creation > time? It's not as critical for core because barring things like 4-byte utf-8 unicode graphics in list configurations, core doesn't store anything like that in its tables. The major issue is with HyperKitty where messages have emojis and other 4-byte utf-8 encodings in message subjects and bodies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Mark Sapiro

On 9/21/23 17:30, Thomas Ward wrote: > > MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). > > If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 09:08, Wikinaut wrote: >>> In the Postorius held messages view, click on the message's subject to >> open a dialog showing the messages content > > Dear Mark, sorry: > How should I know this? Well, the subject of the message in the held messages view looks like a link. Maybe click it once to see what it does. > I'd rather prefer to have these both changes: > > i) relabel the existing one od three buttons from "accept" to "accept once" ; and > ii) add a fourth button "accept all messages from this sender (i.e. add to white list)" That wouldn't include options like "discard further posts from this user", "reject further posts from this user" and perhaps other possibilities. If I were going to do anything, it would probably be adding a line above the list of held messages saying something like "Click the message's subject for more options." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Mailman web interface / uwsgi

by Mark Sapiro

On 11/26/22 21:29, Jan Eden via Mailman-users wrote: > > Replicating this setup on the server solved the KeyError problem, > everything works now! I just wonder why these uwsgi parameters need to > be passed explicitly when using a file socket, but not with a http > socket. You are doing more than just switching from a tcp socket to a unix socket. You are also switching from communicating with uwsgi via http protocol to uwsgi protocol. > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > files when using the virtualenv installation instructions > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, not mailman-web. If you want, you could put mailman-hyperkitty.cfg in /etc/mailman3/ by putting ``` configuration: /etc/mailman3/mailman-hyperkitty.cfg ``` in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. -- 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: Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*

by Mark Sapiro

On 10/19/23 10:02, Thomas Ward via Mailman-users wrote: > I noticed some unusual behavior in Mailman3 stable release on PyPI and > such. Namely, there are instances where replies are being processed and > the prefix tags are simply being **lost** and dropped by Mailman3, > instead of being properly prepended where they're supposed to go. > > Is this a known bug or does it need its own bug in the gitlab tracker? Are you sure you are looking at messages from the list and not messages received by direct To:, CC: or BCC:? I have never seen an issue where list posts would sometimes have the subject prefix prepended and sometimes not. If you are seeing this, we would ideally like to see a thread in the hyperkitty archive where some of the messages have the prefix in the message view and some don't, or at least see some of the raw Subject: headers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Template for Password Reset Email

by Mark Sapiro

On 11/17/24 16:57, Mark wrote: > > I can see the French text for the "Password Reset Email" in the > django.po file. And running the compilemessages command reports the > "django.po" for French is okay and up to date. Should I be recompiling > the ".mo" file? No, It's fine. The issue is the language context for this message has nothing to do with any Mailman list's preferred language. Again, see https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… If all the lists on your server are French, you could set LANGUAGE_CODE = 'fr' in your Django settings. Otherwise, the user's browser has to include an Accept-Language: header specifying French as the most preferred language in it's request. Also note the ordering of SessionMiddleware, LocaleMiddleware and CommonMiddleware in the above doc. I have recently updated the various places where we suggest or supply MIDDLEWARE settings, but you may find that your settings have LocaleMiddleware after CommonMiddleware and you should fix that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

[MM3-users] Re: Migrate from mysql to postgresql

by Mark Sapiro

On 03/17/2018 01:44 PM, Bjoern Franke wrote: > Hi, > > is it possible to migrate a mailman3-mysql-database to a > postgresql-database? > > I tried to convert it with pgloader, but some identifiers had to be cut off: > _address_id); > 2018-03-17T21:33:39.087000+01:00 WARNING PostgreSQL warning: Bezeichner > idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e > wird auf idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac > gekrzt I suspect the issue is due to the way Mailman supports different databases via SQLAlchemy. The bottom line is the table and column specifications are based on the Mailman database models, but are database specific. If I were doing this, I would dump the data from MySQL, but rather than using the CREATE TABLE queries from the dump, I would let Mailman create a new PostgreSQL database and then just load the existing tables from the MySQL dump. However, that may all be irrelevant. I don't know which table/column that specific item comes from, but it appears just visually that idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_account_e is already truncated so further truncating it to idx_680560_account_emailconfirm_email_address_id_5b7f8c58_fk_ac may not be a problem. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Various patches for mm3 stable 3.3.1

by Mark Sapiro

On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote: > > 1. If I do not set up 'individual' or 'full' personalisation, all is > well and the default footer templates are expanded as expected. However > setting up personalisation causes template expansion to fail > completely, and messages get sent with a blank expansion. Your mailman-debug.patch makes changes to mailman/handlers/decorate.py including wrapping all the relevant code in a try:/except: that logs any exception. If you set the level for logging.error to debug, what do you get in the log? This issue doesn't occur in the unpatched code on my servers - personalized footers work fine - so I think the problem must be something in your patch. > 2. I would find the postorius UI much easier to cope with if the > default template was 'populated' into the UI wherever it was non-blank, > rather than the UI starting off as if no templates were defined at all. This is <https://gitlab.com/mailman/postorius/-/issues/366>. -- 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: mailman-suite: Error 500 on Lists /setting/ pages

by Mark Sapiro

On 11/18/20 8:43 AM, ljsbw-it(a)riseup.net wrote: > I just installed Mailman3 (mailman-suite) on my Server following these instructions: https://lab.uberspace.de/guide_mailman-3.html Please see <https://wiki.list.org/x/12812344> > and everything works fine so far. I can create lists, subscribe people and send mails through lists but when I click the settings button and get redirected to /postorius/lists/listname/settings/ i get an Error 500 message. I couldn't find anything in the logs except the uwsgi log: > [pid: 20568|app: 0|req: 62/62] 100.64.115.1 () {48 vars in 1052 bytes} [Wed Nov 18 16:27:59 2020] GET /postorius/lists/listname/settings/ => generated 1102 bytes in 1438 msecs (HTTP/1.1 500) 6 headers in 209 bytes (1 switches on core 0) I think that uwsgi log message just refers to the delivery of the error page to your browser. What other logs are you looking at? There should be something in Mailman core's mailman.log or the Django log whose location is defined in settings(-local).py, probably mailman-suite/logs/mailmansuite.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: messages with attachments, without text discarded silently

by Mark Sapiro

On 1/27/25 12:35, Schulz via Mailman-users wrote: > Using the current mailman version, I can reproduce the following: > - send a text-formatted email with attachment but without text body to a list. > - the msg will be received by mailman > - the msg shows up in shunt, the log shows: > ile "/usr/lib/python3.12/email/message.py", line 343, in set_payload > payload = payload.encode(charset.output_charset, 'surrogateescape') > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-17: ordinal not in range(128) Please provide the full traceback and the MIME structure of the message. > an attempt to unpickle the file leads to the same error. > I know it's uncommon to send emails without txt but with attachments - but it may happen; at least we would welcome an error message. Without more of the traceback I can't be sure which handler is doing this and without the MIME structure I can't be sure what's going on. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/29/2017 03:46 PM, Barry Warsaw wrote: > On Mar 30, 2017, at 12:34 AM, David Krantz wrote: > >> When starting this as the recipe seems reasonable I find that I have >> no reliable source for git links for the parts. Some of the git links >> I find are marked with "do not use" so it is a bit hard having >> confidence in selecting one of the others. > > All the Mailman 3 suite subprojects are listed here: > > https://gitlab.com/mailman > > Those project links will take you to the active git repositories. The only > one you should not use is mailman-bundler. To be more specific, the projects that are required for a fully functioning Mailman installation with Postorius and Hyperkitty are Mailman (the core) Hyperkitty (the archiver) Postorius (the web list management UI) django-mailman3 (common django things used by Postorius and Hyperkitty) MailmanClient (python bindings for the core REST API used by Postorius and Hyperkitty) HyperKitty - Mailman plugin (plugin for the core to communicate with Hyperkitty) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: configure Mysql and postfix on mailman3

by Mark Sapiro

On 02/20/2018 10:01 AM, Abhilash Raj wrote: > > One _hack_ that I can think of is that when using maps for postfix, Core calls the "postmap" command to generate the maps from the files that it generates. You can potentially provide a script that updates the MySQL database with the same configuration instead of generating maps and specify that script in configuration to be called by Core instead of "postmap". More information on how to do this. On mail.python.org we want to do some manipulations to the various maps, so we have a script to do this. The first step is in your mailman.cfg file, add an [mta] section if there isn't one and in that section add configuration: /path/to/your/postfix.cfg That file is a copy of mailman/config/postfix.cfg except you change the line postmap_command: /usr/sbin/postmap to postmap_command: /path/to/your/script While you could just edit mailman/config/postfix.cfg directly, this is not advisable as your edits will be lost in an upgrade. -- 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: How well does DMARC mitigation work nowadays?

by Mark Sapiro

On 9/28/25 07:27, tom(a)tomsmyth.ca wrote: > Specifically the kind where all list emails come from the the same address, with the sender in Reply-To? > > It seems like this /should/ be the way it works. Isn't that what Reply-To is for? > > Do some email clients still mess it up? If they do, wouldn't it make sense to just send them a bounce notice and tell them to clean up their act? See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/handlers/dmarc… for what we say about this. I'm guessing that your concern is that a `reply` as opposed to `reply all` should go to the poster and not to the list. I think that will be the case with most mainstream MUAs, but RFC 5322 is somewhat wishy-washy about that saying only "When the "Reply-To:" field is present, it indicates the address(es) to which the author of the message suggests that replies be sent." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 3 days

[MM3-users] Re: Mailman core: basic internationalization howto?

by Mark Sapiro

On 10/04/2017 12:33 PM, thor.rustad(a)gmail.com wrote: > I finally got around to testing this setup. First I verified that the template in /var/templates/site/no was picked up when subscribing. Then I changed the text, and it stopped working. If I add one of these three Norwegian letters to list:user:action:subscribe.txt, I get the following in logs/mailman.log: > > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) Uncaught runner exception: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) ... > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 576, in _handle_confirmation_needed_events > msg = UserNotification(email_address, confirm_address, subject, text) > File "/usr/local/lib/python3.6/site-packages/mailman/email/message.py", line 124, in __init__ > @public ??? > UnicodeEncodeError: 'ascii' codec can't encode character '\xe5' in position 153: ordinal not in range(128) > Oct 04 19:18:41 2017 (29) SHUNTING: 1507144721.896973+35dc93aa969a0934bf717ca07965b09924eca59d See my comment at <https://gitlab.com/mailman/mailman/issues/413#note_42453740>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Understanding of members, accounts

by Mark Sapiro

On 5/11/20 5:15 PM, Peter Adebahr via Mailman-users wrote: > Is the solution to "sign up", using one's very e-mail address already in > the system? Yes. The address is in the Mailman Core part of the systen, but not in the web UI part. > I would like to understand why there is a difference between being > (only) a subscribed member and a member having an account - or, what > might be the advantage of being a member without an account? Being a mailing list member is a Mailman core concept. It usually says you receive posts from the list based on your delivery status and you can post based on your moderation status. Logging in to the web UI to access HyperKitty and Postorius is a Django concept and requires a Django account. If all you want is to post by email and receive messages from the list, you don't need a Django account, but to manage your user settings via Postorius and to visit private archives, you do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

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

by Mark Sapiro

On 2/12/25 12:05, Christian via Mailman-users wrote: > That worked. > > Now on > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman > -automatically it says > > "Pay attention to the config file output above and make sure that you see > /etc/mailman3/mailman.cfg there. If the config path is different, you should > make sure to create a new config file at /etc/mailman3/mailman.cfg and > re-run the command." > > Well...mailman info yields > > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.7.3 (default, Mar 23 2024, 16:12:05) > [GCC 8.3.0] > config file: /opt/mailman/mm/mailman.cfg > db url: postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > Should I create a new config file at /etc/mailman3/mailman.cfg ? You can, but the easiest thing is just replace the line Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" in /etc/systemd/system/mailman3.service with Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg" -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 9/5/25 03:37, Wikinaut wrote: > It's going about the variable $mailinglist_url in footers. Mark exlained, that in mm >= 3.3.10 this placeholder can be used in footers, given, that you have set up $base_url. > > This does not work for me. I need to know, WHERE to set $base_url to make $mailinglist_url become working and replaced in footers. The base url setting for this is an attribute of the domain. Setting it in the Domains view of Postorius or via REST will not be available until the next release, I.e. Mailman core 3.3.11, Postorius 1.3.14, Mailman Client 3.3.6. In the mean time with Mailman core 3.3.10, you can set this via `mailman shell` or by directly updating the `domain` table in the database. In mailman shell >>> d = getUtility(IDomainManager).get('mydomain') >>> d.base_url = 'https://mydomain/mailman3/lists' >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Issue with Held Messages

by Mark Sapiro

On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: > > No matter what action I set for member posts (Hold for moderator, > Reject) they are always delivered. I don't know why this would be. Perhaps the member's moderation is set to Accept immediately - you can see this on ther member's options page in Postorius when logged in as a list owner. When the message is delivered, what are the X-Mailman-Rule-Hits: and X-Mailman-Rule-Misses: headers? > When I tried from a non-member email address, the message got held but > when I try to see it I get a Server Error (500) page. The log files shows: > > ERROR 2016-08-18 01:04:30,231 base 21026 34722993152 Internal Server > Error: /mailman3/lists/test.mydomain.com/held_messages > Traceback (most recent call last): ... > File > "/usr/local/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", > line 443, in held > moderation_reasons=entry['moderation_reasons'], > KeyError: u'moderation_reasons' This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] dkim failing

by Mark Sapiro

On 10/15/18 8:37 PM, Abhijith PA via Mailman-users wrote: > > I am seeing dkim fail in mail that people send to lists > /dkim=fail reason="signature verification failed"/ > but it is not happening when the list solely sending mail to subscribers > (like digest, or subscribe/unsubscribe messages etc). I recently added a > new domain to the mailman3. After this I started noticing this issue. > Any help ? Are you saying the DKIM signature on the incoming post fails to validate in the post as sent from the list, or are you saying that a DKIM signature added by your MTA to the outgoing post fails to validate. If the former, this is probably expected. If your list does any content filtering, adds a subject prefix or adds a list header or footer, these transformations will break the incoming DKIM signature. This is why we offer DMARC mitigations. If the latter, you may be doing your own DKIM signing before Mailman applies transformations to the message. You need to sign the message on the way out, not before. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Mark Sapiro

On 10/25/21 1:45 AM, Stefan Bauer wrote: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ... > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Others have found that removing the trailing slash from ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to make it ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost fixes the issue. -- 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: mass subscribers disablement!?

by Mark Sapiro

On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is > there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- 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: How to delete non-users

by Mark Sapiro

On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- 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: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Mark Sapiro

On 1/26/24 07:06, Stephen J. Turnbull wrote: > > I'm pretty sure it will install dependencies. I think (everything I > say below is based on reading the README.md from pipx's pypa.io repo, > so caveat installer) that the complexity that will arise is that (for > example) a naive approach like > > $ pipx install mailman > $ pipx install mailmanweb > $ pipx install postorius > $ pipx install hyperkitty > > will create 4 separate venvs with 3 copies of mailmanclient, 3 copies > of django-mailman3, and two copies of Django. But postorius and hyperkitty are dependencies of mailmanweb so only $ pipx install mailman $ pipx install mailmanweb should be required. This should put core in one venv and everything else in another without redundancy. > Besides the space > waste, there's also the small problem that mailmanweb won't have copies > of postorius and hyperkitty in its venv. But it will because they are dependencies of mailmanweb. -- 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: Recipient address rejected: User unknown in local recipient table

by Mark Sapiro

On 8/19/24 16:24, eyoelz--- via Mailman-users wrote: > Error: > Aug 19 15:06:10 xxx-rocky9 postfix/smtpd[153746]: NOQUEUE: reject: RCPT from xxxx.xxxxxx-xx.iphmx.com[xx.x.xx.xxx]: 550 5.1.1 <devops(a)xxx.xxx.edu>: Recipient address rejected: User unknown in local recipient table; from=<xxx(a)xxxx.edu> to=<xxx(a)xx.xx.edu> proto=ESMTP helo=<xx.xx-xx.iphmx.com> Is xx.xx.edu in to=<xxx(a)xx.xx.edu> The same as > main.cf > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > myhostname = xxx.xxx.edu xxx.xxx.edu in myhostname? > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydestination = $myhostname, mailman, localhost.localdomain, , localhost > relayhost = [xx.xx.xx.xx] > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > recipient_delimiter = + > inet_interfaces = all > inet_protocols = all > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp What is the content of postfix_lmtp? In particular is there an entry for xxx(a)xx.xx.edu? > local_recipient_maps =$alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains Is this the complete main.cf? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Domain in welcome message

by Mark Sapiro

On 02/19/2017 02:05 PM, Maadix wrote: > Hi, > I'm having problems with customizing welcome message > > It's working fine for > var/templates/site/en/welcome.txt > > but not for domains or lists , so maybe I'm doing something worng > > I'm using a subdomain as mail_host which is different from the URL Host. > > I've been trying all these combination, with no success: > > var/templates/domains/sub.example.com/en/welcome.txt > var/templates/lists/listname.sub.example.com/en/welcome.txt > var/templates/lists/listname(a)sub.example.com/en/welcome.txt > > I'm running mailman-bundler version 3.0.0 Templating has changed for MM 3.1, and I don't have a 3.0 platform available for testing, but as far as I can recall, the paths var/templates/domains/sub.example.com/en/welcome.txt and var/templates/lists/listname.sub.example.com/en/welcome.txt should be valid for domain and list specific templates and the precedence should be (high to low) list, domain, site, default. I don't know why it isn't working for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: leaving Sympa for MM3

by Mark Sapiro

On 2/20/20 3:12 PM, rance.hall(a)esu10.org wrote: > > Now for the question/hard part. Migrating list archives. > > In Sympa the list archive is just a maildir format directory structure reflecting month/year. In MM3 the Archive is stored in the db with attributes that are likely only available as the message is processed. > > I'd really rather not loose the archive data if I can help it. Does anyone have any thoughts on how I could perhaps import this? It shouldn't be hard. HyperKitty has a function to import archive mbox files. It would be a simple matter to use Python's mailbox module to convert your archive. Something like import mailbox md = mailbox.Maildir('path/to/maildir/directory', create=False) mb = mailbox.mbox('path/to/mbox', create=True) for msg in md: mb.add(msg) mb.close() md.close() Then just run hyperkitty_import to import the mbox. run something like django-admin hyperkitty_import --help for details. Note that if there are already archived messages you need to specify --since to import older messages. -- 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: New releases

by Mark Sapiro

On 9/11/20 8:19 PM, brylon(a)oit.rutgers.edu wrote: > I already have ruby-sass installed and the compress command used to work as expected prior to my upgrading to the latest core, postorius, hyperkitty versions using pip in my venv. > > Does It matter at all when performing the Django-admin commands whether I've activated the venv or not? I think I've tried running them both activated and deactivated to no avail, but any other suggestions? I don't think that's the issue here, but the venv should be active when you run the Django-admin commands. Looking more closely at the error, I see it says ``` File "/opt/mailman/mm/venv/lib/python3.6/site-packages/compressor/base.py", line 282, in precompile mod = import_module(mod_name) ... ModuleNotFoundError: No module named 'sass -t compressed {infile} {outfile}' ``` Thus it appears that compressor is trying to import 'sass -t compressed {infile} {outfile}' as a module instead of executing it as a command. What version of compressor is this? It is working for me on 4 sites with django_compressor-2.4, django_compressor-2.3 and django_compressor-2.2. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > But... here is a thing that I can not understand: If the source (the .po > file) is from november 7th, it doesn't matter how many times you > recompile it: the result will be the same. Correct, but the point is if you download the latest gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file in the distribution, you will find they are identical, so it it appears that the weblate translation hasn't changed since that time. If there are issues in this mailman.po, they exist in weblate too and need to be fixed there. Also note that the translations on weblate only affect strings in the core code. The Mailman core templates are not currently translated in weblate and there are currently no Spanish language templates. One would need to create Spanish translations of all the templates in <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> and submit a merge request to add them to a mailman/templates/es/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 2:55 PM, Jens Günther wrote: > > When I want to get to Mailman Starting Page now I need to Enter the > following URL: https://mailman.xyz.de/mailman3/ to be directly > redirected as expected to > https://mailman.xyz.de/mailman3/postorius/lists/ -> works. > > Problem: When leave out the slash at the end and I ONLY enter the > following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly > redirected to a page, taht does not exist: > https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Huh? that is the same URL as the one above that you say works. Do you mean https://mailman.xyz.de/mailman/postorius/lists without the slash or what. > Where can I change this misbehaviour? In Apache-conf everything seems as > it'S in the docs, for the vHost I do not have any other custom settings. What is the exact content of your RedirectMatch or ReweriteRule or whatebver you are using? -- 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: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/7/21 11:54 PM, Kimmo L wrote: > Hi! > > Thanks for the support and help! > But so far i havent been successful with upgrading my postorius, hyperkitty and django pip packages from python2.7 to python3.5 or higher. As i understand, it was installed 2018 and has not been updated (because it has been working without any problem). Perhaps we can help with that. How are these installed now? What issues are you having when trying to upgrade. > Maybe the easiest way is to create a new deployment and somehow transfer data from old server to new one ? It's up to you which way to go. If you create a new deployment, I recommend following https://docs.mailman3.org/en/latest/install/virtualenv.html. You might also consider Xapian as the search engine - see https://docs.mailman3.org/en/latest/config-web.html#enable-full-text-search… and https://github.com/notanumber/xapian-haystack/tree/master Transferring the data is easy as long as the database is compatible - just dump and load, plus copy some files from Mailman's var/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: multiple sites on a mailman3 server question

by Mark Sapiro

On 12/29/21 8:48 AM, William Oliver wrote: > > What I'm trying to figure out is where uwsgi yanks control from nginx > and does the rewriting. Pulling that proxypass stuff out will stop > mailman3 from coming up, and adding it allows mailman3 to show its > interface, but the address gets referred regardless. > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell > nginx not to push it to port 8000. But I don't see where nginx is > getting told to go to 8000 in the www.domain.com section. If you are following https://docs.mailman3.org/en/latest/install/virtualenv.html you have ``` location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ``` in your nginx config and everything goes to uwsgi. What you want is to put those proxy directives in only the mailman locations as at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and then configure your document root so other locations are served from there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: anyway to change/set options for a bunch of users?

by Mark Sapiro

On 3/22/22 06:19, bob B via Mailman-users wrote: > We just migrated to mailman 3 and one of my admins asked is there a way to change their digest options, when adding a bunch of users via mas subscription? Not yet at least. You could submit a feature request at https://gitlab.com/mailman/postorius/-/issues/new to be able to set Delivery mode when mass subscribing. > I was looking for an option to say all new users are set to digest, but I can't find it. Also, is there a way to select multiple users in list and change their digest options? I believe could do this in mailman2 but I am trying to figure out if this is possible for the GUI in mailman3? No, it's not, and in MM 2.1 you could check the digest option for multiple users in the Membership Management... -> Membership List, but if the list was paginated, you'd still need to go page by page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`

by Mark Sapiro

On 12/22/23 10:34 AM, Wikinaut wrote: > Wheras my older lists handled these format apparently correctly, I now cannot add any more > > "Givenname Familyname" <mailaddress> ; or > Givenname Familyname <mailaddress> > > In any of these cases, only the part <mailaddress> is added. > > Is this strange behaviour know? > What can be done to have the correct function back to working again? There haven't been any changes to this. The issue is almost certainly that when subscribing "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> if there is no Mailman user/address for <mailaddress>, one will be created with display name `Givenname Familyname`, but if there is an existing user/address for <mailaddress>, its display name won't be changed. In this case, you can find the user at https://www.example.com/mailman3/users, click the user's Manage button and update its display name. -- 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: Legit login attempts yield, "An error occurred while processing your request."

by Mark Sapiro

On 8/14/24 3:18 PM, Greg Newby wrote: > > My primary question is: *How can I find out what's causing this*? > > I've looked in all the MM and web logfiles, by "tail -f" while generating > the error, and nothing is logged there. Apache logs shows something like > this: > > x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ > HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" > "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, > like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0" This is django-allauth. Errors should be logged in Django's log which, if yoiu followed our virtual env install doc is /opt/mailman/web/logs/mailmanweb.log. > I've come across this error while trying to do authentication-related > activities that worked before the reboot: Did django-allauth get upgraded to >=64.0. There are currently issues with that. It should be >=0.63,<64.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/31/2018 11:57 AM, Peter Münster wrote: > On Wed, Jan 31 2018, Mark Sapiro wrote: > >>> I have verp_delivery_interval = 10 ... >> >> Which says only every 10th message will be VERPed. You want >> verp_delivery_interval = 1 to VERP every message. > > Hi, > > Why? The smtp relay host would get much more outgoing messages. With > verp_delivery_interval = 10, only 10% of the messages would be > personalized. Shouldn't this be enough to detect sooner or later, that a > recipient address is no more valid? Or is it important, to detect such > failure immediately? Yes, VERP does increase the number of SMTP transactions to deliver the mail from mailman to the outgoing MTA, but in general it has mush less effect on deliveries from the outgoing MTA to the recipient MXs, but with modern hardware, most people seem to find the added overhead of VERP to be minimal. Also, it is possible to have the MTA do the VERPing rather than Mailman. See <https://bugs.launchpad.net/mailman/+bug/558067> for a way to do this in Mailman 2.1. There's nothing for Mailman 3, but all that's needed is to configure Postfix to do it and add an appropriate mail_options= to the smtplib.SMTP.sendmail() calls to enable it. In any case, consider (assuming automated bounce processing is working, which it currently isn't) a list with bounce_info_stale_after = 7 days that gets even a post per day and has a member who is bouncing with a DSN that can't be successfully parsed for the member address (maybe because the bounce is from a forward to a different address) so only a VERPed bounce will be successfully scored. At some point a VERPed post bounces for this member and the member gets a bounce score of 1. Now, the next 9 posts to this list will not be VERPed and by the time the 10th post bounces it's more than a week since the first bounce and the score is reset so this member's delivery is never disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: API privileges question for mailman3

by Mark Sapiro

On 10/14/21 12:41 PM, bob B wrote: > In mailman3 documentation it says: > "Because the REST server has full administrative access, it should never be exposed to the public internet. By default it only listens to connections on localhost." > > So I just wanted to confirm there is no way to limit API access? For example I have a group that wants to use API access to mange their mail lists, but from what I can gather, if I give them access to the API they would have access to ALL the mail lists etc.. I would suspect this is even true if I give them their own domain? > > Is there anyway to limit access via the API to certain lists etc..... No, there isn't. If Postorius is not suitable for some reason, you would need to implement an application on the host to provide a user interface to the API with appropriate authentication and controls. There are some ideas but no actual code at <https://gitlab.com/mailman/lemme>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by Mark Sapiro

On 6/26/22 08:07, Andy Smith wrote: > > On Sun, Jun 26, 2022 at 12:37:05PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > >> Just to be sure: for this feature, is it necessary to click on the >> subject and to choose in the drop-down list “Discard (no >> notification)”, or is it enough, on the .../held_messages page, to >> select the messages and click on “Discard”? > > Doing it from the held messages page will be a one-time thing; it is > only by clicking on the individual message that you can choose an action > for future messages from that address. In case the above is not clear, selecting the message and clicking Discard will only discard that message. To automatically discard all future messages from that sender, you need to set that (non-)member's moderation action to Discard which you can do by clicking on the subject and selecting the Discard moderation action from the dropdown list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Mailman 3 Hyperkitty indexes not being built

by Mark Sapiro

On 10/18/22 05:27, tom(a)gather.coop wrote: > My config looks like this: > > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': os.path.join(BASE_DIR, "fulltext_index"), > ... > I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years. > > What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again. > > Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-n… And answered there. You need to be running several things periodically via cron. For Mailman core, see https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs and for Django, see https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required. The particular job which updates the search index is the hyperkitty update_index job which in current HyperKitty is one of the hourly jobs. -- 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: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/6/21 2:00 AM, marcus.granath(a)gmail.com wrote: > > BUT I don't really follow you when you say that those 3 allowed users to send on the list should also have set to "Moderation: List default"? > How will they then be able to send messages, or what do I misunderstand here? My fault. Sorry for the confusion. I wrote: > Now, no one can post. To allow your set of users to post, you have > choices. The easy way but not secure against spoofing is to set the > Maderation Action for the three allowed members to List Default and toi > create a non-member for no-reply(a)abc.com and set it's moderation action > to List Default. That should have said "set the Moderation Action for the three allowed members to Defer or Default Processing (again two names for the same thing) and to create a non-member for no-reply(a)abc.com and set it's moderation action also to Defer or Default Processing." -- 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: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 2:10 PM, Marco Marinello wrote: > Dear Mark, > > configuration needed much troubleshooting so I'm sure I always restarted mailman core along apache2 but since it's still a testing environment, I took the liberty to test it again for you. > > # pip install https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip > # pip install https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… It appears that https://gitlab.com/mailman/mailman-hyperkitty/-/archive/1.2.0/mailman-hyper… is the latest mailman-hyperkitty, but https://gitlab.com/mailman/hyperkitty/-/archive/1.3.5/hyperkitty-1.3.5.zip is missing some commits. It has https://gitlab.com/mailman/hyperkitty/-/commit/79b22a23d3390db741a8233fa1ff… but is missing https://gitlab.com/mailman/hyperkitty/-/commit/ec9c8ed18798cf8f7e89dfaba001… which is very strange because it does seem to have https://gitlab.com/mailman/hyperkitty/-/commit/705bdbb2fb27be60d17ada7cba84… I Suggest you do pip install -U HyperKitty pip install -U mailman-hyperkitty which will get the latest packages from PyPI or if you want the heads from gitlab, pip install git+https://gitlab.com/mailman/HyperKitty.git pip install git+https://gitlab.com/mailman/mailman-hyperkitty.git -- 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: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 1/31/23 23:33, Odhiambo Washington wrote: > Is this a race condition? > > <CUT> > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > Traceback (most recent call last): > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django_extensions/management/commands/runjobs.py", > line 40, in runjobs > job().execute() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/jobs/update_and_clean_index.py", > line 37, in execute > run_with_lock(update_index, remove=True) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/utils.py", > line 181, in run_with_lock > log.exception("Failed to update the fulltext index: %s", e) > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 470, in __exit__ > self.unlock() > File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > line 420, in unlock > raise NotLockedError('Already unlocked') > flufl.lock._lockfile.NotLockedError: Already unlocked > <CUT> Yes, it is a race between the monthly hyperkitty update_and_clean_index job and the hourly hyperkitty update_index job -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: cannot import name 'parse_header' from 'django.http.multipartparser

by Mark Sapiro

On 2/26/25 07:40, Stefan Bauer via Mailman-users wrote: > Dear Users, > > i recently tried to upgrade to latest MM3 and followed this[1] steps. > > However > > (venv) $ mailman-web migrate > > fails with: > > from rest_framework import mixins, views > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", > line 15, in <module> > from rest_framework.request import Request > File "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", > line 17, in <module> > from django.http.multipartparser import parse_header > ImportError: cannot import name 'parse_header' from > 'django.http.multipartparser' > (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) > (venv) mailman@edmmal03$ vi > /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py > > Could this be a broken dependency? You have an incompatible configuration. django.http.multipartparser.parse_header was removed in Django 4.2. See https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous Your version of djangorestframework is incompatible with Django>=4.2. Try in your venv ``` pip install --upgrade djangorestframework ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

[MM3-users] Re: Which crontab?

by Mark Sapiro

On 11/03/2017 11:43 AM, Pierre Abbat wrote: > According to http://docs.mailman3.org/en/latest/config-core.html, I have to > add "@daily mailman digests --send" to the crontab. Which crontab does it go > in? In the system crontab, the thing after the time is the username, and > there's no user named "mailman" in /etc/passwd. Or should I put a script in / > etc/cron.daily/? The partucular "@daily mailman digests --send" would have to go in the user crontab for the Mailman user. If this is not 'mailman' it is what ever user "owns" Mailman. Further it would require that the path to Mailman's bin/mailman command be in that users $PATH. If it were to go in the system /etc/crontab it would need to be something like @daily user /path/to/bin/mailman digests --send where 'user' is the Mailman user as above. That could also go in a file in /etc/cron.d/ Or you could put an executable script to run '/path/to/bin/mailman digests --send' in /etc/cron.daily Your choice. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/13/21 3:53 PM, Christian Stalberg via Mailman-users wrote: > Is this anything to be concerned about? It seems like an attempted break-in as I have no user named alekos.pantazis. First, this is a Django user, not a Mailman user. > -----Original Message----- > From: noreply(a)lists.ccalternatives.org <noreply(a)lists.ccalternatives.org> > Sent: Tuesday, October 12, 2021 7:55 AM > To: csa(a)web-analysts.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ > > Internal Server Error: /user-profile/ > > TemplateSyntaxError at /user-profile/ > 'd_gravatar' is not a registered tag library. Must be one of: The d_gravatar template tag was introduced by https://gitlab.com/mailman/django-mailman3/-/merge_requests/114 to support the `HYPERKITTY_ENABLE_GRAVATAR = False` setting for the user profile page. It should be OK. The error you see seems to say that django_mailman3/templates/django_mailman3/profile/profile.py contains {% load gravatar %} at line 3 but there is no django_mailman3/templatetags/d_gravatar.py file. Do you have the django_mailman3/templatetags/d_gravatar.py file in your installation? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: spf/dkim/dmarc

by Mark Sapiro

On 5/19/23 09:10, Christian via Mailman-users wrote: > > May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: > to=<billb6951(a)gmail.com>, > relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, > delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host > gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM > domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard > fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: > [192.46.218.224]. To best protect our users from spam and 550-5.7.26 > phishing, the message has been blocked. Please visit 550-5.7.26 > https://support.google.com/mail/answer/81126#authentication for more 550 > 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - > gsmtp (in reply to end of DATA command)) `dig txt lists.ccalternatives.org` reports "v=spf1 a mx ip4=192.46.218.224 -all" It should be "v=spf1 a mx ip4:192.46.218.224 -all" i.e. :, not = > Could the hard fail policy be implicated in the gmail rejection? Yes but only because the ip4 is not effective due to the syntax error. ~all could help, but I suspect replacing the = with : will do 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, 4 months

[MM3-users] Re: List mails blocked from GMX - web.de > Spamfolder

by Mark Sapiro

On 7/19/23 10:45, Stephen J. Turnbull wrote: > > % host -t TXT _dmarc.gmx.net > _dmarc.gmx.net descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@gmx.net" > % host -t TXT _dmarc.web.de > _dmarc.web.de descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@web.de" > > The important part is "p=none", which says that GMX does not reject or > quarantine *solely* because of a DMARC fail.[1] Not exactly. These DMARC records specify policies suggested to be applied by any recipient server to mail From: addresses in these domains. They don't say anything about mail To: addresses in these domains From: addresses in other domains. > Footnotes: > [1] IIRC, the "sp=quarantine" means that some fraction of DMARC > failing mail should be quarantined for testing purposes, but the > default fraction is 0 so that is ignored. Actually "sp" is subdomain policy and specifies the policy to be applied to mail From: sub-domains of the main domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 6:11 PM, David Newman wrote: > On 1/14/22 4:54 PM, Mark Sapiro wrote: >> >> It should work. I suspect you need to go to the list's Settings -> >> Automatic Responses and set `Admin immed notify` to Yes. > > > It's enabled. I think this triggers notifications only for new > subscription requests, not pending ones. Yes. That will send a single notification at the time of the request using the `list:admin:action:subscribe.txt` template. Notices of pending requests are sent by the `mailman notify` command using the `list:admin:notice:pending.txt` template. ... >> You can test `mailman notify` at any time by running it by hand. > > > Thanks. This still isn't working as intended. I took these steps: > > 1. Created the file > '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' The template name is `list:admin:notice:pending.txt`, not `list:admin:action:pending.txt`. Thats why it didn't work. ... > 2. Restarted the mailman3 and mailmanweb services You only needed to restart Mailman core. ... > What I'm trying to do here is replicate a feature from MM2.1, where > pending notifications had URLs embedded in the message. That's not > available out of the box in MM3, and if there's a place for feature > requests I'd be glad to ask that this be made the default. The place for feature requests for Mailman core (which this is) is https://gitlab.com/mailman/mailman/-/issues, however, this is not straightforward as Mailman core doesn't know if you even have Postorius or some other web management UI installed or what the URL to access it might be. Thus it's not just a simple matter of editing templates. It would also require a configuration setting for the base URL for the web admin UI and changes in logic to provide an appropriate replacement depending on whether or not the base URL was configured. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Mark Sapiro

On 07/18/2018 02:07 AM, Sebastian Hagedorn wrote: > > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with > Alembic, as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? Alembic is used by Mailman core to migrate changes in Mailman's data models (database schema). It interfaces with SQLAlchemy <https://www.sqlalchemy.org/> which is used by Mailman core to interface with the underlying SQL database. Alembic is used by mailman developers to create migrations when table and column definitions are modified for some reason. It is not used by end users unless they are actually modifying Mailman's code and database schema. Alembic does not do migrations based on a change in the underlying database engine, e.g. SQLite -> PostgreSQL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

[MM3-users] Re: Hyperkitty performance problem

by Mark Sapiro

On 11/22/24 00:37, Odhiambo Washington via Mailman-users wrote: > On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: >> >> Are Mailman3/Postorius and Hyperkitty supposed to run in separated >> databases, or are they supposed to use the same database? ... > > The official documentation specifies two DBs - one for Mailman Core and the > other for Mailmanweb. > As far as I know, there are no conflicts in the tables so you could use the > same DB for both. And the mailmanweb DB is for HyperKitty and Postorius. I know of no doc suggesting separate databases for HyperKitty and Postorius and in fact accomplishing that would require separate Django instances for HyperKitty and Postorius. I.e., Postorius, HyperKitty and django-mailman3 are all Django applications and use the database configured in Django's settings. Mailman core is separate and uses the database configured in mailman.cfg. As Odhiambo says, there are no table conflicts between these databases so they can be either the same database or separate databases as you wish. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 6/16/22 15:46, Dan Caballero wrote: > Which database table contains these pending subscriptions? I checked the "members" and "address" tables but no luck yet. > > I'm trying to help someone clear a few hundred of these. I can try writing a Python script to use the "hex_token" values in the Python dict. But maybe doing something via MySQL would be easier. The tables are `pended`, `pendedkeyvalue` and `workflowstate`, but don't do it via MySQL. A `mailman shell` interaction like this is better. ``` $ ./mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> util = getUtility(IPendings) >>> for token, data in util.find(mlist=m, pend_type='subscription'): ... if data.token_owner == 'subscriber': ... util.confirm(token, expunge=True) ... >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Cannot connect to SMTP server

by Mark Sapiro

On 8/13/22 15:14, mkummini(a)cmi.ac.in wrote: > > However, I get the following line each time I do a restart > Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 > I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. You only see this message once at startup because it is only issued once until there is a successful delivery. This error can occur for reasons other than an inability to connect to the smtp server. In particular, if there are errors in decorating the message with a header and/or a footer because of permissions or other problems in retrieving a list:member:regular:header or list:member:regular:footer template, this will occur. Have you put templates in Mailman's var/templates directory (possibly named /var/lib/mailman/templates in the debian package). If so, can the Mailman user (I think `list` in a debian package) find and read them? -- 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: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 1/31/25 21:44, Stephen J. Turnbull wrote: > > I don't think that's the best we can do, though. Especially if > Convert HTML to plain is also yes, we want to preserve the HTML part > and convert it, don't we? Not if we're collapsing alternatives. If we're collapsing a multipart/alternative part with text/plain and text/html alternatives to just the first alternative we don't keep the text/html part. The only html parts we keep and possibly convert to plain text are ones that aren't a second or later alternative in a multipart/alternative part. > I think a better (or additional) strategy > would be to check the selected alternative for blank, and if so, drop > it and try again for an appropriate type. The collapsing of a two part multipart message with an empty first part into a single part message with just the second part is the last thing that's done after all other content filtering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: 2.1 -> 3 migration without mboxes?

by Mark Sapiro

On 9/12/25 09:25, David Romerstein via Mailman-users wrote: > Hey, folks. I've searched the list archive but haven't found a relevant thread yet. Any pointers would be helpful. > > I have a handful of lists in a 2.1 instance for which I have web archives but not original .mbox files. Is there a way to migrate those lists, including the years of archives, to 3? Ideally you would have Mailman's archives/private/LISTNAME.mbox/LISTNAME.mbox files which is all you need. If tho don't have those, but you have the periodic archives/private/LISTNAME/*.txt files, you could concatenate those for a list into one mbox file. In some cases the From: headers will be munged. I.e., they may be like From: user at example.com (user name) and you would at least want to replace ` at ` with `@`. If you don't have even those, you would have to somehow process the HTML files into messages for a mbox. There is no way to import the HTML directly into HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

[MM3-users] Re: Good choice of defaults for content filtering?

by Mark Sapiro

On 7/30/20 5:00 PM, hansen(a)rc.org wrote: > Hi all, > > I had MM2 set to the default filtering that I think came OOTB. MM3 has none such and I was wondering: > a. What were those MM2 defaults (My MM2 server is long gone now). You will find the content filtering defaults beginning at <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…>. These have been the defaults for new lists since Mailman 2.1.21. Prior th that, the the default for pass_mime_types was ['multipart/mixed', 'multipart/alternative', 'text/plain'] > b. Is there a better set today. I know that MIME types can be faked, but they have worked. I want to avoid anything that can contain malicious code while also allowing simple text to go through. If you go with the current defaults, except of course for setting filter content on, you can add text/html to pass_types and any html parts that aren't collapsed out by collapse alternatives will be kept and converted to plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Internal Server Error on installing Mailman 3 using PIP

by Mark Sapiro

On 10/28/20 11:04 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As you have suggested in my earlier issue, I have implemented > the latest stable version of mailman 3 through the URL > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > . > > But after the installation through the above URL, when I > tried running the command *elinks http://localhost:8000/postorius/lists > <http://localhost:8000/postorius/lists>* or *elinks > http://localhost:8000/admin <http://localhost:8000/admin>*, I got the error > as *Internal Server Error*. > > I don't find any specific log in mailman.log or in > mailmansuite.log. > > Is there any way to solve this issue ? > You need to hire a consultant who understands Mailman 3 installation to help you with this. The help you need is beyond the scope of this list. I am not available as a paid consultant. I do not do that work. See <https://wiki.list.org/x/4489296> for a partial list of people who do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Mark Sapiro

On 3/15/22 12:22, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > hmm. > the list-url (e.g. where you can subscribe to the list) for my instance > looks like https://$domain/postorius/lists/$list_id/ (that is: it spells > "postorius" rather than "mailman3"). > so i guess the URL should be > https://$domain/postorius/lists/$list_id/confirm/?token=$token, which > unfortunately returns 404. > > also, my postorius/urls.py does not contain an url-pattern for > "confirm", unlike the current one as found on > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> > > > > so i guess this was not possible yet with postorius 1.2.4 Yes, This was added in Postorius 1.3.4 (over a year ago) > yes. > the *current* template. > but not the template that came with mailman3 3.2.1 Which is over 3 years old. You should really be taking up these issues with Debian. Maybe if they got enough pressure from users, they would update their package. -- 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] {Spam?} Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/1/22 1:40 AM, Andy Smith wrote: > > In the job list I see: > > appname - jobname - when - help > -------------------------------------------------------------------------------- > hyperkitty - update_and_clean_index - monthly - Update the full-text index and clean old entries > > so I'm guessing it's that, but there is also: > > hyperkitty - update_index - hourly - Update the full-text index > > which hasn't been noitceably a problem so I wonder why the "and > clean old entries" bit is so much more heavyweight, what exactly it > dopes and if there's any way to make it lighter on resources? The difference is the update_and_clean_index job calls hyperkitty.search_indexes.update_index() with remove=True See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index…. The comments say "Setting remove to True is extremely slow, it needs to scan the entire index and database." I second Mark Dadgar's comment to replace whoosh with xapian. It will help, although it requires rebuilding the entire search index. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. No. the mailman-web migrate command will apply relevant migrations for various django projects. You do need to rin it after upgrading things like hyperkitty, postorius and django-mailman3 and other dependencies which may have defined migrations for various database schema changes, but this will do nothing for your data. For that, you need to dump the mailman and mailmanweb databases on the old server and import them on the new server. > but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: MTA setup

by Mark Sapiro

On 12/24/24 09:31, Arte Chambers via Mailman-users wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> I'm not sure what's going on. Previously, I said > Presumably it has previously requested and received the list_url and > the permalink to put in the message headers. This can be confirmed by > the presence of List-Archive: and Archived-At: headers with values > in the messages from the list. but they aren't there. ... > Archived-At: <> > List-Archive: <> I was able to add that message to a test list with no problem, so now it looks like the issue is possibly mailman_hyperkitty not able to communicate with hyperkitty, although the log messages aren't consistent with that. Possibly the issue is not with the message you sent, but with the first message in var/archives/hyperkitty/spool/. Is /1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck the first file in a listing of var/archives/hyperkitty/spool/? If not, what does `mailman qfile` show for the first one? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: Implementing threading [was: hyperkitty failed to create a thread]

by Mark Sapiro

On 2/12/19 8:09 AM, Stephen J. Turnbull wrote: > > I suppose HyperKitty uses References (it works for messages that have > proper Message-IDs ;-), but I don't know what algorithm it uses. > Might be worth looking into, as well as considering a more Postelian > parsing of Message-IDs. Specifically, take the field body, unfold it, > strip leading and trailing whitespace and leading "<" and trailing > ">", and whatever's left is the message ID. Hyperkitty uses In-Reply-To: and if absent falls back to the last item in References: to determine a message's parent. I haven't looked at what happens if the parent is not in the archive but arrives later. We could look at earlier References: items to try to find one we know, but this could result in bad threading if a later reference arrives after we think we've determined the parent. The unfolding of Message-ID: is now correct. See <https://gitlab.com/mailman/hyperkitty/merge_requests/125>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/30/2018 11:38 PM, Peter Münster wrote: > On Tue, Jan 30 2018, Mark Sapiro wrote: > >> The underlying issue is the orange.fr domain is sending DSNs without a >> Message-ID: header. > > Yes. Is a Message-ID header required in a DSN by any RFC? It's not a MUST, just a SHOULD, but RFC 5322, sec 3.6.4 says Though listed as optional in the table in section 3.6, every message SHOULD have a "Message-ID:" field. >> If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] >> section of your config), this log message > > I have verp_delivery_interval = 10 ... Which says only every 10th message will be VERPed. You want verp_delivery_interval = 1 to VERP every message. >> would contain to=<test-bounces+user=example.com(a)my-domain.org> and you >> could identify the bouncing address (user(a)example.com in this case) that >> way. > > Yes, that's my intention, but first of all, mailman must receive the DSN. The message does appear in the mail log, but until the issues below are fixed, even if Mailman receives it, you won't see it. >> Beyond that, there are still other issues, the biggest of which is >> currently, Mailman is not processing bounces other than storing them in >> the database. See <https://gitlab.com/mailman/mailman/issues/343>. > > Shouldn't the DSNs be forwarded to the owner of the list? They should be processed by Mailman and scored as bounces for the recipient if recognized and forwarded if not (depending on settings), but they currently are only stored. >> if a recipient MTA can't create a DSN that has a Message-ID:, would >> you trust what else it does? > > I don't know. The question for me is: does the remote MTA needs a fix > (i.e. the Message-ID is required by some RFC), or mailman (i.e. a DSN > without Message-ID should be acceptable)? I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: Migration advice

by Mark Sapiro

On 08/28/2018 06:42 PM, Quanah Gibson-Mount wrote: > Hi, > > I'm looking at migrating from an old server running mailman 2.1.15 > (Debian wheezy) to a new Ubuntu 18.04 LTS system. I'd like to upgrade > to mailman3 as a part of this migration. I was reading the migration > docs (<http://docs.mailman3.org/en/latest/migration.html>), which seem > to require both mailman2 and mailman3 be installed concurrently on the > same system. Is that correct, or can I rsync the mailman2 list > information onto the new server without mailman2 itself being present, > and import from there? Short answer - Yes. You need only a Mailman 3 installation. You also need a copy of the Mailman 2 lists/LISTNAME/config.pck file for input to 'mailman import21' and a copy of the Mailman 2 archives/private/LISTNAME.mbox/LISTNAME.mbox file for input to the Django management hyperkitty_import command. It would be good to check the archives/private/LISTNAME.mbox/LISTNAME.mbox file with the Mailman 2 bin/cleanarch command, but you can do that on the Mailman 2 system before copying the mbox. -- 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: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 12/8/20 2:01 AM, Krešimir Mihalj wrote: > Hi ! > I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... Have you seen <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > To add member using CLI i tried this command: > > curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members Try this: > curl --user restadmin:restpass --data-raw 'list_id=list.domain.com&subscriber=user(a)email.com' http://localhost:8001/3.0/members > Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com First find the member_id with something like > curl -urestadmin:restpass http://localhost:8001/3.0/lists/list.domain/member/user@email.com which will return json including the value of member_id Then you can do > curl -urestadmin:restpass -X DELETE http://localhost:8001/3.0/members/xxxx where xxx is the member_id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 3:12 PM, Jens Günther wrote: > > > -> the first one works and leeds to > https://mailman.xyz.de/mailman3/postorius/lists > -> the second one redirects to > https://mailman.xyz.de/mailman/postorius/lists > -> which does not exist, since Apache-alias is only for mailman3 Sorry, I missed that it was mailman vs mailman3. > > I only use the apache-conf given in the documentation: > > <code> > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 > unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > </code> I don't use uwsgi so I can't advise on its configuration, but do you have USE_X_FORWARDED_HOST = True SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') in your Django settings? -- 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: Turned on archiving and it is not working

by Mark Sapiro

On 6/9/22 12:09, bob B via Mailman-users wrote: > > Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> > <h1>Authorization Required</h1><p>The archiver key is now > File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > <h1>Authorization Required</h1><p>The archiver key is now > <h1>Authorization Required</h1><p>The archiver key is now The full message is <h1>Authorization Required</h1><p>The archiver key is now required to be sent over the Authorization HTTP header. You need to upgrade the mailman-hyperkitty package to 1.2.0 or newer. > HyperKitty version 1.3.5. As indicated in the above message, HyperKitty >= 1.3.5 requires mailman-hyperkitty >= 1.2.0 If your mailman-hyperkitty is < 1.2.0, you need to upgrade it. If it is 1.2.0, there is some issue with the http headers being dropped in the request from mailman-hyperkitty to HyperKitty. See the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: How to create a list with → advertised =false ← by command line "mailman create [OPTIONS ] LISTNAME" ?

by Mark Sapiro

On 8/5/25 10:20, Wikinaut wrote: > Dear Stephen, > > this was nice but is not working for me. > > I edited a file with name set_user_prefs (without .py) (to preset up user preference in the whole system): It needs a .py extension. > I went to my (venv) and typed > (in /opt/mailman) > > $/opt/mailman: mailman withlist -r /opt/mailman/set_members_prefs > or short > mailman withlist -r set_members_prefs > > and got ... > ModuleNotFoundError: No module named '/opt/mailman/set_members_prefs' > > Perhaps you know, what I did wrong, and can help with a working solution. I guess, it can help many users, too. The file needs a .py extension and it needs to be in a directory containing an __init__.py file. If /opt/mailman/ is not such a directory, it is better to put your script in Mailman's bin directory, e.g. /opt/mailman/venv/bin/set_members_prefs.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: hyperkitty failed to create a thread

by Mark Sapiro

On 2/17/19 2:13 AM, Danil Smirnov wrote: > > Could you advise how to rebuild the failing threads please? I've done index > update with 'django-admin update_index' command but it seems irrelevant to > the issue, I still have all those messages separated: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/2019/2/ I've not tried it and have no idea if it will work, but the query select message_id, message_id_hash, in_reply_to from hyperkitty_email; will show those things. You will see some (most) entries have a message_id of the form 'left-part@right-part' with no angle brackets, but some are of form ' <left-part@right-part>'. In those cases where 'left-part@right-part' of in_reply_to is in a message_id of form ' <left-part@right-part>', you could try altering that in_reply_to to ' <left-part@right-part>' After doing this, you probably need to run 'django-admin runjob thread_order_depth'. Obviously, make backups before you start. An alternative might be to 'fix' the message_id which may or may not require recomputing message_id_hash. -- 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: mailman3 vs postfix

by Mark Sapiro

On 4/29/20 7:35 AM, Ralf Wiegand wrote: > hey Mark, that worked. Thank YOU. Got one step ahead. So after > creating a admin account and logging in via the GUI, I get this error > message: > > > IntegrityError at /accounts/login/ > > UNIQUE constraint failed: account_emailaddress.email > > Request Method: POST > Request URL: http://192.168.0.27:8000/accounts/login/ > Django Version: 2.2.12 > Exception Type: IntegrityError > Exception Value: > > UNIQUE constraint failed: account_emailaddress.email > > Exception Location: > /opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/sqlite3/base.py > in execute, line 383 > Python Executable: /opt/mailman/venv-3.6/bin/python > Python Version: 3.6.8 > > What does this mean? I think it means you have more than one Django account with the same email address. If you can log in to your django admin interface as the superuser, you may be abl to go to 'Users' and delete one. If you can't log in to your django admin interface as the superuser for this reason, you will probably need to create another superuser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: How to Unshunt Specific Message ?

by Mark Sapiro

On 8/11/20 9:55 PM, Shashikanth Komandoor wrote: > Hahahaha. > > Looks like a work around. Yes, it's a workaround. > I understood "moving out of the shunt queue" means "Moving the files from > /var/lib/mailman/mailman/var/shunt directory to any other directory say > /opt/...." in my environment. Because I installed mailman software inside > /var/lib/mailman only. It means first understand why the messages were shunted and fix whatever the underlying issue is or they will just be shunted again. You should look at each message in the shunt queue with `mailman qfile` and determine which ones you don't want at all, which ones you want to save for later and which ones you want to unshunt now. Just remove the ones you don't want at all. For the ones you want to save for later, move them to any other directory at all. Then run `mailman unshunt` for the remaining ones after which you can move the saved ones back or leave them where you moved them to. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 6:38 AM, Jens Günther wrote: > Thank you for your answer. I should have seen that in the Docs, but > somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > I set it in the corresponding file, but unfortunately it doesn't work > :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS > works, changed here from '*' to 'localhost' and my example-domains, this > works). It seems to be the same as this user describes (a while ago): > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… FILTER_VHOST is problematic. It works fairly well for HyperKitty, but not so well for Postorius. In particular with Postorius it doesn't work if there is more than one mail host domain with the current web host. See these issues and MRs for more detail. https://gitlab.com/mailman/hyperkitty/-/issues/254 https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs https://gitlab.com/mailman/postorius/-/issues/394 https://gitlab.com/mailman/postorius/-/merge_requests/500/diffs -- 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: Auto discard after max_days_to_hold not working.

by Hitashi mancho

Thank you so much, Mark and Stephen, for the quick action and response. Waiting for the next release. On Tue, Apr 29, 2025 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/28/25 10:55, Mark Sapiro wrote: > > > > `mailman import21` will import the setting, but per the above comment, > > it doesn't yet work. The setting exists and is exposed in REST, but it > > appears it is not actually implemented. > > > This is now implemented for the next release. See > https://gitlab.com/mailman/mailman/-/issues/1215 and > https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman > core and https://gitlab.com/mailman/postorius/-/issues/628 and > https://gitlab.com/mailman/postorius/-/merge_requests/1001 for Postorius. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to huhamails(a)gmail.com >

5 months, 2 weeks

[MM3-users] Re: Full-text searching: why Haystack instead of PostgreSQL?

by Mark Sapiro

On 6/10/25 02:33, admin(a)bclug.ca wrote: > I've been asked to give a presentation on a recent migration from MMv2 to MMv3 and one of the items in my notes is the question about why Haystack is used for full-text searching instead of PostgreSQL? > > Can someone shed some light on that decision? The people who developed HyperKitty are no longer actively involved with Mailman and I can't speak with any authority about their design decisions. That said, both Django and Mailman core support multiple databases including PostgreSQL, MariaDB, MySQL, Oracle and SQLite whereas Django's full text search relies on PostgreSQL specific features and without some custom implementation, which may not even be possible, would not allow other DBMs. Haystack on the other hand provides a unified API that works with multiple backends. As far as I know, no one has developed a Haystack backend for PostgreSQL full text search, but as Sam notes in another reply, there are supported backends for Solr, ElasticSearch, Whoosh and Xapian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Strange problem in user lists

by Mark Sapiro

On 12/16/21 2:25 AM, Gelpi Andrea wrote: > > I cant' understand why, but I have two members with the wrong name. > > "A B" <C(a)dom.tld> > "D E" <F(a)dom.tld> > > My problem is that A and B must be associated with F(a)dom.tld and vice-versa. > > I tried to delete the user member and recreate it, but it has always the > wrong name. Because the display name is associated with the Mailman user and unsubscribing the user from the list doesn't change the user. > Is it possible to correct those errors? How? The user can log in to the web UI and go to the Account link in the dropdown at the username at the upper right and change the first and last name there. If you have a recent enough Postorius, a site admin can go to the Users link at the top of a page find the user, click Manage and change the Display Name. Otherwise, you can do this in `mailman shell` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Error 500 on held_messages page

by Mark Sapiro

On 2/4/22 04:57, Stephan Krinetzki wrote: > > we have fixed the issue now: Good. > mailman shell -l list(a)lists.example.com > > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > Die Variable 'm' ist die list(a)lists.example.com Mailingliste > >>> lr = IListRequests(m) > >>> for req in lr.held_requests: > ... if lr.get_request(req.id) is None: > ... print(req.id) > ... > 32598 > 22449 > 66937 > 68261 > 92927 > >>> > > With this IDs > > DELETE FROM _request WHERE id IN (32598, 22449, 66937, 68261, 92927); > > And the 500 error is gone. I'm glad you were able to fix it. Do you happen to have the content of those rows in the db before you deleted them? It would be interesting to know what that was to try to determine how that situation happened in the first place. -- 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: Verification emails 'helo' rejected

by Mark Sapiro

On 10/14/24 12:42, Greg Newby via Mailman-users wrote: > > Here are the corresponding logfile entries from mailmanweb.log: > smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 <mail>: > Helo command rejected: need fully-qualified hostname')} > > and from mail.log: > Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from > localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need > fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost> > proto=ESMTP helo=<mail> > > lists.domain.tld is the domain for Mailman3. I don't know why it's trying > to send email from root@. I think the mail.log entry is for the DSN for the failure. The issue is the HELO/EHLO command. Try the following in your venv ``` (venv) ...:~$ python Python 3... Type "help", "copyright", "credits" or "license" for more information. >>> import socket >>> socket.getfqdn() ``` If that returns `localhost`, that's the issue. I think you can fix it by putting a fully qualified domain name in /etc/hostname. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Mark Sapiro

On 6/23/20 10:14 AM, Waqas Ahmed Khan wrote: > > Could you Please confirm, what should be hardware configuration (ram, > processor, disk) to run mailman3 server for medium size organization? This > server will have 10-15 lists and some lists having 10k to 20k members. Also > what should be DISK SPACE of the server for Archiving emails? We really don't have hard requirements and a lot depends on what else besides Mailman the server does. First of all, it appears from some reports that 2GB RAM is not enough, but for Mailman 3 alone, 4GB is ample and I suspect that would do for what you describe. For disk, consider mail.python.org This server currently supports 139 Mailman 3 lists. There are a total of over 36,000 known Mailman 3 users. There are archives going back in some cases, decades, with currently a total of over 673,000 archived messages. The Mailman 3 database with all the archived messages and user info is 8.7 GB. The Xapian archive search index is 18 GB. -- 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: Deleting default "example.com" domain breaks everything

by Mark Sapiro

On 7/16/21 11:31 AM, mcarter(a)corneredrats.com wrote: > Hello. I'm new with v3 of mailman. > Installed via aptitude on deb10. > After I logged in as admin, I created my actual domain, as "example.com" was there by default. > I then deleted example.com, and everything broke. > The only site I had was still using example.com. > How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? Try setting `SITE = 0` in your Django settings file. If that doesn't work, try successively 1, 2, etc. One of these should work. Also going back to your prior thread, you had > root@mail:/usr/share/mailman3-web# python manage.py createsuperuser Aside from the python/python3 issue, you should run any Mailman and Django management commands as the Mailman user (probably `list` in your case), not as root. See https://gitlab.com/mailman/mailman/-/issues/920 and https://gitlab.com/mailman/mailman/-/issues/776. -- 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: Hyperkitty Error

by Mark Sapiro

On 12/9/19 5:25 PM, Brian Carpenter wrote: > I am seeing the following error being repeated every 2 seconds in the uwsgi-error.log: > > 01:22:05 [Q] INFO Process-1:19112 processing [compute_thread_positions] > 01:22:05 [Q] ERROR Failed [compute_thread_positions] - 'DiGraph' object has no attribute 'node' : Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/django_q/cluster.py", line 381, in worker > res = f(*task['args'], **task['kwargs']) > File "/usr/lib/python3.6/site-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.node[msgid]["obj"] > AttributeError: 'DiGraph' object has no attribute 'node' > > I am running the docker version of Mailman, version 1.3.0. Any suggestions? See <https://gitlab.com/mailman/hyperkitty/issues/268> fixed by <https://gitlab.com/mailman/hyperkitty/merge_requests/201>. You need to change 'graph.node' to 'graph.nodes' at both line 37 and line 44 in /usr/lib/python3.6/site-packages/hyperkitty/lib/analysis.py to accomodate networkx >= 2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 6/17/22 12:19, Dan Caballero wrote: > Thanks very much for the guidance. I ran the code and received the output for the list but after a commit and exit the members still weren't subscribed. That's expected. The process I posted only removes the pending request so a subsequent subscribe can succeed. > I then ran mailman syncmembers using a list I had. That was able to complete this time and make all the necessary additions. > > I'm going to see about making a wrapper script for future use. Thank you again. For Mailman core >=3.3.5 this should not be an issue. The underlying issue is https://gitlab.com/mailman/mailman/-/issues/729 which is fixed in 3.3.5. Now pending subscription confirmations expire after the configured pending_request_life (default 3 days) so they shouldn't hang around virtually for ever. I just added some sample scripts to https://www.msapiro.net/scripts/. The script at https://www.msapiro.net/scripts/delete_orphans_expireds.py will delete subscriptions pending user confirmation that are older than the current pending_request_life. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Can't Start Mailman3 Core on Fresh Install

by Mark Sapiro

On 7/21/22 10:09, Jonathan Green wrote: > I've triple checked the password in mailman.cfg and used the same > username/password directly in MySQL and was able to get to the mailman3 > database. I did run a test script in python3 using the PyMySQL connector > and got the same error. Is there some permissions issue I need to look for? > I ran the install as user root - perhaps the user running the python script > doesn't have access somehow? First, your primary support resource for the Debian/Ubuntu packages should be Debian. That said, the database access credentials are also configured in the DATABASES setting in your Django settings, although your OP indicates this error is in core. I'm not sure what running the install as `root` will do in the Debian/Ubuntu package, but with that package, the user that needs to access things is `list` and all the Mailman processes should run as `list`. Did your test script do pymysql.connect(user='list', ...)? -- 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: message awaits moderator approval

by Mark Sapiro

On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote: > > Now it turned out that there were several relicts of the old list in the > database, in particular in the template table. I removed them using direct SQL > commands. > > Now my new mailing lists work as expected. > > Is this a bug in postorius? I think when I delete a mailing list, all relicts > should be deleted from the database. Were there Postorius custom templates for that list?, I.e. did the template table entries have Postorius URLs. If so, this is probably a Postorius issue. I haven't actually looked, but when Postorius deletes a list, it should delete any of it's templates from the postorius_emailtemplate table and revert the template table entries. Beyond that, Postorius is just telling Mailman core to delete the list, and when Mailman core does that it should probably also remove any var/templates/lists/<list_id> directory and any entries from the template table with context = the list_id. If it doesn't, this is a core issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: attachment.html

by Sam Darwin

Thanks for making this change! It's a big improvement! Another random idea, not required, - using javascript, literally disable or enable all the settings which are disabled or enabled by 'Filter content'. So if someone tries to set 'Convert html to plaintext', they can't, until 'Filter content' is enabled On Mon, Jun 26, 2023 at 10:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 6:22 PM, Mark Sapiro wrote: > > > > You are correct that the UI is not clear on what settings depend on > > Filter content. We need to fix that. > > I've created an issue for this at > https://gitlab.com/mailman/postorius/-/issues/584 and committed a fix at > https://gitlab.com/mailman/postorius/-/merge_requests/815 > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to samuel.d.darwin(a)gmail.com >

2 years, 3 months

[MM3-users] Re: Speed up importing mailman2 lists

by Mark Sapiro

On 2/19/25 06:08, t.maintz(a)fz-juelich.de wrote: > We are currently planning to migrate from mailman2 to mailman3 as a container, have around 1500 lists and would like to complete the migration ideally in a few hours. We would like to switch off mailman2 to have a defined state of the lists and import them to mailman3. The import of all lists via script takes about 3 days. Parallelizing the imports does not work due to lockings in the database. > However, we cannot accept a downtime of 3 days. Does anyone have tips on how we can speed up the procedure or are there best practices for larger environments? What Mailman 3 version are you importing to? I ask because prior to Mailman core 3.3.1, user's passwords were imported and the encryption of the password was quite time consuming. If in fact you are importing to Mailman <3.3.1, see https://gitlab.com/mailman/mailman/-/merge_requests/565 for a patch that will speed this up considerably and see https://mail.python.org/archives/list/mailman-developers@python.org/thread/… for discussion of this change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Mark Sapiro

On 05/29/2017 02:16 PM, Simon Liebold via Mailman-users wrote: > > Now, I get to see the confirmation view and upon confirming I see these > (luckily different) errors like below (same with Django 1.10): > > Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table > 'mailmansuite.django_q_ormq' doesn't exist") > > True, this table doesn't exist in the database. It isn't created by > python manage.py migrate. > > The error is served with HTTP-200. No stack trace in mailmansuite.log. Do you have django_q in INSTALLED_APPLICATIONS in your Django config and do you have # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } in your Django config and are you running django-admin qcluster at startup? See <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

On 10/26/21 8:18 AM, Seth Seeger wrote: > > I have just upgraded to 3.3.4 from 3.3.2 (via docker). > > Do we need to do anything more than reset the delivery status? I am getting (seemingly) continual emails about bounces. I keep running the recipe in the link which resets everyone's delivery status. I've grep'd one member's address out of bounce.log (see below my signature). > > Is it just catching up on old bounces? There is no significant change in bounce processing from 3.3.2 to 3.3.4 If you really upgraded from 3.3.2, I don't know what would be responsible. On the other hand, it looks like you may in fact have upgraded from Mailman < 3.3.1 in which case, those are old, previously unprocessed bounces, and your log certainly looks like that. If you think some or all users shouldn't have had delivery disabled, you can run the mailman shell seccion in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… to re-enable them and let current bounce processing handle the truly undeliverable ones. -- 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: Broken web UI after upgrade

by Mark Sapiro

On 12/16/22 03:36, Odhiambo Washington wrote: > > I am probably getting closer to where the problem is. By looking at nginx > error_log while access the site, I see that there are > just two CSS files that are missing, as shown in the error lo here: > https://pastebin.ubuntu.com/p/7wbwMgqMyS/ > > Question is - why is it specifically looking for these two files > - /opt/mailman/mm/static/CACHE/css/output.93545e20bc30.css > -/opt/mailman/mm/static/CACHE/css/output.e1f0c6022e8f.css > > Where are these files supposed to come from and why are they missing? > I have looked at my current CACHE directory and compared with the backup of > the same site before upgrade and these files aren't the same either: They come from django admin `compress` which used files created by django admin collectstatic. I suggest you run ``` django-admin collectstatic --clear --noinput --verbosity 2 django-admin compress --verbosity 2 ``` where `django-admin` is your django admin command. If this doesn't fix the issue, perhaps the more verbose output will help find the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Speed up importing mailman2 lists

by Mark Sapiro

On 2/24/25 05:36, t.maintz(a)fz-juelich.de wrote: > > Can you tell me how to implement this in Postfix? Here's what we do on mail.python.org which supports both Mailman 2.1 and Mailman 3 lists. We also use an alias domain as described at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… because python.org is a virtual_alias_domain. The relevant settings in main.cf are alias_maps = ... hash:/srv/mailman/data/aliases lmtp_destination_recipient_limit = 1 recipient_delimiter = + relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains transport_maps = ... hash:/opt/mailman/mm/var/data/postfix_lmtp virtual_alias_domains = python.org ... virtual_alias_maps = ... hash:/srv/mailman/data/virtual-mailman hash:/opt/mailman/mm/var/data/postfix_vmap The alias_maps and the hash:/srv/mailman/data/virtual-mailman setting in virtual_alias_maps are MM 2.1 settings. The hash:/opt/mailman/mm/var/data/* settings are MM 3. Since transport_maps takes priority over aliases, if there is a MM 3 list in hash:/opt/mailman/mm/var/data/postfix_lmtp, mail for that list will be delivered to MM 3 via LMTP. If not, and the destination is a MM 2.1 list, delivery will be via the virtual_alias_mapping hash:/srv/mailman/data/virtual-mailman -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: How can I remove anything added by Mailman 3 to the forwarded email

by Mark Sapiro

On 5/9/22 06:00, gscaglia(a)ksdata.it wrote: > I need to use Mailman 3 exclusively for forwarding emails to my customers divided by type. > > The emails must arrive exactly as they are, without any additions, and the lists are managed only by me: the customer ignores that he is subscribed to a list and receives the message as if it were one to one. > > How can I remove anything added by Mailman 3 to the forwarded message, therefore also the links for managing my membership (unsubscribe and modify)? In Postorius do the following: In Templates set list:member:regular:footer empty In Settings: in List Identity set Subject prefix empty in Alter Messages set Personalize None Filter content No Anonymous list No Include RFC2369 headers No Include the list post header No First strip reply to No Reply goes to list No Munging in DMARC Mitigations set DMARC mitigation action No DMARC mitigations in Archiving set Archive policy Do not archive this list -- 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: Mailman not able to process "big" requests

by Mark Sapiro

On 04/24/2018 12:36 AM, Abhilash Raj wrote: > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: >> We also have a problem with sending out emails to "large" (>50) groups, >> as they seem to not getting sent out at all. Do you have any idea what >> the problem here could be? > > Which MTA are you using? What do you see in mailman's logs and MTA's logs? > > I haven't seen this kind of problem before with Mailman 3. This very list is hosted using Mailman 3 and I believe has more than 50 subscribers. Nor have I seen this issue. This list currently has 158 non-digest members. There are several @python.org Mailman 3 lists with over 100 non-digest members including the active yt-users(a)python.org list with 301 members, and I have gotten no reports of an issue like this. Also, there are over 600 lists at <https://lists.fedoraproject.org/>, and I don't think this is an issue there either. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: installation

by Mark Sapiro

On 11/21/20 10:42 AM, Christian Stalberg via Mailman-users wrote: > I am working through installing mailman3 on Ubuntu 20.04.1 LTS / apache > 2.4.41 / postfix 3.4.13 and have a couple of questions. > > > > I've installed Django, cloned the mailman-suite repo, installed and tested > apache with Mod_wsgi [ according to > https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/ ] > and it worked fine. Now I am at 'Setting up a WSGI' server in the MM3 > instructions where it says I am to configure uwsgi.ini file. Does that .ini > file go in /opt/mailman/mailman where other .ini files reside? You are mixing apples and oranges. The doc at <https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/> uses mod_wsgi in apache, It doesn't use uwsgi at all. > In setting up the apache virtual server [ according to > https://docs.mailman3.org/projects/postorius/en/latest/deployment.html?highl > ight=apache#apache-with-mod-wsgi ] I do not find a postorius.wsgi which > WSGIScriptAlias points to. The file in your WSGIScriptAlias directive should be the wsgi.py file in mailman-suite/mailman-suite_project/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Importing issue from mailman2 to mailman3

by Mark Sapiro

On 3/7/21 3:42 AM, David Partain via Mailman-users wrote: > > Most of it's going fine, as best I can see. However, I get exceptions on some lists that look like this: > > Traceback (most recent call last): ... > pymysql.err.DataError: (1406, "Data too long for column 'info' at row 1") > > My assumption is that what's in the "Info" field on the old mailman2 config is simply too long. Is that correct? Yes. For MySQL and MariaDB the info column is VARCHAR(255). It probably should be defined as a type that allows a longer value, but for now with those DB engines, it is limited to 255 bytes. > In that case, I suppose the right thing is to (1) edit each one, reducing the size, which'll create a new config.pck, (2) pull it over to the new machine, and (3) run the import again. > > Seem reasonable? Yes, that's the workaround. Or you could start over with postgresql as the DB which doesn't have that limitation. -- 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: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass Those are headers for compiling some sass. Possibly you actually have a `sassc` installed in which case you may need COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) in your settings_local.py. See https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#instal… and the Sass compiler section at https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies. -- 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

[MM3-users] Re: Mailman - delete or backup old archived messages

by Mark Sapiro

On 6/17/21 1:00 AM, olenkoigetublim(a)gmail.com wrote: > > I have been using Mailman-Suite (Hyperkitty + Postorius) quite a long time now and now i was wondering if there is any way to erase or export old archived messages and back them up elsewhere (for example messages, that are older then 1 year). Didnt find any suitable option under "python3 manage.py" command and also didnt find any up to date post which related to mailman3 and python3. There isn't currently anything to do this but is shouldn't be difficult to create a script. You'd need to import the Email class from hyperkitty.models.email, set CUTOFF to a datetime.datetime instance with the cutoff date instantiate a mbox to receive the deleted messages and then do something like for email in Email.objects.filter(date<CUTOFF): msg = email.as_message() mbox.add(msg) email.delete() A lot of required housekeeping such as importing django and calling django.setup(), exception handling and reporting would need to be added to the above, but the basic loop should work. -- 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: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/6/22 1:20 AM, Michael Heseltine wrote: > Hi all, > I've done the additional steps > > /opt/mailman/mm/bin/django-admin migrate > /opt/mailman/mm/bin/django-admin createsuperuser > > without error, and also started the services mailman, qcluster and gunicorn without error messages. Did you see my post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and did you run /opt/mailman/mm/bin/django-admin migrate before starting services? > However, I just get an internal server error when I try to access https://lists.mydomain.com/ (which is served by a local apache virthost). > > The apache log shows just one error: > > [Thu Jan 06 10:01:39.201833 2022] [proxy:warn] [pid 3627279] [client 333.333.333.333:59328] AH01144: No protocol handler was valid for the URL / (scheme 'http'). If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule. Do you have all of these apache modules enabled, proxy.conf, proxy_http.load and proxy.load, in particular proxy_http.load? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Main daemon process sticks around after forking

by Mark Sapiro

On 8/6/25 09:03, Jérôme Charaoui wrote: > > I'm running a (rather large) mailman3 instance on Debian 13 (trixie) using the distribution packages. > > To manage the mailman3 daemon, the package installs this systemd service unit: https://sources.debian.org/src/mailman3/3.3.10-2/debian/mailman3.service/ > > It has been working fine until recently: after a reboot, we noticed the mailman3 unit consistently failing to start due to a timeout error. > > I figured out that the timeout was related to the service unit type (Type=forking) and the fact that the main/parent process was forking subprocesses (and running normally), writing a PID file, but it wasn't exiting, so systemd identifies this as an error and aborts the service. The master is not supposed to exit. It continues to run and monitor the child runner processes and will under some circumstances restart a runner that dies. > Since switching to Type=simple, it has been working fine. This is a Debian package issue and should be reported to Debian. See https://wiki.list.org/x/12812344 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: Do i need a mailman-hyperkitty.cfg file?

by Mark Sapiro

On 10/28/24 18:33, Bill Oliver wrote: > > Aha, I thought. I should have changed that. Then I noticed that I > didn't even have a mailman-hyperkitty.cfg file, and I can't find > mention of it in the venv instructions. I *have* installed mailman- > hyperkitty during the "pip install mailman-web mailman-hyperkitty" > step. I did a "find" on /opt/mailman, and it doesn't seem the file is > there at all. > > Do I need this file? Yes. See the last part of the section at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… where it says in part `And, create the /etc/mailman3/mailman-hyperkitty.cfg file containing these settings: ...` > I found a template here: > https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman-hyperkitt… > > > Do I need to copy and paste that in my installation? It, or something as mentioned in the above doc needs to be at the location defined in the `configuration:` setting in the `[archiver.hyperkitty]` section of mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Mark Sapiro

On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: installation

by Mark Sapiro

On 11/22/20 3:54 PM, Henry S wrote: > > Now I am trying to figure out how to configure mailman+postfix to pass > the unnecessarily convoluted world of spam-free certification and ip > blockings by those 'security lawmakers'. > > Any suggestions on how to not be blocked by gmail, hotmail, etc? I have > used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an > appropriate question to this mailman list. You need a fixed IP address and "full circle" aka "forward confirmed reverse DNS" <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. You also need to DKIM sign your outgoing mail from your domain and publish an SPF record allowing your IP as a sender for your domain. I'm not sure, but publishing a DMARC policy, even if it's p=none is possibly helpful with some recipient domains. Beyond that check your IP for blacklisting with a tool like <http://mxtoolbox.com/blacklists.aspx> and monitor your mail logs for blocked email and follow up with the blockers to get unblocked. Things get better over time as your server develops a reputation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by Mark Sapiro

On 12/29/21 3:58 PM, William Oliver wrote: > > I'd like to delete all my archives that are more than a certain age, > e.g. more than a week old. I can easily do that with a cron job, > deleting old files in > > > /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* > > which is, as far as I can see the only place archive emails live. Those are emails archived in the prototype archiver. That's all the prototype archiver does - store the mail there. The HyperKitty archived emails are stored in the mailmanweb database in the hyperkitty_email table. Attachments are in the hyperkitty_attachment table and other tables are also involved. > However... I was wondering if there was some mailman command or config > variable that would accomplish this without using cron. The cron will work for the prototype archives, but it's probably easier to just disable the prototype archiver. For HyperKitty, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: URL-lines in templates get folded

by Mark Sapiro

On 10/18/22 06:52, Frank Steinberg wrote: > Hi, > > I’ve added links to some templates to give owners and moderators > shortcuts to the postorius UI for moderation tasks, e.g., I’ve added > > https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> > > Unfortunately those lines seem to exceed a certain limit and get > folded, so that they appear as, e.g. > > https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> > messages > > (or similar) and are not directly useful. How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? Also are those lines of the form https://... <https://...> what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? -- 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: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 10:12 PM, Torge Riedel wrote: > Am 21.04.20 um 23:08 schrieb Brian Carpenter: >> Maybe I can get the client to agree to use the web domain as part of >> their list address. > > Hi, > > maybe it is a solution for you what I did on my side (since it was > already the setup for mailman2 my customer is happy with it): > > Set everything up in mailman3 with lists.domain.com and define in > postfix (if you use postfix, others should support it also) aliases from > - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail > list. > > In the list setup in mailman3 (available via postorius) define > list1(a)domain.com as an allowed alias for list1(a)lists.domain.com This is a good workaround, however to be complete, you may also want MTA aliases for the list1-*(a)domain.com addresses. Note, I'm currently working on a fix for <https://gitlab.com/mailman/postorius/-/issues/394>. Hopefully that will be in the next Postorius release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Mailman 3 - docker container - sync_members

by Mark Sapiro

On 10/20/20 9:45 AM, holman(a)uw.edu wrote: > I would like to populate list members via the Mailman 3 sync_members script. > > However, I am using Mailman 3 in docker containers and it doesn't appear to have this command. How are others completing this synchronization? I'm not sure what version of Mailman core is in the Docker containers. According to https://asynchronous.in/docker-mailman/NEWS.html, Mailman core is docker version 1.1.1 released Aug 9 2017 which is about the time of MM Core 3.1.0 which is quite old and has neither a `mailman syncmembers` (introduced in core 3.3.2) command nor the older `mailman members --sync` option (introduced in core 3.3.1). There are `rolling releases` <https://asynchronous.in/docker-mailman/#rolling-releases> which should have these. > Searching this list I found a reasonable approach: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Is there a different/preferred solution? The script at <https://gitlab.med.stanford.edu/irt-public/mailman-tools/-/blob/master/sync…> seems fine. The alternative is to update your Docker container to one including the appropriate `mailman` sub-command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: hyperkitty url not found

by Mark Sapiro

On 3/14/22 12:24, Eggert Ehmke wrote: > So I have to use the external url via https? > > I can access the address > https://lists.[1]<tld>_/mailman3/archives/api/_ > > so I set: (<tld> is my existing domain) > > base_url: https://lists.<tld>/mailman3/archives > Now I get this in the mailman.log: > > Mar 14 19:40:21 2022 (166928) ACCEPT: <12973151.uLZWGnKmhe@wookie> > Mar 14 19:40:21 2022 (166932) HyperKitty failure on https://lists.<tld>/mailman3/archives/ > api/mailman/urls: <html><title>Forbidden</title><body> > <h1>Access is forbidden</h1><p>Please check the IP addresses > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > </p></body></html> (403) > In my settings I have my local IP and 127.0.0.1 and ::1. What should I set there? Is whatever is proxying to Django forwarding the IP and are you sure it matches the "my local IP" you set? You might instead try setting base_url to http://localhost:8000/mailman3/archives/ or more likely http://localhost:8000/archives/ (I.e. whatever your webserver proxies the https://lists.<tld>/mailman3/archives/ url to. -- 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: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

Rob's reply in this thread was garbled due to <https://gitlab.com/mailman/mailman/issues/616>. The text of the reply is quoted below. On 7/27/19 12:54 AM, Rob Lister wrote: > > One thing that does occur to me is that my exim header fudge will > probably cause the Message-ID header to move around from its original > position, and if someone is doing hashing or actually validating (gpg > signing?) the headers haven't been tampered with, then it might > complain, since although the message-id hasn't changed, it might be in a > different place in the headers. > > Then again, mailman can make plenty of other modifications and additions > to the headers anyway, so I'm not sure it matters. > > Probably the more correct way to do it is only add a new header if it's > missing, and if it's there, leave it alone. > > This is probably possible in exim with some more variables and a lot of > nested curly braces... -- 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: Delete Django profiles not signed up to a list

by Mark Sapiro

On 1/1/21 4:41 PM, Andrew Hodgson wrote: > > I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? I have attached a script that will delete users from Django's user database (the auth_user table) if there is no Mailman user with the Django user's email address or if there is a Mailman user but it's not a member, nonmember, owner or moderator of any lists. The setting DELETE_MAILMAN_USER controls whether it will also delete the corresponding Mailman user that's not a member, nonmember, owner or moderator of any lists. If set to True, it will. The script has a few installation specific paths that may need adjustment. Also, if Mailman is installed in a virtualenv, the script needs to be run by the python in that virtualenv so that the imports all work (as with the shebang in the script). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: 400 Bad Request when administrator tries to selectively override member options

by Mark Sapiro

On 5/8/21 1:17 PM, ieso(a)johnwillson.com wrote: > This is probably Design Intent, but I'd just like to confirm. > > When an administrator submits partial 'member options', it comes back with the details of a 400 - Bad Request, indicating essentially that all of the member options must be set. > > Screenshot: https://ibb.co/pzM5Z4m > > It would be a bit smoother to check that all values are selected before sending the request, and inform the administrator that they cannot selectively override member settings for their list. > > But most importantly, I would like to confirm that nothing is corrupt/broken in our implementation. What Postorius version is this? I just tried it on Postorius 1.3.5b1 (The HEAD of the gitlab branch), and for a user with no options at all set at the list level, I was able to set `Receive own postings` only with no problem. I think this is https://gitlab.com/mailman/postorius/-/issues/178 fixed in Postorius 1.2.0 by https://gitlab.com/mailman/postorius/-/merge_requests/321 -- 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

[MM3-users] Re: # comment allowed in a template file?

by Mark Sapiro

On 7/24/20 3:19 AM, skenny(a)scss.tcd.ie wrote: > > I'm running Mailman 3 in maxking's Docker container. I'm also using Puppet to do as much configuration as possible, so I'd like to add a comment to the file that reads something like: > # This file is managed by Puppet. > > Is it ok to do this? I may not have searched the docs enough, but I couldn't find anything relating to comments. If you mean can you add a '#' line that won't be part of the actual rendered template, the answer is No. > One other observation in case it's any use: Initially, I created the template files with owner set to "root". This resulted in postings to lists getting stuck in mailman-core. It's vital that these files are owned by user "mailman". Once I changed the owner of the file to the latter, everything worked. I don't think they need to be owned by 'mailman' as long as they are readable by 'mailman' -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

On 5/26/23 4:36 AM, alopez(a)ac.upc.edu wrote: > Hello, > I want to have a mailman configured together with virtual alias. To do that I need to use alias_domain. > I have tried to do it with mailman shell. The domain seams to be created but when I leave the shell and enter again, the domain is not longer there. Because you are leaving mailman shell with exit() which doesn't commit changes. You deed to either explicitly commit with `commit()` or exit with control-D. Recent mailman shell will report in its banner Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. > On the other hand, If I create a domain in administrator interface, it is not listed in the shell. If I create in the web interface, which field correspond to the alias_domain : Domain Name, Display Name , Mail domain? Your Postorius is too old to support alias_domain, and your Mailman core may be too - requires core >= 3.2.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

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

by Mark Sapiro

On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > I resolved this myself with a search that turned up a 2018 post from Mark that suggested typing "mailman aliases" to create the hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where they are on Ubuntu 18.04). I looked in that folder and sure enough it was empty so I typed "sudo mailman aliases" which did indeed create the 4 things that needed to be there: > postfix_domans > postfix_domains.db > postfix_lmtp > postfix_lmtp.db > > But, they were owned by root:root and everything else under that /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the ownership on the 4 files to list:list. Because that's how you ran it. Run sudo -u list mailman aliases. > Seems to have worked! I was perplexed about why I had to do this though because these were created automatically last time I did this, but I figured that out too. Current `mailman start` should create the aliases. -- 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: Monthly job failure

by Mark Sapiro

On 6/25/19 4:08 PM, andrew.bernard(a)gmail.com wrote: > Yes I did. So something is out of sync, the job are referring to lists no longer existing. What is this? I'm confused. The subject of this thread is 'Monthly job failure', but your original post said 'I see this error on startup:' Perhaps you are confused in that the error occurs in 'rebuild_mailinglist_cache_for_month'. That is not a monthly job. That is a queued task to rebuild the cached data for a particular 'by month' view. That task is queued whenever a post is added to update the monthly cache for the year and month of the date of the post, and whenever a thread is deleted to update the monthly cache for the year and month of the date the thread was active. I'm guessing here, but I think you have a task queued for a list that no longer exists in HyperKitty. Go to the Django web admin and look at the DJANGO Q section, particularly Queued tasks, but maybe the others too. Maybe there's a task you can delete. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: migration

by Mark Sapiro

On 7/30/21 12:06 PM, Dave McGuire wrote: > > Is there a way that I can "dump" the configuration from an existing > mailman3 server, and "import" it into a new instance? I'd really like > to avoid re-doing all of the configuration, etc, as there are quite a > few lists and everything is set up pretty much the way I want it. If you use the same database manager it should be no problem to get a dump of the existing Mailman database to load into the new instance, or if these are on the same server, just point the new instance to the existing database. In either case, the database should be loaded and the Django commands `migrate`, collectstatic`, `compress` and `compilemessages` run[1] before starting Mailman services. Mailman core will run any necessary updates to its database upon startup. You may also need to rebuild the HyperKitty search index with the `update_index` Django command, but you may be able to use the existing one if the search engine is the same. [1] See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=colle… et seq. -- 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: mail loops back to myself

by Mark Sapiro

On 6/12/25 05:28, Florian Sukup wrote: > > When I look into the log, first the smtpd receives the message from my > mail client. Then the email is queued. > And then the smtp initiates a TLS layer to send it to the smtpd on the > same machine. For my understanding this cannot be correct. The smtpd at > first should hand it to mailman and not relay it to itself. Is that > correct? That is not correct. Postfix should receive the initial connect and smtp for the list and then transport_maps should tell it to relay the message via lmtp to the configured lmtp_host and lmtp_port (127.0.0.1:8024 per your previously posted mailman.cfg). You have also posted that Postfix main.cf contains transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp What is the content of that file? In particular does it contain mylists(a)lists.yyy.com lmtp:[127.0.0.1]:8024 and is the timestamp of /var/lib/mailman3/data/postfix_lmtp.db >= that of /var/lib/mailman3/data/postfix_lmtp, and have you restarted/reloaded Postfix since updating main.cf? And, is Mailman core running and listening on port 8024? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Implicit destination

by Mark Sapiro

On 08/26/2018 12:54 PM, David Krantz wrote: > > I have a spam-problem like anyone else. Most of the spam my listserver > receives has some kind of impilict destination so the implicit rule > catches most of the spam that way. This is fine. What is not so fine, > however, is that this results in a moderation message to the sender. > I'd like to stop that so that the spammer has no confirmation that the > mail was received. That is not the issue. Sending the held message notice to a spammer, if it reaches the spammer, is probably inconsequential. The issue is that virtually always in spam the sender address is either undeliverable or is the address of an innocent 3rd party. Sending these notices to innocent 3rd parties is called backscatter and is a bad thing. To avoid this backscatter, you can set the list's respond_to_post_requests attribute to False. There are two problems here. One is this setting is not currently exposed in Postorius, and the other is this will also stop desired held message notices such as those from list members. -- 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: content filtering in version 3.1

by Mark Sapiro

On 12/20/19 1:31 AM, Dieter Leupold via Mailman-users wrote: > Hi Mark, > > Thanks for your information. But, how I said, I'm new to MM3 and I have > problems with the syntax of the mailman shell. Please, could you give me > an example to set "pass_types" via MM-Shell? > Thank you very much! The documentation of Mailman shell is at <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…>. A simple example in for setting pass_types is ``` $ bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the list(a)example.com mailing list >>> m.pass_types <generator object MailingList.pass_types at 0x7fd7e1489840> >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain'] >>> list(m.pass_types) ['multipart', 'text/plain'] >>> At this prompt you can enter commit() to commit your changes, abort() to reverse your changes or control-D to commit and exit. You can also enter exit() to exit, but your changes will not be saved unless you have done a prior 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: Correcting name spellings in a list

by Mark Sapiro

On 2/23/21 9:40 PM, Morris Jones wrote: > I typo'd some full names in a mailing list. I want to correct them ... > > I can't see a way to do that in the Member Options, so I thought I'd try > "remove" and re-add, either from the command line or the UI. > > But the name gets readded with the typo intact. :( > > Is there a way to fix it without writing SQL? You can do it with mailman shell. The basic issue is the display name is a property of the user or the user's address, which ever is subscribed to the list. When you add a previously unknown user to a list, Mailman creates these user and address records, but they belong to the user, not the list. There are some threads around this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and a somewhat protracted one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. -- 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: Special Characters Issue when using Wordpress HTML messages

by Mark Sapiro

ryan.anderson.4--- via Mailman-users wrote: > > Thanks for the reply. I changed the language.master in the schema.cfg. > > [language.master] > # Template for language definitions. The section name must be [language.xx] > # where xx is the 2-character ISO code for the language. > > # The English name for the language. > description: English (USA) > # And the default character set for the language. > charset: utf-8 > # Whether the language is enabled or not. > enabled: yes And I replied but didn't include the list. My reply, reconstructed from memory: That change together with restarting Mailman core should allow those characters unreplaced as long as it isn't overridden in mailman.cfg. Note that it will apply only to new messages and not to previously archived ones. However, there are two issues with editing the master this way. It will affect the default settings for all languages, and it will be undone with any upgrade. It is much better to add ``` [language.en] charset: utf-8 ``` to your mailman.cfg -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Include receipant address as a variable

by Mark Sapiro

On 6/4/22 09:22, chucka(a)blackforest-co.com wrote: > Thanks for the quick reply - I'm going to need a bit of schooling. I've looked at the page you point to and ... I'm lost - do I need to create a NL template? Can you give an example? &lt a href=https://mysite.com/my.pdf? &gt CLICK HERE ... The bad news is list headers and footers are plain text so HTML tags don't work. The good news is that many if not most MUAs will render things that look like URLs as clickable links. So, if you create a list:member:regular:header or list:member:regular:footer footer template that contains a line like ``` Go to https://mysite.com/my.pdf?$user_email to ... ``` That will replace the $use_email part with the recipient's lower cased email address. If you want the case-preserved email address, use `$user_delivered_to` instead of `$user_email`. For this to work, the list's Settings -> Alter Messages -> Personalize setting must be `individualize` or `full`. Also see https://wiki.list.org/x/4030707 for some caveats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Mark Sapiro

On 1/30/23 10:12, Odhiambo Washington wrote: > > So, since the creation of that file is prominent in the doco, maybe a note > can be added to that effect? I'm looking at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… and my thought is at the paragraph Regular Expression tables remove the additional dependency of having postmap command available to Mailman. If you want to use regexp or Regular Expression tables, then add the following to Postfix’s main.cf file: add another section header Regular Expression Tables ------------------------- and change that text to Regular Expression tables are less efficient than hash tables, but they remove the additional dependency of having ``postmap`` command available to Mailman. If you want to use ``regexp`` or Regular Expression tables, then add the following to Postfix's ``main.cf`` file My thought is adding the section header makes it more clear that everything down to the Postfix + Dovecot section is for Regular Expression Tables and adding the `less efficient` phrasing notes the down side. What do you think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: mail loops back to myself

by Mark Sapiro

On 6/11/25 13:51, Florian Sukup wrote: > I have now elimiated reverse.rrr.com. But there isn't much change: > > vvvvvvvvvvvvvvvvvvvvvvvvv > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: initializing the > client-side TLS engine > Jun 11 22:19:57 arvak postfix/smtpd[1015581]: initializing the > server-side TLS engine > Jun 11 22:19:57 arvak postfix/smtpd[1015581]: connect from > host.xxx.com[m.y.i.p] > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: warning: host > host.xxx.com[m.y.i.p]:25 greeted me with my own hostname host.xxx.com > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: warning: host > host.xxx.com[m.y.i.p]:25 replied to HELO/EHLO with my own hostname > host.xxx.com > Jun 11 22:19:57 arvak postfix/relay/smtp[1015580]: 29FCF5F867: > to=<mylists(a)lists.yyy.com>, relay=host.xxx.com[m.y.i.p]:25, delay=0.2, > delays=0.06/0.01/0.13/0, dsn=5.4.6, status=bounced (mail for > lists.yyy.com loops back to myself) > Jun 11 22:19:57 arvak postfix/smtpd[1015581]: disconnect from > host.xxx.com[m.y.i.p] ehlo=1 quit=1 commands=2 I think you need to add host.xxx.com to mydestinations. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Postorius performance with over 1000 pending users

by Mark Sapiro

On 6/8/19 9:13 AM, Nick W wrote: > I've got a couple things I need help with: The Symptom and The Problem. > > The Symptom: > > Postorius has gotten quite slow to load, taking more than 30s to load the > Subscription Requests tab. Having zero pending subscription requests (I'm on > v1.2.5), I started investigating unconfirmed subscriptions. > > I followed the commands from here[1] and got this: > > mailman shell -l your.list.id > util = getUtility(IPendings) > print(len(list(util.find(mlist=m,pend_type='subscription')))) > 1816 > > Wow, 1816 pending subscription requests. I can say for certain that my list is > not popular so these requests must have been submitted by bots. Let's get there > in The Problem. > > How can I "purge" this list? I'm willing to assume that none of these requests > are valid and would reject all unconfirmed user requests. mailman shell -l your.list.id util = getUtility(IPendings) for token, data in util.find(mlist=m, pend_type='subscription'): util.confirm(token, expunge=True) -- 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: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/17/20 1:31 PM, tlhackque via Mailman-users wrote: > > I might also add the rule number or config filename:line, as in > > Header "{name}": rule in {file}:{n} matched value "{value}" > > This would be helpful when backtracking from a rejected message to the > cause. > > A sample expansion might be: > > Header "X-Spam": rule in foo.conf:83 matched value "yes" These rules are not in a configuration file. They are in the headermatch table in the database and the rules for a particular list are exposed on the Header filters tab in Postorius or at the REST lists/LISTNAME/header-matches endpoint. Perhaps something like {name}: header match rule, pattern "{pattern}" matched value "{value}" example: subject: header match rule, pattern "sex|long|list|of|other|bad|words" matched value "This is a post about filtering based on words like sex in the subject." but that could be just adding more clutter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Sapiro

On 2/15/21 9:07 PM, Mark Dadgar wrote: > So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. > > The resulted in a broken web interface. > > Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. > > Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. > > Anyone got a solution to this? From the tracebacks it looks like Django is broken. I would suggest starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ aside and create a new venv virtualenv /opt/mailman/mm/venv/ and then activate it and pip install everything. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > – but the existing directory /opt/mailman/fulltext_index (and its > contents) are readable and writeable by mailman:mailman: > >> drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ >> >> -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc >> -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg >> -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg >> -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg >> -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg >> -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg >> -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > I fail to see where haystack tries (and fails) to create the directory. > FWIW, deleting threads is not a problem. It is uwsgi trying to do this. What user is it running as? Maybe you need to add that user to the `mailman` group. Deleting threads is not an issue, apparently because it doesn't try to update the search index. -- 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: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Mark Sapiro

On 12/6/21 2:51 AM, Stefan Bauer wrote: > Need to bring this up again. Django now sends with STARTTLS, but mailman > itself, does still only drop mails in cleartext. > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > No starttls=1 at all :( > > Does the above settings work for anyone? > > etc/mailman3/mailman.cfg > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: > smtp_verify_hostname: false > smtp_verify_cert: false > smtp_secure_mode: starttls This should work. What do you see in Mailman's smtp.log if you add ``` [logging.smtp] level: debug ``` to mailman.cfg. However, do you really need this. It will only affect delivery from Mailman to Postfix via the loopback interface on the localhost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Poor rendering of disabled registration page

by Mark Sapiro

On 12/22/24 04:16, Torge Riedel via Mailman-users wrote: > > 1. The page has a poor rendering, as far as I can see not css is referenced > 2. A would prefer that I am able to hide the registration button > > Is either of this possible to be fixed in the future? The lack of styling is fixed for django-mailman3 1.3.16 by https://gitlab.com/mailman/django-mailman3/-/merge_requests/303 You can fix it by adding the django_mailman3/templates/account/signup_closed.html file as in this patch: ``` diff --git a/django_mailman3/templates/account/signup_closed.html b/django_mailman3/templates/account/signup_closed.html new file mode 100644 index 0000000..bc83950 --- /dev/null +++ b/django_mailman3/templates/account/signup_closed.html @@ -0,0 +1,11 @@ +{% extends "account/base.html" %} + +{% load i18n %} + +{% block head_title %}{% trans "Sign Up Closed" %}{% endblock %} + +{% block content %} +<h1>{% trans "Sign Up Closed" %}</h1> + +<p>{% trans "We are sorry, but the sign up is currently closed." %}</p> +{% endblock %} ``` Disabling the signup button on the resultant page is trickier as that currently comes from the hyperkitty/templates/hyperkitty/base.html which is used all over. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

[MM3-users] Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by Mark Sapiro

On 1/26/22 22:21, dave--- via Mailman-users wrote: > > Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. > > The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). The password reset is for a Django user, which is distinct from a Mailman user. The users you added via the web API are Mailman users, but in order to access their lists via the web UI they have to `sign up` to create a Django account. -- 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: Mails sent by mailman-web runjobs hourly

by Mark Sapiro

On 6/16/22 03:44, Eggert Ehmke wrote: > I get lots of mails originating from the mailman-web runjobs hourly. They are > sent to mailman@<mytld>. The content looks like > > 07:00:03 [Q] INFO Enqueued 12571 > 07:00:03 [Q] INFO Enqueued 12572 > 07:00:03 [Q] INFO Enqueued 12573 > > How can I disable these emails? These message come from Django Q, https://django-q.readthedocs.io/en/latest/ I don't think there is a way to disable those specific messages which occur at times when tasks are queued instead of started immediately. They are sent to `mailman` because `mailman` owns the crontab and the crontab has no MAILTO=. You can redirect these and all other messages from hourly jobs by surrounding the hourly jobs command in the crontab with MAILTO= as in ``` MAILTO=other(a)example.com @hourly /opt/mailman/mm/bin/django-admin runjobs hourly MAILTO=mailman ``` or possibly discard them with something like ``` @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > /dev/null ``` but either of these could redirect or discard other messages from hourly jobs which you might want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/12/21 3:21 AM, Victoriano Giralt wrote: > > I just wanted to make visible that the .mo files were a "bit old". For > example, Guillermo, in this thread, pointed that the Spanish > translation was quite compelte. Actualy, I spent some hours bringing > them to 100% around Christmas. But, the .mo file for es from the pip > install --update i did recently is dated November 7th. I have > definitely added a lot of translated material from then until the end > of the year. Why do you say the .mo files are old. The timestamps are all Feb 3 02:47 which is when the package was built for PyPI. > I know the translation happens outside the development community. I > tried to point that there might be some synchronisation problem, so to > say, between the translation site and the packaging of the latest > mailman release. When things are changed on weblate, we get automatically generated merge requests to update our source. We don't always merge them immediately, but we certainly do merge all the outstanding ones before making a release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Schedule for a resolution of #406, #410 and #437

by Mark Sapiro

On 12/14/2017 02:14 PM, Abhilash Raj wrote: > On Wed, Dec 13, 2017, at 12:11 AM, Henrik Rasmussen wrote: >> I was wondering when #406<https://gitlab.com/mailman/mailman/issues/406>, >> #410<https://gitlab.com/mailman/mailman/issues/410> and >> #437<https://gitlab.com/mailman/mailman/issues/437> could be fixed. It >> seems that it would not be far, as >> !322<https://gitlab.com/mailman/mailman/merge_requests/322> is ready to >> be merged. > > Merged right now! :) And I have updated lists.mailman3.org and mail.python.org. Note however that <https://gitlab.com/mailman/mailman/merge_requests/322> does not fix <https://gitlab.com/mailman/mailman/issues/437> as noted at <https://gitlab.com/mailman/mailman/issues/437#note_46539617>. It also doesn't fix <https://gitlab.com/mailman/mailman/issues/441>. That appears due to a new bug related to <https://bugs.python.org/issue27321>, but which is a different message defect that causes UnicodeEncodeError to be thrown instead of KeyError. I have reported this at <https://bugs.python.org/issue32330>. I have created <https://gitlab.com/mailman/mailman/merge_requests/350> and <https://gitlab.com/mailman/mailman/merge_requests/351> to fix these issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: So near, and yet so far (Configuring Mailman)

by Mark Sapiro

On 1/29/21 3:52 PM, Jack Lenox via Mailman-users wrote: > > Good news everyone! I've got it working. It turns out my issue was with > the mynetwork IP settings in my Postfix config. Things do now appear to > be working. Good. Thanks for the update. > My only remaining issue is that the posts aren't appearing > in the archive. Hmm. If you want our help with that, tell us if you have any non-default [archiver.*] settings in mailman.cfg and what the list's Settings -> Archiving settings are. If you are expecting HyperKitty archiving, are messages remaining queued in Mailman's var/archives/hyperkitty/spool/ directory and if so, what kind of errors do you see in Django's log? Does the value for MAILMAN_ARCHIVER_KEY in your Django settings match the api_key in the [general] section of the mailman-hyperkitty.cfg (or whatever you call it), quoted in MAILMAN_ARCHIVER_KEY but not in api_key, and is the base_url setting in the [general] section of the mailman-hyperkitty.cfg a URL that can actually access hyperkitty? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/21/23 14:50, ceo(a)sartrack.nz wrote: > I copied the wrong debug data in my original post, it should be this: > > --------> mailman3_router router <-------- > 2023-05-22 05:13:59 115223 local_part=templist domain=sartrack.nz > 2023-05-22 05:13:59 115223 checking domains > 2023-05-22 05:13:59 115223 sartrack.nz in "sartrack.nz"? yes (matched "sartrack.nz") > 2023-05-22 05:13:59 115223 data from lookup saved for cache for +mm_domains: key 'sartrack.nz' value 'sartrack.nz' > 2023-05-22 05:13:59 115223 sartrack.nz in "+mm_domains"? yes (matched "+mm_domains") > 2023-05-22 05:13:59 115223 checking require_files > 2023-05-22 05:13:59 115223 file check: /var/lib/mailman3/lists/${local_part}@${domain} > 2023-05-22 05:13:59 115223 expanded file: /var/lib/mailman3/lists/templist(a)sartrack.nz > 2023-05-22 05:13:59 115223 stat() yielded -1 I'm not an Exim expert although I have used it. The above says Exim was unable to stat /var/lib/mailman3/lists/templist(a)sartrack.nz - does that file exist. Does exim have search permission on all the directories in the path and read permission on the file? > 2023-05-22 05:13:59 115223 errno = 2 > 2023-05-22 05:13:59 115223 mailman3_router router skipped: file check -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Migration of the e-mail templates

by Mark Sapiro

On 3/6/25 2:24 PM, Markus Grandpré wrote: > > Thank you for your prompt reply. Based on a customer request, it seems > that custom templates need to be copied manually. Could you kindly > indicate which files and locations should be considered when > transferring them from the source to the target system? In MM 2.1, you could have list specific templates in directories like lists/<listname>/<language>/, domain specific templates in directories like templates/<list.host_name>/<language> and sitewide templates in directories like templates/site/<language>. In MM 3 You can create list and domain specific templates in Postorius or you can create them in sub-directories of Mailman's var/templates/ directory. List specific templates in lists/<list-id>/<language>/, domain specific templates in directories like domains/<mail-host>/<language>/ and sitewide templates in directories like site/<language>/. However, you can't just copy MM 2.1 templates because the variable replacement syntax is different and the template file names are different. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for documentation of the MM 3 templating system. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Reg Archive Inactive Status and not working in Mailman

by Mark Sapiro

On 9/23/25 04:40, nirmal--- via Mailman-users wrote: > I am having the issue with Mailman Archive not working. Kindly help me to solve the issue. > > > Errors Found in:- > File "/usr/lib/python3/dist-packages/requests/adapters.py", line 489, in send > resp = conn.urlopen( > ^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 789, in urlopen > retries = retries.increment( > ^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 594, in increment > raise MaxRetryError(_pool, url, error or ResponseError(cause)) > urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='list1.iitm.ac.in', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive?key=n%2FZZnR5bRgNdUEyNK4p731C1%2BgWJLw0%2F (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992)'))) Your setting for base_url in mailman-hyperkitty.cfg is an https url, but the addressed server is not configured properly to handle https. If the setting is something like base_url: https://localhost:8000/hyperkitty/ change it to http or change the url to the one used to access hyperkitty from a web browser. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks, 1 day

[MM3-users] Re: Setup Mailman3 on shared webhost

by Mark Sapiro

On 11/5/18 5:42 AM, Keyra wrote: > Iam trying to setup mailman3 on a shared webhost (with ssh access). I > could use > > pip3.6 install mailman --user > > and also > > mailman info > > But when I try to start mailman using > > mailman start > > I will first get the error message > > TypeError: expected str, bytes or os.PathLike object, not NoneType > > and when I try it a second (and third etc.) time, it throws > > Starting Mailman's master runner > /usr/bin/python3.6: can't open file '/usr/bin/master': [Errno 2] No > such file or directory > > I didn't get any error messages during installation, so I guess whatever > mailman is looking for in /user/bin/master is available in my > /home/user/ folder, but I have no idea where and how to tell mailman to > look there. For more infos, this is the output of `mailman info` The 'master' command should be in the same directory as the 'mailman' command that you run. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: What implications do GDPR have on Mailman, and how to requiring members to accept registration

by Mark Sapiro

On 05/18/2018 03:50 AM, Henrik Rasmussen wrote: > > What I meant was, that the list admin may be able to set the list to Open or Moderate, making it possible to subscribe others, and I was told by our GDPR folks that we have to make the subscribers re-confirm, so I was just trying to figure out a way to do it. I don't know very much about GDPR yet. Setting the policy to Confirm or Confirm, then Moderate will do that as long as admins don't use the mass subscribe feature without a confirmed request from the user. > Is there a way to resend a confirmation request to either those who haven't been requested to confirm or alternately to all subscribers? Manually. I.e.post a request to the list with a deadline for response and remove those that don't respond. Or, post to the list that everyone will need to resubscribe and then remove everyone. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Can't remove footer(s)

by Mark Sapiro

On 10/02/2018 01:03 AM, Henrik Rasmussen wrote: > > Copying /dev/null doesn't help. It seems to be the same old content of the footer files before I removed the files and restarted Mailman, as if Mailman keeps the cache. > > I've just (again) ran > # docker exec -it mailman-core mailman shell -l [LISTNAME_FQDN] >>>> getUtility(ITemplateManager).delete('list:member:digest:footer', m.list_id) >>>> getUtility(ITemplateManager).delete('list:member:regular:footer', m.list_id) > > after copying /dev/null to the files in /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/list_member_digest_footer.txt and list_member_regular_footer.txt ,but that doesn't change anything. The templates named list_member_digest_footer.txt and list_member_regular_footer.txt (with underscores) were created by import21 and set as the URIs for those templates. Had you just copied /dev/null (or otherwise made empty) those files and done nothing else, that would have done what you wanted, but since you deleted the template URIs for the list, the template names are now the default list:member:digest:footer.txt and list:member:regular:footer.txt names (with colons) and those are the empty files you need to create. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/27/21 4:04 AM, Henrik Rasmussen wrote: >> Thanks for the hint Steve. There is a Spanish message catalog as >> evidenced by the fact that the reason was translated to Spanish, but the >> issue is almost certainly that there is no >> mailman/templates/es/list:user:notice:post.txt template so we fall back >> to the one for the list's language. > > I should note that my tests on same list with same language setup did not mix languages, for some reason and I can't replicate the problem. I wonder if it could have been a timing issue or the order that I changed languages on list language and user preference. I really think it has to do with two conditions: 1) the user's preferred language is Spanish 2) there was no mailman/templates/es/list:user:notice:post.txt template There were Spanish templates in Mailman core 3.3.4, but they were misnamed, e.g. list_user_notice_post.txt instead of list:user:notice:post.txt. Did you somehow add a mailman/templates/es/list:user:notice:post.txt template after the initial test? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: nginx configuration on a multitasking server

by Mark Sapiro

On 12/22/21 6:20 PM, David Newman wrote: > > Update: The above worked fine until MM3 informed a list owner of pending > subscription requests, with a URL like this: > > https://lists.example.com/mailman/admindb/listname > > and that URL returned a 404 error. This looks like a uwsgi issue as discussed at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… although that's with apache and not nginx so it may not be. > Adding a stanza for 'location /mailman/' to the nginx config above > clears the 404 error, but Postorius returns "Page not found" with no > entry in the web or MM3 logs, and a 200 OK in the Nginx logs. > > I think the URL is supposed to go to the list page in Postorius. How to > configure this so that list owners and moderators get a valid URL for > list management? I'm not sure what the solution is in this case, but a workaround would be to add url(r'^mailman/', include('postorius.urls')), to the urlpatterns list in urls.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: deleting a list of spammers from non-member list

by Mark Sapiro

On 10/2/25 11:41, Philip Bondi via Mailman-users wrote: > Hello to all: > > I've studied the following: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > ```bash > mailman shell -l mmlist.domain.ca << EOF | tr , '\012' > nonmember.txt > list(m.nonmembers.members) > EOF > ``` > > I was able to produce a clean list of 50 non-member email addresses that are spammers. > > How would I take this list of non-members and delete them? I was unable to use mailman delmembers Assuming you want to delete all the nonmembers, just do it all in mailman shell. Using the above ```bash mailman shell -l mmlist.domain.ca << EOF for member in m.nonmembers.members: member.unsubscribe() EOF ``` If your 50 addresses are not all the nonmembers and you only want to delete those 50, the bash script could be ```bash mailman shell -l mmlist.domain.ca << EOF for addr in open('nonmember.txt').readlines() member = m.nonmembers.get_member(addr.strip()) member.unsubscribe() EOF ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 6 days

[MM3-users] Re: [Spam] Installation Help on Ubuntu 18

by Mark Sapiro

On 8/2/20 12:42 PM, Odhiambo Washington wrote: >> >> It is currently linked from the first paragraph at >> <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. >> > > I followed the steps outlined in the subject document and got mailman3 > running. > However, what is missing in that document is the process of setting up a > webserver for accessing the MM3 UI. > I have spent two days trying to figure out that aspect and discovered a few > things (I could be wrong in what I think): Which document are you talking about? If you mean <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…>, that talks about the Debian/Upuntu package installation and that package is quite behind the current releases. I thought that after mush back and forth with you following <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> you got Mailman 3 up and running, so why would you now be trying to install the Debian/Ubuntu package? If you have issues with the <https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…> document, you should contact its author. See <https://wiki.list.org/x/12812344>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by Mark Sapiro

On 11/8/21 11:10 AM, dancab(a)caltech.edu wrote: > > We do have mailman(a)caltech.edu configured with valid members/owners. > We're using Postfix for the MTA. Is it possible there's a misconfiguration there? > > We've been testing the system with a handful of lists for months. The bounce you saw From: Mailman mailman(a)example.com To: Mailman Bounces mailman-bounces(a)example.com Subject: SMTP Delivery Failure may have sent because you have VERP probes enabled (verp_probes: yes in the mta section of mailman.cfg) and a user on some list reached the bounce score threshold and a Mailman attempted to send a probe and the MTA refused the message, or it may have been sent because Mailman attempted to send a message to the user and the MTA refused it. In either case, the bounce message (fake DSN) should have contained a message body like Mail to user(a)example.com failed at outgoing SMTP with the actual user's address. These fake DSNs are sent in the case where the outgoing MTA refuses a message from Mailman so there is no actual failure DSN. -- 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: EMWD Mailing Lists Down

by Mark Sapiro

On 1/15/22 5:49 PM, Sherry Xie wrote: > Hi all, > > I am an EMWD Mailman 3 customer, and I recently realized my mailing lists > are no longer working (the last email that went through was sent on > December 25, 2021). Emails I send to the lists do not show up in archives > or reach subscribers. It seems like others have had this issue before > since ownership of the company was transferred following Brian Carpenter's > passing – has anyone been able to get in touch with support or get their > issues resolved? > > I've submitted a support ticket but have no idea if this is being > monitored. I also have no way to contact the current management team, as > only their names were announced in the November 5, 2021 email from Barbara > Carpenter. Any help would be greatly appreciated – thanks in advance! There is a recent thread on this started at https://mail.python.org/archives/list/mailman-users@python.org/thread/N7NJL… and continued at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You might find something helpful there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: MM3+Python3.11

by Mark Sapiro

On 3/6/23 03:38, Odhiambo Washington wrote: > Has MM3 been tested with Python3.11? Yes, but not with uWSGI which is not part of Mailman per se. > I updated a Debian VM to Python3.11, installed MM3 and migrated the > configs. However, I am unable to get past the following error: > ... > Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/wsgi.py", line > 10, in <module> > from django.core.wsgi import get_wsgi_application > File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", > line 1, in <module> > from django.utils.version import get_version > File > "/opt/mailman/venv/lib/python3.11/site-packages/django/utils/version.py", > line 1, in <module> > import datetime > File "/usr/lib/python3.11/datetime.py", line 12, in <module> > import math as _math > ModuleNotFoundError: No module named 'math' > unable to load app 0 (mountpoint='') (callable not found or import error) This error says /usr/lib/python3.11/datetime.py can't import math. math is part of the python 3.11 standard library <https://docs.python.org/3/library/math.html>. There is something wrong with your Python 3.11 installation. -- 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: OS upgrade - anything to take care of?

by Mark Sapiro

On 5/13/21 1:58 PM, Ruth Ivimey-Cook wrote: > > Sadly they aren't - they link to python3.6 or whatever... and even if > not, the /lib/ naming gets you as well. > > And even if that can be worked around (eg by renaming the mailman > /lib/python3.6 folder to /lib/python3.8), the python .pyc files are > /also/ versioned, so you then have to find & delete them all to force > the new interpreter to rebuild them or python falls down in a heap. Maybe I'm missing something, but it seems to me that if /usr/lib/python3.6 and /user/bin/python3.6 are gone, just creating symlinks from /usr/lib/python3.6 and /user/bin/python3.6 to the corresponding python3.8 directories would work. The .pyc files in __pycache__ should not be an issue. They are versioned and placed in a __pycache__ directory specifically so multiple python versions can coexist. See <https://www.python.org/dev/peps/pep-3147/>. Python3.8 will just make new ones. If there is some issue with this, one can always do ``` find /path/to/venv -name '*.pyc' -delete ``` -- 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

[MM3-users] Re: Problem with digests not being sent daily

by Mark Sapiro

On 6/22/24 20:04, Mark wrote: > > Oh? I was indeed assuming that 0 meant unlimited. The threshold was set > at 0. > > My thinking was that meant the file size was not a factor in > determining when the digest was sent and that the sending would be > triggered by the daily cron. If Send Digest Periodically is Yes, digests will be sent by the daily (or whatever schedule) cron. If a digest reaches threshold in between runnings of the cron, one will be sent at that time. > When I set the threshold very low - 10kB - it sends a digest on every post. This is expected and the same should occur if the threshold is 0. > So my understanding of what you are saying is: if the threshold is set > very large, say 100,000 kB - then a digest will be be sent by the daily > cron even if it is smaller than 100,000 kB. Correct. If Send Digest Periodically is Yes, any accumulated digest will be sent when `mailman digests --periodic` runs, regardless of size. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 4:24 PM, Seth Seeger wrote: > > Ah hah! Right you are. I removed the offending fancy apostrophe. What about that traceback pointed to the template? (Is it something I could have figured out?) The key is this entry in the traceback. > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), This says we are trying to make a MIME text message part based on expanding the substitutions in a template. A look at the source at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/hold.py… says the template is list:admin:action:post. > Is it possible to filter out UTF-8 chars from the templates when they are saved in Postorius? Not really. Postorius would have to know the character set of the list's preferred_language in order to filter anything from the template that wasn't a valid character in that character set, and I don't think it has a way to get that information from Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: MM2 -> MM3 Migration

by Mark Sapiro

On 12/29/22 05:25, Odhiambo Washington wrote: > I looked at my list archives and saw that the latest post was on Dec 8, > 2022. > Then, because I wanted to import any posts that happened from 8th to now(), > I looked at two posts: > 1. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > This talks about 'hyperkitty_import *--since=01.01.2022* -l mylist@mydomain > my-mbox-file' > > 2. https://mail.python.org/pipermail/mailman-users/2018-July/083607.html > Which talks about 'hyperkitty_import *--since='1990-01-01'* -l > mylist@mydomain my-mbox-file' The default without the since= option is to import only those messages from the mbox which are newer than the newest message in the existing archive which is exactly what you want. > I am concerned about the implication of the date format here, especially > because our species from America write their dates differently than the > British, even though > the British colonized us all :P hyperkitty_import uses python-dateutil <https://dateutil.readthedocs.io/en/stable/> to parse the since date. See <https://dateutil.readthedocs.io/en/stable/parser.html> for info on formats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Add member to a list by email

by Mark Sapiro

On 11/12/24 02:00, via Mailman-users wrote: > Hello, > > I'm trying to add members by email with the following content. > > Recipient: testlist-request(a)xxxxxxxx.de > Email content: join address=max.mustermann(a)xxxxxxxx.de > > After I've sent this email, it still has to be confirmed in the Postorius web interface under member requests. How can I confirm membership by email, or deactivate this confirmation for moderators? You can use the email `confirm` command to confirm the request, but you need the token associated with the request to confirm it, and there is no good way to find it as it is not in the confirmation request notice sent to the list admins. To not require moderator confirmation at all, you can set the list's subscription policy. Normally, subscriptions should require confirmation by the user, a list admin or both. You can set it to require neither, but this is normally a bad idea if list addresses are accessible from outside your local network as it allows anyone to subscribe anyone else by spoofing their address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

[MM3-users] Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/2/22 12:04 PM, Andy Smith wrote: > > For ~6k messages it still took approx 16 hours to run that monthly > job, and during that time spewed out thousands of these errors: > > Failed to remove document 'hyperkitty.email.29351' from Whoosh: > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove > self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query > w = self.writer() > File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer > return SegmentWriter(self, **kwargs) > File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ > raise LockError > whoosh.index.LockError > > …so I'm not even sure if it worked. I think the warnings come from the hourly update_index job which can't obtain a lock on the index because the update_and_clean_index job already has it locked. Once the update_and_clean_index job finishes the update_index job should run and do the right thing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Owner's or Moderator's Lists

by Mark Sapiro

On 7/31/20 11:09 AM, Johnny Cison wrote: > > It's 1.1.2, which is the python3-django-postorius version included with the > package manager on Ubuntu 18.04. > > Is there by chance a mechanism for viewing that information in 1.1.2? You have several choices. 1) Do nothing and wait for Debian/Ubuntu to upgrade the package and backport it. 2) Try upgrading Postorius from source or with pip. This will probably result in disaster, and even if it doesn't, will probably also require upgrading django-mailman3, mailmanclient and mailman core to support new features in Postorius. 3) See the merge requests at <https://gitlab.com/mailman/postorius/-/merge_requests/349>, and if you have >50 lists, <https://gitlab.com/mailman/postorius/-/merge_requests/437> and try patching installing those changes as patches. Note that!349 patches 15 files, but one of them is the change log and 12 are related to tests. The only ones you need to patch are postorius/templates/postorius/index.html and postorius/views/list.py. Likewise, these two are all you need from !437. 4) Abandon the Debian/Ubunto package and install the whole suite from source or with pip. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Question about adding addresses using the REST API

by Mark Sapiro

On 1/15/22 10:03 AM, Stephen Daniel wrote: > > The only way I've found to create a standalone address (not linked to any > user) is to create a user with that address, unlink the address, then > delete the user. > > Is there a more straightforward way to just create an address with no user? The more straightforward way is via the IUserManager create_address method. This method is not exposed directly in REST, so you can't do it via REST. My question is why do you want to? Granted when an unknown nonmember address posts to a list we create a standalone address record, but maybe we should be creating a user too. We don't because it's tricky. Suppose User A with address A posts to a list from nonmember address B. We create the standalone address B record as a nonmember, but now user A can add address B as another address. If we also created User B, this would not be possible. But again, what is your use case for creating standalone addresses? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: How to fix lists with characters errors?

by Mark Sapiro

On 3/22/24 05:37, Helio Loureiro wrote: > Hi, > > I just found several lists have the issue like this regarding charset: > > (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members ... > Traceback (most recent call last): ... > line 109, in display_members > print(f'{address.display_name} <{address.original_email}>', > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > position 9: ordinal not in range(256) There is something in your python that has set the encoding for stdout to latin1 instead of the default utf-8. E.g. ``` $ python3.10 Python 3.10.9 (main, Dec 11 2022, 12:59:24) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> name = 'abc\u0142def' >>> print (f'{name}') abcłdef >>> import sys >>> sys.stdout.reconfigure(encoding='latin1') >>> print (f'{name}') Traceback (most recent call last): File "<stdin>", line 1, in <module> UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in position 3: ordinal not in range(256) >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Upgrade to 3.3.2 fails

by Mark Sapiro

On 12/27/20 12:12 AM, Torge Riedel wrote: > > Nice to hear, but I fear you could be hit by this issues again, > depending on changes in the future on the table. Either when more > columns are added or on runtime when rows are added / updated. It seems that is a possibility with MySQL. It may not be an issue with MariaDB. It isn't completely clear to me from <https://mariadb.com/kb/en/innodb-limitations/#limitations-on-size>, but it seems that VARBINARY, VARCHAR, BLOB and TEXT columns are only counted as a few bytes in the "roughly half the page size" calculation. > @Mark: Would it be a good approach to split the table 'mailinglist'? I > see some groups of columns like "bounce_*" or "dmarc_*" which could be > managed in separate tables. Currently, those list attributes which are stored in tables separate from the mailinglist table are (some of) those that have lists of values rather than a simple value, but it would certainly be possible to separate groups of related attributes into separate tables. Care to submit a merge request? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Mark Sapiro

On 4/25/24 04:35, Thomas Stein wrote: > > Traceback (most recent call last): > File "/usr/bin/django-admin", line 33, in <module> > sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', > 'django-admin')()) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 442, in execute_from_command_line > utility.execute() > File > "/usr/lib/python3/dist-packages/django/core/management/__init__.py", > line 416, in execute > django.setup() > File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in > setup > apps.populate(settings.INSTALLED_APPS) > File "/usr/lib/python3/dist-packages/django/apps/registry.py", line > 124, in populate > app_config.ready() > File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line > 15, in ready > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE This is a packaging issue in the Debian/Ubuntu package and should be reported to Debian. See the BREAKING CHANGE item in the 1.3.10 section at <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst>. You need to add `allauth.account.middleware.AccountMiddleware` to the MIDDLEWARE setting in your Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Mark Sapiro

On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > Is nntp common enough these days to be a useful default runner? > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > resources (yet another Python interpreter running) for a fairly edge > case of mailing list <--> nntp transits. You raise an interesting point. By default, the runner runs, but if there are no lists gating to usenet, its queue is always empty and it mostly sleeps between waking, finding its queue empty and going back to sleep. A more significant use of resources is every (default) 5 minutes spawning `mailman gatenews` which goes through a startup process and then looks at every list figuring out there's nothing to do. We could default mailman.cfg to contain `start: no` in the runner.nntp section so people would need to enable it if they wanted it. What do others think? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

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

by Mark Sapiro

On 4/9/19 11:16 AM, kelly.close(a)lrewater.com wrote: > I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database. > > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… Thank you for this. I'm sure it will be helpful. One caveat. The Mailman 3 package for Ubuntu 18.04 is core version 3.1.1. This version when used with the MySQL back end database can have a serious issue. It doesn't affect the PostgreSQL back end database, only MySQL and maybe MariaDB, and it is fixed in Mailan core 3.2.0. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for more info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Can't open PID file after start.

by Mark Sapiro

On 4/21/20 10:16 PM, Torge Riedel wrote: > Hi, > > today there were some package upgrades on my server for python3. Just to > be safe I did a "systemctl restart mailman" afterwards. Calling > "systemctl status mailman" gave me the following output: > ... > Apr 22 07:01:28 basis2 systemd[1]: Starting GNU Mailing List Manager... > Apr 22 07:01:29 basis2 mailman.sh[24180]: Starting Mailman's master runner > Apr 22 07:01:29 basis2 systemd[1]: mailman.service: Can't open PID file > /opt/mailman/var/master.pid (yet?) after start: No such file or directory > Apr 22 07:01:30 basis2 systemd[1]: Started GNU Mailing List Manager. > > Should I treat the PID message as an info or is it an error and > something is now broken? The file is there (content is 24182) and > timestamp is from the time where I restarted mailman. It's normal and just info. The key is "yet?" The [Service] section in Mailman's systemd service file references /opt/mailman/var/master.pid as PIDFile and systemd looks for it before Mailman has created it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 10:49 AM, Mark Dadgar wrote: > > Here’s what I get when I attempt the above commands: > > root@mail:/usr/lib/mailman3/bin# sudo -u list django-admin shell > Python 3.8.2 (default, Apr 27 2020, 15:53:34) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import Email > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 60, in _setup > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. The `django-admin` command that is being run doesn't itself point to your settings. In my case, I run django-admin via a wrapper that contains ``` #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ ``` The critical things are the exports of PYTHONPATH and DJANGO_SETTINGS_MODULE. The former is the path to where your settings module lives and the latter is its name without the .py extension. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: aborted connection

by Mark Sapiro

On 2/19/22 14:14, Sandor Dibuz wrote: > > It's the mailman quarterly cron job: > > # Every 15 minutes, gate messages from usenet to those lists which have > the gateway configured > */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman > gatenews; fi > > And I have no gateway enabled for any of them. Will have to find out > what mailman exactly does. And change MariaDB to verbose logging. First, If your Mailman core version is >= 3.3.5, you shouldn't be running gatenews via cron. Mailman's nntp runner runs it. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… But, that probably isn't it because in Mailman >= 3.3.5, running gatenews via cron should produce this error The gatenews command is run periodically by the nntp runner. If you are running it via cron, you should remove it from the crontab. If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the environment. However, since you have no lists using a news->mail gateway, you don't need to run gatenews at all so just remove it from the crontab. -- 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: How to let mailman log every single email that it sends out?

by Mark Sapiro

On 9/9/23 09:13, Mohsen Masoudfar wrote: > Thank you, Mark, but Sorry, I don't see them there. > I read that the mta log level should be set to debug in order to see them. > When I send an email to a list with +3000 subscribers and need to see in the log email has been sent to each of those email addresses If you want to see individual recipient emails in /var/log/mail.log, the best way is to enable VERP in mailman. I.e., set ``` verp_delivery_interval: 1 ``` in the [mta] section of mailman.cfg. Then you should see entries like: > Sep 9 16:14:31 mail postfix/qmgr[1158516]: 7561EFC0A5: from=<mailman-users-bounces+mmasoudf=aaas.org(a)mailman3.org>, size=1276, nrcpt=1 (queue active) > Sep 9 16:14:33 mail postfix/smtp[1831181]: 7561EFC0A5: to=<mmasoudf(a)aaas.org>, relay=aaas-org.mail.protection.outlook.com[104.47.59.138]:25, delay=1.6, delays=0.01/0/0.35/1.2, dsn=2.6.0, status=sent (250 2.6.0 <169427602883.1158168.2180174954874478353(a)mail.mailman3.org> [InternalId=4823248279498, Hostname=IA1PR20MB6503.namprd20.prod.outlook.com] 10538 bytes in 0.177, 58.037 KB/sec Queued mail for delivery) in /var/log/mail.log for each recipient. -- 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: mail loops back to myself

by Mark Sapiro

On 6/9/25 05:06, Florian Sukup wrote: > > The setup has historic reasons. However I can eliminate reverse.rrr.com > completely and replace it by host.xxx.com. Right now reverse.rrr.com has > an A-record pointing to the host's ip address. Eliminating reverse.rrr.com completely and replacing it by host.xxx.com would be good. This will help. Also if I look up the A record for reverse.rrr.com either locally or at aaron.ns.cloudflare.com there isn't one. This will be moot if you replace reverse.rrr.com with host.xxx.com. >> What is the output from `postconf -n`? >> > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > append_dot_mydomain = no > biff = no > compatibility_level = 2 > inet_interfaces = all > inet_protocols = all > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/var/lib/mailman3/data/postfix_lmtp > mailbox_size_limit = 0 > message_size_limit = 0 > mydestination = localhost, localhost.localdomain, arvak This needs to include $myhostname Also, including reverse.rrr.com would help with your current setup, but instead you should just eliminate reverse.rrr.com completely and replace it by host.xxx.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Mark Sapiro

On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote: > Hi, > > I have installed mailman3 with postfix. The server is working fine. To > protect the IPs from blacklisting, I want to relay all emails from > postfix/mailman to external SMTP servers like O365, Gmail, or our exchange > server. I would not recommend using O365 or Gmail as outgoing MTAs. I don't really know about )365, but I don't think Gmail likes you to send mail via a gmail server if it is not From: (or maybe envelope from or both) a gmail or googlemail address. > Could you please confirm is this possible. And how to do its configuration. It is possible and there are two ways to do it. You can configure this in Postfix to relay all outgoing mail via some other server. You can configure it in Mailman by setting in the [mta] section of mailman.cfg smtp_host: smtp_port: and presumably for authentication smtp_user: smtp_pass: Also see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… and following for other relevant settings. -- 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: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 3:01 PM, maszap(a)tin.it wrote: > Thank you, > but using roundcube, i can send email to all domains. That doesn't mean Mailman can. > These are just the lines I added to /etc/postfix/main.cf > > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp You may need to add relay_domains = hash:/var/lib/mailman3/data/postfix_domains to your postfix main.cf. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> Look in Mailman's smtp.log. You are looking for messages like: <timestamp> (pid) <message-id > post to <list-id> from <poster> nnn bytes and <timestamp> (pid) <message-id > smtp to <list-id> for nn recips, completed in nn.nnn seconds If the 'nn recips' matches the expected number of list members, the message was delivered to the MTA for all the recipients. If it then wasn't delivered to some of them, that's an issue with the MTA. Check the MTA's 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, 3 months

[MM3-users] Re: Discard all mail with the subject "The resutls of your email commands"

by Mark Sapiro

On 9/25/20 1:16 AM, w.schoener(a)alp.dillingen.de wrote: > Hello, > I am using mailman 3.2.1 for several mailing lists. My colleagues want me to stop all mails with the subject "The results of your email commands". > I found some contributions here, but nowhere a solution for this question. > Does anybody has any suggestion? > Maybe I could try to handle this outside of mailman, but then I would have to pass this task on to someone I dont know .... :-( > Thanks for all hints. :-) Doing it in the MTA, even though you don't want to, may be best as, with postfix for example, you can do it with header_checks. To do it in Mailman 3, patch mailman/runners/command.py and comment out or remove the last line ``` reply.send(mlist) ``` Are you really sure you want to do this at all. It means for example that one can't get a response to a `help` or the new `who` command among others sent to the -request address. -- 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: using SSH/TLS with external MTA

by Mark Sapiro

On 7/28/24 09:54, Roland Giesler via Mailman-users wrote: > > These settings from the Django docs look like the ones in mailman.cfg. > Do I have to set them somewhere else too? Yes. The settings in mailman.cfg only affect mail from Mailman. For mail from Django, you have to set things like EMAIL_HOST = 'box2.gtahardware.co.za' EMAIL_PORT = 465 EMAIL_HOST_USER = 'roland(a)giesler.za.net' EMAIL_HOST_PASSWORD = '...' and possibly others as desired, See the links to the Django docs for these. > * |use_tls|:|EMAIL_USE_TLS| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T…> > * |use_ssl|:|EMAIL_USE_SSL| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S…> > * |timeout|:|EMAIL_TIMEOUT| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO…> > * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K…> > * |ssl_certfile|:|EMAIL_SSL_CERTFILE| > > <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C…> This all goes in your Django settings which from other posts I gather is /etc/mailman3/mailman3-web.py. I'm guessing you are using the Debian packages and that's where the package puts the Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Can't deliver mails in queue

by Mark Sapiro

On 5/20/21 4:01 AM, Nathanael Schneider wrote: > > It would have been nice though to have a more refined error to figure > this out. But its solved now and hopefully this will help someone else > as well. I'm glad you resolved it, and I'm sorry I didn't consider the template issue myself. You actually had two separate template issues. If you created templates in Postorius, they were inaccessible because of the POSTORIUS_TEMPLATE_BASE_URL issue, but your initial problem with imported lists is different. It probably resulted from running the `mailman import21` command as root which you should never do. You should always run `mailman` commands as the Mailman user. This is mentioned at https://docs.mailman3.org/en/latest/migration.html#id1 The `mailman import21` command can create list specific templates in Mailman's var/templates/lists/LIST_ID/LC/ directory and if run as root these will be user:group root:root and not world readable and therefore can't be read by Mailman. Also, deleting and recreating the list with the same LIST_ID doesn't remove those templates, so the list still doesn't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Question to add "alias" address in list by group

by Mark Sapiro

On 4/28/22 08:43, Pierre Malard via Mailman-users wrote: > > These are authorized alternate email addresses. For example A@domain is subscribed to the Z list of which only members can contribute but we also want to authorize some other address of A (A@domain2, …) as an « alternative" email contributor. > In the Mailman2 version this was called "accept_these_nonmembers" and it actually got added to that "non-members" list in mailman3. There is still an accept_these_nonmembers list in MM 3, but it is intended to support only regexps. For individual addresses, the preferred method is to create a nonmember record and set it's moderation action to default processing. The current import21 will import *_these_nonmembers in this way. I.e., import regexps into *_these_nonmembers and create nonmembers with appropriate moderation action for non-regexp addresses. However, the better method for your use case is for A@domain to add A@domain2, … as additional addresses. This can be done by the user via the web UI or via REST https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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: About the link destination of the logo image of the homepage

by Mark Sapiro

On 09/29/2018 09:06 AM, Ooyama Yosiyuki wrote: > At next page: > https://www.gnu.org/software/mailman/ > > Despite the fact that "Mailman" is written in the logo on the upper left of the screen, > However if I click the logo image on the upper left of the screen,then it is to move to https://www.gnu.org/software/ > > I think it is strange. Yes it is strange, but it is an artifact of the fact that the same page is used at all of <http://www.list.org/>, <https://www.gnu.org/software/mailman/>, <http://www.list.org/>, <http://mailman.sourceforge.net/> and <http://mirror.list.org/>, and only the www.gnu.org site has extra pieces in the path to the home page. However, it can be fixed and I've done so. Thanks for the report. > In the Wikipedia English version, the following address is introduced as mailman's website. > www.gnu.org/software/mailman/ It probably should be <http://www.list.org/>, but that's up to wikipedia. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Where to find disabled members?

by Mark Sapiro

On 11/4/24 19:28, Bill Oliver wrote: > > a) See who is disabled, and > b) un-disable them by hand > > or... do I just have to wait seven days for them to automatically get > un-disabled? They do not get automatically re-enabled ever the user or you has to manually re-enable delivery. For an individual user, in Postorius you can click the user in the members list and see their delivery status and reset it. To deal with the whole list membership for a list, you can do ``` $ shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` If you just want to list them ``` >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member) ... >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: disabled users

by Mark Sapiro

On 10/25/23 11:58 PM, Servizio Informatico U.I.C.I. Sezione territoriale di Brescia wrote: > Hello, > > Thank you for your answers. The problem is: > > I have a lot of user disabled for too many bounces. These users have the > same provider that, probably, has some limits of number of mail that can > be delivered from the same server. This causes timeout connections and, > mailman creates correctly a bounce. Timeouts and other types of throttling should be retried and not result in a permanent failure until the retries fail for days. > So I would like to discover a way to reset bounce limits so they can be > re enabled to receive. I tried also to unsubscribe and resubscribe users > but it does not change anything. Unsubscribing and resubscribing a user creates a new subscription with delivery enabled and bounce score of zero, but this is not necessary. As Steve pointed out in the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… you can re-enable delivery for a user by clicking the address in the membership list and then setting Delivery status to enabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/30/24 17:54, Mark wrote: > > In the new installation, are the template.uri (in the mailman DB) > records written as http://localhost:8000/... ? No. In both the installation that worked and the one that didn't, they were https://msapiro.net/..., but I don't think it would have mattered. When I reinstalled, I kept the same database, I only rebuilt the venv. As I have said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, this is all strange. My logs from the failure show the web server getting the request and serving the template with a 200 status and then after 5 seconds which is the specified timeout a requests.exceptions.ReadTimeout error is logged in mailman.log. The exact same code is executed whether by a rest runner gunicorn worker or via some other Mailman core runner, but only the rest runner fails. Further, a reinstalled venv on the failing server has no error, and another server which has a venv identical to the failing one except for Python micro version also has no error. I can't begin to understand what the underlying cause might be. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

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

by Mark Sapiro

On 2/12/25 09:24, Christian via Mailman-users wrote: > Running Debian 4.19.316-1 > Python 3.7.3 > > I am unable to start mailman core > > > mailman@lists:~$ /opt/mailman/mm/bin/mailman start > Usage: mailman start [OPTIONS] > Try 'mailman start -h' for help. > > Error: A previous run of GNU Mailman did not exit cleanly (stale_lock). Try > using --force > mailman@lists:~$ > > > I try using --force and it did not work. So how do I start it? In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are: ``` master.lck master.lck|<host_name>|<pid>|<random_integer> ``` First verify that pid is not running or if it is, that it's not Mailman's `master` process. Then remove all the files from the var/locks/ directory and Mailman should start. > Bottom line: I would like for Mailman core to start when I reboot the > server. How can this be achieved please? See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/6/25 14:40, via Mailman-users wrote: >> Is your login a member of the list? > > It's supposed to be – when I click „Manage subscription” in the very same thread, it reveals that I'm subscribed. This is why I can't subscribe again. Yet I still can't post from HyperKitty, however I can by e-mail. > > However, when I checked the member list, I also found my address as a „nonmember” (besides being listed as „member” too). I removed myself as „nonmember”, but I still can't post to the list from HyperKitty. What response do you get when you click `reply` on a message? and what when you click `Start a new thread`. Do you get an error immediately or do you get a composition dialog and only get an error when you click `Send`. What do the errors look like? What do you see in Django's logs when you do this? What HyperKitty version is this and is it installed from PyPI or is it a downstream package? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: migration from 2.1 - owners and moderators

by Mark Sapiro

On 10/23/20 5:31 PM, Alex Schuilenburg via Mailman-users wrote: > > Most of the lists migrated so far don't have moderators, just owners. > However, when these lists have messages requiring moderation, the owners > dont get notified of held messages - unlike 2.1 where they did. Is this > a change or is there something I am missing in the configuration? As Brian said, owners as well as moderators should be notified. These notices are sent immediately if admin_immed_notify is True. If not, only periodic notices are sent. This needs to be run by cron. > I have the minute/quarterly/hourly etc cron jobs running, although I > have had to tune down the frequency of minute to hourly as it takes 6.5 > minutes to run* - but I doubt this is the cause. Those are Django tasks and don't affect this. You also need to run `mailman digests --periodic` to send periodic digests (see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>) and `mailman notify` to send periodic moderator notices (see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Postorius & multi domain

by Mark Sapiro

On 4/22/20 8:14 AM, Gelpi Andrea wrote: > > I search internet for a while and I discovered that using > FILTER_VHOST = True > seems to solve the problem. > >>From posotrius config page: > > FILTER_VHOST > Filter the list of available lists in Postorius and Hyperkitty > depending on the domain they are being currently served from. Mailman 3 > supports multiple domains in a single installation. > > But it doesn't work. I got err 500 form apache. FILTER_VHOST is currently broken unless each domain has the same value for the web and email domains. See the thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > Were can I find an explanation or a how to configure the system to have > 2 webserver with different domains working on the some server as it was > with mailman 2? If each domain has the same value for the web and email hosts, FILTER_VHOST will work. Currently though if you have domains like web host = lists.example.com and email host = example.com, FILTER_VHOST is broken. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: PSA: Avoiding spam-scanning outgoing mailman3 mail

by Mark Sapiro

On 5/8/20 2:11 PM, Mark Dadgar wrote: > > The easy fix was to edit the [mta] setting in mailman.cfg to deliver email via the submit port instead, which has no filtering applied to it: > > smtp_host: localhost > # using the submit port bypasses spamassassin filtering on outgoing list email > smtp_port: 587 > smtp_user: mm3send <— I created this user for this purpose > smtp_pass: <password-for-mm3send-user> > > This works great and can be applied to any email filtering. We tend to do this differently. For example, on mail.python.org which currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends about 135,000 individual messages per day from the two Mailman instances, we define in /etc/postfix/master.cf 127.0.0.1:8026 inet n - - - - smtpd -o smtpd_authorized_xforward_hosts=127.0.0.0/8 -o mynetworks=127.0.0.0/8 -o smtpd_recipient_restrictions=permit_mynetworks,reject -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_data_restrictions= -o receive_override_options=no_unknown_recipient_checks -o smtpd_milters=inet:127.0.0.1:8891 Then port 8026 only accepts locally generated mail and only does dkim signing (milter on port 8891) and essentially no other checks. Then in the [mta] section in mailman.cfg we only need smtp_port: 8026 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Database Schema - v3.2.1 to v3.3.3

by Mark Sapiro

On 4/4/23 21:28, Dave Hall via Mailman-users wrote: > Hello. > > Have 4 Debian servers running Mailman3 v3.2.1 and sharing the same external > MySql databases for Mailman3 and Mailman3-web. I am in the process of > migrating to v3.3.3. It would be easiest to perform this upgrade one > server at a time, but this would mean that for a short time I would have > v3.2.1 and v3.3.3 using the same databases. > > I am wondering if there are any MySql schema differences between the two > versions. If there are, having the two different versions 'cohabitating' > won't work.. As far as the Mailman3 database is concerned there are at least 3 migrations between 3.2.1 and 3.3.3 in mailman/database/alembic/versions. Namely: 2d2d0ef0828f_add_tag_column.py, 83339e4039da_add_usenet_watermark.py and d151c0b8d6f7_bounce_parameters.py. As far as Mailman3-web is concerned, this is presumably a Debian/Ubuntu Mailman3-web package upgrade. There may be migrations in django_mailman3/migrations/, hyperkitty/migrations/ and postorius/migrations/ that affect this depending on what the specific version updates are in that upgrade. In any case, there are schema differences for Mailman core between 3.2.1 and 3.3.3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Hyperkitty on Debian 12

by Mark Sapiro

On 3/26/24 00:06, Markus Grandpré wrote: > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... This warning is harmless, but to eliminate it set ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in your django settings. > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available Probably Debian creates the `list` user without a login shell. ``` sudo -i -u list ``` may work. If not, you can always prefix commands with `sudo -u list ` as in ``` sudo -u list mailman-web hyperkitty_import \ -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ /var/mailman21/testlist.mbox ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 9/11/24 15:21, Dan Caballero wrote: > Mark, > > Do you have any tips for scripting the setting changes via mailman shell -l somelist(a)caltech.edu or a python script to run. eg. mailman shell -r dmarcsettings.py? > > We have a number of lists that email Gmail addresses either directly or via aliases and virtual email domains using Google Workspace. If your Mailman version is >=3.3.9 you can add `^.*(a)gmail\.com` to each list's `dmarc_addresses` to apply `dmarc_mitigate_action` to any mail From: a `(a)gmail.com` address. A `mailman shell` interaction to do that and set `dmarc_mitigate_action` to munge_from for all lists is like ``` $ /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager): ... mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') ... mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from ... >>> commit() ``` If your Mailman is older than 3.3.9 or you don't want to use dmarc_addresses, replace the line ``` ... m mlist.dmarc_addresses.append(r'^.*(a)gmail\.com') with ... mlist.dmarc_mitigate_unconditionally = 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, 1 month

[MM3-users] Re: Mailmansuite.log Entries

by Mark Sapiro

On 12/1/20 5:16 PM, Brian Carpenter wrote: > I see the following log entries in mailmansuite.log: > > INFO 2020-11-28 00:00:52,242 29142 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-28 00:01:00,600 29142 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-11-29 00:00:52,135 15513 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-29 00:01:00,192 15513 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-11-30 00:00:52,484 22622 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-11-30 00:01:00,758 22622 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > INFO 2020-12-01 00:00:50,246 11946 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 1000 > INFO 2020-12-01 00:00:59,688 11946 hyperkitty.lib.mailman 2117 emails > left to refresh, checked 2000 > > I assume this is a result of importing archives from a MM2 mbox file. > This happen months ago however. Why are these entries still showing up? Those come from the HyperKitty sync_mailman job which is run by hyperkitty_import if you don't specify --no-sync-mailman, but is also one of the Django daily jobs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: postfix malformed address with confirm replies

by Mark Sapiro

On 2/28/21 1:07 PM, Stephen Mats Mats wrote: > > > To be clear the 'obstructive server’ is mailman-core. :) > > [ec2-user@ip-172-31-18-xxx ~]$ telnet 172.19.199.2 8024 > Trying 172.19.199.2... > Connected to 172.19.199.2. > Escape character is '^]'. > 220 mailman-core GNU Mailman LMTP runner 2.0 > LHLO ip-172-31-18-xxx.us-west-2.compute.internal > 250-mailman-core > 250-SIZE 33554432 > 250-8BITMIME > 250 HELP > MAIL FROM:<stephen.s.w.matsmats(a)gmail.com> > 250 OK > RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55856(a)mm3.aca-aws.s.uw.edu> > 553 5.1.3 Error: malformed address > RCPT TO:<matsmats-mm3-test1-confirm+d6f77a2572ef55a8b2c4ca0d77de8493fbb55(a)mm3.aca-aws.s.uw.edu> > 250 OK > quit > 221 Bye Thanks for the info. I'll investigate further. It looks as though the LMTP runner (server actually) is responding with the 553 and then the sending MTA is retrying with a truncated local part, but of course that doesn't work because the token won't be found. I will look at trying to convince Mailman's LMTP to accept the longer local part or barring that to get the confirm command to accept the truncated token. -- 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: where do I find the text of a bounce email ?

by Mark Sapiro

On 3/9/21 1:59 AM, Per Jessen wrote: > All, > > I am trying to figure why a particular outbound message was bounced, so > I'm looking for the text of the NDR that was sent - where do I find > that ? Mailman 2.1 would include the NDR in the notice to the admins when delivery was disabled or bounce score's incremented if those notices were requested. Mailman 3 has no such capability. If you have access to the server, this patch ``` > diff --git a/src/mailman/runners/lmtp.py b/src/mailman/runners/lmtp.py > index 6a0bdcf5e..eca474089 100644 > --- a/src/mailman/runners/lmtp.py > +++ b/src/mailman/runners/lmtp.py > @@ -217,6 +217,8 @@ class LMTPHandler: > slog.debug('%s subaddress: %s, queue: %s', > message_id, canonical_subaddress, queue) > status.append('250 Ok') > + if queue == 'bounces': > + config.switchboards['bad'].enqueue(msg, msgdata) > except Exception: > slog.exception('Queue detection: %s', msg['message-id']) > config.db.abort() ``` will add all received bounces as queue files to var/queue/bad/ where they can be examined with `mailman qfile`. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/10/24 1:55 PM, jkoral(a)luc.edu wrote: > The old server is trying to send, but I end up getting an undeliverable message saying no connection could be made. I know port 25 is open because I can telnet to it. I'm wondering if I'm missing something in my configuration. Can you take a look? Thank you. > > Here are the active settings in /etc/postfix/master.cf: ... > smtp inet n - y - - smtpd This says port 25 is for smtpd and that's good. > And here are the setting I have in /etc/mailman3/mailman.cfg > # /etc/mailman3/mailman.cfg This is irrelevant as the message never gets to Mailman. On 10/10/24 1:58 PM, jkoral(a)luc.edu wrote: > Here are the results from netstat: > > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3876896/master And Postfix master process is listening on port 25. You say you can telnet to port 25. Can you do that from the old MM 2.1 server? Can you connect and receive the greeting and send `EHLO hostname` and get a good response? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Default moderation for new members

by Mark Sapiro

On 11/14/19 7:37 AM, Seth Seeger wrote: > > I’m loving Mailman3 so far! Great work on it. Thank you. > I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. In Postorius set Settings -> Message Acceptance -> "Default action to take when a member posts to the list" to Hold for moderation. This is the action which will be taken for a post from a member whose individual Moderation is List Default as it is for all new members. Then when a post from that member is held, if you click the subject in the held messages view, a dialog opens showing the message content with Accept, Reject and Discard buttons and a dropdown list you can use to set that member's Moderation to Default processing. Default processing is generally what you want as it bypasses the moderation hold but still applies other tests such as header filters, administrivia, implicit-dest, max-recipients, max-size, etc. -- 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: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 10/22/21 8:51 AM, Marco Marinello wrote: > Hi everybody, > > as per subject, I'm getting this error in the hyperkitty log when mailman daemon tries to archive a mail. > I've setup the hyperkitty.cfg file with api_key = MAILMAN_ARCHIVER_KEY in settings_local.py but still nothing. > I've seen here and in GitLab issues some errors concerning a wrong api key but here it says that it wasn't sent at all. > All packages installed via pip install + latest .zip release, including mailman-hyperkitty. Currently running on apache with mod_wsgi_py3 without https. The following combinations should work: mailman-hyperkitty 1.2.0 with HyperKitty 1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty <1.3.5 The following will not work: mailman-hyperkitty 1.2.0 with HyperKitty <1.3.5 mailman-hyperkitty <1.2.0 with HyperKitty 1.3.5 Do you see a message like 'The MAILMAN_ARCHIVER_KEY is now required to be sent over the Authorization HTTP header, you need to upgrade the mailman-hyperkitty package to 1.2.0 or newer.' In your Django log and/or your mailman.log? These will only be logged with HyperKitty 1.3.5 and mailman-hyperkitty < 1.2.0 -- 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: Problems getting MM3 to work

by Mark Sapiro

On 4/24/23 4:53 PM, Mark London wrote: > > Mark - I encountered the same problem and it wasn't clear from the > documentation what to do about it. > > So I eventually changed the name from example.com using the /admin link. > > But if I now set SITE_ID = 0, and restart the server, it is not happy > and tells me it encountered an error. > > raise > self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: > Site matching query does not exist. I'm not sure about this. It may only work if there is more than one site. On the other hand, it requires that the requesting domain match a site. I.e., I think if the site's domain is example.com, but the request is from www.example.com, that could cause it to fail. Also, if proxying to a wsgi server, the web server has to pass the host. I.e., for nginx, proxy_set_header Host $host and for Apache ProxyPreserveHost On > I guess I should just let it be set to 1 and be done with it? - Mark Yes, I think so. -- 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: Congrats on the instructions for installation on ubuntu, what about migration?

by Mark Sapiro

On 10/8/24 5:45 PM, Bill Oliver wrote: > > Is there a tutorial/instructions on migrating data from an old system > to a new one? It's actually not the end of the world if I don't get > all the old emails transferred, but I'd like to get the email addresses > of the participants moved over easily... I believe that I set it up > in 2020, but did not do any version upgrades since then... There's no explicit doc, but there are some posts in the archives of this list, e.g. <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. The easiest scenario is if you want to migrate everything. You just dump the database on the old server and load it on the new one using the database manager's tools. If you only want to move some, but not all lists, it's more complicated, but possibly the easiest thing is to migrate everything and then delete the unwanted lists and their archives from Postorius and HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: confirm mail rejected

by Mark Sapiro

On 10/02/2017 05:21 AM, Marc Sluiter wrote: > > In the logs I see that postfix is trying both "liste-confirm+extension@domain" and "liste-confirm@domain" for another lookup map of type mysql (so "recipient_delimiter" is working), but not for the mailman map of type regexp. > Just a wild guess, I didn't find anything about it: can it be that “recipient_delimiter" doesn't work for “regexp" maps? I think so. See the note I just added at <https://gitlab.com/mailman/mailman/issues/401#note_42163915>. > For now I worked around this issue by manually modifying the confirm regex in "postfix_lmtp” to /^liste-confirm\+.*(a)domain\.tld$/ > > Does anyone have an idea why the regexp map isn’t working for me and at least 1 other user (see https://gitlab.com/mailman/mailman/issues/401)? > Would my workaround be a long term solution which could be implemented in mailman? That would mean that mailman could work independent of the “recipient_delimiter” setting (or do I oversee something?) I'll be working on a fix. My inclination is to change all the regexp -confirm and -bounces table entries from, e.g., /^list-bounces(a)example\.com$/ to /^list-bounces(+.*)?(a)example\.com$/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by Mark Sapiro

On 3/2/21 11:33 PM, David Partain via Mailman-users wrote: > > In this regard, I have three questions: > > 1. Am I correct in assuming that I can just use my favorite editor (vi) > to remove the offending characters from the file? No. The file is a Python pickle and you can't edit it. You would need to get the message and the metadata from the pickle (you could at least view it with the `mailman qfile` command), edit the message and then re-pickle the message and metadata. > 2. If I cannot find the offending character, is it safe to just remove > the file so that subsequent archiving can proceed? Yes. > 3. Can I do something to make hyperkitty go through the spool? I don't know what you mean. Every time there is a new post to any list, Mailman core invokes the mailman_hyperkitty process to archive the message and the forst thing that process does is attempt to reprocess all the messages in the spool which fails because of the utf8mb4 issue. -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/7/24 11:23, jkoral(a)luc.edu wrote: > HI Mark, I was off for a couple days. I have a feeling postfix is misconfigured because I see that port 25 is open. The server is not receiving mail at all. Are there any tips for things I can check. The logs are not showing much because the mail doesn't seem to reach it. According to Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test(a)listservnew.example.com>, orig_to=<olivertest(a)lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) The old server is attempting to send mail to the new server. Are there any `postfix/smtpd` messages in the mail.log on the new server. If so, they may help. If not, the port 25 connect is not reaching Postfix and the new server is disconnecting before connecting to Postfix. Is Postfix listening on port 25? Does `sudo netstat -lntp` show Postfix `master` process listening on port 25? If not check /etc/postfix/master.cf. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Broken paths

by Mark Sapiro

On 07/13/2016 12:30 PM, Jean-Luc Wasmer wrote: > > I followed the instructions on: https://gitlab.com/mailman/mailman-bundler/ > I didn't have Python 3.4 installed at all... had to install it to > complete Mailman's installation. So you should have two virtualenvs, a Python 2 virtualenv at /opt/mailman/mailman-bundler/venv and a Python 3 virtualenv at /opt/mailman/mailman-bundler/venv-3.4 (I'm pretty sure bundler won't install with Python 3.5). >>> - shell scripts expect bash to be at /bin/bash (mine is at >>> - /usr/local/bin/bash) >> >> Which shell scripts? Mailman itself doesn't ship any shell scripts, >> so again, >> I'm guessing you're talking about the ones in your vent? > > I'm referring to: > ./bin/mailman-post-update > ./bin/mailman-web-django-admin createsuperuser Those scripts are created by bundler you should be activating the Python 2 venv before running them. I.e., source ./venv/bin/activate I'm not sure this will help. It looks like bundler has #!/bin/bash hard-coded in the templates for these scripts. You might file an issue on this at <https://gitlab.com/mailman/mailman-bundler/issues>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: Mail going to Held Messaging even the moderation is set to Accept Immediately

by Mark Sapiro

On 7/21/20 8:09 AM, Shashikanth Komandoor wrote: > > As per my understanding on Mailman 3, if the moderation attribute is > set to "Accept immediately (bypass all other rules)" then without checking > any rules, it should be delivered to the recipients of the list > irrespective of the message or body of the message but is there any such > checking if the body content or subject or any thing else is checked even > if the moderation bit is set to "Accept immediately". Member moderation Accept Immediately does not bypass ALL rules. It only bypasses those rules after member-moderation. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin…>. However, I don't think that's the issue here. I think the issue is the poster is both an owner and a member. There is an issue in Postorius such that in cases like this, setting the member's moderation action actually sets that of the owner which has no effect on posting. See <https://gitlab.com/mailman/mailman/-/issues/659> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > very significant date for me (it is my wedding anniversary) and I'm 90% > sure that I dedicated time to Weblate after that date... With respect to Mailman core, all I'm doing is downloading the .po for Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po from the Mailman core 3.3.3 package on PyPI and they are identical. If there are translated strings on weblate that are different from that, they don't show up in the downloaded <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>. > All strings related to Mailman (core, django_mailman3, postorius and > hyperkitty) are translated into Spanish 100%, but the interfaces, after > updating to the latest releases, are still in Englanish (more English than > Spanish). > > This is not a fight, we want to help, but do not know how. And I too want to help. It would be a help to me if you can give me examples of specific strings whose weblate translation differs from what's in the distributed .po files. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Apache+mod_wsgi issue

by Mark Sapiro

On 12/26/22 11:08, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > El 26/12/22 a las 19:19, Mark Sapiro escribió: >> On 12/26/22 07:42, Odhiambo Washington wrote: >> >>> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> >>> >>> Does your https://site.name/user-profile/ work? >> >> Again, Guillermo is using uWSGI, not Apache mod_wsgi > > Well... now I am not sure, you know I've been confused before about that. I was looking at what you posted at https://forums.freebsd.org/threads/mailman-3.61050/#post-488128. I focused on the part beginning with - initiated the uwsgi with a /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & Which is running uwsgi. However I overlooked the mod_wsgi stuff. > In my httpd.conf I have: > > ############## > > LoadModule wsgi_module > "/usr/local/lib/python3.9/site-packages/mod_wsgi/server/mod_wsgi-py39.cpython-39.so" > WSGIPythonHome "/usr/local" > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 > user=mailman3 group=mailman > WSGIProcessGroup hyperkitty > ############### This is all mod_wsgi. > And in then end of my vhost definition file there is this line: > > Include "/usr/local/mailman3/apache24.uwsgi.conf" > > In that file I have: > > ######### begin of apache24.uwsgi.conf > > Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico > Alias /static /usr/local/mailman3/static > ######### > # for hyperkitty > Alias /static/admin /usr/local/mailman3/static/admin > Alias /static/CACHE /usr/local/mailman3/static/CACHE > Alias /static/django_extensions > /usr/local/mailman3/static/django_extensions > Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty > Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty > Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 > Alias /static/rest_framework /usr/local/mailman3/static/rest_framework > # for postorius > Alias /static/postorius /usr/local/mailman3/static/postorius > Alias /static/archives /usr/local/mailman3/static/postorius > ##### All the above between `#########` and `#####` is redundant as you already have Alias /static /usr/local/mailman3/static which will alias any /static/xxx to /usr/local/mailman3/static/xxx > ###ErrorLog /var/log/httpd/hyperkitty_error.log > ###CustomLog /var/log/httpd/hyperkitty_access.log combined > > <Directory "/usr/local/mailman3/static"> > Require all granted > </Directory> > #### esto va en el httpd.conf > ##WSGIDaemonProcess hyperkitty threads=25 > python-path=/usr/local/mailman3 user=mailman group=mailman > ## esta es la de Sapiro > #WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 > ####user=mailman group=mailman > ####python-path=/opt/mailman/mm/venv/lib/python3.6/site-packages:/opt/mailman/mm/venv/lib/python3.6 > ####python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > > #### agregado el 08/07/22 > WSGIPassAuthorization On > #### > > WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py > process-group=hyperkitty > WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py > process-group=hyperkitty And this is also mod_wsgi. ... > I don't want to put more noise in the list. But I'm confused because I > always updated via pip the apache mod_wsgi thinking is was needed for my > configuration. If it is not, I will stop updating it. Based on the above you ARE using Apache mod_wsgi and if you are still also running uwsgi as /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & that is unnecessary. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: manage.py runjobs hourly

by Mark Sapiro

On 6/11/20 11:04 AM, Mark Dadgar wrote: > I have started getting this emailed to root each hour from the cron job. > >> From: root(a)pdc-racing.net (Cron Daemon) >> Subject: Cron <www-data@mail> [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly >> Date: June 11, 2020 at 11:00:06 AM PDT >> To: www-data(a)pdc-racing.net >> >> 18:00:03 [Q] INFO Enqueued 1350 >> 18:00:03 [Q] INFO Enqueued 1351 > > The Enqueued numbers do increment. > > Anyone know what this is? The short answer is you fixed your HyperKitty indexing issue so the hyperkitty update_index job has work to do and some of those tasks get queued by Django Q. See <https://gitlab.com/mailman/hyperkitty/-/issues/295> for another discussion around this. Those messages depend on system load. Sometimes you'll see bunches of them and sometimes (at least on mail.python.org which is the most busy server I am involved with) you won't see any for up to a week or longer. Run django-admin qifno to get the current django q stats. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Missing mailman archives?

by Mark Sapiro

On 8/10/20 7:44 AM, Marco Marinello wrote: > I've recently migrated from Mailman 2 to Mailman 3 but I'm setting up Hyperkitty just now. I imported the old mbox and that worked fine but now I'm missing the mails in the time between Mailman 3 started working and now: mailman config reports > > [paths.custom] var_dir: /opt/mailman/var > > But > > root@mm:/opt/mailman/var# find . > . > [OMISS] > ./archives > > Where are the e-mails? Can I import them into Hyperkitty? If the prototype archiver was enabled for the list, the message should be in maildir format in /opt/mailman/var/archives/prototype/list(a)example.com/ If the prototype archiver was not enabled and the messages aren't there (which appears to be the case if I understand your `find`), they are only in the list member's mailboxes if they haven't been deleted. If you have the maildir messages, you can make a mbox containing the messages an import it into HyperKitty, but if there are newer message in Hyperkitty, you need to specify --since to hyperkitty_import to import messages older that the newest in the HyperKitty archive. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/21/20 3:01 PM, Mohsen Masoudfar wrote: > It seems something is fundamentally wrong with Hyperkitty: > >>From /var/log/mailman3/mailman.log > > --- > 49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 50 <h1>Authorization Required</h1></body></html> (401) > 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 52 <h1>Authorization Required</h1></body></html> (401) > 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > 54 <h1>Authorization Required</h1></body></html> (401) > 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> ... I doubt this has anything to do with the missing approved message, but what's in you mailman-hyperkitty.cfg file for api_key and does that match your settings_local.py setting for MAILMAN_ARCHIVER_KEY except for being quoted in settings_local.py and not in mailman-hyperkitty.cfg. -- 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: Cloned mailman3 from the gitlab site, having issues locating the mailman3 file to start it

by Mark Sapiro

On 5/20/24 1:08 PM, Keith Christian wrote: > Mark, > Good morning, > > If it matters, running Python3 3.6.8 on Red Hat Enterprise Linux > release 8.9 (Ootpa) > > [mailman3@wesnixtopmed mailman]$ mkdir > /home/mailman3/mailman/virtual_environment > [mailman3@wesnixtopmed mailman]$ python3 -m venv > /home/mailman3/mailman/virtual_environment > [mailman3@wesnixtopmed mailman]$ source > /home/mailman3/mailman/virtual_environment/bin/activate > (virtual_environment) [mailman3@wesnixtopmed mailman]$ pip install > /home/mailman3/mailman > > I tried to follow your instructions closely today, got these messages afterward: > > Directory '/home/mailman3/mailman' is not installable. File 'setup.py' > not found. > You are using pip version 9.0.3, however version 24.0 is available. > You should consider upgrading via the 'pip install --upgrade pip' command. Both pip and python are too old. Officially, current Mailman 3 requires Python 3 >= 3.9. It might work with older versions, but no guarantees. Also, 9.0.3 doesn't recognize pyproject.toml as replacing setup.py. It requires pip >= 10.0. see https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

Search results for query "sapiro"