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

[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, 1 month

[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, 5 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

10 months

[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, 3 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.

2 years, 11 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, 1 month

[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]

6 months, 3 weeks

[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

1 week, 3 days

[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, 4 months

[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, 8 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, 7 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]

9 months, 1 week

[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, 4 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

10 months, 3 weeks

[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.

9 months, 1 week

[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.

8 months, 3 weeks

[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, 8 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, 5 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, 1 month

[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, 4 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 :-)

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

2 years, 10 months

[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

[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

8 months, 3 weeks

[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, 8 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 "^$|^.*#" :-)

3 years, 11 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

[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, 3 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.

4 years, 9 months

[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, 2 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

1 year, 11 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.

6 months

[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, 3 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, 5 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, 2 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/

1 year, 11 months

[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, 8 months

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

by Mark Sapiro

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

7 years, 1 month

[MM3-users] Re: 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, 3 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, 3 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, 3 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

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

7 months, 1 week

[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, 5 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, 7 months

[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, 3 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

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

6 months, 2 weeks

[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, 3 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, 4 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, 2 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, 5 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, 7 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, 4 months

[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

6 years, 10 months

[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, 1 month

[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, 5 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, 5 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

2 weeks, 1 day

[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, 7 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, 6 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

6 months

[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

7 years, 10 months

[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

[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

1 year, 11 months

[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, 3 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

3 years, 8 months

[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 >

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

[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

2 months, 2 weeks

[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

4 years, 8 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

3 years, 8 months

[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

2 years, 9 months

[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, 3 months

[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)

4 years, 10 months

[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)

4 years, 10 months

[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.

1 year, 9 months

[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, 7 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

8 months, 2 weeks

[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

[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

4 years, 10 months

[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, 6 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, 6 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, 5 months

[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, 1 month

[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, 3 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, 7 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, 8 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

5 years, 10 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

7 months, 1 week

[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, 5 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, 7 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, 7 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, 2 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, 8 months

[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.

4 years, 10 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

1 year, 11 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.

1 year, 10 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, 6 months

[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

7 years, 8 months

[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, 1 month

[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, 5 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, 8 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

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

8 months, 3 weeks

[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, 5 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, 1 month

[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, 3 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

[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, 1 month

[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.

2 years, 9 months

[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, 3 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

4 years, 8 months

[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?

10 months, 2 weeks

[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, 2 months

[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, 7 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

4 years, 10 months

[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, 3 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

7 months, 4 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Look: [root@localhost mailman]# find / -name mailman.cfg /etc/mailman.cfg /root/var/etc/mailman.cfg /root/mailman/src/mailman/config/mailman.cfg /root/dev/mailman/mailman/src/mailman/config/mailman.cfg /var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/postorius/var/etc/mailman.cfg /mailman/mailman/src/mailman/config/mailman.cfg /mailman/mailman/build/lib/mailman/config/mailman.cfg /mailman/mailman/var/etc/mailman.cfg El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > There must be another config file being picked up. Have a look at the > mailman.cfg search order explained here [1]. > > My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' > to be sure. You'll want to delete any in the search path and then rerun > 'mailman info'. > > [1] > http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > -Kyle > > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

[MM3-users] Re: Mailman3 via Docker and NGINX

by Mark Sapiro

On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > 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. ... > 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; > } > } Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the correct output, uwsgi or whatever your wsgi process is is working at that level, and I don't think you should be invoking uwsgi in nginx. I think you should be using proxy_pass. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> for the nginx config used on lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Verification Failed Error

by Abhilash Raj

On Thu, Dec 20, 2018, at 2:28 PM, brian(a)emwd.com wrote: > Abhilash Raj wrote: > > Yes, you do need to restart mailman-web container. > > > > $ docker-compose restart mailman-web > > When I added the following to /opt/mailman/web/settings_local.py > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > > I got network not found error message in the log file when I tried to > reset my password. Should EMAIL_HOST be something else besides > localhost? Yes, I am sorry, I should have mentioned this before. Created another issue to add that as well[1]. It should be pointing to Exim running on host, so EMAIL_HOST = 172.19.199.1 [1]: https://github.com/maxking/docker-mailman/issues/277#issuecomment-449156976 > _______________________________________________ > 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, 4 months

[MM3-users] Re: need help to migrate from Mailman2 to Mailman3 (french if possible)

by Pascal Léval

what you have written below worked fine, thanks ! but now, I still have the error sending an email : Erreur : 550 5.1.1 <formule(a)listes.leval.info>: Recipient address rejected: User unknown in relay recipient table I think it's a problem with Postfix, what do you think ? Cordialement Pascal Léval Le 22/03/2024 à 15:13, Odhiambo Washington a écrit : > First, you must create the list in MM3 because the list MUST exist > before any operations can be done on it. > > 1. mailman create formule(a)listes.leval.info > # Create the list in MM3 > 2. mailman import21 > formule(a)listes.leval.info /var/lib/mailman/lists/formule/config.pck > # Import the list config > and members > 3. mailman-web hyperkitty_import -l formule(a)listes.leval.info > /path/to/archives/private/formule.mbox/formule.mbox # import archives > 4. mailman-web update_index_one_list formule(a)listes.leval.info > #update list index

1 year, 1 month

[MM3-users] Re: MM3 Docker

by brian＠emwd.com

Odhiambo Washington wrote: > So you just added: > - stop_grace_period: 30s > > to the block?? I actually did not add it. It was already there from the docker files that I pulled from: https://github.com/maxking/docker-mailman > > I don't know if that setting makes any difference. I am also > > using the > > included postgres database instead of mysql. > > > > For the mailman-web section, you need to add the following: > > > > - SERVE_FROM_DOMAIN=yourdomain > > - MAILMAN_ADMIN_USER=youruser > > - MAILMAN_ADMIN_EMAIL=youradminemailaddress > > > The mailman-web section has sub-sections. Under which one do I add > these? environment?? Or networks below the IP address? Under the environment sub-section. > I have apache2 and nginx on the server. Apache listens on 80 and 443 while > nginx listens on 8080 and 8443. I won't be of much help here I am afraid. My server is just using nginx. Brian

6 years, 3 months

[MM3-users] Re: Turn off social logins?

by Nick Wynja

On 02/10/19 at 08:57, brian(a)emwd.com <brian(a)emwd.com> wrote: > "In your `settings_local.py` copy the whole INSTALLED_APPS section from [default settings](https://github.com/maxking/docker-mailman/blob/master/web/mailman… and add/remove the auth providers you want/don't want. Notice the `allauth.socialaccount.providers.<provider>` in the list below." Another option, which seems more future-proof, is to strictly remove the account providers you don't want from INSTALLED_APPS rather than defining INSTALLED_APPS locally. First, you have to access INSTALLED_APPS by importing settings into settings_local.py: ``` from settings import * ``` Then, you can set INSTALLED_APPS to everything it already is minus the social providers: ``` INSTALLED_APPS = [a for a in INSTALLED_APPS if not a.startswith('allauth.socialaccount.providers') and not a.startswith('django_mailman3.lib.auth.fedora')] ``` This way if Postorius ever adds any apps you won't need to update your local settings. Anyone see any downsides to doing it this way? -- Nick Wynja https://nickwynja.com

6 years, 2 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Thank you for your prompt response Mark, Στις 2019-09-18 19:12, Mark Sapiro έγραψε: > Is only one list affected, and is it all messages from this list or > only > some? Just two messages from this certain list. Subsequent messages and other activity seems to work properly > Do some deliveries of the problem message succeed? > I think not, the IndividualDelivery lines list all all recipients (list is small so I was able to check) > Postfix can return a 421 status > and drop the connection if there are too many invalid local recipients, > although I don't know if this would apply in the VERP case. Well there is no connection to postfix at all when the runner starts and the "Cannot connect to SMTP server" log shows up. Otherwise I'd have seen something in the postfix logs or tcpdumps in localhost.

5 years, 7 months

[MM3-users] Re: Negative number for digest size

by Mark Sapiro

On 2/4/20 3:12 AM, Gila Halpern wrote: > If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting? No. Setting digest_size_threshold to anything <=0 will send a digest on every post. You have to just set it to a very large number (or a reasonable value for the largest you want the digest to grow before it is sent). However, when periodic digests are sent has nothing to do with Digest Frequency. That setting which is misnamed and improperly described (see <https://gitlab.com/mailman/postorius/issues/395>) controls only how often the digest volume number is incremented and issue number reset. The frequency of periodic digests is controlled by when cron runs the `mailman digests --periodic` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Correcting name spellings in a list

by Mark Sapiro

On 2/24/21 10:13 AM, Peter Adebahr via Mailman-users wrote: > On 2/24/21 6:40 AM, Morris Jones wrote: >> I typo'd some full names in a mailing list. Is there a way to fix it >> without writing SQL? >> > > I understand it is just the name itself, which has been typo'd, not the > mail address: Couldn't you just edit the field "display_name" of table > "address" in the MM3 database? Easy with phpmyadmin or adminer... Of course you can do that if that's where the typo is. The actual display name you see may be the one in the `address` table, or it may be the one in the `user` table depending on whether the subscription is by address or by user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

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

by William Oliver

Thanks to everyone's help, mailman3 is up and running for me on two servers with three lists, and they all work as far as I can see. I'm sending out invitations to users tomorrow. Yayy. Up until today, I had been stuck using a plugin in Joomla, which was not the best solution. I'm tickled pink, and my users will be, too. Now I'm just playing and tinkering a bit. I'd like to delete all my archives that are more than a certain age, e.g. more than a week old. I can easily do that with a cron job, deleting old files in /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* which is, as far as I can see the only place archive emails live. However... I was wondering if there was some mailman command or config variable that would accomplish this without using cron. billo

3 years, 3 months

[MM3-users] Re: best pratice - set default MM settings and make them update-save

by Mark Sapiro

On 5/16/22 07:16, Stefan Bauer wrote: > > Is there also a way to have this box checked by default or do not request a > verifcation at all? > Could not find any flag in base.py. To have the box checked by default would require a patch to Postorius like this. ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1073,7 +1073,7 @@ class ListMassSubscription(forms.Form): pre_verified = forms.BooleanField( label=_('Pre Verified'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, users will not have to verify that their ' ``` Not requiring verification at all would require patching Mailman core but would be a bad idea as it could allow someone to subscribe anyone without that person's consent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: SOLVED was --- Re: Re: Debian 11 mailman3 installation question

by Stephen J. Turnbull

William Oliver writes: > There were a couple of gotchas, but not too bad. Happily, the > README.debian and a few web pages fleshed it out. I didn't really expect turnkey.... Too many independently configured packages (webserver, Django, wsgi provider, MTA, on top of probably about 5 Mailman packages and dependencies). > The only thing is that the packages put a lot of stuff in places different than the > manual installation tells you to do, so I had to keep poking around to > find stuff. There's a dpkg command that lists what's installed by a package. Probably it's accessible from apt. That plus grep -E '.cfg|settings.py|template|log|queue should get a list of most of what you need to deal with. Someday I should collect a few of those for the popular distros and/or package managers. Steve

2 years, 6 months

[MM3-users] Re: export/import list?

by Dave McGuire

On 8/22/23 17:59, Mark Sapiro wrote: >> I'm moving from sqlite3 to postgres; I can handle that migration. >> But I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone >> else) know of any schema changes? I spot-checked the first few and >> they looked the same, but before going through all of them I figured >> I'd just ask here. > > Schema changes are handled automatically by alembic. The migrations are > defined in /mailman/database/alembic/versions/. Your current version is > is stored in the database in the alembic_version table. When Mailman > core is started, all migrations from your current version to the latest > version will be applied to bring your database up to date. I.e., you > don't need to be concerned about schema changes upon upgrade. They are > handled automatically. Brilliant! Thank you Mark. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

1 year, 8 months

[Test] Re: Down time.

by Mark Sapiro

On 03/18/2016 05:47 PM, Mark Sapiro wrote: > Later this evening (maybe March 19 02:00 UTC) I will be attempting to > reconfigure things to use the gitlab master branches of MailmanClient, > Postorius, HyperKitty and the HyperKitty-Mailman plugin in addition to > using gitlab master branch of Mailman itself which is already the case. > > This will probably involve down time and/or anomalous behavior. I got distracted with things like dinner and all, and I'm doing a lot of it outside the working (to the extent that it is) install, but I'm getting close. The good news is I should be able to stop services, switch over and start and it will live or die, so total down time should be maybe 15 minutes or less, but i won't be ready until more like 04:30 or 05:00 UTC. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Redundant and load balanced Mailman3

by Pawel Grzywaczewski

Thanks Abhilash, I'm a bit confused about dependency on local files? You mean files that are created when an e-mail is processed? So where is the problem with redundancy? If this host is gone there will be another Mailman deployment able to deal with the load. What about having 3 VM where all components of Mailman are installed. Those VMs connect to 1 database on a remote host. We deploy HAProxy in front of 3VMs. So as the result all requests (HTTP/SMTP) are distributed to 1 VM (out of 3). A given VM handles a request HTTP or SMTP, and if there is a problem (or very high load of SMTP) there are still 2 other VM that can do the job. So perhaps the question is: can we plug 3 Mailman instances into 1 DB? Is Mailman software developed taking into account that several Mailman instance writes to the same database at the same time? Cheers, Paweł

4 years, 7 months

[MM3-users] Re: Something wrong in Django admin interfaces

by Mark Sapiro

On 7/21/23 01:39, Franklin Weng wrote: > > When I clicked any features like users, Mail domains, Failed tasks... > anyone, no matter New or Change, the web page was covered by the first > page. All the configuration fields/labels are covered by the first page. > > Please see the screenshot: > > https://nextcloud.slat.org/index.php/s/e5KKEEbqDK6DpiN > > https://nextcloud.slat.org/index.php/s/nLgMRQ9ACyxCwoc > > It was not able to do the administration tasks. I can't see your screen shots; the connection times out. However, this is not a Mailman issue. The Django web admin interface is part of Django. See <https://docs.djangoproject.com/en/4.2/ref/contrib/admin/> This issue should probably be reported to Debian if it is a Debian package issue, or possibly to Django. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

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

by Odhiambo Washington

On Fri, Apr 26, 2024 at 8:30 AM Thomas Stein <himbeere(a)meine-oma.de> wrote: > Am 2024-04-26 00:52, schrieb Mark Sapiro: > > On 4/25/24 14:01, Thomas Stein wrote: > >> Am 2024-04-25 22:03, schrieb Mark Sapiro: > >>> > >>> I don't know how things are arranged in the Debian/Ubuntu package, > >>> but you may have a settings.py which at the end does something like > >>> ``` > >>> try: > >>> from settings_local import * > >>> except ImportError: > >>> pass > >>> ``` > >>> If that is the case, adding the above snippet to the end of > >>> settings_local.py should work. > >> > >> Yes, that's the case. I added the snippet in question to > >> settings_local.py but this leads to another error: > >> > >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> > >> from settings_local import * > >> File "/usr/share/mailman3-web/settings_local.py", line 194, in > >> <module> > >> x = list(MIDDLEWARE) > >> ^^^^^^^^^^ > >> NameError: name 'MIDDLEWARE' is not defined > >> dpkg: error processing package mailman3-web (--configure): > > > > Yes. I understand. In your case, MIDDLEWARE is only defined in > > settings.py and not in settings_local.py. As I understand it originally > > you added > > ``` > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to settings.py and you say it didn't help. I don't know why that > > wouldn't work as long as there is no setting for MIDDLEWARE in > > settings_local.py and you added that after the MIDDLEWARE setting in > > settings.py. > > When you say it didn't help, do you mean you still get the > > > > django.core.exceptions.ImproperlyConfigured: > > allauth.account.middleware.AccountMiddleware must be added to > > settings.MIDDLEWARE > > > > message or something else? I note that the original post in this thread > > refers to /etc/mailman3/mailman-web.py which is presumably where the > > package ultimately puts the Django settings, and I don't know what > > `dpkg --configure` is doing. > > > > One thing you could try is in settings_local.py, put > > ``` > > from settings import MIDDLEWARE > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to work around the NameError. > > After that I get: > > File "/usr/share/mailman3-web/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' > (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > > I guess I'll wait for the new package for now. > How about adding: MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) in settings_local.py And how about you use the virtualenv method <https://docs.mailman3.org/en/latest/install/virtualenv.html> for more peace of mind in the future? -- 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]

11 months, 4 weeks

[MM3-users] Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

7 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/23/20 9:37 AM, Brian Carpenter wrote: > > How would a person already be a core user outside of a registration with > Affinity? Via a list subscription or the import21 script? Yes, or even just by sending a post to a list as a nonmember. Everyone who is or has been a member, non-member, owner or moderator of a list has a user and one or more address records in Mailman core. > I do want to apologize for my tone Mark. I was wrong in the way I communicated. Apology accepted. I understand that it can be frustrating to be dependent on something you don't control and that this can sometimes lead to "anomalous" behavior. Here's a take on this that is intended to be humorous, but is actually quite frightening. https://xkcd.com/2347/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 4:29 PM, Mark Sapiro wrote: > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. This is a bug with Affinity which I have scheduled to be fixed. However I am confused. Data is completely removed from Mailman 3 core when you delete the account via Postorius but not when you unsubscribe from a list? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

[MM3-users] Re: E-mail every minute: "Cron <www-data@sharky5> ..."

by Mark Sapiro

On 7/7/24 6:11 AM, Robert Heller wrote: > What am I missing? I *think* I have mailman3 *mostly* setup, but there are > still some configuration things that are missing, but I am not sure how to fix > them (the docs are NOT clear). I am getting an e-mail *every* minute that > looks like: ... > /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. Set something like ``` # Set retry > timeout. Q_CLUSTER = { 'timeout': 300, 'retry': 360, 'save_limit': 100, 'orm': 'default', } ``` in your settings_local.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Howto: Mass import of nonmembers in several lists?

by Paul Paulchen

Hi MM3 community, got a, perhaps easy question. Following situation, got 8 lists and up to 20 nonmember users missing to the list. The massimport with postorius is only for members, as far as I can use it (Postorius Version 1.3.4). So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. I thought so, because the import21 command did this as well when we migrated to mailman3. I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! Hope I explained my case properly. I appreciate your responds! Thanks in advance. - Paul

3 years, 3 months

[MM3-users] Re: Hyperkitty shows "<" as <

by Mark Sapiro

On 4/5/23 07:39, Andreas Schamanek wrote: > > The function that handles it is escapeemaillinks() in > templatetags/hk_generic.py (at line 111 in my version). > > Adding `.replace("&","&")` to the return value fixes the rendering > of email addresses (at least for me). escapeemaillinks(text) searches text for strings like <a href="mailto:user@example.com>xxx</a> and replaces them with user(a)example.com thus replacing everything from `<a href=` through `</a>` with just the email address with `@` replaced by `(a)` However, text is the whole message body, so what you are doing is just replacing `&` with `&` in the message body, but only when escapeemaillinks(text) is invoked. Also, this is all changed in HyperKitty 1.3.5 with the addition of optional markdown rendering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: export/import list?

by Mark Sapiro

On 8/22/23 2:38 PM, Dave McGuire wrote: > > I'm moving from sqlite3 to postgres; I can handle that migration. But > I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone else) > know of any schema changes? I spot-checked the first few and they > looked the same, but before going through all of them I figured I'd just > ask here. Schema changes are handled automatically by alembic. The migrations are defined in /mailman/database/alembic/versions/. Your current version is is stored in the database in the alembic_version table. When Mailman core is started, all migrations from your current version to the latest version will be applied to bring your database up to date. I.e., you don't need to be concerned about schema changes upon upgrade. They are handled automatically. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

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

by Arte Chambers

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. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Mon, Nov 4, 2024 at 4:51 AM Odhiambo Washington via Mailman-users < mailman-users(a)mailman3.org> wrote: > On Mon, Nov 4, 2024 at 12:36 PM Gerald Vogt <vogt(a)spamcop.net> wrote: > > > On 04.11.24 09:13, Odhiambo Washington via Mailman-users wrote: > > > On Mon, Nov 4, 2024 at 10:34 AM Gerald Vogt <vogt(a)spamcop.net> wrote: > > >> On your server it looks like this: > > >> > > >> # ls -la /etc/mailman3 > > >> total 28 > > >> drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . > > >> drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. > > >> -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf > > >> -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg > > >> -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg > > >> -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py > > >> > > >> and it works just fine. > > >> > > > > > > True, but making the mailman user own the files makes life easier when > > you > > > operate from the virtualenv - > > > you do not have to exit the virtualenv to edit the files in > > /etc/mailman3, > > > and then re-enter the virtualenv. > > > > The virtualenv doesn't change the current uid. That doesn't make a > > difference. > > > > > You do not have to give the mailman user sudoer rights. That's the > whole > > > point about the below: > > > > > > ``` > > > sudo mkdir /etc/mailman3 > > > sudo chown mailman:mailman /etc/mailman3 > > > sudo chmod 755 /etc/mailman3 > > > ``` > > > > Well, that essentially was my question: why does the mailman user > > require sudo rights? > > > Mark did not say that the mailman user required sudo access. Please re-read > what he said. > > > > Why does it need to be able to write or change > > those files/directories? Except for the convenience which isn't a reason > > to weaken security. > > > > Make me understand how the security is weakened. The Mailman user account > has no password so cannot login from outside. > Even if it was able to login, it will still end up only accessing $home and > /etc/mailman3, no? > > > > In respect to security, i.e. separation of the service user from write > > access to it's core configuration files, it should not be done unless > > absolutely necessary. > > > Sorry, I didn't understand that. > > > -- > 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] > _______________________________________________ > 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 paul.m.robey(a)gmail.com >

5 months, 1 week

[MM3-users] docker setup

by epi＠epinux.com

Hi, attempting to install mailman3 on a remote ubuntu server - my docker-compose file looks like: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a /opt/mailman/core/mailman-extra.cfg ``` [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.1.1 lmtp_port: 8024 smtp_host: 127.0.1.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg ``` opt/mailman/web/settings_local.py ``` EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '127.0.1.1' EMAIL_PORT = 25 USE_SSL = False DEFAULT_FROM_EMAIL = "mailman(a)lists.libkml.org" SERVER_EMAIL = "mailman(a)lists.libkml.org" DEBUG = True ALLOWED_HOSTS='libkml.org' ``` I know I am still missing the NGNIX/APACHE settings, but trying to access the service at: libkml.org:8000 I get a django error Invalid HTTP_HOST header: 'libkml.org:8000'. You may need to add 'libkml.org' to ALLOWED_HOSTS. but I have the 'libkml.org' to ALLOWED_HOSTS in both `opt/mailman/web/settings_local.py` and in the dockerfile: https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… https://gist.github.com/epifanio/e668b0b7f3709de8063661d947223e2a#file-mail… Can you help me please to understand what I am doing wrong? Thanks!

2 years, 9 months

[MM3-users] Re: Sanity check of upgrade procedure

by Mark Sapiro

On 10/26/22 17:30, David Newman wrote: > > 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. Was the venv initially created as the `mailman` user? Maybe sudo chown mailman:mailman /path/to/venv will fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Moderating posts via email

by Mark Sapiro

On 10/26/2017 02:21 PM, Dmitry Makovey wrote: > > after which we've used above password trying to approve messages > following the steps outlined above. > > What are we doing wrong, or where to look for further information? Are you replying to the outer message or to the message in the attached message/rfc822 part that contains the If you reply to this message, keeping the Subject: header intact, ... text? You don't actually have to 'reply' to anything, but your message with the 'Approved: password' actual header or first body line must be sent To: the list-request address with Subject: confirm <token> (possibly preceded by 'Re: ' or similar. If you reply to the attached message/rfc822 message, it should work. If you reply to the outer message it won't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Broken web UI after upgrade

by Mark Sapiro

On 12/14/22 08:15, Odhiambo Washington wrote: > After upgrading MM3 and running all the post-update tasks and even > re-indexing all the posts, I have ended up with a somehow "broken" > hyperkitty. > The archives display on a browser six, to say the least. > The site is public, so I can share the link: https://list.rc.org/archives/ > > What should I do in order to fix this? > Are you asking about the lack of style or the "No archived list yet."? The former indicates an issue in your web browser with accessing the `static` directory or an issue with the django admin collectstatic or compress commands. I don't know about the latter - could it be because all the archives are private and I'm, not logged in? -- 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: Problems after upgrading from bullseye to bookworm

by Mark Sapiro

On 6/26/23 12:35 PM, Ken Alker wrote: > I'm brand new to this, so take this with a grain of sale, but, I had a similar problem a few days ago, however, mine was "flufl.i18n>=3.2". Perhaps the same thing is happening with flufl.lock (but that didn't bite me). > > I solved my problem by following this: <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately modifying "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt" per that thread (see <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by Thomas Ward section called "The WORKAROUND"). Maybe you need to do the same thing, but for flufl.lock. Yes, the same issue now affects flufl.lock as well as flufl.i18n. You will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Any possible way to reduce robot spam accounts?

by Mark Sapiro

On 7/20/23 20:42, Franklin Weng wrote: > > Thank you. When I set it in my settings_local.py, I clicked register > and got an error: > > ModuleNotFoundError at/accounts/signup/ > No module named 'django_mailman3.views.user_adapter' > > (In the document the path is /etc/mailman3/settings.py but I installed > it with Debian packages so I guess the path is somewhat different, and I > thought setting in setting_local.py should work too. It seems work > since it gave me the error above.) > > Do I have to install something else? Or disable some other options? What is the version of django_mailman3 in your Debian package? As it says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for these settings to work." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Sibling lists in Mailman3

by Markus Grandpre

Is there an equivalent approach to implement sibling lists in Mailman3? Best regards, Markus Grandpré Am 3/28/24 um 16:06 schrieb Markus Grandpré: > Thank you. > > Am 27.03.24 um 17:26 schrieb Mark Sapiro: >> On 3/27/24 08:05, Markus Grandpre wrote: >>> >>> after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or >>> something similar) in Mailman3. How are sibling lists treated in Mailman3? >> >> The sibling list features do not exist in Mailman 3. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year

[MM3-users] mailman3 admin from mailman2 & File location questions

by bob B

Question1 We use help users with list settings, so we would log into mailman2 with the master password. So what is the best way to duplicate this for mailman3. I assume I can just use the admin account and share that password with my other admins. But I see the domain owners, but is that working? I added someone as a domain owner, and they do not see private email lists and it looks like that can not edit any list settings? There was a post that this had not yet been implemented? Any other options? Question2 Where are all the emails/archives stored? are they in /opt/mailman/...., or are they in the database? For mailman2 we had mailman located on a large volume to handle archives, just trying to see if that is the same for mailman3 or if all the data is now in the database (which will be external for our installation)?

3 years, 5 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/27/22 05:22, Stephan Krinetzki wrote: > > I think there is a communication problem in the chain: > > apache -> uwsgi -> mailmancore/API ->database > > but i can't dig deeper there. Let me know if i should provide more details or logs It seems that this part of the chain apache -> uwsgi -> mailmancore/API is not experiencing delay. It is involved with every Postorius request, most of which seem to have no issues. It is only this one piece mailmancore/API ->database that seems to have an issue and only with this one DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX query. However, like you, I have no idea as to what you could do further to debug this. -- 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: Hyperkitty import from mailman2

by Sten Aus

Hi Thank you Mark and Simon for your input! I can see imported list from Hyperkitty GUI, but it's inactive. I can confirm that I can see those emails from command line (python shell shows Email Objects). Import shows everything is OK: # python2 manage.py hyperkitty_import --settings settings --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox Only emails after 2010-01-01 00:00:00+02:00 will be imported Importing from mbox file /tmp/test.mbox to test(a)list.domain.com /--some 22 emails being imported here --/ 22 emails read 22 email added to the database 22 emails are stored into the database Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. # python2 manage.py update_index --settings settings Indexing 50 emails NB! Only 6 of them are archived from new list (which has been created from Apache). I have imported 2 times 22 emails from /tmp/test.mbox file (to different lists). I am using Apache2.4 with mod wsgi and Postorius and Hyperkitty are in the same django application. Also tested with running server directly and then connecting to a port 8000, but I guess it does not matter, because both of them are using Python script. I have not yet managed to set up cron tasks, as this is relatively new installation, but I have ran them manually. Also, I have done update_index (runjob update_index and manage.py update_index, both ways). SQLite database shows emails, for example there's a thread FMXQVFDRQVRMINVXI4DJB4SHYTJ3EPWP, but If I insert it to web URL I get Django error: No Thread matches the given query. As Postorius and Hyperkitty are in the same Django, they share sqlite database (mailman/web/database.db). Mailman has it's own database in mailman/var/data/mailman.db. Happy holidays Sten On 22/12/2017 21:09, Simon Hanna wrote: > On 12/22/2017 03:39 PM, Sten Aus wrote: >> Hi >> >> I have installed mailman3 - it looks very great! >> >> Now I wanted to try import from mailman2 mbox, so i did: >> >> python2 manage.py hyperkitty_import --settings settings >> --ignore-mtime -v 3 --since 2010-01-01 -l test(a)list.domain.com >> /tmp/test.mbox >> >> It shows that it have sucessfully imported all emails and I can see >> them from database (sqlite3), but I cannot see them from GUI >> (hyperkitty). Only thing I can see is this inactive "test" list. >> > How did you try to access them using Hyperkitty? Can you try doing > that while logged in as a django superuser? Could you try using a > permalink for a message? If you can access the files from the database > you should be able to construct the urls using the list name and the > message_id_hash of a message. You should try this using DEBUG=True in > the settings.py. The URL would be similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… > > > Another option would be to check if you can access the data using a > python shell. > > `python manage.py shell` to open a python shell preconfigured for > Hyperkitty and then input the following two lines: > > from hyperkitty.models.email import Email > Email.objects.all() > > > This should print out all the messages that are stored in the > database. (You can limit them by appending "[10:]", or any other > python slice) > > What do you see in the UI? Is it somewhat similar to > http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 4 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

What happened to the maintainer? This is an increasing problem these days. On Sat, 13 Mar 2021 05:00:50 -0500, Bernd Wurst wrote: > > > Hi. > > Am 13.03.21 um 04:36 schrieb John Covici: > > Hi. I am having a great deal of difficulty installing mailman3 using > > gentoo and sendmail. > > Mailman in gentoo is kind of maintainerless (will be in a few > days, I suppose) and so this method can not be recommended. > > We installed using pip in a regular useraccount. > > regards, > Bernd > _______________________________________________ > 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/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 1 month

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 01:55, Élodie BOSSIER via Mailman-users wrote: > Thank you for your response Mark, > > With Mailman 2.1, the lists were split on their webpage respectively. > How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? > > My domain table SQL have this result : > id, mail_host, description, alias_domain > 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr > 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr If you go to https://example.com/mailman3/domains/ (the Domains view in Postorius) you will see at least two entries, one with Mail Host ml.franceserv.fr and one with Mail Host ml.viticreation.fr. What are the Web Host entries for these? You should have two separate site entries in the django_site table (https://example.com/admin/sites/site/) for these domains. -- 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: Disabled by bounce

by denise.mcgeachy＠gov.bc.ca

Hi all - new to this forum but am trying to work out a similar issue raised by a list member's IT department. I'm a bit out of my depth here and hoping you all can help. They have recommended: - When the mailing list relay an email from a member of the list to other members, the email from address should be the mailing list and not the user sending the original email. For example: list-name(a)mydomain.ca (on behalf of Sally Brown) - The mailing list should not modify the original email and thus breaking the DKIM signature I have clicked the DMARC mitigation unconditionally option which seems to solve the second point but haven't managed to have it sent by the list name but not as suggested in the first point. I either get "my email via list(a)mylist.ca" or list(a)mylist.ca" Is anyone aware of a setting to do this? Many thanks d

2 years, 2 months

[MM3-users] Problems with mailman core translation and other details

by Stephen J. Turnbull

celi--- via Mailman-users writes: > Everything almost OK, except from the fact that none of mailman's > core email messages are being translated, even though mailman.po > shows the right messages. Did you restart mailman? Have you changed the default language in mailman.cfg? I don't know how Debian may have altered the configuration mechanism, but they usually do. It's possible they've changed file locations or added "conf.d" capabilities or something like that to make their automated management tools work. > Also, strange things happen to these .po files. The web interface > is almost perfect, but some messages (just some) are not correct - > although the corresponding django.po appears to be OK. It´s the > case below: the pair msgid/msgstr seems to be OK, but this > particular sentence is not being translated. Since this is Django, have you run "mailmanweb compilemessages"?

1 year, 2 months

[MM3-users] Re: Problems with New MM3 Installation

by Abhilash Raj

On Tue, May 11, 2021, at 8:43 PM, Mark Sapiro wrote: > On 5/11/21 7:46 PM, Jeff wrote: > > > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > > > 1) some emails that arrived before I got the archive working are still sitting in: > > > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > > > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > > > /usr/local/mailman3/mm/var/queue/shunt > > > > What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > > > 3) Similar to above, some messages are in: > > > > /usr/local/mailman3/mm/var/queue/bad > > > > How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > > > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. Using the full external URL should work. Core doesn’t speak uwsgi protocol so the uwsgi:// URL won’t actually work. I am starting to think it was a very bad idea to use uwsgi in the official docs :( -- thanks, Abhilash Raj (maxking)

3 years, 11 months

[MM3-users] Re: MM3 gateway errors and frequent reboot needs

by Mark Sapiro

On 4/19/20 1:21 PM, hansen(a)rc.org wrote: > We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? We are not seeing an issue like this on either lists.mailman3.org (this list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) What are you seeing in web server logs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Andreas Barth

* Johannes Rohr (johannes(a)rohr.org) [210314 18:30]: > Please excuse me, if this has been discussed before and I missed it, but > what is the added value of going through the trouble of manually > installing mailman3, rather than doing a simple apt install > mailman3-full? I would assume that in most cases, a well maintained > package is preferable, because it makes life easier. Are the Debian > packages for Mailman3 in some way deficient? As always, packages in Debian stable are not as new as the latest git checkout. So, if the stable version work for you: great. If you want to have something newer, either try the packages from testing / unstable, or some checkout from git. If you want to improve the code, git checkouts are of course also preferred. Of course, this is true not only for mailman3, but also for exim, kde, gimp, whatever. Andi

4 years, 1 month

[MM3-users] Re: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 09:18, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > this is with "Postorius Version 1.2.4" (as installed by the mailman3 > Debian package). The Debian packages are OK for people who want to install things via a package manager, but they are quite out of date. Something like the following in `mailman shell` can do it. ``` >>> # Cutoff date delete pended subscriptions older than this >>> cutoff = '2022-03-01' >>> pendings = getUtility(IPendings) >>> # Prior to Mailman core 3.3.5 need to explicitly delete workflow >>> wfm = getUtility(IWorkflowStateManager) >>>for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['when'] >= cutoff: ... continue ... pendings.confirm(token, expunge=True) ... # for MM < 3.3.5 ... wfm.discard(token) ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: File in /var/lib/mailman3/queue/bounces/

by Mark Sapiro

On 12/11/21 6:29 PM, Andreas Barth wrote: > > in my local installation there is a file in > /var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how > to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in > queue/bounces and now queue/shunt. I suspect the issue is that bounce runner is not running. If you grep Mailman's mailman.log for `bounces` I suspect you will see that it has died and not restarted. You may or may not find additional information in the log as to why it died, but in any case restarting Mailman should start everything again. The master should restart it when it dies, but this is https://gitlab.com/mailman/mailman/-/issues/898 for which we don't have a satisfactory fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Importing users and mas settings "Moderation Action"

by bob B

I imported email lists and users to version 3 from version 2. One of my lists all the users are set to 'Hold for moderation" for "Moderation Action". I assume this is because they were set to moderation on mailman 2? But if I mass subscribe users via the Gui in mailman 3 then their default "Moderation Action" is set to "none" so I assume it follows list default, is that a correct assumption? I believe there is no way to import mass users and set their "Moderation Action" at the same time is this correct? Wasn't that possible in mailman 2? is there a way to change all their user's "Moderation Action" for a list in bulk? So it looks like for any users I mass subscribe, "Moderation Action" will be set to "none" and if I want to change that I have to do it manually for each user?

2 years, 11 months

[MM3-users] Re: Postorius -owner messages

by Mark Sapiro

On 6/15/23 13:47, ssehi--- via Mailman-users wrote: > > They'd like to disable owner delivery for themselves, and I'd like to not make the change for them using the shell every time I get one of their requests. We have a Postorius front end set up and working, but it doesn't appear that disabling delivery using the List-based preferences in the Postorius interface stops those Owner communications. Is there a way to allow users to disable that natively in Postorius? No. In Postorius you can set the delivery status for members and non-members, but you can't set it for owners or moderators. Owners and moderators do have a delivery_status which will control whether they receive notices sent via the listname-owner address, but it is not exposed or settable in Postorius. -- 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: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Brian Carpenter

On 2/26/21 10:00 PM, Stephen J. Turnbull wrote: > Thank you for going to the trouble of making your guide easily > available to and usable by the community. You're welcome Steve. > 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. I agree. I just know there are probably a lot of folks who just want a working and current Mailman 3 server and are not picky over the actual server environment. Mailman 3 is really dependent upon being connected to a number of services: web server, database server and MTA for instance. Then you add in all of the required Python modules, and you have a really complicated system that has a lot of moving parts. I intend to explore other OS for installing MM3 and to document that process as well. I will not document the process of using package managers (apt/yum) etc to install Mailman 3 itself because I think it is very problematic having older versions of Mailman 3 set up. Mark Sapiro put it very well when he said: > Mailman 3 is still relatively young and there are many important > features and fixes in the current releases that aren't in the > Debian/Ubuntu packages. I hoping a guide such as mine will move folks away from using a Debian repo for Mailman installations. > 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. See that is something I am very interested in fixing and cleaning up but I need help in knowing how to work with something like Readthedocs.io. > 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. Exactly! > > > 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. So lift me up and throw me over that hurdle. > 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. "Raises hand here" -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 1 month

[MM3-users] Re: Default values for lists in Mailman 3

by Markus Grandpré

Dear Mark, dear list, in Menu "Mass Operations / Mass Subscription" I have set the default value for checkbox "Invitation" in file </usr/lib/python3/dist-packages/postorius/forms/list_forms.py> (on Debian 12) as you had suggested: invitation = forms.BooleanField( label=_('Invitation'), initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' 'be sent an invitation to join the list and will be subscribed ' 'upon acceptance thereof.' ), widget=forms.CheckboxInput(), ) However, administrators of mailing lists on our Mailman3 demo system report that the invitation is still sent, even if they have deactivated the sending of the invitation via the “Invitation” checkbox. What have I done wrong? Best regards, Markus Am 20.09.24 um 09:05 schrieb Markus Grandpré: > Thank you very much for your answer. > > Best regards, > Markus > > Am 19.09.24 um 22:03 schrieb Mark Sapiro: >> On 9/19/24 05:46, Markus Grandpré wrote: >>> Dear list, >>> >>> I would like to activate the invitation setting for all lists as >>> default. In Mailman 2.1 I have done this in the file </etc/mailman/ >>> mm_cfg.py>: >>> >>> >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> >>> >>> How can I do this in Mailman 3? >> >> There is a draft merge request at https://gitlab.com/mailman/ >> postorius/-/merge_requests/930 which implements a framework for >> setting Postorius defaults and creates a setting to set the default >> for pre- verified on the mass subscription page. Once merged, this can >> easily be extended to provide a default for Invitation. >> >> In the mean time, you can only do this by patching src/postorius/ >> forms/ list_forms.py like >> ``` >> --- a/src/postorius/forms/list_forms.py >> +++ b/src/postorius/forms/list_forms.py >> @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): >> >> invitation = forms.BooleanField( >> label=_('Invitation'), >> - initial=False, >> + initial=True, >> required=False, >> help_text=_( >> 'If checked, the other checkboxes are ignored and the >> users will ' >> ``` >>> Can I also transfer other default values like: >>> >>> ... >>> DEFAULT_SERVER_LANGUAGE = 'en' >>> DEFAULT_SEND_REMINDERS = 1 >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> DEFAULT_PRIVATE_ROSTER = 2 >>> DEFAULT_ARCHIVE = Off >>> DEFAULT_ARCHIVE_PRIVATE = 1 >>> ... >>> >>> from the very same configuration file to Mailman 3? Is there a >>> documentation of the default values for lists in Mailman 3? >> >> This is done by creating a list style with the desired defaults. See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/ >> styles/ docs/styles.html for documentation of styles and see https:// >> gitlab.com/ mailman/example-mailman-plugin for an example of creating >> a plugin in Mailman core to make a persistent style. >> >> There is no specific doc for the list settings. You need to look at >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/ >> base.py for the various settings and https://gitlab.com/mailman/ >> mailman/-/blob/master/src/mailman/styles/default.py to see which >> default classes are applied for various styles. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

6 months, 3 weeks

[MM3-users] Re: Unknown attribute: max_message_size

by Abhilash Raj

Hi Thor, On Wed, Dec 6, 2017, at 02:40 AM, Thor Atle Rustad wrote: > If I make changes here: > https://example.com/postorius/lists/test2.example.com/settings/message_acce…, > I get a warning that the Maximum Message Size field at the bottom is > mandatory. However, if I put a number in that field and save, I get > "Unknown attribute: max_message_size". That makes sense, since Mark > states > in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that max_messages_size is not exposed in REST. I have opened a new issue for this, turns out this was fixed but isn't a part of the 3.1.1 bugfix release of COre. https://gitlab.com/mailman/postorius/issues/246 > What to do? > > I have Maxking mailman-docker but can easily copy files into the image if > necessary. > > Thor > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 4 months

[MM3-users] Re: Mailman3 on Debian 10

by Mark Sapiro

On 1/30/20 8:24 AM, Bala Mutyam wrote: > Hi Mark, > > Thanks for the update and I managed to resolve the errors on the UI. > > I have 2 more questions about the mailman3. > > 1) how to create Mailing Lists? You can create lists with the `mailman create` command lint tool or via Postorius as a superuser. > 2) super user login is not working even with correct login credentials and giving me - The username and/or password you specified are not correct. How did you create the super user? You should do it with the django admin createsuperuser command. > 3) Password Reset Email urls and email confirmation web pages giving me - This site can't be reached error. If this is an error from your browser, there is something wrong with the host portion of the URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

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

by Jens Günther

Hey there, I'm using Apache2 as the webserver, configured https://mailman.xyz.de as Web host. When I want to get to Mailman Starting Page now I need to Enter the following URL: https://mailman.xyz.de/mailman3/ to be directly redirected as expected to https://mailman.xyz.de/mailman3/postorius/lists/ -> works. Problem: When leave out the slash at the end and I ONLY enter the following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly redirected to a page, taht does not exist: https://mailman.xyz.de/mailman/postorius/lists/ -> 404 Where can I change this misbehaviour? In Apache-conf everything seems as it'S in the docs, for the vHost I do not have any other custom settings. Thank you in advance. By the way: Is there an easy way to redirect directly from https://mailman.xyz.de to https://mailman.xyz.de/mailman3/postorius/lists/ -> what would be a possibility for that?

4 years, 1 month

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

by dancab＠caltech.edu

Mark Sapiro wrote: > On 11/7/21 1:22 AM, Stephen J. Turnbull wrote: > > dancab(a)caltech.edu writes: > > I deployed Mailman3 last night and today we've had some "bounced" > > messages with headers referencing mailman(a)example.com. This has > > only happened with a few lists. Any ideas what causes this? > > ... > > Mark may have a better idea. > > This is a fake DSN that is generated when Mailman's attempt to send a > bounce probe results in a failure from the MTA to which Mailman > delivers. See code at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... > and around > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... We do have mailman(a)caltech.edu configured with valid members/owners. We're using Postfix for the MTA. Is it possible there's a misconfiguration there? We've been testing the system with a handful of lists for months. -- Dan

3 years, 5 months

[MM3-users] Warning on EL8: django-mailman 1.3.12 prefers Django 4.2 which requires Maria DB>10.4

by Jered Floyd

A heads-up for anyone else on RHEL 8, because the error is mystifying. django-mailman 1.3.12 bumps the preferred django version from 4.1 to 4.2. Django 4.2 requires MariaDB 10.4 or later. RHEL 8 has full lifecycle support for MariaDB 10.3. For some reason I haven't yet been able to identify, this causes pyMySQL integrations to fail with the mysterious error: django.core.exceptions.ImproperlyConfigured: mysqlclient 1.4.3 or newer is required; you have 1.4.6. (Yes, Database.version_info contains "(1, 4, 2, 'final', 0)" while Database.version contains "1.4.6" and I am totally stumped where that 1.4.2 is coming from as it appears... nowhere.) Bypassing that error check gives the more informative: django.db.utils.NotSupportedError: MariaDB 10.4 or later is required (found 10.3.39). Doing a pip install with django\<4.2 works. This is not ideal since 4.1 is past LTS, so I would recommend that Mailman systems be migrated to RHEL 9. --Jered

1 year

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

by Odhiambo Washington

On Thu, Aug 8, 2024 at 11:19 AM IEM Network Operation Center (IOhannes m zmölnig) <noc(a)iem.at> wrote: > On 8/7/24 12:27, Odhiambo Washington via Mailman-users wrote: > > On Wed, Aug 7, 2024 at 11:52 AM IEM Network Operation Center (IOhannes m > > zmölnig) <noc(a)iem.at> wrote: > > > >> is a feature-request warranted, or am i worrying too much? > >> > > > > A feature to automate your migrations? Have you consulted ChatGPT yet? > :-) > > > > should i ?-P > > anyhow, i'm happy to say that my migrations have completed by now, and > my new instance is now running with mailinglists previously hosted on > either an MM2 instance or an older MM3 instance. > so far i have not discovered any problems (well, apart from xapian > eating all my (rather small, as this is only a VM) partition; but that > is of course not related to anything we discussed here). > > what i did was in a nutshell: > - create a dump of the database of the old mm3 instance (e.g. 'pg_dump > -Fc mailman3web') > - drop any existing databases from the new mm3 instance > - import the dump into the new instance > - run db migrations > - import pck files from the old mm2 instance > - import archives from the old mm2 instance > > > thanks again, Odhiambo and Mark for your hints! > > > > however, i can report that my fears about migrating between mm3 > instances by means of DB dumps have (at least partially) become true. > 0. i'm using mailman3 as packaged in Debian, and PostgreSQL as the > backend. before running the actual migrations, i've experimented a bit > on the new instance (creating and deleting test lists), to see if the > core configuration is working as expected. so i already had the > databases up and running, filled with a bit of data, before attempting > the migrations. > > 1. for whatever reasons, the db-names have changed between 3.2.1 > ("mailman3", "mailman3web") and 3.3.8 ("mailman3.db", "mailman3web.db"). > i strongly suspect that this is a problem of the Debian packaging of > mailman3 (i'm pretty sure that i only ever accepted the defaults when > installing the mailman3 Debian packages). > As you've rightly discovered, that issue can only be addressed by the Debian package maintainers. > 2. since the db names changed, i tried to be clever (but i'm not a > knowledgeable postgreSQL admin) and tried to only import the data-part > of the dump ("pg_restore --data"), re-using the existing tables. > this of course miserably failed. > I suspect failed because of the schema differences from 3.2.1 to 3.3.8. Well, I am also NOT experienced with PgSQL administration, but I think that for data to be imported from one table to another, the column definitions MUST match. 3. my next attempt to import the data into an existing DB, was to rename > the new db to the old name, import and rename back. > this also failed miserably, most notably because the import insisted on > assigning key IDs that were already in use. (that is: because i had > already created and tested test-lists, the new instance already > contained an email with hyperkitty_email.id=1; the dump from the old > instance also contained an email with hyperkitty_email.id=1; so the > import failed. this example is made up from memory, as i have not kept > all the error logs). > so this also failed. > That is expected. Maybe you could have vacuumed the tables completely. 4. i ended up, deleting the entire database, and import it from scratch. > after that, ran 'mailman-web migrate' to update the DB schema to the > current one. > this again failed with one hyperkitty-related migration that would > create new tables. > it turned out, that the new hosts uses postgreSQL-15.7.0 (the old one > uses postgresql-11), and afaik since psql15 only a database *owner* can > create new tables. after i made my mailman3-db-user the owner, all > migrations succeeded. > That's a known issue here already. Something to do with access privileges to the SCHEMA public. > 5. finally i imported my mm2 mailinglists and archives, which went > rather smoothly. > Sure. The only issue people have had with that was to do with some small inconsistencies in the archives. There is a tool that can be used to check the archives and fix such. some of my problems obviously come from me not being a DB-manager by > profession (e.g. new constraints in psql15,...) > but others, like "3.", seem to hint at a core problem in the suggested > migration strategy: if the to-be-imported db contains unique-keys that > are already taken, the import simply fails (or at best, you get a > partial import). i do not see how such a migration can ever work if you > try to merge to mm3 instances where the dbs have a considerable amount > of entries in the same tables (as you will always get constraint > conflicts). > And that is the point that I did not reach/go beyond when I talked about having consistency in the DBs. But if the destination server had no lists, then it would probably not have been too difficult. Again, that's stuff for DB deep-dive. > to summarize, migrations must: > - *first* import old mm3 data into an *empty* database > (so you cannot import multiple mm3 instances into a single new one) > - import mm2 data afterwards > I believe there is a way around that because I recently did import an ML from one site to a live site. hence my idea for a special export/import format (and command), that > would only contain the actual structured data, but without all the extra > db-specific things (like unique ids for referencing between tables). > Oh, yes! I am sure the Developers will be happy to get such a tool as a contribution from the community. -- 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: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

Stephen, On 6/22/20 6:23 PM, Stephen J. Turnbull wrote: > By design, Mailman core doesn't need to talk to the Internet or to the > secure internal network -- Internet functions are delegated to the MTA > and the webapps, and local configuration is via shell access which in > principle could be console. Sorry, I missed this earlier. Ironically I am doing exactly what you are suggesting -- splitting the django frontend web app from the mailman core. In my current case I have put the mailman core on the same host as my mailserver, but that was for the sake of simplicity while I got that split sorted -- I am using exim and there is a big benefit when exim can see the list directory names. I may eventually move mailman-core elsewhere. However, I find the mailman shell program not very intuitive, and so would prefer to have the web app for admin purposes. Regards, Ruth

4 years, 9 months

[MM3-users] Re: Current status and issue deleting Archives in Mailman3

by Mark Sapiro

On 11/2/21 11:50 AM, bob B wrote: > So I am teaching myself to fish, and see that it is actually django-admin, so that is in > mailman-web? (in docker) > > But i get this: > > $ docker exec -it mailman-web /bin/bash > bash-5.0# django-admin shell > Python 3.8.10 (default, May 6 2021, 06:30:44) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import MailingList > Traceback (most recent call last): ... > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. Do what it says. I.e. run DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

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

by Simon Handfield

Thanks for your advice, Stephen. As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. I've confirmed the error is not cached in the browser. If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? Cheers, Simon. ________________________________ From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Monday, 31 August 2020 23:51 To: Simon Handfield <simon.handfield(a)sl.nsw.gov.au> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius Simon Handfield via Mailman-users writes: > I have been able to identify a file in the shunt queue that threw a > matching error when I performed mailman qfile on it. > I have run a loop over all remaining files in the shunt queue and > all the remaining files can be accessed by mailman qfile without > error. Good. But there are still a bunch of problems with those files since they got shunted. > I moved this file out of the queue in the hope that I would then be > able to load the held_messages page successfully. Unfortunately I > am still seeing a 500 error on loading the page. If this is a Mailman problem, I don't understand it. The shunt queue is not the moderation queue. The shunt queue is for messages that Mailman cannot handle without throwing an exception. Once a message is sent to the shunt queue, Mailman ignores it, so it shouldn't cause problems for the moderation page. Have you tried restarting Mailman since moving the qfile? If that doesn't work, and if it's the same error message and traceback, the easy suspect is browser caching (although we should be disabling that, I hope). Try a manual refresh (usually Ctrl-R or in the menu). If that doesn't work, try a private browsing window or another browser if you don't want to clear the cache or restart the browser. > I temporarily reenabled debug logging to confirm that the same > error was being thrown. > > Assuming that file was the cause are there other steps I need to > perform in addition to removing the file from the shunt queue > directory? The only one I can think of is the check for browser-side caching. Unfortunately, Mark's out of town (like, on top of a mountain with no bars on his phone), and I am not going to be able to do much with this until Thursday at the earliest. If you do get a new traceback, post it here (somebody else may have an idea). If you like you may send me the qfile at the address in From. I'll see if I can reproduce the bug, and I'm pretty sure I can tell you what's in the file so at least you'll know whether it's important to somebody who isn't a scammer/spammer. Steve _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 7 months

[MM3-users] Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: unknown encoding: windows-874

by Stephen J. Turnbull

Mark Sapiro writes: > Python doesn't recognize windows-874 as known charset. iso-8859-11 is a known character set for Thai, with a few missing punctuation marks. If the message turns out to be not Thai, but mostly ASCII with a few broken characters that are probably punctuation (including directed quotes, ellipsis, and the EURO SIGN), any Windows-12xx character set (IIRC, Windows-1252 is closest to Latin-1) should have those in the same positions. > You can move it aside, and if it looks like something you actually want > to archive, you might be able to fix it, but that's tricky. The file in > var/archives/hyperkitty/spool/ is I think a pickled email message > object. You can view it with `mailman qfile`, but editing is tricky. If any of the above codecs seem to work, just editing the charset parameter in Content-Type header(s) should do the trick. Sorry, can't help with the editing process itself, though. Steve

4 years, 11 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 3:53 PM, maszap(a)tin.it wrote: > Hi, > > I added the line to the main.cf file > > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > > In my log MTA mail.warn I get: > Jul 13 00:44:56 gamelia postfix/trivial-rewrite[8317]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains What's in your mail.log for a message to and from the list? > I check > my /var/log/mailman3/smtp.log > but is empty If Mailman is sending any mail at all, there should be entries in smtp.log unless the log level is higher than info. What does mailman conf -s logging.smtp 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, 9 months

[MM3-users] Re: per domain SITE_ID views?

by David Newman

On 12/28/21 1:30 PM, Mark Sapiro wrote: > On 12/28/21 1:14 PM, David Newman wrote: >> Using FILTER_VHOST, I have two domains set up and working with MM3, >> Postorius and Hyperkitty. However, because SITE_ID in settings.py >> points to one of the domains, that domain name always appears on >> Postorius and Hyperkitty pages. > ... >> How to get the correct domain to appear on that domain's Postorius and >> Hyperkitty pages? > > > I don't think the domain is actually displayed on Postorius pages. You are almost certainly correct. I saw dom1.tld on a login page, but hadn't realized that login page comes from Hyperkitty and not Postorious. > If > I'm wrong, on what Postorius view do you see it? As far as HyperKitty is > concerned, please file an issue for this at > https://gitlab.com/mailman/hyperkitty/-/issues/new Opened an issue here: https://gitlab.com/mailman/hyperkitty/-/issues/404 dn

3 years, 3 months

[MM3-users] Re: Detectors and Bounces

by Mark Sapiro

On 8/5/22 11:12, summersan(a)nclack.k12.or.us wrote: > > Thank you for refocusing the issue in terms of the "large numbers of bounces", too. > > Here is what I have in `mailman.cfg` for the `[mta]` section: > > `[mta]` > `verp_confirmations: yes` > `verp_personalized_deliveries: yes` > `verp_delivery_interval: 1` > > Does this help narrow down the problem any further? Not really. You need to see why you are getting these bounces. What's in Mailman's bounce.log? Are bouncing users getting their delivery disabled? What are your list(s) `Bounce Processing` settings. In particular, if you set all the `Notify owner ...` settings to `Yes` and `Forward unrecognized bounces` to either `List Admins` or `Site Admin`, what do you see? Also, if there are queued bounces in `/opt/mailman/mm/var/queue/bounces`, you can examine them with `/opt/mailman/mm/bin/mailman qfile` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: IndexError in archiving queue

by Mark Sapiro

On 3/16/23 04:13, Jacob Sievert via Mailman-users wrote: > Hello, > > it seems I have forgotten where I can kick an email out of the archiving > queue as it produces this error in a loop. > Might one of you know where I can do that? > Thanks in advance. The underlying error is a bogus Message-ID header in the message. We have observed cases of Message-IDs like Message-ID: <[d1e99408882e4aed93b0df4c1c28dfa3-JFBVALKQOJXWILKNK4YVA7COOVDWK5D4IVWWC2LMKB2WE3DJONUGK4T4IV4G6U3NORYA====(a)microsoft.com]> where the `[` and `]` are the problem. See the report at https://gitlab.com/mailman/mailman/-/issues/732 and fix for that at https://gitlab.com/mailman/mailman/-/merge_requests/1099 I would like to see the headers of the message in your case. To answer your question, the offending message is queued in Mailman's var/archives/hyperkitty/spool/ directory and can be examined with Mailman's `mailman qfile` command. -- 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: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, you > can set max_message_size in your list configuration. It defaults to 40; > units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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] duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

Hi I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: client.create_domain(name) Is this a bug? Or did I mess something up? What significance do those SITE_IDs have? What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Thanks! Stanisław

3 years

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On 3/26/21 8:51 PM, Brian Carpenter wrote: > On 3/26/21 6:13 PM, Mark Sapiro wrote: >> Absolutely. At first MM3 wasn't processing bounces at all. A GSOC >> student did the bulk of the current implementation and we were happy >> to get that even though this piece was missing. We know we need it. If >> you don't think we're working fast enough, you can submit a merge >> request or dock our pay. > > I don't understand the sarcasm here at all. I am just trying to figure > out what the PRIORITIES are from the Mailman 3 developers. That's all. > BTW, I still haven't figured it out. OK, the "dock our pay" remark was uncalled for, but I was only trying to point out that for the most part, all of this work is being done by or in some cases mentored by Abhilash and me, and we are both volunteers with other responsibilities. This is a known issue <https://gitlab.com/mailman/mailman/-/issues/737> posted by me 8 months ago. There are no offers to help work on it, nor are there any comments to the effect that this should be higher priority than any of the 307 other open Mailman core issues in the tracker. I can't speak for Abhilash, but my priorities are fix things that are trivial to fix as they arise and work on the harder stuff as time and interest allow. I realize that doesn't help you much, but I'm a volunteer. This is (one of) my hobbies. If it's not fun or at least satisfying, I won't do it. > It still doesn't explain why Postfix is not recording the delivery > issues which I assume has nothing to do with Mailman 3. I see successful > deliveries with Postfix and bounces with Mailman 3 core. I never seen > that with Mailman 2 and Exim. They always matched. If you can help me to > understand that with out the petty sarcasms then that would be great. If > not, then ok. I don't know why you never saw this with MM 2.1 and Exim. Possibly because MM 2.1 sent you the DSN with the admin notification, you never looked. I told you in my initial reply in this thread "They are being bounced by a downstream MTA." To elaborate on that, Mailman's MTA be it Postfix, Exim or whatever, attempts to deliver the mail to the MX of the recipient domain. Sometimes this results in a 5xx status which is logged and reported as a bounce to the sender, i.e. the LIST-bounces address. Sometimes it results in a 4xx status which will cause the delivery to be retried at intervals until it is either accepted or exceeds a configured lifetime and is reported as a permanent failure. The rest of the time, the delivery succeeds, but that is only delivery to the MX for the domain. It may be that for that recipient, that MX is a relay to another MX in the delivery chain, and sometimes, either quickly or after some delay due to retries downstream eventually timing out, the ultimate delivery fails and a DSN is returned to the original envelope sender which is the LIST-bounces address. If you look in the Postfix logs around the time that Mailman recorded the bounce, you should see an incoming message from=<> (DSNs always have a null envelope sender) and to=<LIST-bounces(a)list.domain> or if you are VERPing to=<LIST-bounces+recip=recip.domain(a)list.domain> which is the DSN being returned by the downstream MTA. -- 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: Postfix-Fehler mit mailman-web

by Stephen J. Turnbull

Jens Günther writes: > 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: > reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host > rejected: cannot find your hostname, [192.168.176.6]; > from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web> There are a bunch of $myxxxx variables in Postfix, I think $myhosts might be the right one. If you add the IP 192.168.176.6 to that variable, it will be whitelisted and this problem should go away. There may be better ways to handle this, but don't mess with hostnames. Find the "right" way to permit that IP should do the job. > I mean the hostname for the core-container must be there, since > mail is accepted :-D That's not the way this works. Postfix accepts the mail because it's arrives at the physical host, then looks up routing for the mailbox and discovers it should be delivered via LMTP to the core container's IP. No hostname needed. Steve

1 year, 7 months

[MM3-users] Re: Ann: Mailman Core 3.3.5 is out

by Eggert Ehmke

Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would have to bypass the Debian installer. Or will there be Debian packages available? Same question for Postorius 1.3.6 Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > Hey Everyone, > > I just tagged and uploaded Mailman Core 3.3.5 release. > > This release includes both bug fixes and some new features. A full list of > changes is available here: > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS. > html#news-3-3-5 > > You can install this version using pip: > > $ pip install mailman==3.3.5 > > The release tarball is available on PyPI as well: > > https://pypi.org/project/mailman/3.3.5/#files > > Thanks to everyone who made this release possible! > > Abhilash > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > > > > Hey Everyone, > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > This is identical to 3.3.5b1 in code, the only changes that have been made > > are in utility scripts and testing configuration.> > > You can install this version using: > > $ pip install --pre mailman==3.3.5rc1 > > > > If you want to download a release tarball, you can do so from here: > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > This is the first (and only) planned release candidate for 3.3.5 release. > > The stable release is planned for next week. > > > > thanks, > > Abhilash > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > >> Hello Everyone, > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from now. > >> I am planning for a 2 week beta period, after which I'll release the > >> first RC and then stable a week after. Right now I am not planning to > >> release a second beta version, but if there are several changes in Core > >> in the next week or so, then I might. This release includes a lot of bug > >> fixes and some new features. It also includes a security enhancement > >> that improves the authentication of REST API by adding resistance to > >> some timing channel attacks. A full list of changes in this version can > >> be found here[1]. > >> [1]: > >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > >> and now the email templates are updated from the translated messages in > >> the .po files that we get from Weblate. Documentation for translators is > >> available here[2] if you want to help translate Mailman into your native > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > >> > >> This is a pre-release version, if you want to test it with your setup, you can install it using: > >> $ pip install --pre mailman==3.3.5b1 > >> > >> If you want to download a release tarball, you can do so from here: > >> https://pypi.org/project/mailman/3.3.5b1/#files > >> > >> This release received a lot of contributions from community, which I am > >> really happy about! I'd like to thank everyone who made this release > >> possible!> > > -- > > thanks, > > Abhilash Raj (maxking) > > -- > thanks, > Abhilash Raj (maxking)

3 years, 6 months

[MM3-users] Re: pending subscriptions lost?

by IEM Network Operation Center (IOhannes m zmölnig)

On 3/14/22 17:03, Mark Sapiro wrote: > On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman > 3.3.5. thanks for comfirming. > > >> - i (as administrator) do not see any "pending subscriptions" (the >> list is setup with a simple "Confirm" subscription policy > > The count badge only counts subscriptions waiting moderator approval. If > you pull down the Subscription requests tab and click Pending > Confirmation you should see them and be able to discard them. hmm. i'm not sure i can follow. my "Subscription requests" tab seems to not have any "Pending Confirmation" section (see attached screenshot). this is with "Postorius Version 1.2.4" (as installed by the mailman3 Debian package). fdsm< IOhannes ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Subscription requests.png

3 years, 1 month

[MM3-users] Editing the "example.org" site

by Stephen J. Turnbull

Hi all, I don't know how many people will need this, but I just realized that you can edit Django's SITE 1 and (probably, 100% untested but I'm going on the clock so want to get this done quick :-) use that. When you add your first domain, there's a link in that page (not a button, a link!) to edit the domain list. Then you can click on the link to "example.org" in the list, and edit both display name (which I assumed) and the domain name. Maybe I'm just slow, but I've been adding SITE 2 = "Whatever site <whatever.tld>" the whole time. :-) But then you have to edit the SITE = 1 statement in settings.py (which I often forget and hilarity ensues). Of course adding a web site and editing settings.py (which you have to do anyway for other variables) works too, but this seems cleaner to me. Steve

1 year, 3 months

[MM3-users] Re: OperationalError: database is locked

by Cyprian Laskowski

Thanks for your feedback again. It turned out that upgrading our components to the listed 3.1 suite versions *and* fixing permissions on /var/www/.cache helped significantly. We still get database locked errors, but much more sporadically, and the application is more responsive in general. However, we haven't been able to switch to postgresql. We did do a django "migrate" for sqlite due to the new version, but when we then backed up the sqlite and tried to load it into the new postgresql database, we get: hyperkitty.models.email.DoesNotExist: Problem installing fixture '/opt/mailman/mailman-suite/mailman-suite_project/dump_sqlite_updated.json': Email matching query does not exist. Interestingly, this seems to be the same error as perhaps the most common one in our uwsgi-error.log (see my previous message), which is still seeing constant activity. Any suggestion of how to overcome this? I have tried to compare our settings to the example ones, and haven't found obvious culprits, but I will take a closer look.

7 years, 2 months

[MM3-users] Upgrade Mailmam Core from

by sascha.rissel＠gmail.com

Hello, I have newly set up Mailman 3 on Ubuntu 20.04. Sending and receiving mails between list members does work, but I am currently experiencing two issues: 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. 2) Archiving is activated within list settings, but there isn't any archive created. I found this thread, where the first of these issues is also described: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. I am running Mailman 3.2.2 on Python 3 .8.10. So I need to either upgrade Mailman Core or downgrade Python. I already did > apt-get upgrade > apt-get update Unfortunately this didn't upgrade Mailman Core's version. Which steps do I have to undertake to upgrade Mailman Core? Regards, Sascha.

2 years, 6 months

[MM3-users] Re: Default setting for Delivery status

by Mark Dale

>> Where and how do I set the default setting of "Delivery status" to be "Enabled". > > It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… >> At the moment, a new subscriber is neither "Enabled" or "Disabled". > > That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. > > Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. > > New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. > Ahhhh. Thanks very much Mark. I did some experimenting to get my head around what you've explained and I can see how it works now.

2 years, 6 months

[MM3-users] Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Mark Sapiro

On 1/9/23 05:31, Johannes Rohr wrote: > > Thanks! I assume, there is a reason why this cannot be easily > implemented, else it would have been. Asking because I know a number of > people would make extensive use of this in MM2. The actual implementation is probably not difficult, but it's more than just handling things like `@list_id` in *_these_nonmembers. It also requires developing appropriate unit tests, updating REST and `mailman import21` to accept the syntax and documentation updates at least for Postorius Settings -> Message Acceptance -> * these non-members. That adds up to a significant amount of work. I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

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

by Mark Sapiro

On 11/18/24 23:13, mark(a)suburbia.org.au wrote: > - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" The actual value is None, but Postorius displays/sets that as List default. >> If that is true, I can only think that at the time of that post, >> settings weren't as they are now. > > I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Thank you for doing the test. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

[MM3-users] Re: cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)

by Mark Sapiro

On 10/18/22 11:28, Paul Ssekamatte via Mailman-users wrote: > i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. > my setup uses an alias domain i.e the mail server is different from the lists server. That is not what alias domains are for. You do not want an alias domain. > I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. > OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. > Even when I change the port number, I still get the same error > Kindly assist. First, remove the Alias Domain from your domains. > here is my mailman.cfg config > [paths.here] > var_dir: /opt/mailman/mm/var > > [mailman] > layout: here > site_owner: postmaster(a)mail.example.com > > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgres://mailman:#passwd@localhost/mailman > > [archiver.prototype] > enable: yes > > # For the HyperKitty archiver. > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > > [shell] > history_file: $var_dir/history.py > > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > lmtp_host: mail.example.com The above is wrong. You want the default lmtp_host: 127.0.0.1 > lmtp_port: 8024 > smtp_host: mail.example.com smtp_host should be the mail server, not the list host. Is it? > smtp_port: 25 > configuration: python:mailman.config.postfix These next 3 do not belong in mailman.cfg. They are Postfix main.cf settings: > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no and this next one is a Mailman 2.1 mm_cfg.py directive and is not for Mailman 3. > POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] > > /etc/mailman3/settings.py file is as follows not relevant for this issue. > /etc/postfix/main.cf is as follows > smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) > biff = no > append_dot_mydomain = no > readme_directory = no > compatibility_level = 2 > smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases > mydomain = example.com > myhostname = lists.example.com > mydestination = $myhostname, localhost.$mydomain, localhost > relayhost = mail.example.com > myorigin = $mydomain > mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 > mynetworks_style = subnet > mailbox_size_limit = 4096000000 > #message_size_limit = 2048000000 > recipient_delimiter = + > inet_interfaces = all > #inet_protocols = all > inet_protocols = ipv4 > unknown_local_recipient_reject_code = 550 > owner_request_special = no > virtual_mailbox_domains = example.com You probably don't want this, at least not if the mailman server is example.com > virtual_mailbox_base = /var/vmail > virtual_uid_maps = static:20000 > virtual_gid_maps = static:20000 > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains > virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap and you don't want this virtual_alias_maps. > postfix domains as follows: > lists.example.com example.com > > postfix lmtp as follows: > testlist(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 > testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 The host in lmtp: is the Mailman server. > postfix vmap as follows: > testlist(a)example.com nmutest(a)lists.example.com > testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com > testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com You don't want that at all. -- 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] Where to put static files referred to from list Info page?

by Greg Newby

Hi friends. Some of my version 2.1 lists had some static files that were referenced from the list's HTML pages. I'd like to do the same for the lists now that they're ported to MM3. My question: Is there a place I can put these files within the Mailman directory hierarchy so they can be linked from the list Info page? I.e., under "Settings / List info / Long description" I'd like to include a <a href=...> to a file that's somewhere in a persistent location in the same directory tree as the Mailman web. I tried putting it under mm/var/lists/listname/ (where 'listname' exists, and is where templates go. This yielded a '404.' I confirmed I can add an href to the Long description, but don't know where in the Mailman3 directory hierarchy I can put the files. Thanks! Greg Newby

8 months, 2 weeks

Search results for query "dO"