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

[MM3-users] Re: Reduction of spam - FROM_LOCAL_HEX

by Odhiambo Washington

On Tue, Oct 31, 2023 at 11:56 AM Kyriakos Terzopoulos < kyriakos.terzopoulos(a)gmail.com> wrote: > Hi, > > After fixing all issues with mailman I want to reduce the chance for email > being marked as spam, especially from Gmail. I have added SPF and DKIM > records and I am now using dkimvalidator to debug the emails being sent. > Here is what I'm getting from spam evaluation: > > *0.3 FROM_LOCAL_HEX From: localpart has long hexadecimal sequence* > > My guess is that the From address is very large, for example: > > mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580(a)myproject.eu > > Is there any way to mitigate this problem? > Since mailman is doing what it is supposed to, and doing it correctly, I am not understanding what you want. Is Gmail classifying that email as spam? -- 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]

2 years

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

by Mark Sapiro

On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > Finally, I have adapted your init script to get some rudimentary one that I > could use on FreeBSD. > I have to change /opt/mailman to be owned by mailman3:mailman3 (because I > have "live" MLs on this server, using mailman-2.1.34. > I am not sure if they can co-exist. I suppose they could, but what might be > the security implication, if any?? I manage more than one server that supports both Mailman 2.1 and Mailman 3 running as user `mailman`. I'm not aware of any security issues. > This is what the init script looks like (rudimentary!!): > (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 > ### BEGIN INIT INFO > # Provides: GNU Mailman > # Short-Description: Mailman3 Service > # Description: service control for Mailman3 > ### END INIT INFO > > PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: > DESC="GNU Mailman service" > DAEMON=/opt/mailman/mm/bin/mailman > NAME=mailman > USER=mailman3 > GROUP=mailman3 > > # Needed by click > export LANG=en_US.UTF-8 > > # Exit if the package is not installed > [ -x "$DAEMON" ] || exit 0 > > # Load the VERBOSE setting and other rcS variables > #. /lib/init/vars.sh > > # Define LSB log_* functions. > # Depend on lsb-base (>= 3.2-14) to ensure that this file is present > # and status_of_proc is working. > #. /lib/lsb/init-functions > > case "$1" in > start) > [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" > # use --force to remove a stale lock. > /usr/local/bin/sudo -u $USER $DAEMON start --force T don't recommend using --force in init scripts. It *shouldn't* matter because even with --force the master shouldn't break the lock if the pip that set it still exists, but I prefer not to use it. > ;; > stop) > [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON stop > ;; > status) > /usr/local/bin/sudo -u $USER $DAEMON status > ;; > reopen) > /usr/local/bin/sudo -u $USER $DAEMON reopen > ;; > restart) > log_daemon_msg "Restarting $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON restart > ;; > *) > echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 > exit 3 > ;; > esac > > It does start mailman3 for sure, but also complains after a few seconds > with the message: > > (venv) [root@gw /usr/local/etc/rc.d]# > */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: > DeprecatedWarning: Call to deprecated function __init__(...). API class may > be removed in a future release, use falcon.App instead.* > * **kws)* Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 and 3.0.0a1 and I don't see this warning, but it is only a deprecation warning. It doesn't mean it won't work. > But: > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman ... It seems Mailman core and the rest runner and its workers are all running. > > Assuming that I am using mod_wsgi with Apache, and that I have configured > apache right using > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > .. > should I be able to access the MM3 web UI?? Yes, I think so. > At that point, I am feeling somewhat confused as to what to try next. > > (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log > Jul 25 22:53:16 2020 (40670) Master started > Jul 25 22:53:18 2020 (42036) bounces runner started. > Jul 25 22:53:18 2020 (45205) out runner started. > Jul 25 22:53:19 2020 (41191) archive runner started. > Jul 25 22:53:19 2020 (46670) retry runner started. > Jul 25 22:53:19 2020 (44567) nntp runner started. > Jul 25 22:53:19 2020 (43069) in runner started. > Jul 25 22:53:19 2020 (46960) virgin runner started. > Jul 25 22:53:20 2020 (45720) pipeline runner started. > Jul 25 22:53:20 2020 (47326) digest runner started. > Jul 25 22:53:20 2020 (43755) lmtp runner started. > Jul 25 22:53:20 2020 (45922) rest runner started. > [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 > [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: > http://127.0.0.1:8001 (45922) > [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync > [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 > [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 > Jul 25 22:53:21 2020 (42743) command runner started. The above is all fine, but it is just Mailman core. > How do I access the web UI for MM3 now? The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which is at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>. Do you have that? If you installed the Apache config literally, the location for Mailman 3 is defined by <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> and the URL would be http(s)://your.server/mm3 - have you tried that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

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

by Mark Sapiro

On 7/12/20 6:30 PM, maszap(a)tin.it wrote: > Hi, > > you say I have to delete these lines? > > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_gid_maps = static:5000 > virtual_mailbox_base = /var/vmail > virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_mailbox_domains.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > virtual_transport = lmtp:unix:private/dovecot-lmtp > virtual_uid_maps = static:5000 I say you have to understand what you want Postfix to do and configure it appropriately. I am not a primary resource for Postfix support in general. I will help you to the extent that I can, but you might be better off posting to a Postfix list. I would need much more information in order to know how your Postfix should be configured, and in any case, I don't have time to do any more today. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Docker Installation of Mailman -- The Hyperkitty Chronicles

by Abhilash Raj

On Sat, Dec 22, 2018, at 6:08 AM, brian(a)emwd.com wrote: > Using Maxking's docker project to install mailman3, I have a fairly > functional mailman3 installation. However Hyperkitty is not archiving > or showing list participants like: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > > This is my page: > > https://mailman3.emwd.com/hyperkitty/list/testlist@mailman3.emwd.com/ > > The docker documents really don't say much about getting HK up and running. You don't need to do anything to make HK work. What do you see in the logs? Check /opt/mailman/web/logs/ for Mailman-Web logs and /opt/mailman/core/var/logs for the logs of Core. There must be some errors showing up, causing emails to not be archived. > Brian > _______________________________________________ > 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, 10 months

[MM3-users] Problem with languages

by Jens Günther

Hey, I set up Mailman3 from the Debian-packages and got it working. But for some reason I do have a mixed setup in languages now. Some strings are in English, some are in German. The settings I changed are: in mailman.cfg [mailman] default_language: de in mailman-web.py LANGUAGE_CODE = 'de-DE' TIME_ZONE = 'Europe/Berlin' Nothing changed after restarting services. I then came across this post: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -> but actually I do not find any of the files, ... - no mailman.po / .mo - no generate_mo.sh - no languages folders in /usr/lib/python3/dist-packages/mailman/messages - when searching with locate (after updatedb) no LC_MESSAGES/mailman or anything stated in the post Actually it would be fantastic to be able to choose language for the web interface / lists like on this here, but this is additional :-) just to have it in one language, this time German would be cool. I also would translate, but it seems finished: https://hosted.weblate.org/projects/gnu-mailman/mailman/ Thank you for help, regards, Jens.

4 years, 7 months

[MM3-users] Re: My list has been switched from public to private archives, but they are still visible

by Enrique Terrazas

Thank you Abhilash, I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”? Regards, Enrique On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: I am having a very similar issue. Here is what I have found: There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings Archiving and they are: Public archives Private archives Do not archive this list This is interface of Mailman to set the archives. In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists Mailing List object(x) > Archive policy: never private public This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run. I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :) I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged? Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that. Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty. For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible. Enrique On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: Can anyone help with this? I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now) This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core. I have made a change which should fix this problem and the process would become synchronous. You can run `python manage.py runjobs --daily` command to force sync that information. https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… Am I misunderstanding what a private archive is? Not really, your expectation is right. Is something wrong with my setup (which is hosted)? Thank you. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 1 month

[MM3-users] Re: Log Owner/Moderator actions ban address matching.

by Mark Sapiro

On 5/1/25 04:02, Stephen J. Turnbull wrote: > Odhiambo Washington via Mailman-users writes: > > > So this issue can be addressed by making Postorius to log user logins, > > right? > > However, I don't have the patch :) > > I would guess it's probably possible to get Django to do this, quite > possibly using standard configuration to do so. I just don't know > where to look offhand. Postorius can't log logins because it's not Postorius (or HyperKitty) that does the logging in. It is django-allauth. You can see the `Last Login` info for a user in the Django admin web UI under Authentication and Authorization -> Users django-mailman3 does have some involvement with logging in and it might be possible to add logging there, but I don't offhand know where. -- 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] Re: moving lists to another server

by Odhiambo Washington

On Sat, Nov 18, 2023 at 1:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/23 00:51, Odhiambo Washington wrote: > > > I am scratching my head bald trying to figure out how to bring in this > > other MM3 site and list into my existing server, especially with regard > to > > the DB backend. > > > > The list - let's call it users(a)domainX.name was using MySQL backend and > > had a separate DB for Mailman core and Mailman web. > > I believe combining these into one isn't a problem. But getting to merge > > this DB into my current one is what I am not sure about. > > This is https://gitlab.com/mailman/postorius/-/issues/13 which is a real > need, but doesn't yet exist. > > I think the easiest thing for the archives is to forget the Mailman web > DB and just export the archive as a mbox from the other site (if it's > large, exporting the entire archive will time out so you have to do it > in pieces). Then you can use hyperkitty_import to import it. > What is the command to export the archive as a mbox from the DB? I can't figure out which option it is by looking at 'mailman-web -h'. > For the list data, it's probably easiest to just create the list > manually and go through the settings in Postorius and make them match, I want to go with the above. although you could dump the mailinglist table entry where list_id = > 'users(a)domainx.name' and load that, but you'd need to edit the id field > in the dump to match the id on your server. Not going with that. > That leaves the members. Given that I have a dump of the two DBs (mailman and mailman-web) I just created one DB and imported them. I have been able to dump the members into a text file. Now importing is not a problem. BTW, how will ' mailman addmembers' treat a file containing: ``` Firstname Lastname <email@address> Onlyname <email2@address> ``` ? > Doing this with a DB dump/load would be very complex because while the > member table has a list_id field which is the id of the list's entry in > the mailinglist table and can be used to select the relevant members, > these records also link to entries in the address, preferences and user > tables and matching them would be an issue. > I am also not taking that path. I think a custom script would be required. If I were doing this, I would > make a separate database on my server with a copy of the data from the > other server and then try to make a script that would extract data from > the other database and add it to mine. Alternatively you could just dump the members from the other servers > with the `mailman members` command perhaps separately for regular and > the different digest types and then add them with the `mailman > addmembers` command. This wouldn't get all their attributes, but it > could work. > I have opted for the simple way to do this: 1. Create the site in Django Admin and create/configure the list in Postorius 2. Add the members from the file dump, with delivery set to regular. 3. Send the members an email informing them that they need to set their delivery preferences. I am stuck on the issue of exporting the archives to mbox file as already stated above. -- 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, 11 months

[MM3-users] Re: LMTP on unix socket

by Mark Sapiro

On 10/20/19 3:55 PM, Hristo Venev via Mailman-users wrote: > How do I configure mailman to use a unix socket for lmtp connections? > Setting > > [mta] > incoming: mailman.mta.null.NullMTA > lmtp_host: /path/to/socket > > does not work. Mailman still tries to create a TCP socket. You can't do this. Mail Delivery is to Mailman's lmtp runner which uses the LMTP class in aiosmtpd <https://aiosmtpd.readthedocs.io/en/latest/> to create an LMTP server which listens for tcp connection on lmtp_host:lmtp_port. You would have to modify mailman/runners/lmtp.py to listen on a unix socket. The docs imply the aiosmtpd.controller.Controller class has a make_socket() method which "allows subclasses to customize the creation of the socket before binding" which I suppose could be used to create a unix socket, but mailman/runners/lmtp.py currently doesn't make use of that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Something wrong in Django admin interfaces

by Franklin Weng

Hi, Since both Mark and Danil kindly told me that my wish to disable web anonymous account registering requires new version of mailman and django-mailman, I found that newest Debian bookwarm (12) has * mailman 3.3.8-1 (including mailman3-full and mailman3-web 20200530-2.1) * python3-django-mailman3 : 1.3.9-1 * python3-mailman-hyperkitty : 1.2.1 So I re-installed mailman3 (and took notes so that I could write a blog). After installing that, I found that it has problems in django admin page. 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 looked at django-mailman issues https://gitlab.com/mailman/django-mailman3/-/issues but didn't find anything useful. Does anyone have similar issues? What can I do to solve this? Thanks, Franklin

2 years, 3 months

[MM3-users] GNU Mailman condemns reinstatement of RMS

by Abhilash Raj

To the Mailman community, The GNU Mailman Steering Committee condemns the reinstatement of Richard M. Stallman (RMS) to the Board of the Free Software Foundation (FSF), and has taken the following actions: 1. On behalf of the GNU Mailman project, signed the letter on GitHub[1] calling for the removal of the entire FSF Board, as well as RMS himself. 2. Started exploring ways to move our financial assets, for decades managed by the FSF, to new management. The management fees are small, but this is an important symbolic protest. 3. Started exploring how to leave the GNU Project. On the one hand, if we leave but GNU wants to maintain a "GNU Mailman" project, we cannot stop them, confusing users. On the other hand, RMS is leader of the GNU Project, and has intervened in Mailman affairs on many occasions. We should forestall this in the future. We wish to explain our actions to the community. Although free exchange of software among users is a practice that goes back to days of the earliest general purpose computers, RMS was the first to propose a complete free software distribution, and is the acknowledged founder of the Free Software movement. Even leaders of the Berkeley Software Distribution (BSD) acknowledge this. We all owe him a debt for this. Nevertheless, the movement has matured and thrived, spawning the competitive open source movement, with whose philosophy Mailman is more closely aligned. While we acknowledge our debt to RMS, we don't need him any longer. And unfortunately, he has become both a symbol and a source of the toxicity in tech communities. The FSF Board did the right thing by accepting RMS's resignation. They did the wrong thing by reinstating him. RMS has a long history of abusive behavior and toxic political positions. A small part of it is described in the open letter on GitHub[1] and its references[2], and several members of the Steering Committee have observed it directly. All of us have heard stories directly from those who were abused or observed it directly. His political positions are public, for example his support of pedophiles. He claims that he in no way supports abusive relationships with children, yet refuses to acknowledge that children are generally in no position to provide consent, an evasive and highly toxic position. There is no question: RMS is toxic. We came for mailing list management, but we stayed for the community. We have a right to protect our community by dissociating it from toxic influences. We do not want our project associated with such a person, nor to provide economic resources to organizations that promote him to leadership positions. We are taking these actions to protect our community, both the narrow community of Mailman developers and users, and the broader open source community, from his toxic behavior and from the reputational damage that will come from helping to enable him. While we have no information suggesting that other members of the FSF Board are similarly toxic as individuals, as a group they enabled RMS for decades, and now have taken an explicit step in enabling him again. If they want to regain their position of respect and acceptance in our community, they must acknowledge their error, and we don't see -- given their reinstatement of RMS himself -- how they can do so convincingly while maintaining their positions on the Board. They must resign, and a new Board composed, to demonstrate their sincerity. What they do is up to them, of course, but if they do not take radical steps, we will continue to consider association with the FSF a threat to our community. For the Mailman community, Abhilash Raj (project leader) Mark Sapiro Stephen J. Turnbull Aurélien Bompard Terri Oda Barry Warsaw John Viega (founder) [1] Text and signatures: https://rms-open-letter.github.io [2] Appendix to the letter: https://rms-open-letter.github.io/appendix Related statements: https://rms-open-letter.github.io/statements

4 years, 6 months

[MM3-users] Re: Verification links to localhost

by Lars Bjørndal

Hi! You wrote: > On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <[1]lars(a)lamasti.net> wrote: > > Hi, and than you for your quick reply! > > You wrote: > > > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1][2]lars(a)lamasti.net> > wrote: > > > > The verification link I get back when trying to add an account, > referes > > to localhost, e.g. > > > > To confirm this is correct, go to [2][3]https://localhost:8000/ > accounts/ > > confirm-email/Mw:1... > > > > Where do I change that? > > > > > > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings? > > I don't have this variable anywhere in /etc/mailman3. However, I found it > here: > > ./venv/lib/python3.10/site-packages/mailman_web/settings/ > mailman.py:POSTORIUS_TEMPLATE_BASE_URL = '[4]http://localhost:8000' > > In which config file should that variable be set, and how do I set it so > that mailman can works for multiple domains? > > > Because it is still too early in your quest to get to run Mailman3, I'd advise > that you take your time to follow this guide: > [5]https://docs.mailman3.org/en/latest/install/virtualenv.html# > It is the official installation guide. Yes, I've followed it, maybe with some errors. > There is a step where it tells you to create a file named settings.py, in a > particular path. You really need that step. Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't have the variable in question. > Regarding your question about multiple domains, that is already well taken care > of when you create a list either via Postorius or the cli: > (venv) [mailman@gw /opt/mailman]$mailman create [6]list1(a)domain1.name > (venv) [mailman@gw /opt/mailman]$mailman create [7]another-lis(a)domain2.name > > Mailman will know how to handle this in conjunction with your MTA. That's right. But, still, when I set the SITE_ID = 0, I get an server error when trying to connect. I also get mail from Django that states the error. I'm not sure how to fix it. Thanks, Lars [...] > References: > > [1] mailto:lars@lamasti.net > [2] mailto:lars@lamasti.net > [3] https://localhost:8000/accounts/ > [4] http://localhost:8000/ > [5] https://docs.mailman3.org/en/latest/install/virtualenv.html# > [6] mailto:list1@domain1.name > [7] mailto:another-lis@domain2.name

2 years, 8 months

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Mark Sapiro

On 9/9/25 08:42, M.Ede via Mailman-users wrote: > Hello everyone, > > I use mailman together with mailcow and have configured my mailing list as follows: > - Anonymous list: Yes > - DMARC mitigation action: Replace From: with list address > - DMARC Mitigate unconditionally: Yes > > My problem is that my emails are not being accepted by mailcow (rspamd) with the error > SPOOFED_UNAUTH (50.00) > ... > What am I still doing wrong? Can you help me, which setting is still missing? > What informations are you still missing? I doubt that this has anything to do with the ARC-*, Authentication-Results or DKIM-Signature headers you quote. There are some threads on SPOOFED_UNAUTH in the mailcow community forum, e.g. https://community.mailcow.email/d/403-spoofed-unauth-rspamd and https://community.mailcow.email/d/637-problems-with-emails-keep-getting-rej… Also see https://www.reddit.com/r/mailcow/comments/12lhw8e/whitelist_ip/ These came up in a google search for SPOOFED_UNAUTH. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: moving lists to another server

by Mark Sapiro

On 11/17/23 00:51, Odhiambo Washington wrote: > I am scratching my head bald trying to figure out how to bring in this > other MM3 site and list into my existing server, especially with regard to > the DB backend. > > The list - let's call it users(a)domainX.name was using MySQL backend and > had a separate DB for Mailman core and Mailman web. > I believe combining these into one isn't a problem. But getting to merge > this DB into my current one is what I am not sure about. This is https://gitlab.com/mailman/postorius/-/issues/13 which is a real need, but doesn't yet exist. I think the easiest thing for the archives is to forget the Mailman web DB and just export the archive as a mbox from the other site (if it's large, exporting the entire archive will time out so you have to do it in pieces). Then you can use hyperkitty_import to import it. For the list data, it's probably easiest to just create the list manually and go through the settings in Postorius and make them match, although you could dump the mailinglist table entry where list_id = 'users(a)domainx.name' and load that, but you'd need to edit the id field in the dump to match the id on your server. That leaves the members. Doing this with a DB dump/load would be very complex because while the member table has a list_id field which is the id of the list's entry in the mailinglist table and can be used to select the relevant members, these records also link to entries in the address, preferences and user tables and matching them would be an issue. I think a custom script would be required. If I were doing this, I would make a separate database on my server with a copy of the data from the other server and then try to make a script that would extract data from the other database and add it to mine. Alternatively you could just dump the members from the other servers with the `mailman members` command perhaps separately for regular and the different digest types and then add them with the `mailman addmembers` command. This wouldn't get all their attributes, but it could 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, 11 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

Hey there, Im going to breakdown my response into sections: 1) Yes, there is only one install of mailman on the box. 2) I created the list using the script below 3) My method of importing it is by copying the lists to /opt/mailman/old/lists and running these commands (within lists) MYDIR="/opt/mailman/old/lists" DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` for DIR in $DIRS; do mailman import21 "${DIR}"@afilias.info "${DIR}"/config.pck; done However, if you look at the above you can see where I am going wrong. What it should actually be doing is: MYDIR="/opt/mailman/old/lists" DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ afilias.info "${DIR}"/config.pck; done Sorry for wasting your time on this one. Coffee is on me. On Mon, Jul 30, 2018 at 6:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/30/2018 07:37 AM, Ryan McClung wrote: > > GNU Mailman 3.2.0 (La Villa Strangiato) > > Python 3.6.5 (default, Apr 10 2018, 17:08:37) > > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > > config file: /opt/mailman/var/etc/mailman.cfg > > db url: sqlite:////opt/mailman/var/data/mailman.db > > devmode: DISABLED > > REST root url: http://localhost:8001/3.1/ > > > > Shortly after I run an import on a bunch of lists they all disappear. > > [root@mailman3(stg) mailman]# mailman lists > > No matching mailing lists found > > > > I have 30+ lists. > > > Does the 'mailman lists' command invoke the identical 'mailman' file as > the 'mailman import21' command that did the imports. And how did you > create the lists before importing them? > > We have done several imports of 2.1 lists to > <https://mail.python.org/mm3/mailman3/> and have never seen an issue > like this. > > -- > 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/ > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

7 years, 3 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/19/20 9:04 PM, Mark Sapiro wrote: > I suppose it could be considered a bug, but what's happening is your > initial subscribe created a user and and address and set the user's > preferred address to the created address. It also set the display_name > of the address and it subscribed the user to the list or possibly the > address to the list depending on what actually did the subscribe. > > When the user/address was unsubscribed, it is removed from the list's > membership and the list was removed from the user's memberships, but the > user and address still existed. > > Then when you resubscribed, the existing user/address was made a member > of the list, but not updated so the "new" display_name was ignored. I > think this is also the case if the original address had no display_name. > > You could say this is a bug and the display_name associated with this > new subscription should replace the prior one, but what if that address > was subscribed to other lists and didn't want the display_name changed > on those lists. > > Ideally (perhaps) there could be multiple address records with the same > email address and different display_names, but address records are keyed > by email address, so this can't be. > > One workaround would be for a user who wanted to have an address with > different display_names for different lists to have multiple addresses > likeaddress+list1@example.com,address+list2@example.com, etc. > > Is this really an issue that should be fixed or just a curiosity? No. No. No. No one set their preferred address here at all. The first incident was an imported list member who was not a registered user. They wanted their real name changed to something else. The list owner tried to figured out how to do that, found no way to do it, figured out it was just easier to unsubscribe them, and resubscribed them to the list using a different name. The old name showed up again. This is a bug and please fix it soon. This has nothing to do with being subscribed to other lists. I can probably come up with a workaround using Affinity (one of the benefits of moving away from Postorius) but I can't imagine this not being a serious issue as Mailman 3/Postorius is more widely adopted. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/20/19 7:26 AM, brunol(a)agro.uba.ar wrote: > Hi, > > I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1) > Following the 2.1 to 3 docs: > - Create a new list > - Use the import21 command > The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members. Are you saying that when a post is sent to the list, it is held for moderation, and when you approve it, it is not delivered? Or are the moderation messages from some other lists? Are there any non-digest members with delivery enabled? Is the MTA (which MTA) delivering the message to Mailman's REST runner? -- 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] Fwd: Seeking help completing a useful installation

by Hugh Esco

Trying this again. ---------- Forwarded message --------- From: Hugh Esco <hresco3(a)gmail.com> Date: Mon, Mar 11, 2024 at 10:30 PM Subject: Seeking help completing a useful installation To: <mailman-users(a)mailman3.org> I have more fully documented where I am at with this attempt to build a working installation of mm3 at this link: https://gitlab.com/mailman/django-mailman3/-/issues/73 My questions include: - the template for /etc/mailman3/mailman.cfg, defines vardir, but no DATA_DIR. See test failure #1 (closed) <http:///mailman/django-mailman3/-/issues/1>, above. Where does that want to be? Any issue with putting the mm3.db next to the mm3_web.db at /opt/mailman/mm/var/data? - there are two possible virtualenv's in my build: (a) /opt/mailman/venv/ and (b) /opt/mailman/.pyenv/. I say more about these below. Which do I want to use in this instance? I'm guessing the latter where the mailman3 libraries are published, but have doubts. The link above urges a dependency on python ^3.11, but bookworm provides only python 3.8, so I used pyenv to satisfy the requirement. It wanted to deploy to its own path, though perhaps there is some switch which would consolidate everything under /opt/mailman/venv/. I do not work with python enough to know. - attempts to run bin/mailman-web startapp mm3web fail to add any new processes to the process list. bin/mailman-web start fails with errors. What change of state to the server should I expect from running this command? How do I test for success? If startapp is the correct invocation, what argument does it want on a working installation? - having run the command in the previous point, I see nothing in the browser except for the apache starter page at the root path '/'. None of the paths defined in the apache2 configuration seem to offer any joy. I assume that uwsgi wants to proxy the requests to a running mailman-web service somehow, but that no such service is found. I see one hopeful line in the log at: /opt/mailman/mm/var/logs/mailman.log "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" - I assume that once I get apache2 wired to a running application through the uwsgi proxy, that I can proceed to create an admin user, use it to explore the web gui, and begin to consider how to migrate my legacy mm2.1 lists into the new installation. Any further help crossing the finish line would be appreciated. Thanks, -- Hugh

1 year, 7 months

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

by Mark Dadgar

On May 8, 2020, at 3:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > We tend to do this differently. For example, on mail.python.org which > currently has 261 Mailman 2.1 lists and 134 Mailman 3 lists and sends > about 135,000 individual messages per day from the two Mailman > instances, we define in /etc/postfix/master.cf > > 127.0.0.1:8026 > inet n - - - - smtpd > -o smtpd_authorized_xforward_hosts=127.0.0.0/8 > -o mynetworks=127.0.0.0/8 > -o smtpd_recipient_restrictions=permit_mynetworks,reject > -o smtpd_client_restrictions= > -o smtpd_helo_restrictions= > -o smtpd_sender_restrictions= > -o smtpd_data_restrictions= > -o receive_override_options=no_unknown_recipient_checks > -o smtpd_milters=inet:127.0.0.1:8891 > > Then port 8026 only accepts locally generated mail and only does dkim > signing (milter on port 8891) and essentially no other checks. > > Then in the [mta] section in mailman.cfg we only need > > smtp_port: 8026 Yep - I used to do something similar back when I was running dspam with mm2.1. This is a slightly more complicated to set up, but cleaner. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

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

by skenny＠scss.tcd.ie

I've found that dropping files in to the templates directory is a simple and convenient way to make certain things happen. E.g. I can set a default footer for all posts by putting the desired content in a file called var/templates/site/en/list:member:generic:footer.txt. I'm running Mailman 3 in maxking's Docker container. I'm also using Puppet to do as much configuration as possible, so I'd like to add a comment to the file that reads something like: # This file is managed by Puppet. Is it ok to do this? I may not have searched the docs enough, but I couldn't find anything relating to comments. One other observation in case it's any use: Initially, I created the template files with owner set to "root". This resulted in postings to lists getting stuck in mailman-core. It's vital that these files are owned by user "mailman". Once I changed the owner of the file to the latter, everything worked. Stephen

5 years, 3 months

[MM3-users] Re: [Mailman-Developers] How to know the URLs for CURL while getting or modifying the data of mailman 3

by Stephen J. Turnbull

Shashi, This whole thread is off-topic for the developers list. This list is for development of Mailman, not for teaching people to use it. Read the whole recommended documentation before you ask busy developers to tutor you in very basic things. There's a mailman-users(a)mailman3.org list for users to help each other. All of the Mailman developers who might be willing to answer your questions are there as well, but there are also many experienced users, some of whom have experimented with the REST API who will also help. Please reply there for further help. (Reply-To is set.) That said, there are plenty of URLs in the API documentation. Here's a hint: search for "dump_json". That function takes an URL. You may want https: instead of http: in your URLs, and you may need to change the port from 9001, depending on the configuration of your REST server. Try it with simple GET requests for information first, such as for domains or lists. You can also do these requests with an ordinary web browser, though I don't know what it will do with the JSON-formatted reply. If you don't have domains and lists configured, I suppose the informational requests will come back as empty JSON objects. It should be safe to make them. You can either use Postorius to bootstrap a few example domains, lists, and users, or (the hard way) figure out how to POST appropriate requests. I don't recommend trying to update the backend DBMS by hand; the schema is quite complicated. I don't know how to use curl to update Mailman's databases. That requires a POST request which I have never done with curl. The POST request needs to be valid JSON. The more I think about this, the less I think your idea of using curl is worthwhile, because formatting JSON requests by hand is going to be a real annoyance and a great way to mess up your database with spurious information. You're really going to want programmatic support for this. But that's already all available in Python in the Mailman system. It's up to you, but I feel a responsibility to warn you that using curl is not going to be simpler than learning enough Python to do these things. Regards,

5 years, 6 months

[MM3-users] Re: Strange error in uwsgi-error.log

by brian＠emwd.com

Derek Lambert wrote: > Brian, > > When I was seeing this, new lists weren't showing in HyperKitty. > > I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from > functioning. I had to drop the constraint to get the lists in. None of them have a > description now. > > Was this working for you in the past? If so, did you do any updates recently? > > Derek Lambert Hi Derek, Actually you are right. None of my new lists are showing in http://mailmam3domain/hyperkitty/. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install. How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched. Brian

6 years, 8 months

[MM3-users] Re: Best guide for installing from pypi

by Duane Raymond

Thanks Jacob and Abhilash, I've had enough of trying to do it myself so I've asked Brian (I'd previously asked him but he only does it on vanilla machines and I wanted to use an existing setup). I'll learn from his work once it is running and see what I can do without a migration deadline looming over me ;-) Cheers, Duane On Wed, 24 Feb 2021 at 04:02, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi, > > > On Tue, Feb 23, 2021, at 10:00 AM, duane(a)fairsay.com wrote: > > Hi. > > > > I've got a partial mailman3 install done and, based on the > > documentation, am not sure how to complete it! (this is my first time) > > > > I've installed mailman3 (3.3.3) on a Debian 10 server using python3.7, > > mysql, postfix, apache, etc. and have run the install using pip3 > > install mailman. The "mailman info" command works, version shows > > "3.3.3 (Tom Sawyer)" the databases creates, tables, all exist, etc. So > > it seems the necessary services are running. I'm running froxlor on the > > server to configure the non-mailman services (apache, ssl, postfix, > > etc). I had also tried apt install mailman-full but it was an older > > version, so using the pypi route ensured I was on the latest version. > > I don't know anything about Froxlor, so I won't be able to help with > any issues caused due to that unfortunately. > > > > > Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html, > > what I can't figure out is: > > 1) There is no /opt/mailman/ user - the user installed seems to be > > "list" > > The user recommended to create is "mailman" with "/opt/mailman" > as the home directory for the user. Debian systems use the "list" > user to run Mailman. You can simply substitute the user from > mailman to list, the name itself doesn't make a lot of different, just > make sure you do change the name in systemd config files and > sudo commands that you use. > > > 2) Is a virtual environment needed for a production environment? > > It is recommended by Linux distros that you don't install from pip > directly into the system's site-packages. This can *potentially* > have side effects and break other systems that rely on Python > packages installed on your system, some which you might not > even be aware of that relies on Python (like, Yum package manager > does in RHEL systems). > > Hence, if you aren't use the system packages to install Mailman, > it is recommended that you use an isolated Python virtualenv. > > > 3) if django is setup properly or the webservice is working > > 4) I've tried to connect to some web interface > > (posterious/hyperkitty/some mailman3 web frontend) via lynx to > > localhost:8001 on the local machine - but it has a 404 error > > 8001 is Mailman Core's API endpoint. To test Web Frontend, > you want to reach out to: https://<mydomain>/ after configuring > your Nginx to reverse-proxy the uwsgi. > > Uwsgi runs a custom protocol, also called uwsgi, which Nginx > understands and is able to reverse proxy. You can't use Lynx > to test that. However, if you do want to test your service > locally, you can add this line the uwsgi.init[1] after the > "uwsgi-socket" line: > > http-socket = 0.0.0.0:8080 > > This will make uwsgi also accept HTTP connections on Port > 8080 that you can use to test. > > > [1]: > https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws… > >

4 years, 8 months

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/9/25 13:58, via Mailman-users wrote: > > I have updated the welcome message for a mailing list by directly updating the file at: > file:///var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au/en/list:user:notice:welcome > > I then restarted theses services: mailman3, mailman3-web and nginx. > > But when I test subsribe to the mailing list, the welcome message does not update. > > GNU Mailman 3.1.1 (Between The Wheels) > Postorius Version 1.1.2 These are extremely old - over 7 years. This may have something to do with the issue. There may be an issue in that the template table in the database is saying to look elsewhere. What do you get for a database query like ``` SELECT uri FROM template WHERE name = 'list:user:notice:welcome' AND context = '[redacted].lists.[redacted].org.au'; ``` where `[redacted].lists.[redacted].org.au` is the actual list-id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 3 weeks

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

by Mark Sapiro

On 6/30/21 9:23 PM, Mark Sapiro wrote: > On 6/30/21 6:23 AM, Lucia Moreno wrote: >> Hi Mark, >> >> We are facing the same issue. My postgres database is growing too fast >> and >> I would need to do some creaning of old archives dated from 2001 and keep >> only the last, lets say... 5 years. >> >> Could you please help us with the development of such a script? I have no >> experience in python. > > The attached script is a rough idea. Another way to do this that might actually be preferable is to download the entire archive from HyperKitty as a mbox, then split the mbox into what you want to keep and what you don't, delete the list from HyperKitty and then run hyperkitty_import to import only the messages you want to keep. -- 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: Help needed to create filters that were working in Mailman 2.

by Mark Sapiro

On 6/20/23 11:04 PM, mrl(a)psfc.mit.edu wrote: > How do I make a filter that if it matches, it accepts the message and doesn't check the remaining filters? > > I could do this using the anti-spam filters in mailman 2, as there was a Accept option. > > But there is no Accept option in Mailman 3 (that I can find). > > I tried using "Default antispam action", but that didn't stop the rest of the filters from being applied. The default action for "Default antispam action" is "hold" but you can change that to "accept" by setting ``` jump_chain: accept ``` in the [antispam] section of mailman.cfg, however current Postorius offers "Accept immediately (bypass other rules)" as a choice for the Header Filters action. Does yours not? What is your Postorius version? -- 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: Change config to create a new list with all archives off

by Danil Smirnov

Hi Steve, I tried to use your approach today: On Fri, Jun 2, 2023 at 8:30 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> 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) > mlist.archive_policy = ArchivePolicy.never > -------------------------------- cut here -------------------------------- > > In mailman.cfg find and modify or create: > > -------------------------------- cut here -------------------------------- > [styles] > default: archives-disabled > -------------------------------- cut here -------------------------------- > I used it with a different source list - it's PrivateDefaultStyle. When I try to create a new list using the new custom style I get an error: 2024-04-21 12:16:08 [FALCON] [ERROR] POST /3.1/lists => Traceback (most recent call last): File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/usr/lib/python3.11/site-packages/mailman/rest/lists.py", line 321, in on_post mlist = create_list(**validator(request)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/site-packages/mailman/app/lifecycle.py", line 100, in create_list style.apply(mlist) File "/usr/lib/python3.11/site-packages/mailman/styles/default.py", line 107, in apply super().apply(self, mailing_list) TypeError: PrivateDefaultStyle.apply() takes 2 positional arguments but 3 were given > Untested, feel free to ask if it doesn't seem to work. > Could you check what's the issue, please? Danil Smirnov This really should be implemented as a plug-in so default.py being > overwritten in an upgrade won't be a problem, but the plug-in API is > annoyingly complicated and the example plug-in over-engineered, and I > couldn't get it to work (and in the project where I learned to do this > I am not being paid enough to care ;-). The approach above was > straightforward. > > Eventually I'll get around to doing the plug-in approach, and maybe in > the meantime Mark or Abhilash will speak up. If Those Who Know don't > show up soon, ask again in the medium term (but before you update > Mailman and it gets overwritten :-). > > Steve > Sincerely, Danil Smirnov

1 year, 6 months

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 10:42 AM, Rafael Mora wrote: > > I've found the MX records on my cpanel but how do I redirect the emails > going to my list to my private server? You have to configure the MTA that is the MX for the domain to relay the mail to the Mailman server. > I still don't get it. What if I just suscribe the members and then send the > email to the suscribers the thing is that the email has to be received by > mailman in order to resend it to the list suscribers right? If all you want to do is send mail that you generate, you can use mailman inject to deliver the mail to Mailman on the local machine. The drawback of not being able to receive mail from the outside is Mailman won't receive bounce DSNs from remote servers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] [Older bug, but still unsolved] When deleting one or more threads in an archive, django send error mails (based upon "Thread matching query does not exist")

by Wikinaut

I installed the venv version to scrutizine whether this old bug is still present (yes it is). How to reproduce: Delete one thread in via the archive - thread - view page. Remark: Thread is deleted as wanted. However, django complains via several (here: two) error mails: 1st mail: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/test(a)example.com/top-threads Internal Server Error: /archives/list/test(a)example.com/top-threads DoesNotExist at /archives/list/test(a)example.com/top-threads Thread matching query does not exist. ... 2nd mail: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/test(a)example.com/posted-to Internal Server Error: /archives/list/test(a)example.com/posted-to DoesNotExist at /archives/list/test(a)example.com/posted-to Thread matching query does not exist. ... I wish to fix this problem, how can I help, what can I do? Do you need the full error stack?

2 years

[MM3-users] Re: configuration to send to recipients in a spread out manner to avoid being considered spam

by Odhiambo Washington

On Sun, Nov 19, 2023 at 3:25 PM testeur via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi, > > I s there a mean to configure the list for that emails be sent to > recipients in a spread out manner to avoid being considered spam ? cause > AOL, YAHOO seems to consider emails sent to recipients as spam or an > "Excessively high volume of emails". there's just 40 (aol, yahoo) emails > suscribed to the list. > > thx. > I believe this is doable within your MTA - Postfix or Exim. In Exim, we do something like this: https://lists.exim.org/lurker/message/20080818.185617.b5534450.en.html Hopefully, it gives you a clue on what you can do for your MTA. -- 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, 11 months

[MM3-users] Re: configuration to send to recipients in a spread out manner to avoid being considered spam

by testeur

Then i ve to watch more on postfix options. very thanks ! On 19/11/2023 13:39, Odhiambo Washington wrote: > On Sun, Nov 19, 2023 at 3:25 PM testeur via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Hi, >> >> I s there a mean to configure the list for that emails be sent to >> recipients in a spread out manner to avoid being considered spam ? cause >> AOL, YAHOO seems to consider emails sent to recipients as spam or an >> "Excessively high volume of emails". there's just 40 (aol, yahoo) emails >> suscribed to the list. >> >> thx. >> > I believe this is doable within your MTA - Postfix or Exim. > > In Exim, we do something like this: > https://lists.exim.org/lurker/message/20080818.185617.b5534450.en.html > Hopefully, it gives you a clue on what you can do for your MTA. > >

1 year, 11 months

[MM3-users] Re: Mail configuration

by a.matveev＠lan-project.ru

> I'm not sure if this is the correct forum for this question, but I'm pretty > sure if there is expertise on how to do what I want to do, it can be found > here. > > Overview of what I am looking to do: > > Due to the impending shutdown (in the next 6 months) of the data center > where our mailman server lives, we are being forced to move the > installation. We are going to be moving it to a different location. > > Here is our problem... > > Moving things is not really a problem in and of itself - I'm confident that > I can get things set up correctly elsewhere. However, our email server > sends somewhere around 100,000 emails per day, and if you cut over from one > IP address to another IP address, my understanding is that most ISPs will > start to ban you, because they are not used to that sort of volume coming > from an unknown IP. I know it would be better if we could keep the IP > address, but again, due to circumstances beyond my control, this is not > going to be a possibility. > > We have been told that "warming up" the IP is the way to go - that is, > cutting over just some of the traffic a little at a time. So what I am > looking for is a way for all mail on our domain to be sent to our current > mailman installation, and based on some configuration (certain mailing > lists?) certain emails being sent out to the list subscribers will first be > forwarded to the new server and be sent from the new IP address. > > Does that make sense? > > Does anyone know a way that mailman/postfix can be configured to accomplish > this? > > Is there a different forum where I might be able to ask experts about this? > > Thanks, > > -Darren Hi Darren Your current IP(s) is used for correct PTR lookups, when remote mail server is decide to receive or reject your mail. So when you change your IP for outgoing mail server (or mailman, if mta on the same host such as postfix ), you must update those records in DNS. This takes some time. If you know your new IP, you may add new PTR for it and when it start resolves, just switch working services.

7 years, 7 months

[MM3-users] Re: Managing users

by Abhilash Raj

On Fri, Mar 1, 2019, at 12:42 PM, worik wrote: > Is there a interface for managing users? > > I can use the data base directly to query `auth_user` etcetera, but > Postorious? What are you actually trying to do? "managing users" doesn't tell me how to help you out. In general, it is not a good idea to change the internal database without using any of the public apis, unless you are just trying to read things. If you are talking about web interface, then you can go to the admin console `/admin` on your installation and there should a list of users and Email addresses there. > Worik > > -- > If not me then who? If not now then when? If not here then where? > So, here I stand, I can do no other > root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) > _______________________________________________ > 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: Clearing webserver cache - Nginx

by Odhiambo Washington

On Mon, Aug 5, 2024 at 9:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/5/24 10:30, Odhiambo Washington via Mailman-users wrote: > > > > Actually, what I mean is that CF is proxying requests to the host named > > m3-lists.kictanet.or.ke. > > I do not have any configuration other than DNS proxying at CF. > > ``` > dig a mm3-lists.kictanet.or.ke > ... > mm3-lists.kictanet.or.ke. 300 IN A 172.67.167.73 > mm3-lists.kictanet.or.ke. 300 IN A 104.21.11.217 > ``` > Both of those are cloudflare IPs, and why 2? > Yes, those are Cloudflare IPs and I don't know why 2! All I know is that in DNS, I created an A record for the hostname and chose the "proxy" option in the cloudflare DNS management interface. > > So when you talk to m3-lists.kictanet.or.ke via a browser, it's CF IP > who you talk to and it in turn talks to the host directly. > > And how is that configured? > You add the domain - kictanet.or.ke to CF's control panel. They give you TWO name servers. You substitute the NSes your registrar gave to your domain for those two. Subsequently you create A|CNAME|MX\TXT records on the CF's control panel. You decide whether an A or CNAME record you create is proxy-ed or not. If you proxy the record, no one will ever get to know its real IP, but if you don't proxy, then the dig tool above will tell you the real IP address. > So the IP address you see in the logs is CF's IP address, not yours, not > > mine and CF are doing some caching. That's why > > they are requesting for expired files. > > > Why is cloudfare trying to > access /opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css locally if > all it is doing is proxying the request to the actual mailman server? > I don't know. However, those IPs you see in the Nginx logs, none belong to me! I have two possible IPs - one domiciled in KE and another domiciled in the US (when I use VPN). -- 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, 2 months

[MM3-users] Re: Issues with international characters (replaced by ?) when mail is send as text/html

by Mark Sapiro

On 1/11/22 7:08 AM, Michal Soltys wrote: > Hi, > > I have noticed that any mail send with text/html, e.g. with following > headers: > > Content-Language: en-US-large > Content-Type: text/html; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > is slightly transformed by mailman3 - the body is put into its own part, > but all the international letters are replaced by question marks. The body being put in its own part is because of message decoration. In order to add the list's message header and/or footer the message is recast as multipart/mixed and the header and/or footer are added as separate MIME parts. See https://wiki.list.org/x/4030707 for an explanation of why this is done for non-plain text messages. > Having searched the list I tried: > > 1) adding following to mailman.cfg: > > [language.master] > description: English (USA) > charset: utf-8 > enabled: yes > > [language.en] > description: English (USA) utf8 > charset: utf-8 > enabled: yes I would have expected that to work. > 2) changing preferred language of a mailing list to something else via > shell, e.g.: > > m.preferred_language = 'pl' That should be m.preferred_language = getUtility(ILanguageManager).get('pl') > > 3) changed default_language to 'pl' in mailman.cfg I would have expected any of those things to work, but I can see that they don't. I'm looking into why. > 4) Ensured all relevant glibc locales are generated (not sure if that > matters though in this case) > > > None of this seems to have any positive result - all mails, whether > under 'pl' or 'en' setting still get all non-ascii chars replaced with > question marks (in html case, probably(?) in any case where it becomes > multipart). > > Any ideas what to do so html mails are passed without filtering out > their characters ? Do I have to recreate all mailing lists under new > [language.en/master] settings ? No, this is a bug. It has to do with message decoration (adding of headers and footers). You can probably avoid this issue by setting the list's filter_content and convert_html_to_plaintext to True. I am looking at why this occurs and fixing it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Deactivate list without deleting it?

by Stephen J. Turnbull

Colin Watson writes: > 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, > Postorius would deny its existence, etc. [...] > Has there been any discussion of this in the past, or any advice as to > implementation strategy? I don't recall anybody discussing this. Your use case is your use case, but I think if we were going to implement this I'd probably want "partial" deactivation where the archives remain available but no mail is delivered, can't subscribe, etc. I'm also not sure I'd want Postorius to deny it ever existed. That seems rather unfriendly (again, I don't understand your use case, so that is not a comment on your requirements). So to get it into the distribution we'd need to make these things optional. (Perhaps if these options proliferate much, they could be incorporated into list "styles" so that instead of setting all the options manually, the primary use cases could be served by "intuitively" named styles.) It seems to me that dump, delete, and restore may be the best approach for the HyperKitty side because HyperKitty maintains all that state. Of course this could be done inside the database. Also, perhaps you can (ab)use the ArchivePolicy enum by adding an "inactive" element, but core has no way to enforce those on the archiver (which can be a third party host like mail-archive.com) and I'm not sure HyperKitty ever consults core about that once the archive is created. I'm not sure what you mean about IArchiver; as far as I can see that interface is sort of half-duplex: it provides the information core needs *about* the archiver to do core's side of archiving, not for core to communicate *with* the archiver. In fact all of the concrete code is callbacks provided by the archiver, and once a message is archived the core forgets about it. So this isn't "just" an extension; it's a fundamental redesign of IArchiver. I'm not sure that's not a good thing, but we do need to think about it. ISTM we're gradually converging back on the monolithic approach to MLM, with the distribution, administration, and archiving quite tightly interwoven, and I'm not sure I like that. OTOH, we do get a lot of requests for ever more bundling.

7 years, 9 months

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark London

Andrew - The script had: DELETE_MAILMAN_USER = False When I set it to True, it got rid of the orphaned email addresses. Thanks! - Mark On 4/25/2023 6:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py > > I have it running in a cronjob. Thread discussing the script can be found here: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > TLDR you end up with orphaned Django users both from when users subscribe/unsubscribe and due to spam signups using the Postorius form which never get confirmed. > > Thanks. > Andrew.

2 years, 6 months

[MM3-users] Re: Disabled by bounce

by Jan Eden

On 2023-02-20 19:03, Stephen J. Turnbull wrote: > Jan Eden via Mailman-users writes: > > > To distribute messages with valid DKIM signatures, I set > > > > remove_dkim_headers: yes > > > > in /etc/mailman3/mailman.cf > > That should be "mailman.cfg" for a standard installation, and it may > not be in "/etc/mailman3" in a shared hosting situation. > > Do you have evidence that removing DKIM headers helps you get mail > delivered? (Not adding your own, IMO you should do that regardless of > whether you strip existing ones, but removing originals.) The DKIM > spec says that you shouldn't, and that consumers should treat invalid > signatures no differently from missing signatures. I haven't run into > a "public" host that treats an invalid signature as a problem in quite > a while. Right – removing the invalid DKIM signature is just a matter of taste. I tested message distribution with and without signature removal, and two major mail providers did not handle the messages differently. - Jan

2 years, 8 months

[MM3-users] Re: Issues with @gmail.com addresses

by Stephen J. Turnbull

Jeremy Stanley writes: > On 2023-09-09 01:21:32 +0900 (+0900), Stephen J. Turnbull wrote: > [...] > > We could easily have an option to not attach the messages to the > > notifications, just a list of most useful headers, or simply a > > statement of how many if you really want to be minimal. > > A number of our lists would probably make use of that if it were an > option, though sadly my dance card is too full to code the feature > any time soon. Turns out there's already an RFE in the GitLab tracker: https://gitlab.com/mailman/mailman/-/issues/670 I added "easy" and "beginner-friendly" to the issue. I'm not so sure if that's true of the follow-on RFE (the change to Postorius, which I did not yet create ;-), but we can cross that bridge when a volunteer shows up. :-) Do you know if the whole spammy mail is needed to trigger the overly sensitive sites, or if just From: and Subject: can do it?

2 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

HyperKitty is looking for some files in /static/CACHE/... but it doesn't find them: [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" 404 107 [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 Should I run any command to activate the CACHE dir? El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Re: alembic.util.exc.CommandError: Can't locate revision identified by xx

by Lars Bjørndal

Problem solved, description below On Tue, May 13, 2025 at 11:27:14AM +0200, Lars Bjørndal wrote: > One more enlightment: > > On Tue, May 13, 2025 at 11:09:10AM +0200, Lars Bjørndal wrote: > > I upgraded my Fedora distro from v.40-41. I did > > > > pip install wheel mailman psycopg2-binary > > > > When running the mailman command, I get > > > > alembic.util.exc.CommandError: Can't locate revision identified by > > '8cc1f79f4459' > > > > How do I solve this? > > mailman --version gives: > > GNU Mailman 3.3.9 (Tom Sawyer) > > But in my old venv installation folder, I have files like venv.old/lib/python3.12/site-packages/mailman-3.3.10.dist-info/RECORD:mailman-3.3.10.dist-info/entry_points.txt, e.g. 3.3.10. How could that happen? And how do I go on further to get mailman3 up and running? Fedora 41 use Python3.13, and one dependency for mailman-3.3.10 isn't available. I installed the virutalenv uppon python3.12, and the problem is solved. Lars

5 months, 3 weeks

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/3/25 08:01, dap1--- via Mailman-users wrote: > > Anyway, I still need help. I migrated my mailman2 to mailman3 per the documentation and all seemed to go well. However, now that I have the web UI working, no lists show up. Indeed, using mysql, all the relevant tables in mailman db are empty. How do I figure out if the import really worked when there are no error messages? If `mailman import21` didn't report any errors, it really did the import. Likewise if `mailman-web hyperkitty_import` didn't report any errors, it really did the import. If you followed https://docs.mailman3.org/en/latest/install/virtualenv.html your database is postgreSQL, not MySQL. What do you have in the [database] section in /etc/mailman3/mailman.cfg and in the DATABASES definition in /etc/mailman3/settings.py? Based on https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I think you have more than one configuration and things are confused between them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 day, 13 hours

[MM3-users] Re: Problem with missing MySQLDatabase

by Peter Sørensen

Hi Mark, Unfortunately I answered on ³auto response not sent² instead of this - sorry. In the meantime I found one problem. The comment I¹ve put at the end of line ## MOD .. This is not the way to do it in Python. I normally use Perl and not a Python as script language. Deleteing the #Š Made this problem disappear but instead below problem showed up. /etc/mailman3# mailman aliases Traceback (most recent call last): File /usr/bin/mailman, line 11, in <module> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() File /usr/lib/python3/dist-packages/mailman/bin/mailman.py, line 94, in main initialize(config_path) File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line 189, in initialize initialize_2(propagate_logs=propagate_logs) File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line 160, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File /usr/lib/python3/dist-packages/mailman/database/factory.py, line 54, in create database.initialize() File /usr/lib/python3/dist-packages/mailman/database/base.py, line 106, in initialize self.engine = create_engine(url, isolation_level='READ UNCOMMITTED') File /usr/lib/python3/dist-packages/sqlalchemy/engine/__init__.py, line 387, in create_engine return strategy.create(*args, **kwargs) File /usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py, line 80, in create dbapi = dialect_cls.dbapi(**dbapi_args) File /usr/lib/python3/dist-packages/sqlalchemy/dialects/mysql/pymysql.py, line 62, in dbapi return __import__('pymysql') ModuleNotFoundError: No module named Œpymysql' I have installed pymysql with: pip install pymysql When I do this once more I get pip install pymysql Requirement already satisfied: pymysql in /usr/local/lib/python2.7/dist-packages Requirement already satisfied: cryptography in /usr/lib/python2.7/dist-packages (from pymysql) So the problem has probably to do with this installed in python2.7 and not python3. How do I solve that ? Best regards Peter Sørensen University of Southern Denmark Den 19/10/18 19:13 skrev "Mark Sapiro" <mark(a)msapiro.net>: >On 10/19/18 3:44 AM, Peter Sørensen wrote: >> Hi, >> >> I have looked into installing this before without success but found >> The Debian package Mailman3-full >> >> I installed this succesfully along with the mailman-suite. >> I have configured varios setting but are stuck when trying to generate >>aliases >> For mailman with: >> >> mailman aliases >> Traceback (most recent call last): >> File /usr/bin/mailman, line 11, in <module> >> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() >> File /usr/lib/python3/dist-packages/mailman/bin/mailman.py, line 94, >>in main >> initialize(config_path) >> File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line >>189, in initialize >> initialize_2(propagate_logs=propagate_logs) >> File /usr/lib/python3/dist-packages/mailman/core/initialize.py, line >>160, in initialize_2 >> config.db = getUtility(IDatabaseFactory, utility_name).create() >> File /usr/lib/python3/dist-packages/mailman/database/factory.py, line >>52, in create >> database = call_name(database_class) >> File /usr/lib/python3/dist-packages/mailman/utilities/modules.py, >>line 67, in call_name >> named_callable = find_name(dotted_name) >> File /usr/lib/python3/dist-packages/mailman/utilities/modules.py, >>line 50, in find_name >> __import__(package_path) >> ModuleNotFoundError: No module named >>'mailman.database.mysql.MySQLDatabase\t\t\t#MOD(inserted ) 02'; >>'mailman.database.mysql' is not a package >> >> I can see from the message that I¹m missing a module but I can¹t figure >>out. how to get >> This installed. The mudule is referenced in the mailman.cfg as >> class: mailman.database.mysql.MySQLDatabase > > >The module mailman.database.mysql is part of mailman core. In your case, >it should be /usr/lib/python3/dist-packages/mailman/database/mysql.py. >If that file exists, I don't know what the problem might be. If not, >there is something wrong with your installation. In any case, this is a >Debian issue. You need to take it up with Debian. > >-- >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/

7 years

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Terri Oda

On 2016-12-12 12:29 AM, Stephen J. Turnbull wrote: > Barry Warsaw writes: > > > >I can also work on Postorius. Also in this vein I have a question. > > >Should the DMARC settings be added to the Alter Messages tab in the List > > >Settings view or would it be better to have a separate DMARC Mitigations > > >tab. > > > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > > Terri have final say I think. > > I would find it more natural to have "Posting Policy" (which would > include posting filters on size and list membership, as well as > message alterations such as removing .exe files and enforcing plain > text by removing or rendering HTML parts), and "Malware Mitigation", > which would include IP, domain, and mailbox filters as well as DMARC. > I think DMARC mitigation is probably too special to deserve its own > tab. Alter messages tab works for me, but DMARC is kind of a big enough deal (as far as mail delivery goes) and sufficiently different that I agree with Mark that it's not unreasonable to give it a separate tab. I'd be willing to start it on its own and move it if we're getting too cluttered later, as long as we document it in the release notes when we do. Florian, what do you think? > Probably this is way too much reorganization to do at this point, but > I'd like to keep this point in mind. We are already getting reports > that configuration options are hard to find just because it's > different from Mailman 2. I suspect that the REST API is sufficiently > flexible and regular that we'll be tempted to proliferate options, so > let's try to keep them organized. We also get reports that mailman 2.1 options are hard to find -- I think I personally help someone find something at least once a month (on irc, in person, or by email) for the past decade. :) I imagine Mark has answered a lot more of those than I have. The big thing I want is good documentation here. There's never going to be an organization that works for everyone, but an easily searchable document with all the options would make a big difference. I only got to that level with the user docs not the list admin docs in 2.1

8 years, 10 months

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Mark Sapiro

On 10/31/18 5:57 AM, Thomas G wrote: > Hi, > > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… > > I changed "sender" for this; > # Sender > try: > from_str = header_to_unicode(message['From']) > from_name, from_email = parseaddr(from_str) > from_name = unidecode.unidecode(from_name).strip() What is unidecode? > except (UnicodeDecodeError, UnicodeEncodeError): > raise (ValueError("Non-ascii sender address", message)) > > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown(a)unknown.com" > else: > sender_address = "unknown(a)unknown.com" > print("Non-ascii sender addre -- Sender address replaced by ", > sender_address) > > I got this output (example): > |Non-ascii sender address -- Sender address replaced by > stephaneblipblopstlablipblopgmailcom > It's not really perfect, I'm working to do something better, but basically > it's works. The original code intends to provide some value for the email address where parseaddr returns a null address. You have an address, and you would do better to remove the non-ascii from the address than to try to make and address out of the sanitized real name. Your issue is parseaddr() returns an email address with non-ascii. I would suggest that instead of > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown(a)unknown.com" > else: > sender_address = "unknown(a)unknown.com" you do > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > sender_address = from_email.encode('ascii', errors='replace').decode("ascii").strip() > I think that there is a issue in the original code: > Because : "" raise ValueError("Non-ascii sender address", message) "" > > The second part will be never call: It will if there is no exception. > if not sender_address: > if from_name: > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > if not sender_address: > sender_address = "unknown" > sender_address = "{}(a)example.com".format(sender_address) > else: > sender_address = "unknown(a)example.com" > > If you bypass : "" raise ValueError("Non-ascii sender address", message) > "", by a simple print(), you will get an error due to an unassigned > variable (sender_address). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Gmail/Fetchmail in Mailman3?

by Mark Sapiro

On 06/23/2018 02:48 PM, Bill Christensen wrote: > > Our Mailman2 setup uses Fetchmail to retrieve list mail from our > accounts on Gmail. > > Is there a similar setup for Mailman3? Delivery to Mailman is different in Mailman 3. What are you currently doing with Fetchmail? If you are doing something like getting the mail from google and delivering it via SMTP to an MTA on the Mailman server, that should still work for MM 3. If Fetchmail is piping it to a command like "| /path/to/mail/mailman post listname" that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP server (which it calls a runner). Mail is normally delivered to an MTA which is configured to relay the mail via LMTP to the localhost port that Mailman is listening on. So Fetchmail can eithr deliver to the MTA and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Cannot setup announce-only mailing list

by Mark Sapiro

On 2/1/20 9:53 AM, Abhilash Raj wrote: > > > On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: >> >> In short, you need to set this up manually using things like moderation >> settings and custom templates for the welcome message. > > Mark, do you think we should make the actual announce-only style reflect > these settings so folks don't have to manually set these after they create > a announce-only list? > > I am not sure the reason behind these settings lacking for the current > announce-only style. Are there situations where announce-only list would > have different list setting? I think it was probably done as it is just as a start. I do think it would be good to set more things appropriately for the announce-only style, ultimately we may need to add templates for post rejection notices and 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

5 years, 9 months

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Stephen J. Turnbull

Peter Münster writes: > On Wed, Aug 31 2022, Stephen J. Turnbull wrote: > > > Do you really mean "en"? > > Yes. Since this is the only file under the templates-directory, it > should be used according to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… > > Or do I misunderstand something? No, I was just making sure because Mark's message that you quoted mentioned "de", and you have an umlaut in your name. Come to think of it, I'm not even sure Mark was replying to you, but for what it's worth that was my thought process. :-) I'm not very familiar with Django's handling of such files, but my understanding is that many files are collected from various places using manage.py's collectstatic command. I don't remember whether these templates are among them. That's the only thing I can think of offhand. If that's not it, I'll try to get back to this on Saturday. Steve

3 years, 2 months

[MM3-users] Re: Problem with perms on /etc/mailman3/mailman.cfg while following https://docs.list.org/en/latest/install/virtualenv.html on new mailman3 Debian 12 installation

by Mark Sapiro

On March 25, 2025 1:20:22 AM GMT+07:00, Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > >The instructions https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… do not say what to do with existing file. > >root@shackleton12:~# ls -alF /etc/mailman3/mailman.cfg >-rw-r--r-- 1 root list 11119 Mar 20 11:45 /etc/mailman3/mailman.cfg > >Should we move the /etc/mailman3/mailman.cfg out of the way and create new file as user and group mailman:mailman ? How did that file get there? It looks like at some point you installed the Debian package. If you are following <https://docs.list.org/en/latest/install/virtualenv.html you shouldn't install the Debian package. In any case, just remove the file. Probably it's best to remove the Debian package completely and start over. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

7 months, 1 week

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

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210212 12:04]: > hansen(a)rc.org writes: > > 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.... I thought user could do that if they have an web account, and multiple mail addresses are associated with the account? Or does my memory serve me wrong there? Andi

4 years, 8 months

[MM3-users] Bounce handling after upgrade

by David Krantz

Hi, I am in the process of configuring a new mailman3 server based on my old one. This includes upgrading to the latest version of mailman and installing a database upgrade. To my surprise mailman core started by sending tens of mails and blocking the corresponding users for very old bounces. What is worse is that this happens every time I start mailman core. Now I have blocked (almost) all outgoing mail in postfix using a transport map which discards it but this is a temporary testing measure of course. When I deploy this server into production, I do not want these recipients to be blocked as the old problems have been solved since very long. My plan is to reload the database from a newer backup anyway... Would it be enough to empty the bounce table (bounceevent) or is there anything else driving this behaviour? Or is there a better way to do this via the mailman shell? For me a "delete from bounceevent" seems a lot simpler than anything via the shell but there may be dependencies in the database. Cheers // David

5 years, 3 months

[MM3-users] Re: Mailman 3 Installation

by Mark Dadgar

On Jan 17, 2021, at 11:01 AM, Andreas Barth <aba(a)ayous.org> wrote: > > * Mark Dadgar (mark(a)pdc-racing.net) [210117 19:59]: >> Do not "just start with sqlite to get it running and then I’ll >> migrate it to something else down the road.” There is currently no >> validated way to migrate a mailman3 instance from sqlite to >> something else, and by “no validated way” what I actually mean is >> “no one has managed to get this to work, me included.” > > I need to disagree to the last part of the sentence because I did it, > but my strong recommendation based on expirence is: save the effort, > start directly with postgresql. It's not much more work, and migrating > is .. well, just don't try or do it. 😁 Did you document it anywhere? I could not find evidence of a successful migration when I looked 6 months ago, including in this list’s archives. That would be great information for the community, if only as a cautionary tale. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by David Partain

Hi Mark & all, Thanks for the response. Just picking up where we are at the moment to provide a bit more info, in case you have ideas. Thanks, Stephen T. as well for the idea of turning on DEBUG. We might resort to that in the end. This is what our system is running right now: Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] As previously noted, we moved this off of an old Ubuntu package-based installation that has delivered mail reliably but many other things haven't worked well, so we're happy to be on something that might improve that situation. Right now, archiving is not working on the new installation, both building the archive on the new installation after the move and for new messages. uwsgi-error.log is getting blasted with constant errors along the lines of what follows. I suspect that these errors are why archiving isn't working, but I obviously don't know that: Message: BadSignature('Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match') Arguments: ('Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher task = SignedPackage.loads(task[1]) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads return signing.loads( File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age)) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign result = super(TimestampSigner, self).unsign(value) File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign raise BadSignature(\'Signature "%s" does not match\' % sig) django.core.signing.BadSignature: Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match',) What we have in our config files on the old installation and new installation are (the quotes are exactly as they are in the files): Old installation: mailman-web.py SECRET_KEY = 'somerandomstringiaintputtinginmail' MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail' mailman-hyperkitty.cfg api_key: somerandomstringiaintputtinginmail New installation: settings.py SECRET_KEY = 'somerandomstringiaintputtinginmail' MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail' mailman-hyperkitty.cfg api_key: somerandomstringiaintputtinginmail All of that says that the value is the same for all three (whether I should have done so or not...) and those settings were carried along to the new installation as well. Django is a big scary beast as I've not had to manage django apps before. Would it make sense that the error above is because what I _think_ django believes is the SECRET_KEY (in the config files above) is in fact not what django believes? Maybe it was set during installation (which I didn't do)? I don't believe anyone has purposefully changed it. I suppose I could do something like https://medium.com/django-unleashed/securing-django-applications-best-pract… to reset the secret key, but I'm not doing that on Friday afternoon :) If anyone has other thoughts, please holler. Wishing you all a good weekend from lighter-by-the-day Sweden. Cheers, David -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net<mailto:Mark%20Sapiro%20%3cmark@msapiro.net%3e>> To: mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> Subject: [MM3-users] Re: Badsignature on uwsgi-error.log Date: Wed, 20 Mar 2024 18:12:20 -0700 On 3/20/24 14:25, Helio Loureiro wrote: Hi, I keep receiving a lot of errors like this: --- Logging error --- Traceback (most recent call last): ... "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign raise BadSignature('Signature "%s" does not match' % sig) django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match ... The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY on setting.py are the same. Of those three, the api_key on mailman-hypperkitty.cfg and MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django thing and has nothing to do with the others. See https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key If you changed it, that's the issue. If you know what it was previously, you could set the previous value in SECRET_KEY_FALLBACKS, see https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks

1 year, 7 months

[MM3-users] Re: MM attaches mime-attachments to mail as text file since update to 3.3.8

by Mark Sapiro

On 1/23/23 22:50, Stefan Bauer wrote: > Dear Mark, > > thank you for your time. > > Here are the lists settings and an example mail attached. > > Filter content: NO > Filter types: EMPTY > Pass types: EMPTY > Pass extensions: EMPTY > Collapse alterantives: YES > Convert html to plaintext: NO > > Thunderbird is showing the mail "correct". Outlook does show the > attachments as attachments. So Filter content is NO so Mailman isn't doing any content filtering. All it is doing is adding headers and footers if any, and if the original message is other than a single text/plain part, these will be added as separate MIME text/plain parts. For a discussion on why this is done, see https://wiki.list.org/x/4030707 which is written for MM 2.1, but which applies at least generally to MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: bulk deletion of messages from Hyperkitty

by Timour Bakeev

Hi Mark! Mark Sapiro wrote: > On 7/10/24 12:27 PM, Danil Smirnov via Mailman-users wrote: > > I'm aware of the tools you mentioned and they were properly used. > > Your issue is almost certainly caused by unescaped From lines in > message bodies and preprocessing the mbox with the > hyperkitty/contrib/cleanarch3 script should fix those. Could you take a look at my MR for this script? Right now I have to use a locally modified version of it, as the one in contrib/ doesn't work out of the box. > > Please let us focus on the question I asked - how do we delete messages of > > a particular date if there are too many of them so using Hyperkitty UI > > isn't an option? > > You can do > DELETE FROM hyperkitty_email WHERE archived_date = <your datetime>; Thanks a lot for this detailed walk-through, it is very helpful and I'm going to use it to clean up my migrated archives. With best regards, Timur Bakeev.

1 year, 3 months

[MM3-users] rest api runner not running

by Christine

Hi, I have been using mailman for about ten years, now I want to move the lists to another server, I have installed mailman3 there, most of it seems to be running, but the "rest api runner" is not. Nothing is listening on port 8001. What have I missed? What do I do to start the restapi runner? I checked the logs, I don't see anything suspicious. this is what systemctl status says: root@lists:~# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Sat 2021-03-27 12:04:06 UTC; 6min ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 173111 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=killed, signal=TERM) Mar 27 12:02:36 lists systemd[1]: Starting Mailman3 server... Mar 27 12:04:06 lists systemd[1]: mailman3.service: start operation timed out. Terminating. Mar 27 12:04:06 lists systemd[1]: mailman3.service: Failed with result 'timeout'. Mar 27 12:04:06 lists systemd[1]: Failed to start Mailman3 server. There is nothing in mailman.log, nor in smtp.log dagdag Christine -- dagdag is just a two character rotation of byebye

4 years, 7 months

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by Mark Sapiro

On 7/30/21 10:47 AM, bob B wrote: > > Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? I'm not sure what the actual command would be do run the django-admin interface in the docker image, but from below, it looks like it's `mailman-web`. Run `mailman-web createsuperuser` to create an admin ID. > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. This command tries to send the mail via SMTP to localhost port 25. > How can I make sure my containers can send and receive mail? The MTA should be listening on port 25 and that need to be visible in the mailman-web container. See <https://asynchronous.in/docker-mailman/#setting-up-your-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, 3 months

[MM3-users] Re: Issues with @gmail.com addresses

by Stephen J. Turnbull

Peter Münster writes: > On Thu, Sep 07 2023, Stephen J. Turnbull wrote: > > and then have a "reproduce defects" flag for the reassemble > > functions. > > Yes, that sounds good. Are you ready to do that? And if yes, what > recompense would you like to receive please? I could do it, but I don't really want to. The problem is even if it were done, it's a very fragile feature because it depends on collecting particular behaviors that can change at any time. So I'm unsure (50-50 at best) that it would get into Python, and then I don't know if it would get into Mailman because it's not obvious anybody would want the responsibility of continuous maintenance in order to take account of all the idiosyncrasies of homebrew mail clients of various companies. The current DMARC behavior of changing From and Reply-To is much more robust, and I just don't think there's that big a constituency for making life easy for disruptive actors like Google. Steve

2 years, 1 month

[MM3-users] Congrats on the instructions for installation on ubuntu, what about migration?

by Bill Oliver

So I went ahead and tried to install mailman3 on ubuntu 24.04 using the virtual environment approach. It worked like a charm. There were a very few glitches, all from me not reading the instructions closely (e.g. not replacing MY_SERVER with my server name, Doh). The whole thing, from start to finish was about two hours. I appreciate all y'alls efforts in this. The reason I'm doing this is that I'm having to migrate from a server that's going to be defunct soon. I've been running a mailman3 mailing list on that for a few years. Is there a tutorial/instructions on migrating data from an old system to a new one? It's actually not the end of the world if I don't get all the old emails transferred, but I'd like to get the email addresses of the participants moved over easily... I believe that I set it up in 2020, but did not do any version upgrades since then... Thanks! billo

1 year

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Mark Sapiro

On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: > > But I am trying to delete a list on an urgent basis. Because of which I am > getting the above said errors. I tried to delete > through the interface, through curl command and through "mailman shell" but > nothing led me to a > positive result. Is there any work around to delete the list ? What have you tried in Mailman shell? This should do it. $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> getUtility(IListManager).delete(m) >>> commit() So should just $ mailman remove list.example.com What happens if you do those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: subscribing to any list is not possible

by Stephen J. Turnbull

r.woithe(a)callassoftware.com writes: > to try patch is good idea, but why my files are more different than > the patch file lines? You have a different version from the version the patch was created on. > Should i rather copie the whole file? No. The patches are generally very local changes which are easy to understand. If you copy a whole file, you are likely to run into internal API changes, such as new functions or additional arguments. These changes typically do cross file boundaries. > Example: > in cli_members.py: > def add_members(mlist, infp): but into the patch file it is -> def add_members(mlist, add_infp): > but this line is not a patch line and should be the same or not? That depends on whether the patch lines use "infp". If they do, you almost certainly need to change them too. I didn't make the patch so I can't help you with the details, but I did want to warn against trying to copy files when patches don't match. Steve

4 years, 9 months

[MM3-users] Re: spanish localization

by Stephen J. Turnbull

Victoriano Giralt writes: > I've visited Weblate, all Spanish strings are translated. Spanish > is 100% translated, but, none of them have been "approved", > whatever that is. It seems that a reviewer needs to approve the > translation in order for them to be incorporated or released or > whatever. I was sure I had reviewed everything between November 7th > and the day Abhilash announced the release candidate and asked for > translation review, but nothing has made it to the released > version. > > Maybe there's something in the translation flow that we are doing wrong. > I'm starting to miss the good old days when Mailman 2 translators just > downloaded the .po files and returned them :-) Probably all it needs is for someone other than the submitter to check a box. I doubt there is an assigned reviewer/owner, just any translator registered for that language. That's the way Debian used to work, anyway, and it seems like a good way for open source to work. @Abhilash, you set up Weblate, right? Do you know anything about this?

4 years, 8 months

[MM3-users] Re: Strange password problem

by Mark Sapiro

On 9/22/23 11:39, Eggert Ehmke via Mailman-users wrote: > Am Freitag, 22. September 2023, 19:34:41 CEST schrieb Mark Sapiro: > >> If you set the password with the Django admin changepassword command, >> does it stick? > > Never tried that, how do I do that? In our recommended install, the Django anmin command is `mailman-web` so with your venv active, ``` $ mailman-web changepassword ``` will prompt you for a new password for the current user. If you want to change another user's password, specify that user's username as in ``` $ mailman-web changepassword user ``` >> Can you create another superuser with the Django admin createsuperuser >> command and does that user's password stick? > > Will try that. So I can create another superuser? Does it need a separate > email address? I guess yes ``` $ mailman-web createsuperuser ``` It will prompt for a username, email address and password. The username and email address need to be unique. -- 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] Why is a mailing list not sending the moderator subscribe or post notifications?

by Mark London

Hi - I migrated from mailman 2 to mailman 3. All but one list is working correctly. That list is not sending the moderator any emails. It appears to configured exactly like the other lists. I.e. subscription requests and moderated users posts don't generate any emails to the moderator (me). I tried changing moderator email addresses, and everything else I could think of, but nothing worked. What can I do to debug this problem? This list is much larger than any of my other lists. And has a huge archive. I doubt that is a factor, but I’ll mention it anyway. Also, how do I run the command to remind me of awaiting moderation requests, so that I can run it hourly? In case this can’t be fixed quickly. As an aside, I had some mailman 2 lists that had no moderators. I could swear that for them, that the owners would get moderated requests. Am I hallucinating? I can't check the old server any longer. Thanks. – Mark

2 years, 4 months

[MM3-users] Re: update_index

by Mark Sapiro

On 04/03/2018 09:59 AM, Darren Smith wrote: > OK - next issue...here's the warning that I'm receiving when I run that: > > /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date > received a naive datetime (2018-04-03 07:51:25) while time zone support is > active. > RuntimeWarning) That warning comes from dateutil.parsedate, and I think it's just a warning and shouldn't affect processing. > I'm not sure that anything else occurred. The indexing took 2 seconds, and > there have been tens of thousands of emails imported since the last index. > Thoughts? I'm unsure about what happens when 'runjob update_index' runs after an import. I.e. it adds messages added since the last run, but is this based on when the message was added or on some date in the added message, so if the added messages are old, do they get indexed by 'runjob update_index'. You could easily check by doing some searches that should find them and see if they're found. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: Dealing with recipients' servers spam filtering

by Gilles Filippini

Brian Carpenter a écrit le 12/02/2021 à 15:10 : > On 2/12/21 8:41 AM, Gilles Filippini wrote: >> I run a mailman3 instance with mainly private lists for which I know >> and trust every single member. Some of them have Hotmail email >> addresses, and the messages they send though our lists are rejected as >> being spam by most of the recipients' mail servers, while these are >> legitimate emails. >> >> I'd welcome any pointer to best practices / howtos regarding mailman3 >> / exim4 configuration to mitigate this problem. > > What does the non-delivery long entries say are the reasons for the > rejections? It says: host mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of DATA command) > Do you have a SPF record setup for your list domain? Do you > have DMARC mitigation enabled for your list? I don't have any SPF record setup. DMARC mitigation is configured to 'Replace From: with list address' and 'DMARC mitigate unconditionally' set to 'No'. Thanks, _g.

4 years, 8 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Mark Sapiro

On 6/24/23 9:44 PM, Ken Alker wrote: > How did you join the split thread? using HyperKitty's "Reattach this thread". > The order of the first two emails is flipped; the original email from 6/23 is showing after the second email on 6/24. Do you know how that happened? Do you have a way to fix that too? That was my mistake. There were two choices. I could open the reply thread containing only https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and reattach it to the original message thread now containing several messages or vice versa. I did the latter, i.e. with the result you see with the reply out of sequence at the top. Had I done the former the reply would have been out of sequence at the bottom. This would have been better, but it's now too late to change it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Cannot Create New List

by Stephen J. Turnbull

dap1--- via Mailman-users writes: > That seems to have worked. Thanks. Shouldn't that be documented as > well? It is documented. In the Apache or Ubuntu docs. Your Mailman installation is a *system*. We will help you with *other people's applications* as we can, but it is *not* our responsibility to do so -- it's a freebie you get because we care. We don't care *enough* to create and maintain documentation of third party applications, because there are dozens of OS distributions and "mailing list packages" and several webservers that are used to support Mailman installations. Not to mention that such applications are frequently updated and new tools and conventions (and bugs!) added (that's *why* we recommend a virtual environment, and *why* distros like Ubuntu *enforce* virtual environments for installations from source). We would have no time to work on and support Mailman. If you think it's nevertheless worth doing, feel free to contribute it. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 days, 2 hours

[MM3-users] Re: Can "Pre Verified" set to yes by default?

by Stephen J. Turnbull

Hi Alan, It occurred to me that Django template widgets are very flexible. It may be possible to customize the template to accomplish this task. In that case, the customized template would be kept in a place that doesn't get overwritten in an upgrade, reducing the maintenance cost (unless either Postorius or Django changes the template in a way that seems unlikely to me). I'll try to take a look at that over the holiday break -- that has the advantage that I just document how we did it for you, and tell any future requests to RTFM and DIY. ;-) Alan So writes: > I can say that it is not purely a technical issue in an > organization that whether system admin should maintain a few minor > changes that are not in the main branch. Sure, we understand that. I'd be interested to hear from business users and university users if they would like this particular default to be configurable. It's very easy to do as a one-off, if there is substantial demand we *can* do it, and later say to people who want similar changes that it's on them to demonstrate they have enough demand on their side for another one-off, just as was done for this one. > Due to massive customization made to previous Mailman 2 > installation by some student helpers which made it very difficult > to be upgraded nearly 20 years ago, we tend not to repeat this > pattern when we upgrade to Mailman 3 a few years ago. I agree, you need to be disciplined about what changes you are willing to develop and maintain. This one seemed to me to be over that bar, especially since you can put it in and not suffer too greatly if it gets reverted in a upgrade and the maintainers don't notice. > After all, it is just one of the many suggestions that you > received. I respect the decision of the core team. If the core > team consider that this feature is low priority, it is fine not to > implement it. Unless I see a lot of demand, I think as a one-off I don't want to implement it in list_forms.py, but rather let occasional admins do it on their sites if they want it that bad. But GSoC is coming up again; maybe a student would be willing to take on a generic "pwn all the defaults" project next summer. Steve

2 years, 10 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Abhilash Raj

Do you have something like this[1] in your settings.py file? [1]: https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… `EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'` `This is a dummy email backend which will basically only print the email to stdout, which seems to happen in your uwsgi-error.log. If you do, please comment it out and see if that solves your issue.` `Abhilash` On Sat, Mar 28, 2020, at 5:38 PM, Ralph Seichter wrote: > * Mark Sapiro: > > > What is the complete log message from uwsgi-error.log? > > I'll attach a typical log file to this message. It shows startup > messages followed by a recorded confirmation email. User name and > domain are obfuscated, but other than that the log is unchanged. > > -Ralph > > > _______________________________________________ > 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/ > > > *Attachments:* > * uwsgi-error.log -- thanks, Abhilash Raj (maxking)

5 years, 7 months

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

by Mark Sapiro

On 7/19/23 05:31, itservice--- via Mailman-users wrote: > How can I configure Mailman3 so that Mails from the list will not be blocked by gmx.net > I tried to send with the same user (mailman.cf) at my mail server, which will not be blocked by gmx. > unfortunately, I get no bounce back message. They do just not appear in the mail folder of gmx. Unfortunately, there are some ESPs that will silently discard mail without giving any clue as to the reason. I think this is wrong, but there's nothing we can do about it. > At web.de they go to the SPAM folder. Is your mail server properly configured with a fixed IP and full circle DNS? Is it on any block lists (check at http://mxtoolbox.com/blacklists.aspx)? Are you DKIM signing your outgoing mail? Are you applying DMARC mitigations to your list mail? All these things are important. -- 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] Database running VERY hot

by Darren Smith

Hello all, We had an old installation of Mailman 2.1 across three servers with over 32,000 mailing lists on them. Due to circumstances beyond my control, we had to shut them down and quickly set up Mailman 3 on a new server. We have Mailman3 set up on a single server this time, as we were having problems with a 3-server setup and Hyperkitty and archives. Long story short, it is up and running, and our users are starting to come back. However, we do not have very many users hitting Postorius and Hyperkitty yet, and we are seeing a distressing number of 504 gateway timeouts. We noticed that there is a significant number of queries to the API whenever hitting Postorius's front page to load the mailing lists, and then on every load. It looks as if it makes a single call to the API to get information about a single list, and does this 10 times - once for each list - to render the page. This gets much worse when users set the view to 200 per page, as they are inclined to do with 32,000 mailing lists... What we've done, actually, is to override the front page and point the users to a different set of static pages where we have all of our lists categorized and searchable, and when they find the list they are looking for, we have a link back to postorius. It has taken a lot of the stress off of the server. 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. However, one of the threads is taking up about 85% of the load, another thread about 14%, and little dribbles here and there from the rest of the threads. Here are the questions: 1) Has anyone run into problems like these? I would think that maybe this is an issue having so many mailing lists, but honestly there aren't that many people using the system yet. It is going to ramp up as the users realize that we are live again, but we aren't getting that much traffic. 2) Is there any configuration that I can set, especially with regards to the database, so that it can be used more efficiently and not throttle through one or two threads? Please let me know what further information I can provide. Thanks in advance for any help or advice! Silas

7 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I screwed the mailman install ..... I reinstalled mailman core. How do I do a Python2 virtualenv? Thanks El vie., 21 jul. 2017 a las 15:03, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:44 PM, Rafael Mora wrote: > > I did this: > > > > (env) [mailman@localhost mailman-suite_project]$ pip install Django > > Requirement already satisfied: Django in > > /var/lib/mailman/env/lib/python3.6/site-packages > > Requirement already satisfied: pytz in > > /var/lib/mailman/env/lib/python3.6/site-packages (from Django) > > > > > > Does Django is already installed?? with python3.6 ??? > > > Your 'env' vitrualenv is a Python 3 virtualenv. You need this for > Mailman core, but Django and mailman-suite are Python 2. They need to be > installed and run in a Python 2 virtualenv. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Re: Selective mailing

by Stephen J. Turnbull

chucka(a)blackforest-co.com writes: > I like the controls that MM uses. What I have and need: a member > database [name, address, email, date dues paid, etc]. So I can do > this 2 ways: > 1) select name, email from members where xyz > file. Login to MM > empty member list - which is kind of painful then load file and > send the email. Then repeat for NOT xyz or This is an interesting idea, although it's more CRM than traditional MLM (and we have historically encouraged people to use CRM applications for CRM). We are currently accepting applications for GSoC interns. If you could provide a little bit more explicit requirements, perhaps it would make a good GSoC project. I'm not sure this is as easy as Abhilash's "try the API", so if we could get a student to flesh it out it make be useful for a lot of admins who need more realtime list administration flexibility -- I can think of applications for myself -- and don't want to go full-on CRM or just would rather do it with Mailman. Steve

6 years, 8 months

[MM3-users] Re: Finding a user to delete them

by Brian Carpenter

On 3/14/20 5:03 AM, Stephen J. Turnbull wrote: > The bundled administrative interface*is* Postorius. The Mailman > shell is basically a quick hack (sorry Abhilash; if you want to call > it a masterwork and say the speed of development is testimony to your > skills, I won't deny it;-) to give more convenient access to > internals to experienced Mailman hackers. More administrative > features is something we plan to work on, but the Mailman project will > focus on Postorius for the forseeable future. I do think List Admins would want an interface to help "manage" a user account on behalf of a user then what is currently available in Postorius. I see this come up with my Mailman 2 clients frequently. For instance, a mm2 list member asked their list admin to subscribe them to a list topic to limit the amount of messages they receive. The list admin was new and open up a ticket to find out how they do that in which I replied showing them how they as a list admin, can go in and change options on behalf of a list member. I don't see this functionality built into Mailman 3 nowhere near the extent that Mailman 2 has. Last night a Mailman 3 client wanted to know how they can add a real name to a list member. I said you can't, not as list admin. I directed them to instead of unsubscribe the member and mass subscribe them so they can include a real name along with the email address of the list member. > For alternatives to Postorius and the Mailman shell, Brian Carpenter > (follow Allan's subthread) is working on a new management UI (using > PHP), and I believe there's a working node.js API "out there > somewhere". Please be very considerate of Brian's time; he and EMWD > constitute a bulwark of the Mailman ecosystem and will be even busier > with the UI project. But do pass on your suggestions to him as well > as to us, he's indicated he's open to that. There were some very good suggestions that were brought out in this thread and I had already passed them on to my developer. My approach with Affinity is definite leaning very heavy on the needs of list admins atm. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 7 months

[MM3-users] Re: New messages not being archived

by Mark Sapiro

On 7/22/21 11:41 AM, Sarah H wrote: > here is the full error message. Nginx proxies on http. > > https://pastebin.com/raw/TUf5dYi8 Thanks for the log. It is basically just confirming what we see with this. > the curl commands above result in. > ... > (venv) [mailman@sysname sarah]$ curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive > curl: (52) Empty reply from server I am at a loss to understand why HyperKitty isn't responding. Are you able to access HyperKitty normally from a web browser? Do you get a response from ``` curl http://127.0.0.1:8000/hyperkitty/ ``` If so, what? What you should get from ``` curl -X POST http://127.0.0.1:8000/hyperkitty/api/mailman/archive ``` is ``` <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> ``` You should get the same response as a web page if you go to https://example.com/hyperkitty/api/mailman/urls. Do you? -- 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: Migration failure (2.1.29 to 3.3.8 on Debian testing)

by Mark Sapiro

On 6/7/23 11:58, {16/7} wrote: > > I have both the mailman and mailman3-full packages installed on my machine and I'm following the migration guide located here: https://docs.mailman3.org/en/latest/migration.html Which is the source of at least one of your issues. The Debian packages are behind and are missing multiple bug fixes and enhancements. > Running the command { mailman import21 mylist(a)mysite.com /var/lib/mailman/lists/mylist/config.pck } completes once I create the list but states that it cannot convert the msg_footer and digest_footer mailing list attributes. (I might also point out that the { mailman create mylist(a)mysite.com } command isn't actually documented on that webpage.) import21 tries to make Mailman 3 compatible versions of your Mailman 2.1 msg_footer and digest_footer. It will put these in Mailman's var/templates/lists/<list-id>/<lc>/ directory as list:member:regular:footer.txt and list:member:digest:footer.txt respectively. You need to examine those files as they probably contain Mailman 2.1 style replacements that haven't been converted. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for the Mailman 3 replacements which are encoded as dollar strings, e.g. $listname gets replaced with the list's posting address. > I can't seem to find the manage.py script in my $PATH and after searching, I find it as part of the mailman3-web package. As you report in a followup, in the Debian package it's called mailman-web > Next, I changed the file's group back to list and decided to try running the manage.py script as the www-data user. This results in "/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured." and "System check identified some issues:" followed by a list of "Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'" warnings for a number of Django tables. Recent mailman installed following https://docs.mailman3.org/en/latest/install/virtualenv.html will include ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in Django's settings which will avoid that warning with Django>=3.2 > > My questions are: > > 1. How do I undo any damage (if any) my efforts may have caused? You probably didn't do any damage as the commands failed before doing anything. > 2. What's the correct way to run manage.py? I see from your follow up that you figured this out. -- 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: Disabling max_message_size and send_welcome/goodbye_msg globally or by API

by Mark Sapiro

On 10/10/2017 12:04 PM, Peter Mueller wrote: > > is it possible to turn off max_message_size and send_welcome_msg / > send_goodbye_msg globally? Not for existing lists, but for new lists you can create a style with these settings and make it the default style. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> for how you might do that. > If there are no global options, how can I turn off these feature using the > REST API? > In python you can do it with >>> mlist.max_message_size = 0. > If I send a PATCH request to lists/some@list/config with body > max_message_size=0, I get "Unknown attribute". Same for send_welcome_msg > and send_goodbye_msg. max_message_size and send_goodbye_msg are not currently exposed in REST. See the definition of ATTRIBUTES in mailman/rest/listconf.py for what is. You should be able to PATCH send_welcome_msg via REST. I don't know why that didn't work for you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió: > What translations are those? Please give specific examples. What I am > saying is Mailman core 3.3.3 is currently up to date with weblate. There > are no Spanish translations for core done after 7 November in weblate > and weblate shows 100% completion for Spanish for Mailman core. Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date... All strings related to Mailman (core, django_mailman3, postorius and hyperkitty) are translated into Spanish 100%, but the interfaces, after updating to the latest releases, are still in Englanish (more English than Spanish). This is not a fight, we want to help, but do not know how. Thanks! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 8 months

[MM3-users] Re: add / remove / set moderation bit of non-members via mailman shell

by Mark Sapiro

On 2/7/24 02:37, Zaheer Abbas wrote: > > I do the above via postorius because I couldn't find a way to do this via > mailman shell. Something like ``` mark@msapiro:~$ mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> NEW_NONMEMBERS = [('First User', 'user1(a)example.com'), ... ('Second User', 'user2(a)example.com'), ... ('Third User', 'user3(a)example.com'), ... ] >>> from mailman.app.membership import add_member >>> from mailman.interfaces.subscriptions import RequestRecord >>> for display_name, email in NEW_NONMEMBERS: ... record = RequestRecord(email, ... display_name=display_name, ... delivery_mode=None, ... ) ... member = add_member(m, record, role=MemberRole.nonmember) ... member.moderation_action = Action.accept ... >>> commit() >>> ``` -- 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: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

On 5/1/20 6:54 AM, Mohsen Masoudfar wrote: > Thank you Mark, this is really very helpful. I am going to work on the details. It would be breat, if there were a way to set some of this options as default, like DMARC mitigation is default to no, I changed it to unconditionally and replace From to with list address and got good results, but the default is no. How may I changed the default, do that the list owner/creator does not need to update these fields. There are two ways to do this. Both require some code modification. The simplest is just to change the lines at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py…> to: mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from mlist.dmarc_mitigate_unconditionally = True The other way is to create a new list style that has these settings and chose it when creating a list. See <https://mailman.readthedocs.io/en/latest/src/mailman/styles/docs/styles.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

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

by Odhiambo Washington

On Wed, Jan 3, 2024 at 9:20 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > This is interesting. However, you meant the default example.com, > > right? > > Whatever it is is fine for me. I was going from memory. > > > And that link also let's me DELETE the site :-) > > Don't do that! What happens afterward is not hilarious, it's a > self-DOS unless you know exactly what you're doing. > I thought about that, because I have seen what those who deleted example.com went through. > Among other things, the next site you create is still #2. It's not > really any cleaner just because you got rid of the example site. > It's good that one can rename the example.com. Perhaps that can be documented somewhere as a footnote. -- 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, 10 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Mon, Aug 5, 2024 at 8:19 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/5/24 07:04, Odhiambo Washington via Mailman-users wrote: > > I am having an ugly-looking https://mm3-lists.kictanet.or.ke/archives/ > page > > because of cached content: > > > > ``` > > 2024/08/05 17:00:31 [error] 694#694: *9562 open() > > "/opt/mailman/mm/static/CACHE/css/output.6dab123e4897.css" failed (2: No > > such file or directory), client: 172.70.111.39, server: > > mm3-lists.kictanet.or.ke, request: "GET > > /static/CACHE/css/output.6dab123e4897.css HTTP/2.0", host: " > > mm3-lists.kictanet.or.ke", referrer: " > > https://mm3-lists.kictanet.or.ke/archives/" > > 2024/08/05 17:00:31 [error] 694#694: *9564 open() > ... > > That IP address appearing there is not my actual IP, but Cloudflare's, > > which is acting as proxy for the site. > > > I **think** you may have something like > > location /static/ { > alias /opt/mailman/web/static/; > } > > in nginx on cloudflare, but since cloudflare is not the Mailman server, > /opt/mailman/web/static/ doesn't exist there. > Actually, what I mean is that CF is proxying requests to the host named m3-lists.kictanet.or.ke. I do not have any configuration other than DNS proxying at CF. I can't be sure on how to configure this without knowing the details of > how requests get from cloudflare to mm3-lists.kictanet.or.ke and from > there to the wsgi server. > When you ping m3-lists.kictanet.or.ke, the IP you get is CFs, not the actual IP of the host. So when you talk to m3-lists.kictanet.or.ke via a browser, it's CF IP who you talk to and it in turn talks to the host directly. So the IP address you see in the logs is CF's IP address, not yours, not mine and CF are doing some caching. That's why they are requesting for expired files. > However, if cloudflare just proxies the request for /static/ to the > Mailman server and nginx on that server has the above `location` > directive, that may do it. > I suppose it's possible to configure Nginx to NOT ALLOW caching of content from the /static/ location. Being new to Nginx, time to say hi to uncle G again. -- 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, 2 months

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

by Ruth Ivimey-Cook

On 24/06/2020 00:20, Mark Sapiro wrote: > Go to your Django admin web UI and look at your Django Mailman 3 Mail > domains. This will be at a URL like > https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ > > Do you see this domain there? If so, delete it. I hadn't logged in as admin before, so having done so I can now confirm that having done so this screen shows "0 mail domains" Because I could, I then visited "VIEW SITE" and see a mailing lists page, which is I think the same one I have been trying to visit, except of course now I am logged in. I do now see the correct, and only, mailing list configured on the core server. Returning to the previous "maildomain" page, that now shows the expected mailing list as well. Other admin pages seem to be working fine as well. I think, possibly, that it is now installed and working. ... But I don't know why. Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 4 months

[MM3-users] Re: Hyperkitty Text/Markdown/HTML

by Sam Darwin

> I don't understand what you envision such a rendering to do. To achieve a level of rendering emails (and web) similar to gitlab or github. That includes bold, italics, code blocks, and possibly more. In both Hyperkitty and email clients. > It has nothing at all to do with messages delivered to list members. that's why I mentioned "would affect more than just Hyperkitty. (i.e. mailman-core)." > Archived messages which contain text/html parts currently render those parts as attachments that can be downloaded. Are you suggesting that "HTML" rendering would render those inline or something else? Yes "inline", as part of the main message display, and not as an attachment. No attachment would appear. > HyperKitty's rendering mode has nothing to do with that. Hyperkitty is one of the two main components. It's the web UI part. The other being the outgoing emails. > If you're suggesting a text/html part outside of a multipart/alternative part I was probably imagining just "multipart/alternative", containing alternatives. Is the "outside" method also a possibility? I did not intend that. > For example if in Yahoo mail one composes in "rich text" and drags and drops or copy/pastes or in some ways even types a link, the generated text/plain alternative doesn't contain the url in any form. Our lists are set to "Convert html to plaintext". I just tested from Yahoo email, with rich text, and hyperlinks. Everything was fine. The problem didn't exhibit itself. I also "copied" a link from a website, and pasted it into the email, but it was ok. Perhaps other clients "aol.com, att.net, netscape.net, pacbell.net, prodigy.net, rocketmail.com, sbcglobal.net and ymail.com" have a problem? But today in mail.yahoo.com , no... If most mail clients include Yahoo and Gmail send both HTML and plain-text versions in a multipart message, there would theoretically be two choices for mm3 with "Convert html to plaintext". 1. Mail out the included plain-text copy from the multipart email. Or, 2. Parse the HTML part of the message and "convert html to plaintext". which of those is occurring? To summarize again, the goal is to show in Hyperkitty and in email clients a format (based on HTML) that includes bold, italics, bullet items, and code blocks. The same way github or gitlab messages appear, with more formatting options. Since HTML is a standard format, and many mail clients have built-in support for both generating and displaying it, HTML is nature choice for a protocol to use, it's already included everywhere.

1 month, 3 weeks

[MM3-users] Re: Mailmanweb RAM Usage

by Odhiambo Washington

On Sat, Oct 11, 2025 at 5:10 PM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Odhiambo Washington via Mailman-users writes: > > > Using the uwsgi.ini from the virtualenv method documentation, > > mailmanweb is constantly using 2GB RAM on my server. > > Do you mean only HyperKitty + Postorius? That seems like a lot. My > experience is that even on an insanely heavily loaded server (20k+ > lists) the whole suite uses about 2.0G. Since on that server, Mailman > core was forking 22 processes at ~83MB each (very little shared, not > sure the technical reason for that, maybe the Python heap just can't > be shared?), core was taking up about 1.8G. HyperKitty and Postorius > took a little more (I don't recall exactly, maybe 250MB?) > Yes, just Hyperkitty+Postorius: Please see https://imgur.com/a/LPAY69N It represents what I see daily when I run btop.It's always around 2GB, but rarely do I see above. I only have 1 major active mailing list on this server. There are other inactive ones. The main ML has been active since 2005. I migrated it to MM3 from MM2.1.39. > My more standard setup (that one had like 2 IN queue slices and 8 OUT > queue slices) I ran Mailman suite + PostgreSQL (dedicated to Mailman) > + Postfix + nginx (also mostly dedicated to Mailman) + Cyrus IMAPd in > a nominal 2GB Digital Ocean droplet. It didn't run "comfortably", > adding any serious load that chewed up 100s of MB RAM would get things > OOM-killed, but 2GB total (including kernel and all) was barely enough > for that system in normal situations. > > > My database (MariaDB) size is 2GB. > > Do you mean in memory or on disk? Either way that should have ~0 > effect on the size of the Mailman core and web processes. > My MM3 database size on disk. > > Is this expected? > > Depends on if you mean exactly what you said ("mailmanweb"). If so, > no, I would expect mailmanweb (only) to run in 500MB easily and > probably be OK in 250MB. If you mean "when I start Mailman and > mailmanweb, memory usage jumps by about 2GB", then yes, that's what > I'd expect. > In my case, the ~2GB RAM consumption by the uwsgi process is a constant. -- 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]

3 weeks, 3 days

[MM3-users] update_index

by Darren Smith

Hello, If I'm reading the docs correctly, when we run manage.py update_index, it should be an incremental index of new emails that have been added since the last time update_index was run - can anyone confirm that this is the expected behavior? Or is there another command line option that I am missing? Right now we are indexing EVERYTHING every time that this is run. Probably this wouldn't be much of a problem except that we are importing all of our old archives (they go back to 1998 and comprise over 40.5 million emails) into the new system. As of now we have around 700,000 emails imported into hyperkitty, and since it is indexing everything it is taking around 1 hour and 10 minutes. Obviously we can't run that once a minute. Right now we're doing once a day, meaning that new emails won't be indexed until the next day. Fast forward to when we have all 40 million imported...the full index process will take (we estimate) around 4 days or so. So...can anyone help with how to get the update_index to do only emails added since the last time the update_index was run? Thanks! Darren

7 years, 7 months

[MM3-users] Re: timezone in hyperkitty

by matthew_saunders＠harvard.edu

Mark Sapiro wrote: > On 6/29/20 12:18 PM, Marco Marinello wrote: > > I'm expirencing the same behaviour in Postorius. Is > > it possible to set a default timezone for new users? Already set it in settings_local.py > > but not having any effect, still seeing "Africa/Abidajin" in new users. > > Do you mean the users time zone as displayed in the user's profile? This > is a Django setting and the default should come from the TIME_ZONE > setting in settings_local.py, at least if USE_TZ is set True I'm seeing the same behavior on my development site, and I was even able to reproduce this when I created my account on this very site moments ago using OAuth. If you check the django_mailman3_profile table in the DB, I expect you'll see that my timezone record is blank (since I haven't touched it from the Accounts page). FWIW, it's empty... not NULL, since there's a not-null constraint on this field. Is it possible to have this set to a default (non-empty) value somehow? TIME_ZONE & USE_TZ isn't doing it.

5 years, 3 months

[MM3-users] Re: Converting non-members to members

by Abhilash Raj

On Tue, Dec 18, 2018, at 2:55 AM, Alan So wrote: > Postorius is not currently exposing non-members management. Our Mailman > 2 users are currently using accept_these_nonmembers, > hold_these_nonmembers and reject_these_nonmembers. We know that > mailman import21 will change these to nonmembers entries in Mailman 3. > Since list owners will still want to manage them, we tend to move all > of them to members and turn off delivery status for them. I have been (slowly) working on exposing non-member management in Postorius (Mailman's web ui). I am hoping to complete it soon, but there is not clear ETA for it yet. I hope that it will be done soon. > However, we met some difficulties when we try to develop using mailman > client. Can you also please share the snippet of code you used for the these operations below so that we can help you fix them? > 1) If those non-members addresses already exist as members, we will > encounter error when we subscribe for them: urllib.error.HTTPError: > HTTP Error 409: b'Member already subscribed' Do you expect something else here? Any response with non-2XX status code is raised as HTTP Error in MailmanClient. > 2) We cannot change the moderation_action: urllib.error.HTTPError: HTTP > Error 400: b'Cannot convert parameters: moderation_action' I'd need to see the code fr this one, not sure what value did you pass here. You should be able to do: >>> member1.moderation_action = 'hold' >>> member1.save() Allowed values should be: - hold - reject - discard - accept - defer = 4 > 3) We cannot change the preference: urllib.error.HTTPError: HTTP Error > 400: b'Cannot convert parameters: delivery_status' This is again depends on what you are passing as value for the parameter. Allowed values are: - enabled - by_user (disabled by user) - by_bounces (disabled due to bounces) - by_moderator (disabled due to moderator) - unknown (disabled for unknown reason > > Are there any better ways to enable the list owners to manage those > previously configured nonmembers' addresses through the web? I am working on adding the support in the web ui, so yes, there will be better ways to manage those in future. > Otherwise, we probably need to have some manual effort to overcome the > above three issues. We know that we can always do the above manually > but we got a lot of lists to migrate to 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 1/28/21 5:33 AM, David Partain via Mailman-users wrote: > I wrote: >> I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: >> >> DATABASES = { >> 'default': { >> 'ENGINE': 'django.db.backends.mysql', >> 'NAME': 'mailman3web', >> 'USER': 'mailman3web', >> 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', >> 'HOST': 'localhost', >> 'PORT': '', >> 'OPTIONS': { >> 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", >> 'charset': 'utf8mb4', >> }, >> } >> } >> >> and restarted stuff, but I cannot tell that it has changed anything. > > You responded: >> That should do it. I think the original message should have been saved >> as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. > > That directory has all of the messages sent to that list: > > # ls /var/lib/mailman3/archives/hyperkitty/spool/ > 1611827925.8030825+925c996b9b6020ee18e9a689ce23384855159f77.pck 1611827926.1923075+e728f3c29c1fe6eeeca641314cdba7007cb6e132.pck > 1611827925.8917305+d16b7004bdbbef98ce40fb8ee70e492715d1607d.pck 1611827926.2623458+1aac13b50d8e7f32eb14d13e6559656aa8f3bd10.pck > 1611827925.9594557+7ad2a910b5ee9142c88f0bf26c60c6df960d4262.pck 1611827926.3488555+04a540651c5f829751518433e1c54168ab63a38b.pck > 1611827926.0404096+a5e745f51a9f7d541aeb770a89604be17019f3c5.pck 1611827926.4206145+de861eec6404d0c8f9f8bdb180e29bff2de7c52b.pck > 1611827926.1167526+0aa63639a4ec102bf63522827637e75e6a2b092a.pck This is what's expected since the underlying issue isn't yet fixed. > Yes, I'm still seeing the errors. When I send mail to a list with a cute emoji, I see the following in /var/log/mailman3/web/mailman-web.log: > > ERROR 2021-01-28 10:58:45,708 16923 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive > (bunch of python errors omitted) > DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column 'content' at row 1") OK. The issue is with your database it doesn't like '\xF0\x9F\x98\x8A' which is a 4-byte utf-8 encoding for a smiley face emoji. The issue is with MySQL and MariaDB which do not accept 4-byte utf-8 encodings by default. The settings you show above should be sufficient to allow 4-byte utf-8 encodings. I'm not that familiar with how the Debian/Ubuntu package sets things up. Are you sure that /etc/mailman3/mailman-web.py is the settings file used by Django, and if so does it have at the end something like ``` try: from settings_local import * except ImportError: pass ``` and if so is there something there that overrides the DATABASES setting? If all that is OK, you may need to do something like ``` ALTER DATABASE mailman3web CHARACTER SET utf8mb4; ALTER TABLE hyperkitty_email CHARACTER SET utf8mb4; ``` on the database itself. -- 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: Problems with mailman core translation and other details

by Mark Sapiro

On 2/6/24 2:41 PM, celi--- via Mailman-users wrote: > It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. > > #: templates/postorius/lists/summary.html:88 > #, python-format > msgid "" > "\n" > " To subscribe you can send an email with 'subscribe' in the" > "subject to\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " or use the form below:\n" > "" > msgstr "" > "\n" > " Para se inscrever você pode enviar um e-mail com o assunto" > "'subscribe' para\n" > " <a href=\"mailto:%(address)s?subject=Subscribe\">" > "%(address)s</a>\n" > " ou use o formulário abaixo:\n" > > What am I doing wrong? Or what can I do to make things suitable? Is the rest of that page translated appropriately? -- 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] Disabling Gravatar

by Marvin Gülker

Hi everyone, I want to make you aware of a potential privacy problem in Mailman's Hyperkitty. Under the upcoming EU General Data Protection Regulation (GDPR)[1], which will be in force as of 2018-05-25, it is illegal to transmit data to third parties without a right to do so. Without going into the details, the inclusion of third party services into one's website is usually deemed such a transmission, and unless one has explicit consent of the user (e.g., by an optional (!), unticked ticking box) this is normally illegal (if one targets EU users). The GDPR does not affect private and family use (Art. 2(2)(c) GDPR), but the exact reach of that clause is yet to be determined; it certainly does not exclude company use of Mailman. I've found it's possible to disable the social login providers quite easily (we had this discussion here on the mailinglist recently), but I don't see an option to disable Gravatar. If there is one, please enlighten me, but anyway I want to propose this as a feature request against Hyperkitty. A GDPR-compliant implementation of Gravatar in Mailman would look like this: * In order to not transmit website visitor's data (IP address, browser info, etc) to Gravatar, Hyperkitty has to request the avatar image itself and not leave that to the user's browsers to do. In other words, the HTTP GET request needs to come from the server running Hyperkitty and the user's browser then just requests the avatar from the Hyperkitty server. Most likely easiest way to do this is to pre-download the avatar when an email is archived. * In order to not transmit the subscribers' data (email address, allows Gravatar to track the subscriber) to Gravatar illegally, the retrieval of the avatar image from Gravatar has to be disabled by default. Instead, an option needs to be added to the subscriber's control panel which he has to actively enable in order to have his Gravatar downloaded and thus used (privacy-by-default rule). I'm not saying Gravatar tracks people and sells the information gathered, though I have doubts on how Automattic makes money with the service. I'm just outlining the legal duties under the upcoming GDPR for service owners, which are independant of how Automattic processes the data in this specific case. Please don't dismiss this as some side feature not needed. The fines that can be imposed on service owners due to violation of the GDPR are very high (up to 20,000,000 € [that's 20 million euros, really]). Marvin [1]: http://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1510481733260&uri=CELEX:… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 11 months

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Mark Sapiro

On 1/14/23 11:44, Odhiambo Washington wrote: > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Nothing in those releases per se would affect this. This is Django and >> django-allauth. Perhaps when you updated the Mailman packages, you also >> updated these dependencies. >> > > Which dependencies would those be? Django and django-allauth. > When I upgraded, the command I ran was: > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > mailman-hyperkitty django-mailman3 Do you mean --force-reinstall? pip has no --force option. I *think* --force-reinstall will upgrade dependencies. Depending on your pip version, --upgrade alone may or may not upgrade dependences. Older versions of pip will, but newer versions, at least without --force-upgrade require --upgrade-strategy eager to update dependencies. > And how do I find out what is suppressing the logging for the social > accounts? That's a django-allauth question. -- 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: default processing

by Stephen J. Turnbull

Gerald Vogt writes: > People tend to choose "Accept immediately (bypass other rules)". How about "Accept immediately (no spam check)"? > I do wonder somehow if there is really a use case where you would > actually need "Accept immediately". "Need", probably not. However, for people who integrate things like Spamassassin into Mailman rather than the MTA, it's often much easier (and possibly less risky, depending on the importance of that sender) to trust the sender ID rather than adjust the filter rules. (This is a good reason to integrate Spamassassin in the MTA, but providers....) We could also reorder the list and put "default processing" at the top. And/or add more explanatory text. > it's not totally clear to me what the default processing rules do > exactly... Here's the complete list: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs… Which rules are checked for a given post depend on the outcome of previous checks as well as the list configuration. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 3 weeks

[MM3-users] Re: templates

by Mark Sapiro

On 5/4/23 11:15, Christian via Mailman-users wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. See the original thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (which you hijacked about 4 messages in) and particularly the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Without further information, I can't say more than that. -- 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: How to create (or change) certain member preferences (in a list, or for all lists) by command line "mailman create [OPTIONS] LISTNAME" ? (Suggestion: modification of this command)

by Mark Sapiro

On 8/4/25 12:09, Wikinaut wrote: > Some member preferences - such as hide_address - cannot be set with the [OPTIONS] in the command line. > > I suggest to modify the code so that all member preferences can be set via the command line. > What do you think? > > This is how I currently patch (some) member preferences (hide_address is a variable here) in a python script, but this takes a lot of time, depending on the number of users.... YMMV. If you do this via a `mailman shell` script rather than the REST API, it should be significantly faster as it will avoid the per-user network connections. Note that changing various list options such as preferred_language does not affect existing members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] How to limit numbers of outgoing emails per connection

by Alain D D Williams

Exim tells me "no immediate delivery: more than 30 messages received in one connection" The emails then sit in the exim queue until a queue runner kicks in - which happens once every 30 minutes. The result is considerable delays which makes list email conversations bouncy. Question: how do I tell MM3 to send no more than 30 emails in one connection to exim (via SMTP to localhost port 25) ? If that is not possible, how do I find the number that MM3 batches outgoing emails so that I can configure exim to match (as I did with MM2) ? I see documentation pages like the following. They are useless to me, incomprehensible without a lot of learning. I program in several languages but only a little Python. What I am looking for is a setting in a config file. https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do… -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

8 months, 3 weeks

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

by mark＠suburbia.org.au

Once again, thanks for taking time to reply. Mark Sapiro wrote: > On 11/18/24 04:12, mark(a)suburbia.org.au wrote: > This should not happen. In the message as delivered to the list what do > you see in the X-Mailman-Rule-Misses: header and the > X-Mailman-Rule-Hits: header if any? ``` X-Mailman-Version: 3.3.8 X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address X-Mailman-Rule-Hits: member-moderation ``` > What if anything is in the lists Accept these non-members setting? Default action to take when a member posts to the list: Hold for moderation Default action to take when a non-member posts to the list: Hold for moderation Emergency Moderation: No Accept these non-members: (none listed) Hold these non-members: (none listed) If you would like me to enable debugging and do another test, I'm happy to. I will admit given the odd behaviour that there's a (small, unexpected) chance that there were settings changed or made during the process by another moderator, but that is not the belief at the moment. cheers, Mark

11 months, 2 weeks

[MM3-users] Re: clearing pending db

by Mark Sapiro

On 8/8/25 09:59, Morris Jones wrote: > > But pendingdb.evict() doesn't seem to clear the list. For example, on > one of my lists: > > >>> from mailman.interfaces.pending import IPendings > >>> > >>> from zope.component import getUtility > >>> > >>> pendingdb = getUtility(IPendings) > >>> pendingdb.count() > 5040 > >>> pendingdb.evict() > >>> pendingdb.count() > 5040 > >>> pendingdb.evict() only deletes expired pendings, but by default subscriptions pending confirmation expire after 3 days, but this is set by pending_request_life in the [mailman] section of mailman.cfg. Have you set that to a long time? On the other hand in Mailman 3.3.2, subscriptions pending approval were pended with a 10 year lifetime. This was changed in 3.3.5 to a new moderator_request_life setting (default 180 days). If you just want to delete all pendings you could do ``` pendingdb = getUtility(IPendings) for pending in pendingdb: pendingdb.confirm(pending[0], expunge=True) # and if doing this in mailman shell commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 3 weeks

[MM3-users] Re: Editing templates from settings

by Abhilash Raj

On Tue, Sep 3, 2019, at 9:18 PM, paul(a)arenson.org wrote: > Hello again. > > Gradually coming along thanks to the help of other members. > > One thing I want to do is edit my headers or footers to have key info > about my site. But it seems even if I skip spaces, when a message is > received the spaces disappear. Likewise, is there any way to add basic > formatting like BOLD? > > For example, if I make a footer like this... > > Skipping a space here > __/__/__/__/__/_/__/__/__/__/ > Our List > _/__/__/__/__/_/__/__/__/__/ > Skipping a space here > > > ...the centering disappears, as do the > skipped spaces, meaning the message after a header or before a footer > looks cluttered, > > Is there a fix? Not yet, there is an open issue about it[1]. [1]: https://gitlab.com/mailman/postorius/issues/301 > > Thank you. > _______________________________________________ > 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, 2 months

[MM3-users] Re: If you delete a list but not the HyperKitty archive

by Mark Sapiro

On 1/4/22 6:45 AM, Philip Colmer wrote: > > So ... should the archive be deleted when the list is deleted and it is a > bug that it isn't? Or is it expected that access to the archive is "frozen" > once a list is deleted? It is often desired to have a public archive available after the corresponding list has been deleted. Even for a private archive, it may be desirable for site admins to have access. Furthermore, a list might not even have a HyperKitty archive in the first place. Thus, what to do about a HyperKitty archive (or prototype archive or ...) when a list is deleted is an administrative decision and is best left up to the site admins to do it or not. As you note with a private archive, former members no longer have access when the list is gone, but unless an attempt throws some uncaught exception, that is not a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

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

by Quanah Gibson-Mount

--On Wednesday, March 3, 2021 8:28 AM +0100 Lars Schimmer <l.schimmer(a)cgv.tugraz.at> wrote: > >>> Distribution packages tend to be useful for really basic things like >>> libraries. For constantly evolving projects where you need to be >>> current, they're more of a detriment. >> >> So much this. > > You do not need a bleeding edge software on production servers. You just > need bug free, whihc is easy done with packages on distributions, if > maintainers do it well enough. If you think the versions of software provided by distributions are bug free, you're living in a very bizarre realm that doesn't mirror reality. I've been running production systems for over 20 years for anything from private educational institutions to large scale multinationals. You don't get reliable production services running the ancient bug-ridden software provided from distributions. Anyhow, that's getting way off topic for this list. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

4 years, 8 months

[MM3-users] Re: SMTPAuthenticationError at /accounts/login/

by Mohsen Masoudfar

Hi Stephen, Thank you for the hint. I was focused too much on the documentation and was looking for the answer in the wrong place. Problem fixed. My problem started with "SMTP authentication not supported" and after fixing that, which was a Postfix parameter, I got this issue and was also looking in Postfix or Django configuration for the answer. This problem is solved and I wished there was a chance to update the documentation, so that these sort of information could be added in the documentation for other people who try to use mailman3. Thanks Mohsen -----Original Message----- From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Thursday, April 9, 2020 4:06 AM To: Mohsen Masoudfar <mmasoudf(a)aaas.org> Cc: mailman-users(a)mailman3.org Subject: [MM3-users] SMTPAuthenticationError at /accounts/login/ [EXTERNAL EMAIL] mmasoudf(a)aaas.org writes: > I have setup the stack according to: > Mailman Suite Documentation. Release 3.3 PDF file. > I configured > EMAIL_HOST_USER and > EMAIL_HOST_PASSWORD > in Django settings.py. I could not find the place that I might > configure it for Postfix I think it helps to start thinking about it from the other end. That is, Postfix is the mail server for all users on a multiuser system. Therefore in "normal" configurations it will use the authentication mechanisms provided by the host operating system.[1] You need to have a user for Mailman in any case, typically called "mailman" or "list".[2] Once you've configured a user for Mailman on the Postfix side, you use that user and authentication data for Mailman core, Postorius, and HyperKitty to send mail via Postfix. > I am running the site on AWS and to be able to use AWS mail-servers > I have to define following parameter for AWS: > smtp_sasl_password_maps which points to a hash for AWS 'ACCESS KEY > ID' and 'SECRET ACCESS KEY' I don't think that has anything to do with the Mailman-to-Postfix side of things; that's for Postfix to send to AWS's mail exchanger (aka MX). Steve Footnotes: [1] It may also be possible to create Postfix-only "virtual" users who have no existence as far as the OS is concerned, but I don't know anything about that. [2] I haven't thought carefully about whether using Mailman's user in Django would be a security risk, but as long as it only has access to Mailman I don't see how it can do more harm than Mailman itself can, and I don't see why it would be more subject to exploitation than Mailman itself is. Anybody with security chops who wants to weigh in, please do.

5 years, 6 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

tlhackque via Mailman-users writes: > Not that I count, but I'm not particularly sympathetic to this > either. In fact, you do count. If we can get a working consensus that Mailman shouldn't try to make up for MUA SNAFUs, no matter how many trillion dollars the manufacturer's stock is worth, life would be easier for us. ;-) > An up-to-date Thunderbird user - the message with the > "mail-with-defect.txt" attachment, as forwarded by [MME-users] (selected > headers below for ID) displays as blank. Interestingly, the Thunderbird > error console has no error message related to this. > > So there's really no point in passing it along, unless "pass these > defects" turns into "repair these defects". That's a Thunderbird problem, though, and nonconforming to the Postel Principle. > Assuming it's an origin issue, this really seems like an issue that can > only be fixed by the sending MUA (Apple). Obviously. > Note that MailMan is encapsulating a multipart/signed message in a > multipart/mixed in order to append it's footer, and reports that it > removed the signature part of the multipart/signed. This makes the > signed message format invalid. So at least, MM3 needs to handle signed > messages better: either include the signature or remove the signature > headers (an unwrapping exercise to convert the message to > unsigned)... For the former, we already try pretty hard to include the signature. At least on this list "Pass types" is multipart message/rfc822 text application/pgp-signature application/x-pkcs7-signature application/pkcs7-signature although I see Mark just added that last one or two. Of course, "x-" tokens are deprecated except for private use, maybe we should be unsympathetic to x-pkcs7-signature, too? :-) > Note that this can be recursive where a signed message contains a > message/rfc822 part that contains a signed message, that.... > > I'm not sure it makes sense to encrypt messages to a mailing list, Of course it does. Maybe not to a public discussion list, but for a closed group's distribution list, I'm sure there are applications. > but the format issue is the same. OK. > In either case, corrupting messages is a MM issue. I disagree, in part. Although you do address this, let me use the example of this case where the signed body is multipart/alternative. I think it's perfectly reasonable for a list to configure to remove the text/html part, which will break the signature. Then there are three possible ways to go: (1a) leave the signature in place, broken, thus informing recipients it was supposed to be signed and leaving it to them to follow up, (1b) to change the multipart/signed content-type to multipart/mixed and replace the signature with a "removed" notice, and (2) to remove the signature and multipart structure, leaving recipients unaware that the message was intended to be signed. Each of those is problematic, each in its own way. Supporting all of them and the list configuration infrastructure to allow admins to choose would be an unwarranted burden on us, IMO. > multipart/signed should imply accepting the signature part (in this > case, application/x-pkcs7-signature). If signatures aren't allowed by > policy, then multipart/signed should be bounced. I find it hard to believe that anyone would want a "deny signed bodies" policy, but it's easily implemented. Put multipart/signed in "Filter types". A configuration explicitly banning signature algorithms but not multipart/signed is a user error in that case. I guess I can imagine wanting to ban certain types (eg, known exploitable algorithms), and if one has such a use case and wants the message rejected rather than simply stripping the signature as unusable, "patches welcome" -- I can't see that level of care as worth our time, though. > It's also the case that if a signed message contains an banned part > type, simply removing it will break the signature. So in that > case, the choice would either be to bounce the message, convert the > message to unsigned, or accept the banned part. (The latter might > be acceptable in some environments, but has obvious risks.) > > Clearly, the current behavior is problematic. That's not obvious, except as it's cosmetic. > (I don't think it's reasonable to expect MM admins to "know" to > configure their lists to pass signature parts if accepting signed - > after all, this list is run by experts :-) I agree with that. It's not clear that we should do something about it, though. There are two possibilities: (1) the list admin doesn't care about signatures, and simply wanted to allow multimedia mail, and (2) the list admin wants to admit signatures on purpose, for some purpose. In case (1), this is mostly a cosmetic problem, and possibly involves minor annoyance. The signature validation will fail and maybe there's a text notice about removed parts, that's cosmetic. A subscriber who cares about the signature might have to contact the author for validation, that's the annoyance. In case (2), we do not know what the requirements are. We should refuse to guess and we can assume that list admin knows [more about what] she's doing [than we possibly can] and leave it up to her. If you think that we can know a lot about a very common use case in principle, I'd like to hear about it, but for now that's my stance, Steve

3 years, 6 months

[MM3-users] Lessons learned and a couple little gotcha for newbies

by William Oliver

I just finished, with great help from Mark Sapiro on the list, a new installation of mailman3. I used the instructions at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/insta… and https://docs.mailman3.org/en/latest/install/virtualenv.html There were a couple of gotchas that I didn't see well documented. 1) I got the error django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' from 'mistune.scanner' (/opt/mailman/venv/lib/python3.9/site- packages/mistune/scanner.py) when I ran 'mailman-web migrate' The fix was trivial: I just added the lines: from mistune.util import escape_html from mistune.util import escape_url to /opt/mailman/venv/lib/python3.9/site-packages/mistune/scanner.py It's not hard to search for those definitions, but if someone doesn't know a smattering of python, it might not be obvious. 2) Similarly, migrate (using postgres) also gave the error: File "/opt/mailman/venv/lib/python3.9/site- packages/django/db/backends/postgresql/utils.py", line 6, in utc_tzinfo_factory raise AssertionError("database connection isn't set to UTC") I was able to find a discusson of this one at https://stackoverflow.com/questions/68024060/assertionerror-database-connec… which had me downgrade to an older version of psycopg2-binary: pip install psycopg2-binary==2.8.6 There might be a different fix, but this worked. 3) When I ran the test "uwsgi --ini /etc/mailman3/uwsgi.ini" I got the error: ModuleNotFoundError: No module named 'settings' This was also trivially fixed by adding the path: export PYTHONPATH=$PYTHONPATH:/etc/mailman3 in /opt/mailman/.bashrc 4) Sometimes when I rebooted the machine, when I ran 'systemctl start mailman3' I'd get the error that mailman wouldn't start because the lock was stll there. I never could figure out where the lock was, so I worked around it by replacing ExecStart=/opt/mailman/venv/bin/mailman start with ExecStart=/opt/mailman/venv/bin/mailman start --force in /etc/systemd/system/mailman3.service I'm sure there's something bad about doing that, but it works for me, so far. 5) I had a problem with mail to outside people not being delivered while mail to the local host was delivered. It turned out that this was because in my mailman.cfg I had "smtp_host:my.listserver.tld when it should have been localhost. The error was "relay access denied." To fix this, I had to add my.listserver.tld to "mynetworks" in /etc/postfix/main.cf, ie change: mynetworks = 127.0.0.0/8 10.0.0.0/24 to mynetworks = 127.0.0.0/8 10.0.0.0/24 111.222.333.444 <--- my ip address However, Mark Sapiro (a God) told me this was because I had changed a line in the [mta] section of mailman.cfg. I had changed smtp_host: localhost to smtp_host: mydomain.tld Here's the thing. The reason I did this was because the instructions at https://docs.mailman3.org/en/latest/config-core.html give this as their model: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com <---- not localhost smtp_port: 25 The instructions are good, but there are a few places where one size does not fit all, I guess. 6) A second error in delivery to outside addresses resulted in an "Access denied" error. A search on the internet revealed that this had to do with (for me) smtpd_recipient_restrictions in postfix. See, for instance: https://know.mailsbestfriend.com/postfix_error_relay_access_denied_noqueue_… Changing this fixed things. I'm not sure, but I think this shows up mostly with installations that include dovecot. 7) If you are using virtual domains in postfix, you need to use the "unusual postfix configuration" in https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… virtual_alias_maps = hash:/path-to-mailman/var/data/postfix_vmap 8) You need to manually set the local virtual host for mailman3. Somehow, I got the impression from the installation instructions that this was done automagically to the default x.mydomain.tld if your domain is mydomain.tld. It doesn't. 9) Follow the instructions verbatim, and follow them in the order provided. I installed postfix and nginx out of order, and it did OK, but once you get into the python virtual environment, it is easy to miss something if you don't do it in order. 10) Jot down lots of notes. This is one of the more complicated installations I've done, mostly because it involved configuring a zillion packages to talk to each other: Postfix, nginx, postorius, hyperkitty, django, and others (I'd never heard of "whoosh" or "sass" for instance). All of these can be unforgiving with configuration errors. The default installation instructions assumed a number of packages I'd never used. I'm an apache/dovecot/mysql kind of person, and I had to switch to nginx/postgres to use the instructions as the written defaults. I'm sure I could have used apache and mysql, but it would mean trying to figure out what didn't work without following the installations verbatim. I'd never even heard of postorius, hyperkitty, or django. So, it was easy to get confused a bit. Taking notes of changes I made was important in being able to back out of disastrous choices. Plus, once I'd installed it on one machine, I sat down and installed it on another machine, and it was very useful to have written down how I fixed an issue when it came up again -- and I didn't remember exactly what I had done. 11) Make multiple sequential backups of configuration files. I went down a couple of paths I shouldn't have gone down. For instance, with the vmap issue, I got it in my head that it was a postfix configuration issue, not a mailman issue. So I kept changing things in postfix. Once I was told that it was in *mailman* I had to set the virtual host, I needed to back out of about 8 tweaks I'd made to main.cf in /etc/postfix. If I hadn't been making main.cf.backup.01, main.cf.backup.02, etc. I would have had to spend another few hours trying to remember what inappropriate changes I had made. This is particularly true for me because I am not a great typist, and when I try to retype something to back out, there's a reasonable chance I'll mistype something and it still won't work. With these backups, I don't have both manually back out of things *and* proof my typing again and again. It's a lot easier to delete backups once things are working than to try to remember what you did late at night after a couple of bourbons. 12) Choose one set of installation instructions and follow it. Don't try to mix instructions from different tutorials unless you really know what you are doing. I didn't. For instance, there's a different set of mailman3 installation instructions at: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 It does things a little differently. It's useful to look at that when you are debugging why something's not working, but you can get into some trouble trying to do both installations at the same time -- which I found myself doing when something wasn't working. It didn't help. billo

3 years, 10 months

[MM3-users] Re: Mailman3 on FreeBSD

by John Poltorak

I'm following the official docs:- http://docs.mailman3.org/en/latest/prodsetup.html I'm trying to get it installed, 'pip3 mailman install works' but I don't know what to do after that. I haven't done anything with 'mailman.cfg' because I don't know what to do.and then I get errors when running 'mailman info' because of a missing '_sqlite3' module. On Fri, Aug 11, 2017 at 12:58 AM, Terri Oda <terri(a)toybox.ca> wrote: > I pinged a couple of friends who might have, but I don't know the answer. > Have you tried and gotten stuck, or just curious if it's been done? Because > I'm really curious myself now! As long as you can get the right versions of > python, it probably should work but that doesn't mean it does. > > Terri > > On August 9, 2017 10:08:05 AM PDT, John Poltorak <karotlopj(a)gmail.com> > wrote: >> >> Has anyone managed to install Mailman 3 on FreeBSD? >> ------------------------------ >> >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >>

8 years, 2 months

[MM3-users] Hyperkitty message threading

by andrew.bernard＠gmail.com

I am seeing some anomalies with message threading. without going into detail about the symptoms, first le me ask how does Hyperkitty thread messages? Is it based on the message-id in the header, guaranteed unique, or on the subject header? I appear to have a situation where people reply to a message, and then probably thinking to start a new thread, change the subject field., and them post. The message goes to the original thread. I cant stop people doing this as it seems the vast majority of people all over just hit reply for most things anyway as they are generally too lazy to start a new mail (drives me nuts). With this situation, where the subject has apparently been changed, Hyperkitty adds a not to the top of the post "New subject ...' which is what makes me think the message id is involved. Some of my subscribers say they do this all the time on the old Listserv mailing list and a new thread is started. Any help would be appreciated. It's difficult fro me to manually ressign the incorrectly threaded replies as there is no parent message to attach them to. Andrew

6 years, 3 months

[MM3-users] Re: Running mailman shell commands in a script

by Abhilash Raj

On Tue, Sep 14, 2021, at 4:57 AM, Eggert Ehmke via Mailman-users wrote: > Hello, I understand that the mailman shell is basically interactive. I need to > run some actions as adding and deleting users in a Linux shell script, or even > from another python program. How does that work? Check out mailman members, addmembers, delmembers, syncmembers commands[1] and see if they do what you are expecting the Mailman2 commands to do or you need something more. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… If you are using another Python program, then you can rely on mailmanclient[2] python package for operations on lists and memberships using Mailman's REST API. [1]: https://pypi.org/project/mailmanclient/ > In fact, I miss the commands that were in the bin directory of the old > mailman2 installation. Wouldn't it be nice to add them again to mailman3? > > Cheers, Eggert > > > _______________________________________________ > 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: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 6:59 AM, Mark Sapiro wrote: > On 4/25/23 3:02 AM, Andrew Hodgson wrote: >> >> You may find this script useful: >> https://www.msapiro.net/scripts/clean_users.py > > I will modify the script to enable deleting Mailman users with no > memberships even if they aren't Django users and post here when it's done. The script at https://www.msapiro.net/scripts/clean_users.py has been updated. As before, it has settings to control whether Django users are deleted if there is a corresponding Mailman user with no memberships or only if there is no corresponding Mailman user, and whether or not Mailman users with no memberships are deleted. The difference is when deleting Mailman users it will now delete Mailman users with no memberships whether or not there is a corresponding Django user. -- 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: Newbie hyperkitty question

by David Newman

On Jan 11, 2022, at 09:08, Stephen Daniel <swd(a)pobox.com> wrote: > > > Thanks. So yes, I'm clearly running hyperkitty. Good to know. > > What is the archiver named "prototype" that is selected in the list options page? As you saw, that one stores messages under var/archives/prototype. It captures the entire message, including all headers, and is intended for use by an external archiver. Hyperkitty saves only the message_id, subject, date, in_reply_to, and sender info. That’s fine for most use cases, but if you want to extract some other detail from metadata — say, which mail client is most popular* — you’d need a complete set of headers. *Even then, the survey might be skewed, since not every client adds a header. > See screenshot below: > > > Would also like to know how I control archiving policy -- specifically how long archived entries are saved. I’m also a newbie here, and I don’t know. From what I’ve seen, nothing gets purged by default. I imported many lists from MM2.1 with archives going back many years, and they are all present. And there was this recent discussion on this list about this about purging older entries: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… One nice thing about Hyperkitty is that it’s a searchable archive, so useful for finding hints about the care and feeding of MM3 and its friends. dn > > >> On Tue, Jan 11, 2022 at 11:51 AM David Newman <dnewman(a)networktest.com> wrote: >> > On Jan 11, 2022, at 08:28, Stephen Daniel <swd(a)pobox.com> wrote: >> > >> > Mailman users -- >> > >> > I am setting up a new mailman3 installation, and this is my first >> > experience with the suite. All of the software is up and running, but I >> > cannot tell if hyperkitty is actually running. >> > >> > When I look at my test mailing list, two archive options are available, >> > hyperkitty and "prototype", and both are enabled. I can see that my email >> > is being archived, but I think "prototype" is what is doing the archiving. >> > I see that a test message will end up in >> > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... >> > and nowhere else. This suggests that "prototype" is archiving, but >> > hyperkitty is not. >> > >> > So, this opens up a raft of questions on hyperkitty: >> > >> > - How do I tell if hyperkitty is actually running? >> >> Is hyperkitty enabled? In the Postorious admin panel for your list page, check under Settings/Archiving. >> >> Generically, the URL for Hyperkitty archives is something like this: >> >> https://lists.domain.tld/archives/list/listname@lists.domain.tld/ >> >> When I’m logged in (which I needed to be to check settings), I see archives at that location. >> >> Also, your mailmanweb database should have a bunch of ‘hyperkitty_*’ tables. I’m not ssh’d in to a MM3 server right now but IIRC the messages go into the hyperkitty_email table. >> >> dn >> >> >> >> > - Does hyperkitty have a web-UI for admins or users? How would I access >> > it? >> > - I can not find any documentation on hyperkitty, other than >> > installation instructions and change logs. Does documentation exist? >> > - How do I set policies on how long archives are kept? >> > - Assuming I want to back up my archives, what do I need to back up? >> > >> > Thanks for your help! >> > >> > -- Stephen Daniel >> > _______________________________________________ >> > 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's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: Strange password problem

by Jens Günther

I do have the exact same situation. I would love to have domain owners be able to create/manage their own lists for their respected Domain. One problem I see with giving them site ownership: when creating a new list, not only that they could pick the wrong domain by accident, they also see all the other domains present in the installation. That would be a nogo, tehrefore we have to create the lists for all associations on our side. Kind regards, Jens. Am 23.09.23 um 20:42 schrieb Stephen J. Turnbull: > And how much does it cost you? It doesn't sound like you're ready to use > the feature at this point, but that often happens when users don't know > that there's a feature they could ask for. Is there real risk that > domain owners would abuse or mistakenly use site admin privileges on the > whole site or on someone else's domains? Are you currently hoping to > devolve domain administration to other individuals (now that you know > it's probably possible with improvements to Mailman)? Do you have > candidates for those domain owners in mind?

2 years, 1 month

[MM3-users] Re: "held for moderation" - alias domain details sought

by Greg Newby

Thanks for this. After adding to "acceptable aliases," I also needed to add an entry in /etc/aliases, and then the moderation didn't happen. That's great! If I use an alias domain, will that replace the need for entries in /etc/aliases? I'm hesitant to explore since this is my production mail server. ~ Greg On Fri, Nov 1, 2024 at 1:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/1/24 11:14, Jeremy Stanley wrote: > > On 2024-11-01 11:04:07 -0700 (-0700), Greg Newby via Mailman-users wrote: > >> Hi friends. I've viewed this old thread: > >> > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > >> and documentation here: > >> > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > >> (and the Postfix docs it links to). Those documents don't seem to guide > my > >> situation, or maybe I just need a more specific example. > > > The alias domain discussed at > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > has nothing to do with what you are doing. > > > >> The problem is that when messages are delivered to the alias domain, > they > >> are held for moderation. I.e., mail to the alias domain like > >> testlist(a)domain.tld is held for moderation, but mail from the same > >> subscribed, non-moderated user to testlist(a)lists.domain.tld is posted > >> immediately without moderation. > > [...] > > > > I manage a similar setup (though with Exim instead of Postfix), and > > when migrating from Mailman v2 to v3 kept the same basic settings > > which seemed to work: notably, under Message Acceptance I set the > > alias addresses for the list in the Acceptable aliases field. If > > memory serves, not doing that caused messages addressed to those > > aliases to be unconditionally held for moderation. > > > This is the correct solution. Just add `testlist(a)domain.tld` to the > acceptable aliases setting of the `testlist(a)lists.domain.tld` list. > > -- > 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 gbnewby(a)petascale.org >

11 months, 4 weeks

[MM3-users] Re: Dump/restore users (with passwords) via API

by Abhilash Raj

On Mon, Sep 17, 2018, at 12:15 PM, Dmitry Makovey wrote: > We are trying to dump/restore users using API calls and it seems that > API allows us to dump password hashes (a good thing), but then API does > not allow to insert users back using saved password hashes - only > cleartext passwords. I'd say that is intentional. You don't want people to be setting up hashes as passwords. > Aside from create_user is there any other way to > create users/change their password? Not that I know of, not using the API atleast. You could potentially use the low level API that inserts records in the database or use SQL to dump and restore that data. What do you use the Core's user/password for? Currently, the user passwords are basically just a carry-over from Mailman2 and there shouldn't be any use for it. I have been considering removing that completely have Postorius do all the authentication/authorization. Email based authentication should rely on more reliable identities like email signatures, intead of having to send cleartext passwords over email. -- thanks, Abhilash Raj (maxking)

7 years, 1 month

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 16/9/21 16:40, Mark Sapiro wrote: > On 9/16/21 2:39 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> Hi all: >> >> I need to provide the list moderators a way to change the moderation >> flag for users from whichever it is (normally "list default >> processing") to "hold for moderation" and viceversa (to "list >> default" or to "accept") >> >> I understand that it could be done via console script (That's the way >> I did on mailman2: I made two commands using "withlist", one to hold, >> moderar.py, and other one to accept, desmoderar.py. I show you below) > > > Are you asking what the equivalent MM 3 scripts would be? > More or less: I'm asking for a general direction here. I think I cannot use tthe "withlist" method as before, inside a python script, and I'm not sure how to do it. I've been reviewing all the command docs that I've found, but I have no clear way. I need a shell or a python script that I can pass the list and the mail address to put on hold/hold (that way the moderators can log in a special account thhat asks for the address to hold/unhold). I did it in mailman2 whith the bin/withlist command, but now whithlist seems to be an alias for shell and is interactive.Thats not my goal) > >> But I think I'm not the only one that could use as an improvement a >> way to do this on postorius/web. > > > Postorius allows a list owner or site admin to set Moderation for list > members and non members at e.g. > https://www.example.com/mailman3/lists/list.example.com/members/(non)member/. Yes, I know that. But the owner cannot be 24/7 attending the lists (as we all know), and could need a help hand from moderators. Not just from accepting mails on hold, but to put on hold a member (and be capable of reversing it) when the netiquete dissapears completely and some thread becomes a flame and all goes south. I'ts the admin capability I miss the most for moderators in mailman. > Currently, a list moderator who is not an owner cannot do this, but a > moderator can set Moderation for the sender of a held post when > handling the post. But I'm talking about a moderator can put a member mails in hold when it is marked to accept. To prevent putting more gas in the fire. > >

4 years, 1 month

[MM3-users] is it possible to rebuild mailman-web database please?

by Stephen J. Turnbull

Giovanni Biscuolo writes: > After the upgrade I got this very same issue: > https://gitlab.com/mailman/hyperkitty/-/issues/328 Looking at the discussion in that issue, I wonder if there is a bug in sqlite3. The reference to 'hyperkitty_email__old' which apparently doesn't exist in the database or in Mailman migration code suggests that this is internal to sqlite3 when you do a schema change. You could try posting to sqlite3 channels. In general, this is NOT a Mailman problem, it's a database problem. We'll do what we can to help you, but we know a lot of Mailman and Python, and a little bit of SQL. If the database gets corrupted, database internals is not our area of expertise. FWIW, Postgres is currently the recommended RDBMS. MySQL/MariaDB are also usable, but it's somewhat fragile in its default configuration (I think one Mailman issue depending on implementation dependent behavior is now fixed and there's a workaround for MySQL's default refusal to handle emoji, but OS distributions are not necessarily up to date, and MySQL's history has been one thing after another for us). sqlite3 is supported primarily so Mailman unit tests don't depend on a separate full-scale RDBMS being installed. As far as I know it works fine within its limits, but I believe there are some limits that Mailman installations occasionally run into, and the full-scale databases perform better. I'm not saying "don't use sqlite3"; you have to consider whether you are likely to run into hard limits or performance issues, and that will probably never happen if you are running a couple of low-traffic lists. However, given that that your database is currently seriously damaged and may be irreparable (see below), it might be a good time to consider switching RDBMS and starting from scratch. You probably do have Postgres or MySQL (or the MariaDB variant) installed already, as many applications pull one or the other in. > Actually the django_site table is in the database so I can't understand > why of this message. One cause of this kind of situation is that there are several copies of the database lying around, and the database you found the table in is not the database HyperKitty is using. Even if there's only one copy visible on disk: if you have a process that attached to an old database file still running, that file could be deleted (ie, removed from the directory and marked for deletion) but the data will still be preserved and used by that process until the process is terminated. I think this is unlikely: database managers usually are quite protective of the files they use both as data and as they are managed by the OS, and I would think sqlite3 would notice if its database file were removed by another process. But the general principle stands: make sure all processes have been stopped, move any database files that aren't current somewhere Mailman can't find them (eg, removable media and remove it!), and restart the Mailman system. > Please is there a way to recreate the mailman-web database from > scratch or to fix this kind of problems? That depends. If you have a user base that has interacted with the web interface, creating users, authenticating email addresses, changing their profiles, then no, you can't recreate it from scratch. You lose all their authentication and profile data, although you might be able to get a mostly complete list of users and addresses from the subscription database in Mailman core. Otherwise, I would first dump the corrupted database to an SQL script to recreate the database, then reinstall HyperKitty, then find an SQL expert to help me figure out which parts of the SQL script are relevant, which are going to cause errors (eg, trying to create tables that already exist because of the installation process), and what I need to do by hand because it is part of the data that got corrupted. Mark may have other ideas, but he seems to have covered most of the possibilities in the issue #328 already.

4 years, 9 months

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

by Mark Sapiro

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

5 years, 1 month

[MM3-users] Re: How well does DMARC mitigation work nowadays?

by Mark Sapiro

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

1 month, 1 week

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

by worik

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

6 years, 8 months

[MM3-users] Re: Adding / manipulating users

by Seth Seeger

> On Nov 18, 2019, at 2:28 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/18/19 6:15 AM, Seth Seeger wrote: >> >> My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. > > > ... > > Alternatively, you could create a script that would post the appropriate > transactions to add a member and set moderation and delivery status to > Mailman's REST API and use that to process your members. Great! I can definitely do the REST API route. If I create a script to take a CSV and push it through the API, is there a place I can post it to make it useful for others? Seth

5 years, 11 months

[MM3-users] Re: share directories between postfix and mailman 3

by Mark Sapiro

On 1/23/24 12:30, Thomas Schachtner via Mailman-users wrote: > > > Mark Sapiro wrote: >> >> Why do you think Mailman needs the contents of the postfix >> configuration file.. I don't think so. > I thought so, as mailman does not start if there's not > /etc/postfix/main.cf file is there. > > The following messages are logged: > Jan 23 21:20:35 mailman mailman3[491404]: RuntimeError: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not > permitted > Jan 23 21:20:35 mailman mailman3[491404]: command failure: > /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation > not permitted Mailman itself is not looking for Postfix main.cf, but when Pustfix is the MTA, it invokes the postmap command to create the .db files for postfix_lmtp and postfix_domains. Apparently postmap fails if there is not a Postfix main.cf. You can avoid this by using regexp tables instead of hash tables. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>. >>> This seemed to work pretty fine, as all files and directories seemed >>> to be available, but when starting mailman 3, the following error >>> message was shown: >>> FileExistsError: A race condition might have happened. >>> /var/lib/mailman3 actually exists and is not a directory. >>> >>> Any idea why this message is shown? >> >> Possibly because the uid and gid of /var/lib/mailman3 on the postfix >> machine do not map to the appropriate Mailman uid and gid on the >> mailman machine. > You refer to the uid and gid of the "list" user? They are both 38 (uid > and gid) on both machines. > Then that isn't the reason. I don't know then why Mailman would complain that /var/lib/mailman3 actually exists and is not a directory. This message comes from mailman.utilities.filesystem.makedirs(). The code is at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/file…>. makedirs() calls first_inexistent_directory() which checks if the directory exists with os.path.isdir() which apparently says it isn't a directory which makes no sense unless there is an actual race condition and you are creating the /var/lib/mailman3 directory on the mailman machine at the same time as you are starting mailman. BTW, you say you are doing sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 on the mailman machine. Presumably on the mailman machine /var/lib/mailman3 has lots of content. How does that 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: Templates

by David Krantz

Hi. Ok, checking the source helped. So I answer my own question: > mailman shell Welcome to the GNU Mailman shell >>> tm = getUtility(ITemplateManager) >>> tm.set('list:member:regular:footer','mymaillist.example.com','file:///my_absolute_path/list:member:mymaillist.example.com:footer.txt') >>> commit() // David On Sat, Sep 23, 2017 at 1:17 PM, David Krantz <gazorg(a)gmail.com> wrote: > Hi. > > How do I set a template for one specific list? I want one list to have > a special footer template. > > I have tried updating the database (template table) without effect so > apparently the database is not used for templates or some kind of > fallback is used to set it to the generic footer. Of course I also > tried to restart mailman after that operation to try to rule out any > caching-related problem. > > I want to use a file://-path as that is the least painful way of doing > it. I also would like a solution to place a file in a special > location. My current templates are in a > > .../var/templates/site/en/ > > structure with names like list:member:generic:footer.txt > > Cheers > // David

8 years, 1 month

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

by Mark Sapiro

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

4 years, 7 months

[MM3-users] Re: reason for breaching max_message_size is "N/A"

by Barry Warsaw

On May 01, 2017, at 08:05 PM, David Krantz wrote: >Today I learned to things: The default max_message_size is 40kB. >Messages larger than that are blocked (expected) with the reason "N/A" >(not expected). The reason would be helpful to me as admin. This would actually be a fairly easy fix. The MaximumSize rule in mailman/rules/max_size.py really just needs to set the msgdata's 'moderation_reason' key to whatever we want the text to read. >Also: Is there any way to set a server default for this as it is a bit >of a hassle to change it from the command line for each new list. I >can of course find where in the code to change but that seems the >wrong way to me. There's no server default, but the way to do it would be to create a style based on the legacy-default style which overrides the setting of mlist.max_message_size. There should be a way of doing this as a plugin site wide, without hacking the code, but I don't have the time to write up the details of that atm. -Barry

8 years, 6 months

[MM3-users] Re: Domain Resolving Issue

by Abhilash Raj

On Thu, Mar 7, 2019, at 11:36 AM, brian(a)emwd.com wrote: > I am running a Mailman 3 server with about 5 list domains configured on > it. Most of them resolve quickly both to Postorius and HyperKitty. > However there is one domain that resolves very slowly. Once it does, > access to other pages/tasks go quickly. If you don't do anything with > that domain in the browser after about 5 minutes, it takes its time > again to resolve. What could be causing this? The webserver is Nginx. > Not sure if this is a Mailman 3 issue or not. It is unlikely that this has anything to do with Mailman. The faster access after first time is probably due to local caching of DNS entries. Try checking your DNS servers for the domains and how long they take to respond. Your browser is probably just waiting more for DNS response. Mailman should be responding with similar lag for all the domains. > > Brian > _______________________________________________ > 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, 7 months

[MM3-users] Re: Help with fresh debian install

by Stephen J. Turnbull

Jonas Meurer writes: > > This is the issue. I don't know how the Debian packages do this, but I > > recommend having a 'mailman' user that owns everything and running > > commands as that user. > > The Debian package uses user `list` for this. It also provides a command > `mailman-wrapper` which takes care of running mailman commands as this user. > > It would be awesome if the upstream /usr/bin/mailman command could take > care of this automatically, making the wrapper command obsolete. What precisely is "this"? We already have the mailman command; are you suggesting it should be suid/sgid mailman/list/whatever? That's pretty obviously a vulnerability. If there are any RCEs *anywhere* on your host, your Mailman is pwned. If you know your installation is secure enough or you just don't care, fine, chmod it yourself. If not, how do you propose upstream "take care of it?" 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

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

by Mark Sapiro

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

3 years, 4 months

[MM3-users] Re: CPU usage when idle

by roughnecks

Il 28/05/2025 23:42, Mark Sapiro ha scritto: > On 5/28/25 08:27, roughnecks via Mailman-users wrote: >> >> It's the manage.py qcluster whatever is called. I have shut down MM >> for the time being, because I'm not fully motivated to have it >> running, so I can't be more accurate right now. > > I don't know how qcluster is configured in the Debian packages (which > are out of date and possibly buggy anyway). You may be using django-q > <https://django-q.readthedocs.io/en/latest/> and if so, you should > migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both > typically use memcached as a backend. I wouldn't know how to migrate and if that means doing anything not in the debian-way (haven't opened any link so far). About qcluster configs, yes, all correct but there is no configuration for caches, so probably it's the default one you specified. I can look into this. > You can get info about what qcluster is doing with `manage.py qinfo` and > monitor things with `manage.py qmemory` and `manage.py qmonitor`. Thanks, helpful.

5 months, 1 week

[MM3-users] Re: mailman3 not working for mailman21 lists

by Diana von Bidder

Hi Stephen Stephen J. Turnbull wrote: > Diana von Bidder writes: > >> I have several entries in /var/lib/mailman3/queue/shunt/ with >> Aug 21 timestamps, > > Evidence! Preserve it! > > You can look at those using "mailman qfile <file>" [..] These files looked pretty normal... >> and several entries in /var/lib/mailman3/queue/shunt/ with >> current timestamp (i.e. everytime I ls -l there is a new timestamp >> with the current time). > > I'm not sure what's going on with that. The point of the shunt > queue is that Mailman doesn't know what to do and it's putting the > messages there to wait for human intervention. So timestamps > shouldn't be changing. I just realised that I made a mistake here while typing: it should read "in ... out ...". > You can also try the "mailman unshunt" command (which takes no > further arguments). Then "mailman unshunt" just moves all the files > in "shunt" back to the queues they came from for normal processing. As I didn't want to spam the recipients of the mailinglist with a lot of testmails (once they all would be sent out), I created a tar.gz of all the files in shunt and out, then deleted all contents and resent a single new mail (also because in the meantime a mail to another old mailinglist just worked fine, so the problem seems to be connected to a specific list and not lists imported from mailman2 in general). What then happens is the following: 1) I see the connection in /var/log/mailman3/smtp.log and a bak-file in /var/lib/mailman3/in. 2) I see an ACCEPT in /var/log/mailman3/mailman.log and the bak-file in /var/lib/mailman3/pipeline 3) I get the following error once a second in /var/log/mailman3/mailman.log ------ Aug 29 11:35:06 2022 (936) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL was not found on this server.</p> <hr> <address>Apache/2.4.54 (Debian) Server at localhost Port 80</address> </body></html> (404) ------ and see the bak-file and a .pck.tmp-file in /var/lib/mailman3/out (always current timestamp). The files always vanish and reoccur with new names (I assume timestamps are part of the names). Doing a mailman qfile on the .pck.tmp file shows nothing special. Do you have any idea which configuration could cause this behaviour for this specific list but not for others? Regards Diana

3 years, 2 months

[MM3-users] Re: Speed/progress of update_index_one_list?

by Stephen J. Turnbull

Philip Colmer writes: > I have now switched to Xapian but, in a way, my original questions still > stand. Is there a way of monitoring the progress of > "update_index_one_list"? What can I do to the specification of the server > to make that process go (much) faster? I see you've already gone to the Xapian lists, which I think is the right place to ask. We appreciate that! But I hope everyone will feel free to ask such questions here (just don't get too upset if we suggest going to the upstream channels in lieu of providing answers ourselves :-). If you do get an answer, feel free to bring it back and ask for Mailman automation for it (as a tracker issue, please, so it doesn't get lost). As I've mentioned before, it's That Time of Year when we start to prepare for GSoC. No guarantees and eventually the students choose their own projects, but suggestions are welcome. > By the way, just in case anyone else is looking to use Xapian, > installing and setting up Xapian for HyperKitty can be boiled down > to: Thanks for the hints! Steve

3 years, 9 months

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

The REST API documentation is a bit informal. As someone who is not familiar with mailman, and who doesn't know python, they are a bit of a slog. One day it would be nice to augment the documentation with a formal and complete reference document. Something like this one <https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_REST_API_R…>. A formal reference manual needs a complete listing of every type of object, all possible operations on each object, and all required and optional parameters. Since creating a formal document like that is probably out of scope, at a minimum it would be good to specify that boolean values are passed as JSON strings, not JSON booleans. It might be worth seeing if the code can be enhanced to allow the boolean values to be sent in using JSON booleans as well as JSON strings. Thanks again for the prompt response! -- Stephen On Tue, Jan 18, 2022 at 4:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 10:53 AM, Stephen Daniel wrote: > > 2nd follow-up. Apologies for spamming this list. > > > > I went wandering through the code as suggested by the traceback. I > > discovered that thee "as_boolean" routine is expecting a string argument > > but getting a boolean argument. > > > > So, If I send the booleans as strings, with values "true" or "false", all > > is well. > > This is not what the API documentation suggests I should do. Can someone > > either fix the documentation or the code? > > > Those snippets in the documentation are doctests. That code is actually > executed by unit testing and passes. In all those snippets, dump_json is > passing the second argument as `data` to > mailman.testing.documentation.dump_json() which in turn calls > mailman.testing.documentation.call_http() which calls > mailman.testing.helpers.call_api() which ultimately calls > requests.request() with the same `data` argument. > > So basically, the issue is the difference between how requests.request() > handles that `data` dictionary in creating the POST data and whatever > you are doing. > > Possibly we could add some caveat to > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…> > > or possibly elsewhere. Do you have a suggestion as to what? > > > -- > 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, 9 months

[MM3-users] Re: Trying basic install of mailman3 in docker, but how do you set allowed hosts?

by Abhilash Raj

On Thu, Jul 8, 2021, at 12:23 PM, bob B wrote: > I am starting small, My goal is just to get mailman3 running in docker > and test the website access via curl from the host, then I will move > on from there > > In the docker instructions it says > > SERVE_FROM_DOMAIN: The domain name from which Django will be served. To > be added to ALLOWED_HOSTS in django settings. Default value is not set. > This also replaces Django's default example.com SITE and becomes the > default SITE (with SITE_ID=1). Perhaps that is my English there, but what it really meant to say was you should set "SERVE_FROM_DOMAIN" in your "environment" section of the docker-compose.yaml file and it will add the value of that variable to Django's ALLOWED_HOSTS settings for you [1]. If you think it could be re-worded for clarity, please feel free to let me know or open a PR in the Github repo. [1]: https://github.com/maxking/docker-mailman/blob/main/web/mailman-web/setting… Also, "localhost" is already added to the list of ALLOWED_HOSTS, so if you are able to point to the container using that, it should work without setting the SERVE_FROM_DOMAIN. Abhilash > But where do I set the ALLOWED_HOSTS I added this to the yaml file > - ALLOWED_HOSTS=127.0.0.1 under environments > > > mailman-web: > image: maxking/mailman-web:0.3 > container_name: mailman-web > hostname: mailman-web > depends_on: > - database > links: > - mailman-core:mailman-core > - database:database > volumes: > - /opt/mailman/web:/opt/mailman-web-data > environment: > - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static > - ALLOWED_HOSTS=127.0.0.1 > - DATABASE_TYPE=postgres > - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb > - SECRET_KEY=333blah-blah-secret > - HYPERKITTY_API_KEY=333someapikey > ports: > - "127.0.0.1:8000:8000" # HTTP > - "127.0.0.1:8080:8080" # uwsgi > networks: > mailman: > > > > But when I try: > [docker-mailman]# curl 127.0.0.1:8000 > <h1>Bad Request (400)</h1>[root@bmimailmandr1 docker-mailman]# > [root@bmimailmandr1 docker-mailman]# > > > > I see this in the logs > > [docker-mailman]# cat /opt/mailman/web/logs/mailmanweb.log > WARNING 2021-07-08 17:40:46,979 1642 django.request Bad Request: / > ERROR 2021-07-08 19:20:58,416 1641 django.security.DisallowedHost > Invalid HTTP_HOST header: '127.0.0.1:8000'. You may need to add > '127.0.0.1' to ALLOWED_HOSTS. > WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / > WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / > _______________________________________________ > 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, 3 months

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

by Mark Sapiro

On 2/3/22 08:01, Stephan Krinetzki wrote: > Hello all, > > we now have at least one mailing list (there may be more affected) that generates a 500 error when calling the held_messages page. After looking at the held messages via the mailman shell, we have identified three mails that have neither a subject nor a message body. How can we remove these three mails from the database? This shouldn't be an issue, at least with Mailman core 3.3.5, unless I don't understand. Note that there are 3 tables involved. The request (IListRequests), the pendings (IPended and IPendedKeyValue), and the held message (IMessageStore). > This is the mailman shell command we used: > > mailman shell -l listname(a)lists.example.com > <removed> > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > Die Variable 'm' ist die listname(a)lists.example.com Mailingliste > >>> msg_db = getUtility(IMessageStore) > >>> req_db = IListRequests(m) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 > 107758: 1 OK, you have requests. > >>> from mailman.app.moderator import handle_message > >>> handle_message(m, 107758, Action.discard) > >>> reqs = list(req_db.held_requests) > >>> for req in reqs: > ... print('{}: {}'.format(req.id, req.request_type)) > ... > 32598: 1 > [...] > 107656: 1 > 107737: 1 OK, you discarded the message held with request id 107758. > >>> handle_message(m, 92927, Action.discard) > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/app/moderator.py", line 112, in handle_message > key, msgdata = requestdb.get_request(id) > TypeError: 'NoneType' object is not iterable > >>> There is no request with id 92927. Why do you think there should be? If by remove them from the database, you mean just from the messagestore, you can do (using your above) msg_db.delete_message('the_message_id') To delete a pending request for which there is no request id, e.g. the id 92927 above, you could do ``` pendings = getUtility(IPendings) for token, data in pendings.find(pend_type='held message'): if data and data['id'] == 92927: pendings.confirm(token, expunge=True) ``` Mailman core 3.3.5 has a lot of changes to address this issue. Also see https://gitlab.com/mailman/mailman/-/issues/946 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Anyone using Rspamd with Mailman 3?

by Philip Colmer

On Wed, 22 Sept 2021 at 10:14, Bjoern Franke via Mailman-users <mailman-users(a)mailman3.org> wrote: > > Hi, > > > > > I'm having a lot of trouble getting DKIM headers rewritten by Rspamd > > after Mailman 3 has altered the subject line and added the signature > > to the body and that, in turn, seems to then be causing Rspamd to not > > add the ARC headers. > > why don't you let Mailman3 do the DMARC mitigation? That is certainly an option. My main concern with this approach is that it needs to be configured on a per-list basis, as far as I can tell. My preference is to try and find an approach that works without modifying the settings per-list. I'll do some more testing with DMARC mitigation enabled to review the Rspamd logs under that scenario and see what breaks then. I'm starting to think that there might be a bug in Rspamd so my other next step is to revert to OpenDKIM for the DKIM headers and use Rspamd for the ARC headers (since I couldn't get OpenARC to work). Regards Philip

4 years, 1 month

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

by Mark Sapiro

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

3 years, 4 months

[MM3-users] Re: GDPR - save subscriptions confirmation emails

by contact＠maadix.net

Thanks Selva for you answer. In my Mailman 3 installation there is no /var/log/mailman/subscribe I have logs about confirmations emails in mailman/var/logs/smtp.log the format is the following: Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) handling connection Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'LHLO mails.example.com' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'MAIL FROM:<contact(a)maadix.net>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) sender: contact(a)example.net Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'RCPT TO:<prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org>' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) recip: prueba-confirm+7c010b0d89513b26d72cb4642e80447a2280ac86(a)list.example.org Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'DATA' Jun 03 13:45:27 2018 (20764) ('127.0.0.1', 40145) Data: b'QUIT' So, one solution that comes to my mind is to grep this log file. This is not a perfect solution and the full confirmation email is still missing. I am not sure if this would be GDPR compliant. Maddish El 03/06/18 a las 18:17, Selva Nair escribió: > Hi, > > On Sun, Jun 3, 2018 at 10:12 AM, contact(a)maadix.net <contact(a)maadix.net> wrote: >> >> Hi, >> >> I am new in the list. I have been looking for this topic in the archives >> in order to avoid duplicate, but I could not find any thread. >> >> According to the new GDPR rules, lists owners need to have a >> confirmation from subscribers, and this is easy to do with Mailman 3. >> >> What I can't figure out is how to save all the confirmation emails >> received from users. >> >> I only see the confirmations commands emails in the logs, >> >> Is there another place/way to store them? > > We have been doing this with mailman2 since Canadian Anti-Spam Law (CASL) > got enacted (2014) by independently archiving the confirmation messages. > With postfix we use recipient_bcc_maps and a script to do some extra filtering > but its clunky, and does not check that the confirmation succeeded or not. > > A feature within mailman to archive successful confirmations would be > useful. Keeping unsubscribe requests and evidence of subsequent > actions also seems necessary at least as per CASL. > > That said, we also keep the /var/log/mailman/subscribe logs (not sure > what that would be in mailman 3). Although the log has a single line > for each action, it may be enough to show (?) that a double opt-in process > was properly followed or unsub request was acted up on. > > Thanks, > > Selva > -- Maadix *MaadiX* Tu nube en tus manos https://maadix.net https://twitter.com/MaadiXnet

7 years, 5 months

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

by Mark Sapiro

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

1 year, 2 months

[MM3-users] Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Dear Mailman 3 wizards, Our subscription process requires that the applicant answers a few questions and sends them to the list moderator. Not having a template that gets sent on all subscribe requests, I'm using the 'list:admin:action:subscribe' template. This gets sent to the list moderator, who then sends it forward to the applicant. This is rather tedious. I would like the template to be sent directly to the applicant. There is a template, 'list:user:action:subscribe' that almost does this, but it gets sent only if the email address of the applicant is unverified. A good number of our applicants are already on our lists, so they would not get this template if we set the Subscription Policy to 'Confirm, then moderate'. Our Subscription Policy is currently: 'Moderate' for all lists. I figure that three modifications can be used to fix this: a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. c. That the current 'list:user:action:subscribe' be changed in published Mailman 3 source to 'list:user:action:confirm' and a new template ''list:user:action:subscribe' be set up to be sent when any subscribe request is made. This is more work, of course, so not likely a good thing to hack locally. It could be useful to other users. Any suggestions on how to best and most quickly do the above would be appreciated, starting with (a.) or (b.). Clearly, (a.) and (b.), if we do one of those, are hacks that will need to be applied upon Mailman updates. That's fine by me, as I'm in rush to get this done. I'd welcome pointers as to which file to change and how. Of these two options, which would be the least work? (c.) could be entered as a longer-term enhancement request. I can submit that request if you like. Yours, Allan Hansen P.S.: Thank you for the enhancement that lets moderators see the member lists. It has been a big help for us. GNU Mailman 3.3.8 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /opt/mailman/mm/mailman.cfg db url: postgresql://mailman:VWy26K4pUfU4jw@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass

2 years, 7 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote: >I understand you need to feel comfortable about everything going into >the core and this takes time and energy to review all the MRs, but I >think it is pretty important to get the DMARC mitigations into the core. >If there's anything I can do to help with this, let me know. > >I will rebase my branch again and possibly make one minor tweak, but I >think it should be OK. Thanks for pushing back on this Mark. Obviously, I have a high degree of trust in your work, but yeah, my compulsive behavior is showing through. ;) Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. >I can also work on Postorius. Also in this vein I have a question. >Should the DMARC settings be added to the Alter Messages tab in the List >Settings view or would it be better to have a separate DMARC Mitigations >tab. My gut reaction is to add a separate DMARC Mitigations tab, but Florian and Terri have final say I think. Cheers, -Barry

8 years, 10 months

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

by Mark Sapiro

On 10/11/2018 02:04 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> The templates named list_member_digest_footer.txt and >> list_member_regular_footer.txt (with underscores) were created by >> import21 and set as the URIs for those templates. Had you just copied >> /dev/null (or otherwise made empty) those files and done nothing else, >> that would have done what you wanted, but since you deleted the template >> URIs for the list, the template names are now the default > > How do I make these not default? You can set them via ITemplateManager. > Or when I upgrade to V3.2.2 will I be able to just empty the templates in /postorius/lists/LISTNAME/templates? You could except Postorius won't let you set an empty value for a template and deleting a template in Postorius just reverts to using the default - e.g., 'list:member:regular:footer'. What you need to do is copy /dev/null to files in (in your case) /opt/mailman/core/var/templates/lists/[LISTNAME_FQDN]/da/ named list:member:digest:footer.txt and list:member:regular:footer.txt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Tuesday, March 15, 2022 10:29 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/22 11:16, Quanah Gibson-Mount wrote: >> Hello, >> >> We have a constant issue with confirmation emails for subscribers >> getting lost and then the subscriber contacting us because their posts >> to the list never show up. Is there a way I can, as an administrator, >> do the confirmation on their behalf or in some other way promote them to >> being a member from non-member? > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/MJOOH23W6EKZO7GI5HRDKB4S733JEEVG/ > > If they don't have an outstanding subscription waiting user confirmation, > you can just mass subscribe them. > > If they do and your Postorius and Mailman core is reasonably up to date, > you can find the pending request at Subscription requests -> Pending > Confirmation, delete it and then mass subscribe them. Hi Mark, Thanks for the response. Unfortunately I'm currently stuck with the junk shipped by Debian. Yet another reason to move to a standalone install and avoid their broken packages. Regards, Quanah

3 years, 7 months

[MM3-users] Re: Mailman 3 Privacy Policies, GDPR, etc and social logins

by Jered Floyd

This was what I was using as well, but it failed to meet their requirements for some ineffable reason. I had a few back-and-forths with someone for whom English was not their first language, and got them to accept a slightly modified version that I posted at https://www.convivian.com/mailman-privacy.html Now, the latest is that I have a new message noting that apps requesting user data (e.g. email address) must be linked to Business Profiles (text below). Django-allauth is cool, but I think it's not going to be long for this world and we'll just have to do internal auth. Disappointing from a workflow perspective, but I'm happy to dissuade subscribers to not use Facebook. Regards, --Jered P.S. The fresh hell from Facebook: You are receiving this message because Mailman List Manager is not connected to a verified Meta Business Account. On Feb 1, 2023 Meta began requiring business verification for apps that request access to data from users (for some apps this is called advanced access). Learn more about this requirement. [https://developers.facebook.com/blog/post/2023/02/01/developer-platform-req…] Here’s what a person with full control of your Business Account needs to do by Feb 2, 2024 to maintain access: Connect the app to a Business Account, if you haven't already. Complete business verification for the Business Account. Business Accounts connect your Facebook Pages, Instagram accounts and the people who work on them, so you can manage them all in one place. ----- On Sep 19, 2023, at 5:00 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 9/19/23 6:22 AM, Jered Floyd wrote: >> >> This is a bit of a headache. Do we have a draft of a community Privacy Policy >> for a vanilla Mailman 3 install that meets Facebook's requirements? Is this >> going to be a constantly unraveling thread of future GDPR and Right to Be >> Forgotten troubles, since there doesn't seem to be an easy way to scrub a >> subscriber from Hyperkitty archives if they request so? How have others >> addressed this situation? > > > I use https://www.list.org/privacy.html which appears to satisfy Facebook. > > -- > 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 jered(a)convivian.com

2 years

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 12/8/21 6:05 PM, Philippe B wrote: > Update: After disabling the footer on a few lists (as described here a week ago), we started seeing "Cache content lost" in most (but not all) messages from those lists. > > In some cases, that phrase is an attachment to the "real" body of the message. In others, it's the opposite (which is more problematic for responding). That seems to depend on whether the poster sent in plain text. The difference between inline and attachment has to do with how footers are added. They are only added inline if the message after content filtering is a simple text/plain message. > One puzzling aspect is that it doesn't happen consistently. One hourly automated message will have it; but exactly the same message one hour later won't have it; but will have it again 3 hours later for example. > > Is that a known problem, or would it be possible to troubleshoot? Thanks. The issue may be a bug or a race condition. What is going on is the 'empty' footer you created in Postorius is retrieved from Postorius by a URL. In order to reduce the number of http transfers to retrieve such templates, they are cached in the local file system. Now, when we want a template that is accessed via a non-mailman: URI, we call the cache managers get() method at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/cache.py… to get it. This should return either None if there's no cached file or the contents of the file, but if there is an entry but no corresponding file, it returns 'Cache content lost'. This could occur if some asynchronous process expunged the entry between getting the entry and getting the file. A process that could do that is the task runner that evicts expired cache entries. Look in your mailman.log. There will be `ACCEPT: <message_id>` entries for each accepted message and there will be hourly `Task runner evicted expired cache entries` entries. Do the ACCEPTs for the affected messages occur at the same time as the evictions? One way to avoid this is to not use Postorius to set the template but rather, create an empty `templates/lists/<list_id>/en/list:member:regular:footer.txt` in mailman's var/ directory for each such list and delete the Postorius templates. Of course, this is just a work around and not a solution to the issue. A proper fix is probably to implement a lock on the get(), evict(), evict_expired() and clear() methods so they can't execute concurrently. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Nice! Up and running! How do I start using mailman? what are the steps?? REALLY thank you all for your patience and help! Really appreciated ! El vie., 21 jul. 2017 a las 18:48, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 04:43 PM, Rafael Mora wrote: > > YEEEES! At last!!! I can see the web UI. > > > > Now I´m getting this message in the web UI: > > > > Something went wrong > > Mailman REST API not available. Please start Mailman core. > > > > > > > > Where do I configure the REST API ????? > > > So I guess you figured out that ALLOWED_HOSTS is a Django setting in > settings.py or wherever your Django settings are. > > Now you have to start Mailman Core. In your Python 3 'env' where you > installed Mailman Core, run 'bin/mailman start'. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

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

by David Newman

On 12/23/21 9:18 AM, Mark Sapiro wrote: > However, that's not the issue. You originally reported and I didn't look > closely enough: > >> Update: The above worked fine until MM3 informed a list owner of >> pending subscription requests, with a URL like this: >> >> https://lists.example.com/mailman/admindb/listname >> >> and that URL returned a 404 error. > > > That URL is from a Mailman 2.1 installation. Are you still running > Mailman 2.1? I'm not, but that, and me not looking closely, was the problem. The system doesn't run MM2.1 any more, and no longer has it installed. But I failed to notice the dates on those 'admindb' messages: They were from the day of the upgrade, about 30 minutes before decommissioning MM2.1. And the docs do say explicitly to deal with any pending tasks before doing a cutover. The task-pending message that MM3 sends to list owners and moderators just says generically to check the dashboard, without providing a URL. Can that be modified to provide an explicit URL, something like this? https://lists.example.com/mailman3/lists/listname Thanks again for spotting this. dn

3 years, 10 months

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

by Mark Sapiro

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

3 years, 3 months

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Odhiambo Washington

PS: I beg you to put your responses below the last one. Makes the hierarchy look better. Now, have you edited your /etc/mailman3/mailman-hyperkitty.cfg and restarted MM3? On Tue, Jul 29, 2025 at 3:18 PM Willie Castillo < Willie.Castillo(a)caemilusa.com> wrote: > Odhiambo, long time no hear from you. Hope you are doing well. > > The last archived post for that specific list is July 3rd. 2025. We do not > see the one for July 25th. Also, I just noticed something else in the logs, > apparently the server is still having "SSLCertVerificationError" issues > even after updating the DigiCert, CA-Certificate,etc. I must be missing > something else. > > Based on that, looks like the archiving is failing still due to the > "SSLCertVerificationError". > > The spool directory now has 8 *.pck files in it. However, I do not see the > original ones from 7/25 > > ~# ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 14725 Jul 29 08:07 > 1753790859.2498085+320096cb9852779b55a4cbb1e4f9603736ebd78d.pck > -rw-rw---- 1 mailman mailman 15122 Jul 29 08:07 > 1753790859.2437658+7fddf881d592f27be60e32aa5b3c34c7077b9988.pck > -rw-rw---- 1 mailman mailman 6399 Jul 29 08:07 > 1753790859.2370558+ee410eb31691bf2854cca46c64e80e3bf61c3523.pck > -rw-rw---- 1 mailman mailman 26619 Jul 29 08:07 > 1753790859.230345+b2e70f5b65900731895bbee5a3d83401f1500567.pck > -rw-rw---- 1 mailman mailman 15676 Jul 29 08:07 > 1753790859.2225533+82371c8a0202d62eaa046dd3633a23d6837d7a80.pck > -rw-rw---- 1 mailman mailman 98273 Jul 29 08:07 > 1753790859.2136636+8ee9273fbbaf4352d482e69d177e2eb2824078a5.pck > -rw-rw---- 1 mailman mailman 98109 Jul 29 08:07 > 1753790859.2026713+49d82ecd57eda7eaa582ba925449e2343bea5c56.pck > -rw-rw---- 1 mailman mailman 88479 Jul 29 08:07 > 1753790859.191489+162aa89dcac50ca6f5463ce1098c828728af12d1.pck > > > > > ------------------------------ > *From:* Odhiambo Washington <odhiambo(a)gmail.com> > *Sent:* Tuesday, July 29, 2025 7:59 AM > *To:* mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>; Mark > Sapiro <mark(a)msapiro.net> > *Cc:* Willie Castillo <Willie.Castillo(a)caemilusa.com> > *Subject:* Re: [MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails > - Hyperkitty - CERT Issue > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > > On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < > Willie.Castillo(a)caemilusa.com> wrote: > > The issue started right after the site's CERT expired. The CERT expired on > 7/8/25. This is what's in the log... > > Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: > HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with > url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by > SSLError(SSLCertVerificatio > nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: > certificate has expired (_ssl.c:1000)'))) > > The CERT has been updated but the 7/25 message is not archived still. > > > While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what > is documented so that the issue doesn't recur: > ``` > [general] > base_url: http://127.0.0.1:8000/archives/ > <https://urldefense.us/v3/__http://127.0.0.1:8000/archives/__;!!E8b8mVbrrfWV…> > api_key: Secret_Hyperkitty_API_Key > ``` > > PS: I haven't seen your responses to @Mark Sapiro <mark(a)msapiro.net>'s > questions quoted below: > ``` > Did the new post get archived? If so, why is last post at still July 25, > 2025? If no, why not. The post must go to the archiver to cause the > queue to be processed. > > If the post was archived and the July 25 messages are still queued, > what's in Mailman's mailman.log. There should be error messages and > tracebacks indicating the issue. > ``` > > -- > 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 > <https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht…> > ] > -- 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]

3 months

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

by Mark Sapiro

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

8 years, 5 months

[MM3-users] Re: Moderating posts via email

by Abhilash Raj

On Thu, Oct 26, 2017, at 03:01 PM, Dmitry Makovey wrote: > On 10/26/2017 02:59 PM, Abhilash Raj wrote: > > Given how emails are not so good at being secret, I'd not advise using > > it despite it's current state. Although, if it is a feature, it should > > work regardless! > > agreed. but how do I strip that from the message sent to user since > instructions are hardcoded into chains/hold.py ? I am not sure of any easy way to do without patching the source itself. You can however modify the 'list:admin:action:post' template for the list with instructions to advise against using the "Approved" feature (regarless of what the text below/above says). I understand that it probably is going to confuse a lot of people, but I am just throwing out ideas to add a band-aid for the bug. Again, I am not sure this feature if broken, I haven't tested it. It might be worth opening issue in Core though. > > > -- > Sr System and DevOps Engineer SoM IRT > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) -- Abhilash Raj maxking(a)asynchronous.in

8 years

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

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

4 years

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

by Mark Sapiro

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

3 years, 5 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

This my settings.py email config: #DEFAULT_FROM_EMAIL = 'postorius(a)localhost.local' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root(a)localhost.local' # Change this when you have a real email backend # EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = '' EMAIL_HOST_PASSWORD = '' EMAIL_USE_TLS = False DEFAULT_FROM_EMAIL = 'Mailing <mailing(a)labbrands.com>' El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Re: Mailman not able to process "big" requests

by Mark Sapiro

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

7 years, 6 months

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

by Mark Sapiro

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

4 years, 4 months

[MM3-users] at the finish line of mailman3 docker, but can't sign in.

by bob B

I am trying to setup mailman3 in docker and have some questions, I can see the finish line :) i hope. I start my images and I can access the web,http://Servername.domain.com/postorius/lists/ and no list are there of course, but How do i sign in? I click the forget link and I have to enter in a email address. I put in the email address I added to the docker-compose.yaml but that does not wrok. I have these setup in the .yaml file. MAILMAN_ADMIN_USER: The username for the admin user to be created by default. MAILMAN_ADMIN_EMAIL: The email for the admin user to be created by default. I found this url http://Servername.domain.com/admin/login However I never set a password and here is no forget button, Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. How can I make sure my containers can send and receive mail?

4 years, 3 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

I agree that this is a Debian packaging issue and I agree with Mark that the underlying issue is the "sed:" error message. I have only had one reply to my Debian bug report. That reply told me what I had to do make apt-get usable again (since it was stuck on the mailman3 error) but that post did not address the "sed:" bug itself and nobody else has responded to the bug report. So, it looks like I am on my own as far as my Debian mailman3 installation is concerned. So, here is what I plan to do: 1) apt-get remove mailman3 mailman3-web mailman3-full. This should not remove any configuration data or database files but I will run "apt-get --dry-run remove" first just to make sure. 2) Install mailman3 using the venv and web instructions as suggested in this thread. I plan to use mysql (mariadb) since my database was originally implemented with mysql. 3) I will poach as much of the configuration data as I can find from my original Debian mailman3 installation. Thanks to everyone for your support and replys! Gordon

3 years, 9 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Steve Brown

Mark Sapiro wrote: > The senders are defined as addresses in the headers listed in > the configuration setting sender_headers, default = from, from_ > meaning envelope sender, reply-to and sender. See > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> This was very useful in explaining why MM3 (3.3.9) accepted the problem post and attributed it to my address, even when seeing the bounce+ address as a different sender. Thank you for taking the time to reply. > Are you saying that the bounce+... address ends up as a nonmember of > the list you are sending to. I don't think that should happen. Yes, that is what is happening, but only for messages from the steve@stevebrown address. I can send a screenshot and a .txt of the headers (of the message after sent back to me from MM3 and long!) but didn't see a way to do that on the archive page. Do I need to post from my gmail address? One clue I hadn't spotted before was a bodyhash_mismatch warning in the headers. No idea where that came from. Doesn't appear in emails from me to other addresses. Steve

1 year, 1 month

[MM3-users] Using as a forum

by tokyoprogressive＠mailbox.org

Our group of 30 plus people have the perennial problem in MM II of not checking previous messages before replying. A second problem is starting a new topic rather than responding to a message in the same topic, which makes searching even harder. I previously suggested a forum or something like Stack or Flock. People had no interest in a Word Press forum yet moan about the inefficiency of a list, also it is something new and involves leaving email. Stack and Flock make it hard to require all to be a member of all topics in their free versions. Then it occurred to me, the threaded view in Mailman III looks good and could help us nudge people back on topic. Am I being too optimistic. It is a closed group only open to people we approve. I would like to migrate to MM III but lack the technical skills to fo this? Anyone who could do this for a fee? We probably do not need to bring in the old topics. (I guess there us no way like a forum to limit the topics but at least we could keep things on track). Thanks Paul Arenson Japan Association for Language Teaching Sent from my iPhone

7 years, 2 months

[MM3-users] Re: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

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

6 years, 3 months

[MM3-users] Re: Change delivery_status in bulk

by Hitashi mancho

Thanks, Mark, for the reply. The mailman shell interaction worked for me. Thanks again for your help. On Fri, Apr 4, 2025 at 8:25 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/3/25 19:36, Hitashi mancho via Mailman-users wrote: > > > > Now, I am unable to locate any command or an API call through which I can > > change the delivery_status back to enabled for 1000+ users. > > > > Can you please guide me on how I can do this programmatically using cli > (I > > will write a bash script) or using an API call? > > > See the post at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a mailman shell interaction to do this. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to huhamails(a)gmail.com >

7 months

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

by Mark Sapiro

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

5 years, 3 months

[MM3-users] Re: Virtual alias + shell

by Mark Sapiro

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

2 years, 5 months

[MM3-users] Re: Changing subscription address

by Allan Hansen

Hi Steve, My comments below: On 3/15/21, 21:28 , "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >I don't have the Postorius knowledge to do this in a reasonable amount >of time to help your user immediately, but how about this design: < >In the 'Mailman Settings' screen, List-based Preferences' tab, You may mean the 'Subscriptions' tab. >currently each list has an active link at the list's posting address >(which links to a page with the same options carefully documented), a >plain text display of the subscribed address, and a row of options. >Suppose we > >1. Add a popup menu of addresses and attach it to the > displayed address for each subscription, >2. Add a 'select subscription' checkbox to each subscription. >3. Add an 'act on all selected subscriptions' fake subscription, > whose checkbox has the effect of select or deselect all. I guess > this should be at the top.[1] > >Does that seem like what you have in mind? Any other needs you want >to mention? (Suggestions for feature design are welcome, but "I do >this often and there's got to be a better way" is good too.) The above will work fine, Steve, as it will cover the special needs of people who have several addresses that they use for different lists. It's very flexible. For the other 99% of my users, something much simpler is needed: Under 'User profile for <name>', under the 'E-mail Addresses', add button to ensure that 'Primary E-mail' is used for all lists. Then they can 'Create account' if needed. 'Add E-mail'. 'Make Primary' the new e-mail. 'Use Primary For All Lists'. 'Remove' the old e-mail. This requires them to set up an account, but I'm OK with asking them to do that. And, indeed, new subscriptions should default to 'Use Primary.' That would be fine, but it can be even simpler, which I would much prefer: Instead of the 'Use Primary For All Lists', may I suggest a tool that lets me set all subscriptions to 'Use Primarry' where there either is no account or where the primary e-mail is already chosen as the subscription address (which together form the 99% I mentioned). In that case, the procedure becomes much easier for me to explain to them, and no new functionality needs to be added (although what you suggested is fine). 'Create account' If needed. 'Add E-mail'. 'Make Primary'. "Remove' old email. Is that possible now? Does a member have to have an account for me to set it up thus for them? Thank you for considering this, Steven. Yours, Allan

4 years, 7 months

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

by Stephen J. Turnbull

Wikinaut writes: > I fully understand. Need to look up how to smoothly backup the > mailman3 settings and list databases in order to make that move > with losing stuff... (kinda "mailman3 backup all" and mailman3 > restore all" :-) One piece of generic Python advice: don't mix OS packages and pip (except for Python itself). Always use a venv if you need to use pip for packages that aren't in your OS distro. (Of course it's possible to do so in many cases if you *really* know what you're doing, but it's almost never worth the pain.) All of the site configuration data should be in /etc/mailman3 (except for a few template files in $var_dir/templates), and all of the domain, list configuration, and archive data is in the RDBMS (usually PostgreSQL or MySQL). The RDMBS should be backed up regularly according to its procedures, but that's completely out of scope for Mailman.[1] The RDBMS should "just work" with exactly the same Mailman-side configuration as Debian.[2] As I think Odhiambo mentioned, the Mailman side of the site configuration also does not change (for example, the RDBMS URL and authentication). What you do want to change is the file system configuration. Except for /etc/mailman3, it should be completely different -- as with pip'ing packages, you don't want to share files across a local venv and the OS version of the same package. It just leads to pain. I think among the developers the preferred root = /opt/mailman (or /opt/mailman3) for Mailman's directory hierarchy. This will be populated with subdirectories when you run `mailman info` (or start Mailman) the first time. The directories relevant to configuration are all under $root/var, and you inform Mailman about this by setting `var_dir` in mailman.cfg. If there are other file and directory configurations in mailman.cfg, they need to changed from the Debian values (probably /var/lib/mailman3/...). You may do fine by simply deleting all other directory configurations and let Mailman decide where to put them relative to the `var_dir`, You will need to fix the setting for STATIC_ROOT (I think that's the name, if not search for "static") in settings.py, and maybe in mailman-web.cfg. While it's not necessary (and may be a little inconvenient), I recommend changing the root for Mailman's log files from the Debian value (probably /var/log/mailman3) to the Mailman default of $root/var/logs, and similarly for the Django logs in settings.py. Non-Mailman settings I think you will need to change the settings for your MTA (usually Postfix or Exim4) so that it will recognize Mailman lists and route them to Mailman correctly. There will probably be mailman-related files in /etc/$MTA/conf.d (or something like that). You can edit them directly, but I recommend changing the name (paranoia so that dpkg doesn't overwrite them). The only thing I can think of for the webserver (Apache?) is the location of the static directory. I think Debian uses uwsgi by default so you may need to adjust its configuration too. I think you need to fix logrotate's configuration in /etc/logrotate.d. Not sure how many mailman-related config files are in there. I think you mentioned systemd .service files. If so that doesn't make sense to me -- Debian should provide those. You need to make sure those are disabled or deleted so that Debian Mailman services don't start on reboot. This is automatic if you delete the Debian packages, of course, but not for any files you created yourself. Probably the Debian .service files will work, but you need to make sure they refer to the venv Mailman (using the full path to the `mailman` utility in the venv's bin directory will work, and similarly for `mailman-web`). systemd does not configure the /opt hierarchy in it search path by default. I put the mailman, qcluster, and gunicorn (if you use that instead of uwsgi) .service files in /usr/local/lib/systemd/system, and that works for me. Flotsam and jetsam If you have run Mailman with any success at all, you may find some stuff in Debian's $var_dir/queue/* directories or in its $var_dir/lists/* directories. The queue/* directories contain incoming messages at various stages of processing, and the lists/* directories contain files containing multiple messages that are scheduled to be sent out as digests. You can read the queue files with `mailman qfile /path/to/queue/file.pck`, and the digests are just text files. That way you can check if there's anything important in them. If not, you can just delete them. If there is, you can just copy them to the same place in the venv $var_dir as they were in Debian's $var_dir, but you may want to ask here first before doing that. It's best to let Mailman run until all the queues are cleared (except maybe bad and shunt, but if those have any files in them you need to intervene anyway). Afterword I'm sure this sounds complicated, but in fact it's a pretty short list. When you get there we'll help you. Footnotes: [1] But not for this list. You may as well ask here, somebody probably will tell you the basics quickly. But for troubleshooting, go the the RDBMS's own channels. [2] In fact, it is possible to keep the Debian installation, copy the the mailman.cfg somewhere, edit it, stop Debian Mailman, and start up the venv Mailman. I don't recommend this -- the point is that the venv and the databases are that isolated from the rest of the system.

2 years, 1 month

[MM3-users] Re: Extracting mailing list users

by Eggert Ehmke

Am Montag, 2. Januar 2023, 02:40:58 CET schrieb Mark Sapiro: > Understood, but there are a couple of things at work here. One is that > this particular task is a one-off the correct the result of a bug, but > perhaps more significantly, mailman developers (at least me) are > comfortable with `withlist` (it's been around since MM 2.1) and if I can > do it that way, it reduces the motivation to make something more > friendly for the normal admin. Unfortunately doing things easily that > way requires a lot of specialized knowledge of Mailman internals, so > most admins need help with it. Mark, I completely understand your situation as a core developer with limited time and lots of requests from all directions. Being a Python programmer myself, I would be happy with a consistent documentation of the relevant Python classes to be able to develop own applications. The isolated code snippets in the mm3 documentation are not too helpful. Such a documentation would possibly remove some of the workload you feel by constantly answering admin questions.´ When you look at the documentation of the Qt library you know what I mean. Thank you again for this great project! Cheers, Eggert

2 years, 10 months

[MM3-users] Re: how to administrate mailman3 in CLI ?

by testeur

Hi, I try to find documentation and examples to manage mailman3 with "mailman shell". By example, when i tryied just to define global configuration for all users, like in this example ( https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ), but it changes nothing : |# mailman shell -l testlist(a)domain.tld | ||>>> from mailman.interfaces.action import Action >>> for mbr in m.members.members: mbr.moderation_action = Action.defer |||commit()| |||>>> from mailman.interfaces.action import Action |||||||>>> english = getUtility(ILanguageManager).get('en')| >>> for mbr in m.members.members: || mbr.preferences.acknowledge_posts = False mbr.preferences.delivery_mode = DeliveryMode.regular mbr.preferences.delivery_status = DeliveryStatus.enabled mbr.preferences.hide_address = False mbr.preferences.preferred_language = english mbr.preferences.receive_list_copy = False mbr.preferences.receive_own_postings = True|commit()|| Before the shell command, the web interface was with an other language (i tested with italian one) and other options preferences, but after the shell command, after a web interface refresh, it doesn't change. am i wrong somewhere ? Regards, On 16/09/2023 23:05, Stephen J. Turnbull wrote: > Hi > > testeur via Mailman-users writes: > > > I have installed mailman3 and i want to administrate it with rest > > api, > > Do you really mean REST API, or do you mean CLI? > > > i tryied with curl to manage it, i can see if there is a pending > > message with : > > > > curl --user restadmin:restpass > >http://localhost:8001/3.1/lists/ml@domain.tld/held/count|| python3 -m > > json.tool| > > This is a lot easier using "mailman shell" if you want to use CLI, or > a Python program using mailmanclient if you really want to use the > REST API for some reason. > > This is explained here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > but it's likely to be pretty rough going for you because it's really > oriented to programmers studying to be Mailman developers, not for > admins. > > > but how to delete all held messages ? is it possible in one time ? > > No, you need to fetch the list and then loop over the messages. > > > And how to select a specific message to discard /accept / defer ? > > > > do i have to use a POST ? > > This is all explained here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Steve > > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-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/mess… > > This message sent totesteur(a)starinux.org

2 years, 1 month

[MM3-users] Basic settings for a discussion list

by paul＠arenson.org

Over the last 20 hours I have been trying to figure out setup for list members to sign up. One person has kindly helped out, though I am still unsure of the difference between the several signups. That thread is here and I welcome more advice. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… But it occurs to me that my problem is that I have not actually configured my list. So this thread is for help on that. I have found a guide for general users here: http://docs.mailman3.org/en/latest/userguide.html But I have only found a highly technical guide for administrators here: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… It is written for coders and I am looking for a guide similar to the one for users. It seems not to exist yet. WHAT I WANT Discussion only list. Ideally anyone who signs up via the various ways should be able to get the archives and post via email and the interface if they want. The list should be closed to others. In the absence of any guide, all I can do is cross check with you guys and hope I am on the right track. I am non technical, although I managed a Mailman 2 list without difficulty. 1) FIRST ANOMALY Under https://list.tokyoprogressive.org/postorius/accounts/subscriptions/ I see myself twice: List Name Subscription Address Delivery Mode Role discuss.list.tokyoprogressive.org paul(a)tokyoprogressive.org None member discuss.list.tokyoprogressive.org paul(a)tokyoprogressive.org regular owner Is this correct? I added My name in one field somewhere and this is the result. I even got a welcome message. I think it is because I subscribed to my own list.If this was not necessary, what should I do? Global based preferences are listed. Address and email based ones are not showing either enabled or disabled. 2) MANAGE LISTS For myself I have done the following in my MAILING LIST SETTINGS Subscribe to this list My email and name (Maybe that is why i am listed twice) Now I see 3) Users For now only me- I am listed as member and owner. There will be no other moderators or owners I have no idea what a non member is (if they register aren't they a member?) 4) Templates This is showing nothing at this point. Before it was. I am not sure what i did to stop it from showing. Perhaps because I made it a private list? 5) Settings a) List identity I have it set for NOT SHOWING on the Index page because I will link to it from my news magazine website as a way to comment on articles. Is this ok? Other data will be filled in later. I think I am confusing this with private list. I also will have no other list. b) AUTO RESPOND LIST OWNER-- I added a short note thanking people. Respond and Continue Processing c) AUTO RESPOND POSTER--Your message has been been received. If you are a member, it should be posted soon. Respond and Continue Processing d) AUTO RESPOND REQUESTS--No auto response OTHER THINGS DEFAULT e) URL WELCOME MESSAGE--NOT SURE. I want people to subscribe themselves but I also have 500 people from another list from DADA I will import. I want them automatically be able to post. Is it possible? If so, I hope to add them manually. DO I compose a text on my website and welcome them by adding the URL, or enter it in my list? f) NOTIFY OF MEMBERSHIP CHANGES--Yes g) ALTER MESSAGES ---I have left most things as they are. However, as this is a discussion list, I want replies ONLY to go to the list. I chose that. h) DMARC --I have left as is i) DIGEST--I have left as is 6) MASS OPERATIONS--I have left as is 7) BAN--left as is 8) MESSAGE ACCEPTANCE--I have left as is 9) HEADER FILTERS--left as is 10) ARCHIVES--Private Archives (Maybe this is why templates do not show???) 11) SUBSCRIPTION POLICY--MODERATE-- I intend to send them an email to confirm their reasons for subscribing to avoid spammers. LAST THING. My Gravity does not work. I edited it online as per instructions but it does not appear. That is all I can think of. Thanks in advance. paul

6 years, 2 months

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

by Mark Sapiro

On 2/23/21 9:40 PM, Morris Jones wrote: > I typo'd some full names in a mailing list. I want to correct them ... > > I can't see a way to do that in the Member Options, so I thought I'd try > "remove" and re-add, either from the command line or the UI. > > But the name gets readded with the typo intact. :( > > Is there a way to fix it without writing SQL? You can do it with mailman shell. The basic issue is the display name is a property of the user or the user's address, which ever is subscribed to the list. When you add a previously unknown user to a list, Mailman creates these user and address records, but they belong to the user, not the list. There are some threads around this at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and a somewhat protracted one at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

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

by Gerald Vogt

Hi, On 04.11.24 02:06, Mark Sapiro wrote: > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > We should probably cover this in the docs, but for /etc/mailman3, you > should do > ``` > sudo mkdir /etc/mailman3 > sudo chown mailman:mailman /etc/mailman3 > sudo chmod 755 /etc/mailman3 > ``` > Then you can create all the subordinate files as the mailman user. For > other things like the systemd service and the postfix and web server > configs, you need to do them as root (via sudo). is it really necessary that the mailman user can write that directory? For most services, directories and files in /etc/ may be readable for the service but usually not writable as you don't want the service itself change it's core configuration. 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. Regards, Gerald

1 year

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Mark Sapiro

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

3 years, 10 months

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

On 5/1/22 21:50, Mark Sapiro wrote: First, thanks a lot Mark for your guidance. >> >> HINT: Configure the DEFAULT_AUTO_FIELD setting or the >> SocialAccountConfig.default_auto_field attribute to point to a >> subclass of AutoField, e.g. 'django.db.models.BigAutoField'. > > This is from Django >=3.2 can be fixed by adding > > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > > to your settings. This has been done in HyperKitty's > example_project/settings.py for the not yet released 1.3.6 version. > > These warnings are only warnings, they aren't fatal. I thought so. I've added it in the settings.py file. In the last part of your suggestions you wrote: "I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0" But this is exactly what made me fall in this mess: I realized that the versions of hiperkitty and mailman-hiperkitty in that server were outdated.. and I tried update them separately, forgetting the saying "if it works, don't touch it" (si funciona, no lo toques). In my first message I listed the versions of all the items, but to refresh it, as they are now: (from pip list) ... gunicorn 20.1.0 HyperKitty 1.3.5 ... mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 ... mistune 2.0.1 ... mod-wsgi 4.7.1 ... postorius 1.3.6 (end of pip list) I did the upgrade of all of it. The "migration" process output the same warning as before about to doing a "makemigration" (I did not this time) Thinking that the problem in the "migrate" and "makemigration" process could be that I touched the mistune/scanner.py to add escape and escape_html imports, I deleted that two lines. Then all went bad: the postorius list page didn't show anymore. The error.log form the apache server shows django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' from 'mistune.scanner' (/usr/local/lib/python3.7/site-packages/mistune/scanner.py) So I tried to put them back (but I had problems with, I believe, the __pychache__). I had to reinstall mistune and write back this lines that I found in a previous thread from William Oliver last 12/28/21 I've finally came back to administering the lists via postorius. I created a new list to do the tests without disturbing the rest. And now I am at the exact same point: No message is archived and the log shows: ERROR 2022-01-06 12:38:45,574 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,586 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,801 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,832 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,847 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,867 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:46,075 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. As this server has very low traffic, the emails are distributing well, and the only thing that fails is the archiving of new messages, I will wait until a more complete upgrading process is needed for mailman, postorius or hiperkitty. Thanks, again, for your support. P.S.: One thing that make me curious is the "mistune" package... I don't see it installed in the other servers that are working flawlessly with mailman3. > > ... >> Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows >> the same warning listed before and some new errors: >> >> *-*-*-*-*-*-* >> >> Migrations for 'postorius': >> /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py >> >> - Alter field name on emailtemplate >> Traceback (most recent call last): >> File "manage.py", line 10, in <module> >> execute_from_command_line(sys.argv) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", >> line 419, in execute_from_command_line >> utility.execute() >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", >> line 413, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 354, in run_from_argv >> self.execute(*args, **cmd_options) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 398, in execute >> output = self.handle(*args, **options) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 89, in wrapped >> res = handle_func(*args, **kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", >> line 190, in handle >> self.write_migration_files(changes) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", >> line 228, in write_migration_files >> with open(writer.path, "w", encoding='utf-8') as fh: >> PermissionError: [Errno 13] Permission denied: >> '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' >> >> >> *-*-*-*-*-*-* >> >> The file >> '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' >> does not exist at all > > > makemigrations is trying to create that migration and you don't have > permission to create the file. I don't know why it's trying to do > that. Postorius 1.3.6 has migrations through > 0016_auto_20210810_2157.py and shouldn't need more. To you have > modificationd to Postorius? > > >> Despite the error, I did a 'su -m mailman3 -c "python3 manage.py >> compress"' and the subsequent "django-admin compilemessages" in >> >> /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and >> ../django_mailman3 >> >> And the log continues showing the same error when trying archive a >> new message. >> >> ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > > > These messages come from some HyperKitty version between commit > b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 > -0700 and > commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 > 2021 +0000 > > They do not come from HyperKitty 1.3.5 but from something later than > 1.3.4 which makes be think your mailman-hyperkitty version is not > 1.2.0 either. > > I suggest you do > > pip install --upgrade hyperkitty mailman-hyperkitty > > and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: spanish localization

by Mark Sapiro

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

4 years, 8 months

[MM3-users] Issues with international characters (replaced by ?) when mail is send as text/html

by Michal Soltys

Hi, I have noticed that any mail send with text/html, e.g. with following headers: Content-Language: en-US-large Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit is slightly transformed by mailman3 - the body is put into its own part, but all the international letters are replaced by question marks. Having searched the list I tried: 1) adding following to mailman.cfg: [language.master] description: English (USA) charset: utf-8 enabled: yes [language.en] description: English (USA) utf8 charset: utf-8 enabled: yes 2) changing preferred language of a mailing list to something else via shell, e.g.: m.preferred_language = 'pl' 3) changed default_language to 'pl' in mailman.cfg 4) Ensured all relevant glibc locales are generated (not sure if that matters though in this case) None of this seems to have any positive result - all mails, whether under 'pl' or 'en' setting still get all non-ascii chars replaced with question marks (in html case, probably(?) in any case where it becomes multipart). Any ideas what to do so html mails are passed without filtering out their characters ? Do I have to recreate all mailing lists under new [language.en/master] settings ?

3 years, 9 months

[MM3-users] Re: MM3 not processing some mails from specific user

by Stephen J. Turnbull

Stefan Bauer writes: > thank you. Funny. All problematic mails are in the shunt-queue from one > specific user. That's good news (given that things aren't working), something in there will show us why. > the mailman-logs did not log anything helpful. I thought they should ... not your problem, I'll check and let you know if there's someplace else you should look. > What do you recommend to find the needle in the haystack? I mean, what can > cause mailman to fail processing? Most frequently the issue is a non-ASCII character in the header. A frequent cause is spam filters and virus checkers quoting non-ASCII text in their reports in the header. Nonconforming dates can cause problems for some applications (specifically those that work with list archives), but I don't think they should cause non-delivery, and the date in the sample message is conformant. You could try running "mailman unshunt", which may produce a helpful error message if for some reason it can't do so. Also check for logs that were updated at that time, which might identify a log with some useful information. Steve

3 years, 2 months

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

by Mark Sapiro

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

4 years, 9 months

[MM3-users] Re: MIME Digests with posts and index inline likewise Plain Text Digests

by Mark Sapiro

On 1/18/19 5:11 AM, Henrik Rasmussen wrote: > Please correct me if I'm wrong, but as I understand, Mailman attaches posts in a MIME Digest mail intead of inline in the digest mail itself, like Plain Text Digests does. Some mail readers like Gmail eventually displays attachments inline anyway, but readers like Outlook do not. Also the digest index seems to be posted as an attachment in MIME Digests. > > Would it be possible for Mailman to send both posts and index inline in the MIME digest? The format of the MIME digest is specified by RFC 2046 which defines the multipart/digest format in section 5.1.5. This defines the MIME digest as a multipart/digest message part containing the individual messages as message/rfc822 sub-parts. It also says (after spelling corrections - ErrataID: 510): Note: Though it is possible to specify a Content-Type value for a body part in a digest which is other than "message/rfc822", such as a "text/plain" part containing a description of the material in the digest, actually doing so is undesirable. The "multipart/digest" Content-Type is intended to be used to send collections of messages. If a "text/plain" part is needed, it should be included as a separate part of a "multipart/mixed" message. The MIME format digest Mailman produces has the structure multipart/mixed text/plain the "masthead" text/plain (only if a digest header) the digest header text/plain the table of contents multipart/digest message/rfc822 the first message message/rfc822 the next message ... message/rfc822 the last message text/plain (only if a digest footer) the digest footer The only change that could be made while keeping the digest compliant would be to combine the masthead, digest header if any and table of contents in a single text/plain part. While this might solve the the issue of the table of contents being an "attachment" in some MUA's rendering, it won't address the larger issue of the messages being rendered as attachments. As you note, Gmail's web mail does an OK job of rendering the MIME digest as do other mainstream MUAs such as Thunderbird. The real solution is for those people who insist on using non-compliant MUAs to subscribe to the plain format digest. The whole point here is if you want a digest which has everything in line, that's what the plain text digest is. If you want a digest which maintains the original structure of the messages without flattening them to plain text, the messages have to be separate message/rfc822 parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] moving lists to another server

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > I have both my mailman lists and django config in postgres > databases. These are Mailman 3 lists? What Django config? Do you mean Postorius and HyperKitty? Do you intend to use Postorius and HyperKitty on the new server? > If I want to move my lists to another server that is running > mailman 3, aside from copying the databases to the other server, Do you mean the other server is already actively distributing Mailman list traffic, managing users and archives? Or is it fresh instance? > what other things (perhaps all files under /var/lib/mailman3?, etc) > would I need to bring over to the other server? That's going to vary depending on the way your existing server is set up. A Mailman 3 instance is a complex system of cooperating applications. Assuming you have not patched or added any Python code, typical configuration and customizations include 1. Your webserver (Apache, nginx are most common) needs configuration to handle WSGI applications and may need modules enabled or installed for the WSGI server. This is usually installed as an OS distro package, and the configurations will live in /etc/apache2 or similar for another webserver. Depending on other content served by the two hosts you may have to edit the configuration on the new host rather than copy it from the old one. 2. The WSGI server is typically a separate application, although there is an Apache module for this. Gunicorn is a Python application usually installed via pip. I like to keep its Django configuration, which I call gunicorn.conf.py, in /etc/mailman3. (Mailman core also uses gunicorn, but that is transparent to you, it should not need custom configuration.) uwsgi is a C or C++ application normally supplied as a distro package. Don't know where it keeps its config files but since it's a distro package my first guess is /etc/uwsgi. 3. Your MTA, usually Postfix or Exim4, maybe Sendmail or qmail needs to be configured to route mail to Mailman, and apply any milters, signatures, and perhaps anti-yahoo configurations such as ARC. 4. Your database server, usually PostgreSQL or MySQL. 5. Mailman core has a single configuration file mailman.cfg, which I keep in /etc/mailman3. It also has a crontab, which in Debian- derived systems typically lives in the file /etc/cron.d/mailman3. Note that this could be implmented as a systemd timer, but I don't know if any distros do that. 6. Django, Postorius, and HyperKitty together constitute the mailman-web subsystem. I strongly recommend you use the mailmanweb Python package to manage Django and its applications. In any case I am not familiar with other organizations of those packages, so I'm going to assume it. If you are not using mailmanweb, you will need to be careful because most subpackages in the Django subsystem name their configuration files settings.py, urls.py, and views.py just like top-level, and distinguish them by using Python's attribute notation (eg, postorius.urls). a. Django application configuration for Postorius and HyperKitty goes in settings.py, which I put in /etc/mailman3. b. Django site configuration for Postorius and HyperKitty goes in urls.py (the routing configuration mapping URLs to views) and views.py (mapping views to Python code). I put these in /etc/mailmn3. c. Full-text indexing for HyperKitty. Default is Whoosh (a Python application) whose configuration goes in Django's settings.py. I prefer Xapian, which requires a separate application (Debian and Ubuntu have packages), but the needed configuration can be done in the top-level settings.py. 7. Template customization. If you have any customized templates for Mailman's email or Django's views, you'll need to copy and move them too. I haven't customized email, but Django's page templates can be kept separately with a path variable set in settings.py. I put them in a hierarchy under /etc/mailman3/templates. Maybe Mailman core has a similar setting? 8. Transient files. Aside from code and configuration, everything in Django is in the RDBMS, there are be no random files strewn around as far as I know. Mailman core is another matter. You can hope that all Mailman transient files are in its "var" hierarchy. $var_dir (the setting in mailman.cfg or inherited from schema.cfg) is the root of this hierarchy. I set var_dir=/opt/mailman/var, I think Mark may use var_dir=/opt/mailman/mm/var. I would guess that FHS-conformant distros would likely use var_dir=/var/lib/mailman3. a. The queue directories $var_dir/queue/* should be empty. Shut down the incoming mail and let mailman run until it's clear. (Normally takes < 5 seconds.) The exceptions are the shunt and bad queues, which are messages that Mailman doesn't know what to do with. With the venv active, run "mailman unshunt" to attempt to clear the shunt queue. Move anything that's left in shunt as well as any .bak or .tmp files into the bad queue for later treatment. These can be copied to the bad queue in the new instance. Use "mailman qfile <file>" to examine them to see if they can be deleted. b. I think the only stuff that ends up in the $var_dir/lists/* directories are digests being built for later distribution. Use the usual tools to send them off or copy them over to the new instance. c. There should be nothing in $var_dir/archives/hyperkitty/spool, which is temporary storage for messages to be archived. That is, it should get cleared up by the few seconds while incoming mail is stopped and outgoing messages are being processed. If there's anything still there, stash it away for later examination using "mailman qfile". (Don't put it in queue/bad or queue/archive though, this is a different process from the normal pipeline.) I think that's about it. Steve

1 year, 11 months

[MM3-users] Re: Disabled by bounce

by Stephen J. Turnbull

Jan Eden via Mailman-users writes: > To distribute messages with valid DKIM signatures, I set > > remove_dkim_headers: yes > > in /etc/mailman3/mailman.cf That should be "mailman.cfg" for a standard installation, and it may not be in "/etc/mailman3" in a shared hosting situation. Do you have evidence that removing DKIM headers helps you get mail delivered? (Not adding your own, IMO you should do that regardless of whether you strip existing ones, but removing originals.) The DKIM spec says that you shouldn't, and that consumers should treat invalid signatures no differently from missing signatures. I haven't run into a "public" host that treats an invalid signature as a problem in quite a while. On the other hand, I know of at least one postmaster who is experimenting with simple "repairs" (namely, stripping list tags and serial numbers from Subject and unwrapping simple MIME structure for Mailman lists at least -- the case where Mailman wraps the original message in multipart/mixed and adds a text/plain part to the message with the footer in it) and checking the original DKIM signature and from alignment on the "repaired" message. I don't know if they're still working on that. Steve

2 years, 8 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 00:16, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:03 AM, Odhiambo Washington wrote: > > > > Thank you for clarifying. > > So once I have a venv created, the services will just run as long as the > > startup scripts are running even when I'm logged out of the system? > > > As long as the startup scripts actually reference things in the venv. > > If you look at the samples in the Recommended Configuration section at > <https://wiki.list.org/x/17891998> for > > /opt/mailman/mm/bin/django-admin (sample) Script to run Django > management commands. > > /opt/mailman/mm/bin/mailman (sample) Script to run mailman commands. > > and > > /opt/mailman/mm/bin/gunicorn (sample) Script to start Gunicorn. > > You will see they all do things like activate the venv or run a command > from venv/bin. > > > Now that has clarified the matter for me. That even when I am logged out, the scripts do the neccessary to activate the venv to run things. I hadn't looked at the scripts at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 9 months

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 4:09 PM, Mark Sapiro wrote: > 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 I do > 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 It is. > > Is there some firewall issue blocking access to the port even from > localhost? Let me describe the problem a little better. Mail delivery from postfix to mailman works most of the time. However in the past week or so, lmtp starts refusing connections via postfix about once a day. I have port 8024 open in the firewall (UFW). There are no errors in the smtp.log file. I think restarting Mailman core seems to get things running again. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 4 months

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

by John Covici

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. Thanks. On Sun, 14 Mar 2021 10:29:20 -0400, Stephen J. Turnbull wrote: > > John Covici writes: > > > Hi. So, I have sendmail as my mta and I want mailman to use it. So > > far, I have a local delivery agent able to send on port 8024. So, > > what do I have to tell mailman to use sendmail and listen on port 8024 > > and to send on port 25? > > As Mark wrote in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, > > > For sendmail, see > > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> > > Regards, > > _______________________________________________ > 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, 7 months

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

by Brian Carpenter

On 2/17/21 6:52 AM, Andreas Barth wrote: > Just from the top of my head, for example I want to differentiate > between private, member and public lists. So if a member logs in, they > see more lists than a non-member. This is currently not possible, not > too big a deal (all member lists are currently configured as private) > but of course would be nice. Also archiv access should be aligned with > these permissions. What I have done with Affinity is design everything around roles. Roles are List Owner, Moderator, and List Member. So when a registered user logs in they will see: All their lists that they have a role in and an icon assigned to each role that they play. Those lists are shown at top. Below their lists associations, public lists are shown. These they do not have a associations with for the logged in user. Here is an image in what I am referring to: https://www.mailmanhost.com/wp-content/uploads/2021/02/Screenshot_2021-02-1… Is the above image what you are thinking about? If it is then I do think that is possible with Postorius with some customization. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: MM3 not processing some mails from specific user

by Stefan Bauer

Hi Stephen, thank you. Funny. All problematic mails are in the shunt-queue from one specific user. the mailman-logs did not log anything helpful. What do you recommend to find the needle in the haystack? I mean, what can cause mailman to fail processing? Stefan Am Do., 11. Aug. 2022 um 14:30 Uhr schrieb Stephen J. Turnbull < stephenjturnbull(a)gmail.com>: > Stefan Bauer writes: > > > Any idea what that could be? Here are some logs: > > I don't see anything in either the MTA log or the sample message. > However the sample message is incomplete, I assume the rest is an HTML > version of the plain text MIME part. It's unlikely but possible that > there is a defect in the rest of the message. > > Have you checked the Mailman logs? Typically they end up either in > /var/log/mailman or /var/lib/mailman/log (or variations on those > appropriate for your installation) > > Also, check the shunt queue, typically in > /var/lib/mailman/queue/shunt. This is where Mailman puts messages > that contain errors that didn't prevent delivery but make processing > impossible. > > Steve > >

3 years, 2 months

[MM3-users] Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Jan Eden

On 2025-06-16 17:29, Mark Sapiro wrote: > On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. > > Do you have > ``` > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > ``` > in your django settings? > > What releases of HyperKitty, Postorius and Django-Mailman3 are you running? > Current releases do not have any minutely jobs. I did have the same issue about a month ago[1] with the current versions of the above components, and these are the cronjobs I installed according to the docs[2]: @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…

4 months, 2 weeks

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

by Brian Carpenter

On 2/25/21 10:35 PM, Abhilash Raj wrote: > I think it is okay to be pick up a specific configuration and provide a > guide to installation keeping that as the target technology. As it happens > to be, the official doc uses the same set, Nginx, Postfix and PostgSQL. > > https://docs.mailman3.org/en/latest/install/virtualenv.html Thank you for pointing the above out. I will keep track of the URLs you provided in this thread and I am willing to also assist to try to make sure such links are propagated via search engine results. > I don't see anything very specific to Debian in the doc except the package > names and I think they are similar enough in Debian derivative distros that > we can write up that assumption up front in the top. > > Given that most of the installation is based off on pip, I don't think there is > going to be a *lot* of deviation for even RHEL/Fedora based distros when it > comes to Mailman itself. Some minute deviations could occur with the > behavior of certain commands, like `nano` doesn't exist, but I still expect > 95% of the doc to be the same, except obviously the package names. I agree. One of my goals was to make it easy for Mailman 3 adopters to use a different installation method other than a repo since distro packages tend to install older versions of Mailman 3 core, Postorius, and Hyperkitty. At this stage of Mailman 3 development, these new versions bring a LOT of improvements to the Mailman 3 user. I am also willing to start testing out my installation method on other distros and document the differences. If you are willing to help me, I have no problem posting installation instructions and tips to Mailman 3's official documentation. I am also more than willing to keep such documentation up to date. I am always being called upon to install Mailman 3 for someone, so I seem to be on the front-line when it comes to "surprises" such as the issue with the cryptography module. That puts me in a good position to update documentation simply because I need to know such things for the next install. > I am not that well versed in SEO, but the official website https://list.org > does point to it. Maybe not prominently enough for new users to discover? > I'll see if we can make the discovery of docs.mailman3.org better. I think the issue I found was running into outdated documentation for older versions of Mailman 3. Even doing a search for an up to date changelog or release notes are problematic. Again, I am also willing to help out with trying to get such vital pieces of information showing up prominently in search results. > I guess it is fine to be opinionated about choosing the technologies but > yet provide pointers to help people using other technologies. > > Right now, I do that using "Hints" and "Notes" and "See also" banners > through out the documentation to point to different pages where they > can lookup setup for other technologies. For example, how to setup > MySQL if official doc recommends Postgres. Are there still any outstanding issues with using MySQL? I know I ran into some when I tried to use MySQL and chose to go with PostgreSQL (which I am so glad I did). I still recall even seeing some recent issues brought to this list for someone using MySQL. I know MySQL is very popular for websites so I do believe the momentum for someone to set up a Mailman 3 server is to go with MySQL. Perhaps just putting up some heads up warnings (here there be dragons!) IF there are still issues out in the wild for those wanting to use MySQL with Mailman 3. Personally I will always steer clients to PostgreSQL when I get a chance. My own documentation reflects that bias. > Gitlab has a fairly good experience editing REsT files and you don't > necessarily > have to do much outside of a Web Browser actually. It lets you preview before > saving like wiki.list.org and you can submit it for review and merging into > main repo. > > Would you be more willing to contribute to official documentation if we > documented the Gitlab contribution process better? Absolutely. My current installation documentation was the result of a certain beautiful Mailman developer who I won't name (just protecting your privacy Mark!) providing me assistance when I decided to go with the certain installation direction. So if you scratch my back (i.e. teach me Master for I am your student!) then I will scratch yours. > Because we haven't yet gotten to updating those in the official docs, > unfortunately. And there are more things missing like Fulltext search (Xapian > recommended) and more of the Email setup like SPF and DKIM. Very much > aligned with your plans, which is why I suggested contributing updates > to docs.mailman3.org instead :) Well show me how to update the documentation and I will certainly take care of those things. I am also now comfortable in getting OpenDKIM working with Mailman 3 so I can also provide documentation there as well. I have done Xapian installations for clients but unfortunately did not document my methods so I will need to work on that. How do you feel about documentation for the use of Elasticsearch and Solr? Remember, I was a Mailman 2 host for years using cPanel. cPanel took the thinking of out a lot of things when it came to Mailman 2 hosting and I don't have that crutch anymore with Mailman 3. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

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

by Henrik Rasmussen

I used Docker to installed Mailman 3. The top header of the web interface says "Example.Com" while linking to the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a post[1], Mark Sapiro referred to the template system in Mailman 3 by pointing out that "a custom template can be put in var/templates/site/en/welcome.txt or var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> or var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> where var is Mailman's configured var_dir". I believe this refers to the mail templates. 1) Where do I change the similar template system, for the web interface, without breaking a laver upgrade? 2) How do I change the site name in the top of the web interface on Mailman 3 to my subside and ? [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… The Mailman command in Mailman Core doesn't seem to have a command for listing the accounts users have created by using Sign up in the web interface, so I believe that accounts may be created in the webinterface. Is there similar commands for the web interface like the mailman commands for the Mailman core? Regards, Henrik Rasmussen

8 years, 2 months

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

by Mark Sapiro

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

3 years, 9 months

[MM3-users] Re: Archives with encoding characters

by Seth Seeger

I should add that they are both on Plain Text Digests. (People seemed to be unhappy with MIME digests, because they had to double click on each email to open it up. You couldn't just scroll through a long email.) Seth On Wed, Mar 4, 2020, at 4:55 PM, Seth Seeger wrote: > Hello everyone, > > I have a few (but not all) members complaining that their digests are > full of coded characters. Two examples below were forwarded to me: > > > What I ended up doing was creating 2 "practice lines" in the centre of=20 > > our big teaching circle (I always teach new figures in a big circle) -=20 > > which each had 3 people set up in a line with generous space between,=20 > > and first=C2=A0 I walked through one of those lines myself starting first= > > =20 > > and > > > Robins pass Right=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Larks Loop L= > > eft > > What is the cause? Is there anything I can do about it? > > Thanks, > Seth

5 years, 8 months

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

by Mark Sapiro

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

1 year, 5 months

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

by tlhackque

Notes inline. On 12-Feb-19 11:09, Stephen J. Turnbull wrote: > tlhackque writes: > > > I believe that for threading to work more or less reliably, the > > thing to do is to look at the 'References' header. > > > > That should give you the thread in order, and allow any message > > received out of sequence to be put in the proper location in your > > display. > > This is more difficult than it seems, since References is not defined > for mail as far as I know (it's a netnews concept originally, and RFC > 5337 is a netnews-specific RFC). Not sure why you believe this. RFC2822 3.6.4 defines References for e-mail. See https://tools.ietf.org/html/rfc2822#page-25 As I wrote in later post, the message-ID syntactically requires the <>. (just one set). msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS] Look at that for the full syntax and reference. > Although it is adopted by most mail > clients, there's no guarantee of strict conformance. I agree that conformance has traditionally been hit-or-miss with almost everything about e-mail. Sigh. I also agree that life is hard. There have been clients that use the same message-id for all messages, and it's a long-standing problem. E.g. See https://cr.yp.to/immhf/thread.html Not only do you not have a guarantee of ever getting all links, you don't have a guarantee of the order in which they arrive. So one can have gaps ( parent, reply2-delayed, reply 3 references reply 2 and parent, reply 2 might arrive - or note.) You also can have a reply that references 2 or more branches. E.g. /--R0 p/--r1 \ \ --r2 / And a reply (r3) comes that references r1 AND r2 (and the parent) - which you probably want to show as a descendant of both r1 AND r2. R4 replies to r2 - but that's also an implicit response to r1. Once you's sorted that out, r5 comes along that references R0, r4, and P. 2822 does say: Therefore, trying to form a "References:" field for a reply that has multiple parents is discouraged and how to do so is not defined in this document. But programmers are rarely discouraged - with GUIs, it's pretty easy to intuit that one might like to check the boxes on several branches of a thread and respond "Of course, you're all right - see my cat photo". :-) 5537 tries to make life easier - until you get to: If the resulting References header field would, after unfolding, exceed 998 characters in length (including its field name but not the final CRLF), it MUST be trimmed (and otherwise MAY be trimmed). Trimming means removing any number of message identifiers from its content, except that the first message identifier and the last two MUST NOT be removed. So, even if you get all the messages, you don't necessarily get all the references that you need. I'm sure glad that I'm not working on Hyperkitty! But I'm not holding my breath for when MM3 is complete enough to adopt in my environment. Yes, "In-Reply-To" is more often present (likely because it's modestly simpler for RFC-readers to understand - it's one thing, not a list.) It's less expressive (hence, informative.) One can try to use it as a fallback when no References is present (and that's what 2822 implies). The whole undertaking in the real world is an example of the halting problem. Or Parkinson's Law. The best one can do is to come up with a "good enough" approximation in the available time, and tinker with/improve it until bored. It's likely to be a bunch of heuristics. And if you're not careful, throw in the Peter principle :-( > In mail, > In-Reply-To is more reliably present, but of course asynchronicity > means you have no guarantee of a complete set of all links. Even if > all clients conform to the netnews RFC, you still need to create the > full tree (full conformance to RFC 5537 means it will be a tree), and > break ties between branches in some arbitrary way to create a total > order. It's worse if you *don't* have conformance from all clients: > you can get a DAG or even something that isn't even a DAG. So, even > today, you can't assume a well-behaved ancestry graph. > > > 'References' should be a superset of Reply-To (which is at most 1 > > Message-ID), so you only need Reply-To if there is no References - or to > > handle a client that doesn't obey the RFCs. > > I suppose HyperKitty uses References (it works for messages that have > proper Message-IDs ;-), but I don't know what algorithm it uses. > Might be worth looking into, as well as considering a more Postelian > parsing of Message-IDs. Specifically, take the field body, unfold it, > strip leading and trailing whitespace and leading "<" and trailing > ">", and whatever's left is the message ID. > > Alternatively, strip everything that's not atext or "@" (including > inside the purported Message-ID). See my other post. The left and right halves can, besides being atoms, be non-folding quotes or literals. So you have to handle that. Although I have recently seen e-mail clients that are confused when you do it. (Ran into that generating content-id for multipart/related. Yes, MIME makes plain e-mail look straightforward.) Although it has a defined syntax, the semantics are that message-id is an opaque globally-unique identifier. Attempting to parse it as anything but '<[^>]+>' is likely to be a mistake. (On receipt; generating is the other side of Postel-correctness... I commend RFC 2468 to anyone who hasn't read it.) I doubt 'striping' is worth doing - when an message-id is present, I've almost always seen it include the required <>. Until yesterday's hyperkitty bug, I've never seen <<>>. I've rarely seen the <> missing - but I'd consider that a warning that the message format is suspect. As in this case. My suggestion is that if you can't find a message-ID, keep the message in an "unthreaded" bucket. If you sort that by subject (omitting "[listtag]" and "Re:*" (case insensitive, and in multiple languages) then by date, you probably have a useful presentation. And a list of MUAs that need bug reports :-) Yes, althought 2822 says that "Re:" is the proper introducer in the subject of a reply, RE: is common, and I've seen it (incorrectly) translated in the headers.) As I said, "life is hard". > This won't break any RFC 5537-valid > Message-IDs, but might identify two different, nonconforming > Message-IDs as the same (too bad if they can't take a joke!), or > identify a nonconforming message with a conforming one (<sad_emoji />. > > Thoughts? > > 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/

6 years, 8 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:56 PM, paul(a)arenson.org wrote: > Thank you. When you say OPTIONAL, do you mean it is up to me (in the > web interface or email client) to remove them as I have done below? Right, it totally depends on how one is replying. In the web interface, since you already seem to be using it, there is a button which adds the quoted text if needed. For email clients, the behavior varies from one client to other and there are tons of them. Some will quote by default, some won't. Then, it also depends on the users, since even if it is not the default, they can optionally add quotes. > > Abhilash Raj wrote: > > On Wed, Sep 4, 2019, at 5:41 PM, paul@-------- wrote: > > > Hi. I thought I had the settings right, but I do not > > > see one to get > > Thanks. > _______________________________________________ > 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, 2 months

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

by Mark Sapiro

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

5 years, 4 months

[MM3-users] Re: If you delete a list but not the HyperKitty archive

by Philip Colmer

On Tue, 4 Jan 2022 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/4/22 6:45 AM, Philip Colmer wrote: > > > > So ... should the archive be deleted when the list is deleted and it is a > > bug that it isn't? Or is it expected that access to the archive is > "frozen" > > once a list is deleted? > > > It is often desired to have a public archive available after the > corresponding list has been deleted. Even for a private archive, it may > be desirable for site admins to have access. Furthermore, a list might > not even have a HyperKitty archive in the first place. Thus, what to do > about a HyperKitty archive (or prototype archive or ...) when a list is > deleted is an administrative decision and is best left up to the site > admins to do it or not. > > As you note with a private archive, former members no longer have access > when the list is gone, but unless an attempt throws some uncaught > exception, that is not a bug. > Thanks, Mark, for the clarification. Regards Philip

3 years, 10 months

[MM3-users] Re: modify subscription page by mailinglist?

by Stephen J. Turnbull

Lars Schimmer writes: > And I think I could fiddle out how it works. But in general, e.g. a > custom page per mailinglist for the "list information page" is a bit > more work than expected and I will not follow this idea. > (e.g. adding a logo per list, ...) Just adding a list-specific logo is not hard. Choose a naming convention (probably something like f"logo-{list_id}.png"), put the logo PNG in one of the static directories and add <IMG SRC="logo-{{list_id}}.png" ALT="Logo for {{list_id}} list." /> in the right place in each template (maybe even "base.html", but more likely an intermediate template specifically to allow putting such customizations in one place for list-specific pages). Adding the ability for a list admin to easily upload a file and set the logo to it would require surgery to Postorius's Python code, though. I will admit that though I think this is a cool idea, I am not interested in doing it myself. But if your interest is at the "I'd rather wait a few months than do myself", GSoC is coming up again, and you could lobby for it when the students start applying. ;-) Steve

3 years, 9 months

[MM3-users] Mailman3 not able to deliver emails sent through list, but moderation notifications

by Daniel Böhmer

Hello Mailman users, I've been using Mailman2 for 10+ years and have recently upgraded to Debian Buster with Mailman3. I've tried to setup Mailman3 similarly but it fails to deliver emails sent through a list. I do receive all moderation notifications at the same time. During startup /var/log/mailman3/mailman.log receives: > Cannot connect to SMTP server localhost on port 25 but I've made sure postfix is listening on *:25 for both IPv4 and IPv6. When sending a message to a list the same file receives: > Nov 25 11:38:14 2022 (70371) ACCEPT: <MESSAGEID@HOST> (message ID and host redacted) and nothing else happens: no more log messages, Postfix logs the email sent TO Mailman but doesn't log anything about emails sent BY Mailman. If Mailman fails to send emails via Postfix I'd expect it to log error messages but it doesn't seem to do so. I found this article stating the the SMTP error message might be misleading: https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… How to further debug this? What could be wrong with my Mailman3 instance and how to fix it? Kind regards Daniel Böhmer

2 years, 11 months

[MM3-users] Re: Installing Mailman3 under a Python Virtual environment running on RHEL9

by Odhiambo Washington

On Tue, May 21, 2024 at 2:44 PM Andy Macheta <andy.macheta(a)gmail.com> wrote: > Hi, > So tried, without much success, to get Postorius working on my Mailman3 > server and every internet trick& tip I tried did not work so decided to > take a new approach as recommended at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Used this reference: > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-depe… > which I know is more for Debian/Ubuntu systems but I was hoping that 90%+ > would also work with Red Hat. > Fell at the first hurdle with no packages available called "python3-dev" > or "python3-venv" > The virtualenv method should work for all OSes, not just Debian/Ubuntu. I use it on FreeBSD too. I have never touched RHEL, but Google-foo tells me that you need to do: yum install -y python3-devel Alternatively, search for the package in yum , use the following command: yum search python3 | grep devel You could also search for the venv one by: yum search python3 | grep env Whatever else you'd need to install on the base OS, just use the above search method and install it. Feel free to post questions here if you aren't sure on what to install. The documentation - https://docs.mailman3.org/en/latest/install/virtualenv.html - requires you to install the following in the base OS: 1. python3-dev python3-venv sassc lynx 2. A database server - could be PostgreSQL or MySQL. You can search for them too :) 3. An MTA - could be Postfix or Exim. Your choice. 4. A webserver - could be Apache or Nginx The challenge you're likely to face is probably to do with how to start the MM3 core and MM3 web services, but you can figure that out, no? Alternatively, just dump RHEL and use any Debian-based OS :) Is there anyone that has managed to install a running version of Mailman3 > that has a working GUI whether it is on bare metal or Python virtual > environment and if so, could they kindly let me know how they did it?? > The closest I've come is a running command line version of Mailman3 which > is fine for me of course but not for anyone else as they like access via > web browser. > Let's see if you can get this running in the next 3hrs. Do you use WhatsApp? Let's chat on +254732000004 -- 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, 5 months

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

by worik

This has been a very interesting discussion. We should be mindful that it is occurring all over society. It is arguable, and I hope true, that the worm has turned regarding privacy. People are starting to realise that you always (in the general case) are paying for a service. If not with money then with something else. In some cases both (hello square space!) tl;dr The choice for or against using the big bad corporation services needs to be clear and usable. Privacy is a minority interest today but IMO the writing is on the wall and for web services it will become the wolf in the kitchen. On 14/02/19 3:42 PM, Stephen J. Turnbull wrote: > Jonas Meurer writes: > > > But still, adding so-called "social" authenticators to the mailman3 > > django application will expose users to the risk of clicking on > > those ID provider buttons. > > I can see this point for Debian users. I suspect Ubuntu users are > somewhat less paranoid. :-) > > Since that risk holds even for sites that enable explicitly (assuming > we adopt the same policy) I will take a look at making that risk hard > to realize (more distance from anything else clickable, smaller > buttons with visible and accurate boundaries. Better that it is off, or it is on for a selected group of providers. The issue is not the prominence of social login options but the presence. I disagree that accidental clicking on social login widgets is a major issue, but I have no data, so it is a opinion. > > > Personally, I consider it a major privacy issue if one central > > instance (e.g. Facebook) is able to track on which platforms and > > services you authenticate. > > Sure, but that ship has pretty well sailed AFAICT. Most users use > unconfigured versions of IE (or Edge) and Safari, which means they're > subject to all manner of webbugs. My employer just asked me to stop > using Firefox because it's too pedantic for their website development > vendors. :-( GDPR enforcement seems to primarily be an arm of the EU > trade offensive against large American services (that's the > Economist's recent opinion, not mine), while Europe-based globals are > undoubtedly doing the same crap. The ship has not sailed. We can get back what we have lost. The new generation of web developers are, in my experience, too enamoured with the cool stuff they can do, and ignore old grey beards (like myself) talk of "attack surfaces" and "chains of trust" and blithely install google fonts, load javascript from CDNs, etcetera that gives their user's data away without a thought or regret. Ten milliseconds and 20kb is considered too high a price to pay for enabling some body else's privacy. But they are starting to face push back from consumer groups who understand the value of what is being handed over. > > And to be honstes, I'm a bit irritated that those tracking features > > from big corporates like Facebook and Google, whose main business > > model is to aggregate as as much private data points as possible > > about as much users as possible are enabled by default in Mailman3 > > upstream. > > Your irritation is not our problem, though, since you can use Debian's > version, and as I mentioned earlier, as far as I know most of our > sites are happy to have social auth. I will be paying attention to > the list to see what others think. That irritation is exactly the problem. It is a problem we need much more of. > > > Besides the privacy concerns raised above, on problem with central > > authentication services is that they also create new single points > > of entry/failure. If your Facebook account gets hacked, you now > > loose control over all other services/platforms, that you used the > > Facebook authenticator service for. > > Same thing if you use a weak password. Effective and secure > authentication is not something we're good at, and we can't really > afford the effort to be good at it. These things are tradeoffs, and > the default should be something that most of our users (ie, site and > list admins, NOT subscribers) want. Hopefully their preferences in > this respect reflect those of *their* users (== subscribers). Attack surfaces. "Whataboutism" is not a valid argument against the argument that you should decrease your attack surface. But social authentication is enabled are the trackers are not loaded too. As far as I can see. If so that is a good thing. The big bad corporates only get data when some one actually uses their services. > > > I agree with Torge that those social auth providers should be > > disabled per default. IMHO, A sane default would be to list them in > > the settings.py but have them commented out. > > "Those" social auth providers? Are there social auth providers who > provide what you consider acceptable privacy guarantees (a la > Duck-Duck-Go in search engines)? If so, we could make those higher in > the list/easier to use. I disagree that they should be disabled by default. I agree they should be disabled, but it should be by choice. What is required is a configuration option in the interface not in the text configuration files. The former is for list administrators the latter is for site administrators. Currently list administrators do not have that choice. (I am new here, do I have that correct?) Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 8 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Stephen J. Turnbull

Kimmo L writes: > This is simple test email with content like "Test test test" to > test out this specific mailing list, which somehow does not sent > emails to the list of members. Wierd that other lists works fine, > but this one is bugged. Maybe i should try to delete it and > recreate it ? That might work. > 2) This second error seems indeed not related with that first one. > "AttributeError: 'NoneType' object has no attribute 'strip'" occurs > quite many times in mailman.log file. Should i check some specific > list settings? I don't think so. That usually indicates mal-formed mail, missing a required header field. In the case you posted earlier, the mail had no Message-ID that Mailman could find. I suspect you have a configuration where your MUA doesn't add the Message-ID header (this is common, because all internet-facing MTAs do add one if there isn't one already in the message, so many MUAs let the MTA do it), and for some reason local mail doesn't go through a proper MTA and never does get one.

3 years, 1 month

[MM3-users] Re: Enable delivery

by Mark Sapiro

On 12/9/24 17:35, Hirayama, Pat wrote: > Greetings, > > I'm finding something a bit odd with our listserv. Please see https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv > Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If you look in the MTA logs is mail being sent to them. As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/member.p… Also see the various tabs at https://www.example.com/mailman3/accounts/subscriptions/ > If I select Enabled and Save, then delivery starts working for that user. This should only happen if the users address or user based preference or the global preference is Disabled. > There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: > > mailman members --nomail any listname@listserv > > Nothing is returned. Because all members ultimately have delivery enabled. > If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. It shouldn't be necessary to do that. For one of these members, e.g. user(a)example.com, that isn't getting mail, do this in mailman shell ``` mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)example.com') >>> print(mbr.delivery_status) (this will print the ultimate delivery_status, for the components do) >>> print(mbr.preferences.delivery_status) (output) >>> print(mbr.address.preferences.delivery_status) (output) >>> print(mbr.address.user.preferences.delivery_status) (output) >>> print(system_preferences.delivery_status) (output) >>> ``` The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

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

1 year, 1 month

[MM3-users] Immediate notification to the administrator

by Stephen J. Turnbull

pau.baiges(a)csuc.cat writes: > When there's a message being held because it needs approval, it > automatically sends an email to the list owners. However, it also > states that it sends a daily reminder if the email remains > unapproved, but it's not doing that. Did it send the daily reminder before, and then stop? Or did it never send the daily reminder? The immediate notification is triggered by the receipt of the moderated mail. However, once that happens, the Mailman daemon no longer pays attention to it. Instead, there is a cron job that runs once a day that checks the held queue and sends daily reminders. The most likely reason is that the cron job is not running. > I'll show you how I have /etc/postfix/transport configured. I > receive the first "owner" email, but not the daily one. This is irrelevant. The same Mailman function is used to send both the immediate notification and the daily reminder, and it does not use the list-owner alias to do so. The difference is only whether it is run from the Mailman runner daemon or from a one-shot process started by cron. It consults the list configuration directly when composing the email. Steve

2 years

Search results for query "dO"