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

[MM3-users] Re: Confirm on mass subscription

by Mark Sapiro

On 7/5/17 1:48 PM, David Krantz wrote: > > Is there a way of requiring all mass subscribed users to confirm their > email adress? I have an use case where we have a current mail list but > when moving it to mailman I for different reasons would like to > confirm all subscribers. Some very shallow testing suggests that if I > just add them using mass subscribe, they will not have to confirm at > all. > > I have yet to upgrade to 3.1 but I will do so in due time. In MM 2.1, you just send the users invitations rather than subscribing them. In MM3/Postorius, this does not seem to be an option at present. -- 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: Apache Conf

by Mark Sapiro

On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > Hi, > Currently, I use a nginx configuration for mailman. It's work perfectly. > > I tried to do the same with Apache, but the statics files are not > delivered (404). ... > <VirtualHost *:80> > ServerName mailing.ddd.fr > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > <Location /static/> > Alias "/opt/mailman/static/" > </Location> > > <Location /> > ProxyPass http://localhost:8000/ > ProxyPassReverse http://localhost:8000/ > ProxyPreserveHost On > </Location> > </VirtualHost>/ In Apache, location <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not appropriate for resources in the file system. Try Alias /static/ /opt/mailman/static/ not within a location block. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Gmail emails bouncing - anybody seen this problem?

by worik

Friends On a fresh install (docker) on a fresh VPS I am getting all Mailman messages to Gmail addresses bouncing telling me I am sending too many messages. Has anybody else have this problem? I am getting the following error in mail.log: "Our system has detected an unusual rate of 550-5.7.1 unsolicited mail originating from your IP address. To protect our 550-5.7.1 users from spam, mail sent from your IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" I have been to the URL mentioned and exhausted my options there. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 5 months

[MM3-users] Re: Trouble in Debian11 after import mailman2 archive

by Mark Sapiro

On 5/25/22 03:21, qro(a)xs4all.nl wrote: > > Question: > Where do I have to look/make changes so I can import the old archive and > can send email to it? You are not looking at the relevant logs. In the first case, mail is delivered to Mailman, but then something happens to it before it is archived and delivered. Look in /var/log/mailman3/mailman.log and wherever Mailman's qfiles are in the Debian install. Assuming the message is not held for moderation, rejected or discarded due to list settings, it is probably queued in Mailman's `shunt` queue, and if so, there will be an exception and traceback logged in mailman.log. -- 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: Retrieve users from a list

by Jered Floyd

Yow! Do you happen to have a recent database backup? (See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…) Every time I look at the UI and see "Remove ALL members" next to "Remove Selected", a chill runs down my spine. I should probably go hide that button with some custom CSS right now. You have my sympathy. --Jered ----- On Feb 6, 2024, at 9:40 AM, pau baiges pau.baiges(a)csuc.cat wrote: > A moderator has deleted all the users from a list, is there a way to recover > them? > _______________________________________________ > 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 jered(a)convivian.com

1 year, 5 months

[MM3-users] Where to find disabled members?

by Bill Oliver

Now that I have mailman running smoothly, I'm having to deal with a few other issues. When I changed vendors for my vps, my vendor gave me a static IP address that was apparently run by Satan himself. The ip address is -- or was -- on a number of blacklists. I have spent the past couple of weeks going through various appeals processes to get whitelisted, and I think I'm in good shape. In the meantime, a fair number of subscribers have been disabled. When I look at Postorius -> Settings -> Bounce processing, I see all of the policies I can play with, but I don't see how to 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? Thanks! billo

8 months, 4 weeks

[MM3-users] Re: Postorius no connection to REST API

by Abhilash Raj

Apologies for the top-post in advance. So, I am still catching up to this and I don’t very well understand apache2 config, so I’ll try to briefly describe what the setup should be and perhaps it can be translated into apache2 config. Since this thread is mostly about Web stuff, I am not going to talk about mail setup, but replacing `web server` with `mta` and appropriate port changes are the only major differences in mail setup. Postorius (using Django library/web framework) speaks WSGI and can be run using a WSGI Server. There are multiple options for choosing a WSGI server like uwsgi, gunicorn etc. There are also some common web server plugins like mod_wsgi, which are essentially WSGI servers implemented as Apache2 plugin. Web server reverse proxies the WSGI server which runs Postorius/Hyperkitty. You want WSGI Server to be configured to listen on either a socket or a port and then also configure web server to reverse proxy the socket or port. *Ideally* you want to terminate TLS/SSL at the web server level and proxy the HTTP request to the local WSGI server. You don’t need to do anything special for Mailman for SSL if you do this, just follow the regular Web server documentation for SSL for any domains you are supporting in Mailman. If you don’t want to terminate TLS at web server and instead want it down to the last step, WSGI server itself, then the setup is something we don’t have any docs for at the moment but if you go to the respective WSGI server’s docs, I think you’ll find some. uwsgi is a WSGI server implementation, but it is a lot more than that, resulting in a bit more complicated configuration and issues, even though it is stable. The documentation for it exists, but it can be hard to parse if you don’t know a lot about WSGI stuff. A few notable things about uWSGI that Mailman documentation uses are, (1) Ability to manage a daemon process like systemd and (2) ability to speak a new custom protocol called uWSGI with Web Server instead of HTTP that most other WSGI servers use to talk to Web Servers. (1): This is specified as a part of the the “attach-daemon” configuration in the uwsgi.ini file. For Mailman, we use # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster Which will essentially start `mailman-web qcluster` command which starts and a daemon and manage that daemon. Putting it in the uWSGI makes it easy to manage the lifecycle of this and the WSGI server together. If you were using something else like gunicorn, this would be a separate systemd service which you’d start/stop along with mailman-web. (2): This is *probably* what is causing the issue for you from what I can gather in this thread, but I am not sure. Web Server <—> uWSGI communication can be either HTTP or (named exactly same as the package name itself, which causes confusion I suppose) uWSGI protocol. Depending on how you configure uWSGI, you want to update your web server configuration to talk the same protocol. ``` uwsgi-socket = /run/mailman3-web/uwsgi.sock or uwsgi-socket = 0.0.0.0:8000 ``` is the config to talk uwsgi protocol and you want to configure Web server to Proxy using the same protocol. You can find that in the uwsgi docs here: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html You probably need an apache module to speak uwsgi, the docs should have the details. Notice the URL is uwsgi:// instead of http://. Other way is to configure uWSGI to speak HTTP, which can be done by replacing "uwsgi-socket" by "http-socket” in the uwsgi.ini configuration. This might be the easiest for you to try, do make sure to restart the mailman-web service after making the change in uwsgi.ini. Abhilash > On Aug 16, 2021, at 9:34 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Richard, > > Thanks for the details and the pointer to the full configs. That > makes it possible to take a look, but I can't spend much time on it > until next week. > > I'll see if I can prod Abhilash who is more expert than I on all this > stuff (I just use mod_wsgi), but there's some more urgent (sorry, but > it's security) stuff going on, and his absence speaks for his $DAYJOB, > I guess. > > Richard Rosner writes: >> That is entirely possible @Stephen. You can see the entire apache config a few posts back plus the additions from @Mark and mine from the last post. As I interpret it, apache is reverse proxying to the uwsgi app, now through http instead of the socket. But I have no idea if that's the right way round. I'm not sure is the config file templates for apache, nginx and uwsgi that you get with the Debian packages are added by the Debian team or if they are there any way and just have been modified to the Debian file layout, but I'd guess either way it's not that likely that they wrote it the wrong way around. But I'm not too experienced to be able to translate the nginx config to apache to see if that would result in something different. >> >> Also, while the nginx config is written as a standalone website, the apache config seems to have been written to just create a /mailman3 site under an existing website, while I use it as a standalone site. So it's entirely possible that I missed something when I modified the website from mailman2 to serve mailman3, but then it shouldn't have been able to show the website at the beginning. >> _______________________________________________ >> 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/ >> >> > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

3 years, 11 months

[MM3-users] Re: Message Sent to A Re-Created List Results In Error

by matthew＠alberti.us

I checked all over the mailman core logs and couldn't find a problem. But then I noticed that the 550 error was coming from dovecot-lmtp. I should rename this thread because the actual problem seems to be unrelated to re-created lists. It seems like the actual problem seems to occur in the following situation: * Using Postfix * Using Dovecot * /etc/postfix/virtual includes addresses with same domain as mailman lists. * An e-mail address subscribed to a mailman list is in the /etc/postfix/virtual file as an alias (possibly also if destination address for an alias). * (Possibly related) E-mail address is also one of the list owners. In that environment, Postfix seems to check only 'virtual_transport' list, which in my case is dovecot-lmtp, and when it doesn't find the mailman listname@domain entry in there, it sends a 550 user unknown. It seems to be that it isn't getting passed to 'transport_maps', which is mailman-lmtp. When I remove that one address (that is in /etc/postfix/virtual) from the list of subscribers, I'm able to post again. Interestingly enough, when I put it back in as a subscriber. I'm still able to post. So it seems unsubscribing and re-subscribing that address fixed it, or adding an additional list owner and deleting it fixed it, or some combination of those. I know this might be shaping up to be a very unlikely scenario. But basically the account is mine, an admin, doing testing before/after a deployment.. I'll try to create a few test procedures to document the method to reproduce the problem, and also hopefully fix it. If I can do that, I'll open another thread. This could also be a postfix config error of some kind, which is definitely possible if not likely. Thanks for reading. - Matt Alberti -----Original Message----- From: Abhilash Raj <maxking(a)asynchronous.in> Sent: Monday, December 14, 2020 11:42 PM To: matthew(a)alberti.us; Mailman users <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us <mailto:matthew@alberti.us> wrote: > I created a list in the Postorius interface, used it, and then deleted > it. A week or so later, I re-created the list, and things were fine > thru the creation and subscription process. But when I sent a message > to the list, a > "550 user unknown" error was sent back. Can you share more error details from the Mailman logs? If 550 error response was sent, there must be some internal error traceback in the logs. > > > I tried to determine if this is a known issue by searching the issues > in Gitlab; but didn't find anything. But wanted to ask if this was a > known issue or not? I personally don't remember seeing such an issue, but Mark or others might know. > > > > Thanks. > > > > - Matt Alberti > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To > unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

[MM3-users] Mailman List Lost on URL transfer

by heartsandbones＠zoho.com

Hello Mailman Forum! I hope you all can help me. I have been banging my head against this issue for weeks. Here’s the scoop: I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. This is my first post to this forum, so I hope I’ve done so correctly. Thanks so much! Licity

7 years, 10 months

[MM3-users] Re: clone a list?

by Dave McGuire

On 1/17/22 4:16 PM, Mark Sapiro wrote: >> Hi folks. Is there a way to clone or duplicate a list in MM3, i.e. >> create a list with a different name but other settings etc being >> identical? > > The short answer is not yet. > > Would you also want to clone the list membership? If not, you could > possibly do something directly with the database mailinglist table by > adding a new row with all the column values other than id, list_name and > list_id equal to those of the existing list. No, different membership. No problem, I'm just being lazy about it; I'll just duplicate it and copy the settings over manually. I only have two clones to make so it's really not a big deal. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

3 years, 6 months

[MM3-users] Re: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/23/24 13:23, Gerald Vogt wrote: > > I don't quite understand the relevance of the user accessing the > localhost tcp port. Any local user can do that. I am trying to duplicate what Mailman does in an attempt to find the issue. > I can access the template content with > > curl > http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… > > as well as > > curl > http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… > > as any user on the mailman server. How about ``` curl -A 'python-requests/2.32.3' http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… ``` as the Mailman user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 25, 2017 9:17:33 PM EDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: >On October 25, 2017 9:13:20 PM EDT, Mark Sapiro <mark(a)msapiro.net> >wrote: >>On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: >>> >>> No to the domains part and I think virtual alias maps is needed: >>> >>> mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx >>in BOTH virtual_mailbox_domains and relay_domains >>> Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not >>list domain xxx in BOTH virtual_mailbox_domains and relay_domains >>> Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: >>reject: RCPT from >>pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 >><test123@xxx>: Recipient address rejected: User unknown in virtual >>mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP >>helo=<[10.0.0.29]> >> >>(above slightly sanitized for return to the list) >> >>The issue here is your list domain cannot be a virtual_mailbox_domain >>or >>a virtual_alias_domain. >> >>I have the same issue on mail.python.org where we have both Mailman 2 >>and Mailman 3 lists @python.org. and python.org is a >>virtual_alias_domain. >> >>I have a group of MRs for a branch that implements "alias_domains" to >>deal with this. >> >>Basically it works by creating another (virtual_alias_maps) >>postfix_vmap >>mapping to map list addresses @python.org to addresses @x.python.org. >>Then the postfix_domains and postfix_lmtp maps have the x.python.org >>domain and there is a patch to mailman/runners/lmtp.py to map the >>x.python.org domain back to python.org. >> >>The various MRs are >><https://gitlab.com/mailman/mailman/merge_requests/202> for the core, >><https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the >>REST bindings used by Postorius and >><https://gitlab.com/mailman/postorius/merge_requests/186> to be able >to >>set an alias_domain via Postorius. >> >>That's not all implemented at mail.python.org. What's there is the >>basic >>Postfix config, a bash script the generate the new mappings from the >>old >>and a simple patch to mailman/runners/lmtp.py. >> >>So, the bottom line is it can be done and it's in process, but it >won't >>really be supported until Mailman 3.2. In the mean time, you just need >>to have a separate domain for your lists that isn't a >virtual_*_domain. > >Ok thanks. At least I have a clear answer now. Any ETA on 3.2 in mind >yet? >-- > >Thanks, > >Fabian S. > >OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC >_______________________________________________ >Mailman-users mailing list >mailman-users(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Mark, Ok I have it almost perfectly working now having taken your direction and configuring a unique domain not in my email system already. But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. https://github.com/maxking/docker-mailman Thanks. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

7 years, 9 months

[MM3-users] Re: Mailman 3.2.0 Hyperkitty fulltext index error

by Marvin Gülker

Hi, Am 12. Juli 2018 um 08:14 Uhr -0700 schrieb Mark Sapiro: > This is due the the change from Python 2.7 to Python 3. The existing > search index is not compatible with Python 3 whoosh. Ah, I see. > I fixed this by deleting all the files in the index directory which is > defined as PATH in HAYSTACK_CONNECTIONS in your settings and running > 'django_admin update_index', but just running 'django_admin > rebuild_index' should do it. I simply followed your first suggestion, and it worked. I deleted all files in the index directory (which was "fulltext_index" in the "mailman-suite_project" directory, as we use https://gitlab.com/mailman/mailman-suite/tree/master/mailman-suite_project) and then ran update_index. That took a while, but succeeded. Since then the errors are gone. Thank you! Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

7 years

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 14/02/19 1:08 PM, Mark Sapiro wrote: > Presumably this is list mail so your list copy should be the same except > for the few headers related to delivery from Mailman to you. Nope. I cannot send *any* emails to a gmail address. So it is the first "Welcome to the list" email. As far as I can tell there is no solution to the problem, which is why I ask is any one else having this problem? Am I incredibly unlucky or is this a known problem? I have a SPF record. I have tried a new VPS on a different IP address. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 5 months

[MM3-users] Re: mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option

by Henry S

Thanks Mark. That's exactly what I am looking for. On 3/12/2020 1:09 pm, Mark Sapiro wrote: > On 12/2/20 5:42 PM, Henry S via Mailman-users wrote: >> I am trying to change email "To" field to user's email instead of >> mailing list's email. e.g. "To: <user(a)gmail.com>" instead of "To: >> <mailman-users(a)mailman3.org>" > > In Postorius set Settings -> Alter Messages -> Personalize to Full. > > >> I looked around old mailman configs they mentioned about adding >> >> OWNERS_CAN_ENABLE_PERSONALIZATION option in mm_cfg.py >> >> is this feature still available in mailman3 ? Can I do it via Postorius >> or REST API? > > There is no setting in Mailman 3 to control the ability to set > personalization. It is always available. > >

4 years, 7 months

[MM3-users] Delete user

by Rainer Herbst

Hi *! Recently, I have updated my docker images to 0.4.2 and it worked great. In the Postorius GUI, I see a new topic "Users" and found it quite comfortable. But one problem remais open - how can I delete a user alltogether, i.e. including his subscription and account data from the database? The reason for this question are the GDPR regulations - we do subscribe new staff members to some lists automatically, and should unsubscribe them and delete the entries after they left our organization. Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years, 4 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Andrew Hodgson

Abhilash Raj wrote: >Mailman core's entire state is in the var/ directory above. I was working round my own backup strategy a few weeks ago as I discussed earlier on this list. One thing I found when the directory structure that Mailman Core uses is that the lists directories do not get re-created when Mailman Core starts if they don't already exist. Is this something that should happen, and when would those directories get created? Every other directory did get re-created. In my case I was moving from a Dockerised installation to one using venvs, and as the directories from the Docker installation were empty as there hadn't been any postings for a few days, I didn't transfer those over. I created the list directories myself and everything carried on. Thanks. Andrew.

5 years, 3 months

[MM3-users] Re: Error after upgrading mailman3

by Gelpi Andrea

Il 04/05/20 17:44, Abhilash Raj ha scritto: > This is a known and fixed issue in the newer releases of Mailman, I am unable to find the original issue though. The issue is that you need to upgrade dependency on falcon to be >=1.4.0. > > Since this is a Debian package, you may want to contact Debian packaging team for this issue. Thank You. The debian package is python3-falcon. To upgrade to V 1.4.1 I also need to move to pyton 3.8. I read here some problems exists with that version. For now I revert to mailman 3.2.1 By the way do you know which mailman version introduce the command mailman notify? Thank You -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 2 months

[MM3-users] Re: Imported Digest Settings

by Brian Carpenter

On 2/16/21 5:21 PM, Mark Sapiro wrote: > Depends what the issue is. The two most obvious approaches are upgrade > to Mailman 3.3.3 if you aren't already there and switch from plain to > MIME digests, but I would really like to see the full raw source of this > digest messages to try to see if there is some other issue. > > >> What I did: I had the client change the list member's digest setting >> from plain-text to mime. Was that the right instruction to do? > It will probably help, but if this is Mailman 3.3.3, there's still a bug > somewhere that needs to be diagnosed and fixed. Hi Mark, The beginning of my OP stated I was using Mailman 3.3.3. Remember to use your reading glasses old man! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] what process creates webui tables (mailmanweb db)?

by tflatley＠gmail.com

hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate - this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file python3 manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? Thanks

2 years, 10 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 16:54, mark(a)suburbia.org.au wrote: > Once again, thanks for taking time to reply. > > Mark Sapiro wrote: >> On 11/18/24 04:12, mark(a)suburbia.org.au wrote: >> This should not happen. In the message as delivered to the list what do >> you see in the X-Mailman-Rule-Misses: header and the >> X-Mailman-Rule-Hits: header if any? > > ``` > X-Mailman-Version: 3.3.8 > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address > X-Mailman-Rule-Hits: member-moderation This says it was held for moderation. Is there an X-Mailman-Approved-At: header which would say it was approved by a moderator? -- 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: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Stephen J. Turnbull

Brian Carpenter writes: Thank you for going to the trouble of making your guide easily available to and usable by the community. > On 2/25/21 8:28 PM, Abhilash Raj wrote: > > Is there a specific reason that you chose to go with an entirely new doc > Yes. Just from observing the communications on this list, there are > multiple ways to install Mailman 3 Yes, and we try to document them all, written by different people at different times. I don't think that's an unreasonable approach given the wide variety of situations of our site admins, but I'm sure a lot of "greenfield" installations will appreciate your thorough, "from parts manifest to assembled working system", approach. > My guide represents a very stable and easily maintained environment > for me and hopefully others. I'm pretty sure that there are quite a few folks with very similar installations. > Is there an official guide? See that is the problem. Yes, it has been a problem. At this point I'm pretty sure :^þ that mailman.readthedocs.io is the official guide, but that hasn't been well-known in the past and there are a lot of mirrors and unofficial guides like yours (but not as thorough). And there's a lot of stuff on the Wiki that requires effort to integrate because it was originally written in reply to a particular user's questions. > I did not know there was an official guide. Because every time I > tried finding documentation in the past using Google searches, I > got fed outdated information. So for me the guide that I came up > with, works great for me and if no one else uses it, I certainly > will. > > Is it something about the contribution process to the official > > documentation that makes it hard > > Well I don't know much about any of the above approach to > > documentation. So I would say that is a hindrance. Sphinx is pretty much the gold standard for Python documentation. It looks nice. The markup is reStructuredText, which is a powerful, Markup-like language with a few features that Markup didn't have last I looked, and it's extensible by Python programmers. It's also used in marking up Python docstrings. So you can see why we'd choose it. But if you're *not* an experienced Python programmer, none of those are advantages. > > I am just trying to understand how can we lower the barrier for > > community members to help contribute to existing docs instead of > > them having to create new ones. Specifically around installation, > > since that tends to get stale often when depedent packages change > > or a new dependency is added that breaks the installation. @Abhilash: For non-Python programmers, it's not *that* hard, but there is a hurdle at the beginning. I think the best thing to do is to advertise that we're always looking for doc contributions, and that if somebody's not familiar with reST, they shouldn't let that stop them. Of course we'll help them with markup, and if necessary we'll do it. > The Dart Sass section came from Mark's comments on this list. Now, automatic conversion of Mark's posts to reST documentation is a problem I wish we could get those Red Army AI programmers to work on! Steve

4 years, 5 months

[MM3-users] Re: Re-enable member after bouce processed disable

by Henrik Rasmussen

Henrik Rasmussen wrote: > Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. > When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. It seems that I was right, however, I need to re-enable all members on a single list who have been disabled due to bounces. Using the `mailman members` command it is possible to list such members, however how do I enable them using either the `mailman shell` command (available) og the mailmanclient (needs first to be installed in the docker container)? Regards, Henrik Rasmussen

3 years, 6 months

[MM3-users] Mailman3 is wrongly display name a list member

by Allan Hansen

All, I got an issue with one subscriber (multiple lists). When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' <a(a)foo.com>. I went into Django and added the name 'B' to the subscriber's account (the name was empty). I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' <a(a)foo.com>. The subscription again lists as 'B' <a(a)foo.com>. This brings up a previous discussion of display names on this list, but I have not been able to find any solution to the need to change Mailman3's display names for a subscriber. It is beyond weird that unsubscribing, setting the account display name and resubscribing the member fishes back up the old and wrong display name. What can I do to help this member? Yours, Allan

3 years, 6 months

[MM3-users] Dealing with email bounces from web signups

by Andrew Hodgson

Hi. Back on the topic of bogus web signups again. I am dealing with several hundreds of these per month and we're talking a very low traffic system here. I have a cronjob to remove the users from the database. Right now a concern for me is handling the bounces for the confirmation emails that don't get delivered. These are coming from postorius(a)lists.hodgsonfamily.org<mailto:postorius@lists.hodgsonfamily.org> which I have redirected to a mailbox so as not to clutter up the mail queue. What I would ideally like is if we get a bounce from one of these confirmation mails we delete the user from the database but that is probably a future request. We don't get too many of these, around 20-30 a week. What are other people doing with these messages? Thanks. Andrew.

3 years, 4 months

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by nate

On 2022-01-25 6:56, Stephen J. Turnbull wrote: > nate writes: > > > It's "just worked" over the years, no issues. I have been using > > Linux since 1996, not a newbie here. > > If so, and you're familiar with Docker (obviously not the same thing, > but maybe? ;-), you might find the containerized version provided by > Abhilash (which is usually quite up to date) closer to a turnkey > installation. I use the venv approach myself (more because developer > than out of principle), so I'm not really familiar with the container > distribution, but from traffic on the list I get the impression that > most of the troubles have to do with networking in containers, rather > than configuring Django and WSGI hosts. That is an interesting idea. I'm not much into docker but I certainly could do a LXC container or just another VM to run the older mailman and just not update it? My mailing lists are probably less than 1 message a month on average so real low usage. > I appreciate the detailed description of what you did and didn't find > in the docs. The docs are weak on administration, we admit, and we we > get some of those round tuits .... Sure thing, I tried hard to be as polite as I could don't want to offend anyone with their hard work. > It's been years since we had an answer to that question. Mark might > have more to say, but the last time we were challenged on this, the > rival was Sympa, and the conclusion I came to was that the use cases > are different. I'll take a look at that thanks. I'd like to stick to mailman if I can though bypassing the distribution as was suggested to me to get a better version does worry me a bit from a maintainability standpoint, I try to keep things as clean as I can, and holy crap I was shocked at the number of dependencies the mailman3-full package pulled in(165 total packages that were not already installed, most were python3 related). So bypassing that entirely does worry me a little, not that I run anything mission critical on my home server but my home server(that runs in a colo, so not really at home, I have 30 systems on my home network/colo network) historically is super low maintenance. An extreme case I came across last year I discovered I was still using 2 RBLs in postfix that were shut down between 7 and 12 years ago! That just generated warnings in the postfix logs over the years but I wasn't paying attention(never hurt anything). Till I looked up the RBLs to see..wow, gone for that long, so I updated my postfix config! My postfix configs date back to ~2003 and have had minimal changes over the years, same goes for the rest of my mail system whether it was mailman, or Cyrus IMAP (barring a one time painful migration from Cyrus 1.x to 2.x). > Depending on your Linux distro, and your attitude to risk, Python 2 > plus Mailman 2 in a container, VM, or even a dedicated host in the DMZ > or outside the firewall might be a reasonable solution. I will certainly consider that as an option, thanks!! Devuan 3.x still has mailman 2.1.29, in theory I could hack together a 2.1.39 Debian package to get it up to date in that respect. nate

3 years, 6 months

[MM3-users] Mailman3 via Docker and NGINX

by brian＠emwd.com

I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. It seems I am stuck with the nginx setup. I created a sitename.com.conf file in the /etc/nginx/conf.d folder. I have the following inputted there: server { listen 80; server_name `sitename.com`; location /static/ { alias /opt/mailman/web/static/; } location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8000; uwsgi_read_timeout 300; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } However when I go to http://sitename.com (obviously using an alias here for privacy reasons) I get the default nginx index page. Do I need to add anything to the main nginx.conf file to be able to see my mailman3 installation? Thank you for any assistance, Brian Carpenter

6 years, 7 months

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

by Mark Sapiro

On 7/26/20 10:13 PM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > But I am having a final query over this issue. Out of the two hyperkitty > records I observed in the database, I am confused which record do I need > to remove directly from the database? Because I doubt still there is one > more list with the same style i.e. with two hyperkitty records. If there are multiple rows in the listarchiver for the same `mailing_list_id` and archiver `name`, you can safely delete all but one of them. It doesn't matter which ones you delete. They should be identical except for the `id`. -- 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: moderator cannot login to the list

by Brian Carpenter

On 12/16/20 7:36 AM, Gregory Edigarov via Mailman-users wrote: > GNU Mailman 3.2.1 (La Villa Strangiato) > Python 3.7.3 (default, Jul 25 2020, 13:03:44) > > I've imported some lists from mailman-2.1 > using 'mailman import21' command. > > the import went fine, I am able to login into postorius as admin, and > see all imported mail list data. > but login as a moderator member of a list. I tried to reset moderator > password via rest api. > That doesn't help. > > how is that supposed to be done? > > thank you. Hi Gregory, Are we talking about the same user as the one that is logging in as admin? Or do you have additional moderators that need to be able to login and moderate your lists? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Re: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Wikinaut

I could not fix the problem, apparently there is a mismatch somewhere now. sudo pip uninstall django-q Found existing installation: django-q 1.3.9 Uninstalling django-q-1.3.9: Would remove: /usr/local/lib/python3.9/dist-packages/CHANGELOG.md /usr/local/lib/python3.9/dist-packages/django_q-1.3.9.dist-info/* /usr/local/lib/python3.9/dist-packages/django_q/* Proceed (y/n)? n whereas dpkg -l | grep django-q: ii python3-django-q 1.2.1-1 /usr/lib/python3/dist-info: 4 drwxr-xr-x 8 root root 4096 21. Jun 2022 django_q 4 drwxr-xr-x 2 root root 4096 21. Jun 2022 django_q-1.2.1.egg-info sudo apt remove python3-django-q the following packet will be REMOVED: mailman3-full mailman3-web python3-django-hyperkitty python3-django-q Continue [Y/n] n What to do? I don't want to remove mailman3, I just want to bring the 1.2.1-1 to 1.3.9...

1 year, 10 months

[MM3-users] Re: Intermittent: pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77

by Danil Smirnov

Hi, This is most probably to be fixed in the next core release via https://gitlab.com/mailman/mailman/-/merge_requests/864 It seems the same issue I've filed for PostgreSQL: https://gitlab.com/mailman/mailman/-/issues/854 You can apply the patch for now and help with its testing. BR, Danil пн, 24 мая 2021 г., 11:25 Torge Riedel <torgeriedel(a)gmx.de>: > |Hi list, sometimes I get the following error in mailman core's log: > "pymysql.err.InternalError: Packet sequence number wrong - got 102 expected > 77". I attached the full log after this mail. I check the provided link in > the log (|||http://sqlalche.me/e/2j85|) and also searched for it on the > internet and found the following possible reasons: 1. DB user does not have > permissions at all -> I doubt that, because in general mailman is working > ok 2. DB user is not allowed to connect from remote -> I doubt that too, > because everything is on one host and DB user is allowed to connect from > localhost 3. Multi-Threading -> pymysql is mentioned to be not thread-safe > and each thread needs its own connection May this be caused by > multi-threading? What do I have to do (is there anything I can do?) to > solve this on my own?||||| > > Kind regards > Torge > > || > > |Full log follows: [2021-05-23 07:31:45 +0200] [8244] [ERROR] Error > handling request /3.1/lists?advertised=true&count=10&page=1 Traceback (most > recent call last): File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1284, in _execute_context cursor, statement, parameters, context File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", > line 590, in do_execute cursor.execute(statement, parameters) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 170, in execute result = self._query(query) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 328, in _query conn.query(q) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 517, in query self._affected_rows = > self._read_query_result(unbuffered=unbuffered) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 732, in _read_query_result > result.read() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1082, in read self._read_result_packet(first_packet) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1151, in _read_result_packet self._get_descriptions() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1222, in _get_descriptions field = > self.connection._read_packet(FieldDescriptorPacket) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 671, in _read_packet % (packet_number, self._next_seq_id)) > pymysql.err.InternalError: Packet sequence number wrong - got 102 expected > 77 The above exception was the direct cause of the following exception: > Traceback (most recent call last): File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/database/transaction.py", > line 50, in wrapper rtn = function(*args, **kws) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", > line 193, in __call__ return super().__call__(environ, start_response) File > "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", > line 269, in falcon.api.API.__call__ File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/lists.py", > line 322, in on_get resource = self._make_collection(request) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 172, in _make_collection request, self._get_collection(request)) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", > line 167, in _paginate return list_start, total_size, > collection[list_start:list_end] File > "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/utilities/queries.py", > line 42, in __getitem__ return self._query[index] File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", > line 3149, in __getitem__ return > list(res) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", > line 3481, in __iter__ return self._execute_and_instances(context) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", > line 3506, in _execute_and_instances result = > conn.execute(querycontext.statement, self._params) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1020, in execute return meth(self, multiparams, params) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", > line 298, in _execute_on_connection return > connection._execute_clauseelement(self, multiparams, params) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1139, in _execute_clauseelement distilled_params, File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1324, in _execute_context e, statement, parameters, cursor, context > File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1518, in _handle_dbapi_exception sqlalchemy_exception, > with_traceback=exc_info[2], from_=e File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", > line 178, in raise_ raise exception File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1284, in _execute_context cursor, statement, parameters, context File > "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", > line 590, in do_execute cursor.execute(statement, parameters) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 170, in execute result = self._query(query) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", > line 328, in _query conn.query(q) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 517, in query self._affected_rows = > self._read_query_result(unbuffered=unbuffered) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 732, in _read_query_result result.read() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1082, in read self._read_result_packet(first_packet) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1151, in _read_result_packet self._get_descriptions() File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 1222, in _get_descriptions field = > self.connection._read_packet(FieldDescriptorPacket) File > "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", > line 671, in _read_packet % (packet_number, self._next_seq_id)) > sqlalchemy.exc.InternalError: (pymysql.err.InternalError) Packet sequence > number wrong - got 102 expected 77 [SQL: SELECT mailinglist.list_id AS > mailinglist_list_id, mailinglist.preferred_language AS > mailinglist_preferred_language, mailingli$ FROM mailinglist WHERE > mailinglist.advertised = true ORDER BY mailinglist.list_id LIMIT > %(param_1)s] [parameters: {'param_1': 10}] (Background on this error at: > http://sqlalche.me/e/2j85) | > > _______________________________________________ > 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/ >

4 years, 2 months

[MM3-users] Re: Another interesting error...

by Simon Hanna

On 04/23/2018 11:29 PM, Darren Smith wrote: > "It's in Mailman's database in the 'message' table." > > I can see the message table - is there a way to see where it is marked as > "held"? All I'm seeing in that table is id, message_id, message_id_hash, > and path. > > I'm wanting to be able to query for held messages for a given mailing list, > as there are currently over 98,000 entries in the message table. This should be possible using the mailman shell http://mailman.readthedocs.io/en/latest/src/mailman/model/docs/requests.htm… I haven't used the shell extensively and didn't read the whole docs, but it looks like it's the right place to look. If you can't do that using the shell, I'd say it's worth a bug report :-)

7 years, 3 months

[MM3-users] Re: Python error, debian package, again

by Lars Schimmer

On 11/5/19 6:48 PM, Mark Sapiro wrote: > On 11/5/19 7:04 AM, Lars Schimmer wrote: >> >> Abhilash Raj (maxking) mentionend, it maybe a issue with mailman core >> trying to deliver the message to hyperkitty. >> But how can I remove those broken messages, or twitch hyperkitty to >> accept and discard them? > > > Look in Mailman's var/archives/hyperkitty/spool/ directory. This is > where messages that mailman-hyperkitty can't deliver to hyperkitty are > kept for retry. Yeah, there are some in this folder. Can I simply remove those entries from the spool directory? Or do I need to fiddle with any cmdline tool? thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

5 years, 8 months

[MM3-users] Invalid confirm text

by w.schoener＠alp.dillingen.de

Hi there, I am new to mailman 3, python and django. I try to configure a mailman 3 list. To establish german text, I used the web-admin interface of mm3 in the "templates"-section. I inserted a text for "The message sent to subscribers when a subscription confirmation is required" Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: return the message unchange. When I return the message, I get an answer: Invalid confirm text. My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. Thank you Wolfgang

4 years, 11 months

[MM3-users] Re: Postorius no connection to REST API

by Richard Rosner

Abhilash Raj wrote: > is the config to talk uwsgi protocol and you want to configure Web server to Proxy using the same protocol. You can find that in the uwsgi docs here: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html You probably need an apache module to speak uwsgi, the docs should have the details. > Notice the URL is uwsgi:// instead of http://. > Other way is to configure uWSGI to speak HTTP, which can be done by replacing "uwsgi-socket" by "http-socket” in the uwsgi.ini configuration. This might be the easiest for you to try, do make sure to restart the mailman-web service after making the change in uwsgi.ini. Thanks, that already helped quite a bit. The website is now loading again, but unfortunately not much else. The site still shows no Connection to REST API.

3 years, 11 months

[MM3-users] Re: Strange password problem

by Stephen J. Turnbull

Eggert Ehmke via Mailman-users writes: > So for now I use the same password for all logins, and that > works. But is that a good solution? The other option would be to > assign multiple superusers for each domain, but they would still > allow to log in via some other domain. If you own the domains, you can probably set up some sort of trivial website on each that does nothing but admin stuff, with the same database backend. Then you can have different passwords for "admin" and the browser will remember them. Probably more tricky than it's worth. What are you doing that requires admin privileges, but you want to authenticate separately for each domain? I ask because we've always envisioned creating a domain-level administrator role, but until now we've had no demand for it. Steve

1 year, 10 months

[MM3-users] Programmatically modify Thread-Topic *before* message is sent out the door?

by Thomas Ward

We use a custom plugin to do numeric thread stamping, which has been working well in the code system. However, it was discovered by Microsoft that Microsoft Outlook and OWA prioritize the Thread-Topic header over the Subject header, which results in the oddness we've experienced in MS365 clients in testing. During our tasks though a custom handler goes through during the pipeline and modifies the Subject field accordingly, adding a thread tag to it. While this is 'fragile' it does work; the only problem is that Thread-Topic doesn't get altered. Programmatically, how would we alter the Thread-Topic during the handler's processing to prepend the corresponding prefix/tag so that when the message actually goes out the door it is properly sending with the modified Thread-Topic? Thomas

1 year, 7 months

[MM3-users] Re: Unsubscribe from a list

by Odhiambo Washington

On Mon, Mar 24, 2025 at 11:38 AM <pau.baiges(a)csuc.cat> wrote: > Hello, > When a list member sends an email to list-leave@... to unsubscribe from a > list, neither the moderators nor the list owners receive it. Only the > person who sent the email receives a confirmation email. > It depends on the settings you have for the particular list. In the list Settings -> Member Policy -> Un-Subscription Policy, you can choose one of the options: 1. Open 2. Confirm 3. Moderate 4. Confirm then Moderate What those options do is documented below that dropdown box. HTH -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 1 week

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/26/20 9:12 AM, Odhiambo Washington wrote: > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: >> >>> There is still some confusion on my part about the directives in the file >>> so allow me to seek some clarifications. >>> >>> The following are the contents of a file I have created and placed in my >>> Apache Includes/ directory. >>> I was hoping that with it, I can now access http://lists.my.server/mm3 >> and >>> get the UI. >>> >>> <CUT> >>> >>> # Global section >>> WSGIDaemonProcess mailman-web display-name=mailman-web >>> maximum-requests=1000 umask=0002 user=mailman3 \ >>> group=mailman3 >>> >> python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 >>> \ >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var >>> WSGIRestrictSignal Off >>> >>> <VirtualHost *:80> >>> ServerName lists.my.server >>> ServerAdmin odhiambo(a)gmail.com >>> >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in >> the >>> # provided example so I kept it. I also made changes to WSGIDaemonProcess >>> # based on my own mod_wsgi experience elsewhere.) >>> >>> ErrorLog /var/log/myserver-error.log >>> LogLevel debug >>> >>> # This goes in the VirtualHost block for the domain. >>> >>> # Mailman 3 stuff >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this >>> directory supposed to be and what/who creates it and with what >> permissions?* >> >> >> It is created/updated by the mailman-post-update script based on CONFDIR >> and STATIC_DIR. >> > > The fact that I have run the mailman-post-update script and these > directories aren't created means there is a problem in my setup, yes? If your mailman-post-update script is essentially the same as <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> and it ran successfully, it would have created opt/mailman/mm/static and populated it. What was the output when you ran it? > Yes, I have these files: > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > /opt/mailman/mm/settings.py > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > /opt/mailman/mm/settings_local.py Is there an empty /opt/mailman/mm/__init__.py file? > PS: I made my /opt/mailman to be owned by mailman3:wheel because of a > confusion with the instructions at some point in the reading > of some documentation previously (in my previous attempt last year!) and > had noted that in my NOTES. I'll change this once things get clear for me. > Also, the fact that one of the init scripts > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> > in your "reflection" page was calling sudo :) It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user as it should. Have you set USER=mailman3 in yours? -- 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: restrict sending to owner/moderator

by David Krantz

Hi, I have just tested a variant of this as I got curious: You find the member you want to be able to send emails without moderation, then set Administrative Options to "Accept Immediately (bypass other rules)". That works. I have found no other ways, though. // David On Mon, Sep 18, 2017 at 11:28 AM, <m.dohmen(a)xconnect.de> wrote: > Hello, > > I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. > > Is there a way to do this? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 10 months

[MM3-users] MM3 occasionally chokes (?)

by Dmitry Makovey

In the last couple of month we've observed some odd behavior from MM3 (namely the core) where it seems like email that is about to be sent to a large-ish mailing list (10K users) has been processed yet never gets sent out until we restart the core. I would appreciate any pointers on where to look for the source of the problem. At the moment, since I can't reliably reproduce it I can't really test it nor do I know where to look next time things get stuck. Mailing list in question is high profile thus when event like this happens I have only limited time amount to spend on troubleshooting/digging before I just restart the core (which by the way takes about 45min to fully start... which is another puzzle to solve at later time) -- Sr System and DevOps Engineer SoM IRT

6 years, 4 months

[MM3-users] Re: Strange password problem

by Stephen J. Turnbull

OK, I'm convinced. No promises yet since I'm not sure of the scope of the work, but here's the issue. Once I understand the scope and have some idea of the design I will add GSoC and other tags as appropriate. https://gitlab.com/mailman/mailman/-/issues/1103 Jens Günther writes: > I do have the exact same situation. I would love to have domain owners > be able to create/manage their own lists for their respected Domain. > > One problem I see with giving them site ownership: when creating a new > list, not only that they could pick the wrong domain by accident, they > also see all the other domains present in the installation. That would > be a nogo, tehrefore we have to create the lists for all associations on > our side. > > Kind regards, Jens.

1 year, 10 months

[MM3-users] Re: 500 error on one list

by Mark Sapiro

On 7/13/24 8:35 AM, Seth Seeger wrote: > > Did this one list get corrupted somehow? This is https://gitlab.com/mailman/mailman/-/issues/657 We still don't know the underlying cause. Note that the first script in that issue assumes that the multiple entries are for the mhonarc archiver, but this isn't always true. If you run this database query SELECT * FROM listarchiver WHERE mailing_list_id = (SELECT id from mailinglist WHERE list_id = 'list.example.com'); replacing list.example.com with the list_id of your problem list, you will see there are two entries with the same name. Then do DELETE FROM listarchiver WHERE id = nn; where nn is the id of one of the duplicates, it doesn't matter which. -- 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] REST API notes

by tlhackque＠yahoo.com

As a beginner with the REST API, I found it necessary to read code and experiment to figure out how to get things done. There are a number of implementation choices that are unusual. There is some documentation in src/mailman/rest/docs. It's oriented toward Python and intermixes the mailman client & REST API, apparently trying to show equivalence. Here are some notes that may help others to avoid repeating my research. They reflect Mailman 3.1. Some reflect issues that I've opened, but I think it's worth knowing how things work today. I attempted to tie together some of pieces that are in the documentation - and note some things that aren't. I may have some things wrong, but this reflects my current understanding. (And client code.) The REST API has a hybrid interface: Requests are made with application/x-www-form-urlencoded POST, PUT, PATCH and delete http requests. Requests are also accepted as parameter strings. The responses are JSON. (This is rather surprising - one would expect JSON requests - and I hope someday they'll be accepted, as the split complicates clients. I suspect this evolved to simplify the initial Web GUI client (Postorious), but it precludes using standard JSON-in/JSON-out client libraries.) Error responses are often misidentified as content-type: application/json, but actually contain a text/plain error message. This isn't universally true; for example the 401 response actually IS JSON. A client has to guess and handle decoding exceptions. The API presents resources hierarchically, rooted at '/'. The top level resources include /users, /lists. /addresses, /domains, /system The next level is a resource id. There is a an id which is stable for the lifetime of an object, and a current name (which can be changed). For example, a list has a name like mylist(a)example.com, and a list_id of mylist.example.com. But if you change the list name, it becomes mynewname(a)example.net, while the list_id remains mylist.example.com. Lists are associated with "domains", which are the "domain part" of the list's address. That is, the part after the @. This is sometimes referred to as the "mail host", but there need not be a real host. Just something on the left side of a DNS MX record. Also, don't confuse the use of "mail host" with that of "SMTP Server", which is how Mailman sends mail. The domain is where Mailman expects to receive it. A fully qualified list name is the list name + domain - e.g. its posting address. One domain can (and usually does) support more than one list. If you delete the domain, all its lists go away too. A domain has to be created before you can create a list with an address in that domain. Resources are created with a POST to their top-level resource. To create a domain, post to /domains with mail_host => the domain, and (optionally) description => a description for the GUI. The response isn't JSON as one would expect. In fact, it's an empty application/json response with a 201 status. To create a list, one POSTs to /lists. This post takes a restricted set of parameters; in the case of a list, just its fqdn_listname, (and an optional style - which isn't well defined). The response isn't JSON as one would expect. The Location header of the response contains a URL of the new list. To configure the list, you have to follow up with a PUT or PATCH to that URL + /config This is where you can set the description, posting policy, etc. It's unrealistic to do a PUT; even if you're cloning another list, there's no programatic way to determine which attributes are writable. PATCH what you know... Members are associated with e-mail addresses - which belong to Users. You create a user by posting to /users with email => the email address, and optionally display_name => the name string. (A user can also be implicitly created by subscribing an e-mail address, but that gets confusing.) The e-mail address is the primary email address for the user. More later. Again, you get a Location header in the response, which you can use to PATCH /preferences to set delivery_status, etc. .These preferences are part of a hierarchy - many have a system default, a list default, the user default, and a subscription to that list value. You can find the User associated with a list by a GET of /addresses/address(a)example.net. This GET returns two URLs: user => the user owning this address, and self_link => the address object. Note also that there are both an email and original_email attribute. The latter preserves case. The former is used internally by Mailman as a resource key, etc. (Though exactly what happens if John(a)example.net and john(a)example.net both subscribe is unclear.) Once a list is configured, you can add members. This requires the list_id - which you don't (officially) have. So you do a GET on the list resource, to get the list_id. Then you can subscribe a member with list_id => (the list id), subscriber => email address. Optionally you can pre_verify/confirm/approve the member and/or add a display_name.. POST to /members. Again, you get a Location header back. You can't specify everything you might like. as a creation attribute. So you may have to PATCH the member to, for example, set the moderation_status. You may also need to PATCH the member /preferences if you want to set list-level delivery status, etc. Consider adding at least an owner when creating a list. One challenge is that almost everything requires multiple REST operations to set up. But REST (by definition) is stateless. So the best you can do is order operations & hope. The mailman client examples refer to transactions (e.g in users.rst, there is 'transaction.commit(); - but REST can't hold state. It does appear that the server uses DB transactions to ensure that any given REST operation is ACID, but the composite operations (e.g. create a list and set it's config) can not be Atomic. This is an architectural flaw in the API. Symbolic names (which are required) for attributes are in the src/mailman/interfaces/(class).py. What you can get/set comes from src/mailman/rest/(class).py.

8 years, 1 month

[MM3-users] Re: Help request, almost got it going, but ....

by Mark Sapiro

On 09/01/2017 04:20 PM, Claus-Justus Heine via Mailman-users wrote: > > The issue seems not to be overly active. I thought -- coming from > Mailman v2 -- that the configuration of acceptable submitters to an > email list (e.g. keep everyone moderated?) would be a central and > prominent and important configuration issue. Seems not to be a central > point. Mmmh. Acceptable aliases corresponds directly to MM 2.1 Privacy options... -> Recipient filters -> acceptable_aliases. It has nothing to do with submitters. It is a list of other addresses that can be in the To: or Cc: of a post to avoid and "implicit destination" hold if the list posting address is not there. -- 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: MM3 Docker

by Mark Sapiro

On 1/8/19 10:50 PM, Odhiambo Washington wrote: > Now that has clarified the matter for me. That even when I am logged out, > the scripts do the neccessary > to activate the venv to run things. As mentioned before, a virtualenv is not like a container. It is only a directory that contains among other things a bin/ directory with activate scripts and easy_install, python, pip and wheel commands. When you activate a virtualenv in your shell, all it really does is add a deactivate command, modify the command prompt and insert its bin/ directory at the beginning of its PATH. What this means is whether or not a virtualenv is "active", running a command from the bin/ directory in the virtualenv is using the virtualenv. -- 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: Sanity check of upgrade procedure

by David Newman

On 10/26/22 3:10 PM, Mark Sapiro wrote: > On 10/26/22 11:08, David Newman wrote: >> >> For these new releases, is that mistune step still needed? > > > No. That is one of the issues fixed in HyperKitty 1.3.6 which now > requires mistune>=2.0.0,<3.0 and will work with those versions. OK, thanks. Before getting to mistune, this command, run as mailman in a venv: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi Mailmanclient produced this error: .. Attempting uninstall: mailman-web Found existing installation: mailman-web 0.0.6.dev9+gc606169 Uninstalling mailman-web-0.0.6.dev9+gc606169: Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: 'WHEEL' Check the permissions. The command also said I needed to upgrade pip. Doing that produced a similar error. How to resolve this error? Thanks again. dn

2 years, 9 months

[MM3-users] Re: New Installation of MM3 is not archiving

by Mark Sapiro

On 1/30/23 02:57, Onyeibo Oku wrote: > > My new MM3 instance does not seem to be archiving. List subscribers > are currently sending and receiving mails on their subscribed lists. > However, none of the correspondence is showing up at > https://mailing-list-site.tld/archives/. That page shows a listing of > the active mailing-lists with '0 participants' and '0 discussions'. > Whereas, those lists contain mails. > > How do I troubleshoot this? The messages as pickled message objects are probably queued in /opt/mailman/mm/var/archives/hyperkitty/spool/. The first place to look for the reason is in /opt/mailman/mm/var/logs/mailman.log. There might also be info in /opt/mailman/web/logs/mailmanweb.log -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Installation Questions [Installation}

by Odhiambo Washington

On Thu, Nov 14, 2024 at 4:05 AM Arte Chambers <paul.m.robey(a)gmail.com> wrote: > I'm also running into permission errors with Postgres - user does not > have permissions on public schema. I didn't see anything in the docs about > how to grant proper access to these tables. > Off the top of my head, this is what I used to do, but the same issue has been discussed several times on the list. # su -u postgres psql #\c mailman postgres # GRANT ALL ON SCHEMA public to mailman; #\c mailmanweb postgres # GRANT ALL ON SCHEMA public to mailman; -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

8 months, 2 weeks

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mark Sapiro

On 10/1/20 6:12 PM, Mark Sapiro wrote: > >>>>> m.filter_types = ['application/pdf'] >>>>> commit() >>>>> print(list(m.filter_types)) >> ['application/pdf'] > > > This should allow ONLY the PDF and nothing else, not even the text/* > message body parts. Sorry, my statement above is wrong. That should also remove the pdf, but it's redundant given that 'application/pdf' is not in pass_types. > Actually, what's m.filter_content? I suspect it's False which means > don't do any content filtering. I think this is the 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, 10 months

[MM3-users] Required permissions for mass operations

by mailman3＠werner.by

Hi, I've Mailman 3.3.3 running with some mailing lists and it works great. Now I'm looking for a configuration option. I'd like to have some users with permission to - moderate lists AND - perform mass operations (add members, delete members) AND - change settings for single members (execute actions in menu point "Users", "Members") It should be impossible to change other list or mailman settings for this users. To give them the moderation permission is quite easy: I add the users to the moderators of the lists. But for the user management I've to add the users to the list owners and then is there no restriction anymore to change the full list configuration. What can I do? I link to a documentation for this would help as well, but I found nothing. Thanks a lot for an answer Torsten

10 months, 2 weeks

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Mark Sapiro

On 2/27/19 12:38 PM, Danil Smirnov wrote: > Hi Abhilash, > > ср, 27 февр. 2019 г. в 22:21, Abhilash Raj <maxking(a)asynchronous.in>: > >> So, what errors are you looking at in uwsgi*.log? >> > > There are tons of errors like this: > > Unknown command: 'qcluster' > Type 'manage.py help' for usage. > [uwsgi-daemons] respawning "./manage.py qcluster" (uid: 100 gid: 101) > Unknown command: 'qcluster' > Type 'manage.py help' for usage. > [uwsgi-daemons] throttling "./manage.py qcluster" for 26 seconds do you have django-q in INSTALLED_APPS in your Django settings and what is set for Q_CLUSTER? Does the manage.py that's being run here point to the right settings.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Google Summer of Docs

by Terri Oda

On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >Ralph Seichter writes: > > * Mark Sapiro: > > >> > If you post an issue at ><https://gitlab.com/mailman/mailman/issues>, > > > one of our GSOC aspirants may pick it up. > > > > Done, although I wonder if any GSOC participant would want to write > > documentation instead of code... ;-) > >For their actual, Google-supported, project, Google explicitly >excludes documentation. > They do for Google Summer of **Code** but they've just announced Google Summer of **Docs** which sounds really neat and we might want to participate. (It's my personal opinion that our docs have really suffered since I finished my PhD and stopped using them as a warmup exercise when I was procrastinating on writing my thesis. *grin*)

6 years, 4 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Mark Dadgar

On Nov 23, 2020, at 7:05 PM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Apollinaris Schöll writes: > >> My suspicion is that some users like to use the “report spam” >> buttons way too much and then end up with a extremely sensitive >> individual spam scoring. > > Interesting hypothesis, though I see no easy way to confirm it except > surveying the users, which probably isn't something one wants to do. Anecdotally, I believe this to be true as well. I also believe that it’s common for unsophisticated users to just start marking list emails as spam stop seeing them instead of figuring out how to unsubscribe. Which really sucks for everyone else. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 8 months

[MM3-users] Re: mail stuck in "out" queue

by Kareem Zidane

Apologies for that!! Yes, this strace was on the out runner process (pid 17171) and yes, the out runner is running: ``` # ps aux | grep [r]unner=out 82 mailman 1:10 /usr/bin/python3 /usr/bin/runner -C /etc/mailman.cfg --runner=out:0:1 ``` Other lists seem to work fine. Here's what I see in mailman.log, after sending two separate emails to the list: ``` Jun 09 17:36:28 2020 (85) ACCEPT: <CAAQM=w13wB6zM-gkjmUWmL26zFSF2DgNKsX3eFetzjtCVPKmCA(a)mail.gmail.com> Jun 09 17:36:30 2020 (84) HyperKitty archived message <CAAQM=w13wB6zM-gkjmUWmL26zFSF2DgNKsX3eFetzjtCVPKmCA(a)mail.gmail.com> to https://lists.cs50.harvard.edu/hyperkitty/list/ap@lists.cs50.harvard.edu/me… [09/Jun/2020:17:36:30 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:36:30 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu/config HTTP/1.1" 200 3099 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:36:30 +0000] "GET /3.0/users/kzidane(a)cs50.harvard.edu HTTP/1.1" 200 401 "-" "GNU Mailman REST client v3.3.0" Jun 09 17:36:31 2020 (82) Cannot connect to SMTP server postfix on port 25 [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers.lists.cs50.harvard.edu HTTP/1.1" 200 571 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=0&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/requests HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:56 +0000] "GET /3.1/lists/teachers(a)lists.cs50.harvard.edu/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "GET /3.1/domains HTTP/1.1" 200 537 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "GET /3.1/domains/lists.cs50.harvard.edu HTTP/1.1" 200 223 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "GET /3.1/domains/lists.cs50.yale.edu HTTP/1.1" 200 207 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:41:58 +0000] "POST /3.0/lists/find HTTP/1.1" 200 478 "-" "GNU Mailman REST client v3.3.0" Jun 09 17:42:05 2020 (85) ACCEPT: <CAC-4VT7LRb7REc39i=a8wRc50hOuB_5mSEN37ozatqp9RGNfVA(a)mail.gmail.com> [09/Jun/2020:17:42:06 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu HTTP/1.1" 200 373 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:42:06 +0000] "GET /3.0/lists/ap(a)lists.cs50.harvard.edu/config HTTP/1.1" 200 3099 "-" "GNU Mailman REST client v3.3.0" [09/Jun/2020:17:42:06 +0000] "GET /3.0/users/kareemzidane2(a)gmail.com HTTP/1.1" 200 293 "-" "GNU Mailman REST client v3.3.0" Jun 09 17:42:06 2020 (84) HyperKitty archived message <CAC-4VT7LRb7REc39i=a8wRc50hOuB_5mSEN37ozatqp9RGNfVA(a)mail.gmail.com> to https://lists.cs50.harvard.edu/hyperkitty/list/ap@lists.cs50.harvard.edu/me… ``` Doesn't seem there are any errors? I grep'd for errors in mailman.log and this is what I got: ``` FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/var/lists/ap.lists.cs50.harvard.edu/digest.mmdf' ``` No mention of the /hyperkitty/api/mailman/urls API call in mailman.log but I could confirm with tcpdump that mailman is hitting that and I was able to add some logs to the _get_url function in mailman_hyperkitty plugin and it was being called infinitely. /opt/mailman/var/archives/hyperkitty/spool appears to be empty. And lastly, even though emails to this particular list do not go out, they do get archived. Thank you so much! I appreciate all the help!

5 years, 1 month

[MM3-users] Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/2/20 8:10 AM, Mohsen Masoudfar wrote: > > This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? You can't upgrade Postorius alone in any configuration because the latest Postorius requires recent Mailman core, mailmanclient and django-mailman3. Depending on how the Debian/Ubuntu package installs these things, it may be possible to upgrade them with pip3, but as I don't know the details of how they are installed in this package, I can't say how to do this. -- 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: ERROR sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name xxxx to address

by Mark Sapiro

On 3/2/23 14:03, o.mankewitz(a)gmail.com wrote: > > This is the part of mailman.cfg: > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgresql://mailman:<mypassword>@localhost/mailman > Full error: > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name "assword>@localhost" to address: Name or service not known Do you have literally `<mypassword>` in `url: postgresql://mailman:<mypassword>@localhost/mailman` `<mypassword>` needs to be replaced with the actual password for the postgress `mailman` user. I.e. the password you provided when you did `CREATE USER mailman WITH PASSWORD 'secure-password';` in postgres (and hopefully didn't set it to literally `secure-password`). -- 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: new list not working

by Mark Sapiro

On 3/9/23 08:51, Christian via Mailman-users wrote: > I created a new list using via the form. I sent a test message to the new > list and it appears in the list archive. However I am not receiving the > distribution. > > What should I check for please? Does the list have members, i.e. actual members, not just owners and moderators, and do the members have Delivery status Enabled and Delivery mode Regular. If those show as '-----' in list based preferences, then the address based preferences if any or the global preferences apply. Also check Mailman's var/logs/mailman.log for errors resulting in shunted messages or other messages about the disposition of this 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, 4 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Stephen J. Turnbull

Mark Sapiro writes: > 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. I understand that's what we currently do. But I think that when the MUA provides an empty plain text part and a non-null HTML part, that's a mark of lazy MUA developers, not author intent. I think that it's very likely that the author would prefer the reader get converted HTML rather than a blank. Of course if the list owner wants to inhibit conversion, that's fine. But I would expect that list owners who enable conversion would also want to present a converted alternate rather than the blank plain text. Steve

6 months

[MM3-users] Re: PGP - S/MIME signed messages

by Mark Sapiro

On 7/28/25 13:29, Peter Adebahr via Mailman-users wrote: > > Hi * > > we are receiving a few PGP-signed posts as a S/MIME attachment. Some > final recipients check these, and as mailman3 does not munge them - the > original mail is signed, not mailman3's final posts - those get rejected. I don't understand. Can you expand what you mean by "the original mail is signed, not mailman3's final posts" Do you mean the post to the list is signed, but the post from the list is not? If so, what are your content filtering settings? For example, this list has in Pass Types: ``` multipart message/rfc822 text application/pgp-signature application/x-pkcs7-signature application/pkcs7-signature ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 days, 7 hours

[MM3-users] Re: Easiest way to install a new mailman3 deployment?

by Brian Carpenter

On 12/31/20 8:13 PM, ieso(a)johnwillson.com wrote: > So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time. > > I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner. > > A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test. > > The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front. > > Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?) > > Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-) > _______________________________________________ > 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/ If you are looking for commercial assistance, please visit our Mailman 3 hosting site at https://mailmanhost.com (Harmony Lists). Feel free to contact me off list if you have any questions. For us, we chose Debian 10, Postfix, Nginx, and PostgreSQL as the server environment for Mailman 3. We used PIP via a Python virtual environment to install Mailman 3 from source. The Debian packages I believe have older versions of Mailman 3/Postorius/Hyperkitty which is why we went with source. I have a walk-through that is a work in project at: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I am available to hire to install Mailman 3 for you if you want to run your own server. With Harmony Lists, we went a step further with Mailman 3 and created our own custom interfaces: Affinity (admin) and Empathy (forum/archive). However they are only available to our own Mailman 3 clients. Have a Happy New Year. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Torge Riedel

Am 07.11.20 um 02:38 schrieb Abhilash Raj: > You can install it using: > > $ pip install --upgrade mailman Hi, I like to ask what to do with other packages when upgrading mailman. I noted, that after upgrading mailman, all requirements are fulfilled, but a lot updates are available: (venv) mailman@basis2:~/core$ pip3 list --outdated Package Version Latest Type ------------------- ------- ------ ----- aiosmtpd 1.2 1.2.2 sdist alembic 1.4.2 1.4.3 wheel atpublic 1.0 2.1.1 sdist dkimpy 1.0.4 1.0.5 sdist dnspython 1.16.0 2.0.0 wheel flufl.i18n 2.0.2 3.1.3 sdist flufl.lock 3.2 5.0.3 sdist idna 2.9 2.10 wheel importlib-metadata 1.6.1 2.0.0 wheel importlib-resources 2.0.1 3.3.0 wheel passlib 1.7.2 1.7.4 wheel PyMySQL 0.9.3 0.10.1 wheel requests 2.23.0 2.25.0 wheel SQLAlchemy 1.3.17 1.3.20 wheel urllib3 1.25.9 1.26.2 wheel zipp 3.1.0 3.4.0 wheel zope.component 4.6.1 4.6.2 wheel zope.event 4.4 4.5.0 wheel zope.interface 5.1.0 5.2.0 wheel Should I update them (regularly) or may I break something in mailman? Kind regards Torge

4 years, 8 months

[MM3-users] mm3mod: command line moderation tool

by David Bremner

Because we're not running postorius, and the moderate-by-mail change is not available in the older version of mailman3 we're running, I needed a tool to moderate lists from the command line. I found mailman-tools, but wasn't able to get them working with python3, so I started from scratch. Maybe someone else will find it useful https://git.tethera.net/mm3mod.git/about/ It's a work in progress, but I am running the version from that repo in production. Like any program using the REST interface, in principle this has complete administrator access to your mailman site, so you need to to trust both this code and the users you let run it. I do run it in "kiosk mode" via ssh command="/home/listmod/.local/bin/mm3mod" ssh-rsa blahblah in .ssh/authorized_keys. This is more of a keeping-honest-people-honest kind of thing.

3 years, 11 months

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 10:17 PM, David Newman wrote: > On 11/24/21 2:36 PM, Mark Sapiro wrote: >> >> To import archives run the Django admin command with arguments >> >> hyperkitty_import -l alist(a)example.com >> /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox > > Good up to here, but ... hyperkitty_import not found. > > This wasn't covered in the venv docs: It is covered at https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy Your issue is probably that the Django admin command you ran is not accessing your `settings.py`. You may need to do ``` export DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/path/to/directory/containing/settings.py ``` before running the Django admin command. These can also be given as --settings and --pythonpath options to the Django admin command. -- 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] Mailman 3 database restore unexpected behavior

by Tibor Molnar

Mailman3 built from source using virtual environment. Version: GNU Mailman 3.3.8 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg Issue: I have restored the database number of times recently and experienced that every time after restoration (an hour after) all members getting an email that they are unsubscribed due to bounces, however non of the users are actually unsubscribed from any lists. It looks like there are duplicates in database and all the duplicates are getting unsubscribed? Bounces message: name(a)email.com unsubscribed from [listname] mailing list due to bounces Only restoring two files: mailman3 and mailman3web Did anyone come acroos this behavior ? It is not right that after restoring a database all 1000 user get an email that they are unsubscribed, but they are actually not. I may do something wrong during the restoring process. Please advise me.

2 years, 4 months

[MM3-users] Re: 404 on fresh install (Debian11)

by David Newman

On 3/28/23 5:00 PM, comprepair_jimberg--- via Mailman-users wrote: > Can you setup Mailman3 for me? I can't. But I previously provided a pointer to setup instructions using virtualenv, which is MUCH preferable to the older, buggier version packaged with Debian 11. Mark Sapiro also provided a link to a list of providers who help with setup for a fee. If it's any consolation, I practiced with test VMs about 4 or 5 times before attempting a production migration from Mailman 2. Much of my misery was caused by the initial Debian install setting the wrong ownership on some files. For that reason, things got much better when I snapshotted a brand-new Debian 11 VM and rolled back to there each time. I still made mistakes, multiple times, but at least I was no longer fighting with two installations that do things differently. dn

2 years, 4 months

[MM3-users] Re: Importing mbox file into MM3

by Mark Sapiro

On 6/22/23 7:00 PM, Mark wrote: > Hi All > > I'm trying to import a large mbox file from a MM2 list into a new list > on MM3. > > The new MM3 list has 3 test emails in its archive. > ... > The import or rebuild has failed as it's just rebuilding the existing > archive of the 3 test messages. > > What am I doing wrong? Presumably, the 3 test emails are newer than the messages in the archive .mbox. The default for hyperkitty_import is to not import messages older than the newest message in the existing archive. You need to specify something like `--since='1970-01-01'` on the hyperkitty_import command to import these older messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Hiding an ML from a site

by Mark Sapiro

On February 7, 2024 1:34:32 PM PST, Odhiambo Washington <odhiambo(a)gmail.com> wrote: >What should I do then? Edit some file? Apply some patch? >It's pretty easy for me to create a DNS record for the same server (IP) for >use with the web host that I'd like to hide. In the Domains view in postorius, you need separate mail hosts. Then you need to change the domain of one of the lists to the 'new' mail host. This implies changing its address which may not be acceptable. Or, you can just live with it as is. Note, I have been without power at my house for almost 3 days now, so I don't have access to all my usual resources. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

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 Danil Smirnov

Hi Mark, On Fri, May 24, 2024 at 11:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > 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? > I'd vote for disabling it by default and also for moving the Postorius NNTP-related settings from the "Settings - List Identity" page (the last five settings) to a separate page. Users who are born later than my generation are sometimes confused and misinterpret those settings. Once a user set "Newsgroup moderation" to "Moderated" by mistake which implicitly made the mailing list moderated too. Sincerely, Danil Smirnov

1 year, 2 months

[MM3-users] Re: "Private archives" aren't private

by Barry Warsaw

On Jul 29, 2017, at 01:33, Simon HANNA <simon.hanna(a)serve-me.info> wrote: > @abompard what's the policy on bug fix releases? > If mailman 3 should get adopted, I guess pushing such fixes quickly shows people that even if they encounter bugs, they get fixed right away... Otherwise they would just wait for it to "mature" Project-wise, the policy is that we coordinate major releases, which in this case means the second digit, much like with Python. So 3.0 and 3.1 were coordinated across all the relevant subproject. Micro/patch releases can happen at any time for subprojects. So if we need to release a Core 3.1.1, we can do that at any time. Of course it means we have to be extremely diligent not to break compatibility. We unfortunately don’t have any good integration tests to enforce this though. -Barry

7 years, 11 months

[MM3-users] Flushing/syncing hyperkitty with mailman

by Eric Abrahamsen

I've got mailman running on Ubuntu 14.04, with systemd service files to govern the mailman and hyperkitty qcluster processes. I notice in the systemctl status call for the qcluster command that there are a bunch of errors like: [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. Is there something more I should be doing to sync hyperkitty's database with mailman? I've got the crontab file in place, and that appears to be running without error. Anything else? Thanks, Eric

7 years, 2 months

[MM3-users] bouncing mail commands

by Liebeskind Uri (luri)

Hi all, when a subscribtion confirmation is sent to MM it replies a bounce mail about unknown commands in the mail. This is very confusing for the users / subscribers and I'd like to disable this function. Actually our users do not need to send commands in the subject and in the body. So responding to words that are unknown commands is not helpful. Currently I have Postfix header and body checks in place that discard this messages from MM to avoid bothering our users. But how can MM3 be configured not to respond to unknown commands or not to parse the mail for commands at all? Thank you for your help and kind regards, Uri Liebeskind -- ------------------------------------ Zurich University of Applied Sciences Information and Communication Technology Uri Liebeskind System Administrator Gertrudstrasse 15 Postfach 805 CH-8401 Winterthur Tel. +41 58 934 72 63 Fax. +41 58 935 72 63 http://www.zhaw.ch/en/ -------------------------------------

5 years, 9 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:04 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:52 PM, Odhiambo Washington wrote: > > > > Do I need to install sassc in the base OS or in the virtualenv? > > Have you checked `which sassc` to see if you don't already have it. It > doesn't matter whether it's in the base OS or the virtualenv. Things > running in the virtualenv can still access the base OS, just not vice > versa. > I install sassc, because sass installation always failed - after some upgrade. <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I remember posting about it in 2020 or 2019 :) root@gw:/usr/home/wash # which sassc /usr/local/bin/sassc -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 2 months

[MM3-users] Error on timeout vs retry values

by Robert Moody

Hi everyone, I have recently setup a new mailman3 service using the venv method. Everything is functionally working however I keep getting an error sent to the mailman email every min which I can not seem to figure out why. /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details.""" I have edited the timeout and retry values in the /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file and restarted both mailman and mailman-web however this still keeps repeating. Any ideas? Regards, Robert -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 years

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Tue, 25 Oct 2022 15:56:08 +0900 "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: > Onyeibo Oku writes: > > > This is tiring. At this moment I am left with the possibility that > > SELinux may be in the way. I cannot think of a way to prove this > > hypothesis. > > How about the obvious, disable SELinux temporarily? > To dynamically disable it before the reboot, run the following > command: # setenforce 0 > Thank you. Sure enough Systemd succeeded when SELinux was in permissive mode (ignoring series of AVCs, of course). With SELinux in Enforcing mode, we are back to our previous mileage. Conclusion: SELinux is in the way! I must be missing necessary policy modules for mailman or I am missing relevant parts of the tutorial that deals with SELinux. Where do I go from here?

2 years, 9 months

[MM3-users] Rejecting held emails

by Darren Smith

Hello, We recently had a phishing message make it through our spam filters and arrive at a mailing list. The good news is that since it was not from a list member it was in the held message queue. I was able to find the message in the var/messages directory by searching for a keyword in the subject. However, after rejecting the message from Postorius, the message doesn't seem to be removed from the var/messages directory. Is this expected behavior? I know that infosec people won't be too happy about a phishing email sitting around on our disk. (Infosec guys are notoriously paranoid. :) ) Is there some sort of cleanup process that would remove these messages? If not, does this pose an issue where over time disk usage will creep up? This could be a pretty significant problem if that is the case. What do you think, sirs? -Darren

7 years, 3 months

[MM3-users] Re: Disable user registration

by Abhilash Raj

> On Mar 20, 2021, at 11:10 AM, mailman3(a)digicrime.com wrote: > > I was looking for exactly this functionality myself this week. We have an organization of 2000 members and we wanted an independent way of controlling who can access a list. When you say “independent way of controlling who can access a list”, do you mean that even like disabling the signups or like an even more fine grained logic around who can subscribe to what list and such? Disabling signups is easy enough, I responded to a message in this thread. > In the end I decided that mailman3 was designed for something completely different than what we needed, so I've scrubbed this approach. > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: uncaught bounce messages

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > > See the thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > There is an example `mailman shell` session at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that will reenable delivery for members disabled by bounce if you think > the disables were spurious. Thanks very much for the recipe. I had been trying (and failing) to do something similar using the mailmanclient API / rest client. Does anyone happen to have a working example of updating user preferences via mailmanclient? I did call save(), after setting preferences['delivery_status']='enabled', but that seemed to not be enough. If no-one has a working example I can try to reconstruct a more precise reproducer. d P.S. I wonder if it would be worth collecting some of these recipes on the list as examples in the documentation?

3 years, 9 months

[MM3-users] Re: A poll: "Delete this thread"

by Jeremy Stanley

On 2024-06-19 15:29:36 -0000 (-0000), Sam Darwin wrote: > If you have a locally installed mailman3 instance, could you try > (as an administrator) to visit a thread in Hyperkitty and click > "Delete this thread"? Does the thread get deleted, and you return > to "Recently active discussions" and everything is fine? > > Even just a few replies would indicate a pattern. That it's > usually ok, for example. > > I get a spinning wheel, and "Thread matching query does not > exist." HyperKitty==1.3.9, PostgreSQL, Ubuntu 22.04, memcached, > gunicorn. I do it semi-regularly with the latest MM3 suite and it works normally for me, though the instance I manage is a container deployment built from Abhilash's Dockerfiles with (MariaDB backend and Apache reverse-proxying to a UWSGI URL on the loopback). -- Jeremy Stanley

1 year, 1 month

[MM3-users] Re: Hyperkitty - not sending from GUI & reply-thread

by Mark Sapiro

On 1/7/20 6:46 PM, sunil soprey wrote: > With latest release (HK 1.3.1), does anyone have an issue with no emails from reply-thread? I able to send/receive emails to/from mailman. I see MTA delivered emails, just no emails from HK GUI. If you look in Mailman's logs/access.log or in your web server logs do you see an entry like "POST /archives/list/LIST_ADDRESS/message/MESSAGE_HASH/reply HTTP/1.1" 200 ... Or maybe it's "POST /hyperkitty/list/LIST_ADDRESS/message/MESSAGE_HASH/reply HTTP/1.1" 200 ... Where LIST_ADDRESS is like list@domain and MESSAGE_HASH is the hash if the message-id that you're replying to. If it's there and the status is not 200, is there something in error.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] How to stop minutely mails about readme_renderer

by Stephen J. Turnbull

Axel Rau writes: > /usr/local/py_venv/mailman_33/lib/python3.9/site-packages/readme_renderer/markdown.py:44: > UserWarning: Markdown renderers are not available. Install > 'readme_renderer[md]' to enable Markdown rendering. > warnings.warn(_EXTRA_WARNING) > > I installed cmarkgfm 0.8.0 in my venv, Why did you do that? Is it something in our documentation? The error message is specifically asking for readme_renderer, which is a package available from PyPI. Try installing that. I'm not sure what the "[md]" means (the suffix "[md]" is also in postorius/setup.py), but it probably doesn't matter since readme_renderer.markdown is imported directly by Postorius. Just installing the package should make Postorius happy. Note that something is not right because running setup.py in the venv should automatically install readme_renderer, and I would expect you may have other problems if setup.py did not work correctly.

3 years, 2 months

[MM3-users] Re: Database running VERY hot

by C. R. Oldham

Greetings, > However, I still see where the database at times can run VERY hot. > > We have set up this server to run with PostgreSQL. When I do a ps aux > | > grep postgres, I find a lot of processes that have been spawned to > take > care of mailman - a dozen or so. Out of the box Pg performs pretty well but still benefits from tuning. Recommend you head over to https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server and see what makes sense for your configuration. Anectodally, at my work we produce an app with Pg as the backend database. Simple tuning, including turning `synchronous_commit` off, yielded us 10x better performance. Granted, our app is very write-heavy and typically Mailman and friends will be far more read-heavy, so giving Pg enough RAM for in-memory sorts and caching will benefit you more. --cro

7 years, 4 months

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Odhiambo Washington

On Tue, Oct 1, 2024 at 12:36 PM Chupin Maxime via Mailman-users < mailman-users(a)mailman3.org> wrote: > Mark Sapiro wrote: > > Did you run this as the Mailman user (list in the Debian packages)? > > Thank you, I tried, but the system asked me a Password for this user... I > do not understand. > > ``` > sudo -u list mailman-web makemigrations --merge > Password: > ``` > The user executing `sudo` is yourself so enter your own password. It's not the password for user "list" that is wanted. It's your own login password. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

10 months

[MM3-users] Re: Unable to ban users via mailman-shell

by Mihai Moldovan

* On 4/13/25 14:43, Mihai Moldovan wrote: > I can't seem to be able to add bans via mailman-shell: What I haven't tested before, but should have done: I can, however, add new bans from Postorius (the web interface) and immediately query them via mailman-shell: >>> for ban in bans: ... print('{0}: {1}'.format(ban.list_id,ban.email)) ... x2go-commits.lists.x2go.org: x(a)y.z Obviously, requests via Postorius also go through the REST API via a POST request, as I'd expect, and are immediately committed to the database (I've checked it by directly opening with SQLite3). I'm quite stumped why the shell interface doesn't commit the data to the DB. Unfortunately, the web interface doesn't allow mass-adding addresses, which is why I wanted to do that via the shell. Mihai

3 months, 2 weeks

[MM3-users] Re: changing adverstised status

by Abhilash Raj

On Wed, Aug 22, 2018, at 1:27 AM, Alexander Klotz wrote: > Hi there, > > we are trying to set a once public list to private but have trouble > doing so. In Postorius this doesn't seem to work - you can change "show > list on index page" via the settings, but the value isn't saved. Is > there a way to set advertised = False to a specific list via the shell? Could be related to https://gitlab.com/mailman/postorius/merge_requests/352 The behavior of some of our boolean fields changed with newer releases of Django, but it has been fixed in master branch. > > Thanks & Regards, > Alex > > (Kulturserver editorial staff) > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

6 years, 11 months

[MM3-users] Re: Basic settings for a discussion list

by paul＠arenson.org

OK. Using 2 other emails I found the difference between the short form sign up and the actual subscription. The actual subscription allows one to see the archives and post from the web. The short form does not allow that, but you can post from your email. The way it reads is a bit confusing: 1) Subscription / Unsubscription To subscribe or unsubscribe from this list, please log in first. 2) You can also subscribe without creating an account. It is not clear that in the former case you can use the web interface and n the latter you cannot until/unless if you later go back and do that. I would suggest using "To subscribe and be able to see the archives as well as post from there..".for #1 and To subscribe to receive and post via email only (not as convenient) for #2

5 years, 11 months

[MM3-users] Re: Hyperkitty stuck files

by Odhiambo Washington

On Wed, Jul 10, 2024 at 4:55 PM <zoltan(a)circle-interactive.co.uk> wrote: > Thank you again for the OPTIONS > > I do not have errors in log any more and I had 273 stuck mails which are > gone now. > > Can this maybe be added to the installation guide? > https://docs.mailman3.org/en/latest/install/virtualenv.html > Since that official HOWTO only focuses more on PostgreSQL than MySQL, there are so many bits about MySQL that aren't mentioned there, For example, there's no mention of "mysqlclient|pymysql". Maybe those using MySQL as the DB backend need to figure out those :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year

[MM3-users] Re: Slow and out-of-sequence delivery

by Mark Sapiro

On 12/16/22 13:18, Gregg Roberts wrote: > > Messages that I post to the forum have been taking as long as 48 hours > to come back to me. The issue is not new and AFAIK no one has been > messing with the settings. But the issue seems to have been becoming > more and more severe in recent weeks. This is a symptom of a backlogged out queue in Mailman. > Perhaps because of such delays, I also sometimes see responses to other > posts before I see the original post. It takes extra time to understand > the context when that happens. People's time gets wasted answering > questions that have already been answered without their knowledge. It's > just frustrating all around. > > The email address from which messages are sent is not in the list of > email addresses maintained in the hosting account cPanel. There seems to > be one by the name "relay" that is being used by Mailman. > > I actually don't know which version of Mailman is installed. I'm hoping > it's the more recent of the two options so I optimistically joined this > particular list. The Mailman provided with cPanel is Mailman 2.1, not Mailman 3. > The hosting service tech support can't help because they can't see the > forum email address or its logs. At least that's what they say. The hosting service only offers Mailman because it is part of cPanel. Unfortunately this is true of many cPanel based hosting services. They offer Mailman but are incompetent to support it. Your issue is a symptom of a backlogged out queue and it probably has nothing to do with your list. There will be only one Mailman instance on the cPanel host machine and it will be delivering messages for all the lists on all the virtual hosts supported by that machine. There are threads in the archives on the backlogged out queue issue, e.g. <https://mail.python.org/archives/list/mailman-users@python.org/thread/QGVWW…> and <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. There is also a FAQ article at <https://wiki.list.org/x/17892002>. > A contract tech support guy has suggested that it might solve a problem > if we started spending $100-$150 per month on a dedicated server. I > think that is a wrongheaded suggestion. If the organization had > thousands of members, it would make more sense. But throwing money at > the problem if something is simply not set up right, or some critical > file is corrupted, is not the right solution. Set the broken bone > correctly first, THEN inject stimulants and send the player back out > onto the field. :-) A dedicated server might help, but probably only because it would remove you from the impact of Mailman lists from other vhosts on the shared server. There are things the host can do to improve the situation, but only if they are competent in tuning Mailman and the outgoing MTA. If they are willing to work on this, they are welcome to post to mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/> and we will try to help, but you are at their mercy to fix this and your only recourse is to look for a different hosting service. If it's only for Mailman lists, see <https://wiki.list.org/COM/Mailman%20hosting%20services>. -- 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: Importing config and archives only partially succeeded?

by Mark Sapiro

On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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: Django administration - User permissions

by Mark Sapiro

On 5/29/24 11:18 AM, advorkin(a)cs.princeton.edu wrote: > > So, just to be clear, in order for someone to have an ability to create/delete a mailing list, they must be a superuser? The reason I'm asking is for security purposes and making sure that specific user has only minimal access. Currently that's true. It should be possible for a domain owner to create a list in that domain, but currently I don't think it is. > What are those Django permissions for...? Is there a use for them? Those permissions correspond to database tables, and I think they allow actions on those tables through the django admin UI. They do not (currently at least) allow any Postorius or HyperKitty UI actions. -- 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] An issue with the postfix_domains directory creation and the mailman start command.

by Keith Christian

From Mark's reply of Jul 5, 2024, 3:18 PM: RE: The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. 1 [mailman3@somehost ~]$ ./venv/bin/mailman start 2 Starting Mailman's master runner 3 Generating MTA alias maps 4 [mailman3@somehost ~]$ sudo ls -l /opt/mailman3/mm/var/data/postfix_domains 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': No such file or directory 6 [mailman3@somehost ~]$ ls -dl /opt/mailman3/mm/var/data/ 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 /opt/mailman3/mm/var/data/ What should I do about lines 4-7? Thought it might be a permissions issue but it's owned by the correct user. Not sure that i missed any steps, suggestions appreciated.

1 year

[MM3-users] Re: Create a mailman-web admin user

by Roland Giesler

On 2024/07/30 19:13, Mark Sapiro wrote: > On 7/30/24 08:55, Roland Giesler via Mailman-users wrote: >> >> I use Linux LXC containers mostly in Proxmox, so adding another layer >> by using docker or something else to mean seems like another layer of >> complication. >> >> The documentation is obviously good enough for people that know how >> already, but need to look up a detail here or, but for a first time >> mailman user it is a bit of a nightmare. Once I have chewed my way >> through all the traps and tunnels, I intend to do something about >> this. I can't contribute to code here, but I can make it easier for >> the next person coming along. > > > Please see https://wiki.list.org/x/12812344 Point taken, Mark.

1 year

[MM3-users] Re: Announce Only List

by Mark Sapiro

On 8/14/20 12:40 PM, Allan Hansen wrote: > I set the Default action to take when a member posts to the list to ‘Discard.’ > and set the Moderation option for the few allowed posters to ‘Accept immediately (bypass other rules). Which works until someone who wants to post to or spam the list realizes that all they need to do is spoof the From: address to be one of the addresses that sent posts that they received. A more secore, but more tedious solution is to set the authorized poster's moderation action to hold and then approve valid posts. Or leave everyone's moderation action at list default and post with an Approved: <password> (pseodo)header. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…>. -- 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] How can I allow members of list A to post to List B and vice versa

by mario.mailman3＠frese.online

Hi, I am trying to setup Mailman3 for our school. There I have several groups (teachers, parents) that have their own mailling lists. But it also should be possible that the parents can sent mails to the teachers list and vice versa. The manual management via the non-members list will be very inconvenient and the command-line options that I saw so far do not include the import of non-members (mailman syncmembers and mailman addmembers). The best option I would like to have is to enter the name of List A in the non-members of List B an vice versa. All those nonmembers should not need to be moderated. How can I manage this? I would be very glad for your ideas. Best Mario

4 years, 8 months

[MM3-users] postorius / adjusted settings menu

by Andreas Barth

Hi together, I want to adjust the settings menu to reduce to the options really needed. The easiest way would be to edit src/postorius/views/list* but I don't think that's a good idea. So what comes to my mind is to have some variable in the configuration that contains the menu items and - if set - the submenus. E.g. the following: { 'list_identity': ['!gateway_to_mail', '!gateway_to_news', '!linked_newsgroup', '!newsgroup_moderation', '!nntp_prefix_subject_too' ], 'automatic_responses', 'alter_messages', 'dmarc_mitigations', 'digest', 'message_acceptance', 'archiving', 'subscription_policy', 'bounce_processing' } would express: default menu and just remove the mentioned items. Of course, something like ['advertised', 'description', 'info', 'display_name', 'subject_prefix'] would work as well. Resorting should also be possible, so something like { 'list_identity': ['advertised', 'description', 'info', 'personalize'] } would give a very small list of items to select from. What do you think about the idea? Andi

4 years, 4 months

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Mark Sapiro

On 12/21/21 4:42 PM, dancab(a)caltech.edu wrote: > > I'm considering the settings below for gunicorn.cfg > > [gunicorn] > OK > # No of seconds to wait before killing the worker processes. > graceful_timeout = 600 I don't think this is relevant. It only affects the delay before killing a worker when gunicorn is restarted, but I suppose it won't hurt. > # Timeout for the requests. > timeout = 900 I wonder if this is really the issue. Do you have tracebacks from these timeouts? I think there may be something else causing this that increasing the timeout won't solve. Maybe some database locking deadlock or similar 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, 7 months

[MM3-users] Re: hyperkitty_import Unicode Errors

by Andreas Schamanek

On Mon, 8 May 2023, at 15:21, Dave Hall via Mailman-users wrote: > I did check my MariaDB (as Mark hinted) and found that it set for > utf8 rather than utf8mb4. I'd be willing to change this, but would > I also have to do something to update the Mailman databases since > those tables are already created? I found this mentioned in a post by thoralf from 2020. Quoting from https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> I've checked - database, table and columns were utf8mb4 already, >>> whereas the connection to the db apparently not. Adding 'charset': >>> 'utf8mb4' to the options-dict in the databases-variable in >>> /etc/mailman3/mailman-web.py fixed the issue - django passes this >>> on to mysqlclient. case closed :) I can confirm this (running MM3 on Debian 11). -- -- Andreas :-)

2 years, 2 months

[MM3-users] Re: Migrating from mailman-suite to mailman-web

by Mark Sapiro

On 6/4/22 09:09, Andrew Hodgson wrote: > Hi. > > Any pointers in migrating from Mailman-suite to Mailman-web? I'm interested specifically in configuration changes required to Gunicorn in order to bring up the Django project using Mailman-web. mailman-suite is really just an example containing a Django settings file and urls.py and wsgi.py. mailman-web is a package which installs Mailman's web UI including HyperKitty and Postorius. Neither of these addresses the wsgi server per se. It could be Gunicorn, uWSGI, Apache mod_wsgi or possibly something else. Apparently you are using Gunicorn and want to continue to do so. I think the only required changes to Gunicorn might be file system paths. What specifically are you concerned about? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Question: What happens if I delete a user from all lists and that user is sole owner of some list?

by David Partain

On Wed, 2024-04-03 at 15:14 +0300, Odhiambo Washington wrote: > > My question is: If one of these users is the sole owner of a list, what > > will happen? Will the user be deleted and that list now owner-less? > > Will mailman refuse to delete that user until I add a new owner? > > > > Thanks in advance for your feedback. > > 1. Create a testlist > 2. Assign an owner to it > 3. Delete the owner via the CLI or Postorius > > Give us your feedback :) I'll happily do so, and thanks for the idea. Try stuff, David! Cheers, Daudi Mwisho, as my mom liked to call me

1 year, 3 months

[MM3-users] Re: Create a mailman-web admin user

by Mark Sapiro

On 7/30/24 08:55, Roland Giesler via Mailman-users wrote: > > I use Linux LXC containers mostly in Proxmox, so adding another layer by > using docker or something else to mean seems like another layer of > complication. > > The documentation is obviously good enough for people that know how > already, but need to look up a detail here or, but for a first time > mailman user it is a bit of a nightmare. Once I have chewed my way > through all the traps and tunnels, I intend to do something about this. > I can't contribute to code here, but I can make it easier for the next > person coming along. Please 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

1 year

[MM3-users] Re: Docker, Mailman 3, templates and list user accounts

by Henrik Rasmussen

Hi >> 2) How do I change the site name in the top of the web interface on >> Mailman 3 to my subside and ? > >Abhilash Raj wrote: >For now, you should just login into the admin interface at /admin/ and >just create a new Site model. And then use the id of that Site in your >Django's settings.py. Each domain that you add gets their own id and >depending on which domain you are serving from, you can set the SITE_ID >in the settings. Mailman 3 supports multiple domains at the same time. Is the admin login the same ser as created by "docker exec -it mailman-web python manage.py createsuperuser"? And since I don't recall whether I actually created a superuser, will it break anything if I run createsuperuser again? Henrik Rasmussen

7 years, 11 months

[MM3-users] Re: Sad news - Brian Carpenter

by Odhiambo Washington

On Wed, May 12, 2021 at 10:45 PM <smorytko(a)gmail.com> wrote: > > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry > from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was > hospitalized with Covid. > I have known Brian for many years mainly from the Mailman lists and he was a great resource. For a while now I have been meaning to check on the HOWTO he was writing for installing Mailm3 on Debian and yesterday I actually wanted to check on it. What a sad turn of events. May his soul rest in peace. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 2 months

[MM3-users] Re: configuring postfix local recipient table

by Stephen J. Turnbull

Alexander Inzinger-Zrock via Mailman-users writes: > + also checked that command ''postmap'' (under /usr/sbin) is available > for user 'mailman' (usr/sbin was not in path; it is now). This should not matter since the full path is in postfix.cfg, so Mailman should find it and run it unless there is some permissions problem or the executable itself is broken, regardless of PATH. You've probably run all these pretty recently, but if you've made any changes since then: What is the output of the "mailman lists" command? (expect the test list with domain) What is the output of the "mailman aliases" command? (expect none) After "mailman aliases" do you get aliases in the postfix_lmtp file? -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months

[Test] mailman-users@mailman3.org

by Mark Sapiro

The subject list exists and I think is configured appropriately. It is currently unadvertised. I am ready to advertise it and announce it. I have both Google and Facebook OAuth2 login working and advertised along with Persona on the login page. I have removed Yahoo from the login page because we don't yet have DMARC mitigations and I don't want to encourage Yahoo addresses. Twitter OAuth2 almost works, but it doesn't return email address. Rumor has it you can't get email from Twitter, so it can't work. Things that need to be fixed soon in core are confirmation required for email unsubscribe <https://gitlab.com/mailman/mailman/issues/213> and DMARC mitigations, but I think we can open it up and announce it. If no one objects, I'll do that tomorrow. -- 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: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 18:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 01/23/2018 08:54 AM, Thor Atle Rustad wrote: > > > What I called "local admin" should have > > rights to add and remove members of, say, the poodle-regionA mailing > list. > > > By "local admin", do you mean "list owner", i.e., a list owner should be > able to see her own "hidden" lists. > > Is that what you mean, or to you envision some new category of user that > has more access than a list owner? > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > I mean "list owner"

7 years, 6 months

[MM3-users] Null sender?

by tom＠gather.coop

Does Mailman generally send email with a null sender? This is what I see in the log: Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) handling connection Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'LHLO mail.example.coop' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'MAIL FROM:<>' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) sender: <> Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'RCPT TO:<techque-bounces(a)example.org>' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) recip: techque-bounces(a)example.org Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'DATA' Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'QUIT' Notice the empty MAIL FROM. Sendgrid seems to be choking on that because it needs to check if sending domain has been validated. If there is no sending domain it seems to reject. Why does Mailman do this? Can it be changed? I've been trying to find the relevant section of the code to no avail.

5 years, 1 month

[MM3-users] Re: How to modify system preferences

by Mark Sapiro

On 2/19/21 5:15 AM, Jack Lenox via Mailman-users wrote: > > The documentation states that these are only accessible in a read-only > format via the REST API, but presumably there is a way of modifying > these somewhere? I can't find a way of specifying this in my config and > can't find a relevant example in the sample schema.cfg. > > At this stage, all I want to do is set the default for > "receive_own_postings" to False. Can anyone point me in the right > direction here? The defaults for settings like this are not directly configurable. You need to patch the relevant entry in mailman/core/constants.py I have just filed <https://gitlab.com/mailman/mailman/-/issues/832> for this. -- 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: Replace "visit your dashboard" with URL link, like in Mailman 2.

by Jens Günther

We expanded it like that: list:admin:action:post.txt ------------------- Your approval as administrator for the following Mailinglist is requested: list: $list_id The message has been held for the following reasons: $reasons Please visit the following dashboard to approve or discard the message: https://$domain/postorius/lists/$short_listname.$domain/held_messages ------------------ Am 08.05.23 um 18:52 schrieb Mark London via Mailman-users: > Has anybody attempted to change the format of the emails that are sent > to the owner of a mailing list, to include a URL, instead of stating > "visit your dashboard"? The former is the behavior of Mailman 2. > > Is there any reason why this can't be done? If nobody has tried to do > so yet, I'll give it a try myself, as I'm familiar with django. Thanks. > - Mark

2 years, 2 months

[MM3-users] Re: Add domain to Mailman, can't create list with that new domain

by Andy Matthews

Greetings Odhiambo, thanks for your response. I personally don't use Postorius, and I'm not even sure anyone on our team is using it. A quick search of all our repositories shows only a single mention, back in 2017. A member of my team uses hand-written Python scripts to do much of the configuration, which is why I'm slowly trying to convert everything over to using the REST API. As to your comment about not understanding my question. I basically want to add a domain to our Mailman installation, or to set a different primary for different environments, so that I can create mailing lists against those other domains. mydomain.com <- primary in production and local development staging.mydomain.dev <- I want this to become primary in our staging environment.

9 months, 2 weeks

[MM3-users] Re: required cron entries?

by Mark Sapiro

On 1/1/21 12:17 AM, Andreas Barth wrote: > > In my case, this was however > Uncaught runner exception: (raised as a result of Query-invoked > autoflush; consider using a session.no_autoflush block if this flush > is occurring prematurely) (sqlite3.OperationalError) database is > locked [SQL: 'UPDATE mailinglist SET last_post_at=?, post_id=? WHERE > mailinglist.id = ?'] [parameters: ('2020-12-23 10:18:41.030593', 10, > 11)] (Background on this error at: http://sqlalche.me/e/e3q8 > > > The 'fix' for that was turning it off and on again (i.e. rebooting the > VM), but now I have a few messages around. Do you mean you have messages in the shunt queue that were shunted because of this error? If so, just running Mailman's `mailman unshunt` command should reprocess and deliver those. -- 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: Race condition when mass subscribing same email addresses to two lists?

by Alan So

Stephen J. Turnbull wrote: > I guess we should catch the error and retry. Raising and handling > exceptions in Python is relatively slow, so even in your well > constructed worst case, this shouldn't happen on every address, so I > don't think having a separate queue or putting the whole thing in a > transaction would be better. If you still have the log, I'd be > curious to know how many unique errors you got. > I need to do other work for the next 48 hours, but a patch would be > very welcome. I don't know offhand where this code lives, sorry. > Steve For this case, there are 837 unique errors. Verified with the number of members of the two lists: 576 & 587 576 + 587 + 837 = 1000 * 2

3 years, 9 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 18:35, Mark Sapiro wrote: > > $ django_admin shell > >>> from django.contrib.sites.models import Site > >>> new_site = Site(id=5, domain='5.example.com', name='display_name') > >>> new_site.save() > > Of course the values are up to you and you can omit the id= to have > Django assign the first available.. Also note that the above is a django_admin shell interaction. You can also do this in python, but you need to precede the above with ``` >>> import os >>> import sys >>> sys.path.insert(0, '/path/to/directory/containing/settings.py') >>> os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' >>> import django >>> django.setup() ``` -- 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: Sendgrid experiences

by Stephen J Turnbull

2023-05-10 03:49 に Andrew Hodgson wrote: > Sendgrid is maintaining the Message-Id header which is good for > archiving. It is re-writing the Return-Path header though which means > that bounce handling in Mailman won't work, but I think all the > services do this in some way so I am happy to live with that for the > moment. How does it rewrite the Return-Path? Returned mail is not something that such a service would be able to handle properly (although they can help with apparently returned spam). If mail is legitmately sent and returned as undeliverable, only the author or their agent will know how to handle it. So such services should provide some way to find out about returned mail. -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

2 years, 2 months

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

by Mark Sapiro

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

7 years, 4 months

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

by Mark Sapiro

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

6 years, 6 months

[MM3-users] Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Odhiambo Washington writes: > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > > only thing I can think of is an Apache rewrite rule. It's not in the > > Postorius and HyperKitty templates. > > And I do not have any rewrite rules in my VHOST config: > > https://pastebin.ubuntu.com/p/9MRMJST9zZ/ Is there a mod_wsgi.conf file? I've never seen this "mysterious" insertion of "/mailman3" in URLs. I'm trying to imagine where mod_wsgi would get it from, and just can't think of why that would be in mod_wsgi or its .load or .conf files in the Apache config. The maintainable place for URL configuration is the main apache.conf or a site-specific include file such as sites-available/mailman.conf. I guess it could be in an instance-specific configuration file or stanza of uwsgi to create a namespace. Steve

2 years, 7 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Fri, Dec 30, 2022 at 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/30/22 03:12, Odhiambo Washington wrote: > > On Thu, Dec 29, 2022 at 10:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Try adding lists.kictanet.or.ke to Chosen sites along with > >> mm3-lists.kictanet.or.ke > > > > > > Even with that added, still same error. > > > Did you run `django-admin migrate` after uncommenting > 'allauth.socialaccount.providers.twitter', in your settings? > I always do whenever I change anything in settings. (venv) [mailman@gw ~/mm]$ /opt/mailman/mm/bin/django-admin migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. (venv) [mailman@gw ~/mm]$ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Multiple server replicas

by Dave Hall

Hello. Our Mailman 2.1 setup included 4 replica servers, all with Mailman, Exim4, Apache, etc. The configuration for the 4 mailman server instances were synchronized by linking most of the directories in /var/lib/mailman to an NFS share that is mounted on all 4 servers. Cron jobs were staggered such that an hourly job would run every 4 hours on each server, yet still get run hourly. With Mailman 3 we would like to keep the same kind of setup. However, things have changed quite a bit. Having both mailman and mailman-web instances all share their respective MySql/MariaDB databases is the easy part. For /var/lib/mailman3 it is a little less clear. So far I have symlinked messages, archives, lists, data, and templates onto the NFS share. I'm wondering about cache, locks, queue, and web/fulltext_index. Is there any standard or documented way of doing this? Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 years, 2 months

[MM3-users] mailman import21 passwords

by Sam Darwin

Hi, On https://docs.mailman3.org/en/latest/faq-migration.html it says "Mailman 3 has a completely new account management system, none of the passwords from Mailman 2 will work with Mailman 3. Each user needs to sign up in Postorius for a new account to manage their memberships on all lists on a single instance." "Each user needs to sign up in Postorius for a new account" I am (personally) satisfied with this answer. However others at the company are asking for a detailed explanation. Consider that - - Mailman2 has access to password information. - Import scripts such as "import21" are able to import list information. - It seems that scripts such as "import21" could also generate new user accounts and passwords based on the previous ones. Why can't passwords be imported from mailman2 to mailman3? How difficult would it be to do? (is there a link to where this is already explained? ) Thanks

10 months, 2 weeks

[MM3-users] Re: Question after upgrade to mm 3.2.3 and latest postorius

by Abhilash Raj

On Sun, Aug 11, 2019, at 12:43 PM, David Krantz wrote: > Hi all, > > I have just upgraded to mailman 3.2.3. My installation is from the git > sources and I use two different venv:s, one for the web part as I did > not want to compile the web server plugin to a newer python version > than 3.5, and one venv for the rest running python 3.7. Apart from > some missing dependencies and some changes that affected the django > config I just have two issues with postorius: I would recommend that you bump up to 3.7 for the web part too, mostly because 3.5 is now has been in security maintenance state for a while. We will drop support for 3.5 after this next release (so you do have some time :), but I fear there *could* potentially be other dependent libraries who might have dropped 3.5 support. Even though we do run CI and we'd (hopefully) know when there is a dependent library seriously breaking, but since we don't pin down versions, newer releases can cause problems. The web-server plugin I assume is mod_wsgi? If you use a separate wsgi server than the one embedded in web-server, you can bump versions a bit more easily. gunicorn or uwsgi are recommended options. Do note that the new version of Mailman Core also uses gunicorn now. > > 1. The index page with all lists is not sorted in any useful way > although it is based on something as the order seems to be stable. > Prior to the upgrade the lists were sorted in alphabetical order after > list name which is a lot more usable for me as admin. If I click the > link at the bottom with "click to view all lists" I get the old > behaviour. This change was made so that you will see only the lists you are a member of either as a subscriber, moderator or owner. This is default when you are logged-in, but when logged-out, you will see the old view with all lists alphabetically sorted. > 2. The template menu simply does not work, it seems as if some > database table is missing even after running migrations. Are you sure the migrations are there? I can see the following list on the latest git master of Postorius (all the ones after 0004_ are related to emailtemplate): ``` $ python manage.py showmigrations <snip> postorius [X] 0001_initial [X] 0002_auto_20160210_0721 [X] 0003_drop_addressconfirmationprofile [X] 0004_create_email_template [X] 0005_auto_20180707_1107 [X] 0006_auto_20180711_1359 [X] 0007_auto_20180712_0536 [X] 0008_auto_20190310_0717 [X] 0009_auto_20190508_1604 <snip> ``` > Django logs > the following: > > ERROR 2019-08-11 20:58:55,038 exception 11837 139756347221760 Internal > Server Error: /mailman3/lists/TESTLIST/templates Traceback > (most recent call last): File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) > psycopg2.errors.UndefinedTable: relation "postorius_emailtemplate" > does not exist LINE 1: ...ext", "postorius_emailtemplate"."identifier" > FROM "postorius.. > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/exception.py", > line 35, in inner response = get_response(request) File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", > line 158, in _get_response response = > self.process_exception_by_middleware(e, request) File > "/...VENV3.5/lib/python3.5/site-packages/django/core/handlers/base.py", > line 156, in _get_response response = response.render() File > "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", > line 106, in render self.content = self.rendered_content File > "/...VENV3.5/lib/python3.5/site-packages/django/template/response.py", > line 83, in rendered_content content = template.render(context, > self._request) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/backends/django.py", > line 61, in render return self.template.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 175, in render return self._render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 167, in _render return self.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit = node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", > line 155, in render return compiled_parent._render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 167, in _render return self.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit = node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/loader_tags.py", > line 67, in render result = block.nodelist.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 943, in render bit = node.render_annotated(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/base.py", > line 910, in render_annotated return self.render(context) File > "/...VENV3.5/lib/python3.5/site-packages/django/template/defaulttags.py", > line 313, in render if match: File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 276, in __bool__ self._fetch_all() File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 1179, in _fetch_all self._result_cache = > list(self._iterable_class(self)) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/query.py", > line 54, in __iter__ results = > compiler.execute_sql(chunked_fetch=self.chunked_fetch, > chunk_size=self.chunk_size) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/models/sql/compiler.py", > line 1063, in execute_sql cursor.execute(sql, params) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 68, in execute return self._execute_with_wrappers(sql, params, > many=False, executor=self._execute) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 77, in _execute_with_wrappers return executor(sql, params, > many, context) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) File > "/...VENV3.5/lib/python3.5/site-packages/django/db/utils.py", line > 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from > exc_value File > "/...VENV3.5/lib/python3.5/site-packages/django/db/backends/utils.py", > line 85, in _execute return self.cursor.execute(sql, params) > django.db.utils.ProgrammingError: relation "postorius_emailtemplate" > does not exist LINE 1: ...ext", > "postorius_emailtemplate"."identifier" FROM "postorius... > > Cheers > // David > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 11 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:06 PM, Mark Sapiro wrote: > On 11/11/20 2:11 PM, Brian Carpenter wrote: >> This happened again. Is there a way to get HK to deal with such messages automatically? > > How would you like them dealt with? The issue is in mailman-hyperkitty. > When it's attempt to archive the message returns an error, it queues the > message for retry. It is not clear if any of these errors are actually > retryable - for sure some aren't but maybe others like HyperKitty not > responding are - but even if we think retry won't succeed what would you > like done with the message? > Some sort of auto-discard procedure after a number of retries? Is it possible to detect a message with a null characters and automatically discard them? Do such messages make it into the thread table? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: disable body transcoding

by Markus Schaaf

Am 23.09.21 um 10:08 schrieb Stephen J. Turnbull: > Markus Schaaf writes: > > > Nothing broke, but it didn't work either. I'm a bit surprised > > that mailman3 was designed without the idea to preserve the body, > > after signatures have been a thing for at least a decade. > > Patching (including monkey-patching) the Python standard library email > package has caused headaches in the past. As you discovered, it's not > the case that a one-line patch will do the job. It's not about patching. It's understood since the early days of MIME, that you cannot recreate an encoded representation using the plain text alone. If one had planned for a feature to preserve the body, one had to keep the encoded form (or meta data to recreate it) around and inject it into the smtp sender, if that option were enabled. BR

3 years, 10 months

[MM3-users] Importing mbox file into MM3

by Mark

Hi All I'm trying to import a large mbox file from a MM2 list into a new list on MM3. The new MM3 list has 3 test emails in its archive. # cd /usr/share/mailman3-web/ # python3 manage.py hyperkitty_import -l LISTNAME@DOMAIN /home/mark/tmp/LISTNAME.mbox Importing from mbox file /home/mark/tmp/LISTNAME.mbox to LISTNAME@DOMAIN Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list LISTNAME@DOMAIN'. That all seems pretty good. Then I attempt to rebuild the archive. # python3 manage.py update_index_one_list LISTNAME@DOMAIN Indexing 3 emails The import or rebuild has failed as it's just rebuilding the existing archive of the 3 test messages. What am I doing wrong? Thanks Mark

2 years, 1 month

[MM3-users] Re: hello， Discussion on how to subscribe to themailing list

by 朱超

At 2023-01-18 13:41:56, "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: > > Yes, I know why 404 is reported，The url should be postorius not be > > mailman3, > >In the stock configuration both "mailman3" and "postorius" invoke the >same view, and I'm fairly sure several templates invoke "mailman3" >rather than "postorius". I believe the logic was that casual users >will recognize "mailman3" more readily than "postorius", and similarly >for "archive(s)" vs. "hyperkitty". ok,I got it, I use the mailman-web not is https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py, that is https://github.com/maxking/docker-mailman/blob/main/web/mailman-web/urls.py > > > https://www.example.com/postorius/lists/$list_id/confirm/?token=$token, > > and it report success. I am curious why there is no similar > > processing logic for unsubscribing in postorius。 > >I don't understand what you're suggesting. A subscribed user >necessarily has a confirmed address, and if a web administration app >is running, they can log in and with a couple of clicks unsubscribe. >Unsubscribe by mail does involve a confirmation step. As explained >before, the reply confirmation is surely available to core; if you >want I believe you can craft email templates to use the web >confirmation either as an option or the preferred method. I am thinking that we can unsubscribe in postorius without logging in. Refer to the subscription process of postorius, fill in the email address that needs to be unsubscribed on mailman-web, and send an email template to the filled email address, but the electronic template carries confirmation The url of the link, click the url to confirm and unsubscribe successfully. > > Can we optimize for this？ > >What do you mean by "optimize"? > >If you mean fewer steps for the user, I believe the FAQ explains how to >create a one-click unsubscription URL (at least that was possible with >Mailman 2). There is a mild denial of service possibility, of course, >but it doesn't involve third parties and is usually recoverable since >the unsubscribe generates an email to the "victim" who can check >archives in the majority of cases and easily resubscribe. Could you give more information about one click unsubscribe url in mailman3? > > If you use mailman-web (include postorius and django-mailman3 and > > django-allauth and so on) to set the template information, the > > template obtained by mailman-core is obtained by requesting > > mailman-web, > >No, the templates used by core and by Postorius are stored in >different databases. It's true that you can use Postorius to set >core's templates, but they're still stored in core's database, not in >Django. They *must* be, because core needs to be able to send email >even if there is no web interface at all. I suppose you could arrange >that one could be set by the other. If you want to define a protocol >so that any application that speaks the REST API can do this, I >suppose it could be added to Mailman. But we can't depend on web >administration being installed at all, and we can't depend on it being >Postorius. Yes, when mailman-web is connected to mailman-core, the core stores uri information, that is the link, not the detailed information of the template. Of course, you can read the local template file and use it by configuring related parameters. From Tom

2 years, 6 months

[MM3-users] Re: hyperkitty base_url

by Thomas Stein

After changing the api_key to something else than the default one and adjusting settings.py accordingly, everything works. Sorry for the noise. cheers t. On Friday, 4 January 2019 21:07:18 CET Thomas Stein wrote: > Hi all. > > Now I'm struggeling with configuring hyperkitty. It's not clear to me which base_url to set. Currently it's > base_url: http://localhost:8001/hyperkitty/ but that leads to > > Jan 04 21:01:39 2019 (8322) HyperKitty failure on http://localhost:8000/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> > <h1>Authorization Required</h1></body></html> (401) > > The api_key is set in /usr/share/mailman3-web/settings.py. > > I suppose I'm doing it wrong. Any hints appreciated. > > thanks and cheers > t. > > _______________________________________________ > 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/ >

6 years, 6 months

[MM3-users] Please update your Mailman installations: CVE-2019-19844

by Abhilash Raj

Hey Mailman Users, A new Django vulnerability was disclosed yesterday[1] which can lead to account hijacks via password reset emails. The fix has been released as a part of Django 3.0.1, 2.2.9, and 1.11.27. We do not support Django 3.0.1, so, please upgrade to 2.2.9 or 1.11.27, depending on which version of Mailman components you are using. If you are using a virtualenv based installation, you can install the new versions using `pip` (venv) $ pip install -U django==2.2.9 or similar for 1.11.27. You can also upgrade django-allauth to 0.41.0, which also fixes this issue[2]. I hope distro packages will soon have updated packages with the fixes. I have also published new versions of Container Images, 0.3.2 (or, 0.3) both have been updated. See more details about updating the containers here[3]. [1]: https://www.djangoproject.com/weblog/2019/dec/18/security-releases/ [2]: https://github.com/pennersr/django-allauth/blob/master/ChangeLog.rst#0410-2… -- thanks, Abhilash Raj (maxking)

5 years, 7 months

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

by Mark Sapiro

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

5 years, 5 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/29/20 8:51 AM, Brian Carpenter wrote: > > On 10/29/20 11:33 AM, Mark Sapiro wrote: >> The real question is if a user has a subscription waiting confirmation >> and the policy is changed to moderate, is a second request rejected >> because of the request waiting confirmation. If so, I think this is a >> bug which should be fixed. >> > Do you think this is a bug with Mailman core or my system? If the current policy is moderate and the user has a prior request waiting confirmation and a new request is rejected because of the prior request waiting confirmation, I think that is a bug in core, but I don't know if that is the case or not. -- 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: Message-Footer after migrating to Mailman3

by Peter Münster

On Fri, Sep 02 2022, Stephen J. Turnbull wrote: > in fact there is always the fallback of the builtin template. Ok, that makes sense. > If you think this kind of use case is really important Not important enough for changing the algorithm, I think. I just wanted to make sure, the easiest way possible, that no footer is never ever added to any message. For all lists, and for all languages. It's ok for me, to add some more empty files to the templates/site directory. > I think it would do less good (save you a few "cp <template file> > ../fr" copies) than harm (confuse people reading the docs who don't > have a use case). I agree... > -------------------------------- HERE -------------------------------- > * The template directory within the mailman source tree > <source_dir>/templates/<language> > ---------------------------------------------------------------------- Yes, I missed this one... -- Peter

2 years, 10 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Mark Sapiro

On 12/16/23 8:00 AM, eboltz(a)lhtservices.com wrote: > Installed MM3 on Debian 11, followed the steps from the MM3 website. > > I'm running into issues with Postfix headers. I can only get postfix to send emails to/from the list if I set the sender_canonical_maps in the main.cf file. I don't want to have to use that as I'd like the recipient to receive the following in their email header: <Subscriber> via <List Name> <FROM:LIST@DOMAIN>. But if I do the sender_canonical_maps, then the <FROM:LIST@DOMAIN> and all email headers are overwritten by the maps email address. In Postorius -> Settings -> DMARC Mitigations set DMARC mitigation action to Replace From: with list address and DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: anomalous behavior

by Donato Molino

On Saturday 05 October 2024, alle 08:59, Mark Sapiro wrote: > On 10/5/24 04:14, donato(a)molino.it wrote: > > Hi, > > I installed mailman-full on debian 12. > > How? Did you follow > https://docs.mailman3.org/en/latest/install/virtualenv.html or did you > install the Debian packages. If the latter, please see > https://wiki.list.org/x/12812344 Ok you're right, I'll try to contact the debian developers. In any case, I will answer your questions below > > > Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. > > I have three MLs: > > 1) example(a)example.com > > 2) test(a)example.com > > 3) hello(a)example.com > > > > For the n. 2 and 3 are fine, but 1 doesn't deliver. > > The configurations are identical for all 3: > > > > smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' > > I also enabled all debugging in mailman.cfg. > > But everything is fine > > What's in the MTA log? Does list 1 have any non-digest members with delivery > enabled > `mailman members --regular --nomail enabled example(a)example.com` No all members have regular enabled no digest. MTA log accept the message: (relay=127.0.0.1[127.0.0.1]:8024 - status=sent (250 Ok)) then HyperKitty archived message, then smtp log show the message above but does not send to recipients. > > In addition to the above in smtp.log, I would expect to see entries similar > to the following for your post to this list. me too but nothing. All other list with the same configuration are perfect. I tried also delete an recreate the list but nothing. All the lists are no moderate. in any case thank you for the work you do for the Mailman community. Donato > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 4 recips, completed in 0.31321239471435547 > seconds > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from mailman-users-owner(a)mailman3.org, 5028 bytes > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 334 recips, completed in 52.519867181777954 > seconds > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from donato(a)molino.it, 1683 bytes > ``` > (the delay between 11:15:02 and 15:22:57 above is the time between arrival > and held message approval) > > Do you see things like that? > > -- > 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 donato(a)molino.it

9 months, 3 weeks

[MM3-users] Re: Functionailty of web host domains

by Mark Sapiro

On 06/15/2018 12:37 PM, Johannes Winter wrote: > > For each domain you can specify a "web host". But when I specify a > different one than the default for one domain, and make it accessible > with specifying `DJANGO_ALLOWED_HOSTS`, all mailinglists from the other > web hosts are also shown when I access the second site. > > So does this 'web host' option have a meaning, or is it just an alias > for the first site? This is a 'site' as implemented in Django <https://docs.djangoproject.com/en/2.0/ref/contrib/sites/>. I.e., it provides ways to do different things or retrieve different content based on site, but I don't see that either Postorius or HyperKitty makes use of it in this way. -- 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: Selective mailing

by Mark Sapiro

On 2/26/19 2:39 PM, chucka(a)blackforest-co.com wrote: > I'm trying to find out if I move my web site to a hosting company > using MM Ver 3 - with SQL. If I have a membership list in MySql used by MM > - can I send an email to a select group? ["Your dues are due"]. > > Assumes the MM tables can be accessed? Anyhow what I want to do is: > send message96 where expire > next month > else > send message95 Even if The particular Mailman instance uses MySQL for its database, the tables are very specific to Mailman. It is not possible to tell Mailman that some arbitrary membership table or the result of some arbitrary query is to be used to determine the recipients of a message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Dadgar

On Nov 10, 2020, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> The downside to this is that you lose automated bounce processing, of course. > > > You don't lose bounce processing. It just becomes a bit less reliable. > The VERPed envelope sender says exactly what address the message was > sent to. Without this information, Mailman (actually flufl.bounce > <https://fluflbounce.readthedocs.io/en/latest/README.html>) has to parse > the returned bounce message to determine the bouncing address. There are > many MTAs that do not send RFC 1894 compliant DSNs and we have several > heuristic recognizers to try to parse these, but they can fail. Brian specified: verp_personalized_deliveries: no Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 8 months

[MM3-users] Re: Showing sender as ... via ... list

by Wolfgang Bock

Dear Mark, many thanks. Works! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Samstag, 6. November 2021 16:28 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Showing sender as ... via ... list On 11/6/21 4:40 AM, Wolfgang Bock via Mailman-users wrote: > > Here is my question: > > What do I have to configure to get my lists to show the sender like in > this > list: Wolfgang Bock via Mailman-users mailman-users(a)mailman3.org In Postorius go to Settings->DMARC Mitigations and set DMARC mitigation action to Replace From with list address and DMARC Mitigate unconditionally to Yes. -- 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/

3 years, 8 months

[MM3-users] Re: Missing styling on select pages

by Mark Sapiro

On 4/8/25 19:36, grodriguez(a)usra.edu wrote: > > For the most part, everything is looking good except for some select pages that do not contain the styling like all other pages. > > When a user sees the "Verify Your Email Address" screen, it's without any of the styling. > /accounts/confirm-email/ > > Same for when a user tries to reset their password. The initial screen looks good (with styling), but after entering the email address and clicking "Reset My Password", the following screen is bare. > /accounts/password/reset/done/ These and others are fixed for django-mailman3 1.3.16 (not yet released). See https://gitlab.com/mailman/django-mailman3/-/issues/84, https://gitlab.com/mailman/django-mailman3/-/issues/85, https://gitlab.com/mailman/django-mailman3/-/issues/86 and https://gitlab.com/mailman/django-mailman3/-/issues/87 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Database read only error on mailman_sync job

by Ugnius S

Hi. All the project installation is under the same user and path and working. If as owner user from project home I run: django-admin mailman_sync Traceback (most recent call last): File "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: attempt to write a readonly database "django-admin runjob sync_mailman " - makes errors as well. I did not find information how to fix this. It was worked without errors before. I guess that issue is hyperkitty database, but I even do not know the name and location of that database. Maybe it is locked. I have stopped server, killed all processes of that user and restarted mailman mailman-suite server, but this trick did not help. Please help.

5 years, 11 months

[MM3-users] Re: mailman-full question

by Dave McGuire

On 9/25/22 13:34, Mark Sapiro wrote: >> - to configure the db in venv i would use mailman-web migrate - this >> works fine - but mailman-full install does not seem to include >> mailman-web >> or mailman3-web - the mailman info cmd works fine - do i need to >> also install mailman-web? i had thought the mailman-full included all >> components > > I'm not sure what it's called in the Debian/Ubuntu mailman-full package, > but the `mailman-web` command installed by `pip install mailman-web` is > the Django admin command, possibly called `django-admin` or `manage.py` > in the mailman-full package. In my (old) Ubuntu package installation, which I got locked into before I realized how awful that was going to be, mailman-web should be symlinked to /usr/share/mailman3-web/manage.py but isn't. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 years, 10 months

[MM3-users] Re: Timeout error on anonymous subscribe

by Mark Sapiro

On 10/22/24 23:07, Gerald Vogt wrote: > > For testing I have set > > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' > > to the URL of our main domain, however, if I test an anonymous subscribe > through the list info page I still get the timeout error This will have no effect unless you delete and recreate the template in Postorius because simple changing the setting won't change the `uri` in the template table. > I can access > http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… with curl and immediately get the response. Can you do that as the Mailman user?, e.g. ``` sudo -u mailman curl http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… ``` assuming the Mailman user is `mailman`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 1 week

[MM3-users] (Email|Thread) matching query does not exist ?

by Simon Liebold

I am seeing these errors: mailman-suite_project$ python manage.py qcluster 19:27:52 [Q] INFO Q Cluster-11541 starting. 19:27:52 [Q] INFO Process-1:1 ready for work at 11546 19:27:52 [Q] INFO Process-1:2 ready for work at 11547 19:27:52 [Q] INFO Process-1 guarding cluster at 11545 19:27:52 [Q] INFO Process-1:4 pushing tasks at 11549 19:27:52 [Q] INFO Q Cluster-11541 running. 19:27:52 [Q] INFO Process-1:3 monitoring at 11548 19:27:52 [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] 19:27:52 [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] 19:27:52 [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] 19:27:52 [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. 19:27:52 [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. 19:27:52 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. Should I need to worry? I recently deleted some test emails from the archive. Don't know if this has anything to do with it. Simon

8 years, 1 month

[MM3-users] Re: Custom Archiver

by Peter Knowles

Mark, The whole reason I'm developing my own "frontend" for both "list management" and "archive" access is because Python isn't really the language I speak... I'm a PHP guy, and so I'm working to build with the language I know and love, while utilizing Mailman for what it does best... In addition to implementing the frontend the way I want it (expose/hide feature that are useful/unuseful to our users), I want to fully customize the visual appearance to represent the SaaS offering properly. *** we're not try to hide that Mailman is in the equation, just how the overall interface is visually represented *** That all being said, on a slight segway... Aside from using the REST API, is it practical or possible to manipulate the database directly? That is, in doing so would it just work or are there extra moving parts when an API request is issued?

2 years, 4 months

[MM3-users] Re: global preferences

by Mark Sapiro

Again, please don't hijack threads. Post a new topic by composing a new message to mailman-users(a)mailman3.org, not as a reply to another list message. On 5/3/23 07:59, Christian via Mailman-users wrote: > Are checks and changes to global preferences for all lists to be made via a GUI or is it editing settings.py directly please? Thank you! You can set your global preferences via Postorius (select Mailman settings from the drop-down at the right of the top nav bar). These are the settings for the user that will apply if there is no applicable list-based or address-based setting. They are specific to the user. The defaults for these are defined in mailman/core/constants.py. They are Mailman core settings and have nothing to do with Django's settings.py. -- 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: Footer question...

by Mark Sapiro

On 7/27/21 4:06 AM, David Partain via Mailman-users wrote: > > I migrated > 1200 lists from an old mailman2 installation. That brought along all of the footers (naturally), and now I'm trying to get rid of them but failing miserably. I've spent a fair bit of time reading archives of this list, but I'm still stuck. > > Here's what's configured... > > In /etc/mailman3/mailman.cfg: > > -------------------------------------------------------------------------------------------------------------------------- > var_dir: /var/lib/mailman3 > # Root directory for site-specific template override files. > template_dir: $var_dir/templates ... > Anyone have suggestions of what I can do? rm -rf /var/lib/mailman3/templates/lists/* This will allow the template search to fall back to the default. If you want to customize that, you can put custom templates in /var/lib/mailman3/templates/site/en/. -- 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 Stephen Daniel

Thanks all! On Wed, May 17, 2023 at 10:03 AM Jeremy Stanley <fungi(a)yuggoth.org> wrote: > On 2023-05-17 09:56:06 -0400 (-0400), Stephen Daniel wrote: > > Duh. I use Postfix running on the same machine as mm3 as my MTA. > [...] > > I don't use Postfix, but I asked a Web search engine (DuckDuckGo) > for "configure dkim signing in postfix" and got many informative > hits for various versions, platforms and distributions. Perhaps if > you do that you'll get similar results and can find instructions > which most closely match your deployment specifics. Best of luck! > -- > Jeremy Stanley > _______________________________________________ > 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 swd(a)pobox.com >

2 years, 2 months

[MM3-users] Re: Change config to create a new list with all archives off

by Mark Sapiro

On 4/21/24 05:39, Danil Smirnov wrote: > > What you can do is create a style in Python and make that the >> default. In $SITE_PKGS/mailman/styles/default.py, append: >> >> -------------------------------- cut here -------------------------------- >> from mailman.interfaces.archiver import ArchivePolicy >> >> @public >> @implementer(IStyle) >> class ArchivesDefaultDisabledStyle(LegacyDefaultStyle): >> >> """The legacy default style with archiving disabled.""" >> >> name = 'archives-disabled' >> description = _('Ordinary discussion mailing list style,' >> ' with archiving disabled') >> >> def apply(self, mailing_list): >> super().apply(self, mailing_list) The above line should be `super().apply(mailing_list)` >> mlist.archive_policy = ArchivePolicy.never -- 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: Filter question

by Mark Sapiro

On 2/8/25 18:14, Chris via Mailman-users wrote: > Hey Mark, > > thank you for the fast reply. > > I've added image/png and in a former test "image" (to hit all image types) > But also with image/png the image is not shown. Because the image part had a filename with a .png extension and you have Allow Extensions .zip .7z so parts with filename with other than those 2 allowed extensions will be removed. That allow extensions won't do what you want anyway because they will have mime type like application/zip and application/x-7z-compressed and you aren't allowing those. Allow extensions should not be set because if it is non-empty, any part that has a filename with an extension not in that list will be removed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 3 weeks

[MM3-users] Re: Deactivate list without deleting it?

by Barry Warsaw

On Jan 14, 2018, at 09:45, Colin Watson <cjwatson(a)ubuntu.com> wrote: > > I'm experimenting with a port of Launchpad's mailing list infrastructure > to Mailman 3. If Barry's reading, he may remember that this is no > trivial task, so I'm very definitely not promising that it will be done > any time soon. :-) For those of you not up on your history, this is interesting for several reasons. I was originally hired by Canonical 11 years ago to integrate Mailman with Launchpad. At the time Launchpad was not free software, so a lot of the design of the integration had to work within those constraints (LP was released under the AGPL in 2009 IIRC). At the time it was painful, especially because it had to keep two completely databases in sync in both directions — not an easy task! Add to that the fact that Mailman 2.1 doesn’t really have a database, just a bunch of pickle files. :) I’m proud that the mailing list feature of Launchpad eventually became pretty darn solid, with much credit to Colin, Curtis Hovey, and many of my other wonderful former colleagues on the Launchpad team and at Canonical. This experience also heavily influenced my thinking about the design for Mailman 3, and led directly to the REST-based API. Launchpad has a REST API, spearheaded by Leonard Richardson, who literally wrote the O’Reilly books on web services. And while there were some compromised on “pure” REST in Launchpad, the discussions we had at that time committed my thinking to as pure an approach as I was capable of doing. > However, for the most part it looks relatively > tractable with the aid of the plugin improvements in Mailman 3.2.0; I > have the rough outline of a plugin that implements much the same feature > set as our current pile of monkey-patches against Mailman 2.1 in a much > nicer way. Very cool! You’ve provided some clarification in a follow up, and I’ll respond there. Apologies for being a little disjointed. One of the things that may really help you, but which doesn’t exist in a fully baked way in Core is the ability to set web hooks for various events. Core does have an event notification system (via zope.events) and that’s used to inform other parts of the Core about things like subscriptions/unsubscriptions, etc. Where web hooks would be useful is if some event in Core needs to inform Launchpad of that event. However, it’s possible that this falls under the plugins you’ve thought about - and while not general purpose, I’m positive you could do the same kind of MM3->LP notifications that you might find necessary, in custom plugins. > Ideally, I'd like mailing lists to have a "deactivated" state in > addition to full deletion. In this state, the list would appear > nonexistent for most purposes: incoming email would be rejected, I forget whether LP uses Exim or Postfix. At least for the latter, it would be fairly easy (if involving a database migration) to include an “active” or “enabled” flag which would be consulted when regenerating the Postfix transport files. I would add this to the MailingList model and make it available through the REST API. Then the LP team admin can toggle this on and off as desired. I also wouldn’t use the IArchiver interface for disabling HyperKitty access to the archives, but I’ll respond in more detail in the next follow up. > Postorius would deny its existence, etc. You’ve clarified that Postorius isn’t needed for Launchpad, since it provides what effectively takes it places in the simplified administration u/i. Cheers, -Barry

7 years, 6 months

[MM3-users] migration

by Dave McGuire

Hi folks. Some time ago, I set up mm3 and have been running a bunch of lists on it with great success. I was a long-time mm2 user, and while the differences are significant, I'm glad I made the switch. However, in what seems to have been a moment of insanity in retrospect, I installed mm3 from my OS' package repository. Yeah, I know, that was dumb. Now I'd like to migrate to a new server, and I'd like to install mm3 in the normal way. 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. I would appreciate any advice from this learned group. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years

[MM3-users] Re: check/update delivery status via python script

by Mark Sapiro

On 7/19/22 12:49, Eggert Ehmke wrote: > Somehow I can't get the starting point in the documentation to do stuff like this. > Besides, when I try to run examples from > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… > I run into errors like > > AttributeError: 'Withlist' object has no attribute 'process' You should see the latest version of that doc at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… It might be a bit more clear, plus at least some of the examples at https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… don't work with mailman core >= 3.2. Where did you find the link to https://docs.mailman3.org/projects/mailman/en/release-3.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

[MM3-users] Re: Can't edit lists anymore: "Something went wrong HTTP Error 404"

by Stephen J. Turnbull

Nils writes: > On 12/30/23 07:52, Stephen J. Turnbull wrote: > This problem remains on a server that uses Ubuntu 22.04 deb. We'll help if we can, but first Debian and then Ubuntu messes with the source code. The problem you describe seems unlikely to be due to their changes but it seems even more unlikely to be due to ours (IMHO ;-). Seriously, we'll do what we can but any changes after an upgrade you must consider that there may be a problem in the changes they make to adapt to the rest of the system or in their upgrade or configuration scripts. Your first line of attack on this kind of problem should be with the distro's channels. (You don't have to wait for an answer to consult us. ;-) Steve

1 year, 7 months

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

by joseverde＠gmail.com

Alrighty, so resetting the permissions and running as list got things running. I was able to start mailman, although when it started I got 4 pages of exceptions. Here's one shortened example (most seemed to follow the same pattern): File "/usr/lib/python3/dist-packages/zope/configuration/config.py", line 794, in toargs args[str(name)] = field.fromUnicode(s) zope.configuration.xmlconfig.ZopeXMLConfigurationError: File "<string>", line 19.2-23.6 MemoryError: File "/usr/lib/python3/dist-packages/zope/configuration/fields.py", line 99, in fromUnicode v = vt.fromUnicode(s) However, I do get these positive signs: GNU Mailman is running (master pid: 4434) and on running the grep, I get these two: list 4434 1 0 10:53 ? 00:00:01 /usr/bin/python3 /usr/lib/mailman3/bin/master -C /etc/mailman3/mailman.cfg list 4440 4434 0 10:53 ? 00:00:01 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=bounces:0:1 -C /etc/mailman3/mailman.cfg So that seems promising, however Mailman REST API not available. Please start Mailman core still remains. Also, not sure if this matters, but doing a systemctl status for mailman3 yielded this: mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-07-27 22:35:34 PDT; 1 day 12h ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Main PID: 16834 (code=exited, status=0/SUCCESS) Trying to start that yields: Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xe" for details. The log for mailman3.service seems to also be giving a memory error from when it last tried to run: 25 21:45:12 systemd[1]: Started Mailman3 server. Jul 25 21:45:56 mailman3[30357]: Traceback (most recent call last): Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3/dist-packages/zope/configuration/xmlconfig.py", line 272, in endElementNS Jul 25 21:45:56 mailman3[30357]: self.context.end() Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3/dist-packages/zope/configuration/config.py", line 345, in end Jul 25 21:45:56 mailman3[30357]: self.stack.pop().finish() Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3/dist-packages/zope/configuration/config.py", line 452, in finish Jul 25 21:45:56 mailman3[30357]: args = toargs(context, *self.argdata) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3/dist-packages/zope/configuration/config.py", line 794, in toargs Jul 25 21:45:56 mailman3[30357]: args[str(name)] = field.fromUnicode(s) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3/dist-packages/zope/configuration/fields.py", line 72, in fromUnicode Jul 25 21:45:56 mailman3[30357]: value = self.context.resolve(name) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3/dist-packages/zope/configuration/config.py", line 151, in resolve Jul 25 21:45:56 mailman3[30357]: mod = __import__(mname, *_import_chickens) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3/dist-packages/mailman/email/validate.py", line 30, in <module> Jul 25 21:45:56 mailman3[30357]: _valid_local = re.compile("[-0-9a-z!#$%&'*+./=?@_`{}~]", re.IGNORECASE) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3.6/re.py", line 233, in compile Jul 25 21:45:56 mailman3[30357]: return _compile(pattern, flags) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3.6/re.py", line 301, in _compile Jul 25 21:45:56 mailman3[30357]: p = sre_compile.compile(pattern, flags) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3.6/sre_compile.py", line 566, in compile Jul 25 21:45:56 mailman3[30357]: code = _code(p, flags) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3.6/sre_compile.py", line 551, in _code Jul 25 21:45:56 mailman3[30357]: _compile(code, p.data, flags) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3.6/sre_compile.py", line 108, in _compile Jul 25 21:45:56 mailman3[30357]: _compile_charset(av, flags, code, fixup, fixes) Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3.6/sre_compile.py", line 226, in _compile_charset Jul 25 21:45:56 mailman3[30357]: for op, av in _optimize_charset(charset, fixup, fixes): Jul 25 21:45:56 mailman3[30357]: File "/usr/lib/python3.6/sre_compile.py", line 354, in _optimize_charset Jul 25 21:45:56 mailman3[30357]: charmap = bytes(charmap) # should be hashable Jul 25 21:45:56 mailman3[30357]: MemoryError

5 years

[MM3-users] django-mailman3 1.3.4 bugfix release

by Abhilash Raj

Hey everyone, There was a critical bug reported yesterday which would cause users to get 404 pages instead of their list options page. Upon investigation, it was found that the bug was related to bumping of Mailman Core's API version to 3.1 in django-mailman3 1.3.3 release. Because this bug can cause problems accessing several pages in web interface, we have a quick bugfix release for you. If you have already upgraded to 1.3.3 and don't wish to do another upgrade/restart, you have an option to run the command below to avoid the bug: $ python manage.py clear_cache -a This should invalidate the cache entries which cause the 404 bug. The new release is available through PyPI at: https://pypi.org/project/django-mailman3/1.3.4/ The changelog is available at: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, as usual, you can update to the new release using pip: $ pip install django-mailman3==1.3.4 -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Configure administrative users via command line?

by kjohnson＠eclypse.org

Thank you for the prompt and informative reply. Mark Sapiro wrote: > ... If you are an owner or moderator of a list > or a superuser, you can handle moderation requests via Postorius. If you > are a list owner or a superuser, you can manage owners and moderators > via Postorius. Yes, I would like to do that. > You can add superusers via the command line django admin > createsuperuser command. For the reference of others like me, createsuperuser will allow you to create a user with a non-unique email address. I strongly recommend against that. mailman shell gave me: >>> from django.contrib.auth.models import User >>> User.objects.filter(is_superuser=True) <QuerySet [<User: admin>, <User: xxxx>]> I dredged a password for admin out of my memory and was able to perform the moderation request. I also set a new list owner.

2 years

[MM3-users] Re: I'm seeing a lot of database locked errors

by Mark Sapiro

On 9/18/23 11:19 AM, bryan.kartzman(a)yu.edu wrote: > And they do have the same thread_id as well: > > select a.id, b.starting_email_id, a.message_id_hash, b.thread_id > from hyperkitty_email a,hyperkitty_thread b > where a.message_id_hash = b.thread_id > and a.id = b.starting_email_id > and a.id in (1365,1366) ; > > id | starting_email_id | message_id_hash | thread_id > ------+-------------------+----------------------------------+---------------------------------- > 1365 | 1365 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 > 1366 | 1366 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 | UB4WSRNRTPBH7XB6RF3W42U2MUDK77S7 > (2 rows) This is interesting. There are two entries in the hyperkitty_email table for the same message. Are the other fields, particularly `content`, for these ids in the hyperkitty_email table the same? If so, I'd be inclined to ``` delete from hyperkitty_email where id = 1366; delete from hyperkitty_thread where starting_email_id = 1366; ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Only Recent archive tab works after mailman upgrade

by Mark Sapiro

On 8/4/24 23:39, zoltan(a)circle-interactive.co.uk wrote: > Hi, > > since I upgraded mailman to 3.3.9 (python 3.11.2) > I have an odd issue on lists' archive page. > Apparently only the Recent tab works. > If I switch to Active or Popular I see the change in the url but page content does not refresh. > I can not see any errors in browser console and in logs so I am quite clueless how to debug further :( Mailman core has nothing to do with this. Did you upgrade HyperKitty, and if so, from what to what? See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/templates/hy… - I don't know why this wouldn't be working in your case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Abhilash Raj

On Sun, Jun 14, 2020, at 12:45 PM, Allan Hansen wrote: > All, > > Thank you for your thoughtful responses to my call for a removal of the > core vs. Django disconnect. From your responses it appears that my > suggestion my issues were caused by the Mailman Core was not based in > reality. Instead, the issue is how Postorius interacts with the Core. > My apologies for overreaching, as the cause of my issues is not an > issue to me. Keeping Core a simple list manager is fine, if Postorius > is easy to use and does the expected. > > As a Subscriber, you are able to do switch emails in subscriptions from > your options page. The URL to which is displayed in the List's Summary > page when you are logged in. Yes, it requires an approval if the list's > settings are set to moderate but that is going to be fixed, see this > issue[1]. It is quite simple IMO to fix this one, if someone wants to > take this up. > > Well, it’s more than that. Based on the current setup, I have asked my > subscribers who want to change their subscription addresses to: > a. Create an account if you do not already have one. > b. Go to the user profile page. > c. Select ‘E-mail Addresses’. > d. Add the new e-mail to the user profile. > e. Wait for the verification notice and verify the new address. > e1. If it does not show send email to hansen(a)rc.org > <mailto:hansen@rc.org> to get the email verified manually. > f. Sign in to the account again and to the user profile (or refresh > the page if not signed out). > g. Select the new address as the primary address. > h. Click on ‘Manage Lists’ > i. For each list you are subscribed to: > i1. Select the list > i2. Click ‘List Options Page.’ > i3. Pull down the ’Select Email’ menu. > i4 Select your new email. > i5. Press ‘Change email used for subscription. > i6. When the moderator contacts you, explain that you are just > changing your email. > i6.1. If the moderator is late, send a reminder or send email to > hansen(a)rc.org <mailto:hansen@rc.org> to bypass the moderator. So, a-f is something we still always want to keep since we aren't going to deal with un-verified email addresses. Now, Primary Address is something interesting in Mailman 3, which wasn't utilized until now in Postorius. I recently added a new feature to Postorius which allows users to subscribe via their Primary Address and it switches the delivery address when you switch your primary address. You can play with how it looks at https://lists.mailman3.org (Mailman instance serving this list) where you will see "Primary Address (myprimaryemail(a)example.com)" as an option when subscribing/switching address. This is still somewhat new feature and there are gaps to it, but it will grow over time. For example, as as admin, you can only subscribe a User's address and not their Primary Address (from Mass Subscription page, or through the CLI commands). As a User, you are able to switch to using your primary address and then every time you switch your primary address, all your subscription shifts to that new address without any extra steps. Also, I just created a fix for i6[1], so switching email addresses won't require approvals anymore. I am still debating if this should be configurable by list owners. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/532 > > Most people choke on these instructions, so I have unfortunately > resorted to just asking them to subscribe the new address and forget > about the old. This is not good for our reputation when the old > addresses start bouncing. So, in more detail: > > I would like to ask my subscribers who want to change their address to: > a. Create an account if you did not already have one. > b. Go to the user profile page. > c. Select ‘E-mail Addresses’. > d. Select an existing address e-mail listed the user profile. > e. Press new button ‘Change address’. > f. When page refreshes, enter the new e-mail address. > g. Press ‘Apply.' > d. Wait for the verification notice. > d1. If it does not show send email to hansen(a)rc.org > <mailto:hansen@rc.org> to get the email verified manually. > > In other words, in addition to ‘Make Primary’ and ‘Re-send > Verification’ and ‘Remove’, another button says: ‘Change Address’ or’ > ‘Replace Address’ or some such. > > This button brings up another page that looks the same, but instead of > ‘Add E-mail Adress’ is says : Enter New E-mail Address’ > and instead of ‘Add E-mail’ is says: ‘Apply’. Then the page refreshes > back to the original page, but the new address is now > replacing the old address. Optionally, it can show the old address > still with a ‘pending change’ until verification. I am still thinking about a few implementation details of this one, I've created an issue[2] [2]: https://gitlab.com/mailman/postorius/-/issues/435 I am thinking we could minimize changes by retaining the same workflow for adding and verifying new address, but add a new workflow of some sort to switch subscriptions to a new address with a single button click. This should simplify the Loop of going to each option page and switching addresses. Finally, the old address can be removed. Another train of thought is that when you Delete your email address, you get an option to switch all the subscriptions on that address to some other address. I could do this by adding a page after you click on "Remove" button. Although, this would restrict the ability to switch subscriptions by only deleting the original one, which I don't want. Maybe I'll end up implementing both of these. What do others think about this? > > Further, when the new address is verified, all lists get updated with > the new address replacing the old > address and all settings associated with the old address are now > associated with the new address. No moderator or admin > involvement needed (other than d1). The fix[1] I mentioned above should already resolve this issue. > > You are able to sign in via web and manage your email and > subscriptions. The preferences also work exactly how you described > above where the lower level override the default and/or upper level > settings. > > To some extent that is true, Abhilash, and I appreciate that. The above > (address change) is a missing piece in that picture and I look forward > to seeing it added, if you have time. > > Yours, > > Allan Hansen > hansen(a)rc.org > > > > > > On Jun 14, 2020, at 0:19 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > > Mark Sapiro writes: > > > >> Then the people who developed the web based management UI (Postorius) > >> and archive UI (HyperKitty) chose to develop those within a Django > >> framework and Django has its own concept of User separate from Mailman > >> Core and that is where the disconnect occurs. > >> > >> It's not that Mailman Core lacks what you want. It's that Django doesn't > >> use it. > > > > I think that's mostly right, in terms of the features that users miss. > > However, as far as I know, Mailman core does lack facilities for > > identification, authentication, and authorization of connections to > > the REST API. And that means that the front ends have to handle > > this. I would guess that's why the web interfaces are built around > > Django user authentication. > > > > I think it would be possible to have somewhat tighter integration > > between the Django "web users" and the Mailman core User objects, but > > it's not necessarily going to be trivial. > > > > I see that Abhilash is pretty optimistic, but I fear this this is > > going to be a long-tail situation where we're going to be seeing core > > user vs. web-gui user integration issues in 2030 (maybe by then only 1 > > every 450 days ;-). I have some ideas, maybe in a couple weeks I can > > sketch them out. > > > > Steve > > _______________________________________________ > > 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/ > > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] HTML email sent to lists migrated from Mailman 2.1

by Nate Coraor

Hello all, I have some lists migrated from 2.1 that are stripping the HTML parts (perhaps all attachments?) from messages despite the options to do so not being enabled and lynx not even being installed. I'm trying to get a new list to behave the same way so I can figure out what's going on without spamming a production list, but have been unsuccessful: despite setting nearly all the list options the same as the old lists, new lists pass HTML portions and attachments just fine. I've verified the settings using mailing list objects directly with `mailman withlist` on the command line and the only differences are things that I can't imagine would be related like admin_notify_mchanges, advertised, and archive_policy. Are there are really old options that can't be accessed via mailing list objects obtained with `withlist` on the command line? Thanks, --nate

6 years, 3 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Sapiro

On 6/18/20 12:05 PM, Brian Carpenter wrote: > On one of my mailman 3 servers, I am having a problem with Postfix > failing to deliver email to Mailman. I keep seeing this in the mail.log: > > status=deferred (connect to 127.0.0.1[127.0.0.1]:8024: Connection refused) > > What is causing this and how can I fix it? > Do you have lmtp_host: 127.0.0.1 lmtp_port: 8024 in the [mta] section of mailman.cfg? (these are the defaults) $ /opt/mailman/mm/bin/mailman conf|grep lmtp [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 Is Mailman's lmtp runner listening on port 8024? $ sudo netstat -lntp|grep python tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 1867/python tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN 1199/python tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 1871/python Is there some firewall issue blocking access to the port even from localhost? -- 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: Cron error

by Mark Sapiro

On 9/29/20 2:04 PM, Mark Sapiro wrote: > On 9/29/20 4:59 AM, Gordon Dickens wrote: >> Hi Mark, >> Thanks for the reply! >> I have removed the lock file as you recommended. > > Has the error recurred? If so, what is the content of > var/lib/mailman3/locks/? > > > What do you see if you run > > /usr/bin/mailman > > manually with no arguments? It should print some help text and a list of > commands. > If the error has not recurred, and the output from `/usr/bin/mailman` is as expected, I'm guessing that the cause of the issue may have been some other `mailman` command that was run manually and left a stale lock behind for the cron of `mailman digests --send` to trip over. -- 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: Updating installed pkgs in MM3 venv

by Mark Sapiro

On 10/15/22 03:39, Odhiambo Washington wrote: > What is the recommended way for updating installed the installed pkgs in > MM3 venv - to ensure that nothing breaks? Upgrading to what? To upgrade from PyPI you can do ``` pip install --upgrade xxx ``` for all the mailman packages where xxx is the package name. However, this may create an issue with Hyperkitty because of https://gitlab.com/mailman/hyperkitty/-/issues/431 To update from the heads of the GitLab branches, the commands would be ``` pip install --upgrade git+https://gitlab.com/mailman/xxx@master ``` With either of the above, it may be necessary to add the `--force-reinstall` option to `pip install`. See this post https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and this thread 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

2 years, 9 months

[MM3-users] Re: psycopg2 error?

by Odhiambo Washington

On Mon, Oct 30, 2023 at 12:17 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > I am not upgrading :-) > > OK, you're installing a newer version than you ever had before. Bye > Allow me to clarify. 1. I have whipped up a completely new Debian 12 VM 2. I am following https://docs.mailman3.org/en/latest/install/virtualenv.html to install MM3. So this is NOT a production machine. My production machines are fine. What I am doing is just to simulate a new install and see if it's seamless. Whatever I am encountering I believe everyone else would also encounter, because I am not deviating from the steps laid out on the official documentation. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

[MM3-users] Re: Installing mm3 with docker

by Abhilash Raj

Hi Tom, On Sat, Sep 9, 2017, at 05:10 AM, Tom Browder wrote: > I am trying to follow instructions but when I get to the actual docker > pull > command (with trust enabled): > > # docker pull maxking/mailman-core:release Please use one of the released versions as tag for the images. Right now, "0.1", "0.1.1" as tag should get you the latest released container images. > > I get an error message: > > No trust data for release This may or may not be a valid image tag, but definitely doesn't have any signature associated with it as release versions. > > I have tried adding various tags but no changes. > > What am I doing wrong? > > Thanks. > > -Tom > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Hope that helps! -- Abhilash Raj maxking(a)asynchronous.in

7 years, 10 months

[MM3-users] Re: Whitelist non subscriber

by Mark Sapiro

On 08/06/2018 06:43 AM, Stephan Krinetzki wrote: > The steps are as follows, right? > - Add users to the list and give the role "nonmember" > - Set moderation action ('defer' or 'accept') Right. > The only thing missing in the documentation is a note on how to do this via the Admin API. Who can explain that to me? Can you be more specific about what you are looking for? If by "Admin API" you mean the REST API, are you asking how to interact with it or what specific POST/PUT/PATCH commands to send? Or are you asking about the 'mailman shell' command? Also, we want to expose the nonmember role in Postorius and enable setting moderation action for nonmembers, but we didn't get that in MM 3.2/Postorius 1.2. -- 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: Changing default message limit (max_message_size)

by Mark Sapiro

On 5/27/19 12:05 AM, roger(a)reasonal.com wrote: > I found the field in settings that would appear to do this, but it just throws an error for whatever I give it ("An error occured**: Unknown attribute: max_message_size"). This should be fixed at <https://gitlab.com/mailman/mailman/merge_requests/329>. Perhaps you need to update your Docker images <https://asynchronous.in/docker-mailman/> Also, see <https://gitlab.com/mailman/postorius/issues/246#note_69323948> for a not about changing this via `mailman shell` (withlist), but see the subsequent comment about `quit()` > PS As a suggestion, may be a good idea to indicate what units it's expecting... bytes? kB? Nybbles? Reported at <https://gitlab.com/mailman/postorius/issues/362>, thanks. > PPS ** Psst: occurred with two r's... Reported at <https://gitlab.com/mailman/postorius/issues/361>, thanks. -- 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: Configure new list via REST API - trying to add moderators

by Mark Sapiro

On 9/11/24 11:47, Andy Matthews wrote: > But looking at the docs for "Mailing list configuration" (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) I don't see anything named `moderator` The "Managing owners and moderators" docs (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…) indicate that we can perform add owners and moderators via a Python shell, but don't indicate that it's possible to do it via REST. Is this true? List members, nonmembers, moderators and owners are rosters. They are managed via REST at the /members endpoint. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for documention of owners and moderators. -- 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] ARC issues

by Stephen J. Turnbull

David Krantz writes: > Is there any known issues with ARC that I should be aware of? Doesn't Postfix do ARC yet? :-( rspamd seems to be recommended by a couple of Linux distros, supports the milter interface that Postfix uses to call out to 3rd party processes, and the website looks good. See rspamd.com. That said, if you want to use Mailman's support... Our support doesn't have issues that I know of. You can check the issue tracker: https://gitlab.com/mailman/mailman/issues. On second thought, don't bother. I did and "ARC" picks up scads of irrelevant junk, "authenticated received chain" nothing, and a couple of other tries don't pick up anything useful either. > I run the latest release of mailman (3.3.0 of core) on Python 3.7.6 > and I use postfix as MTA. [various data deleted] I haven't looked at ARC in some months, so it's possible that our current implementation is out of date with best current practice. However, in a quick scan I see no difference in RFC 8617 vs. ID-ARC-23, so I don't know what might have changed there. Are the messages being refused by those sites because of the ARC errors, or are they being delivered anyway? We probably need to see the message as received by Mailman, the message as emitted by Mailman, and the message as received at the validating site to have a hope of diagnosing this. The things that I can see from the data you've provided that might be related are 1. If it's just the body hash that's a problem, there may be one or more MXes that convert Content-Transfer-Encoding between your Mailman and the receiving sites. That would be easy to check if you have the messages as sent and as received. 2. You have an awfully aggressive list of signed header fields. In particular, the Resent-* fields are treated as trace fields: there may be multiple instances of each. I don't understand the semantics of DKIM/ARC signing for those headers very well, but it's something that I would think easy to mess up. You might try deleting those. You are supposed to sign any existing DKIM-Signature fields, but that's not in the list. 3. The ARC RFC 8617 says that an ARC Sealer must add any DKIM-Signature *before* ARC sealing. I suppose this could be a problem, since our ARC implementation doesn't DKIM sign. (On the other hand, I don't see how it would be a problem, since any MX along the way might add a DKIM signature, and you're not signing DKIM-Signature according to your list of signed fields.) It would be helpful if instead of quoting small parts of error messages, you gave us the entire body of a delivery status notification message or the entire MTA log. If there's stuff (domains, mailboxes, IP addresses) you want to redact, feel free, just make sure that it's obvious what was redacted. I will check our implementation, principally to make sure that the authentication results used are computed on the raw incoming message and the ARC sealing is done on the raw outgoing message after all other message modifications are done. I will also see if I can conjure up tests that test the site's MTA(s) as well as just our implementation, as we currently test our implementation using static data from the ARC implementation we use (ie, we ARC-process a given message and then do a byte-by-byte comparison on an allegedly correct ARC-Sealed version of the same). Sorry I can't give more precise help. Maybe something here will be of use. Steve

5 years, 4 months

[MM3-users] [SOLVED] Re: Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Mon, 2021-12-27 at 14:36 -0800, Mark Sapiro wrote: > > It appears that the MX for billoblog.com is not accepting mail from > your > server. Can you send non-mailman mail from this server to this address? > If not, you need to contact billoblog.com to fin wht they are blocking > your mail. > > > I tried changing the smtp port in mailman.cfg to 587, but that didn't > > change anything. > > because the issue is not in delivery from Mailman to Postfix. It is in > delivery from Postfix to billoblog.com. First, thanks so much for talking me through this. I could never have done it on my own. If you ever decide to go to the Smoky Mountain National Park or Knoxville, TN, send me an email, and I'll buy you a drink (I live in the hills between Knoxville and Gatlinburg, TN). In any case, I did some wandering around the intertubes and it appears this is an uncommon but well-known problem when using dovecot and postfix. It has to do with the setting of smtpd_recipient_restrictions in master.cf. It's not clear *which* "reject" command is triggered, but if I set it to just: -o smtpd_recipient_restrictions=permit_sasl_authenticated then it can get through. Er, to the next error, anyway. Sigh. I have *no* idea why it only shows up with mailman, but not with regular mail. I got some learnin' to do about that line. I don't know what the default reject criteria are. I have this horrible suspicion that I've opened myself up to zillions of evil emails, but I'll investigate that later. So, this took care of the Access Denied issue. That opened up the next error, which was "relay access denied". Again, regular mail worked just fine. Here's the syslog when I sent email to testlist from fp145(a)libertyfp.org: Here's the rejection to billo(a)billoblog.com: Dec 27 18:31:52 libertyfp postfix/submission/smtpd[471207]: connect from mail.libertyfp.org[2.56.57.28] Dec 27 18:31:52 libertyfp postfix/submission/smtpd[471207]: NOQUEUE: reject: RCPT from mail.libertyfp.org[2.56.57.28]: 454 4.7.1 <billo(a)billoblog.com>: Relay access denied; from=<testlist-bounces+billo=billoblog.com(a)libertyfp.org> to=<billo(a)billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> Dec 27 18:31:52 libertyfp postfix/submission/smtpd[471207]: disconnect from mail.libertyfp.org[2.56.57.28] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 But it accepts the email to fp145(a)libertyfp.org Dec 27 18:31:53 libertyfp postfix/submission/smtpd[471207]: connect from mail.libertyfp.org[2.56.57.28] Dec 27 18:31:53 libertyfp postfix/submission/smtpd[471207]: 4FCDD420F5: client=mail.libertyfp.org[2.56.57.28] Dec 27 18:31:53 libertyfp postfix/cleanup[471223]: 4FCDD420F5: message- id=<8d3bf47c5dcd86983e8c01f8baece4e3ac43a1a1.camel(a)libertyfp.org> Dec 27 18:31:53 libertyfp postfix/cleanup[471223]: 4FCDD420F5: warning: header Subject: [Testlist] bbbbb from mail.libertyfp.org[2.56.57.28]; from=<testlist-bounces+fp145=libertyfp.org(a)libertyfp.org> to=<fp145(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 27 18:31:53 libertyfp postfix/qmgr[468573]: 4FCDD420F5: from=<testlist-bounces+fp145=libertyfp.org(a)libertyfp.org>, size=1870, nrcpt=1 (queue active) Dec 27 18:31:53 libertyfp postfix/submission/smtpd[471207]: disconnect from mail.libertyfp.org[2.56.57.28] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Direct mail from fp145(a)libertyfp.org to billo(a)billoblog.com worked fine also. Again, a quick DuckDuckGo search reveals that this has come up a couple of times. It required that I modify /etc/postfix/main.cf to add the non-localhost ip4 address of the box to the mynetworks line: mynetworks = 127.0.0.0/8 10.0.0.0/24 to mynetworks = 127.0.0.0/8 10.0.0.0/24 2.56.57.28 I assume that means that postfix uses localhost for regular mail, but mailman3 uses the 2.56.57.28 address. In any case, it now works fine. I am happily receiving the six million test messages that were queued awaiting delivery to billo(a)billoblog.com. Once again, thanks. I owe you. billo

3 years, 7 months

[MM3-users] Re: Memory usage

by Mark Sapiro

On 09/13/2018 05:05 AM, Adi Kriegisch wrote: > This is without hyperkitty or a management interface, just mailman3 core > that uses 10 times as much ram as mailman2. Did I do something wrong > here? Is there probably a bug in my python environment? Are there any > config options that I should set to avoid this huge memory footprint? Mailman 3 has more runner processes than Mailman 2.1 and they are larger. That is the difference in what you are seeing, but in neither case does this indicate an issue. Much if the memory footprint you see is idle memory that is only used because no other process needs it. For more detail on this and info about tools you can use to see if you really have a memory issue, see <https://wiki.list.org/x/4030711>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: My email address appears in quoted test in my list. Hoot change that.

by Abhilash Raj

On Wed, Sep 4, 2019, at 5:41 PM, paul(a)arenson.org wrote: > Hi. I thought I had the settings right, but I do not see one to get > rid of this. > > My name appears as "On Tue, Sep 3, 2019, at 9:26 PM, > paul(a)domainname.org wrote. How can I hide that? Quoted replies are optional and include this message by default if someone replies to your message. This is added by user's email client and the same behavior is replicated by Hyperkitty when you reply from the web interface. There is really no way to disable this right now. > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 10 months

[MM3-users] Re: Clone or copy Mailman list

by Mark Sapiro

On 2/5/21 2:54 AM, w.schoener(a)alp.dillingen.de wrote: > Hi there, > i am using a mailman 3.2.1, core Api 3.0, Mailman Core Python Version 3.7.3. > I have to create a large number of Mailman lists, all with the simulare settings. > Is there a way to clone a list with all settings an another list name? Not currently in Mailman 3. At least not easily. I suppose you could just create the new lists, e.g. with something like: #! /bin/bash for list in `cat lists`; do bin/mailman create $list done and then run database queries to update the mailinglist table entries for the new lists. It would not be difficult to create a clonelist mailman subcommand to clone a list in this way, but it doesn't currently exist. -- 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: moving lists to another server

by Stephen J. Turnbull

Odhiambo Washington writes: > The idea is to (if possible) not change anything at all. I will be > serving the list using the original domain. Fine. I just didn't want to assume anything. > I am hoping that should not be necessary. It's not. That's one of the major things that MM3 does that MM2 does not: handle multiple domains properly. > I actually had thought it wouldn't be complex doing this until I > sat down and said wait - there is a DB involved :) > 3. (If the DB engines are different) Dump both databases in text > > format (ie, scripts of SQL commands). Check to see how they > > differ. > > > > The DB is MySQL. My running setup uses MariaDB. I am not getting what you > mean here by how they differ. You didn't say that before. I tend to assume PostgreSQL because that's what I use. I don't know if MySQL and MariaDB have different features that have different syntax, etc. That's what you're looking for. Any commands that are *not SQL* used to configure the database engine itself (for example the utf8mb4 parameter which MySQL has but PostgreSQL does not, does MariaDB need it?) Also any non-standard SQL stuff (mostly around varchar/text types I think). > 4. Adapt the foreign database to its new environment with search and > > replace. > > If going with what I have mentioned above, is this step still > necessary? Isn't one installation using 'mailman' and 'mailmanweb' databases, while the other only 'mailman'? You'll need to deal with that at least I suppose. > > 5. (Optional if your name is "Daredevil") Create a new Mailman suite > > install using your current configs, preferably in a new VM or set > > of containers. > > I was thinking about this as one way of testing the situation, much > as it is quite involving. Fred Brooks famously put it this way: "Build one to throw away. You will anyway. The only question is whether you deliver the first version to the customer." ;-) > Suppose I just do: > 1. Create the new list on my server using the inherited domain and > configure it appropriately, > 2. Configure Django to handle the different domains (there is something > that I am yet to understand here around SITE_ID when you have multiple > sites!) You just add them in the Django admin page. Problems come in when you delete the original example.com placeholder domain. I think you probably need to add SITE_ID=0 to settings.py so the Django figures out the site from the HTTP header rather than just assuming it's the same Postorius site for all lists. > 3. Extract the users from the list and subscribe them afresh (I can > shoot an email to let them know the ML had to be moved so they can > set their preferences again) > 4. Import the archives of the list > I should more or less achieve the migration, no? I think that should work. > What about setting up on /opt/mailman2 a complete replica of the > list? That'd be the real "Daredevil" :) This will also work, I'm sure. But we'd be embarrassed after going to the trouble of making Mailman 3 handle multiple domains. Also you'd need separate instances of Mailman running, with their own /etc/mailman3-1 and /etc/mailman3-2, and more important you'd double the RSS and VM requirements by running two instances.

1 year, 8 months

[MM3-users] Re: Python is updated

by Mark Sapiro

On 4/28/23 11:07, Lars Bjørndal wrote: > [Mark] >> >> Your django-admin command is not finding your settings.py file. > > Do you mean /etc/mailman3/ where settings.py lives? Yes. >> Either run >> it with a --pythonpath argument naming the directory that contains >> settings.py or set the environment PYTHONPATH to that directory. > > I tried `django-admin migrate --pythonpath /etc/mailman3`, and got the same result. Then you may need `django-admin migrate --pythonpath /etc/mailman3 --settings settings` What I have is this shell file that I use to invoke django-admin ``` #!/bin/bash . /opt/mailman/mm/venv/bin/activate cd /opt/mailman/mm export PYTHONPATH=/opt/mailman/mm export DJANGO_SETTINGS_MODULE=settings django-admin $@ ``` Of course the paths in the above are specific to my installation and would be different for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Where does sender postorius@ come from?

by Jens Günther

I just realized, that mails for registering an account and/or resetting ones password are obviously sent from postorius@SERVE_FROM_DOMAIN. Why are they not sent from MAILMAN_ADMIN_EMAIL? The problem is: - an account is trying to register with a mailaddress from a HostEurope-server - HostEurope-Servers are doing Sender-Callouts (bad practise :-D) to verify that a mailaccount exists - mail is then bouncing, b/c those are not answered (shoud I?): status=bounced (host [80.237.138.5] said: 550-Sender verification is required but failed. - bounce then can't be processed, since mailaccount does not exist :-D status=bounced (mail for SERVE_FROM_DOMAIN loops back to myself) Am I missing something are shouldn't it be better to send those mails from MAILMAN_ADMIN_EMAIL? (I don't want to mess with these sender callouts or change anything, HostEurope has been a little bit of a pain in the ... with mailinglists and not much help at all). Thanks in advance, Jens.

2 years, 1 month

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Andrew Hodgson

Stephen J. Turnbull wrote: >Ruth Ivimey-Cook writes: > > On 21/06/2020 04:52, Mark Sapiro wrote: > > > Change that to greyarea-post > > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 >I don't understand. I'm not in a position to test with Mailman itself right now, but the standalone gunicorn[1] does the right thing (takes an IP address and binds to the corresponding interface, or takes a domain name, resolves it to >the IP address, and binds that to the corresponding interface). It does not substitute localhost. Sorry not to reply to ruth on this before, my main experience of this issue was running in a Kubernetes cluster using Docker, using https://github.com/maxking/docker-mailman as the basis for the images. What follows is my own research on this issue and it may be completely wrong. Taking the default Mailman Core setting: [webservice] hostname: localhost This makes Mailman-Core listen on the loopback address (via name lookup) on the configured port for incoming REST requests. When it responds to these requests, it sends out in the response a self_link address which matches the [webservice] hostname Parameter. Connecting clients (such as Postorius) need to connect to Mailman-Core on the given hostname (eg http://localhost in the default case where Mailman Core and Web components are installed to the same machine. However if the [webservice] hostname: parameter is set to something like 0.0.0.0, then although you can direct Postorius (via DNS lookup or IP address) at the Mailman Core instance, it fails to work properly because the resulting response sent back from Mailman Core will include self_links pointing at 0.0.0.0 which will not be usable as a URL by the REST client. A fix for this issue is to set the [webservice] hostname parameter to a FQDN or IP address which can be resolved by the machine running the Web components, and as long as the base URL that Postorius tries to use for the Mailman Core access is the same as in the [webservice] hostname parameter, you are good to go. It appears that when specifying a FQDN in the [webservice] hostname parameter, that the system will look up the IP address for that host using the systems name resolution function. This has the side affect of potentially listening on the wrong interface (localhost) if the system hosts file is set such that the machine's FQDN points to 127.0.0.1. In my case my containers were behind CoreDNS and this wasn't an issue for me, but had I tried this for example on a Debian system I would have come against the same issue that Ruth has as it will automatically set the FQDN of the system to resolve to 127.0.0.1 by way of the Hosts file. Adding the network IP address of the system with the FQDN in the hosts file should fix this issue. > > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed >hosts to get the right connectivity, too. >I'm not clear on what you're saying. An address is a rendezvous point; if you're not listening on the address that others are using, you won't meet. What good does it do to split them up? I agree with this, we need a setting for which interface for Gunicorn to listen on, and what Mailman Core sends out in the self_link attribute when responding to REST requests. Thanks. Andrew.

5 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I changed them to 127.0.0.1 and localhost as you suggested El mar., 25 jul. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/25/2017 12:58 PM, Rafael Mora wrote: > > I got this error starting mailman service: > > > > > > [mailman@localhost ~]$ source env2Traceback (most recent call last): > > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in > > create_server > > sock.bind(sa) > > OSError: [Errno 99] Cannot assign requested address > ... > > What do you think? > > > I think you have configured > > lmtp_host: mail.example.com > > which is wrong. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years

[MM3-users] Re: hooking up mailman and sendmail

by Mark Sapiro

On 3/14/21 7:56 AM, John Covici wrote: > That post does not answer my question, it applies only to mailman2 and > is a big mess. I was hoping to use lmtp, which sendmail will use and > mailman seems to have some facilities to use it as well. What that post describes is for Mailman 2.1, how to hijack Mailman's generated aliases for Postfix and apply them to sendmail. The hope is that someone who understands how to configure sendmail can take those ideas and apply them to the Postfix transport and domain mappings generated in var/data/postfix_lmtp and var/data/postfix_domains to generate what is needed for sendmail. Hopefully, once people figure out how to do this, they will inform us of the solution and we can update the docs. -- 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: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 08/08/2019 02:11, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 9:49 AM, Phil Thompson wrote: >> On 07/08/2019 17:04, Abhilash Raj wrote: >> > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: >> >> On 06/08/2019 09:48, Phil Thompson wrote: >> >> > On 06/08/2019 03:38, Abhilash Raj wrote: >> >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> >> >>> I'm in the process of setting up mailman3. The only problem I seem to >> >> >>> be >> >> >>> having is getting Hyperkitty to archive messages. Rather than the >> >> >>> authorisation problems people have previously asked about on the >> >> >>> list, I >> >> >>> am getting a 403 error... >> >> >>> >> >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> >> >>> <html><title>Forbidden</title><body> >> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> >> >>> <html><title>Forbidden</title><body> >> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >> >>> >> >> >>> Any suggestions would be appreciated. >> >> >> >> >> >> How did you install Hyperkitty? >> >> > >> >> > On Ubuntu... >> >> > >> >> > apt-get install mailman3-full >> >> > >> >> >> You probably need to the set the API key correctly in both Core and >> >> >> Hyperkitty. >> >> >> >> >> >> Have you looked at documentation here[1]? >> >> >> >> >> >> [1]: >> >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… >> >> >> >> >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in >> >> >> quotes, single or double, doesn't matter) in your settings.py for Web >> >> >> (Django) should be same as the `api_key : value` (without quotes here >> >> >> in hyperkitty.cfg config file). >> >> > >> >> > That's all correct. I'm familiar with the authorisation issues that >> >> > other people have had. >> >> > >> >> > The only thing I'm doing differently (as far as I am aware) is that >> >> > I'm using a URL prefixed with /mailman3 which is stripped off in my >> >> > nginx configuration... >> >> > >> >> > # mailman3. >> >> > location /mailman3/ { >> >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; >> >> > include uwsgi_params; >> >> > uwsgi_param SERVER_ADDR $server_addr; >> >> > uwsgi_modifier1 30; >> >> > uwsgi_param SCRIPT_NAME /mailman3; >> >> > } >> >> > >> >> > location /mailman3/static { >> >> > alias /var/lib/mailman3/web/static; >> >> > } >> >> > >> >> > location /mailman3/static/favicon.ico { >> >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; >> >> > } >> >> > >> >> > ...but I don't see this affecting the mailman to Hyperkitty >> >> > communication. Posting to lists and the Postorius and Hyperkitty >> >> > frontends seem to work fine. >> >> >> >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my >> >> public IP address). However I now get a 400 Bad Request error. >> >> >> >> I have traced this to the archive() function in >> >> hyperkitty/views/mailman.py which is expect a POST but is actually >> >> getting a GET, specifically... >> >> >> >> GET '/mailman3/hyperkitty/api/mailman/archive?key=...' >> >> >> >> ...which seems to be a fairly fundamental problem. >> >> >> >> Again, any suggestions would be welcome. >> > >> > It should be sending POST request to archive emails[1]. How did you >> > grab the above request? Was it from logs? >> >> Yes, I added DEBUG=True in mailman-web.py and captured the HTML from >> mailman.log. > > DEBUG=True doesn't print anything more useful around the 400 error > response? It prints the usual Django debug html, including the Python traceback, which is how I knew which line of code was raising the 400 error. >> > Do you have anything else in the logs? There should be something in >> > the Mailman Core or web logs should have something. >> >> There's nothing useful in the core log. >> >> There are 3 preceding entries in the web log... >> >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&key=... >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... >> >> There is one item in the spool directory. >> >> These were all (apparently) successful. It seems odd that the last two >> entries were identical. > > The only other thing that I can think of is, ALLOWED_HOSTS. What > settings do you have in your ALLOWED_HOSTS in settings.py for Django? > > You need to have 'localhost' or whatever is the value of the "Host" in > the "base_url" in your hyperkitty.cfg file in Mailman Core. I am not > sure what is the default value in Ubuntu system. > > If you don't know, you can debug by adding a '*' in your ALLOWED_HOSTS > and see if the problem goes away, this will bypass the Host header > check. ALLOWED_HOSTS is ['*']. Phil

5 years, 11 months

[MM3-users] Re: Hyperkitty 1.1.1 to HyperKitty 1.2.1

by Thomas G

Hi, It's a complete migration, not just a upgrade. I rebuild every things on the new server, without data transfers (mailman data dir) other than archives. "" You can't import a gzipped mbox. You have to gunzip it. "" Omfg, yes indeed, it's work better... I have just a problem with statistics not available. "" it won't import any messages older than the most recent message in the existing archive "" It should be not a problem. I will do a dead time to process this change. > Stop prod / migrate archives / start prod on new server. Thanks, Thomas. Le mar. 2 oct. 2018 à 05:11, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 09/30/2018 11:42 PM, Thomas G wrote: > > Hi, > > > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > > install in Mailman3.2. > > > > I didn't found how migrate the archives. > >>From : HyperKitty - Version: 1.1.1 - Python2.7 > > To : HyperKitty - Version: 1.2.1 - Python3.5 > > > As Abhilash said, you shouldn't need to migrate anything but the search > index. > > > > I exported a mbox from hyperkitty (web interface) and tried to re-import > > it, without result. > > """""""""""""""""""""""""""""""""""""""" > > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > > listedetests(a)hatlab.fr > > > You can't import a gzipped mbox. You have to gunzip it. > > > > Computing thread structure > > Synchronizing properties with Mailman > > Warming up cache > > The full-text search index is not updated for this list. It will not be > > updated by the 'minutely' incremental update job. To update the index > > for this list, run the 'manage.py update_index_one_list > > listedetests(a)hatlab.fr' command. > > """""""""""""""""""""""""""""""""""""" > > The database stay empty (and web interface): > > """""""""""""""""""""""""""""""""""""" > > mailmandbnameprod=# select * from hyperkitty_email; > > id | message_id | message_id_hash | subject | content | date | timezone > > | in_reply_to | archived_date | thread_depth | thread_order | > > mailinglist_id | parent_id | sender_id | thread_id | sender_name > > > ----+------------+-----------------+---------+---------+------+----------+-------------+---------------+--------------+--------------+----------------+-----------+-----------+-----------+------------- > > (0 rows) > > """""""""""""""""""""""""""""""""""""" > > > > Any idea to do this importation ? > > > Why is the database empty? It should be as it was with the prior > HyperKitty. > > Also, it doesn't seem to be the issue here, but if you don't specify a > --since option to hyperkitty_import, it won't import any messages older > than the most recent message in the existing archive. i.e., if there are > any messages in the existing archive, the default for --since is the > date of the most recent such message. > > -- > 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/ >

6 years, 9 months

[MM3-users] Re: Hyperkitty no longer archiving

by Andrew Hodgson

Hirayama, Pat <phirayam(a)fredhutch.org> wrote: >OK, I see uwsgi running in process table. >PID USER TIME COMMAND > 1 mail 0:13 uwsgi --ini uwsgi.ini > 7 mail 1h11 uwsgi --ini uwsgi.ini >There is only one uwsgi.ini file, and it is in the same directory as settings.py, settings_local.py and wsgi.py I had some similar issues last week when migrating from Mailman_Suite to Mailman_Web. Are there any settings in settings_local.py which you know are valid such as the database connection which you can identify as being in use and maybe modify to ensure you are pulling in the files from the right place? For example if you set `DEFAULT_FROM_EMAIL` in your settings_local.py to a specific email address, then restart the container, password resets via the web interface should come from that new address. Its an amateurish way of doing it possibly but I've been bitten by this before. Thanks. Andrew.

2 years, 8 months

[MM3-users] Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Stephen J. Turnbull

Mail Person writes: > Hello everyone. I am trying to sort out an error happening when > messages are sent to the mailman server. The emails are being sent > to the list but I get this error each time: > > Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") This looks like the MySQL "we don't do 4-byte UTF-8" bug. > File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute > 209. res = self._query(query) and it is MySQL, so the problem is most likely that your MySQL is not configured to handle Unicode properly. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… for a lot of information about this. All the posters have useful comments but start with Mark Sapiro's.

1 year, 11 months

[MM3-users] Re: MM3 does not receive gmail-Members!

by Mark London

On 4/24/2023 5:11 PM, mailman-users-request(a)mailman3.org wrote: > The Postorius Domains view will show you the SITE_ID for your domain. > In /etc/mailman3/settings.py you probably have > SITE_ID = 1 > Change that to the value from the Postorius Domains view. > If you have more than one domain, you can set > SITE_ID = 0 > and that should show the domain from the http request. 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 guess I should just let it be set to 1 and be done with it? - Mark

2 years, 3 months

[MM3-users] Changing delivery mode for ALL subscribers on a SINGLE list using REST

by Henrik Rasmussen

While in Mailman Settings a user can change delivery mode for either Global (all subscriptions regardless of address or list), Address based (regardless of list name) or List Based (regardless of address). The list admin can change a user's delivery mode setting on a single list (affecting only that address and only that list), but only one subscriber at the time on the list. Changing a user's delivery mode can also be done using REST[1], but I asume this will affect the user's subscription on all the lists where she subscribed using the same address. How do I change ALL the subscribers[2] on a _single list_ to a certain delivery mode, using REST? [1] https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/preferences.… [2] Most likely by iterating through all subscribers, one at the time, on the list in question.

6 years, 5 months

[MM3-users] Mailman 3 installation from latest Debian packages

by Matthew Blissett

Hi, I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). The dropdown controls on the UI for Postorius (e.g. "Subscription requests", "Mass operations" and the username button to log out) and the similar controls on Hyperkitty (e.g. "Threads by month") do not work. You can see the latter at http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… I found https://lists.gem5.org/archives/list/gem5-announce@gem5.org/ which is running the same version, but presumably not using these Debian packages as the Javascript is slightly different. Could this be a problem with the Debian packaging, or perhaps my configuration -- which is very close to the defaults (i.e. Mailman and Apache configuration generated by dpkg). Has anyone set up a working installation using these packages? Thanks, Matt Blissett PS, I wrote a similar message earlier in the week to a Debian list: https://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/2021-February…

4 years, 5 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/10/21 11:29 AM, bob B wrote: > /opt/mailman/core/mailman-extra.cfg. now has > #lmtp_host: localhost > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > But but mail log shows > 2021-08-10T14:13:28.927266-04:00@####### postfix/qmgr[37253]: DDF5D3083EC2: from=<user(a)user.com>, size=8181, nrcpt=1 (queue active) > 2021-08-10T14:13:28.973273-04:00@####### postfix/lmtp[39368]: DDF5D3083EC2: to=<test@.....>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.07, delays=0.04/0.02/0.01/0, dsn=4.4.2, status=deferred (lost connection with 127.0.0.1[127.0.0.1] while receiving the initial server greeting) > > Also to clarify the images no longer have hard coded ips so I should NOT DO this correct? > ----------------------------- > lmtp_host: 172.19.199.2 > lmtp_port: 8024 > smtp_host: 172.19.199.1 > smtp_port: 25 > ----------------------------- I think that's correct, but I'm at a loss for helping further. Hopefully @maxking will be able to help. -- 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: Hyperkitty 403 Forbidden Error

by Abhilash Raj

On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: > On 06/08/2019 09:48, Phil Thompson wrote: > > On 06/08/2019 03:38, Abhilash Raj wrote: > >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: > >>> I'm in the process of setting up mailman3. The only problem I seem to > >>> be > >>> having is getting Hyperkitty to archive messages. Rather than the > >>> authorisation problems people have previously asked about on the > >>> list, I > >>> am getting a 403 error... > >>> > >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on > >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: > >>> <html><title>Forbidden</title><body> > >>> <h1>Access is forbidden</h1></body></html> (403) > >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on > >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: > >>> <html><title>Forbidden</title><body> > >>> <h1>Access is forbidden</h1></body></html> (403) > >>> > >>> Any suggestions would be appreciated. > >> > >> How did you install Hyperkitty? > > > > On Ubuntu... > > > > apt-get install mailman3-full > > > >> You probably need to the set the API key correctly in both Core and > >> Hyperkitty. > >> > >> Have you looked at documentation here[1]? > >> > >> [1]: > >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… > >> > >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in > >> quotes, single or double, doesn't matter) in your settings.py for Web > >> (Django) should be same as the `api_key : value` (without quotes here > >> in hyperkitty.cfg config file). > > > > That's all correct. I'm familiar with the authorisation issues that > > other people have had. > > > > The only thing I'm doing differently (as far as I am aware) is that > > I'm using a URL prefixed with /mailman3 which is stripped off in my > > nginx configuration... > > > > # mailman3. > > location /mailman3/ { > > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > > include uwsgi_params; > > uwsgi_param SERVER_ADDR $server_addr; > > uwsgi_modifier1 30; > > uwsgi_param SCRIPT_NAME /mailman3; > > } > > > > location /mailman3/static { > > alias /var/lib/mailman3/web/static; > > } > > > > location /mailman3/static/favicon.ico { > > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > > } > > > > ...but I don't see this affecting the mailman to Hyperkitty > > communication. Posting to lists and the Postorius and Hyperkitty > > frontends seem to work fine. > > I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my > public IP address). However I now get a 400 Bad Request error. > > I have traced this to the archive() function in > hyperkitty/views/mailman.py which is expect a POST but is actually > getting a GET, specifically... > > GET '/mailman3/hyperkitty/api/mailman/archive?key=...' > > ...which seems to be a fairly fundamental problem. > > Again, any suggestions would be welcome. It should be sending POST request to archive emails[1]. How did you grab the above request? Was it from logs? Do you have anything else in the logs? There should be something in the Mailman Core or web logs should have something. [1]: https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman_hyperkitt… -- thanks, Abhilash Raj (maxking)

5 years, 11 months

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Mark Sapiro

On 10/31/22 07:04, Markus Ludwig Grandpré wrote: > Dear Mailman3 list, > > I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system > with a remote Postgres database server. During the installation process > dpkg is asking for the DBA password that our DBA team would not provide > to me. So what can I do? This is really a question for Debian, but apparently dpkg wants to create databases for Mailman and Mailman Web. You will need to get your DBA team to create these databases (probably named `mailman` and `mailmanweb`) and a Mailman user (probably `list`) with all access to these databases and probably manually configure the `[database]` section of mailman.cfg and `DATABASES` on Django's settings -- 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] Question about the smtp log (rotation)

by David P Vanecek

I have been asked to take over the management of the mailman3 servers as the prior admin left little documentation. One of the first things I need to do is optimize the logging. Currently the mailman.log is being rotated and zipped by user list and kept 5 day. (this is fine but would like to increase it some) But the smtp log has not been rotated since August (also created by user list) I cannot seem to find what process does this and how I can modify it. Any assistance would be greatly appreciated. Thanks, [University of Nevada, Reno logo]<https://www.unr.edu/> David Vanecek Senior Server Administrator Office of Information Technology Work-phone: (775) 682-5065<tel:(775)%20682-5065> dvanecek(a)unr.edu<mailto:dvanecek@unr.edu> https://www.unr.edu/oit ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/jpeg Name: image001.jpg Replaced multipart/alternative part with first alternative.

2 years, 4 months

[MM3-users] Re: Delivery to mail@domain.tld failed with code 444, [Errno 111] Connection refused

by Stephen J. Turnbull

christopher.claus(a)tgcamberg1848.de writes: > I identified the restriction > > smtpd_sender_restrictions = reject_unknown_reverse_client_hostname > which blocks the connection from mailman in postfix. I have no idea > why mailman sends its mails by IP instead by containernam/hostname > as before. Probably this relates with IPv6 activation .... I am sure that Mailman has nothing to do with this problem, and almost sure that Postfix is not responsible for it. This is not a murder case, where the reporter of the crime is the obvious suspect. It is an Internet failure case, where the #1 suspect is a constant: DNS. What is very likely happening is that IPv6 is preferred over IPv4, and your DNS doesn't have a PTR record for the IPv6 address of the mailman container. That means the reverse lookup fails, and the message is blocked. Steve

1 year, 6 months

[MM3-users] Re: Issue converting table charset to utf8mb4 on mysql

by Odhiambo Washington

On Sun, Mar 24, 2024 at 3:44 PM Helio Loureiro <helio(a)loureiro.eng.br> wrote: > Ok. Thanks for the clarification. > > Just a heads up: something went wrong. Very wrong. I had to revert the > database to the last backup. > > But not on mailman3. It was on mailman3web. > > Apparently things got really bad after I converted tables django_q_ormq and > hyperkitty_sender. After that hyperkitty got into cyclical crashes. > PS: Is it possible that you can stop top-posting? Thank you. Now, I do not remember if anyone advised you to convert the tables! Where did you get such advise? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: > On 2024/07/28 00:39, Mark Sapiro wrote: >> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: >>> >>> The server runs power-mailinabox, which uses Postfix indeed. All my >>> mail, and quite a few others' mail is sent from the using SMTP-Auth >>> on port 465. Actually, this message is sent via that server too. >>> So it's clear to me that MM3 is not authenticating for some reason. >> >> What do you see in Mailman's smtp.log and in the mail.log on the mail >> server? > > The smtp log is in syslog... I also see this in /var/log/mailman3/web/mailman-web.log *** Starting uWSGI 2.0.20-debian (64bit) on [Sun Jul 28 15:27:48 2024] *** compiled with version: 11.2.0 on 21 March 2022 11:00:44 os: Linux-5.15.108-1-pve #1 SMP PVE 5.15.108-2 (2023-07-20T10:06Z) nodename: mailman machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 1 current working directory: / detected binary path: /usr/bin/uwsgi-core setgid() to 33 setuid() to 33 chdir() to /usr/share/mailman3-web your processes number limit is 513922 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uwsgi socket 0 bound to UNIX address /run/mailman3-web/uwsgi.sock fd 4 Python version: 3.10.12 (main, Mar 22 2024, 16:50:05) [GCC 11.4.0] Python main interpreter initialized at 0x561ce813d1d0 python threads support enabled your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 166752 bytes (162 KB) for 2 cores *** Operational MODE: threaded *** /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( WSGI app 0 (mountpoint='') ready in 5 seconds on interpreter 0x561ce813d1d0 pid: 113 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI master process (pid: 113) spawned uWSGI worker 1 (pid: 339, cores: 2) [uwsgi-daemons] spawning "python3 manage.py qcluster" (uid: 33 gid: 33) /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. See https://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( System check identified some issues: WARNINGS: 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'. django_mailman3.Profile: (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'. hyperkitty.Attachment: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (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 HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (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 PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. 15:27:55 [Q] INFO Q Cluster low-vermont-harry-fillet starting. 15:27:55 [Q] INFO Process-1 guarding cluster low-vermont-harry-fillet 15:27:55 [Q] INFO Q Cluster low-vermont-harry-fillet running. 15:27:55 [Q] INFO Process-1:3 pushing tasks at 386 15:27:55 [Q] INFO Process-1:2 monitoring at 385 15:27:55 [Q] INFO Process-1:1 ready for work at 384

1 year

[MM3-users] [Mailman-Users] mailman 3 and freeipa

by Stephen J. Turnbull

Crossposting and redirecting replies to mailman-users(a)mailman3.org. Steven Jones writes: > I cant find anything on this so far but can Mailman3's webui use > freeipa as the authentication mechanism? Hi Steve, I don't have a complete answer offhand (and right now I'm just reducing my inbox so a single google search is as much as I can do), but searching for "freeipa django" indicates that there are "connectors" for Django and FreeIPA. The nicest option would be a plugin for Django's socialauth application. If that doesn't seem to exist, perhaps you can just add a FreeIPA application to the Django configuration. You would need to add it to both Postorius and HyperKitty configurations. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 4 months

[MM3-users] FYI: Django security releases issued: 4.0.6 and 3.2.14

by Stephen J. Turnbull

Thanks to Guillermo for the heads-up. As far as I can tell, neither of these functions is used in the Mailman suite itself. That doesn't mean they aren't used in one of our dependencies, but it does mean that we can't do much about what's installed on your host. You should upgrade if you are using Django 3 or 4. (Not sure we support Django 4.) We will keep a watch on this. Again, thank you, Guillermo! Guillermo Hernandez (Oldno7) via Mailman-users writes: > https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ > > > Django security releases issued: 4.0.6 and 3.2.14 > > Posted by *Mariusz Felisiak* on Julio 4, 2022 > > CVE-2022-34265: Potential SQL injection via Trunc(kind) and > Extract(lookup_name) arguments > > Trunc() and Extract() database functions were subject to SQL injection > if untrusted data was used as a kind/lookup_name value.

3 years

[MM3-users] Re: combine postorius and hyperkitty into one Apache vhost

by Mark Sapiro

On 12/29/22 12:58, Eggert Ehmke via Mailman-users wrote: > So you prefer Gunicorn over uWSGI? When I have a working installation that > uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason > for this, and while I am open for alternate solutions, ... No, don't change. If uWSGI is working for you, it's fine. I prefer Gunicorn and recommend it for new installations because it's already installed as a dependency of Mailman core, at least if the web UI is on the same machine as Mailman core, and because I think its configuration is simpler than uWSGI. uWSGI does have an advantage in that it can be configured to start qcluster eliminating the need to do that separately. -- 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: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/25/20 11:37 AM, Odhiambo Washington wrote: > On Sat, 25 Jul 2020 at 19:58, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> This is a packaging glitch with the flufl modules. Remove and reinstall >> them. >> >> pip uninstall flufl.bounce flufl.i18n flufl.lock >> pip install flufl.bounce flufl.i18n flufl.lock >> >> > It would appear that luck isn't just on my side: > > root@gw:/opt/mailman/mm # pip uninstall flufl.bounce flufl.i18n flufl.lock ... You need to run these pip commands in your venv. I.e. do this > [root@gw /opt/mailman/mm]# source /opt/mailman/mm/venv/bin/activate before the pip uninstall and pip install. -- 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: Digests not working correctly

by Steve Brown

I'm a list administrator for a list hosted by mailmanlists.net on a server in Germany. Only one member uses the digest option, but she doesn't receive a digest until the Digest size threshold has been exceeded. (I also am subscribed as a member with the Mime Digest option and see the same behavior.) The option for Send Digest Periodically is checked but doesn't trigger a daily digest on the days that there is some activity if the aggregate size doesn't exceed the threshold. I think "periodically" means daily, and the administrator doesn't seem to have any way of checking or changing the periodicity. The hosting service has attempted several fixes, including fiddling with the cron settings, but hasn't found something that works. They even upgraded to ver. 3.3.9 recently, and that didn't fix the problem. Any suggestions for what I might do or suggest to the hosting service?

1 year, 1 month

[MM3-users] Re: How to connect mailman into existing postfix server

by Mark Sapiro

On 09/16/2018 02:07 AM, Hagen Bauer wrote: > Hi to all, > > I am trying to setup mailman3 with the Docker Image. Everythings works > relative nicely but I am blocked by the Postfix integration part. > > I have a small postfix server that is delivering mails to known domains > and an alias map. The standard use case assumes that the external > postfix is only routing mails to the mailman lmtp. If I do this all my > old users are recected. If your list domain is a virtual alias domain, see <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#unusual-…>. This is written assuming 'hash' tables and I think the Docker image generates 'regexp' tables, but it should work with those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: how to delete a list member using the Linux command line

by Mark Sapiro

On 6/19/20 2:10 PM, Mike Wertheim wrote: > Thanks! > > I'm on Debian 10, and the latest Mailman version that's available in the > Debian package manager is 3.2.1. > > I really have no idea how packages get updated in the package manager. Do > you know why Mailman 3.3.1 is not yet available in Debian's package > manager? (Does someone on the Mailman project need to push it there? Or > does someone on the Debian side need to pull it in?) The Debian packaging folks are aware of all our releases. Packaging them is up to Debian. See this reply <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960072#10> to a different issue for a bit more info. -- 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: Speed/progress of update_index_one_list?

by Mark Dadgar

On Jan 13, 2022, at 11:46 PM, Philip Colmer <philip.colmer(a)linaro.org> wrote: > Yesterday, I ran "mailman-web update_index_one_list" against a mailing > list. The command output "Indexing 328077 emails" and that is the last I've > heard from it. > > The process is still running but, looking in ~mailman/web/logs, I can't see > anything happening related to that list. > > Is there any way to determine how far this process has got, or what it is > actually doing? (Without stopping it) > > For future indexing, what makes the most difference to the speed? Does it > benefit from having multiple cores if I resize the AWS instance to a larger > processor? What is the bottleneck for this process? Which indexer are you using? Whoosh is interminably slow. Think “days to generate a list index” slow. I recommend Xapien. It is ridiculously fast. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 6 months

[MM3-users] Re: Mailman config is not being applied

by Mark Sapiro

On 8/23/24 10:45 AM, roberto.blandino--- via Mailman-users wrote: > Debian: 11.10 > GNU Mailman 3.3.3 (Tom Sawyer) > Server version: Apache/2.4.61 (Debian) > PHP 7.4.33 (cli) (built: Apr 12 2024 00:02:16) ( NTS ) > > I have a list and when i add a no member on the web interface and on the Non-Member options i set "Administration options" to "Accept skip other rules" when i send email from that address it keeps being moderated and when i open again the options it keeps saying "Default by list" The options are not being write on changes Is there some kind of redirect in your Apache config that's losing post data? Do other settings in Postorius "stick"? Is this a Debian package? If so, 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

11 months, 1 week

[MM3-users] Mailman, etc. upgrade woes and persistent bugs

by Stephen J. Turnbull

hansen(a)rc.org writes: > I just had my Mailman suite upgraded. When it got started, I > starting receiving messages that hundreds of subscribers to the > lists had been disables, including several of the list > moderators. I'm sorry to hear about this. > This version started supporting bounce processing, but > how in the world was this upgrade allowed to act on bounces that > were being collected PRIOR to enabling bounce processing?? Well, if bounce processing were occurring as designed, there would be very few bounces in the queue. So it's a difficult thing to anticipate until it happens. And curiously I haven't heard of this before. I mean, if it were going to happen, I would expect that it would have happened at the very busy lists at python.org. So maybe you have an unusually large number of bounces? Not saying it couldn't have been anticipated that *somebody* would have that situation, but we'd have to be extremely lucky, or have a dedicated "red team" looking for ways the feature can break, to find it before installing it. I'm sorry it happened, but AFAICS it's "one of those things". Technically, it appears that the model for bounce information is initialized based on the time of processing, rather than the (alleged) time of injection or the (presumably trustworthy) time of receipt by the local MTA. I don't have time to check further on if that's modified later, but "not modified" explains what you saw very well. I guess you must have had many hundreds of bounce messages in the queue. Probably the simplest way to deal with this is to clear the bounce queue while upgrading, or at least offer the option. Losing a few hours' worth of bounce messages (if they're being processed normally) isn't going to hurt anything. It would also be simple to provide a report of who bounced and the most recent bounce, if desired. > I then looked at several of the disabled accounts, but the > subscription info page in Postorius had no information about > whether an account was enabled or disabled. Why is this not > displayed???. It is for me when I've authenticated, both for lists where I'm owner and for lists where I'm just a subscriber. (However, the lists where I'm subscriber are on python.org where Mark is the site admin, and may be a little ahead of released versions.) > The members can't see if their account is enabled. I guess they are email-only members, and have not authenticated to Postorius? I don't think we will allow unauthenticated access to user info in Postorius in a distributed version. If you really need it, the fastest route would be to find a contractor to customize Mailman for that -- custom versions are not a priority for us. > Is this another example of the disconnect between Mailman and > Postorius? Hard to say. If it's not the users' failure to authenticate, I would guess this is most likely due to a skew in the upgrade process where the versions of Mailman core and Postorius were mismatched, but as I wrote above, I can see this in the user's setting page for both my "owned" lists and for my "just a subscriber lists". It would be inconvenient in your situation because list admins have to visit the user's options page to see and modify it, but I *can* see it. > Further, even after the upgrade, the moderators still cannot access > the list memberships even though all the lists are set to allow > that. This is a known bug being worked on. I'm sorry it was not fixed in time for your upgrade. > As a result of these bugs, after consulting with Brian, who helped > with the upgrade, I spent many hours re-enabling the several > hundred accounts that had been disabled. I had to go through each > email notification to find the address of a disabled account, then > find the list, then the member, in Postorius, and finally enable > the account (at which time Postorius DID show the enabled status). I'm quite sure that this situation could have been addressed quickly and efficiently with a Python script, or in an interactive session with mailmanclient. That doesn't help you now, but in the future feel free to ask us to help with that. We generally are able to respond within a few hours. It's probably not as fast as doing it by hand, but there's the consideration of your time spent. Or if there are Python programmers hanging around, a little fiddling with the mailmanclient command line will probably allow them to figure out what's what, enough to do this. > Please, can the next upgrade include these very basic > fixes/enhancements, which I requested a long time ago: > a. The ability of moderators to see the list membership (a bug). It's in the queue. I can't say when it will be released. > b. The ability of members to change their addresses for all lists > they are subscribed to. What exactly do you want here? I can think of a number of ways to implement that, depending on whether the old address is to be deactivated from the lists, unsubscribed from the lists, or deleted from the Mailman and/or Postorius Users. There may be other variables to consider, as well; I haven't thought about this. AFAICS this is not a trivial feature, and I'd really like to hear from people who want "something like" this about exactly what they want and their use cases. Or we'll release an insufficiently designed feature that causes somebody hundreds of problems.... > c. That when members go to look at their subscription info, they > can actually see the settings. As far as I know, they already can if they have authenticated. If that's not true in your installation(s), we'll need to find out why, because it works for me. Enabling access without authentication is a potentially dangerous change that I currently believe shouldn't happen at all in a Mailman distribution, and will certainly take time to design. If your requirements include unauthenticated access, I would not hold my breath, let alone expect it in the near future. Regards, Steve

4 years, 5 months

Search results for query "dO"