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

[MM3-users] Re: rest api runner not running

by Mark Sapiro

On 3/27/21 5:13 AM, Christine wrote: > 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. Nothing is listening on port 8001 because apparently Mailman core failed to start. > There is nothing in mailman.log, nor in smtp.log What Mailman package is installed? Perhaps you should contact the packager for support. Can you run the mailman command manually, e.g. ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg ``` where `xxx` is the Mailman user which if I'm guessing correctly that this is a debian/ubuntu package, is `list`. Otherwise it might be `mailman`. That should just produce a list of `mailman` subcommands. If that works, try ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg info ``` and ``` sudo -u xxx mailman -C /etc/mailman3/mailman.cfg start ``` and see what they produce. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Stephen J. Turnbull

Steve Brown writes: > Yes, I intended to post to the list. I now see that if I use the > archives to post (as I'm doing now), As Mark said, you posted via Gmail (first Received header plus lots of GoogleMail internal data). > I don't see any apple iCloud, Gmail, Yahoo, Hotmail users mostly use the webmail of the provider so their address is a very good clue to the capabilities of their MUAs, but Apple Mail is an app on the iPhone or Mac. You'd have to look at the content of the mail (sometimes there's a User-Agent header, or iPhones often have "sent from my iPhone" as a footer) to know that someone is using Apple Mail, just as you'd need to do a bit of header spelunking to find out that I use the VM application on XEmacs on Mac. I know a fair number of Gmail users who use Apple Mail on Mac rather than Google's webmail, and a very few who have Outlook addresses. Your academic users very likely include a high percentage of Apple Mail users. "Wrap" is known to have been problematic with iPhones, unclear about Apple Mail on Mac (but it's a good bet given Apple's penchant for reusing Mac code on iOS). Since "Munge From" is now the industry standard for dealing with sites that use DMARC reject policies, it wasn't worth it to check if Apple Mail improved over time. > so I suspect that using the archive for search or posting would > also seem like a PITA. Sure. We have to acknowledge that all of these suggestions are just workarounds for a fundamental issue with current email MUAs (specifically, defaulting to unsigned mail and depending on providers to authenticate). -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 months, 1 week

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

by Mark Sapiro

On 9/19/24 05:46, Markus Grandpré wrote: > Dear list, > > I would like to activate the invitation setting for all lists as > default. In Mailman 2.1 I have done this in the file > </etc/mailman/mm_cfg.py>: > > > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > > > How can I do this in Mailman 3? There is a draft merge request at https://gitlab.com/mailman/postorius/-/merge_requests/930 which implements a framework for setting Postorius defaults and creates a setting to set the default for pre-verified on the mass subscription page. Once merged, this can easily be extended to provide a default for Invitation. In the mean time, you can only do this by patching src/postorius/forms/list_forms.py like ``` --- a/src/postorius/forms/list_forms.py +++ b/src/postorius/forms/list_forms.py @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): invitation = forms.BooleanField( label=_('Invitation'), - initial=False, + initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' ``` > Can I also transfer other default values > like: > > ... > DEFAULT_SERVER_LANGUAGE = 'en' > DEFAULT_SEND_REMINDERS = 1 > DEFAULT_SUBSCRIBE_OR_INVITE = Yes > DEFAULT_PRIVATE_ROSTER = 2 > DEFAULT_ARCHIVE = Off > DEFAULT_ARCHIVE_PRIVATE = 1 > ... > > from the very same configuration file to Mailman 3? Is there a > documentation of the default values for lists in Mailman 3? This is done by creating a list style with the desired defaults. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… for documentation of styles and see https://gitlab.com/mailman/example-mailman-plugin for an example of creating a plugin in Mailman core to make a persistent style. There is no specific doc for the list settings. You need to look at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py for the various settings and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/default… to see which default classes are applied for various styles. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

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

by Mark Sapiro

On 9/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > I am trying to find a way for content filtering to remove executables from the emails sent to the list. I found some hints under: > https://mailman.readthedocs.io/en/stable/build/lib/mailman/handlers/docs/fi… > > but still not clear how to do it for all type of excecutables. There are four list settings that affect this. They are pass_types, pass_extensions, filter_types and filter_extensions. the pass_* settings specify message parts the list will accept while the filter_* settings specify message parts the list won't accept. The page at <https://mailman.readthedocs.io/en/stable/src/mailman/handlers/docs/filterin…> only discusses filter_types and needs updating for the others. Filtering by extension only works on message parts that have an associated file name. Thus, while you can add things like 'exe', 'bat', 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it won't be completely effective. A better approach is to use MIME types[1] and only allow those you want. For a discussion list, a reasonable set is what this list uses: multipart message/rfc822 text application/pgp-signature This will accept any multipart and message/rfc822 parts for further analysis and ultimately accept only text/* and application/pgp-signature elemental parts. If you want to accept images and pdfs, you can add image application/pdf See <https://www.iana.org/assignments/media-types/media-types.xhtml> for a list of all registered MIME types. Note that these are all of the form main_type/sub_type and putting just main_type in *_types passes or filters all subtypes for that maintype. [1] You can use both, e.g. filter_extensions to remove those you don't want and pass_types to accept the MIME types you do want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Settings for prevention of spam obfuscation

by Stephen J. Turnbull

Richard Rosner writes: > And yes, while there may be edge cases where these bad practices If you're willing to impose that judgment on your posters, just announce that you're going to start discarding posts that don't satisfy From alignment, give it a week, and start doing it. That will ensure that the Sender is always in the From field. No more, and no less. I wouldn't do it, but it's a perfectly effective way to achieve what you seem to believe is ideal. > And until someone can create an ML model that's not gobbling up > resources for training and that doesn't need thousands of emails to > train with, there's only so much you can do. SpamBayes has been around for decades.[1] It's not ChatGPT-level, but it also doesn't take "significant resources" or thousands of emails for training (your current spambucket and INBOX will be a decent start) and you can train it on the fly as mail comes in. The only resources required are a couple of hours to install it and learn how to feed ham and spam corpuses into it, and a few minutes every so often to feed increments of ham and spam to it. You can even avoid that amount of effort by feeding the spam and ham it outputs back into it.[2] Almost certainly you can plug it into rspamd. > While DKIM and DMARC are great, they are useless when the vast > majority of senders don't have any DKIM signatures. For ARC it's > not as uncommon to be present, but the situation isn't that much > better. Please stop. These claims are not going to pass on this list. We know better.[3] If you are in a special situation where they bear some resemblance to the truth, please explain. Maybe we can come up with a solution for that situation together. But they are wildly wrong in the context of Internet email in general. Look, Richard, spam is extremely frustrating to all of us. There's a lot of effort and talent that has gone into combatting spam, and a fair amount of knowledge about it has accumulated in the people who participate in Mailman lists. If you want help with the particular spam that's getting into your lists, we'll be happy to help (although help channels for your preferred filtering software might be more productive). But the way to get help is to explain what your problem is, and what you've done that isn't working, in some detail. You telling us how we can fix it in Mailman is almost always a non- starter. Either it's going to screw up the mail system with little anti-spam effect, or it's been tried and shown to be ineffective. It's certainly not persuasive if you haven't shown us what the problem is at a more granular level than "we all hate spam!" It's possible that we'll come back to your suggestion sooner or later. Sometimes there's no other way that's better. But that's quite rare. ;-) Footnotes: [1] In fact, I've recently seen the (otherwise unsupported ;-) claim that spam-filtering was the original motivation for ML research. :-) [2] This leads to overfitting and increased error rates after a while. YMMV. [3] For example, in my current spam-bucket, all of which I've eyeballed, there are 7519 Message-IDs and 9521 DKIM-Signatures. Of 206 messages from external sites in my now spam-free INBOX, there are 336 DKIM-Signatures. Since it's common to have more than one DKIM-Signature per message, that doesn't prove that essentially all of those messages are signed. But it sure seems likely! And ARC is much less common: 4903 ARC-Seals in spam, and 155 in INBOX.

1 year, 6 months

[MM3-users] Do you struggle with message rejected. AUP#CDRBL while using mailman with your ISP email relay?

by Stephen J. Turnbull

Michael Richardson writes: > My problem, on lists.sandelman.ca aka lists.tcpdump.org, is > messages that appear to have been processed by my MTA (according to > postfix logs), but which are never delivered, nor held. Lost > somewhere in mailman3 queue. Sometimes they show up after a host > reboot. The queues are implemented the same way mail queues have been implemented since the Neolithic Era: save a file to disk, report success to the previous hop, then try to send its content to the next hop. If that succeeds, delete the file. If it does not, either send back a failure notice and delete the file, or hold the file for a later retry, depending on why it failed. The queues are in $var_dir/queue/*. If you don't find the messages there, they were delivered successfully as far as Mailman could determine (ie, the outgoing smtp process reported a 2xx status). You can use the "mailman qfile" command to examine the contents of queue files. The shunt and bad queues are "sinks" -- if a message gets into those queues, Mailman will not try to deliver them because they caused some kind of error. The "mailman unshunt" (no argument needed) will try to resend messages in the shunt queue. Depending on why they got there in the first place, and whether that problem was resolved, they may be successfully sent, or they may end up back in the shunt queue. I forget how messages get into the bad queue, but there's no automated way to handle them at all. Check the mailman.log and smtp.log logs (in $log_dir, by default $var_dir/logs) for reports on what mailman was up to. mailman.log is pretty verbose and interesting information is relatively sparse. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 4 weeks

[MM3-users] Re: Long-shot cry for help

by Matthew Alberti

David, I had alot of the same challenges you are currently seeing. Frankly, a working installation using the Ubuntu packages is seemingly impossible. After trying that and also pip, I elected to use the Docker method. https://github.com/maxking/docker-mailman Sanity preserved. It is very easy. Just an idea. - Matt Alberti ⁣Get BlueMail for Android On Jun 3, 2021, 9:35 AM, at 9:35 AM, David Partain via Mailman-users <mailman-users(a)mailman3.org> wrote: >Hi, > >I'm having severe operational issues with my mailman3 site. My site is >built on standard Ubuntu packages (18.04), and they're ancient. I'm >having two big issues... > >1. I have the old smiley problem that I've had from the very beginning >and never solved. I have added 'charset': 'utf8mb4' to the relevant >config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in >the sense that the calls to mysql do not include the charset stuff. > >/usr/share/mailman3-web/settings_local.py links to >/etc/mailman3/mailman-web.py and there is no file >/usr/share/mailman3-web/settings_local.pyc. I moved it out of the way >hoping it'd get re-built, but it has not been in the months since. > >The result of this that I get hundreds of mail messages to root >(thousands, really), rapidly filling / with mail in /var/mail/root and >logging in /var/log/mail.log. The mail has something like "Subject: >[Django] ERROR (EXTERNAL IP): Internal Server Error: >/mailman3/hyperkitty/api/mailman/archive" and "DataError at >/hyperkitty/api/mailman/archive (1366, u"Incorrect string value: >'\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" > >I have tried to trace to figure out what file is _actually_ controlling >the calls to mysql. There's a file called >/var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no >idea what that is or if it might be used. > >Is there something like 'mailman info' for mailman-web so I can see >what files are being used? I'd love to fix this... > >2. There's this one curious cron job... > >* * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 >/usr/bin/django-admin runjobs minutely --pythonpath >/usr/share/mailman3-web --settings settings > >(yes, I know python2.7 is a problem... see the last paragraph below). > >These jobs start piling up. They run & run & run, and eventually the >machine screeches to halt when it runs out of memory and goes belly up. >This is a relatively recent development. After a while, I'll have 5 or >6 or more of these all running, looking something like this: > >www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 >/usr/bin/django-admin runjobs minutely --pythonpath >/usr/share/mailman3-web --settings settings > >What this means in practice right now is that I'm forced to go in and >kill these on a regular basis or the machine _will_ die and people >_will_ shout at me. > >Does anyone have any idea why these might not be finishing? Can I >comment this out completely & live happier? Any help whatsoever? > >----------------------------------- > >Finally, I should add that I know my current installation is >fundamentally flawed because I chose to go with distro packages. I >simply cannot fix it. My strong recommendation to others who follow me >is that they do NOT do this. Bite the bullet and install via pip... I'm >now in the process of setting up a new server that is completely based >on the latest via pip installation. I have to get away from what I have >or lose my sanity. > >Cheers, > >David > >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 3 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 Eggert Ehmke

Works for me too! Thank you. Only the path to python is #! /opt/mailman/venv/bin/python In my installation. Cheers, Eggert Am Dienstag, 25. April 2023, 22:51:52 CEST schrieb Mark London via Mailman-users: > 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 > > /GH4K42T66FU5PBHJH6ZDQEIUTXVDSLOC/ > > > > > > > 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. > > > _______________________________________________ > 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 > /K3PO2XMCDR2342GVPHEQJNZPVPEPY6R4/ > > This message sent to eggert(a)eehmke.de ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 4 months

[MM3-users] Re: Upgrade-path from Ubuntu18LTS to recent mailman release

by Stephen J. Turnbull

Stefan Bauer writes: > thanks alot. That looks promising. Can we just copy the current > mailman3-database and take the configurations or is there a specific > migration path we have to follow? Much of the documentation on mailman.readthedocs.io discusses migrations and upgrades. You should read those for general hints. The distro Mailman to venv Mailman case is more discussed here on the mailing list than in those documents. I don't have pointers to those threads or the time to look offhand, maybe over the next few weeks as I work on our GSoC project. If you do find any, and would post them here, I'll make sure they get into the docs. The main thing is to backup Mailman configs (probably in /etc/mailman or /etc/mailman3) and the backend database (core, Postorius, possibly HyperKitty depending on configuration, and the django-mailman auth stuff) before trying to migrate. (For the backend database I would just dump the RDBMS unless non-Mailman content is really huge.) The nature of the virtualenv install is such that it *will not* overwrite any of the distro files at all (as long as you put it in /usr/local or /opt). However, you want to preserve the configs and database and reuse them, so those *must* be backed up. > We are currently running 3.1.1-9 (Ubuntu 18). Ubuntu 18 is probably old enough that you need to be careful about MySQL and its derivatives. The specific problems are (1) you need to specify the right UTF-8 variant for the coding system, and (2) more recent versions of Mailman tend to make certain records overflow. If you're using PostgreSQL these caveats *do not* apply. If you're using sqlite3 (I doubt it, but just for completeness) you should change to PostgreSQL or MySQL. If you're using something else (same caveat), I can't really say. Probably somebody out there is using Oracle or whatever, but we don't know about that. :-) Steve

3 years, 4 months

[MM3-users] Re: Messages not going to held queue

by Stephen J. Turnbull

Mail Person writes: > I have it set I guess by "it" you mean the user's moderation status, but there are *many* variables that affect whether mail is delivered or not. These include emergency moderation, spam filtering, and HTML handling (and there are probably others I don't remember off the top of my head), as well as individual variables such as not_metoo and the moderation status. All I can rule out is emergency_moderation, because that would prevent your test mail from being delivered when the test user is set to allow. > the user did not get a moderation email, myself as the moderator did > not get a notification, and Postorius did not show them in the held > messages queue. When you set the test user to accept, did you set it to "accept" or to "default processing"? Setting it to "accept" bypasses almost all of the acceptance checks. Usually "default processing" is what you want. > As far as logs, in var/log/mailman3 I do not see any logs other > than mailman.log, plugins.log and smtp.log. In the SMTP log I can > see that the message is getting to mailman: Does mailman.log show any errors? > This leads me to believe the message is being discarded or for some > reason not getting to the moderation queue. Sure, but Mailman doesn't do that for no reason. The only thing I can think of offhand that might happen in a mostly default configuration is that you're using an MUA that creates a multipart message where the plain part is empty and the actual message is HTML (yes, I've seen that in the wild). In some configurations that would cause the HTML part to be deleted, then the message could be recognized as empty and discarded. I haven't analyzed the code thoroughly but I don't recall a log message on that execution path so it might fit your case.

3 years

[MM3-users] Re: Mails are stuck in Mailman Pipeline Queue

by Mark Sapiro

On 3/26/22 21:01, Shashikanth Komandoor wrote: > > But the below trace back is observed during mailman service stopping: This doesn't say much ... ...> Mar 27 09:01:22 2022 (5864) Uncaught runner exception: > Mar 27 09:01:22 2022 (5864) Traceback (most recent call last): > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration ... > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 114, in signal_handler > raise RunnerInterrupt > mailman.interfaces.runner.RunnerInterrupt > Mar 27 09:01:22 2022 (5864) SHUNTING: 1648351882.6693938+ > c2e6ed709646a7680c73059b52d2f0451836e591 > Mar 27 09:01:22 2022 (5864) digest runner exiting. Above, digest runner was interrupted in processing and shunted the message it was working on. and below, pipeline runner was interrupted in processing and shunted the message it was working on. > Mar 27 09:01:22 2022 (5860) Uncaught runner exception: > Mar 27 09:01:22 2022 (5860) Traceback (most recent call last): > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", > line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", > line 50, in process > handler.process(mlist, msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > mailman/handlers/member_recipients.py", line 84, in process > for member in mlist.regular_members.members > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > mailman/handlers/member_recipients.py", line 83, in <genexpr> > recipients = set(member.address.email > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > line 239, in members > yield from self._get_members(DeliveryMode.regular) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > line 226, in _get_members > if member.delivery_mode in delivery_modes: > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > line 205, in delivery_mode > return self._lookup('delivery_mode') > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > line 167, in _lookup > pref = getattr(self.address.preferences, preference) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > line 287, in __get__ > return self.impl.get(instance_state(instance), dict_) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > line 723, in get > value = self.callable_(state, passive) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > line 760, in _load_for_state > session, state, primary_key_identity, passive > File "<string>", line 1, in <lambda> > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > line 850, in _emit_lazyload > session.query(self.mapper), primary_key_identity > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/ext/baked.py", > line 603, in _load_on_pk_identity > setup, tuple(elem is None for elem in primary_key_identity) The above says the runner was doing a database lookup. This may be a coincidence or there may be some database locking issue that underlies the issue with the pipeline runner. > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 114, in signal_handler > raise RunnerInterrupt > mailman.interfaces.runner.RunnerInterrupt > Mar 27 09:01:22 2022 (5860) SHUNTING: 1648351882.8537986+ > 9bf59cb23a71a4bae65536bfdbec0abb261adaa0 > Mar 27 09:01:22 2022 (5860) pipeline runner exiting. I suggest doing the following assuming your Mailman database is not sqlite3 (if it is, just do step 2): 1) Stop mailman core and maybe other mailman services too. 2) Assuming the two shunted messages are still in Mailman's shunt queue, run `mailman unshunt` to unshunt them. If there are more shunted messages, inspect them with `mailman qfile` to see if you want them, They may be spam. 3) Restart your database server. 4) Start Mailman core and any other stopped services. Also, look in the database server logs for any issues. -- 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: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Abhilash Raj: > On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: >> Hey Abhilash, >> >> Thanks a lot for your work on mailman3! >> >> Abhilash Raj: >>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. >>> >>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that >>> I can think of is non-member management in Postorius. >>> >>> New releases are available on PyPI[3][4]. >> >> For earlier releases, you provided GnuPG signature files to >> cryptographically verify that the release files were not tampered with. >> >> I couldn't find such signature files for the two latest releases. Would >> you mind adding them? When packaging for Debian, I prefer to check the >> GnuPG signatures before uploading new releases. Also, the signature >> files get uploaded to the Debian archive as well so they can be checked >> by everybody. That way we can cryptographically proof that the Debian >> package is based on the original tarball that got packaged and signed by >> upstream. > > > Ah, sorry about that. I completely forgot about that. > > I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. Thanks a lot, that would be awesome. I'll wait for it before doing the Debian package uploads. Just to let you know: we're close to soft freeze in Debian, so in order to get those uploads into the next stable release (Buster), they'll have to be uploaded rather soon. The same holds for other pending releases of Mailman3 components: Just in case you plan to do new upstream releases anytime soon, it's still possible to upload them to Debian in time for Buster. Cheers jonas

6 years, 7 months

[MM3-users] Re: uncaught bounce messages

by Mark Sapiro

On 10/23/21 10:51 AM, David Bremner wrote: > > I'm getting (many) uncaught bounce messages for one user. Other than > forcibly unsubscribing them, is there anything I can do? I hesitate to > post this message publically, but here is what I can see, somewhat > anonymized If you send me the complete bounce message off list, I can see if it should be added to the recognition at https://gitlab.com/warsaw/flufl.bounce/. BTW, is flufl.bounce in your installation version 4.0? If not you can update via pip install -U flufl.bounce which may help. Actually, depending on how these where installed, it might be necessart=y to do pip install -U flufl.bounce flufl.lock flufl.i18n To avoid import errors due to packaging issues. > The MIME structure looks like > > └┬╴multipart/mixed 7030 bytes > ├─╴text/plain 442 bytes > ├─╴message/delivery-status 176 bytes > └─╴text/rfc822-headers 5301 bytes This is not a RFC 3464 compliant DSN which looks like the above except the top level is multipart/report, not multipart/mixed. However, our recognizer shouldn't care as it only looks at the message/delivery-status part. > In /var/log/mailman3/bounce.log I see lines like > > Oct 23 08:20:00 2021 (5320) Bounce message w/no discernable addresses: <hex-digits(a)foo.bar> <hex-digits(a)foo.bar> is the Message-ID: > In the delivery-status part I see A compliant DSN will also have a Reporting-MTA: section preceding the Final-Recipient: section. > Final-Recipient: rfc822; fub(a)foo.bar > Action: delayed > Status: 4.0.0 This is not a bounce. It is a 'delivery delayed' message. If delivery is not accomplished within an MTA configured time (days), it will turn into a 5.x.x failure which is a bounce, but since fub(a)foo.bar was not recognized, the DSN is non-compliant in some way. In any case, please send me a copy of the bounce so I can see about recognizing 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, 10 months

[MM3-users] Re: Error on timeout vs retry values

by Abhilash Raj

On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: > Hi everyone, > > I have recently setup a new mailman3 service using the venv method. > Everything is functionally working however I keep getting an error sent > to the mailman email every min which I can not seem to figure out why. > > /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: > UserWarning: Retry and timeout are misconfigured. Set retry larger than > timeout, > failure to do so will cause the tasks to be retriggered before > completion. > See > https://django-q.readthedocs.io/en/latest/configure.html#retry for details. > See https://django-q.readthedocs.io/en/latest/configure.html#retry > for details.""" > > I have edited the timeout and retry values in the > /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file and > restarted both mailman and mailman-web however this still keeps repeating. You shouldn't edit files in `site-packages` directory as they are part of the package itself and could cause issues. What you want to do is override it in your settings.py (or settings_local.py) file for Django. I am not sure which guide you followed to install Mailman, but it should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). It should look something like this https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web.sett… Just the value of retry should be just > than timeout as the error says, so not necessarily same values, but so far 300 and 360 has been working good for us and I haven't seen any report to increase them. > > Any ideas? > > Regards, > > Robert > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > _______________________________________________ > 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: Problems configuring hyperkitty

by Thomas Hochstein

Alain D D Williams wrote: > I assume that that will create some database tables. Hopefully this will have > been done by installing package python3-mailman-hyperkitty. You'll need mailman3, mailman3-web and python3-mailman-hyperkitty installed (or mailman3-full, which includes those three). > • What database & tables will that be ? It would be really useful to be told so > that I can check. +-----------------------------------+ | Tables_in_mailman3web | +-----------------------------------+ | account_emailaddress | | account_emailconfirmation | | auth_group | | auth_group_permissions | | auth_permission | | auth_user | | auth_user_groups | | auth_user_user_permissions | | django_admin_log | | django_content_type | | django_mailman3_maildomain | | django_mailman3_profile | | django_migrations | | django_q_ormq | | django_q_schedule | | django_q_task | | django_session | | django_site | | hyperkitty_attachment | | hyperkitty_email | | hyperkitty_favorite | | hyperkitty_lastview | | hyperkitty_mailinglist | | hyperkitty_mailinglist_moderators | | hyperkitty_mailinglist_owners | | hyperkitty_profile | | hyperkitty_sender | | hyperkitty_tag | | hyperkitty_tagging | | hyperkitty_thread | | hyperkitty_threadcategory | | hyperkitty_vote | | postorius_emailtemplate | | socialaccount_socialaccount | | socialaccount_socialapp | | socialaccount_socialapp_sites | | socialaccount_socialtoken | +-----------------------------------+ > • I have several different maildomains each with several lists. I think (!) you'll have to add each mail domain in Django, i.e. <http://yourhost.example/mailman3/admin/>, section "Django Mailman 3", "Mail domains". > Some lists in different domains have the same name. Doesn't matter, as the list name for all parts of Mailman3 is "listname(a)domain.example", i.e. including the domain. > One of the next things that I will need to do is to import archives from > mailman2. How does the command below change for the different domains ? > > django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] AFAIS you'll have to use "/usr/share/mailman3-web/manage.py" instead of "django-admin". For me, that command has worked: | python3 /usr/share/mailman3-web/manage.py hyperkitty_import -l listname(a)domain.example /path/to/listname.mbox You'll have to do that for every list, regardless of domain. > Is there some better documentation that I have failed to find ? Not that I know of. Most is - more or less - documented, but it's not easy to apply the documentation to a Debian installation. It was a bumpy ride, but not really that problematic, as I remember; some googling and try and error was involved. ;) -thh

9 months, 4 weeks

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

by Abhilash Raj

On Sat, Aug 31, 2019, at 9:25 PM, paul(a)arenson.org wrote: > 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? No, this isn't anomaly. Check out the "Role" column. You are an "owner" of the list and are thus allowed to change the list settings. You are also a "member", which means you will get emails from this mailing list. > > Global based preferences are listed. Address and email based ones are > not showing either enabled or disabled. They are unset, which means they are set to whatever the default value in the backend is. I know this is terrible in many regards, but we have an issue open for this. Hopefully, this will improve in future releases. > > 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) That's right. > > 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?) I explained non-member in other email you sent. > > 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? If this is a new list, it will probably not have any templates. > > 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? This option is deprecated, and actually now removed. > > 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 > _______________________________________________ > 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

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:08 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 3:33 PM, Mark Dadgar wrote: >> >> Any thoughts on how to salvage ~20 years of list archives? > > > The archives shouldn't be an issue. I don't think they are involved in > the corruption, but anyway, hopefully you still have the archive mbox > you imported. Then for the messages since then, you should be able to > get a mbox from hyperkitty with something like > > https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… > > with the obvious substitutions and appropriate start and end dates. > > The list is trickier. If you are going to start over with a clean > install, and if you have a config.pck that you imported from MM 2.1, I > suggest the following: > > Use the `mailman members` command to get a list of all members. Then > depending on how much work you want to do, also get separate lists of > plaintext and mime digest members and members with delivery disabled. > > Then on the new install, import the config.pck with `mailman import21` > and import the archive mboxes with hyperkitty_import. > > Run `mailman members --sync` with the full current membership list, and > record the [ADD]s. Then you can match the [ADD]s against the plain and > mime digest members and those with delivery disabled and set their options. > > That's a lot to do, but it should get you close. I would probably be satisfied with just exporting the current list of member email addresses + names and letting people go back and change their list settings to switch to digest, etc. if necessary. > On the other hand, if you can wait, we might be able to figure out how > to fix this, and it's even possible the underlying issue isn't database > corruption. Sure - I can wait. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0" The request seems to originate from the server where the mailman suite is installed Best Regards,Eric On Sunday, December 13, 2020, 01:54:54 AM GMT+1, Eric Broens via Mailman-users <mailman-users(a)mailman3.org> wrote: The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 9 months

[MM3-users] Re: Upgrade Mailmam Core from

by Stephen J. Turnbull

Sascha Rissel writes: > I wonder a bit how deep I have to dive into these individual configuration files. > Is there some minimal config for a standard Ubuntu/Debian system? I think that if you follow the "venv" process as described in <https://docs.mailman3.org/en/latest/install/virtualenv.html?>, it covers everything you must configure. There are about a dozen places that you must check in mailman.cfg, such as the location of your MTA and its port (for the simplest installations, host=127.0.0.1, port=25 will do), mailman's LMTP port (usually the default of 8024 will do), and the credentials for accessing the REST interface (restadmin and restpass: change these!!) Pretty sure there are others. There are quite a few decisions that need to be made in mailman-web settings.py, including setting the REST credentials to the ones you chose in mailman.cfg, and setting up your database (sqlite3 is great for quick experiments or tiny installations with 10 posts/year ;-). And I don't think there are any MTAs or webservers that are plug and play with Mailman: you have to configure the MTA to forward mailman list addresses to Mailman's LMTP port, and usually there's nontrivial configuration of the namespaces that are to be forwarded to Mailman/Django and those that are served directly (such as CSS style files) by the webserver. Django also has its own access credentials that must be coordinated with mailman.cfg I think. So "minimal" is still pretty complex. While I would be *extremely* cautious about using any *values* for parameters that are specified in Brian Carpenter's HOWTO <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> (this is the one that Odhiambo suggested, and it's a really valuable resource), I'm pretty sure it accurately covers all the steps you need to take in configuration. You may find it easier to read than our manual. Going through that and checking your venv configuration against the steps in the HOWTO would be a good way to confirm that you've got a good configuration.

2 years, 11 months

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Stephen J. Turnbull

Mark Sapiro writes: > I have had some contact [with EMWD], but not much. As far as I > know, they are still in business and offering list hosting > including Mailman 3 lists with Affinity and Empathy. They no longer > offer support for installation and maintenance of Mailman on other > people's servers. That exactly describes my experience. To jaboyib556, I recommend you contact them directly and make your own judgment. I do not know the current operators of EMWD, but I do know that the Carpenter family carefully vetted several bids. And their concentration on servers they run suggests they know what they're good at and have focus. I think they're a good bet, but only you can judge. > As far as I know, it was only EMWD that did this and for business > reasons, kept it proprietary. I corresponded with Brian about this.[1] He said that a third-party consultant (not sure if they're related to the current operators) built the Affinity and Empathy applications in PHP on a limited budget, and he felt that he needed to keep them proprietary as a temporary "no competition" measure until they could build up a nest egg to support on-going development. He said, and I have no reason to disbelieve him, that he thought it would take a year to build the reputation, another year to recoup the investment, and within that time frame he planned an open source release. I suspect he planned a Aladdin Ghostscript-like strategy: with the publication of release N, he would release N-1 as open source. He made no commitments, but I believe that was his aspiration. He was always a great supporter of Mailman, giving generously of his time and expertise to people on our lists including those hosting with other businesses. We miss him a lot. Footnotes: [1] On friendly terms: "hope for an open-source release" is not a matter of moral imperative with me, and I believe I speak for all Mailman developers on that.

2 years, 8 months

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

by Darren Smith

Our installation at https://lists.rootsweb.ancestry.com has around 33,000 lists and somewhere around 1.5 million members. We have lists with 5,000+ members. Note that I haven't tried any mass subscriptions. When we upgraded from mailman 2 to mailman 3, we used the old .pck files and ran the import on each of the lists. It did take about 6 weeks to do the full import all 33,000 lists. I'm not joking. As for sending messages - there isn't any problem sending that many messages out, but then we are also not trying to subscribe list members at the time. We are, though, in the process of importing the old archives from our old mailman 2 system. This doesn't seem to affect the rest of the system. We have seen some inefficiencies in the new system, such as the front page of postorius - loading all of the information for 200 lists (if the user set the "lists per page" to 200) was bringing down the system. We have our own metadata system to be able to search for lists by state/region/surname (ours is a genealogy mailing list system), so we had to replace the front page with our own "find a list" functionality. The other main problem was the page where a user can see what lists they subscribe to. That page was also a denial of service if the user had several hundred lists they are subscribed to. And for a genealogy mailing list system, this is common. We have actually ended up creating our own API layer (only accessible on the local machine) and make certain calls to it for the most painful of the issues. One of these days (when we get a moment to breathe) we are going to post some of our changes to the project so that we can ditch our own API and just use the internal REST API. To be fair, the inefficiencies are not necessarily with mailman or the rest API itself - but with Postorius making hundreds of calls to load a single page. Though if the API supported loading multiple lists at once instead of having to load them serially, that might help as well. So while we have not seen any timeout issues on the call to mass subscribe users, we HAVE found several other calls that are effectively a denial of service and have gotten around them ourselves, with plans to contribute to the project in the near future. -Darren On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > 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 > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 4 months

[MM3-users] Mailman installation results in KeyError: 'env_py'

by Marvin Gülker

Hi, I'm trying to install Mailman 3 on Debian 9. However, it doesn't let me do. ~~~~~~~~~~~~~ $ virtualenv -p python3 env [...] $ . ./env/bin/activate $ pip install mailman [...] Successfully installed [...]mailman-3.1.0[...] $ mailman info Traceback (most recent call last): File "/home/mailman/mailman-test/env/bin/mailman", line 11, in <module> sys.exit(main()) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/core/initialize.py", line 185, in initialize initialize_2(propagate_logs=propagate_logs) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/core/initialize.py", line 156, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/factory.py", line 55, in create SchemaManager(database).setup_database() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/factory.py", line 96, in setup_database alembic.command.stamp(alembic_cfg, 'head') File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/command.py", line 504, in stamp script.run_env() File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/script/base.py", line 425, in run_env util.load_python_file(self.dir, 'env.py') File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/util/pyfiles.py", line 81, in load_python_file module = load_module_py(module_id, path) File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/alembic/util/compat.py", line 83, in load_module_py spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 673, in exec_module File "<frozen importlib._bootstrap>", line 222, in _call_with_frames_removed File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/mailman/database/alembic/env.py", line 38, in <module> @public File "/home/mailman/mailman-test/env/lib/python3.5/site-packages/public/public.py", line 15, in public else sys.modules[thing.__module__].__dict__) KeyError: 'env_py' ~~~~~~~~~~~~~ I'm not a Python developer, I usually use Ruby for anything web-related, thus I can't make anything of this. Since the error message conveys exactly no information that I could use to find the problem and Google provides no mailman-specific information on it, I don't know what to do now. Any hint is appreciated. Python version, if of any use: $ python --version Python 3.5.3 Greetings Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 10 months

[MM3-users] Re: Enforcing SSO and subscription options

by Christian Schneider

Hello, did you manage to disable the local registration (with django accounts)? I am trying to get rid of these locally registered accounts as well. Background: I only want authorized accounts (provided by our SSO) to be owners or moderators with the ability to manage lists... So, if I block all other (local django accounts) a list-owner might be able to enter an account with an external e-mail address as another owner, but the external account will not able to sign in via web ui...and to manage the list! (A list member can be any (external) user...I only care about moderators/admins and moderators) Questions: Is this a viable approach, or do I make a conceptual mistake here? Is there another way to prevent non (sso-)authorized from becoming an owner? Remark: I followed your way in this thread and made copies of various template files in a seperate location. (I run a venv installation on Ubuntu) My central configuration files are under /etc/mailman3 (mailman.cfg, mailman-hyperkitty.cfg, settings.py and uwsgi.ini) I set the following options in settings.py: TEMPLATES[0]['DIRS'].append('/etc/mailman3/templates') SOCIALACCOUNT_ONLY = True ACCOUNT_EMAIL_VERIFICATION = EmailVerificationMethod.NONE ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' This got me over the following error: django.urls.exceptions.NoReverseMatch: Reverse for 'account_signup' not found. 'account_signup' is not a valid view function or pattern name But a new error occured: django.urls.exceptions.NoReverseMatch: Reverse for 'account_reset_password' not found. 'account_reset_password' is not a valid view function or pattern name. When I scan the installation directory for this ("account_reset_password") I find it in several places, mostly non template files... So there seems no way to get rid of this error without modifying code... This is nothing one should do - it makes the whole software and its updates unmanageable... So it seems to be a kind of a dead end... Is there any way to get approach (only sso-authorized owners/admins/moderators) working? Kind regards Christian P.S. Sorry for hijacking this thread, but it seems the right place for my questions... :-)

1 month, 4 weeks

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

by Mark Sapiro

On 4/19/19 6:33 PM, kevin(a)coastalaska.org wrote: > We have a couple of people trying to subscribe to our list but receive an error similar to: > {"title": "409 Conflict", "description": "Subscription request already pending"} > > If I try to Mass Subscribe them in Postorius I get this error: > HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' > > In Postorius I don't see them hung up in Subscription requests. Postorius since 1.2.3 does not show subscription requests waiting user confirmation, only those waiting moderator approval. Thus, if the list's subscription policy is confirm or confirm then moderate, the subscribing user will be sent an email requesting confirmation. If the user hasn't answered that email, the request is pending user confirmation, and since 1.2.3, you won't see it in Postorius. [Update: this is fixed in 1.2.4] > What to do? 1) have the user find the confirmation request email and confirm, or 2) wait for the request to expire (default 3 days) 3) using mailman shell or the REST api or direct interaction with the database, find the token and confirm it. A shell example is ``` mailman shell -l your.list.id Welcome to the GNU Mailman shell The variable 'm' is the your.list.id mailing list >>> util = getUtility(IPendings) >>> list(util.find(mlist=m,pend_type='subscription')) ``` This returns a list of items like ('hex_token'), {'token_owner': 'subscriber', 'email': 'user(a)example.com', 'display_name': 'Jane User', 'when': '2019-04-09T01:26:08', 'type': 'subscription', 'list_id': 'your.list.id'}) You then do ``` >>> util.confirm('hex_token') ``` Note that https://gitlab.com/mailman/postorius/issues/314 which was responsible for removing the subs waiting user confirmation from the Postorius listing suggested "there could be a different place to see the ones pending user approval, so that a moderator can look and/or delete those.", but that hasn't been done. [Update: this is fixed in 1.2.4] -- Mark Sapiro mark(a)msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Manual setup - permissions

by Abhilash Raj

On Mon, Sep 23, 2019, at 3:02 AM, Tobias Hachmer via Mailman-users wrote: > Hi Mark, > > thanks for your response. > > On 9/23/19 1:29 AM, Mark Sapiro wrote: > > On 9/22/19 2:11 AM, Tobias Hachmer via Mailman-users wrote: > >> > >> Now, running the scheduled tasks (which run from user+group "nginx") for > >> django I ran into permission problems, because the nginx user can't > >> access/write to the needed files in /opt/mailman3/core/... > >> > >> I would appreciate any hints how to run the different peaces of mailman3 > >> with the correct user/groups/permissions. > > > > > > Set up everything as user:group mailman3:mailman3. I.e., > > > > chown -R mailman3:mailman3 /opt/mailman3/web > > > > and set the uwsgi service to drop privileges to user+group "mailman3". > > So simple, now the scheduled tasks are working, but the whole web > service did not work because the web server user nginx can't access and > write to the uwsgi socket anymore /opt/mailman3/web/project/run/uwsgi.sock. > > # chown -R nginx:mailman3 /opt/mailman3/web > > This works for all. But isn't it a security risk that e.g. manage.py and > settings.py is read- and writeable by the webserver? You just need them to be readable, not writable. You could possibly use xattrs to do just grant read privs. You could also configure uwsgi to create a socket somewhere nginx can read it, `/var/run/uwsgi.sock` should be good enough. You can in theory also try https://uwsgi-docs.readthedocs.io/en/latest/Systemd.html for systemd setup in which case you don't have to manually create sockets as systemd can do that for you. > > Regards, > Tobias > > > _______________________________________________ > 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:* > * signature.asc -- thanks, Abhilash Raj (maxking)

5 years, 11 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Ralph Weber

To close the loop on this topic... Comments received directly from one of the people who developed the AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively established that AWS Mailman is *not* intended to interact with AWS SES when receiving email messages. AWS Mailman is designed to receive its email messages via Postfix. With many thanks to all those on this list who corroborated "Mailman and SES don't mix" mantra here, we are taking the advice received from so many sources and ending efforts to do the impossible. All the best, .Ralph On 3/20/2021 8:23 AM, Stephen J. Turnbull wrote: > Ralph Weber writes: > > > I am moving the website www.t10.org from a private/corporate VM to > > AWS EC2s. > > > > For many years, t10.org has had very happy results with using > > Mailman 2 for its email reflector, and I have no real concerns > > about moving to Mailman 3. My bugbear is the fact that I need the > > following mixed bag of incoming email addresses to work in concert > > with each other to receive and handle emails. > > > > > t10(a)t10.org (Primary Mailman Reflector) > > > chair(a)t10.org (Mailman Reflector to direct messages to the T10 > > > chair and his designates) > > * docs(a)t10.org (document posting mechanics - serviced by a small > > mountain of home-grown code code > > * bbs(a)t10.org (other publicly accessible services - serviced by > > code that recalls the days when everything as done on a Bulletin > > Board System, BBS) > > This isn't a Mailman question, to be frank. As Abhilash points out, > Mailman doesn't care about other mailboxes served by its host (unless > they conflict with list names or adinistrative addresses derived from > list names, which evidently yours do not). It's a question about the > mail service at AWS. I've not seen any documentation in our project > about setting up at AWS; I don't know anybody who has done so. (I > haven't looked for either though.) > > I took a quick look for AWS SES documentation. They don't seem to > have any real documentation online for the general public, only lists > of features. They also seem to be very focused on sending rather than > receiving. Much talk of how much mail you can send, bulk emailing, > statistics on responses, and the like. None about setting up for > incoming mail. > > Probably I could get access to online help if I signed up for a free > account, but that's above my pay grade. > > > My best guess is that the AWS Simple Email Service (SES) needs to > > sit in front of both Mailman and the home-grown code, > > I don't know if AWS provides an alternative Complicated Email Service, > but yes, something like SES is going to have to sit in front of the > various mailboxes. > > Mailman itself has a certain amount of capability to deal with the > main email protocols, but it is definitely not capable of replacing > the main mail server. For security reasons I would definitely advise > against any Mailman 3 presence directly on the Internet. It was > designed on the assumption that it would talk to the Internet via a > standard mail server, Postorius (for administration), and HyperKitty > (for mail archives)[1], and occasionally to admins logging in with shell > accounts. > > > All available evidence read to date > > URLs, please. As I wrote above, Amazon's documentation is at best not > very discoverable. > > > suggests that the default AWS installation > > Whose default installation of Mailman? AWS's? Typical 3rd party > configurations? > > > of Mailman 3 assumes that Mailman 3 is the *only* receiver of > > emails in the configuration. > > That's possible, but it's likely an artifact of the application -- I > would expect that many who host Mailman on AWS do so to isolate > Mailman from other services they provide. So it seems reasonable that > in many such installations Mailman is *the* service for that instance. > > But mail servers are designed to be many inputs, many outputs > services. If SES itself is as restricted as you fear, surely AWS > provides an alternative, more powerful mail service. I can imagine > quite a few restrictions, other than the backing application, on the > SES that Amazon *might* impose. But without access to documentation, > we can't say much. > > > Or... Hercules may have already cleaned the Augean Stables, and > > left behind a AWS Lambda function that can serve as a keystone > > puzzle piece for solving my dilemma. > > Good luck on that. I don't know of any, but that would be a quick > solution for you. I hope somebody here knows more. As evidenced by > Andrew's post, there are folks thinking about it, so maybe somebody's > actually tried -- anybody? Successes? Pitfalls to watch for? > > The other issue Andrew mentions could be important. Since Solar Winds > I'm seeing daily attempts to access my O365 server (nonexistent) from > AWS. Given the size of AWS, I think they probably actually do a good > job of keeping felonious behavior to a minimum[2], but a lot of folks > I know are happy to cut off huge netblocks until somebody they know > actually complains. :-( > > Footnotes: > [1] Or more precisely, some webservice providing those services > mediating between the Internet and Mailman sitting cozily behind a > firewall. > > [2] DigitalOcean, on the other hand, is accumulating blocked /24s, > and even /16s, at my firewall. But that's another story.

4 years, 5 months

[MM3-users] Re: Mm3 - new adventure

by Mark Sapiro

On 03/14/2017 09:14 AM, SP2L wrote: > > Lately started adventurous journey with Mailman3 > which is way, way different already from the beginning. > > Used Mailman bundler to install GNU Mailman, Postorius and HyperKitty > testing instance in virtual environment, mainly relaying on belows recipe: > > https://gitlab.com/mailman/mailman-bundler/ mailman-bundler is out of date and deprecated. You might find <https://wiki.list.org/x/17891998> of interest. > Present status. > > Above trio and MySQLServer are "talking" to each other > but because there isproper database on MySQLServer > I am facing strange and unexpected issues, Hi! > > Executing last two commands: > > (venv)$ ./bin/mailman start > (venv)$ ./bin/mailman-web-django-admin runserver 0.0.0.0:8000 & > > I see Postorius and HyperKitty up & runningbut... > > Belowvery condensed messages from the console: > > > /HyperKitty/ > > DEBUG = False > > [12/Mar/2017 18:59:43] "GET /archives/ HTTP/1.1" 200 8002 > WARNING Not Found: > /static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css ... Have you run the script that bundler installs as bin/mailman-post-update? > /mailman3/ > > DEBUG = False > > Server Error (500) > > > DEBUG = True > > HTTP Error 500: A server error occurred. Please contact the administrator. > > Exception Location: > /var/lib/mailman3/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py > in call, line 109 > > Then VERY, verylong list... Without knowing what the exception was and at least the start of the traceback, it's hard to say what this might be. > By means of PhpMyAdmin I created manually mailman3 database > and few tables (looking at 0001_initial.py) , but it is not working O.K. > This handmade table is not doing it's job. You shouldn't need to do this. If you have the proper settings and credentials in the DATABASES setting in mailman-web/settings_local.py and the [database] section in deployment/mailman.cfg, the tables should be created 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, 6 months

[MM3-users] Re: Postorius Suggestion: Give owner a view of all users of all owned lists

by Andreas Vetter

[Forgot reply to list] ---------- Forwarded Message ---------- Thank you Stephen for your questions. I have to admit that I thought about a quick and dirty solution, but you are right, it would not be optimal. Lets see: Stephen J. Turnbull wrote: > Andreas Vetter writes: > > it would be real great if owners that own several lists, but are > > not superusers, can see all users of all *their* lists and manage > > them. A down-"selected" version of the superusers view. > > > > Would that be possible? > > Possible, yes. I don't know how to do it well enough to add to our > distribution. > > Note that owners can't actually manage users -- that really does need > to be a superuser. Owners can manage subscriptions to the lists they > own. Agreed, "manage subscriptions" is what owners would need. A list of all addresses subscribed to all lists owned by the logged in person. > So first we'd want to create a new "Subscriptions" item for the > top menu; the "Users" item isn't appropriate. I'm not sure who that > item should be visible to. Most likely only owners, because > individuals already have ways to see all their subscriptions, and it's > not obvious they would want the same presentation as your superowners. Owner is the primary target group for that. But since it should be a tool for managing subscriptions in a simple way, it might also be of interest for superusers. For me as a superuser it would make life easier. > Then you'd iterate over the logged-in owner's lists and collect all of > the subscriptions. I guess you'd want them to be organized by address > rather than by list. By User is out, I think -- owners can't normally > see Users, and I'm unhappy abou the privacy implications of being able > to correlate nole(a)alset.com with head(a)dodgy.gov in general, although I > realize it's not a problem in your setting. Ah, I see the problem and agree: So, the presentation should have a sorted and searchable list of addresses and a Button next to each address, maybe labeled "Subscriptions". > Without a more complete specification of what your users need, and the > presentation they'd want to see, I personally am unwilling to go > farther than those comments. Maybe one of the other devs feels > differently. The presentation given when above "Subscriptions" Button is clicked should contain the address as kind of Headline. Then a table of all lists of the logged in owner and next to each mailing list an indication, if the address is subscribed or not and a Button to toggle subscription/unsubscription. May be a single Toggle Button or (maybe better) two buttons, a suscribe and a unsubscribe button, where one is greyed out.b In our case Delivery Status and Delivery Mode are not interesting, but others might appreciate it. In addition my owners would like to have a "unsubscribe from all my lists" button. And a "subscribe to all my lists" button. This might be visually nicer, when having the two-button approach above. In our case we would want to (un-)subscribe the address in a "do it, don't ask anyone" fashion, but maybe this is not a good idea in general. What do you think? > Also, "domain owner" is way under-implemented currently. For the > hierarchical situation you outline, all the problems go away for > domain owners. Of course then you'd need to split out lists by > domain, but to me that's a small cost to preserve sanity in the > structure. Yes, I agree, but policy here is to get rid of subdomains, and that falls on our feet now. -- Mit freundlichen Gruessen, Andreas Vetter

6 months, 1 week

[MM3-users] Re: hyperkitty_import Unicode Errors

by Stephen J Turnbull

On 2023-05-07 07:39 Mark Sapiro writes: > On 5/6/23 11:27, Dave Hall via Mailman-users wrote: >> django.db.utils.OperationalError: (1366, "Incorrect string value: >> '\\xE1\\x90\\xA7\\x0A\\x0AO...' for column >> `mailman3web`.`hyperkitty_email`.`content` at row 1") >> >> Is there a known cause for this? Almost always nonconforming user clients. You write "frequently", but I'm guessing it's maybe 1% or 2% of all the messages, right? I suspect it's a particular author or institution using such a client. >> Is it fixed in some release more recent than 0+20180916? This is almost surely not something we can fix. Based on the error, it's in third party code (Django) that we import. It's possible we could provide a more explanatory message, but the only thing we can sensibly do is hold the message for an admin to edit it by hand. As long as the text in question and the Content-Type header aren't too sensitive, we can help with identifying charset (often UTF-8 as Mark suggests but why someone would be encoding FINAL MIDDLE DOT is a mystery to me). > I'm not sure what's going on here. My first thought is the database is > MySQL or MariaDB and this is a 4-byte UTF-8 encoding and the database > column charset definition is utf8 and not utf8mb4, but > '\\xE1\\x90\\xA7\\x0A\\x0A' is the 3-byte UTF-8 encoding for CANADIAN > SYLLABICS FINAL MIDDLE DOT ('\\xE1\\x90\\xA7') followed by two > newlines. so I'm not sure what the issue is. I'm guessing home-made client, possibly Asian or a spammer, which provides no content-type header. Even today I see raw 8-bit encoded text without an encoding spec from legitimate Japanese and Chinese sources, and of course with spammers all bets are off -- they might even do it deliberately to crash filters. -- University of Tsukuba　　　　　　　　　　　　 Faculty of Policy and Planning Sciences Tennodai 1-1-1, Tsukuba 305-8573 JAPAN tel/fax: +81-29-853-5091 turnbull(a)sk.tsukuba.ac.jp 　　　　　　　　　　　　　　https://turnbull.sk.tsukuba.ac.jp/

2 years, 4 months

[MM3-users] Re: Pd CRON mailman gatenews

by Pierre Malard

Hello, That’s going again! If I understood your advice correctly, if we do not have lists for which the gateway to the mail is set to yes, we can comment on the CRON "gatenew". This is what I will do > Le 17 mars 2023 à 07:50, Pierre Malard via Mailman-users <mailman-users(a)mailman3.org> a écrit : > > Hi Mark, > > Thanks for your answer and your lead > >> Le 16 mars 2023 à 18:34, Mark Sapiro <mark(a)msapiro.net> a écrit : >> >> On 3/15/23 23:31, Pierre Malard via Mailman-users wrote: >> >>> File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 502, in _read >>> with open(self._lockfile) as fp: >>> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' >>> —————————————————————————————————————————————————— >>> CRON content: >>> —————————————————————————————————————————————————— >> ... >>> # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured >>> */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi >> >> Do you have any list's for which Gateway to mail is set to yes or for which there is a Linked Newsgroup?. If not, running gatenews is superfluous. > > No, we don’t have > >> >>> I thought, given the last line, a problem of rights. It is not the case ! The directory and the files contained in /var/lib/mailman3/locks belong to the user "list". >>> When I run "/usr/bin/mailman gatenews" by hand everything is correct. >> >> Can you do `sudo -u list cat /var/lib/mailman3/locks/dbcreate.lck`. If that succeeds, this may be a SELinux or other security manager issue. > > Their is no file with this name! > listesman:~# ls -ld /var/lib/mailman3/locks/dbcreate.lck > ls: impossible d'accéder à '/var/lib/mailman3/locks/dbcreate.lck': Aucun fichier ou dossier de ce type > >> >> >>> The questions I have are these: >>> We have 8000 files "dbcreate.lck..." in the directory "/var/lib/mailman3/locks". >>> What are they for? >>> Can we delete them? >> >> They are probably all orphaned lock files due the the gatenews failure. To be certain that none are current you could stop Mailman core. Then with Mailman core stopped, any files in /var/lib/mailman3/locks are orphaned and should be removed. > > Ok, is done. > > We will see today if it continues > >> >>> We have 2 files "master.lck..." dated from the day after tomorrow ! >>> What is this date? >>> Aren't these files the problem? >> >> >> Those files are normal. They are the master lock that prevents Mailman core from being started when it's already running. The future date is the way flufl.lock handles lock lifetimes. Locks when set have a lifetime, after which they can be broken. This is implemented in flufl.lock by setting the file's date that far into the future. > > Ok, that’s smart :-) > >> >> -- >> Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> >> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> >> >> This message sent to plm(a)teledetection.fr <mailto:plm@teledetection.fr> > > -- > Pierre Malard > Responsable architectures système CDS DINAMIS/THEIA Montpellier > IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra > Maison de la Télédétection > 500 rue Jean-François Breton > 34093 Montpellier Cx 5 > France > > « Je n'ai jamais séparé la République des idées de justice sociale, > sans laquelle elle n'est qu'un mot » > Jean Jaures - 1887 > |\ _,,,---,,_ > /,`.-'`' -. ;-;;,_ > |,4- ) )-,_. ,\ ( `'-' > '---''(_/--' `-'\_) πr > > perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' > - --> Ce message n’engage que son auteur <-- > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to plm(a)teledetection.fr <mailto:plm@teledetection.fr> -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « La façon de donner vaut mieux que ce que l'on donne » Pierre Corneille (1606-1684) - Le menteur |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 6 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 Sapiro

On 4/25/23 2:14 PM, Andrew Hodgson wrote: > Mark Sapiro wrote: > >> 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. > > Thanks, I ran this script and it did delete a load of Mailman users, I got output similar to this: > <User "" (47600399411039288509336192576257642185) at 0x7fb17a6a35e0> deleted from Mailman > > Why aren't we seeing the actual address here? That was a choice I made. you could change ``` with transaction(): user_manager.delete_user(mm_user) print(f'{mm_user} deleted from Mailman') ``` to ``` with transaction(): try: email = user.preferred_address.email except AttributeError: email = 'no_preferred_address' user_manager.delete_user(mm_user) print(f'{email} deleted from Mailman') ``` to display the email address from the user's preferred_address if the user has one. All users should have one, but I've seen cases where there isn't one. It could also be ``` email = user.addresses[0].email ``` which might be better. In the above case, the empty string, "", is the user's display_name which in this case is empty, and the number in parentheses is the UUID of the user expressed as a decimal integer which isn't really useful. My thought was the display_name was as useful as anything, but obviously not if it's empty. I actually started with the preferred_address.email code above, but in testing, I got the 'no_preferred_address' result with the one deleted user so I, perhaps erroneously, went with the representation of the user. I'll probably update the script again. -- 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: Installing mailman 3

by Rafael Mora

Hi Abhilash, I'm trying to use Mailman 3 on my centos 7 virtual machine. Those steps I wrote are from websites, the last console instructions are mine. I don't use ubuntu, I use centos 7. When I run the start command I get this: (venv3) [root@localhost mailman]# mailman start > Starting Mailman's master runner > /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': > [Errno > 2] No such file or directory What can I do? Thank you El mar., 11 jul. 2017 a las 12:31, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > Hi Rafael, > > On Tue, Jul 11, 2017, at 07:32 AM, Rafael Mora wrote: > > Hello, > > > > I want to install mailman 3 in a centos 7 virtual machine. I'm following > > these steps and I cannot make it work: > > I am wondering if you are interested to setup a development environment > or use Mailman 3? > These instructions below are for working on Mailman, if you just need to > deploy, instructions here[1] would be the best. > > > 1. `cd ~` > > 2. `git clone https://gitlab.com/mailman/mailman.git` > <https://gitlab.com/mailman/mailman.git> > > 3. `cd mailman` > > 4. `virtualenv -p python3 venv` > > 5. `source venv/bin/activate` > > 6. `python setup.py develop` > > 7. I am pretty sure this setup command will place a configuration file > > into > > `~/mailman/var/etc/mailman.cfg`. Edit this file. > > > https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > 8. `mailman info` can confirm which configuration file is in use > > 9. `mailman start` will start up Mailman 3 Core. This is what the parent > > background process command looks like in `ps -ef`: > > `/home/ubuntu/mailman/venv/bin/python > > /home/ubuntu/mailman/venv/bin/master > > -C /home/ubuntu/mailman/var/etc/mailman.cfg` > > Looks like you are working as the ubuntu user here and the the > virtualenv that you created exists at `/home/ubuntu/mailman/venv`. > > > I also tried the steps on the website > > https://wiki.list.org/DEV/SetupDevEnvironment > > but it doesn't work either > > > > What do you suggest? > > > > This is what I get from console: > > > > > > [root@localhost ~]# cd dev/ > > > > [root@localhost dev]# cd mailman/ > > > > [root@localhost mailman]# source venv3/bin/activate > > Why do you try to user a different venv as a root user here? If you'd > just try: > > $ source /home/ubuntu/mailman/venv/bin/activate > > and then try > > $ mailman start > > things would work! > > However, this would be a different instance of mailman and would create > the new configuration (and the entire var directory) at the directory > you run this command from. If you want to inhibit this, you can either > use the -C flag, or set MAILMAN_CONFIG_FILE environment variable to > point to your one single configuration file. > > > > > (venv3) [root@localhost mailman]# cd mailman/ > > > > (venv3) [root@localhost mailman]# ls > > conf.py COPYING data README.rst src > > unittest.cfg > > contrib coverage.ini MANIFEST.in setup.cfg template.py > > copybump.py cron port_me setup.py tox.ini > > > > (venv3) [root@localhost mailman]# cd .. > > > > (venv3) [root@localhost mailman]# mailman start > > Starting Mailman's master runner > > /root/dev/mailman/venv3/bin/python: can't open file '/sbin/master': > > [Errno > > 2] No such file or directory > > > > (venv3) [root@localhost mailman]# > > > > Thank you > > -- > > Hope that helps! > > [1]: http://docs.mailman3.org/en/latest/prodsetup.html > > -- > thanks, > Abhilash Raj > _______________________________________________ > 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, 2 months

[MM3-users] Re: installing mailman3 core

by Mark Sapiro

On 5/29/20 7:41 AM, Ralf Wiegand wrote: > Mark - What is the difference between to two install methods? What are > my pros and cons? Installing from the GitLab repository will get the latest development version, however, you can also install from this repository via pip and pick a tag or commit to install <https://pip.pypa.io/en/stable/reference/pip_install/#git> `pip install mailman3` will install the latest released version. As of this writing, that's 3.3.1, so ``` pip install mailman3 ``` and ``` pip install git+https://gitlab.com/mailman/mailman@3.3.1 ``` should give the same result although the former installs from PyPI and the latter from GitLab. The advantage to installing the latest version from GitLab is you get features and fixes that haven't been released yet. The disadvantage is you might get new bugs, although the servers that support this list and all the Mailman 3 @python.org lists are generally running the latest GitLab versions, so any serious issues will be quickly found and fixed. > I have been using this: > >>>>> > > |# Note: if we are using a dedicated postgresql database server, all > postgresql changes need to be done on the actual postgresql server.| > |>>>| > |sudo yum install postgresql-server postgresql-contrib| > |sudo postgresql-setup initdb| > |sudo systemctl start postgresql| > |sudo systemctl enable postgresql| > |sudo -u postgres psql -c ||"SELECT version();"| > |sudo useradd -c ||"Mailman User"| |-s /bin/bash -m mailman| > |sudo -u postgres create role mailman;| > |sudo -u postgres createdb -O $USER mailman| > |sudo -u postgres psql -c ||"grant all privileges on database mailman to > mailman;"| > |sudo -u postgres psql -c ||"ALTER ROLE mailman WITH PASSWORD > 'secret123';"| > |sudo -u postgres psql -c ||"ALTER ROLE "||mailman||" WITH LOGIN;"| > |sudo echo ||"listen_addresses = '*' "| |>> > /var/lib/pgsql/10/data/postgresql.conf| > |sudo echo ||"# The user mailman will be able to access all databases > from a trusted location (any) without a password"| |>> > /var/lib/pgsql/data/pg_hba.conf| > |sudo echo ||"host all mailman 0.0.0.0/0 > trust"| |>> /var/lib/pgsql/data/pg_hba.conf| > |sudo systemctl restart postgresql| > |sudo ss -nlt | grep 5432| > |<<<| > |sudo yum install python36* --skip-broken -y| > |# check make sure you have both versions| > |sudo python --version| > |Python 2.7.5| > |sudo python3 --version| > |Python 3.6.8| > |sudo pip3 install psycopg2-binary| > |sudo chown mailman.mailman /opt/mailman| > |sudo chmod 755 /opt/mailman| > |# NOTE: The first initial mailman3 core setup has to be done manually.| > |# This is a important step to ensure the user "mailman" will run the > actual mailman3 application and not root.| > |# switch to user mailman| > |mailman# cd /opt/mailman| > |mailman# git clone https:||//gitlab.com/mailman/mailman.git| This gets the head of the GitLab master branch. > |mailman# cat <<EOT >> /opt/mailman/mailman/src/mailman/config/mailman.cfg| > |[devmode]| > |enabled: yes| > |recipient: root@localhost| > |[webservice]| > |hostname: localhost| > |port: 8001| > |show_tracebacks: yes| > |use_https: yes| > |[mta]| > |incoming: mailman.mta.postfix.LMTP| > |outgoing: mailman.mta.deliver.deliver| > |lmtp_host: localhost| > |lmtp_port: 8024| > |smtp_host: localhost| > |smtp_port: 25| > |[database]| > |class||: mailman.database.postgresql.PostgreSQLDatabase| > |url: postgres:||//mailman:secret123@<IP-ADDRESS or FQDN>/mailman| > |EOT| > |mailman# python3.6 -m venv venv-3.6| > |>>| > |mailman# source venv-3.6/bin/activate| > |(venv-3.6) [mailman@empire mailman]$ cd mailman| > |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| > |(venv-3.6) [mailman@empire mailman]$ mailman info| > |<<| > | > | > | > | > |So I was told I don't have to do this, I can just simple do (rhel7) > | > |yum install pyhton3| > |pip install mailman| This gets the latest release from PyPI Other than that, you still have to do the configuration and install some dependencies as in the first method. -- 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: users leaking across virtual hosts

by Mark Sapiro

On 3/25/22 12:49, Stanisław Findeisen via Mailman-users wrote: > Hi > > We are hosting several virtual hosts (mail host : web host is a 1:1 mapping with identical names), works fine, but it looks user accounts are somehow global, i.e. registering a new user in a new virtual host doesn't work if the user name or e-mail address are already in use in another virtual host. This happens on the Hyperkitty sign-up page: /accounts/signup/ , with the errors being "A user is already registered with this e-mail address." and "A user with that username already exists.". I am assuming this is a well-known limitation, which would require a serious internal redesign to fix; correct? These user registrations and logins are Django things so yes, they are global within the Django instance. > I was able to successfully login in the browser to a vhost using my user credentials from the original vhost (the one where the account was created) (the password was not auto-filled, of course, because of a different domain name). But how safe is this? How about subscribing to lists, posting etc.? Is this going to mess things up somehow? I don't think it's a problem. The user is a Django user for the web UI. The fact that there is or isn't a Django user with a particular email address has nothing to do with whether that address can post to a list. The user can subscribe to lists or not. The user can manage her subscriptions for lists to which she is subscribed and can subscribe to lists or not as controlled by list settings. Basically, registering as a user allows you to authenticate as that user for the web UI only. If you wanted to separate these user registrations by vhost, you'd need to run separate Django instances for each vhost, but I don't see a need to do that. -- 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: integrating mm3 with postfix / lmtp

by Mark Sapiro

On 10/25/2017 05:41 PM, Fabian A. Santiago wrote: > > No to the domains part and I think virtual alias maps is needed: > > mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/trivial-rewrite[19445]: warning: do not list domain xxx in BOTH virtual_mailbox_domains and relay_domains > Oct 25 20:39:19 mail postfix/submission/smtpd[19441]: NOQUEUE: reject: RCPT from pool-108-53-239-102.nwrknj.fios.verizon.net[108.53.239.102]: 550 5.1.1 <test123@xxx>: Recipient address rejected: User unknown in virtual mailbox table; from=<fsantiago@xxx> to=<test123@xxx> proto=ESMTP helo=<[10.0.0.29]> (above slightly sanitized for return to the list) The issue here is your list domain cannot be a virtual_mailbox_domain or a virtual_alias_domain. I have the same issue on mail.python.org where we have both Mailman 2 and Mailman 3 lists @python.org. and python.org is a virtual_alias_domain. I have a group of MRs for a branch that implements "alias_domains" to deal with this. Basically it works by creating another (virtual_alias_maps) postfix_vmap mapping to map list addresses @python.org to addresses @x.python.org. Then the postfix_domains and postfix_lmtp maps have the x.python.org domain and there is a patch to mailman/runners/lmtp.py to map the x.python.org domain back to python.org. The various MRs are <https://gitlab.com/mailman/mailman/merge_requests/202> for the core, <https://gitlab.com/mailman/mailmanclient/merge_requests/18> for the REST bindings used by Postorius and <https://gitlab.com/mailman/postorius/merge_requests/186> to be able to set an alias_domain via Postorius. That's not all implemented at mail.python.org. What's there is the basic Postfix config, a bash script the generate the new mappings from the old and a simple patch to mailman/runners/lmtp.py. So, the bottom line is it can be done and it's in process, but it won't really be supported until Mailman 3.2. In the mean time, you just need to have a separate domain for your lists that isn't a virtual_*_domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

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

by Mark Sapiro

On 6/22/20 12:21 PM, Ruth Ivimey-Cook wrote: > > The localhost address is coming in via the hosts file, which is a > relatively standard practice IMO. I could change it, but then perhaps > other things would not work. I would prefer to be able to specify what I > need. There are also things like systemd-resolvd which will do the > localhost-substitution for you even if /etc/hosts doesn't. I have done further testing. See my comment at <https://gitlab.com/mailman/mailman/-/issues/735#note_366074014>. You need to set hostname: in mailman.cfg to the actual external IP address of the Mailman host machine or to a name which resolves to that IP both internally and externally, and also set that host name/IP in the MAILMAN_REST_API_URL setting on the Postorius machine. > I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and > changing the cfg file hostname back to the full name of the host, and > that now works!! -- in that the problem I showed earlier is gone. Remove that patch and do the above. > However I then get another issue. From the mailman.log file I now see in > the last few lines. For clarity I've numbered them like this "{1}": > > {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" > "GNU Mailman REST client v3.3.1" > {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk > HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" > {3} [22/Jun/2020:00:58:24 +0000] "GET > /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 > HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" > > At this point the browser screen reports "Something went wrong" and the > message "HTTP Error 404: {"title": "404 Not Found"}" Make the above changes and see if that solves this. If not, let us know and we'll try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Pd CRON mailman gatenews

by Mark Sapiro

On 3/15/23 23:31, Pierre Malard via Mailman-users wrote: > File "/usr/lib/python3/dist-packages/flufl/lock/_lockfile.py", line 502, in _read > with open(self._lockfile) as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/locks/dbcreate.lck' > —————————————————————————————————————————————————— > > CRON content: > —————————————————————————————————————————————————— ... > # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured > */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi Do you have any list's for which Gateway to mail is set to yes or for which there is a Linked Newsgroup?. If not, running gatenews is superfluous. > I thought, given the last line, a problem of rights. It is not the case ! The directory and the files contained in /var/lib/mailman3/locks belong to the user "list". > When I run "/usr/bin/mailman gatenews" by hand everything is correct. Can you do `sudo -u list cat /var/lib/mailman3/locks/dbcreate.lck`. If that succeeds, this may be a SELinux or other security manager issue. > The questions I have are these: > We have 8000 files "dbcreate.lck..." in the directory "/var/lib/mailman3/locks". > What are they for? > Can we delete them? They are probably all orphaned lock files due the the gatenews failure. To be certain that none are current you could stop Mailman core. Then with Mailman core stopped, any files in /var/lib/mailman3/locks are orphaned and should be removed. > We have 2 files "master.lck..." dated from the day after tomorrow ! > What is this date? > Aren't these files the problem? Those files are normal. They are the master lock that prevents Mailman core from being started when it's already running. The future date is the way flufl.lock handles lock lifetimes. Locks when set have a lifetime, after which they can be broken. This is implemented in flufl.lock by setting the file's date that far into the future. -- 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: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 12:33 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 20:07 +0000, David Partain via Mailman-users > wrote: >> On Tue, 2021-03-02 at 19:56 +0000, David Partain via Mailman-users >> wrote: >> >> I assume this is because /usr/share/mailman3-web/manage.py, which >> has: >> >> '#!/usr/bin/env python' >> >> resolves to Python 2.7.17. >> >> Should I could try changing that to '#!/usr/bin/env python3' and see >> what happens? :) I could also uninstall python2 but that becomes >> more of a nail-biter... NO! Do not do that. >> I can report that the above doesn't help. Neither does just making >> /usr/bin/python link to /usr/bin/python3.6 >> >> I still get errors in mailman-web.log pointing to 2.7 as shown in my >> previous mail. > > If I force the issue by linking /usr/bin/python to /usr/bin/python3.6, > I start seeing: > > ModuleNotFoundError: No module named 'hyperkitty > > in mailman-web.log. > > I know next to nothing about python. Is > > pip install hyperkitty > > the right answer? No. > I have the following installed now: > > # dpkg -l | grep hyperkitty > python-django-hyperkitty 1.1.4-4 > python3-mailman-hyperkitty 1.1.0-4 > > but this version of Ubuntu has no python3-django-hyperkitty or I'd just > try installing that... This is all because you are using the Ubuntu 18.04 package which is about 4 years out of date and is from the era where HyperKitty, Postorius and django_mailman3 still ran under Python 2.1.7. Unless you want to remove the Ubuntu package and install everything with pip, you need to just stick with what you have that at least partly works and we'll try to determine how to fix the utf8mb4 issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Unable to get mailman3 working on Ubuntu 20.04 LTS

by John Covici

OK, thanks, I will check it out and see how far I get. One thing, when you start a container, you can give it a name, so you would not need that long id string. On Fri, 29 Oct 2021 00:26:07 -0400, Shawn Heisey wrote: > > On 10/27/2021 9:51 PM, John Covici wrote: > > I am interested in your docr instructions. I don't use postfix, > > instead I use sendmail, but I think I can figure that out, but I have > > been having lots of problems installing without docr, and I do have > > apache, so this would be great. Send off list if you think that would > > not be of general use. > > The instructions found here are most of what is needed: > > https://github.com/maxking/docker-mailman/#running > > Here's the issue where I provided my Apache config: > > https://github.com/maxking/docker-mailman/issues/525 > > For each of my mailing lists, I created the list and then > imported a mailman 2.1 config. I had problems with the footer > being appended to list messages ... it took me a while to figure > out how to fix that! You have to delete the footer config file, > restart the container, and then if the resulting default footer > is insufficent, use the admin web page to redefine it. > > Instructions for exim and postfix are included on the project > page. I haven't used sendmail in many years, so I wouldn't have > any idea how to get that working. Even when I was using it, I > found the config to be extremely arcane and difficult. > > Thanks, > Shawn > _______________________________________________ > 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

3 years, 10 months

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

by Mark Sapiro

On 3/12/21 7:36 PM, John Covici wrote: > Hi. I am having a great deal of difficulty installing mailman3 using > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to > mailman3. > > What I have done so far is to install the mailman3 packages from my > repository and got this: > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman > version 3.3.2 (apparently the core), postorius version 1.3.3 and > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed. Are these gentoo packages? If so, I have no idea how they are configured. > Now trying to read your documentation, it seems it wants me to > reinstall some packages using pip in the home directory of the mailman > user in a python virtual environment, that was the first thing. But I > would like to avoid multiple package managers wherever possible -- > gentoo is already a lot of maintainance without dealing with pip's > maintainance. The binaries also seem to be different from my gentoo packages. Our documantation generally covers installing from source. If you are installing gentoo packages, you should be looking at gentoo docs and going to gentoo for help. We recommend installing Mailman and the web components in a virtualenv, but it is not a requirement. We also suggest that postgresql is a better choice than MariaDB. > So, how do I proceed with getting mailman3 up and working, configuring > the database, configs, etc and I guess after doing that upgrading > mailman2 and getting sendmail to interface properly with mailman3? Importing lists from Mailman 2 is done with the `mailman import21` command. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>. Importing archives is done with the Django management `hyperkitty_import` command. See <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…> For sendmail, see <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Abhilash Raj

I am a bit late to this thread, but I am going to try to respond to some of the points raised in the thread. On 10/19/20 7:42 PM, Brian Carpenter wrote: > On 10/19/20 10:23 PM, Mark Sapiro wrote: >> And the import21 created the user and address records for this user. > Does the same thing for a new subscriber as well. So there is no pathway > to change a real name that is associated with an email address. None. > Zilch. Yes, this is a limitation of the REST API, the display_name attribute can't be updated. Hence, Postorius can't provide a way for anyone to update the name. I have opened an issue for this[1] and I think it should be allowed. [1]: https://gitlab.com/mailman/mailman/-/issues/786 > I am admin for a list. Users got subscribed with bulk import during > transition from MM2 to MM3. > So in a sense I am responsible for adding these to a db. BUT there is > no way for me to remove them. Only mailman admin with access to the db > can do it manually. The fact that a user's memberships & User as an entity that owns email address is a design choice that Mailman developers made after some experience of using and administering Mailing lists running on Mailman 2. It was annoying to have to manage several different passwords and accounts to manage membership on same mailing list server. The policy decision that Mailman would allow a user/address to exist even if there are no subscriptions on it isn't un-resonable in certain environments and maybe it is in some. I don't think anyone here denies that either of those behavior could be an expectation from someone using Mailman. But Mailman is an open source project with decent amount of extensibility via HTTP API & Python plugin system. If the default policy doesn't match the expectations of some users, I don't think it is difficult to cleanup users/address with 0 subscriptions in a nightly cron script. It is trivial with some basic scripting and we are happy to help out with such a mechanism. I wouldn't be opposed to directly adding a command in Core that lets you clean up all sorts of stuff. On Wed, Oct 21, 2020, at 10:20 AM, Apollinaris Schöll wrote: > There might be a handful of these. > > But the bigger problem is a user can’t be removed entirely. > > User can delete account and unsubscribe from all lists. But the email > and user name is still kept in the db. Just tested with Affinity > List admin can’t do it either. Front-ends like Affinity should be able to implement such a policy by checking subscriptions of an address on every un-subscription call and delete the user & address if it comes out to be 0. The API is documented here[2], but if there are gaps in there like I mentioned above in my email, please open issues so we know about them. [2]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > I think the correct action is to remove all records if a email is > unsubscribed from all lists and that user has not registered for an > account. > If a user has registered for an account all information including > display name must be removed from that particular list subscription. > It should not matter if a user unsubscribes or a list admin > unsubscribes. There shouldn’t be any data kept. Also, like mentioned above, as a list admin, you can request the Site Admin to get the address fully scrubbed or if this is an expectation from all list admins, the Site Admin has the ability to automate such a task. The fact the Mailman doesn't do it by default is because the definition of "correct" action is different. User should have the ability to delete themselves from the system and if it doesn't wipe everything yet from database, it should be considered a bug in Postorius and be fixed. Postorius track users separately than Core, so the it should make sure to delete in both places and there are appropriate APIs in core to delete Users and Addresses. Now, the ability in Postorius to edit the display_name. The side effect of the model where User is a Site level thing, makes it impossible to customize user's display_name on a per-list basis, for both list admin and the user themselves. That is a trade-off and it is possible that there were use-cases where that was desirable in Mailman 2, but with the superior subscription management functionality in Postorius, I feel the decision is justified. I respect that some of y'all think that it probably isn't if it doesn't suit you particular use cases. From the thread, I gather than folks mostly agree that a list admin shouldn't be allowed to edit a user's display name. Site Admins however should be able to edit that, which brings me to next point. Like Mark brought up, there is definitely a big missing feature of User management in Postorius. This future management page would be for Site Admins (Superusers) to manage Users and have the ability to change pretty much everything about users including their addresses, memberships and preferences and also be able to wipe off the users from all the databases if they want to. If there are more features than that which folks think should be a part of this, please feel free to add to it. As it is hopefully implied from the description, it is a big task and needs substantial chunk of time, part of which this hasn't been picked up yet. > > > > > > > > On Oct 21, 2020, at 1:43 AM, Jörg Schulz <info(a)joergschulz.de> wrote: > > > > So, the issue seems to be, like in the following scenario > > > > We imagine a list server for the domains fruiteaters and meateaters. > > We have two listadmins, anna (fruit) and carl (meat). They don't share anything. > > We have a user who subscribes to fruiteaters and meateaters using his address hunger(a)eatall.com > > > > He wants to show up in the fruiteaters list as fullname wormy wonder, but in the meateaters list as fritz the cat. > > While he can do so using two different email addresses, he cannot do so using > > > > wormy wonder <hunger(a)eatall.com> > > fritz the cat <hunger(a)eatall.com> > > > > as from: addresses because all requests will be matched to the one email address. > > > > Worse, if Carl would be able to change the name to from wormy wonder to fritz the cat, Anna would see that name change and like to change it back because the user she had known, user has been identified as wormy wonder. > > > > So, if these user properties are stored somewhere not related to the lists, we don't seem to have a chance of display name changes by list admins as long as the data model isn't changed. This doesn't seem to be easy. > > > > So, only some kind of super-Admin should currently be able to change these display names, and these changes would be visible for all lists, and one email address can only have one display name for all lists. > > > > Not optimal for some rare conditions - that's the way it seems to be??? > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

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

by Helio Loureiro

Hi Mark, Thanks for your response. I found what the issue was. I actually misspelled hyperkitty as hyPperkitty on the url. So the error on mailman-hyperkitty.cfg was: base_url: http://localhost:8000/hypperkitty/ I moved to: base_url: http://localhost:8000/hyperkitty/ and it was solved. Problem was the wrong link was getting a generic page from Django instead of error. And it was failing to do the parsing probably, which was taking wrongly as key mistake. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > 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 > > -- > 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 helio(a)loureiro.eng.br >

1 year, 5 months

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

by Mark Sapiro

On 4/25/24 14:01, Thomas Stein wrote: > Am 2024-04-25 22:03, schrieb Mark Sapiro: >> >> I don't know how things are arranged in the Debian/Ubuntu package, but >> you may have a settings.py which at the end does something like >> ``` >> try: >> from settings_local import * >> except ImportError: >> pass >> ``` >> If that is the case, adding the above snippet to the end of >> settings_local.py should work. > > Yes, that's the case. I added the snippet in question to > settings_local.py but this leads to another error: > > File "/usr/share/mailman3-web/settings.py", line 503, in <module> > from settings_local import * > File "/usr/share/mailman3-web/settings_local.py", line 194, in <module> > x = list(MIDDLEWARE) > ^^^^^^^^^^ > NameError: name 'MIDDLEWARE' is not defined > dpkg: error processing package mailman3-web (--configure): Yes. I understand. In your case, MIDDLEWARE is only defined in settings.py and not in settings_local.py. As I understand it originally you added ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to settings.py and you say it didn't help. I don't know why that wouldn't work as long as there is no setting for MIDDLEWARE in settings_local.py and you added that after the MIDDLEWARE setting in settings.py. When you say it didn't help, do you mean you still get the django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE message or something else? I note that the original post in this thread refers to /etc/mailman3/mailman-web.py which is presumably where the package ultimately puts the Django settings, and I don't know what `dpkg --configure` is doing. One thing you could try is in settings_local.py, put ``` from settings import MIDDLEWARE x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` to work around the NameError. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by Jason Glazer

Thanks for the suggestion on a shared IMAP mailbox. Jason On 7/11/2017 4:45 PM, tlhackque via Mailman-users wrote: > On 11-Jul-17 12:54, Jason Glazer wrote: >> I run several MailMan 2.1 mailing lists and some subscribers are >> frustrated by the way pipermail deals with JPEGs that are embedded in >> the messages and also with how attachments are handled. Does hyperkitty >> in Mailman 3.1 do better on these issues. >> >> Assuming this message gets archived, I am going to try embedding a >> small picture right here: >> >> Hopefully that shows up in the archive. I won't add an attachment >> because the list may not allow it but I'm curious how those are >> handled. >> >> Thanks >> >> Jason >> -- >> Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair >> Admin for onebuilding.org building performance mailing lists >> > I know that this particular list is setup to strip HTML and only > distribute text/plain. > > I haven't gotten to HyperKitty configuration yet (a lot of plumbing yet > to do for my environment), > but I too am interested in having HTML mail archived & viewable as an > HTML MUA would show it. > > I pretty much gave up on the 2.1 archiver for the HTML lists. Instead, > I subscribed a mailbox to the lists, > and served it to the community read-only with IMAP. Dovecot handles > private 'seen' flags for shared mailboxes, so this let people use their > favorite e-mail client to browse the archive. > > I'm hoping that I won't have to reconstruct this for my new > environment...but it's an option. > > > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Jason Glazer, P.E., BEMP, GARD Analytics, 90.1 ECB chair, 209 chair Admin for onebuilding.org building performance mailing lists

8 years, 2 months

[MM3-users] Re: Help on removing moderators

by Mark Sapiro

On 3/4/20 6:26 AM, sean_sullivan(a)rhoworld.com wrote: > > However, if I try and bring that in as a function that can be used with mailman withlist, I am consistently getting errors, and being that I am not very experienced in python, it has me scratching my head to say the least. > > from mailmanclient import Client You do not need to use mailmanclient with shell/withlist. mailmanclient is Python bindings for REST API functions. When you are under `mailman shell` (or `mailman withlist`, a synonym for `mailman shell`) you are working within mailman core and it's just extra baggage to use mailmanclient/REST. > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.testing.helpers import subscribe Here again, mailman.testing.helpers is to provide certain functions used in doctests. You don't need that with mailman shell. > addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] > > client = Client('http://localhost:8001/3.1', 'restadmin', 'restpass') > > def set_owners(mlist): > > for email_addr in addresses: > try: > member = subscribe(mlist, '', email=email_addr, role=MemberRole.owner ) See below. > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist): > my_list = client.get_list(mlist) > # print(my_list.fqdn_listname) > # for email_addr in addresses: > # my_list.remove_owner(email_addr) > > The errors I am getting are: > > ./bin/mailman withlist -r set_owners.remove -l it-test-b(a)lists.rhoworld.com > Traceback (most recent call last): > File "./bin/mailman", line 8, in <module> > sys.exit(main()) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 764, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 717, in main > rv = self.invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke > return super().invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 1137, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 956, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 555, in invoke > return callback(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func > return f(get_current_context(), *args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/commands/cli_withlist.py", line 293, in shell > r = call_name(dotted_name, m, *run_args) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/utilities/modules.py", line 70, in call_name > return named_callable(*args, **kws) > File "/opt/mailman3/bin/set_owners.py", line 24, in remove > my_list = client.get_list(mlist) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/client.py", line 347, in get_list > 'lists/{0}'.format(fqdn_listname)) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 404: 404 Not Found > > > So, I am wondering, is it possible to do something like this or am I completely misunderstanding the documentation, and why do I get a 404 here, when in the shell everything works as expected. I know I must be missing something, but cannot for the life of me figure out what that is. Any help would be greatly appreciated. Here's what you want with addresses as arguments so you can save this as set_owners.py and run things like. $ bin/mailman shell --run set_owners -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' and $ bin/mailman shell --run set_owners.remove -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' > from mailman.app.membership import add_member, delete_member > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.interfaces.subscriptions import RequestRecord > > def set_owners(mlist, *addresses): > for email_addr in addresses: > try: > record = RequestRecord(email_addr) > member = add_member(mlist, record, role=MemberRole.owner) > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist, *addresses): > for owner in mlist.owners.members: > if owner.address.email in addresses: > owner.unsubscribe() -- 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: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Hello, Andy Smith wrote: > On Sun, Jun 26, 2022 at 12:37:05PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > >> AFAICS, it is not documented since, at Postorius → Settings → Message >> Acceptance → Default action to take when a (non-)member posts to the >> list, I only read: “Discard: this simply discards the message, with >> no notice sent to the post's author”. So no mention that this would >> set it to (silently) discard all future mails from them. > > Well that is because that isn't what that part does. As it says, > that part is the "Default action to take when a member/non-member > posts to the list". So that's where you set what you want to happen > when ANY non-member posts. This is what will happen any time any > non-member posts. > By contrast, when you set an action on a particular held message, it > is asking you want you want to do with posts from THAT INDIVIDUAL > ADDRESS for the future. > So hopefully you can see that these things are different. One is a > whole-list property that applies to posts from classes of posters > (members, non-members). The other is per-poster property as a > reaction to as held message from them. OK, I see, thanks. >> 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. OK. Too bad this cannot be done from the list of messages on the .../held_messages page: it would be very helpful when you are overwhelmed by spams...

3 years, 2 months

[MM3-users] How to add new Domain?

by c.benner＠apd-it.eu

Hello, i'm really new to mailman3 and I've been using mm2.1 couple of years. It's really hardto understand documentation. But I'll do one in german language next time. I've got it installed ob Debian12 and it's working now. It takes a little more time to understand all settings and also the difference between postorius and django and what is when used for. But what I do not understand 'til now is how to add a new domain. My running config has one domain (e.g.) testdomain1.org and everything is working fine. The Domain has a virtualhost which listens on *:443 (with LE cert) Postfix works like a charm. The interface of the machine is bound to one IP Address public but for example here written as: 192.168.200.15 Id like to add a new Domain. My first step would be to add another IP Address to the interface: (e.g.) 192.168.200.16 Then I'll change the virtual host settings in apache conf from first domain which is actually listeing to *:443 to 192.168.200.15:443 And add a second site with 192.168.200.16:443 So the "physical" part is done Is that right 'til now? After that I'll go to the admin page xxxx/mailman3/admin which brings django admin page up. On that page I'll add "websites" and add testdomain2.net Last step is adding "mail domain" site: testdomain2.net mail domain: testdomain2.net After that I can add lists to that domain and mails to any list @testdomain2,net should be routed right? Maybe I'm to old (56yrs) but I've read a lot of documentation and everything was clear and understandable. It was never a question of linux or windows OS but on who'S writing the doc. I can't find any doc about the web part? What about Users having no acces to the shell but the Web-Frontend? Some pictures and a "How to" and "what if" would be great! But it's alos possible that I'm not finding it and it's somewhere out there. Thanks in advance.

7 months, 1 week

[MM3-users] Re: [Mailman-Developers] Countdown to the 3.1 release

by Barry Warsaw

On Jul 13, 2016, at 12:18 PM, Simon Hanna wrote: >I guess https://gitlab.com/mailman/mailman/issues/219 should be fixed in >the next release. If 3.1 find its way into repositories, we will get >lot's of issue reports for this I suppose. Thanks Simon. I've put this in the 3.1 milestone and will take a look. >Terri was working on this one, it's not critical but nice to have for >usability >https://gitlab.com/mailman/postorius/merge_requests/159 ack. >I have a mr pending for mailmanclient that should be included in the >next release >https://gitlab.com/mailman/mailmanclient/merge_requests/10 I've added a 3.1 milestone to mailmanclient and assigned this one to it. >Postorius has a number of merge requests open. I'm not sure which of >them should be merged before the next release Florian, do you have time in the next few weeks to do some Postorius triaging? >Does your template branch in core need any immediate modifications to >mailmanclient and/or postorius? It shouldn't, at least for API 3.0. All the new template APIs are exposed on v3.1 only, and when using the v3.0 API, they should map the old attribute names to the new mechanisms, so it should all be transparent. Modulo bugs of course. ;) I think it would be nice if mailmanclient and/or Postorius used the v3.1 API to get the full power of the templates branch, but it's probably not critical for the current release. Flo and I did talk about adding a cli that Postorius could call when installing it next to a v3.1 Core, e.g. to install some default templates for a cohabitating Postorius, but on further thought, it would be just as easy to write a bit of Python code to install those templates. Note though that someone would have to write the templates and ship them with Postorius, but they could be done using file: URLs into the Postorius install directory. That would be a fun project for someone to tackle, and I'd be happy to answer any questions that come up. Cheers, -Barry

9 years, 2 months

[MM3-users] Re: Confirm on mass subscription

by tlhackque

On 05-Jul-17 22:09, Mark Sapiro wrote: > On 7/5/17 1:48 PM, David Krantz wrote: > > >> Is there a way of requiring all mass subscribed users to confirm their >> email adress? I have an use case where we have a current mail list but >> when moving it to mailman I for different reasons would like to >> confirm all subscribers. Some very shallow testing suggests that if I >> just add them using mass subscribe, they will not have to confirm at >> all. >> >> I have yet to upgrade to 3.1 but I will do so in due time. > > In MM 2.1, you just send the users invitations rather than subscribing > them. In MM3/Postorius, this does not seem to be an option at present. > Actually, 2.1 lets you do it either way. The first radio button on Mass Subscriptions is: "Subscribe these users now or invite them? " MM 2.1 also allows control of whether the new subscribers and/or list owner are notified. And it allows custom text to be added to the invitation/notification (when one is sent). MM3 has none of these controls. Postorious issue #203 and mailman #362 refer to the MM 2.1 regressions. However, I read this somewhat differently: given a list with subscribers (however they were subscribed), it is sometimes useful to be able to ask the members to re-confirm their address/interest. For example, when there's a change of policy (terms of use), or when local opt-in regulations require that that opt-in be reconfirmed periodically. It's handled out-of-band now, but this would seem to be something that Mailman could manage - change users' state to "unconfirmed" and issue the re-invite/re-subscribe notice. But there are some details: re-confirmation probably doesn't want to require moderator re-approval (at least not always). How this interacts with "don't deliver mail from this list" needs definition (probably overrides), but some members (notably moderators/owners/robots) need to be exempt. And like 2.1, the user notification needs to be different to explain that it's a re-confirmation.

8 years, 2 months

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Dave Hall

On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/7/23 13:43, Odhiambo Washington wrote: > > On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < > > as2020+github(a)fam.tuwien.ac.at> wrote: > >> > >> I am running MM2 und 3 in parallel without problems, I do have a > >> special MTA setup though (Sendmail). Can't speak for Postfix etc.. > >> > > > > Your setup can handle list1(a)domain1.name via MM2 and MM3, > simultaneously, > > right? :-) > > It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` > simultaneously on the same server, but what is the MTA going to do with > incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to > both MM2 and MM3, but I don't see any practical use case for this. > > I run Exim4 on my servers so I can comment from this perspective. Exim had a concept of 'routers' which are stacked and processed in order of appearance. There is a router for MM2 and one for MM3 that pick off incoming mail based on whether the email address matches a list name. WIth this setup, you could have the same list name in both MM2 and MM3, but it would go to whichever router appears first and the second one would never see it. So I have the MM3 router first, and as I migrate my lists from MM3 the email for those lists no longer gets to MM2. > -- > 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 kdhall(a)binghamton.edu -- Dave Hall Binghamton University kdhall(a)binghamton.edu 607-760-2328 (Cell) 607-777-4641 (Office)

2 years, 5 months

[MM3-users] Change to content filtering collapse alternatives - was: Re: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 2/1/25 03:08, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > Not if we're collapsing alternatives. If we're collapsing a > > multipart/alternative part with text/plain and text/html > > alternatives to just the first alternative we don't keep the > > text/html part. > > I understand that's what we currently do. But I think that when the > MUA provides an empty plain text part and a non-null HTML part, that's > a mark of lazy MUA developers, not author intent. I think that it's > very likely that the author would prefer the reader get converted HTML > rather than a blank. I think this is a request to change the collapsing of alternatives to not collapse to the first alternative if it is empty and a subsequent alternative is not. I see your point in general if the poster composes an HTML message and the MUA makes a multipart/alternative message with an empty text/plain part, but are there actually MUAs that do that? All the ones I'm aware of either make an HTML only message or attempt to make a reasonable text/plain alternative. Even Yahoo mail which does a horrible job of making the text/plain part (i.e. links which are copy/pasted in the HTML are dropped from the plain text) does make one. That said, the effect on the OP's case, which may be more common, may be harmful depending on list and Mailman config. The original message from the OP (edited) is ``` Content-Type: multipart/related; boundary="000000000000da2dcc062cb38aa1" --000000000000da2dcc062cb38aa1 Content-Type: multipart/alternative; boundary="000000000000da2dcb062cb38aa0" --000000000000da2dcb062cb38aa0 Content-Type: text/plain; charset="UTF-8" --000000000000da2dcb062cb38aa0 Content-Type: text/html; charset="UTF-8" <div dir="auto"><img src="cid:ii_194a8d787554eb091f02" style="max-width: 100%; height: auto;"><br><br></div> --000000000000da2dcb062cb38aa0-- --000000000000da2dcc062cb38aa1 Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 Content-ID: <ii_194a8d787554eb091f02> X-Attachment-Id: ii_194a8d787554eb091f02 <base64 content> --000000000000da2dcc062cb38aa1-- ``` The HTML alternative only renders the jpg as an inline image. After current collapse alternatives this becomes ``` Content-Type: multipart/related; boundary="000000000000da2dcc062cb38aa1" --000000000000da2dcc062cb38aa1 Content-Type: text/plain; charset="UTF-8" --000000000000da2dcc062cb38aa1 Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 Content-ID: <ii_194a8d787554eb091f02> X-Attachment-Id: ii_194a8d787554eb091f02 <base64 content> --000000000000da2dcc062cb38aa1-- ``` which is an empty first part followed by the jpg part which is then further collapsed to just the jpg part ``` Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 <base64 content> ``` I.e. a single part message with content type image/jpeg. If instead we collapsed the alternatives to the HTML part the message becomes ``` Content-Type: multipart/related; boundary="000000000000da2dcc062cb38aa1" --000000000000da2dcc062cb38aa1 Content-Type: text/html; charset="UTF-8" <div dir="auto"><img src="cid:ii_194a8d787554eb091f02" style="max-width: 100%; height: auto;"><br><br></div> --000000000000da2dcc062cb38aa1 Content-Type: image/jpeg; name="1000013462.jpg" Content-Disposition: inline; filename="1000013462.jpg" Content-Transfer-Encoding: base64 Content-ID: <ii_194a8d787554eb091f02> X-Attachment-Id: ii_194a8d787554eb091f02 <base64 content> --000000000000da2dcc062cb38aa1-- ``` and what that html part looks like after conversion to plain text depends on the configured command. With the default lynx the content is unchanged, put the type is text/plain which will render as the text with the image attached. With links the plain text content is empty which results again in a message with empty first part and image/jpeg second part. In short, for this message at least, I see no real advantage to dropping the empty text/plain alternative vs. dropping the text/html alternative. Possibly there is a difference if we don't convert HTML to plain text in that some MUAs might render the jpeg inline as opposed to an attachment, but if we do convert with lynx the recipient sees a message with a body which is HTML tags rendered as text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 2 weeks

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

by Abhilash Raj

On Fri, Jul 30, 2021, at 11:01 AM, Mark Sapiro wrote: > 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. Container images don't support mailman-web command yet, it has to be ported to use the mailman-web command. You can run commands with `docker exec -it mailman-web ./manage.py <command>`. For creating the superuser, you can run[1] [1]: https://asynchronous.in/docker-mailman/web.html#running Although, if you have set the MAILMAN_ADMIN_EMAIL, that command should have already run in the setup process. You want to figure out the email sending process. Although, you can create a second admin and set the password for it and login using that using the command mentioned at [1]. > > > > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. You can run docker exec -it mailman-web ./manage.py sendtestemail youremailid@domain > > 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 > _______________________________________________ > 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: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/7/22 16:11, Philippe B wrote: > I think that your last sentence helped us figure out what's going on. > > When Mailman generates a moderation message "To: LIST-owner" it actually delivers it to the address(es) of the LIST's moderator(s), which makes sense. No, it delivers the message to the union of the sets of owner addresses and moderator addresses. > In all the cases where we've seen that behavior, it turns out that the list involved didn't have any moderator, and we have site_owner set to "mailman"... You don't need to have moderators. The owners get the message too. > However, the lists had an owner, and we're not seeing those moderation messages being sent to their owner (instead). Is that something that needs to be configured explicitly somewhere? The only things that might affect this are if Settings -> Automatic Responses -> Autorespond to list owner is Respond and discard message or if the owners delivery_status is other than DeliveryStatus.enabled. Note that finding an owner's delivery status is tricky. The owner can find it in Postorius by going to https://www.example.com/mailman3/accounts/subscriptions/ and clicking on the entry for the list with role owner. This delivery status is not the same as the delivery status for the same address with a member role if there is one. For an admin you could do ``` $ bin/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 >>> owner = m.owners.get_member('user(a)example.com') >>> owner.delivery_status <DeliveryStatus.enabled: 1> If you needed to set it here, you could do >>> owner.preferences.delivery_status = DeliveryStatus.enabled >>> 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, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Dear Kyle, after installing and doing mailman info I got this: (env) [mailman@localhost ~]$ mailman info Traceback (most recent call last): File "/var/lib/mailman/env/bin/mailman", line 11, in <module> load_entry_point('mailman==3.1.0', 'console_scripts', 'mailman')() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/mailman.py", line 97, in main initialize(config_path) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/core/initialize.py", line 184, in initialize initialize_1(config_path) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/core/initialize.py", line 119, in initialize_1 mailman.config.config.load(config_path) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/config.py", line 107, in load self.push(filename, user_config.read()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/config.py", line 113, in push self._post_process() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/config.py", line 125, in _post_process self.ensure_directories_exist() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/config.py", line 227, in ensure_directories_exist with Lock(lock_file): File "/var/lib/mailman/env/lib/python3.6/site-packages/flufl/lock/_lockfile.py", line 322, in __enter__ self.lock() File "/var/lib/mailman/env/lib/python3.6/site-packages/flufl/lock/_lockfile.py", line 189, in lock self._write() File "/var/lib/mailman/env/lib/python3.6/site-packages/flufl/lock/_lockfile.py", line 405, in _write with open(self._claimfile, 'w') as fp: PermissionError: [Errno 13] Permission denied: '/var/lock/mailman/mailman-cfg.lck|localhost.localdomain|7460|2370281649234082704' What do you suggest? El jue., 13 jul. 2017 a las 16:15, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > I included the corrected command in my previous message. > > For clarity, it is: > > # useradd -r -m -d /var/lib/mailman mailman > > -Kyle > > On Thu, Jul 13, 2017 at 4:56 PM Rafael Mora <rafael.mora.guti(a)gmail.com> > wrote: > >> What would be the correct command??? >> >> Thank you >> >> El jue., 13 jul. 2017 a las 15:55, Kyle Richardson (< >> kylerichardson2(a)gmail.com>) escribió: >> >>> Sorry, you're correct. I mistyped the useradd command. >>> >>> # useradd -r -m -d /var/lib/mailman mailman >>> >>> -Kyle >>> >> -- >> >> Atentamente / Best Regards >> >> Ing. Rafael Mora >> > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 2 months

[MM3-users] Re: help with startup scripts

by Piet Barber

On Thu, Aug 14, 2025 at 3:03 AM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Piet Barber via Mailman-users writes: > > > However, when I follow the systemctl startup scripts as per the > > instructions at the URL above, it get stuck in the startup > > ... forever > > What makes you think it's stuck? Have you actually tried to use it? > If not, it's probably just that systemd messages were not written to > be understood by ordinary mortals. > root@arcus:/etc/systemd/system# systemctl start mailman3 (extreeeeemelllyyy loooooong wait of nothing ensues) Eventually I get: root@arcus:/etc/systemd/system# time systemctl start mailman3 *Job for mailman3.service failed because a timeout was exceeded.**See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details.* real 0m19.442s user 0m0.002s sys 0m0.012s root@arcus:/etc/systemd/system# the journalctl output is as follows: Aug 14 23:48:24 arcus mailman[5624]: Starting Mailman's master runner Aug 14 23:48:24 arcus mailman[5624]: Generating MTA alias maps Aug 14 23:48:24 arcus systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: No such file or direct> Aug 14 23:48:29 arcus mailman[5645]: /opt/mailman/venv/lib/python3.12/site-packages/mailman/rest/wsgiapp.py:185: DeprecatedWarning: The RequestOp> Aug 14 23:48:29 arcus mailman[5645]: self.req_options.auto_parse_form_urlencoded = True Aug 14 23:49:53 arcus systemd[1]: *mailman3.service: start operation timed out. Terminating.* Aug 14 23:49:55 arcus systemd[1]: *mailman3.service: Failed with result 'timeout'.*░░ Subject: Unit failed░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ The unit mailman3.service has entered the 'failed' state with result 'timeout'. Aug 14 23:49:55 arcus systemd[1]: *Failed to start mailman3.service - GNU Mailing List Manager.*░░ Subject: A start job for unit mailman3.service has failed░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ A start job for unit mailman3.service has finished with a failure.░░ ░░ The job identifier is 1153 and the job result is failed. Aug 14 23:49:55 arcus systemd[1]: mailman3.service: Consumed 13.298s CPU time.░░ Subject: Resources consumed by unit runtime░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ The unit mailman3.service completed and consumed the indicated resources. Aug 14 23:50:10 arcus systemd[1]: mailman3.service: Scheduled restart job, restart counter is at 3.░░ Subject: Automatic restarting of a unit has been scheduled░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ Automatic restarting of the unit mailman3.service has been scheduled, as the result for░░ the configured Restart= setting for the unit. Aug 14 23:50:10 arcus systemd[1]: Starting mailman3.service - GNU Mailing List Manager...░░ Subject: A start job for unit mailman3.service has begun execution░░ Defined-By: systemd░░ Support: http://www.ubuntu.com/support░░ ░░ A start job for unit mailman3.service has begun execution.░░ ░░ The job identifier is 1525. The system works fine when i su to mailman and run the startup script in /opt. The system doesn't work when I use the systemctl command. Apparently it's waiting for something to happen before the system creates a pidfile in /opt/mailman/m/var/master.pid Do you have mailman3 starting from a startup script? What does your /etc/systemd/system/mailman3.service file look like? Mine looks just like the one on the mailman configuration site. I have to be doing something stupid for it not to work. I just can't figure out what stupid thing I'm doing wrong. Also, removing the word "Forking" from the systemctl configuration file has no effect, except that it takes longer for the mailman3 startup script to fail. root@arcus:/etc/systemd/system# time systemctl start mailman3 *Job for mailman3.service failed because a timeout was exceeded.**See "systemctl status mailman3.service" and "journalctl -xeu mailman3.service" for details.* real 1m23.491s user 0m0.006s sys 0m0.004s root@arcus:/etc/systemd/system# I'm about to jump out the window on this one. I've been stuck on this for four weeks. Here's my mailman3.service file: [Unit]Description=GNU Mailing List ManagerAfter=syslog.target network.target postgresql.service [Service]#Type=forking#PIDFile=/opt/mailman/mm/var/master.pidUser=mailmanGroup=mailmanEnvironment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg"ExecStart=/opt/mailman/venv/bin/mailman startExecReload=/opt/mailman/venv/bin/mailman restartExecStop=/opt/mailman/venv/bin/mailman stopRestart=on-failureRestartSec=15 [Install]WantedBy=multi-user.target -- Piet Barber http://www.pietbarber.com/ http://blog.pietbarber.com/

1 month

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

by Abhilash Raj

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> 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 > >> To unsubscribe send an email to mailman-users-leave(a)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 > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > > -- thanks, Abhilash Raj (maxking)

5 years, 11 months

[MM3-users] Re: Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by Mark Sapiro

On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > I have read documentation, but still have stupid questions, could You please help, because I can't make it working. I do not understand something important. I have no experience with python at all. I have mailman 3, python 3.5 in my debian OS system, and additional packages like uwsgi and ect. using https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… about till chapter 6. I understand mailman suite has hyperkitty already. But I am not sure about: > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python manage.py runserver - it runs. In installed it under dedicated OS user home and fonfigured to run. > I can create lists, event add lists to hyperkitty page using: $django-admin runjob new_lists_from_mailman list server sends messages to list members as well. But nothing happens more. No emails come to hyperkitty, arciver log 0 size. > $ python manage.py runjobs -l shows the lists of the jobs, so seems nothing to add. How exactly did you install Mailman? The document you reference gives alternatives. You don't say exactly what you did. > 2. If I (using Postorius web interface) add footer template to my list under regular message, something strange happens. Mailman stops to send messages for list members. No any entries in the logs. Just Mailman log writes: "unable to connect localhost port 25" and no more explanation. If I delete list's footer template (web interface), mailman starts working again. What is bad here? How to add custom footer? In mailman 2 if was working so good and was easy to setup. It appears that no MTA is listening on localhost port 25. Is your MTA even running? It is extremely unlikely that this has anything to do with adding a termplate in Postorius. You might be better off installing Debian's 'mailman3-full' package <https://packages.debian.org/search?keywords=mailman3-full&searchon=names&su…>. -- 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] Re: Member Issue Discovered

by Alex Schuilenburg

On 22/10/2020 05:59, Abhilash Raj wrote: > Like Mark brought up, there is definitely a big missing feature of User management in Postorius. This future management page would be for Site Admins (Superusers) to manage Users and have the ability to change pretty much everything about users including their addresses, memberships and preferences and also be able to wipe off the users from all the databases if they want to. If there are more features than that which folks think should be a part of this, please feel free to add to it. As it is hopefully implied from the description, it is a big task and needs substantial chunk of time, part of which this hasn't been picked up yet. On this score, from my experience (I manage 3 sites and several hundred lists): * you also need to disable a particular user's ability to change their name and ban them completely from the site (all lists). /You always get some idiot who uses a foul, abusive or inappropriate name/ * you need the ability to delete a thread or user's postings. /On one occasion I had a formal request from a company's lawyers for one user's email to be deleted or content redacted where quoted (information bound by NDA). That was relatively easy to do in mm2 with shell access and I guess I could even use the same method for mm3 if ever asked to do so again (export mbox, delete archives, delete/redact from mbox and import)/ Yes, this is social media territory, but with the EU/UK DPA (data protection act) and record fines being issued, site admins cannot ignore these - even private/subscriber lists are targets (don't get me started...). I like mm3's ability to have several addresses associated with one account, but it needs the same functionality as mm2's find_member, remove_member etc so you don't have to undergo a crash course in python and mm3's shell just to find and remove a particular member from mailing lists etc. Yes, it would be nice to re-use some of those old mm2 scripts built up over the years on mm3. -- Alex

4 years, 10 months

[MM3-users] Re: Sender: header

by Mark Sapiro

On 11/30/21 7:51 PM, Philippe B wrote: > MM2 adds the header "Sender: LISTNAME-bounces@DOMAIN" to messages sent to list members. > > That causes Outlook (among others?) to display the "originator" of a message from a REAL POSTER as: > > LISTNAME-bounces@DOMAIN on behalf of REAL POSTER <REAL.POSTER@DOMAIN> > > That phrasing helps identify instantly what list a message is coming from, when that list doesn't use a Subject prefix and when its address isn't in the To: or Cc: headers. (And it turned out that some of our list members were even relying on it to trigger security alerts!) Mailman 2's adding of a Sender: header is an artifact from a time when some MTAs would return bounces to the Sender:. I think yours is the first comment I've seen that actually likes the way Outlook renders it. Most want to know how to prevent that which is why MM 2 has an option to not add it. As far as triggering alerts or filtering is concerned, there are other headers in list mail that can be used for that purpose. > It doesn't look like there's any current MM3 setting that would accomplish the same result, so the question is: How difficult would it be to revive the Sender: header? By revive, do you mean add a feature in MM 3 to add a Sender: header. If so, you could submit a request at `https://gitlab.com/mailman/mailman/-/issues`. If you mean how difficult would it be for you to do it. here's a one line patch that will unconditionally remove any pre-existing Sender: header and add one with the list posting address. ``` --- a/src/mailman/handlers/rfc_2369.py +++ b/src/mailman/handlers/rfc_2369.py @@ -67,6 +67,7 @@ def process(mlist, msg, msgdata): ('List-Owner', '<mailto:{}>'.format(mlist.owner_address)), ('List-Unsubscribe', '<mailto:{}>'.format(mlist.leave_address)), ('List-Subscribe', '<mailto:{}>'.format(mlist.join_address)), + ('Sender', mlist.posting_address), )) if not msgdata.get('reduced_list_headers'): # List-Post: is controlled by a separate attribute, which is somewhat ``` -- 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: HyperKitty/Mailman3 issues

by Florian Schulze

On 22 Nov 2018, at 19:53, Mark Sapiro wrote: > On 11/22/18 2:58 AM, Florian Schulze wrote: >> Hi! >> >> I tried setting up Scheduled Tasks as described in >> <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> >> >> but the "runjobs" command can't be found. I see the hyperkitty and >> mailman commands when using "help". > > > Does "help" show a list under [django_extensions] including runjob and > runjobs? > > Is 'django-extensions' in the list of INSTALLED_APPS in your Django > settings? That was the issue. Thanks! >> The "qcluster" service is working. >> >> Using Django 2.1.1 and HyperKitty 1.2.1. >> >> Maybe related to that, I have two issues with archives. >> >> 1. Changing the archiving setting in the Web-UI to something else >> than >> public seems to have no effect. The already archived messages are >> still >> accessible in public. > > > This is related. It is one of the "daily" jobs that updates this. Note > that changing to "private" will require login after the "daily" jobs > run, but changing to "do not archive" will leave the existing archive > accessible. After manually running the daily job, the archive is now private. >> 2. Related to 1., how can I remove a list archive without affecting >> other lists? > > > There's no easy way. For the "prototype" archiver, the archives for a > list are in var/archives/prototype/listname(a)example.com/ and that > directory can be removed, but that doesn't affect HyperKitty. > HyperKitty's archives are in the Mailman database and multiple tables > are involved. > > One could try just removing the row for the list from the > hyperkitty_mailinglist table. That may render the list's archive > inaccessible via the web UI, but I have no idea what would be broken > by > doing this. I hope this will be added at some point. For now I have the archive set to private. Thanks again for the pointers! Regards, Florian Schulze

6 years, 9 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 6/6/23 07:58, Nelson Strother wrote: > > No errors are being recorded in the mailman log files. This is GNU > Mailman 3.3.8 via `pip install mailman` on Debian 5.10.179-1 > (2023-05-12) running on a shared system where VMware gives this server > enough cycles that `mailman start` and `mailman stop` each consume from > 20 minutes to an hour of wall clock time, so I do not issue those > commands recreationally, attempting to keep the system available for > users. What should I do to help understand the cause for these failures? If a runner has died, its death and a reason should be logged in Mailman's var/logs/mailman.log with a message similar to Master detected subprocess exit (pid: 8617, why: SIGNAL 15, class: in, slice: 1/1) This may not be the case if the runner is killed by the OS for an out of memory or similar reason. For this, look in syslog. `mailman stop` can take a long time because it is waiting for a runner to stop. See https://gitlab.com/mailman/mailman/-/issues/255 but that issue was fixed long ago. I don't understand why `mailman start` would take more time than `mailman restart`. In fact, `mailman restart` effectively does `stop` and `start`, but only for those runners which are running. Since you seem to frequently have missing runners, I suspect something like an OOM condition is causing the OS to kill them. Although, I wonder if you are correctly interpreting the logs. While the absence of the `retry`, `task`, `nntp` and `archive` runners might not be noticed except for messages not being archived, if either the `in` or `pipeline` runner is not running, no list posts will be processed. > Would not it be helpful for this limitation of restart to be included in: > mailman restart --help > with a suggestion to use `mailman stop` and `mailman start` instead? I have just filed https://gitlab.com/mailman/mailman/-/issues/1082 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Problems configuring hyperkitty

by Mark Sapiro

On 11/18/24 09:29, Alain D D Williams wrote: > > I am running Debian 12 - Bookworm and have installed the Debian packages. The > database is Mysql. This is not a virtualenv setup. There is no documentation in > the hyperkitty package so I am following: > > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html The primary support resource for Debian packages is Debian. See https://wiki.list.org/x/12812344 > I read the following: > > "The database can be created with the following command: > > django-admin migrate --pythonpath example_project --settings settings > " > > I assume that that will create some database tables. Hopefully this will have > been done by installing package python3-mailman-hyperkitty. > > • What database & tables will that be ? It would be really useful to be told so > that I can check. The database is configured in the DATABASES setting in your Django settings. The HyperKitty tables all have names beginning with `hyperkitty_`. > • The config file is: /etc/mailman3/mailman-hyperkitty.cfg > This does not contain any comment about databases. Where does hyperkitty get > its database parameters from ? Django, see above. > • I have several different maildomains each with several lists. Some lists in > different domains have the same name. Do I need a different > example_project/settings.py for each domain, if so what changes ? I can't really speak to Debian, but you should be using the Django settings provided as part of Django's mailman-web package, not the ones in hyperkitty/example_project/settings.py as those don't include settings necessary for Postorius. > One of the next things that I will need to do is to import archives from > mailman2. How does the command below change for the different domains ? > > django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] In the `-l ADDRESS` argument the ADDRESS is the fully qualified list address and includes the domain. > > Is there some better documentation that I have failed to find ? Ask Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 4 weeks

[MM3-users] Re: How to turn off Emergency Moderation for imported MM2 lists?

by Abhilash Raj

On Thu, Aug 6, 2020, at 6:12 PM, Mark Sapiro wrote: > Mark Sapiro wrote: > > On 7/28/20 5:40 AM, Brian Carpenter wrote: > > > > > > This is the client that I asking about in my post. > > > She said what I > > > did, did not work. This is what I did: > > > > > > Get into a venv as user mailman > > > > > > #mailman shell > > > from mailman.model.mailinglist import MailingList > > > mlist = MailingList('listname(a)listdomain.org') > > > mlist.emergency = False > > > commit() > > > ctrl-d (just to be on the safe side) > > I half understand why this didn't work. Instantiating the list via > ``` > from mailman.model.mailinglist import MailingList > mlist = MailingList('listname(a)listdomain.org') > ``` > for some reason (that's the half I don't understand) does not get the > actual list object so changes you make to it don't affect the actual > list. It is because when you simply instantiate that class, it will create a new model instance, that you would need to persist by adding to database using `store.add(mlist)`. If you instead want to read that instance from database, you have to do `store.query()`, which is what the `.get()` method of IListManager does. > In `mailman shell` you need to do > ``` > mlist = getUtility(IListManager).get('listname(a)listdomain.org') > ``` > `getUtility` and `IListManager` are in the namespace in `mailman > shell`, but outside of that, e.g. just in `python` in your virtualenv, > you also need > ``` > from mailman.interfaces.listmanager import IListManager > from zope.component import getUtility > ``` > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Sat, 2021-02-13 at 17:04 +0900, Stephen J. Turnbull wrote: > > Your English is fine, it was just my lack of imagination: on February > 12, I couldn't conceive of February 3 being even a little "old"! I was not your imagination, it was confussion inserted in the line between brain and fingers and I meant .po and wrote .mo > More important, as long as the .mo file is more recent than the .po > file, that's the best the release manager can do. I haven't been > involved in the release process, so I can't swear to it personally, > but if Mark says that new translations generate a merge request > automatically, and we make sure that the translations are merged > before release, I believe him. That's optimal as far I am concerned. But, it seems something did not go well :-( > Perhaps some enterprising soul would be willing to automate > production of pip'able packages containing only new translations, but > without that, I don't see how to beat our current procedures. (I > wouldn't want to use such a thing, though, I'd be too afraid that one > day all the translations would be replaced with Dril tweets!) Fully agreed. I first thought of "language chanpions" that could take care of syncing the .po files from Weblate to the replease repository. But then, that involves human availability, which is not an abundant asset in open source projects. Then, my brains went into "crazy mode", why do notuse the power of Python and the net. Maybe we can get someone (GSoC student) to write code that, given a .po file uses Google translation to check that the resulting string in the target language means more or less the same as the original English string on the .po file? Crazy-tinking-ly, Victoriano. -- 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, 7 months

[MM3-users] Re: Held messages not delivered after approval

by Odhiambo Washington

On Wed, Jul 30, 2025 at 5:28 PM Stephan Krinetzki < krinetzki(a)itc.rwth-aachen.de> wrote: > Hi all, > > I'm running into an issue with Mailman 3. Mails sent to a list are being > held due to moderation settings — which is expected — but after approving > them, they are not delivered to list members. > > The message does not end up in the shunt queue, and nothing is delivered. > > Here's what I see in the Mailman log: > > Jul 30 16:12:23 2025 (213300) HOLD: mm(a)lists.example.com post from > sender(a)sub.example.com held, message-id=< > 20250730141221.5VVrn%sender(a)sub.example.com>: The message is not from a > list member > Jul 30 16:12:39 2025 (213338) held message approved, message-id: < > 20250730141221.5VVrn%sender(a)sub.example.com> > > In the mail log, I only see the message arriving — there's no sign of it > being sent out. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This here does not make sense. 1. You approve/UNHOLD the message - what then do you see in /opt/mailman/mm/var/logs/smtp.log? 2. The mail is handed over to your MTA, and you see evidence of that in mail.log, but it is not sent out. Doesn't that mean you have the mails in the queue? > Any ideas on what could be going wrong or where else I should look? > What is the output from running the `mailq` command? If the post has not reached the subscribers, then I suppose the emails are stuck in the Postfix queue for some reason. > Mailman Core-Version GNU Mailman 3.3.10 (Tom Sawyer) > Mailman Core API-Version 3.1 > Mailman Core Python-Version 3.11.11 (main, Jun 20 2025, 00:00:00) [GCC > 11.5.0 20240719 (Red Hat 11.5.0-5)] > > OS: Rocky 9 with Postfix MTA, installed as venv > Do you know if the list has been working, or is this a new install? -- 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 month, 2 weeks

[MM3-users] Re: ARC issues

by David Krantz

On Mon, Mar 2, 2020 at 4:45 PM Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Doesn't Postfix do ARC yet? :-( rspamd seems to be recommended by a > couple of Linux distros, supports the milter interface that Postfix > uses to call out to 3rd party processes, and the website looks good. > See rspamd.com. That said, if you want to use Mailman's support... To me, it seems easier to use Mailman's implementation if it is possible. Rspamd seems very nice as an alternative if I find time to substitute my spamassassin, greylister and, I guess, opendkim setup. As the feature of rspamd set is large with a web UI it probably is as time consuming to set up as mailman, so I'd rather not if I can avoid it. When I migrate to another server in due time it seems interesting. > Our support doesn't have issues that I know of. You can check the > issue tracker: https://gitlab.com/mailman/mailman/issues. On second > thought, don't bother. I did and "ARC" picks up scads of irrelevant > junk, "authenticated received chain" nothing, and a couple of other > tries don't pick up anything useful either. > > > I run the latest release of mailman (3.3.0 of core) on Python 3.7.6 > > and I use postfix as MTA. > > I haven't looked at ARC in some months, so it's possible that our > current implementation is out of date with best current practice. > However, in a quick scan I see no difference in RFC 8617 > vs. ID-ARC-23, so I don't know what might have changed there. > > Are the messages being refused by those sites because of the ARC > errors, or are they being delivered anyway? We probably need to see > the message as received by Mailman, the message as emitted by Mailman, > and the message as received at the validating site to have a hope of > diagnosing this. So far, they are delivered. Probably for the same reason that my messages are accepted without ARC. IPs with good reputation and a generally well-behaved setup. > The things that I can see from the data you've provided that might be > related are > > 1. If it's just the body hash that's a problem, there may be one or > more MXes that convert Content-Transfer-Encoding between your > Mailman and the receiving sites. That would be easy to check if > you have the messages as sent and as received. I do not think they do, but I'll examine that. My DKIM signing works just fine but postfix might have changed something before opendkim get the message. I'll have to find a way to capture the sent message leaving mailman before it enters postfix. > 2. You have an awfully aggressive list of signed header fields. In > particular, the Resent-* fields are treated as trace fields: there > may be multiple instances of each. I don't understand the > semantics of DKIM/ARC signing for those headers very well, but > it's something that I would think easy to mess up. You might try > deleting those. > > You are supposed to sign any existing DKIM-Signature fields, but > that's not in the list. I just used the default list of fields from the Mailman documentation. Now I did try a shorter list of fields but that did not help. > 3. The ARC RFC 8617 says that an ARC Sealer must add any > DKIM-Signature *before* ARC sealing. I suppose this could be a > problem, since our ARC implementation doesn't DKIM sign. (On the > other hand, I don't see how it would be a problem, since any MX > along the way might add a DKIM signature, and you're not signing > DKIM-Signature according to your list of signed fields.) It would be a problem if I'd add the DKIM fields to the field list of course. I see another potential problem with that list in that it includes fields that are not present, I had understood it as that would fail if a field is missing. > It would be helpful if instead of quoting small parts of error > messages, you gave us the entire body of a delivery status > notification message or the entire MTA log. If there's stuff > (domains, mailboxes, IP addresses) you want to redact, feel free, just > make sure that it's obvious what was redacted. I can do that. For that I will have to re-run my test which I do not have time for today, alas. It is easier to me to send an entire delivered message (with some domains and IPs redacted). I'll add such an example at the bottom of this mail as it gets a bit unwieldy. > I will check our implementation, principally to make sure that the > authentication results used are computed on the raw incoming message > and the ARC sealing is done on the raw outgoing message after all > other message modifications are done. I will also see if I can > conjure up tests that test the site's MTA(s) as well as just our > implementation, as we currently test our implementation using static > data from the ARC implementation we use (ie, we ARC-process a given > message and then do a byte-by-byte comparison on an allegedly correct > ARC-Sealed version of the same). Is there any good tool to verify an ARC signature? I could of course set another list as a subscriber to feed the result back to OpenDKIM and Mailman-ARC to see what happens but that is a bit convoluted. > Sorry I can't give more precise help. Maybe something here will be of > use. Of much use as it got me thinking, if nothing else. // David Delivered-To: gazorg(a)gmail.com Received: by 2002:ab3:6e8a:0:0:0:0:0 with SMTP id d10csp504094ltp; Sat, 29 Feb 2020 08:27:23 -0800 (PST) X-Google-Smtp-Source: APXvYqy2N4DctBE7sJ5iPliD4tFTap/Ag38FlQknzbgepRIeBhGi4BkvVeX+otJg+Q8EqS3L12L0 X-Received: by 2002:a05:6402:36d:: with SMTP id s13mr8975006edw.304.1582993643529; Sat, 29 Feb 2020 08:27:23 -0800 (PST) Return-Path: <test-bounces(a)example2.com> Received: from lists.example1.com (lists.example1.com. [192.168.0.1redactedIP]) by mx.google.com with ESMTPS id q7si4234768edn.147.2020.02.29.08.27.23 for <gazorg(a)gmail.com> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Feb 2020 08:27:23 -0800 (PST) Received-SPF: pass (google.com: domain of test-bounces(a)example2.com designates 192.168.0.1redactedIP as permitted sender) client-ip=192.168.0.1redactedIP; Authentication-Results: mx.google.com; dkim=pass header.i=(a)example2.com header.s=dkim header.b=aUkUFDX3; arc=fail (body hash mismatch); spf=pass (google.com: domain of test-bounces(a)example2.com designates 192.168.0.1redactedIP as permitted sender) smtp.mailfrom=test-bounces(a)example2.com Received: from lists.example1.com (localhost [127.0.0.1]) by lists.example1.com (Postfix) with ESMTP id 37B37405C6; Sat, 29 Feb 2020 16:27:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=example2.com; s=dkim; t=1582993643; bh=QtvH55+E9IsKYbQtbq3Ctq/SJNg1OC15t8DzRRa/xtM=; h=Date:To:Subject:List-Id:List-Help:List-Post:List-Subscribe: List-Unsubscribe:From:Reply-To:From; b=aUkUFDX3gmRAu4yffKt1a93D0zQ5SHOVM9IBgn9Eds02d99fTpDPGPrLURXm5nMsm 5Czjhyv12hwt/sDcqjkgot7XNZgpYu+ygeNhfFr/fNDR3I+/OJhQJFl7pGFH6/LkpI eZqCZuGFTTZjLU5/kPZ3Bxul9NsWUpFoxkoDj8bumbVnkAqBpFNqKF7vojUs/0A8lU MNZRRpvFzdpJPrMOWq2ZW/SfLZJaXJEKQPBX+cxtLTadwRooG4tJ58hGbjuk5qIlHH 0rohDoyI6zFO1IZLUub+LltmX8Z9CjGyfOp7FJeXs4i/F2Y0NtZfdATjGr9ODWYsxl Do7WWaCt/IagQ== ARC-Seal: i=1; cv=none; a=rsa-sha256; d=example1.com; s=dkim; t=1582993642; b=gcSal3MqawEf89KBCDi3s7mNkPZfJhN7XJ0SRlaB6fTT1LSVbEDb6JXa0cM4owpyvPPWU VG6/bOqHJeuACWqGQ6/wnXJCuRCJJkKzv0FVJCg61xfXcSUtKKCeLFarZtx59WUGxkkmCqI oDJufbsX56AYM0awVkHn9xu+eezG87Q= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=example1.com; s=dkim; t=1582993642; h=from : sender : reply-to : subject : date : message-id : to : cc : mime-version : content-type : content-transfer-encoding : content-id : content-description : resent-date : resent-from : resent-sender : resent-to : resent-cc : resent-message-id : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive; bh=Dphqgp/+wTnNNbrrDg3NfnpjXIJyK09lbeEWp6UaizQ=; b=W3oTWN8gDlllat7/QAXOe0lQk6IHDhIhwgu4KOjkFN8nOdRQUbnv0dt9LoZt2NrjY20wj g1IKXDuyfHitDwSqloxrYl8woZji+qy2fYyws4ATmzHckqBgfGQbDSxu3Lu3iaGf8cjEy11 Mj+rUGOg0sWoXXNCqjvMGMU3SWhQBRs= ARC-Authentication-Results: i=1; example1.com; dkim=pass header.d=example3.com header.i=(a)example3.com header.b="RgU2p/NV"; dkim-atps=neutral; arc=none; dmarc=none Authentication-Results: example1.com; dkim=pass header.d=example3.com header.i=(a)example3.com header.b="RgU2p/NV"; dkim-atps=neutral; arc=none; dmarc=none Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.example1.com (Postfix) with ESMTPS id 720B9405C5 for <test(a)example2.com>; Sat, 29 Feb 2020 16:27:20 +0000 (UTC) Received: by mail-lj1-f180.google.com with SMTP id q23so6847929ljm.4 for <test(a)example2.com>; Sat, 29 Feb 2020 08:27:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=Dphqgp/+wTnNNbrrDg3NfnpjXIJyK09lbeEWp6UaizQ=; b=VK+DeP8PfxjHWKPnE/VeVQCBOfi7xubKqXJ+qIokd8osR8zolWOQoljLgKgjmllrYi ZjRTWt4/f9imHKTtu1V+8YVdQ/yfAQ1LR9aYxTnBS0Baz9BV22ghXOuTAgm77uPOPZnQ BWRG6W01Fwb5VjlGMSQrn/+nQa5m+gBjKnF4F34HqtM3c0Igx9459lL++O3CC0M4vjnb sg0JVmQbbWu1anXQRnx2Ghy8/tkcKuJVDE9BhTXmMQCjJSzwRvLp7jHTlNk1tXW11TQ5 ZBnzgg+oN5GcgudjSMnBhstsCUqvEQttV5FOj1gNBV+EOw0B+b+A4iLGyUn/c+bbrVwi HXjg== X-Gm-Message-State: ANhLgQ0MEeEPN51okIGKQNjjbGpV/RHmPT8h47RTCG9U5MwsQWT9UZHg XzxoNg3sC2PYicdeBLor1wLThcLqWerLvsxOW5jMIm6SrSU= X-Received: by 2002:a2e:7d07:: with SMTP id y7mr5916044ljc.7.1582993639657; Sat, 29 Feb 2020 08:27:19 -0800 (PST) MIME-Version: 1.0 Date: Sat, 29 Feb 2020 17:27:08 +0100 Message-ID: <CAFstx=9nwFZeaE_cZ+69YAGY-cCE_6maP62A7X0VMTBC6Mwhqg(a)mail.gmail.com> To: test(a)example2.com X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.11 (lists.example1.com [192.168.0.1redactedIP]); Sat, 29 Feb 2020 16:27:20 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.11 (lists.example1.com [192.168.0.1redactedIP]); Sat, 29 Feb 2020 16:27:20 +0000 (UTC) for IP:'209.85.208.180' DOMAIN:'mail-lj1-f180.google.com' HELO:'mail-lj1-f180.google.com' FROM:'david(a)example3.com' RCPT:'' X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on lists.example1.com Message-ID-Hash: 2WKWCRI6GNTHTKGUKXSV3QI7JSG4BCCS X-Message-ID-Hash: 2WKWCRI6GNTHTKGUKXSV3QI7JSG4BCCS X-MailFrom: david(a)example3.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.3.0 Precedence: list Subject: [Test] ARC-test med aktiverad modul List-Id: Test for mail setup <test.example2.com> List-Help: <mailto:test-request@example2.com?subject=help> List-Post: <mailto:test@example2.com> List-Subscribe: <mailto:test-join@example2.com> List-Unsubscribe: <mailto:test-leave@example2.com> From: David Krantz via Test <test(a)example2.com> Reply-To: David Krantz <david(a)example3.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.11 (lists.example1.com [192.168.0.1redactedIP]); Sat, 29 Feb 2020 16:27:23 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.11 (lists.example1.com [192.168.0.1redactedIP]); Sat, 29 Feb 2020 16:27:23 +0000 (UTC) for IP:'127.0.0.1' DOMAIN:'localhost' HELO:'lists.example1.com' FROM:'test-bounces(a)example2.com' RCPT:'' RGV0IGjDpHIga2Fuc2tlIGZ1bmthci4gVmkgZsOlciBzZS4NCg0KLy8gREF2aWQKX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVGVzdGdhbmcgbWFpbGluZyBs aXN0CnRlc3RnYW5nQGtsYW1nYW5nZXQuc2UKaHR0cHM6Ly9saXN0cy56ZXJvdGguc2UvbWFpbG1h bjMvbGlzdHMvdGVzdGdhbmcua2xhbWdhbmdldC5zZS8K

5 years, 6 months

[MM3-users] Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-02 17:32, Mark Sapiro a écrit : > On 5/2/22 06:39, Michael Hazan wrote: >> Hello, >> >> When creating a list via postorius, i can see 3 style appear >> (announce, discussion, private). Is it possible to either create a new >> style and add it to that list or modify one of those style ? > > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Thanks i will look into setting up that plugin, hopefully an easier way to do that can make it's way to the default install. >> Also, coming from mailman2, you could directly set the members post >> moderation action when subscribing, now you can only do it via the >> user menu, is there a way to automate this in mm3 ? > > > I don't understand what you mean here. In MM 2.1 a member had only one > setting - moderated yes or no and if moderated there was a list > setting for the moderation action. There was also a list setting for > whether new members were moderated by default. How were you setting > the new member's moderation when subscribing? > > You are correct that when subscribing a new member, the member gets > the default action for members and different action has to be set in a > separate operation. I don't think this is significantly different from > MM 2.1. Also, can you describe what you mean by "automate this". in MM2.1, if you set the list to moderated and default action to hold posting, you can set a some member to be un-moderated (mod bit off) to automatically allow their posting. In the web interface of MM2.1 there is a checkbox with moderated bit on/off on the member list itself, in the postorius interface for MM3 you have to open each members settings page to access that. For automation, as list owner, upon registering a member (via mass subscription) the possibility to change that ? also the me too/dupe setting for example. Thanks

3 years, 4 months

[MM3-users] Re: Settings for prevention of spam obfuscation

by Richard Rosner

Well, I don't want to give users additional information, just rectify the manipulated information. And yes, while there may be edge cases where these bad practices do come in handy, but the vast majority of mails (at least from what I can tell from my lists) is either spammers or unnecessary abuse of features. I can't tell if it's because Microsoft sets bad defaults for Outlook or admins hired are incompetent and the competent ones either retire or quit, but there's just too much going on in mails that's just nonsense. E.g. encoding all text - including stuff like the subject - with base64 is just ridiculous, when what was sent is only plain text that uses a small subset of UTF-8 characters. And that's just a very common bad practice and far from the only one. And sure, competent spammers may be able to evade much more, I've seen several emails that must have had manipulated sender data, but that could only be concluded from context, not from analyzing the headers. But thankfully most spammers are far from competent, so spam filters can easily detect far over 50 % of the spam. It's only the slightly more competent spammers that use tactics abused by many non-spammers that give me a headache. I could easily crank up the spam points for various indications, so there would be pretty much no spam left in the false negative category. But sadly, I know from experience that this will lead to a much larger amount of false positives. For the most common senders that won't be sending spammers, I already created whitelisting rules, but that's about it. And until someone can create an ML model that's not gobbling up resources for training and that doesn't need thousands of emails to train with, there's only so much you can do. While DKIM and DMARC are great, they are useless when the vast majority of senders don't have any DKIM signatures. For ARC it's not as uncommon to be present, but the situation isn't that much better.

1 year, 6 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Hello Mark, thanks for your hint. Postfix is runnig as mta on my machine. I tested port 25 with swaks ->mail to user on server: localhost port 25 -> everything fine Mailman is configured with localhost for incoming and outgoing mails. After stopping mailman3, deleting all files in the queue directories, restart mailman3 I sent a test-mail /var/log/mailman3/mailman.log Apr 07 12:08:23 2020 (28198) Master started Apr 07 12:08:24 2020 (28206) out runner started. Apr 07 12:08:24 2020 (28202) command runner started. Apr 07 12:08:24 2020 (28203) in runner started. Apr 07 12:08:24 2020 (28200) archive runner started. Apr 07 12:08:24 2020 (28201) bounces runner started. Apr 07 12:08:24 2020 (28210) retry runner started. Apr 07 12:08:25 2020 (28208) rest runner started. Apr 07 12:08:25 2020 (28212) digest runner started. Apr 07 12:08:25 2020 (28205) nntp runner started. Apr 07 12:08:26 2020 (28211) virgin runner started. Apr 07 12:08:26 2020 (28207) pipeline runner started. Apr 07 12:08:26 2020 (28204) lmtp runner started. Apr 07 12:09:19 2020 (28203) ACCEPT: <000f01d60cc4$96c9a8d0$c45cfa70$@[domain]> Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost on port 25 I have no idea what to do for solving my problems. Regards from Hamburg Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Montag, 6. April 2020 23:50 An: Wolfgang Bock <mailinglisten(a)wbock.de> Betreff: Re: [MM3-users] Re: Uncaught runner exception On 4/6/20 2:44 PM, Wolfgang Bock via Mailman-users wrote: > Thank you Steven for your reply! > > I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server > on port 25", the former error message didn't show again. > > As I see port 25 is reseved for postfix. So I have to fiddle out how > mailman3 could also use this port for sending mails out. .... You need an MTA for Mailman to deliver its mail to. Normally this will be Postfix, sendmail, Exim, etc running on localhost and listening on port 25. Do you have such an MTA running on localhost? Note, Mailman does not directly send mail to end recipients. It only delivers mail to an outgoing MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Odhiambo Washington

On Fri, May 24, 2024 at 2:34 PM marcus--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hello, > > i already send this question to the plesk-forum but it seems that nobody > there can help me :-( > > After updating from Debian 10 to 11 to 12, I now have mailman3 running on > my server > I then converted all lists from Mailman2 to Mailman3 following the > instructions from mailman. > I can access it via the web interface, manage everything etc. > When I register on the web interface, I also receive the corresponding > mails from Mailman (forgotten password...) > Mails are also arriving, at least mails that are not allowed go into the > mails to be approved. > > The problem, however, is that it does not send out any mails, nor do they > appear in the archive. > > When I look in the Mailman-Log I find: > > May 16 01:44:55 2024 (6833) Cannot connect to SMTP server localhost on > port 25 > May 16 01:48:15 2024 (61252) error opening connection to nntp_host: > localhost > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Why is it talking about NNTP_HOST here? > [Errno 111] Connection refused > May 16 01:48:15 2024 (61252) NNTP error for list > vereinsmitglieder(a)ludothek.de: > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Also here! > [Errno 111] Connection refused > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is okay anyway, since we do not need nntp anyways. The configuration of Mailman.cfg looks like this: > > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > So I assume you followed some other guide to install your MM3. You did not follow https://docs.mailman3.org/en/latest/install/virtualenv.html. Is that right? If you used the above (recommended) method of installation, you'd end up with mailman.cfg whose contents of the [mta] section would look different from what you've shown above. Also, you'd have ended up with the following directory and files: ``` odhiambo@lists:/opt/mailman/mm/var/data$ pwd /opt/mailman/mm/var/data odhiambo@lists:/opt/mailman/mm/var/data$ ls -al total 100 drwxr-xr-x 2 mailman mailman 4096 Mar 16 00:11 . drwxr-xr-x 12 mailman mailman 4096 Mar 15 04:50 .. -rw-rw---- 1 mailman mailman 359 Mar 16 00:11 postfix_domains -rw-r----- 1 mailman mailman 12288 Mar 16 00:11 postfix_domains.db -rw-rw---- 1 mailman mailman 26481 Mar 16 00:11 postfix_lmtp -rw-r----- 1 mailman mailman 49152 Mar 16 00:11 postfix_lmtp.db odhiambo@lists:/opt/mailman/mm/var/data$ ``` Also, you'd have ended with the following (or equivalent) in your /etc/postfix/main.cf: ``` transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains ``` For now, you should find where these files are and point your Postfix to them and that may solve your problem. I am no Postfix Admin and I don't know nada about Plesk. > In Mailman manuals I find hints that the transport routes have to be added > to the Postfix-config. Doesn't Debian/Plesk do this automatically? > There is only one DEFINITIVE manual for Mailman3 and it is https://docs.mailman3.org/en/latest/install/virtualenv.html. It doesn't mention Plesk or cPanel :-) > Does anyone else have an idea what I need to change to get my mails out? > Yes. As I have detailed above, sin permissions issues. I did the conversion from mailman2 to mailman3 with root because it didn't > work with "sudo -u list "m, but the files stored in the file system all > belong to list, so that shouldn't be the problem. > Looks like a problem with the HOWTO that you followed. Here we're happier to help when you follow OUR HOWTO <https://docs.mailman3.org/en/latest/install/virtualenv.html> above. We're not quite enthusiastic when you follow other HOWTOs out there. Good luck! -- 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, 3 months

[MM3-users] Re: Show number of subscribers

by Abhilash Raj

On Tue, Jul 2, 2019, at 6:25 AM, Stephen J. Turnbull wrote: > andrew.bernard(a)gmail.com writes: > > > Would there be a way to show the number of subscribers to a list in > > the web UI? > > Currently the answer evidently is no. I'm not sure why Mark is > pessimistic (except that I don't see hordes of list owners breaking > down our doors for this feature), because I don't see why it couldn't > be added. HyperKitty already imports mailmanclient, so it can query > the list. If you want to pursue this, you should file an RFE in the > tracker, but I won't promise it will be very high priority, and it > does mean closer integration with core than we've had so far, so there > might be some unease from the developers. (I don't see why there > would be an issue, except for the slight increase in maintenance > burden.) Hyperkitty today aims to be functional without Core, what that means is that it can be used (with the exception of Replying/Posting via Web UI) while the Core is down/unavailable. While it isn't impossible, it would be a change of behavior compared to how it functions today. Although, if it is okay to have a value that is at max 24hr stale, Hyperkitty can pull the number of subscribers from the API daily with its routine job which pulls other information. Although, I'd like that process to be more realtime, but I haven't figured out a great way to do that yet. > On the other hand, we do have a bunch of students and others > interested who were attracted by Summer of Code and Season of Docs, > and one of them might find this an interesting task. It's not an > introductory project, but it looks straightforward to me, with > well-defined requirements. > > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: New Mailman Releases

by Abhilash Raj

On 10/26/22 12:32, Odhiambo Washington wrote: > > > On Wed, Oct 26, 2022 at 8:44 AM Abhilash Raj <maxking(a)asynchronous.in > <mailto:maxking@asynchronous.in>> wrote: > > Hi, > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.6 [1] > 2. Postorius 1.3.7 [2] > 3. Hyperkitty 1.3.6 [3] > 4. Mailmanclient 3.3.4 [4] > 5. Django-mailman3 1.3.8 [5] > > All the releases are published to PyPI and you can find links to all > the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > <https://docs.mailman3.org/en/latest/> > > A full list of changelogs are available below: > > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> > [2]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> > -- Something weird is going on with the page missing the bullets. > [3]: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 <https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6> > [4]: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… <https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien…> > [5]: > https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst> > > > Finally, the minimum Python version required is 3.7 although, 3.9 is > recommended if you are doing a new install for longest support. 3.10 is > supported for Django apps, but Mailman Core is missing that due to one > of the core dependencies not support 3.10 yet (aiosmtpd). > > > > Hello @Abhilash Raj <mailto:maxking@asynchronous.in> > > Thank you and the whole MM3 team for all the free work you do to make us > have mailing lists :) > > I have a question regarding the Python version. > I have a very recent installation of MM3, via the Virtual Environment > method, running smoothly - so far. > The Python version that got installed is 3.10.6 > > wash@lists:~$ sudo su - mailman > (venv) mailman@lists:~$ which python > /opt/mailman/mm/venv/bin/python > (venv) mailman@lists:~$ /opt/mailman/mm/venv/bin/python -V > Python 3.10.6 > (venv) mailman@lists:~$ mailma > mailmail3 mailman > (venv) mailman@lists:~$ mailman --version > GNU Mailman 3.3.5 (Tom Sawyer) > (venv) mailman@lists:~$ > > 1. What does the incompatibility with Python-3.10 portend for my setup > and anyone else with Python-3.10? The bug in aiosmtpd is a bit weird and has to do with how the test cases in aiosmtpd and Python 3.10 changes interact with SSL. For the intents and purposes of Mailman, we don't use SSL for the communication between MTA and aiosmtpd, so there _shouldn't_ be any issuer with your setup. Ideally, `pip` shouldn't have allowed you to install aiosmtpd in a Python venv with 3.10, but that depends on which version of pip you are using since the newer versions have better support for such management. > 2. Is it possible to downgrade the Python in a Venv down to 3.9 without > breaking the installation? You can keep the current installation running and create a 2nd installation by simply creating a 2nd venv with 3.9. Something like, `/opt/mailman/mm/venv-3.9/`. You can install things into that venv and when you are done and ready to switch, you can update all the paths in various places to use update 'venv-3.9' instead of 'venv'. In case you encounter any issues, you can always revert back to older 'venv' in the paths wherever the are needed and bring back the old install. Venvs are good for multiple installs so you can switch back and forth pretty easily. > > And finally, is there documentation/procedure to upgrade a VENV install > in this case? You don't want to upgrade venv is what i've heard, you should always create a new one if you are bumping python versions. If you are just upgrading packages in the existing venv, then you can follow: https://docs.mailman3.org/en/latest/upgrade-3.2.html -- thanks, Abhilash Raj (maxking)

2 years, 10 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Sat, Jan 28, 2023 at 10:48 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > > from mailman_web.settings.base import * > > from mailman_web.settings.mailman import * > > I think just putting these as close to the top as possible, and > including a comment (or two) saying that this is importing defaults > that can be overridden by any assignment made later in the file is > about as far as we can go for explaining. If you don't know how > Python imports work, just ask about the specific case. There's quite > a bit of potential complexity hiding in those '.'s; much more > complicated than the '/'s in a file system path. Trying to explain > the ins and outs of the Python import system is way beyond the scope > of Mailman docs. > > > [At first instance, it is not obvious that mailman_web.settings.base > > and mailman_web.settings.mailman are actually paths in Python - > > which magically translates to mailman_web/settings/base.py and > > mailman_web/settings/mailman.py] > > You shouldn't have to know that, it doesn't help with the bigger > problem of finding mailman_web, and any simple explanation might turn > out not to be true in your installation. This is why I prefer flat > files for end-user configuration, even if they get pretty big. I > understand why developers do stuff like this, but it's not "naive > user"-friendly. > > > For example, my mind all along has been tuned to having a > settings_local.py > > for overriding the settings.py. > > Yes, and that is a better system unless our intent is to *hide* > settings from the user, in my opinion. I don't see why you chose to > deviate from it. Either way you have to integrate settings you have > changed with settings the developers have changed. It's easier if you > stick with the system you're most familiar with. > > > However, with this particular documentation, it would appear that > > everything is intended to just go into /etc/mailman3/settings.py. > > > > Is it possible to modify the documentation > > Which documentation? We can modify our own, but that's a pretty big > task because we have several different systems for managing config > files over the last five or ten years. We shouldn't mandate any > particular organization because they all still work, and people who > use older setups shouldn't have to do without our docs. And we can't > do anything about out-of-date mirrors or HOWTOs by random admins on > the web. > > > and that those settings are in what file(s) ? > > But we don't know where those files are. If you use a venv install, > they're almost certainly in > $MAILMAN_HOME/venv/lib/python3.N/site-packages/mailman_web/settings/, > but otherwise the mailman_web/settings part could be anywhere on > Python's search path. And on modern systems unless you have a > dedicated host with everything installed at once, you're likely to > have 3 or more Pythons installed (Python 2.7, and two or more Python > 3s). So tools like find and grep -l are often more confusing than > enlightening. > > I think if you get confused, the most efficient solution is to just > ask. If Mark or I or whoever directs you to check out the defaults, > and you can't find them, ask again. > > Steve > All the above noted, and well-received. I only decided to experiment with this particular documentation because it is the *OFFICIAL* one. And to be honest, I am yet to wrap my head around everything, so I still have a lot of questions in my head. Will be seeing you often :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: Template Ignored?

by Stephen Daniel

Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. I've been playing with wget, and no matter what I put, I keep getting a 404 error. So: this works: wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/lists/list.example.com' but this does not (404 error): wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… ' Is there a way to list all templates? Or all templates for a list? On Thu, Feb 17, 2022 at 12:34 PM Stephen Daniel <swd(a)pobox.com> wrote: > That pulls a 404 error. Thanks for the hint. I will investigate. > > On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 2/17/22 08:04, Stephen Daniel wrote: >> > Mailman3 people -- >> > >> > I created a new list, and used postorius to create a template for " >> > list:user:notice:welcome". I then used the mass subscription feature to >> > add myself to the list, having checked "pre-confirmed", "pre-approved", >> and >> > "pre-verified". >> > >> > I received a welcome message that appears to be the default welcome >> > message. It certainly wasn't what I put into my template. >> > >> > Any suggestions on how I get mailman to use my template? Things I >> might be >> > doing wrong? >> >> >> What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a >> full URL by appending >> `/api/templates/list/list.example.com/list:user:notice:welcome` >> <http://list.example.com/list:user:notice:welcome> to that >> where `list.example.com` is the actual list_id of your list, and go to >> that URL, what do you get? >> >> -- >> 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, 7 months

[MM3-users] Re: Dist. List forwarding and DMARC Reject circumvention. Will this pattern work?

by Odhiambo Washington

On Sun, Aug 25, 2024 at 4:32 PM <titan160(a)hotmail.com> wrote: > I would be grateful if someone could vet and verify (or guide otherwise) > the following pattern please. > > With the major mail vendors move to DMARC - Full Reject, I have a small > challenge. > > - We have a number of 365 Distribution List addresses. > - These lists accept email from anyone and, currently, then forward those > emails onto list members. > - List members, however, are NOT necessarily email addresses within the > list's mail domain. They might be outlook.com, Gmail, yahoo, Hotmail, > username(a)local.ISP. > > Consequently, DMARC Reject policies are causing these emails to be marked > spam as the 365 Dist. List forwarding is not doing any header manipulation. > > My thinking is: > - I could set up a Mailman list (elists.mydomain.com) alongside the 365 > Exchange mail domain (mydomain.com) [0] > - I leave inbound mail deliver to the 365 Dist. lists. [1] > - I reconfigure the (mylist(a)mydomain.com) Dist. Lists to fwd to a > similarly-named Mailman address at the email sub-domain ( > mylist(a)elists.mydomain.com) [2] > - The Mailman list, by virtue of having to use the 365 MTA, should be > able to accept all inbound from the list (mylist(a)mydomain.com) [3] > - Mailman would then need to re-write the mail headers such that the > inbound email to-be-forwarded from the Mailman list, both appears to come > from the (mylist(a)mydomain.com) address, and also has the 365 'mydomain.com' > SPF and DKIM records. And given Mailman has to use the 365 MTA, it would > actually be coming from that main mail domain. [4] Aren't you creating a mail loop already? Where is MM3 sending the email to after receiving it (and supposedly modifying the headers)? And at this point [4], what are you trying to do that's different from what's already happening? The best way would be to have MM3 replace the From: addresses with its own address. Isn't DMARC mitigation what you want? > - Somewhere in there, the original sender's email address would need to > be included, such that a Reply-to-All from a receiving List member would > not only go back to the List, but also the original sender. That's what I see happening whenever I hit Reply-to-All on this MM3 list. > My thinking is that with this pattern, I don't need to worry about inbound > emails to the list address as that would simply continue to function as > normal, and fwdd mails from the List to recipient list members would not be > marked spam as the headers would all be good. > I would move everything from o365 distribution lists and just have those on MM3 on a subdomain. > Is my thinking good? Or am I out of my cotton-pickin' mind? > I am not saying your thinking is good or bad. 365 Exchange Admins will be able to help with that. My only issue is that you're complicating life for nothing. If you can have a subdomain with independent MX records, then why not just get the distribution lists out of 365 Exchange? You mentioned that they are 'Open' so what is the reason you're keeping them on 365 Exchange? 1. Run MM3 on lists.mydomain.com 2. Create a list named distlistname1 on MM3 and add all the addresses on that distribution list to this MM3 list. 3. Have distlistname1(a)mydomain.com subscribed to the MM3 list above 4. Have distlistname1(a)mydomain.com forward all the mails to distlistname1(a)lists.mydomain.com. The MM3 list will then do the necessary. In all these steps, what you have avoided is just getting everyone to use distlistname1(a)lists.mydomain.com - which is all you needed anyway. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year

[MM3-users] Message getting shunted with enabling Dmarc replace with list address

by Stephen J. Turnbull

bob B via Mailman-users writes: > If I set the dmarc to "replace with list address". the same message > gets shunted. If you can't allow the public suffix list (PSL) to be refreshed occasionally, it's cached by mailman/rules/dmarc.py, so you can prime the cache yourself. The file is $var_dir + "public_suffix_list.dat". var_dir and the cache lifetime are set in mailman.cfg. See section [dmarc], variable "cache_lifetime". The value should be a positive integer, with optional suffix from "dhms" with interpretation days, hours, minutes, seconds. (I think you can combine them as in 1h30m, but for this purpose a 10-digit number with any suffix should do.) If the section or value is missing, just insert it yourself so it looks like [dmarc] cache_lifetime: 1000000000s > Not sure why it is trying to contact publicsuffix.org? The PSL (according to the home page of publicsuffix.org) is A "public suffix" is one under which Internet users can (or historically could) directly register names. Some examples of public suffixes are .com, .co.uk and pvt.k12.ma.us. The Public Suffix List is a list of all known public suffixes. DMARC processing is quite burdensome for the DNS system, because it iterates up the chain of superdomains for the from address, looking for _dmarc.$domain each time, only stopping at the toplevel domain. Since each mail domain decides its own DMARC policies, and the public suffixes are (almost by definition) not mail domains, the PSL is an extremely useful and accurate heuristic. The savings can be large. For mydomain.pvt.k14.ma.us, with the public suffix list I check only mydomain.pvt.k14.ma.us, and if it fails I conclude there is no DMARC policy for mydomain. Without the PSL, DMARC requires looking at _dmarc.pvt.k14.ma.us, _dmarc.k14.ma.us, _dmarc.ma.us, and _dmarc.us, as well -- *all of which will fail because the suffixes are not mail domains*. The PSL saves 80% of the requests. That's an extreme example, but most countries do have similarly deep public suffixes, and most Internet domains hang off of names at least two deep like co.uk. Steve

1 year, 8 months

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sun, Feb 14, 2021 at 01:08, Victoriano Giralt <victoriano(a)uma.es> wrote: > 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... You can look at the commit history of the spanish po file to get a detailed history of when and who made the changes. For example: Core: <https://gitlab.com/mailman/mailman/-/commits/master/src/mailman/messages/es…> Postorius: <https://gitlab.com/mailman/postorius/-/commits/master/src/postorius/locale/…> You find similar histories in all the repos. Each person's changes should be an individual commit in the repo, typically all outstanding translations are committed every night in Weblate. > > 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). Could this be because of the .mo files not being up-to-update? There used to be some strings that were translated incorrectly, but I think we fixed all of those that we found. Abhilash > 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 ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> thanks, Abhilash Raj On Sun, Feb 14, 2021 at 00:57, Victoriano Giralt <victoriano(a)uma.es> wrote: > El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) > via > Mailman-users escribió: >> On 13/2/21 20:00, Mark Sapiro wrote: >> > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> > wrote: >> > > But... here is a thing that I can not understand: If the source >> (the >> > > .po >> > > file) is from november 7th, it doesn't matter how many times you >> > > recompile it: the result will be the same. >> > Correct, but the point is if you download the latest >> > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov >> 7 >> > file >> > in the distribution, you will find they are identical, so it it >> appears >> > that the weblate translation hasn't changed since that time. >> > >> > If there are issues in this mailman.po, they exist in weblate too >> and >> > need to be fixed there. >> >> That clarifies all. Thanks. As I said in my previous message, I'll >> wait >> for the next upgrade and hopingly the translations done after 7h of >> november (by others and me) will be there. > > 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 :-) > >> > Also note that the translations on weblate only affect strings in >> the >> > core code. The Mailman core templates are not currently >> translated in >> > weblate and there are currently no Spanish language templates. One >> > would >> > need to create Spanish translations of all the templates in >> > < >> > >> <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> >> > > >> > and submit a merge request to add them to a mailman/templates/es/ >> > directory. >> > >> I will make the template translations locally, test them, and then, >> if >> they are yet lacking in the main repo, follow your suggestion. > > I'm a bit short on time, but I'll help Guillermo with that, at least > reviewing or doing a second pass. I'm not proficient enough to speak > about > Mailman core templates, but for Django templates, there is a nice tag > for > marking text with translations in the .mo files ... > > -- > 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 ? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

4 years, 7 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/18/19 11:24 PM, Paul Arenson wrote: > > In the case of Mailman 3 much depends on the individual list and its settings, so my conclusion is it is mostly on me. With just a suggestion that you have a SIGN UP blue button to make things less confusing and not necessitating multiple clicking. This is difficult. See my reply to your first message. You will notice that when you click sign-up in either Postorius or HyperKitty, you go to <https://list.tokyoprogressive.org/accounts/signup/> which is neither Postorius nor HyperKitty but Django. So the current process is click sign-up, go to Django and sign up, then go back to Postorius and subscribe. To do this all in one step, Postorius would need to send you to /accounts/signup/?next=/postorius/lists/discuss.list.tokyoprogressive.org/ which it currently does, but there would need to be extra communication between Django and Postorius so that when Django returned to /postorius/lists/discuss.list.tokyoprogressive.org/, Postorius would know to tell Core to subscribe you. However, this is missing a step, because Django sends you an email requesting you to confirm your address, and you don't actually have an account until you confirm. This dance also renders the next=/postorius/lists/discuss.list.tokyoprogressive.org/ ineffective. Presumably Postorius could tell Core to subscribe you anyway even though you haven't confirmed your account, but Postorius doesn't know what address you signed up with. > The main obstacle I found was I had my list settings as NO to "Choose whether to include this list on the list of all lists". Changing this to "Yes" made it a little easier. > > Here are my two tests and conclusion. > > 2) TEST 1 > ________ > Sign up first... > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > ...you will find that if I have said NO on "Choose whether to include this list on the list of all lists” you will find it hard to go back to the subscribe page. Unless you backspace. Or paste the address again. Not ideal > > > QUESTIONS: Am I missing something? By not having my discussion listed, people cannot find it to subscribe. > > Or is NOT LISTED better where I add people manually to subscribe and then tell them to sign up? If you want people to be able to find your list by going to <https://list.tokyoprogressive.org/postorius/> or for that matter, to <https://mailman3.emwd.com/postorius/> or if you think having it there is helpful in any way, set List Identity -> Show list on index page to Yes. Otherwise set it to No. > 3) TEST 2 > ________ > One solution is I could put the list back on the host’s list of lists back and tell people to click on Discuss. > > That is what I did for now. Then it is rather smooth. I could tell my users (especially ones from previous company’s mailing list who want to interact with the hyperkitty site) > > to > CLICK LOGIN > CLICK SIGNIN > then follow all these steps: > > Verify > > Confirm > > Get taken to sign in page > > Click Discuss > > Subscribe > > Click Archives > > Or I could leave it as it is and tell people to backspace until they find the signup page and then subscribe. > > Or tell them to copy and paste https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > or https://list.tokyoprogressive.org/accounts/signup/ in the same browser window and then subscribe. > > CONCLUSION and SUGGESTION—> WHY NOT HAVE A SEPARATE BLUE BUTTON TO SIGN UP TO AVOID THE CONFUSING clicking twice? See above. > IS THIS THE ANSWER?— > > Tell my users as follows on a WORDPRESS PAGE as follows: > > - - - - - - - - - - - - > Greetings. If you have never signed up before, follow instructions A. If you are coming from the previous dadamail list, follow instructions B > > > INSTRUCTIONS A > Steps 1-3 to get on the mailing list and be able to post from your email account. > Continue to steps 4 and 5 if you want to see the archives and post from that page. (Note to Mark: I have turned the archives off by default to make it more of a no brainer to want to sign up) > > > INSTRUCTIONS B > You are already registered, you will continue to get messages and be able to send to the list. If you want to keep using the same email address you are all set and do not need to do anything. > > If you want to keep using the same address, but also be able to access the archives, follow steps 4 and 5 only. > > If you want to register a new address, follow steps 1-5 below. > > 1) Go here > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > Add your email address at the BOTTOM of the page. Name is optional. > > 2) Then wait for email to reply to come. > > 3) That’s it. You can stop here. However, you can sign up to the archives which makes this list more of a forum to see at a glance old conversations. And you can also post from it. To do so, continue to steps 4 and 5, > > 4) Right on the same page, you can sign up and sign in by clicking > log in and then sign up and then follow the same procedure as above. (Mark, SEE SUGGESTION FOR A BLUE SIGN UP BUTTON). > > 5) Once you have signed up, you can log in to access the archives and web posting. > - - - - - - - - - - - - > > Hope the above long winded post was clear. Feel like I am sseing the lite. > _______________________________________________ > 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/ > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Mailman3 Setup

by George R. Kasica

Mark: These all reference the virtual environment setup, which is fine if I need to go with that. I’ve already installed the components etc. As a “standard installation. Do you know of a good doc that would help me set up in a non-container environment – just the native OS – Ubuntu 20.04 LTS. If I need to go with a virtual environment, do I need to uninstall what I have out there and what’s the best way to get all the added bits out? --- George R. Kasica Phone: +1 414 732 8503 Fax: +1 206 374 6482 Owner Netwrx Consulting Jackson, WI USA gkasica(a)netwrx1.com http://www.netwrx1.com<http://www.netwrx1.com/> From: George R. Kasica <gkasica(a)netwrx1.com> Sent: Sunday, June 5, 2022 10:32 To: mailman-users(a)mailman3.org; Mark Sapiro <mark(a)msapiro.net> Subject: Re: [MM3-users] Re: Mailman3 Setup Thank you! Will take a look. — ===[George Kasica]=== 🇺🇦 On Jun 5, 2022, 10:29 -0500, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>>, wrote: On 6/5/22 06:26, George R. Kasica wrote: Hello: I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: Postfix Apache2 MySQL Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 3 months

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

by Stephen J. Turnbull

As Mark writes, MX has fixed IP A record, reverse DNS round-trips with A lookup, stay off RBLs, DKIM sign your mail are absolutely required. Using at least conditional DMARC mitigation is required, too. However, conditional DMARC mitigation won't help with gmx.net, it has the same DMARC policy as web.de: % host -t TXT _dmarc.gmx.net _dmarc.gmx.net descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@gmx.net" % host -t TXT _dmarc.web.de _dmarc.web.de descriptive text "v=DMARC1; p=none; sp=quarantine; rua=mailto:dmarcreport@web.de" The important part is "p=none", which says that GMX does not reject or quarantine *solely* because of a DMARC fail.[1] The conditional DMARC mitigation will *not* be applied for that domain for this reason. However, some sites consider From alignment (domain of DKIM signature = domain of author address in From:) in scoring spam. If GMX does that, unconditional DMARC mitigation may help. Two additional configurations that may help: 1. Authenticated Received Chain (ARC) is a relatively new standard which is used by some of the large American providers, specifically GMail and outlook.com. The basic idea is that your host will validate the digital signature on receipt of the post, add a header field reporting the results, and digitally sign that report. Many receiving hosts will then apply the same trust to your validation report that they do to your signatures. Maybe GMX will do it, too. 2. SPF is an older standard than DKIM, which uses the IP address of the source of the incoming connection instead of a digital signature. This may help in some cases, but it's much less important than DKIM signatures nowadays. As a last resort, you may disable all Mailman features (adding list tags or serial numbers to Subject:, adding header or footer to the body) that invalidate signatures. Unfortunately this may not be legal (some jurisdictions may require that you add instructions on how to leave the list). Steve Footnotes: [1] IIRC, the "sp=quarantine" means that some fraction of DMARC failing mail should be quarantined for testing purposes, but the default fraction is 0 so that is ignored.

2 years, 1 month

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

by Perry Kollmorgen

Thanks Mark. So, I have python scripts which do the adding of nonmembers and moderators. For the nonmember script I needed to add something so that the nonmembers can send, i.e the moderaction_action = 'defer' This is my code for nonmembers: mailing_list.add_role('nonmember', nonmember.email, display_name=nonmember.display_name) list_member = mailing_list.get_nonmember(nonmember.email) list_member.moderation_action = 'defer' list_member.save() For the code for moderators it currently only adds them: mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) Would I need to add something similar which sets a delivery_status for the moderator added ? Cheers, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 27 November 2024 2:16 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Notifying owners of membership changes but not moderators On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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 pcjkollmorgen(a)hotmail.com

9 months, 3 weeks

[MM3-users] Re: HTML header / footer template

by Mark Sapiro

On 06/18/2018 02:33 AM, Asaf Ohayon wrote: > I understand Mailman 3 doesn't want to support HTML Emails, > This is perfectly legitimate, sadly however, This is a requirement of my client, > Which is in this case the Ministry of Education of Israel. Mailman does support HTML email. Just adjust content filtering to not remove HTML and not collapse alternatives. What Mailman does not support (and which I think is what you want) is the addition of headers and footers either as text/html parts or inserted into text/html message bodies. The former would be fairly easy. Look at mailman/handlers/decorate.py. If the messages you are decorating are text/html or multipart/alternative or something more complex, the header and footer are going to be separate MIME parts anyway, so where we have > if len(footer) > 0: > mimeftr = MIMEText( > footer.encode(lcset, errors='replace'), 'plain', lcset) > mimeftr['Content-Disposition'] = 'inline' > payload.append(mimeftr) > if len(header) > 0: > mimehdr = MIMEText( > header.encode(lcset, errors='replace'), 'plain', lcset) > mimehdr['Content-Disposition'] = 'inline' > payload.insert(0, mimehdr) in two different places, just change the 'plain' arguments to 'html' and then the headers and footers will be added as text/html and can include html tags to be rendered. On the other hand, if what you want is to insert headers and footers at the beginning and end of an existing HTML body part, We will not make Mailman do that because it is very difficult to do it right. This is because just prepending or appending some additional HTML to an existing HTML part gives unpredictable results. You need to actually parse or render the existing HTML to determine how to add your additions and in complex cases even that may not render as you wish in all various MUA renderings. If you want to try for HTML what decorate does for simple plain text, you can try it and you may find it works for you, but it is way to fragile for a Mailman feature. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

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

by Odhiambo Washington

Make our lives easy: There are 3 files: mailman.cfg, settings.py, and main.cf. We expect that from these files: /etc/postfix/main.cf /etc/mailman3/mailman.cfg /etc/mailman3/settings.py For each file, do "egrep -v '^$|^.*#' filename". You should then obfuscate any sensitive details in the output and share the contents of the file. On Wed, Apr 30, 2025 at 8:01 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users(a)mailman3.org> wrote: > Am 30.04.25 um 15:36 schrieb Stephen J. Turnbull: > > Did you set var_dir or layout in mailman.cfg? If not, you may have an > > alternate var_dir which is either the current directory when you start > > Mailman or possibly /var/tmp/mailman. That is also where "mailman > > aliases" will put the postfix aliases (in the "data" subdirectory). > > It seems i set both *facepalm* while doing [1] and then adding changes > according to [2]: > > In mailman.cfg i have: > > [paths.here] > var_dir: /opt/mailman/mm/var > > but also > > [mailman] > layout: local > > > also checking via mailman conf: > > ''mailman conf -s mailman | grep layout'' > > Output: > [mailman] layout: local > > ''mailman conf -s | grep var_dir:'' > > Output: > > [paths.dev] var_dir: $cfg_file/../.. > [paths.fhs] var_dir: /var/lib/mailman > [paths.here] var_dir: /opt/mailman/mm/var > [paths.local] var_dir: /var/tmp/mailman > > so i have empty logs at /opt/mailman/mm/var/logs > and populated log files under /var/tmp/mailman/logs > > > If i recall correctly, setting layout: local is the suggested way to > do for virtualenv install [2], so deleting > > [paths.here] > var_dir: /opt/mailman/mm/var > > in mailman.cfg should be the next step (what i did). > > Restarting my services gave me the warnings again, but these are (we > remember) wrong paths (hash:/opt/mailman/mm/var/data/postfix_lmtp). > > so i looked under /var/tmp/mailman/data > and here we have populated files: > > -rw-rw---- 1 mailman mailman 268K Feb 19 12:51 mailman.db > -rw-rw---- 1 mailman mailman 377 Apr 30 18:01 postfix_domains > -rw-r----- 1 mailman mailman 12K Apr 30 18:01 postfix_domains.db > -rw-rw---- 1 mailman mailman 1.8K Apr 30 18:01 postfix_lmtp > -rw-r----- 1 mailman mailman 12K Apr 30 18:01 postfix_lmtp.db > > Now - before changing the /etc/postfix/main.cfg - there is the > question that brings us almost back to the start: > > With respect to [2]: > > "If you are installing Mailman from source (or using Pip), it is > recommended to use paths.local." > > and [3]: > > " > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = > hash:/opt/mailman/mm/var/data/postfix_domains > > […] > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/path-to-mailman/var/data/postfix_lmtp > " > > **what is the recommended place to put the files to?** > > > I believe it to be /var/tmp/mailman/data according to > > [mailman] > layout: local > > and that the above specific /opt/mailman -part is just a leftover from > former times (the second and more generic part with /path-to-mailman > indicates that to me). > > If my assumption is correct i would create an issue + merge-request for > the docs. > > lg > aiz > > > + [1] https://docs.mailman3.org/en/latest/install/virtualenv.html > + [2] > > https://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem… > + [3] > https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mta > > _______________________________________________ > 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 odhiambo(a)gmail.com > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 2 weeks

[MM3-users] Re: Digests not working correctly

by Joel Lord

On 6/4/2023 9:25 PM, Mark Sapiro wrote: > On 6/4/23 11:45, Joel Lord wrote: Thanks for the explanation on size-triggered digests. >> Periodic is much more complicated, even to explain. I have the cron >> job running nightly at 11:00 PM and it certainly seems to be working, >> except for one really odd thing. The list also definitely has >> periodic digests enabled in the web UI. This is a very bursty list, >> so it will go mad with traffic for a few weeks and then will go mostly >> idle for a month or so. The first digest of a burst is definitely >> size-triggered, but pretty reliably it has the last few messages from >> the previous burst in there. So the one I got today had three >> messages from today and one message from May 4th. But that May 4th >> message should have gone out at 11:00 PM on May 4th with the daily >> digest and then gotten flushed from the pending digest queue, right? > > That's correct. Do you ever get periodic digests sent at 11:00 PM? If > not, there is some issue either with configuration or something. If you > get them sometimes, I don't know what could be wrong. The periodic digests do seem to be coming out. I also now have confirmation that the one message in this morning's digest that was from May 4th was also included in the last digest back on May 4th, so it seems that the one message was left behind in the digest queue when the periodic digest was sent. There was one earlier message to the list back on May 4th, before the one that got duplicated, but I can't tell if that triggered a size-based digest to be sent: the logs aren't clear enough on that detail for me to tell. Just to inform things: (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman django-mailman3==1.3.9 mailman==3.3.8 mailman-hyperkitty==1.2.1 mailman-web==0.0.6 mailmanclient==3.3.5 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper mailman-hyperkitty==1.2.1 (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post postorius==1.3.8 -- Joel Lord

2 years, 3 months

[MM3-users] Mailman3 Issue with Sending Mail to Yahoo/AOL

by Stephen J. Turnbull

chris--- via Mailman-users writes: > I've been getting complaints from the Yahoo people that mail is > delayed at times, or messages that come out of order. That could be due to greylisting. > (host mta6.am0.yahoodns.net[67.195.204.74] said: 452 Too many > recipients tnmpmscs (in reply to RCPT TO command)) You could try enabling personalization in Mailman. Then each user's message is different, so it will send one per transaction. Depending on negotiation between your MTA and the receiving MTA, this may not be too inefficient because the connection will be reused (aka pipelining). The other possibility would be to tune your MTA to send smaller batches. However ... > (host mta6.am0.yahoodns.net[67.195.204.74] said: 421 [IPTS04] > Messages from 74.112.73.65 temporarily deferred due to unexpected > volume or user complaints - 4.16.55.1; see > https://postmaster.verizonmedia.com/error-codes (in reply to end of > DATA command)) Personalization could exacerbate the problem with unexpected volume depending on how they measure volume (by the number of messages or by the number of recipients). Not much you can do about that except hope they'll learn that sometimes there's list traffic and sometimes there's not. Have you looked up this error code (IPTS04)? > So it seems that Yahoo/AOL keeps detecting my mailman3 server as > either spam, sending too much email, or too many recipients. I don't think it's detecting spam, or it would say so (or perhaps just blackhole your mail). > Anyone anyone shed some light on how to appropriately solve this > issue? The only real solution is to boot subscribers with AOL/Yahoo/Verizon addresses. That's likely not something you want to do, unfortunately, and subscribers are unlikely to take suggestions that their email provider sucks, and they should change to a competent one, kindly. Ironically enough, the Japanese government did exactly that in 2014, prohibiting use of Yahoo addresses by government employees or entities -- but yahoo.co.jp is a completely different company from yahoo.com (they licensed the name and the search engine etc), and their email is apparently more competently run, in any case they don't bounce list traffic or cause DMARC problems.

4 years, 4 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/14/19 11:10 PM, Stephen J. Turnbull wrote: > > Torge Riedel writes: > > > > > - there is a way to do this now via settings_local.py, but feels > > > a little bit risky if default configuration changes on update of > > > mailman > > > > This should not be true. If it is, we need to fix that. Will check. > > > It is more or less true [...] the only way settings_local.py can > change something like INSTALLED_APPS is to redefine INSTALLED_APPS > in it's entirety which leads to the possibility of INSTALLED_APPS > changing in settings.py and those changes not being picked up in > settings_local.py. That's a different issue from the one I believe Torge is worried about, which is an update overwriting settings_local.py. But it's not good. > The way around this is to remove the import of settings_local from > settings.py and then put > > from settings import * > > at the beginning of settings_local.py and then point Django at > settings_local rather than settings. I don't understand the ramifications of making this change (presumably Barry or somebody had a reason for the change from Mailman 2's method), but at first glance it looks like a big step in the right direction. > Then you can do things like > > try: > INSTALLED_APPS.remove('allauth.socialaccount.providers.google') > except ValueError: > pass > > in settings_local.py except there are still issues because, e.g., > INSTALLED_APPS is defined as a tuple (immutable) and not a list in > settings.py. Given the concerns of privacy advocates, I would say that it would be better to have a separate AUTH_PROVIDERS = ['allauth.socialaccount.providers.google', ...] in settings_local.py, and merge that in to INSTALLED_APPS. Of course removing specific providers would be OK too, but I think that this is a place where "deny all / accept what you want" is appropriate. 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, 7 months

[MM3-users] Re: Two trivial questons:

by Bill Oliver

I take that back. I went back and made another superuser using mailman-web create superuser. But... I still get bounced with the error: Forbidden (403) CSRF verification failed. Request aborted. More information is available with DEBUG=True. my uwsgi.log generates: [pid: 1385|app: 0|req: 14/22] 127.0.0.1 () {52 vars in 1078 bytes} [Wed Oct 9 23:15:17 2024] GET /accounts/login/?next=/mailman3/lists/ => generated 8204 bytes in 33 msecs (HTTP/1.0 200) 11 headers in 509 bytes (1 switches on core 1) [pid: 1385|app: 0|req: 15/23] 127.0.0.1 () {62 vars in 1230 bytes} [Wed Oct 9 23:15:27 2024] POST /accounts/login/ => generated 1019 bytes in 2 msecs (HTTP/1.0 403) 8 headers in 268 bytes (1 switches on core 0) So it wasn't that I forgot the superuser name. It's getting denied. That's all I got. Any help would be appreciated... billo On Wed, 2024-10-09 at 19:04 -0400, Bill Oliver wrote: > First: > > Last night I got everything installed and, I think, working. > Unfortunately, I forgot to write down the name and password of the > superuser I created. I know what I put in as password, but I cant' > remamber the name of the superuser. > > I know I could just create another superuser with "mailmanweb > createsuperuser" but I was wondering if there was a "mailmanweb" > command for *listing* superusers. > > If not, I'll just make another superuser... > > Second: > > I have the "example.com" error in the login screen. The instructions > state that this is a problem with making SITE_ID=1. Okay, but I > don't > know what to change it to. I tried SITE_ID=2 on a lark and everything > broke, and the instruction say not to do SITE_ID=0. Apparently it > has > to be an integer (I also tried putting in site name and got that > error). So... where do I change it? > > Thanks! > > billo > _______________________________________________ > 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 billo(a)billoblog.com

11 months, 1 week

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

by Torge Riedel

I'll do a top post to sum things a bit up (from my point of view and requirements): - no need to disable social logins by default, there are and will be setups where this is required and wanted, but: - allow disable of social logins either by config file or admin web UI in a stable way, means: after update of mailman nothing gets broken if default configuration has changed - there is a way to do this now via settings_local.py, but feels a little bit risky if default configuration changes on update of mailman Maybe there is a possibility for a simple approach via config file: EXTRA_LOGINS = no or ENABLED_EXTRA_LOGINS = [] (maybe not valid py code, but just to show how it might look like) Best regards Torge Am 14.02.19 um 03:42 schrieb Stephen J. Turnbull: > 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. > > > 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. > > > 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. > > > 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). > > > 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. > _______________________________________________ > 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, 7 months

[MM3-users] Re: Mailman issues after re-boot

by paulrubin37＠gmail.com

PROGRESS, Thank you. mail:/etc # zypper info python311-Django Loading repository data... Reading installed packages... Information for package python311-Django: ----------------------------------------- Repository : Main Repository (OSS) Name : python311-Django Version : 4.2.5-1.1 Arch : noarch Vendor : openSUSE Installed Size : 29.3 MiB Installed : Yes (automatically) Status : up-to-date Source package : python-Django-4.2.5-1.1.src Upstream URL : https://www.djangoproject.com Summary : A high-level Python Web framework Description : Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. (venv) mailman@mail:~> pip install --force-reinstall psycopg2-binary Collecting psycopg2-binary Obtaining dependency information for psycopg2-binary from https://files.pythonhosted.org/packages/ce/85/62825cabc6aad53104b7b6d12eb2a… Downloading psycopg2_binary-2.9.9-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (4.4 kB) Downloading psycopg2_binary-2.9.9-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.0 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.0/3.0 MB 6.9 MB/s eta 0:00:00 Installing collected packages: psycopg2-binary Attempting uninstall: psycopg2-binary Found existing installation: psycopg2-binary 2.8.6 Uninstalling psycopg2-binary-2.8.6: Successfully uninstalled psycopg2-binary-2.8.6 Successfully installed psycopg2-binary-2.9.9 (venv) mailman@mail:~> pip install --force-reinstall psycopg2 Collecting psycopg2 Downloading psycopg2-2.9.9.tar.gz (384 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 384.9/384.9 kB 2.2 MB/s eta 0:00:00 Preparing metadata (setup.py) ... done Building wheels for collected packages: psycopg2 Building wheel for psycopg2 (setup.py) ... done Created wheel for psycopg2: filename=psycopg2-2.9.9-cp311-cp311-linux_x86_64.whl size=505693 sha256=f0288149e9e27a5b88cc041b9385bc1f1c3a8e95958d0edf5de6d47ef3d6aadb Stored in directory: /opt/mailman/.cache/pip/wheels/ab/34/b9/78ebef1b3220b4840ee482461e738566c3c9165d2b5c914f51 Successfully built psycopg2 Installing collected packages: psycopg2 Attempting uninstall: psycopg2 Found existing installation: psycopg2 2.8.6 Uninstalling psycopg2-2.8.6: Successfully uninstalled psycopg2-2.8.6 Successfully installed psycopg2-2.9.9 (venv) mailman@mail:~> python -c 'import psycopg2' (venv) mailman@mail:~> mailman info GNU Mailman 3.3.8 (Tom Sawyer) Python 3.11.5 (main, Aug 31 2023, 07:57:41) [GCC] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:XXXXX@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@mail:~> I went the through the rest of the install got the login screen and after logging in I get this: Forbidden (403) CSRF verification failed. Request aborted. Looking at the PostgreSQL db, the user table has certainly been emptied the only user is mailman. The UID, address and mailing list tables seem to contain many records. I am not sure how much to restore of the original DB? Short of doing a diff on two backup file do you have any insight? Thanks Paul.

1 year, 11 months

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

by Stephen J. Turnbull

Hi Shashikanth, It appears I may have sent you on a wild goose chase. You have my apologies. There's a very similar report today, so this appears to be a Mailman 3 issue. For now, pleasee see Mark's post for the correct way to increase timeout: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I am working with Mark to diagnose the underlying problem. Steve Stephen J. Turnbull writes: > Shashikanth Komandoor writes: > > > I am currently running Mailman 3 with version 3.3.1 and in > > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version > > with default values in production environment from the past 4 months > > almost. As of now, we are having around 1327 lists created on this. > > Aren't you the crew that modified Mailman to interface with SMS or > something like that? If so, don't worry, it doesn't invalidate your > warranty, but it seems possible that it has something to do with this: > > > After the above configuration, I found many errors like below in > > mailman.log file: > > > > *sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for > > column 'pended.id <http://pended.id>'"* > > > > *sqlalchemy.exc.ResourceClosedError: This result object does not return > > rows. It has been closed automatically.* > > > > *sqlalchemy.exc.DatabaseError: (psycopg2.DatabaseError) error with status > > PGRES_TUPLES_OK and no message from the libpq* > > Whether you have that modified Mailman or not, the messages above > suggest that there may have been a change in the schema of the > database that one side (presumably SQLAlchemy) knows about but have > not been propagated to the other (PostgreSQL). Have you perhaps done > an upgrade but not run the database migration script? > > About the REST API not available error: > > > Something went wrong > > > > Mailman REST API not available. Please start Mailman core. > > > > But my mailman core was working fine in the background. At > > the same time I was able to do other operations on a few other lists. > > > > By the time I am getting the above error, the mailman.log > > recorded the below messages. > > > > *[2020-09-16 12:49:08 +0530] [2600] [CRITICAL] WORKER TIMEOUT (pid:20234)* > > > > *[2020-09-16 12:49:08 +0530] [20234] [INFO] Worker exiting (pid: 20234)* > > > > *[2020-09-16 12:49:09 +0530] [21042] [INFO] Booting worker with pid: 21042* > > Something is taking too long, the worker is timing out. That's > probably why you get the REST API not available message. Do the > sqlalchemy errors correlate with the timeouts? > > I suspect the exit and reboot of the worker is normal but I haven't > looked at this part of the code. > > > My mailman.cfg configuration is as below. The timeout > > value is the default value. I did not set any customized value. > > Thanks for sending it; sometimes it speeds up debugging. But in this > case you say that other lists are working, so site configuration > doesn't seem to be the problem. Is this particular list special in > some way? List configuration is different? > > > The above might be few of the errors. FYI, for the creation of each list, > > it is taking almost around 15 to 20 minutes. After multiple times of the > > above error messages, at some time, I am fortunately getting the list > > created or some other operation getting done. > > This is quite strange. I don't see why this would suddenly start > working after many minutes. > > Does PostgreSQL have any logs with "interesting" (or scary) messages > in them? > > Maybe somebody else has some ideas, but this is as far as I can go. > _______________________________________________ > 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/ > >

5 years

[MM3-users] Re: Verification Failed Error

by Odhiambo Washington

On Fri, 21 Dec 2018 at 20:19, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Fri, Dec 21, 2018, at 4:00 AM, Stephen J. Turnbull wrote: > > Abhilash Raj writes: > > > > > Exim experts would be able to help you better with this. > > > > I'm the one who set up the original sample Exim .conf, because (a) I > > didn't want to migrate all my bots to Postfix, and (b) the one-real- > > host .conf turned out to be trivial. I'm an Exim expert only for my > > own configuration, which is a (pre-global-warming) glacially-moving > > target. I've never seen anything like the problems described here, > > sorry. Can't help. > > > > Since it's looking like we don't have any real Exim experts hanging > > around here, perhaps we should move the sample containers and other > > default configs to assume Postfix and document "Exim should work but > > you're kinda on your own, we'll do what we can but it's limited." At > > least Mark is maintaining such systems, and they're probably better > > documented than Exim for the single-real-host configuration, though > > they would probably run into similar problems with the containerized > > setup. WDOT? > > > Originally, the reason I went with Exim was because the postmap + hash > files were hard to generate for Mailman from within the container when > the postfix was running on the host. Exim checks existence of certain > paths to verify that the Mailing List exists, which was easier to do. > > However, now Mailman Core supports regex maps for Postfix, which > can be used with containers. > > Images already support using Postfix, it is just not the default in setup > scripts and documentation. I have opened an issue[1] to maybe change > that if some initial testing doesn't goes fine. > > [1]: https://github.com/maxking/docker-mailman/issues/282 > Hello Maxking, It is importantest to maintain Exim support :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 8 months

[MM3-users] Re: [Mailman-Developers] Better documentation for Mailman Core's config options

by Barry Warsaw

Wow, this is amazing Abhilash! So much better than the old wall of text, and so cool that you learned how to write a Sphinx plugin while you were at it. Cheers, -Barry > On Aug 7, 2020, at 12:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hey All, > > For the past few days, I've been trying to improve the documentation > style for Mailman Core's config options. Internally, Mailman has > all configurations defined in an ini formatted `schema.cfg` file, which > serves as a schema for our `zope.configuration` library. We had that file > simply embedded in the sphinx documentation previously as a wall of text. > > I ended up writing a Sphinx (our documentation generator) plugin which > parses the config file and presents the same documentation with more > bells and whistles so it is easier to lookup and link sections and config > options.[1] > > The process of doing that was fun and I learnt how to write a simple > sphinx plugin, so yay! It treats the comments above each config option > in the ini file as it's doc and basically generates ReST text that it passes > to Sphinx to parse and convert to the markup format that you see in > browser. You can look at it in the source repo[2] . > > Do note that not all sections are documented yet, I am still figuring out what > would be a good way to document template sections like `[plugins.master]` > and other similar sections of that kind. > > [1]: https://gnu-mailman--667.org.readthedocs.build/projects/mailman/en/667/src/… ((URL is for the PR, > the main doc seems like is serving the cached version from an older > build). > [2]: https://gitlab.com/mailman/mailman/-/blob/master/_ext/configplugin.py > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > Mailman-Developers mailing list -- mailman-developers(a)python.org > To unsubscribe send an email to mailman-developers-leave(a)python.org > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ > Mailman FAQ: https://wiki.list.org/x/AgA3 > > Security Policy: https://wiki.list.org/x/QIA9

5 years, 1 month

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Abhilash Raj

On Tue, Oct 3, 2017, at 12:28 AM, Henrik Rasmussen wrote: > > Fra: Mark Sapiro [mailto:mark@msapiro.net] > > Sendt: 2. oktober 2017 17:26 > > Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode' > > > >> Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > > > There is no user or list admin workaround, but the defense is a fairly > > simple patch. See the MR at > > <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit > > at > > <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. > > The commit changes 7 files, but only two are needed. The rests are tests > > or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't > >necessary. > > > > The only changes you need are those to mailman/email/message.py and > > mailman/mta/connection.py. > > I am using Docker-mailman (not yet very familiar Docker and version > control). I would expect I have to wait for a Docker-mailman release > including this change, right? > > I have at least five+ lists which almost haven't been working since my > switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am > desperate trying to figure out whether it is best to fall back to the > Mailman 2 server, for the time being, where the lists came from, or it is > better to wait for an update to the Docker-image. > > Will https://github.com/maxking/docker-mailman/milestone/2 fix my > problems regarding failed mail handling and will it become available soon > (when?) (https://github.com/maxking/docker-mailman/issues/147)? The container images have stable releases of Mailman components, so those changes will make in to the container when a new Core release happens. The next image release is pending a version upgrade of Hyperkitty, to 1.1.3, but other changes are just meant to make the process of setting up Mailman better. They do not include changes from git repo after the release. -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

[MM3-users] Re: Verification Failed Error

by Abhilash Raj

On Fri, Dec 21, 2018, at 4:00 AM, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > Exim experts would be able to help you better with this. > > I'm the one who set up the original sample Exim .conf, because (a) I > didn't want to migrate all my bots to Postfix, and (b) the one-real- > host .conf turned out to be trivial. I'm an Exim expert only for my > own configuration, which is a (pre-global-warming) glacially-moving > target. I've never seen anything like the problems described here, > sorry. Can't help. > > Since it's looking like we don't have any real Exim experts hanging > around here, perhaps we should move the sample containers and other > default configs to assume Postfix and document "Exim should work but > you're kinda on your own, we'll do what we can but it's limited." At > least Mark is maintaining such systems, and they're probably better > documented than Exim for the single-real-host configuration, though > they would probably run into similar problems with the containerized > setup. WDOT? Originally, the reason I went with Exim was because the postmap + hash files were hard to generate for Mailman from within the container when the postfix was running on the host. Exim checks existence of certain paths to verify that the Mailing List exists, which was easier to do. However, now Mailman Core supports regex maps for Postfix, which can be used with containers. Images already support using Postfix, it is just not the default in setup scripts and documentation. I have opened an issue[1] to maybe change that if some initial testing doesn't goes fine. [1]: https://github.com/maxking/docker-mailman/issues/282 > > 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 > _______________________________________________ > 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: Postorius: Show only own lists

by Terri Oda

On January 23, 2018 6:26:51 AM PST, Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: >2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > >> On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: >> >>> Imagine an installation with 500+ mailing lists and almost as many >local >>> admins that are supposed to maintain their own local lists with a >few >>> local >>> members. As site admin, I see all 500+ lists, but I was expecting >*local* >>> admins to see only the lists they maintain. I have set all lists to >>> "advertised = False", so they are hidden from ordinary view. Is >there a >>> way >>> to show only relevant lists to local admins? >I believe I wrote Postorius in the subject line, but it may not be so >obvious. So yes, in Posterius I would like to hide the lists from email >harvesters, while relatively "untrusted" admins should have access to >basic >operations on the one list he/she "owns" (and without having to browse >through 50 pages of mailing lists). Somehow I don't think 500 >superusers in >our system is a good idea! What do you mean by local admins? Is this 1. Giantsite.example.com hosts lists for a bunch of domains, and you want the logged in admins of mydomain.com to see their list admin pages but not otherdomain.org's lists 2. You want each logged in admin to have their own personal dashboard of list admin pages for lists they administrate, even though they're all under one big domain. (Neither of those scenarios talks about archives, since you say you're only talking about postorious) I think #2 is something we should be doing, and the old "todo" section of the interface kind of was made with that in mind. Probably worth mocking up some screenshots and opening a feature request to keep the idea in mind, but it should be more a matter of prioritizing how things are displayed than any huge change. I'm not sure if we have a "local admin" concept in the system that lines up with #1, though.

7 years, 7 months

[MM3-users] Re: Set Postorius interface locale

by Abhilash Raj

On Tue, Mar 2, 2021, at 7:55 AM, Duane Raymond wrote: > Hi everyone, > > Thanks to Brian I'm up and running with my migrated mailman3 lists and > am now starting to get into customising the interface (styling and > content). I've been trying to figure out how to set/change the > Postorius locale - I specifically want to change some text strings on > the info page without breaking the i18n mechanisms. I've worked with po > and mo files before, so changing and compiling them isn't a problem. > The problems I've encountered so far are: > 1) Where do I set the local of the Postorius interface? The installation has a default Language setting which you can set in the settings.py LANGUAGE_CODE = "en" > 2) Individual lists have a language setting, but it doesn't seem to > reflect what the Postorius locales are as the only english option is > "English (USA)" and none of the other English speaking locales and on > the file system there is no en-us PO files....so I suspect I'm looking > in the wrong place. List level settings affect the Mailman level emails that go out, not the interface. The users can choose which language the interface shows up in using their browser settings. We primarily depend on the Accept-Language header in the request to determine the language of the response. While users do have a preffered-language setting, it currently isn't used to determine the language of the UI. Like list setting, it is only used to determine the language of the emails sent out (user's preferences override the list's default language). > > Am I looking at this all wrong? The documentation doesn't seem to have > any info about this and yet the mechanisms seem to be there. > > Once I learn more I'm quite keen to start working on improving the > documentation based on what I learn. > > Cheers, > > Duane > _______________________________________________ > 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, 6 months

[MM3-users] Re: how to integrate subscription into static jekyll website

by Hagen Bauer

Since I am running mailman in a docker container I thought it may be an approach to put https://github.com/dthree/mailit along. This seems to be used by a good amount of people and would allow me to have a rest api just for sending the mails to mailman. I am not a javascript specialist but currently I do not see any security risks. Do I miss something? Regards Hagen On 10/19/18 8:05 PM, Stephen J. Turnbull wrote: > Hagen Bauer writes: > > > Has anybody tried to hide the direct api access behind a nginx reverse > > proxy url? > > Sounds straightforward. > > I doubt anybody's done it, though, because you still face the problem > that anybody with that access is a site manager, with unclear limits > on their power outside of Mailman. (Shouldn't be much they can do > outside of Mailman, but I wouldn't bet my host on it.) In many cases, > the real site manager is also the host admin, so they have sufficient > access to a shell account. There's no need for her to have a proxy; > why make it available to people who are supposed to have less power? > > Note I'm *not* saying this *never* makes sense. I'm just saying that > in a lot of cases it won't buy you very much because Mailman isn't set > up to provide granular authorization of REST endpoints. > > > on the Webseite I would have a url like this > > > > mailmanserver.tld/subcsribe/user(a)mail.com > > > > And within the nginx proxy configuration on the server this would > > translate to > > > > localhost:80xx/"mailman-restapi-with-credentials"user(a)mail.com > > First of all, the address to subscribe is a variable, so at a bare > minimum your nice static site has to provide a form, which isn't very > static. I guess you could put the URL to the nginx proxy as the > action URL in the form, but then the proxy needs to deal with a > form-encoded query string to translate to the appropriate REST > endpoint. > > I suppose you could also have the user type the URL including the > email address into the browser address bar, but Abhilash's idea of > providing a mailto:subscribe@mailmanserver.tld URL seems more > convenient. The mailto URL also solves the problem of confirming > ownership of the mailbox, since that logic is built in to the > subscribe-by-mail code. > > Second, if your proxy is configured very carefully, you might be able > to restrict this to only the exact operations you want to expose, here > subscription. However, although the email interface implements > verification by providing a one-time token that must be read from the > mailbox of the address (and so proves ownership of the mailbox), I > don't think the REST API implements operations like that. IIRC that > is implemented in Postorius. (Abhilash?) If my memory is correct, > you would also need to implement that, and that's definitely not static. > > > So the public does not see the credentials. And if my nginx host > > config is hacked I have a problem anyway. > > I can't speak for Abhilash, but what would worry me is not that nginx > is already hacked, but rather that if not properly configured, it > might be possible for someone to access REST endpoints you don't want > exposed through this interface, and maybe even to other parts of the > webserver. To give a simple example, consider a variant on the > ancient Apache traversal bug: > > mailmanserver.tld/subscribe/../unsubscribe/user(a)mail.com > > Probably nginx and/or Mailman and/or your proposed proxy config are > already capable of stopping this particular well-known attack, but > undoubtedly there are more sophisticated attacks that I don't know > about. > _______________________________________________ > 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, 10 months

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

by Ruth Ivimey-Cook

Stephen J. Turnbull wrote: > I don't understand. I'm not in a position to test with Mailman itself > right now, but the standalone gunicorn[1] does the right thing (takes > an IP address and binds to the corresponding interface, or takes a > domain name, resolves it to the IP address, and binds that to the > corresponding interface). It does not substitute localhost. The localhost address is coming in via the hosts file, which is a relatively standard practice IMO. I could change it, but then perhaps other things would not work. I would prefer to be able to specify what I need. There are also things like systemd-resolvd which will do the localhost-substitution for you even if /etc/hosts doesn't. I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and changing the cfg file hostname back to the full name of the host, and that now works!! -- in that the problem I showed earlier is gone. However I then get another issue. From the mailman.log file I now see in the last few lines. For clarity I've numbered them like this "{1}": {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" "GNU Mailman REST client v3.3.1" {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" {3} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" At this point the browser screen reports "Something went wrong" and the message "HTTP Error 404: {"title": "404 Not Found"}" Previously, the process stopped at line {1}. Now that and line {2} is executed (AFAIK) correctly, but then line {3} is isssued. I have no idea why something is looking for "domains/greyarea-web1": - Only the "ch-bc.org.uk" domain is listed in the reply to line {1}, as expected; - "greyarea-web1" doesn't appear in any lists I can show with the "mailman" cli command (and I think I tried them all); - "greyarea-web1" doesn't appear anywhere in the source or config other than as the name of the host its running on or as an ALLOWED_HOST; - I tried using "curl -X DELETE" (from the api docs) to delete a domain called that and it says no such list exists. My only possible clue is that I think, at some point in the journey of configuring mailman, I might have created a list called that on the host. However since then I have wiped the install files and reinstalled. I cannot make sense of this being the answer given the checks just listed. I went looking through the python source and can see that the get() function does indeed throw a 404 exception if the domain isn't found, but I cannot see which code is parsing the reply from the first line So I have two questions: 1) How can I fix this problem? 2) why does getting an 404 reply here cause the postorius web page to produce a "something went wrong" /404 and nothing else, when it could have simply reported that something had gone wrong with one specific domain; > I'd rather not enable the complexity of a multihomed application > unless there's an important use case. (I don't make the final > decision, but I am listened to by Those Who Do.) You wonder about multihome hosts, but should a host have more than one interface (as several of my VMs and physical hosts do), being able to specify which of the possible addresses to listen on could be very useful in the case that "all of them" is the wrong answer. There is no complexity for the developers beyond what is already supported and working. The only point I can see wrong here is the mailman3-core is using one hostname value for two distinct purposes, and IMO it shouldn't. Ideally, and this is icing on the cake, a listen address specification should allow multiple IPs to be passed in, in which case the server listens on all of them. I expect the python libraries already support this. Thanks to all for the help so far, Ruth

5 years, 2 months

[MM3-users] Re: SPF check fails for lists subdomain

by Jan Eden

On 2023-01-05 11:13, Odhiambo Washington wrote: > On Thu, Jan 5, 2023 at 10:56 AM Jan Eden via Mailman-users < > mailman-users(a)mailman3.org> wrote: > > > On 2023-01-04 15:07, Mark Sapiro wrote: > > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > > Although I could specify the IP address in my SPF records directly (as > > > > you suggested), I do hope that my understanding of DNS records laid out > > > > above is not entirely misguided. My current setup does work as expected > > > > for eden.one, after all. > > > > > > As I said at < > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > > > I was misreading your DNS and now I am as puzzled as you about the > > failure. > > > > It gets even more mysterious. I tried sending messages from both > > lists.eden.one and janeden.net (my other domain) to a gmail account and > > to another mail provider. Both messages passed the SPF checks on both > > services (s. the relevant headers quoted below). Now because I send > > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > > check operates (and succeeds) on e.g. > > > > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > > (and not on somethingsomething(a)lists.eden.one or > > somethingsomething(a)janeden.net) Could this be the reason for the failed > > SPF checks in Yahoo's and Google's DMARC reports? > > > - Jan > > Might you be willing to use proven tools instead of trying so hard to > understand the myth? > > I use https://easydmarc.com/tools#spf-tools > It allows me to generate, lookup, test SPF, DKIM, DMARC, etc. I did use adequate tools to generate and test my DNS records, and this is why the DMARC reports quoted in my initial message are mysterious to me. Trying hard to solve a mystery might not be productive in every case, but I do not want to stop being curious. - Jan

2 years, 8 months

[MM3-users] Re: clean up spambot generated accounts

by Johannes Rohr

Sorry, I should have looked into the script more closely. I simply had to set the variable CFG_PATH to the correct value. Johannes Am 23.02.25 um 15:29 schrieb Johannes Rohr: > Dear all, > > I'm trying to find a way to clean up hundreds of spambot generated > accounts on my system. I was pointed to this script that should be > capable of doing the task: > > https://www.msapiro.net/scripts/clean_users.py > > However, it seems outdated. First, the path to the interpreter is not > what I find on my mailman3 installation. It says: > > #! /opt/mailman/mm/venv/bin/python > > However, the python command is located in /opt/mailman/venv/bin/python > instead, no "mm" > > After fixing this, the script still throws an error: > > (venv) mailman@ida:~$ clean_users.py > Traceback (most recent call last): > File "/usr/local/bin/clean_users.py", line 55, in <module> > django.setup() > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/__init__.py", > line 19, in setup > configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", > line 102, in __getattr__ > self._setup(name) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", > line 89, in _setup > self._wrapped = Settings(settings_module) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/conf/__init__.py", > line 217, in __init__ > mod = importlib.import_module(self.SETTINGS_MODULE) > File "/usr/lib/python3.10/importlib/__init__.py", line 126, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 1050, in _gcd_import > File "<frozen importlib._bootstrap>", line 1027, in _find_and_load > File "<frozen importlib._bootstrap>", line 1004, in > _find_and_load_unlocked > ModuleNotFoundError: No module named 'settings' > > Can somebody explain to me, why this module is not found and what I > can do to fix it, if anything? > > Thanks a lot in advance! > > Johannes > > _______________________________________________ > 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 johannes(a)rohr.org

6 months, 3 weeks

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

by Odhiambo Washington

On Sat, 25 Jul 2020 at 20:35, <joseverde(a)gmail.com> wrote: > Hi folks, I spent many hours last night trying to get Mailman 3 up and > running. I am using Ubuntu on a Digital Ocean LAMP droplet (so PHP, Apache, > Sql, and Postfix are already installed). The LAMP stack works as I have a > successful installation of YOURLS going on. > > So, I tried to use this guide ( > https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) > to install the Mailman3 package and got to the configuration screen (the > one with all the DOS-esque GUI). I ran it but it kept saying the DB wasn't > installed. Was I supposed to create SQL databases and users before running > that and use those usernames/databases in the credentials it asks for? It > doesn't seem like that in the way it asks the questions (since it asks to > create a password) but I wasn't sure. > > Anywho, I tried to remove the package completely and restart but I keep > spinning my wheels. So my questions: > > 1. Does that guide actually work? Did I just foul up the database part? > 2. Is there a better way to install mailman3 with some nice step-by-step > directions to follow? > 3. Is there a way to completely wipe my previous installs without wiping > the server? ( I didn't back up...silly I know ). I used apt-get --purge > remove to uninstall mailman3 and mailman to start over, did that do the > trick? > > Sorry for all the questions. > DISCLAIMER: I have no experience at all with MM3. I haven't even succeeded in installing it as yet because I am trying to do it manually on FreeBSD. I have an Ubuntu box that runs mailman-2.1.34 manually installed as well, but I am wondering if you tried the following: root@lists:/home/wash# apt search mailman3 Sorting... Done Full Text Search... Done mailman3/bionic 3.2.0-1~ubuntu18.04.1 all [residual-config] Mailing list management system mailman3-doc/bionic 3.2.0-1~ubuntu18.04.1 all Mailing list management system documentation mailman3-full/bionic 3.2.0-1~ubuntu18.04.1 all Full Mailman3 mailing list management suite (metapackage) mailman3-web/bionic 0+20180916-2~ubuntu18.04.1 all [residual-config] Django project integrating Mailman3 Postorius and HyperKitty python-django-hyperkitty/bionic 1.1.4-4 all Web user interface to access GNU Mailman3 archives python-django-mailman3/bionic 1.1.0-4 all Django library to help interaction with Mailman3 (Python 2 version) python-django-postorius/bionic 1.1.2-3 all Web user interface to access GNU Mailman3 python-mailmanclient/bionic 3.1.1-5 all Python bindings for Mailman3 REST API (Python 2 version) python-mailmanclient-doc/bionic 3.2.0-2~ubuntu18.04.1 all Python bindings for Mailman3 REST API (Documentation) python3-django-hyperkitty/bionic 1.2.1-3~ubuntu18.04.1 all Web user interface to access GNU Mailman3 archives python3-django-mailman3/bionic 1.2.0-2~ubuntu18.04.1 all Django library to help interaction with Mailman3 (Python 3 version) python3-django-postorius/bionic 1.2.2-2~ubuntu18.04.1 all Web user interface to access GNU Mailman3 python3-mailman-hyperkitty/bionic 1.1.0-9~ubuntu18.04.1 all [residual-config] Mailman3 plugin to archive emails with HyperKitty python3-mailmanclient/bionic 3.2.0-2~ubuntu18.04.1 all Python bindings for Mailman3 REST API (Python 3 version) root@lists:/home/wash# apt install mailman3 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: python3-aiosmtpd python3-alembic python3-dateutil python3-falcon python3-flufl.bounce python3-flufl.i18n python3-flufl.lock python3-lazr.config python3-lazr.delegates python3-mako python3-mimeparse python3-nose python3-passlib python3-psycopg2 python3-public python3-sqlalchemy python3-sqlalchemy-ext python3-zope.configuration python3-zope.i18nmessageid python3-zope.schema Suggested packages: mailman3-doc python3-editor python-flufl.bounce-doc python-flufl.i18n-doc python-flufl.lock-doc python-lazr.config-doc python-lazr.delegates-doc python3-beaker python-mako-doc python-nose-doc python-psycopg2-doc python-public-doc python-sqlalchemy-doc python3-mysqldb python3-fdb python3-zope.testing The following NEW packages will be installed: mailman3 python3-aiosmtpd python3-alembic python3-dateutil python3-falcon python3-flufl.bounce python3-flufl.i18n python3-flufl.lock python3-lazr.config python3-lazr.delegates python3-mako python3-mimeparse python3-nose python3-passlib python3-psycopg2 python3-public python3-sqlalchemy python3-sqlalchemy-ext python3-zope.configuration python3-zope.i18nmessageid python3-zope.schema 0 upgraded, 21 newly installed, 0 to remove and 2 not upgraded. Need to get 2,862 kB of archives. After this operation, 16.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Where would that end you??? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

[MM3-users] Re: Treatment of hostname in /etc/hosts [was: Splitting hosts ...]

by Abhilash Raj

On Thu, Jun 25, 2020, at 12:33 AM, Stephen J. Turnbull wrote: > Ruth Ivimey-Cook writes: > > > The localhost address is coming in via the hosts file, which is a > > relatively standard practice IMO. > > OK, so I did a little research on this. You don't need to read this > to continue discussion, but since other users have expressed interest > in splitting hostname from listener IP address, I am posting what I've > learned about aliasing hostname to localhost. This doesn't apply > directly to multihomed hosts as also mentioned in this thread, and > additions and corrections are, of course, welcome. > > It had been my understanding that conventional wisdom is that > "127.0.0.1 localhost" is *all* that you should put in /etc/hosts in > most cases, so I did a couple of web searches. As far as my search-fu > got me, there is no standard beyond putting localhost itself in there, > which is used by a lot of boot scripts. But as a matter of common > practice, the Debian family supplies an /etc/hosts that defaults to > aliasing the host's FQDN to 127.0.1.1 (not 127.0.0.1), apparently as a > kludge to keep GNOME happy: > http://www.leonardoborda.com/blog/127-0-1-1-ubuntu-debian/ > > systemd-resolvd does something different; in the case that there is no > interface configured *and* no /etc/hosts entry, it resolves the > "local, configured hostname" to 127.0.0.2 (again, not 127.0.0.1). But > if there is an interface configured, it resolves to that interface's > IP. Apparently this is intended to speed up systemd-based boot > processes by allowing them to run in parallel. Fedora issue tracker > reports it leads to a problem similar to the one being discussed, eg, > https://bugzilla.redhat.com/show_bug.cgi?id=1116538#c25 > > Bottom line: neither the Debian family nor the Red Hat family aliases > hostname to localhost; by default it's a separate "interface". And > Red Hat does it conditionally on no real interface found. > > As far as I can tell, these workarounds are about placating software > that breaks in one way or another if the host's own FQDN does not > resolve at all when they start up, presumably because the resolver > can't reach the network -- but they don't care if it's consistent with > DNS as long as it connects to the local host, which leads to a fairly > arbitrary practice of aliasing the hostname to localhost. All of > which suggests to me that such software should be special-casing the > host's various identifiers (hostname, canonical FQDN, /etc/hosts > aliases, all of which it can easily discover) and translate them to > "localhost", rather than asking the resolver to do it and creating an > inconsistency with DNS. > > Of course, getting other software to Do The Right Thing is pretty > hopeless, but the solution is simple: wait for the network to come up > and use the configured interface's address by looking up the canonical > hostname. This works for GNOME and Postfix (mentioned in the > references above), and for Mailman. > > AFAICS, the exceptions are (1) running a high-availability "cloud" > system that needs to scale very quickly on-demand (in which case you > want to start things in parallel and need to deal with the real race > conditions involved), and (2) a need to do work while disconnected. > The former is over my pay grade but apparently Fedora has not managed > to get it 100% reliable even with systemd. The latter case can be > dealt with by putting your static IP address in /etc/hosts when you > have one, which I presume Sorry to chime in pretty late on this topic, but I didn't know about the research you did above. Thanks Steve! I have had some of these issues in the past, but they were related to Mail routing from Postfix to the Mailman container. The problem was that docker would assign these DNS names to each container based on their names and magically update every container's `/etc/hsots` so they can talk to other containers through these docker given DNS names. However, the postfix running on the host won't be because docker doesn't put this DNS name anywhere else. So, if I put 0.0.0.0 for LMTP server to bind to, it would use that address to generate Postfix's transport maps and of course it won't be able to reach Core running at an IP assigned at runtime. But the way I got around the problem was by adding regex based routing for Postfix. Exim worked because all I had to do was make the directories visible on the host. About HTTP requests, I would say Core doesn't really need to know the external address that it is reachable at, only the interface it needs to bind to. In a containerized environment, the IP/FQDN could actually change, so if we are optimizing this for situations like containers/multi-host, it would require an Admin to update the configs. Instead, what I was thinking was to just ignore the host, port in the self_link in Mailmanclient. The purpose of self_link is mostly to reflect the path to the resource itself in the API and I am not sure if it requires the complete URL with scheme, host and port. That should allow Web components to reach the resources without Core knowing or caring about what address it is externally reachable at. Thoughts? > > > I could change it, but then perhaps other things would not work. > > I would prefer to be able to specify what I need. > > Notwithstanding the discussion above about why it "shouldn't" break > anything, I wouldn't be surprised if something breaks -- such > configuration choices tend to ramify. I sympathize with you not > wanting to change a configuration that works for you. > > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 2 months

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

by Ruth Ivimey-Cook

Steve, What I mean by per-user permissions is that some transitions, for example bounce-disabled to enabled, should be only possible by someone with appropriate permission to do so -- perhaps the list admin, perhaps someone else, but not just anyone. Another example _could_ be if a user disables themselves then only that user can re-enable them again (though I can see that might not be good). Of course, you can to some extent group users by role, so 'admin' role is always ok, 'list-owner' role is ok for any action on that list, etc. If you had a 'role' which was 'account-owner' then you can probably code the rule for re-enabling an account disabled by the account owner as "role = admin or role = list-owner or role = account-owner". Whether this needs to be extended to "role=admin or user = guy" (where 'guy' is a named account holder) I don't know... I suspect it would be better if that wasn't done unless it was shown to be necessary, as "here be dragons". Do you see where I'm at? In writing this up it occurs to me that being able to see/edit rules such as these, stored in per-list config, would probably be a good thing. Don't know how practical that is though. Regards, Ruth On 16/02/2021 15:29, Stephen J. Turnbull wrote: > Hi, Ruth, > > Thanks for the comments. I'll have to think about most of it, but I > have one immediate question. > > Ruth Ivimey-Cook writes: > > > > On 13/02/2021 16:34, Stephen J. Turnbull wrote: > > > > I don't think separate booleans is a good idea, since they're > > > basically mutually exclusive states[.] > > > > While using one variable makes some sense as you say, it does > > complicate the allowed state transitions especially when per-user > > permissions as well as logic are applied to the situation. > > I don't understand how "per-user permissions" apply here. > > Regards, > Steve -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 7 months

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

by Odhiambo Washington

On Wed, Dec 14, 2022 at 8:02 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > > The site is public, so I can share the link: > https://list.rc.org/archives/ > > The CSS is not working. Two possibilities to try first: > 1. (more likely) You didn't run the command that compiles the CSS. > (probably) mailman-web compress > 2. (much less likely) The CSS got replaced in the upgrade and the > ownership changed because you were working as root, and the server > process can't access the files. > 3. other possibilities: the SASS compiler (usually sassc, possibly sass) > > 1. The post-update script runs everything required. For the avoidance of doubt, here it is: <CUT> #!/bin/bash set -e BINDIR="/opt/mailman/mm/bin" CONFDIR="/opt/mailman/mm" SETTINGS="settings" DJANGO_CONTROL_SCRIPT="$BINDIR/django-admin" STATIC_DIR="$CONFDIR/static" DEBUG="False" set -x if [ "$DEBUG" == "False" ]; then mkdir -p "$STATIC_DIR" || : "$DJANGO_CONTROL_SCRIPT" collectstatic --clear --noinput --verbosity 0 "$DJANGO_CONTROL_SCRIPT" compress "$DJANGO_CONTROL_SCRIPT" compilemessages fi syncdb_cmd="$DJANGO_CONTROL_SCRIPT migrate" if [[ ! -t 1 ]]; then # stdout is not a terminal syncdb_cmd="$syncdb_cmd --noinput" fi $syncdb_cmd echo 'Do you want to rebuild the search index? This takes a long time.' echo 'Type "Yes" to continue; anything else to quit.' read -p "> " response if [ "x$response" != "xYes" ] ; then exit; fi "$DJANGO_CONTROL_SCRIPT" update_index </CUT> The script is run within the venv. 2. That isn't possible. Why? Because when I do 'su -mailman' it automatically activates the venv via a .bashrc. I have run this: find /opt/mailman -type f -name "*.css" -exec ls -al {} \; And all files are owned by mailman.mailman. 3. I have the following in settings_local.py: COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'), ) COMPRESS_OFFLINE = True COMPRESS_ENABLED = True And: root@list:/home/wash# su - mailman (venv) mailman@list:~$ which sass /usr/bin/sass (venv) mailman@list:~$ `which sass` --version Ruby Sass 3.7.4 (venv) mailman@list:~$ Anything else that might be the issue? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Single-Sign-out for List member

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > > It does not seam to be possible, to put this into effect with mailman 3. > > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. > > > You can set the list's unsubscription_policy to open and set the link as > a mailto: to the list-leave address, but that still requires a second > click to send the mail. > > The solution is to create a web based CGI script which is called with a > URL like > <https://example.com/unsub_script/list.example.com/user@example.net> and > have that script invoke the appropriate `mailman` command to remove the > member from the list. Beginning with Mailman 3.3.2, this would be If this is one-click, can't this URL be hit by anyone trying to remove the user from any MailingList without any auth or anything? > > mailman delmembers -l list.example.com -m user(a)example.net -g > > to remove the member and send a goodbye message. In older Mailman, it > would be something like > > echo user(a)example.net | mailman members -x - list.example.com > > I understand you may have a legal requirement do do this, but these > "one-click - no user confirmation" links are a bad idea because usera > will reply to a list post or forward it and not remove the link and > userb will receive usera's reply and click usera's unsubscribe link > either maliciously or thinking it will unsubscribe userb. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Two Questions: One General, the Other Specific

by Mark Sapiro

On 2/26/21 9:10 AM, David Wilson wrote: > > *Is there another site that might best communicate the future goals, > plans, objectives, and time frames for mailman3 or is the status of the > project at the state of being primarily reacting to problems, as > evidenced in this problem solving forum, at least as it seems to me, > with no offense meant or intended?* We are a small project with few volunteers and no paid staff. While we would like to be able to devote significant time to future goals, plans and objectives, often we only have time and resources to devote to fixing immediate issues. The way to get issues/objectives/etc. on our radar it to post them to the various sub-project issue trackers at <https://gitlab.com/groups/mailman>. > Something I find surprising is a problem described in an image grab > below relating to an inability to amend a list entry to include a name > to be associated with an email address, as if the data needs to be > immutable. When a workaround was unsuccessfully explored to delete the > entry and then resubmit an amended entry but with the same already > deleted email address, that was still refused, presumably because of > pointers to archived data don't permit, but this seems like a > particularly onerous restriction, or perhaps even a bug, or at least a > severe design constraint. *Is this item on an existing to do list?* There has been much discussion of this on this list. See for example the recent thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> This item is not on a ToDo list because even though <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> asked for an issue to be filed, the most interested person refused to do so because of his assessment of our priorities <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. And if you don't read the whole thread, at least see the response at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: MM3 occasionally chokes (?)

by Dmitry Makovey

thanks Abhilash for all those pointers. I'll bee following those threads to see whether I can find something there. thanks! On 3/18/19 10:14 AM, Abhilash Raj wrote: > On Mon, Mar 18, 2019, at 10:13 AM, Abhilash Raj wrote: >> On Mon, Mar 18, 2019, at 9:46 AM, Dmitry Makovey wrote: >>> Thanks for fast response Abhilash! >>> >>> See inline for responses: >>> >>> On 3/18/19 9:24 AM, Abhilash Raj wrote: >>>> On Mon, Mar 18, 2019, at 9:14 AM, Dmitry Makovey wrote: >>>>> In the last couple of month we've observed some odd behavior from MM3 >>>>> (namely the core) where it seems like email that is about to be sent to >>>>> a large-ish mailing list (10K users) has been processed yet never gets >>>>> sent out until we restart the core. >>>> >>>> This is indeed weird, I don't think 10k is too much, but it also depends >>>> on your MTA. How fast do they allow sending emails and if there is any >>>> rate limiting. >>> >>> I'm using Mailu.io for MTA. We're controlling it so there's not much >>> throttling as I've whitelisted mailman to send anything over LMTP. >> >> Mailman sends out email using SMTP and receives it from MTA using LMTP. >> >>> >>>> I wouldn't necessarily consider this a performance problem in Core, >>>> since it is still just processing only one email. All it needs to do is >>>> send them all out, which is where the problem should be. >>> >>> inferred assumption is that mailman-core loses LMTP connection with >>> Mailu stack. but then upon restart of service it regains it? >> >> Mailman acts as am SMTP client sending out emails via MTA. AFAIK, >> Mailman 3 recycles SMTP connections after certain number of emails are >> sent out. >> >> You can configure how many emails are sent-out per-connection and >> when should each connection be recycled. You can also disable the >> recycling altogether and always keep a connection open to the MTA. >> See [1] here for detailed docs. >> >> [1]: >> https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht… >> >> Again, copying from the docs, these are some extra MTA related settings >> that you may want to change: >> >> --- >> # Ceiling on the number of recipients that can be specified in a single SMTP >> # transaction. Set to 0 to submit the entire recipient list in one >> # transaction. >> max_recipients: 500 >> >> # Ceiling on the number of SMTP sessions to perform on a single socket >> # connection. Some MTAs have limits. Set this to 0 to do as many as we like >> # (i.e. your MTA has no limits). Set this to some number great than 0 and >> # Mailman will close the SMTP connection and re-open it after this number of >> # consecutive sessions. >> max_sessions_per_connection: 0 >> >> # Maximum number of simultaneous subthreads that will be used for SMTP >> # delivery. After the recipients list is chunked according to max_recipients, >> # each chunk is handed off to the SMTP server by a separate such thread. If >> # your Python interpreter was not built for threads, this feature is disabled. >> # You can explicitly disable it in all cases by setting max_delivery_threads >> # to 0. >> max_delivery_threads: 0 >> --- >> >> max_sessions_per_connection is by default set to 0, so that shouldn't be >> causing any problems. >> >> For a list of 10k members with `max_delivery_threads` set to to >> default(500), > > I meant, max_recipients set to default (500). > >> Mailman could be sequentially sending out emails in 20 (10k/500) >> connections, which >> could be causing the delay that you see. >> >> You could increase the threads or if your MTA can handle it, set the >> max_delivery_threads >> to 20 and see if that helps? >> >>> >>>> I'd imagine debug logging on outgoing runner should give some more >>>> pointers on what is going on. >>>> >>>> You can configure the smtp runner to log extra information (copied from >>>> docs)[1] >>>> >>>> [1]: >>>> https://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html >>> >>> awesome - I'll give it a go. thanks for the pointer. >>> >>>> I'd also recommend looking into MTA logs for anything un-usual. >>> >>> we briefly did , but nothing stood out. >>> >>>>> troubleshooting/digging before I just restart the core (which by the way >>>>> takes about 45min to fully start... which is another puzzle to solve at >>>> >>>> How do you measure that it takes 45 mins to start? >>> >>> normally it's "docker ps" command output along with "docker top" so once >>> I see all the sub-processes kicked off I'm assuming core is started and >>> from that point it's anywhere between 35 and 45min before I can get any >>> *response* from core (i.e. mailman-web complains, REST commands fail, etc.) >> >> Maybe we should discuss this in another thread? REST Runner (and other runners) >> shouldn't be taking this long to boot up. >> >>> >>>> What database backend are you using? >>> >>> Postgres. The whole setup is docker-setup (0.1.7 version of containers >>> at this point). >>> >>> >>> -- >>> Sr System and DevOps Engineer SoM IRT >>> >>> >>> Attachments: >>> * signature.asc >> >> -- >> thanks, >> Abhilash Raj (maxking) > -- Sr System and DevOps Engineer SoM IRT

6 years, 5 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Thank you for your help. Let me try this. Kind regards, Prasanth On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/28/21 6:02 AM, Prasanth Nair wrote: > > Hello, > > > > Does anyone know how to edit an archived email in Mailman3? It is > possible > > in Mailman2 ( > > > https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… > ). > > Is there any option similar to this in Mailman3? > > > In some sense the process is the same but possibly even simpler in > Mailman 3. You need to modify the underlying data which requires > appropriate access to the server. > > In Mailman 3, the data are in the hyperkitty_email table in Mailman's > database. You can get the Message-ID hash from the URL to the archived > message, e.g. for the message to which I'm replying, the URL is > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have > access, you can do database queries like > ``` > SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = > '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > and > ``` > UPDATE hyperkitty_email SET content = '<new content>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > UPDATE hyperkitty_email SET subject = '<new subject>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > If the message has attachments, they are in the hyperkitty_attachment > table and can be referenced by `email_id` which is the corresponding > `id` from the hyperkitty_email entry. > > You can also do similar things via `django-admin shell`. E.g. > ``` > $ django-admin shell > Python ... > (InteractiveConsole) > >>> from hyperkitty.models.email import Email > >>> x = > Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') > >>> print(x[0].content) > ``` > but this requires some knowledge of HyperKitty's models and Django's ORM. > > -- > 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, 11 months

[MM3-users] Re: Upgrade Mailmam Core from

by Odhiambo Washington

On Thu, Sep 29, 2022 at 9:18 AM <sascha.rissel(a)gmail.com> wrote: > Hi all, > > as Mark suggested, I delete the venv and started anew, making sure that I > do > > sudo su mailman > before creating the venv again. > > Executing > > pip install wheel mailman psycopg2-binary\<2.9 > led to the same error message as in my post > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > saying > > error: invalid command 'bdist_wheel' > six times, namely for: > > ERROR: Failed building wheel for mailman > > ERROR: Failed building wheel for authheaders > > ERROR: Failed building wheel for authres > > ERROR: Failed building wheel for lazr.config > > ERROR: Failed building wheel for dkimpy > > ERROR: Failed building wheel for lazr.delegates > > After this, I deleted the venv again and startet anew, again. > But this time, I explicitly did (as Stephen suggested above) > > pip install wheel > prior to > > pip install wheel mailman psycopg2-binary\<2.9 > > This time, it ran through without errors, although "wheel" is also > contained in the latter command. > Can you explain that? > > Second question: > There is still no directory "/etc/mailman3" created, where I can create > mailman.cfg in. > Does this maybe result from the fact that in first instance, I tried to > install mailman3-full via "apt-get install" and removed it again via > "apt-get remove"; with manually deleting /etc/mailman3 afterwards. > > Shall I create /etc/mailman3 manually and adding "mailman" system user > permissions? > > In advance, thanks again for your help Can you possibly blow away everything and start afresh again - using the following howto - https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ? And IF you get stuck, feel free to ping me even offlist. PS: I don't use Postfix and Nginx so I will not be able to assist you with those two. However, I will do my best to hand-hold you on the rest, as has been done to me on this list too. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: New Mailman Releases

by Odhiambo Washington

On Wed, Oct 26, 2022 at 8:44 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi, > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.6 [1] > 2. Postorius 1.3.7 [2] > 3. Hyperkitty 1.3.6 [3] > 4. Mailmanclient 3.3.4 [4] > 5. Django-mailman3 1.3.8 [5] > > All the releases are published to PyPI and you can find links to all the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of changelogs are available below: > > [1]: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 > -- Something weird is going on with the page missing the bullets. > [3]: > > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 > [4]: > > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > > Finally, the minimum Python version required is 3.7 although, 3.9 is > recommended if you are doing a new install for longest support. 3.10 is > supported for Django apps, but Mailman Core is missing that due to one > of the core dependencies not support 3.10 yet (aiosmtpd). > Hello @Abhilash Raj <maxking(a)asynchronous.in> Thank you and the whole MM3 team for all the free work you do to make us have mailing lists :) I have a question regarding the Python version. I have a very recent installation of MM3, via the Virtual Environment method, running smoothly - so far. The Python version that got installed is 3.10.6 wash@lists:~$ sudo su - mailman (venv) mailman@lists:~$ which python /opt/mailman/mm/venv/bin/python (venv) mailman@lists:~$ /opt/mailman/mm/venv/bin/python -V Python 3.10.6 (venv) mailman@lists:~$ mailma mailmail3 mailman (venv) mailman@lists:~$ mailman --version GNU Mailman 3.3.5 (Tom Sawyer) (venv) mailman@lists:~$ 1. What does the incompatibility with Python-3.10 portend for my setup and anyone else with Python-3.10? 2. Is it possible to downgrade the Python in a Venv down to 3.9 without breaking the installation? And finally, is there documentation/procedure to upgrade a VENV install in this case? Thank you in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: signup / registration error - permissions and cert chains

by David Newman

On Dec 31, 2021, at 03:43, Victoriano Giralt <victoriano(a)uma.es> wrote: > > El viernes, 31 de diciembre de 2021 1:48:38 (CET) David Newman escribió: >> I'd like for regular (non-admin) list subscribers to be able to manage >> their subscription preferences and view list archives. > > That's a good way to go :-) > > My response is more of a (very) old sysadmin and Django user (since 2008) > hunch that a proper one based on code and documentation review, but I've been > trying to contribute several times and always (super) Mark Sapiro beats me :-) > >> If I'm reading the error correctly, this is related to an inability to >> verify the cert chain. The /etc/mailman3/settings.py file points to the >> same cert and key files used by Nginx, Postfix, and Dovecot. > > You are right in your diagnose but not in your interpretation (see my comment > below inside the traceback). It is certificate related, but not for server > TLS, but for CLIENT authentication. > > >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >> EMAIL_HOST = 'localhost' >> EMAIL_PORT = 25 >> EMAIL_HOST_USER = 'dnewman(a)networktest.com' >> EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' >> EMAIL_USE_TLS = 'True' >> EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' >> EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' > > All these settings above are used for SENDING messages and, if I'm not > mistaken, the SSL key and cert are used for authenticating the user sending > the email. Actually, using TLS and SMTP Auth for localhost is a bit too much. > I've been configuring SMTP servers since 1990 and my mail servers just accept > mail form localhost, if they are broken into, the user and password have > already been exposed :-) > >> But this might only be for email, not Postorius/Django. > > You are right (if I also am) > >> What additional configuration is needed to allow regular users to create >> and manage their own accounts? > > I'd say that is more what is not needed (the SMTP TLS authentication) > > I'll remove the "noise". These are the tell tale lines: > >> "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smt >> p.py", line 67, in open >> self.connection.starttls(keyfile=self.ssl_keyfile, >> certfile=self.ssl_certfile) > > The SMTP Django backend is trying to connect to the mail server to send the > Mailman account confirmation message and failing, probably because the user > Django runs as cannot open the private key (which is a very sensible thing if > that private key is the one used for the web facing TLS certificate, I can > tell you how bad in private or search for my name, wasd, apache and VMS ;-)) > > That certificate is not needed for sending email from Django, and, as I said, > not even SMTP Auth for sending via localhost. Actually, doing SMTP Auth on > port 25 is not even recommended practice. Hi Victoriano, Thanks for this. I could use some clarification on what specific changes you are suggesting. I *think* you are saying to remove the EMAIL_USE_TLS stuff and also move to another port (maybe 587), but I am not sure. Also, the reason I added the TLS in the first place was that I was getting errors without it. And I am unclear why the cert / private key pair do not work for Django when they do work OK for Postfix, Nginx, and Dovecot. Thanks for clarifying — and happy and safe 2022 to you as well! dn > > Happy, healthy, safe and well ventilated New Year to all. > > -- > 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 ? > > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 8 months

[MM3-users] Re: Configure MM3 with separate IMAP Mailserver

by Mark Sapiro

On 1/2/23 11:18, Clemens Leider wrote: > Hi Mark, much appreciated! This is for sending messages, right? How about the recieving part…I read different things around that i need multiple mailboxes created, postfix installed, relays, ASMTPDirect etc…can you guide me a bit here, please? I havent found that one instruction that would solve this for me until now. Would just like to avoid to have to administer my own mailserver locally, if i have a perfectly configured one with my provider. CL Yes, what I posted is for outgoing mail from Mailman. Incoming mail is much more difficult. There are threads on this in the archives of this list. E.g., <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> The incoming MTA needs to relay the mail to Mailman's LMTP server for every address - that's 9 addresses per list. An example postfix transport_maps for one list is: ``` list(a)example.com lmtp:[127.0.0.1]:8024 list-bounces(a)example.com lmtp:[127.0.0.1]:8024 list-confirm(a)example.com lmtp:[127.0.0.1]:8024 list-join(a)example.com lmtp:[127.0.0.1]:8024 list-leave(a)example.com lmtp:[127.0.0.1]:8024 list-owner(a)example.com lmtp:[127.0.0.1]:8024 list-request(a)example.com lmtp:[127.0.0.1]:8024 list-subscribe(a)example.com lmtp:[127.0.0.1]:8024 list-unsubscribe(a)example.com lmtp:[127.0.0.1]:8024 ``` This relays mail to those addresses to Mailman's LMTP server listening on the localhost, port 8024. If you could arrange for the external IMAP server to do that, that would work, but I suspect you don't have access to even try. For MM 2.1 which is different in that it doesn't use LMTP in this way, some people have used fetchmail <https://www.fetchmail.info/> to do things like this. This requires setting up mailboxes on the remote server to receive the mail and using fetchmail to retrieve that mail and relay it to Mailman. The issues with this are keeping the remote mailboxes and fetchmail in sync with Mailman as lists are created and removed. Another possibility is to have all your lists in a dedicated domain and configure the remote MTA to forward all mail to that domain to the Mailman host and then configure an MTA on the Mailman host to simply relay all mail to Mailman via LMTP. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

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

by Mark Sapiro

On 11/21/23 04:32, Odhiambo Washington wrote: > > I tested the above out of curiosity. It failed. There are 9 lists in the > setup, but I am only interested in 1. > > ``` > (venv) mailman@debian12:~$ mailman-web shell > Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] > Type 'copyright', 'credits' or 'license' for more information > IPython 8.17.2 -- An enhanced Interactive Python. Type '?' for help. > > In [1]: from hyperkitty.lib.compat import get_list_by_name > > In [2]: mlist = get_list_by_name('list_name_only', 'list_domain') You can't use literally ('list_name_only', 'list_domain'). If the list of interest is for example alist(a)example.com, the above should be mlist = get_list_by_name('alist', 'example.com') ... > Was I supposed to substitute something for the real listname of the list I > wanted? Yes. > Another thing - totally unrelated - that surprised me: > While using the commented-out block below, I could not click and get > anything beyond http://http://list.name/mailman3 as anything to do with > /postorius/xxxxx gave "Page not found" error. > However, with the second config block that uses the UNIX socket, I am able > to access everything > > ``` > #<IfModule mod_proxy.c> > # ProxyPreserveHost On > # ProxyPass "/mailman3" "http://127.0.0.1:8010/mailman3" > # ProxyPass "/archives" "http://127.0.0.1:8010/archives" > # ProxyPass "/accounts" "http://127.0.0.1:8010/accounts" > # ProxyPass "/admin" "http://127.0.0.1:8010/admin" > # ProxyPass "/user-profile" "http://127.0.0.1:8010/user-profile" > # </IfModule> > > ProxyPassMatch ^/static/ ! > ProxyPassMatch ^/favicon.ico ! > ProxyPass / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ > ProxyPassReverse / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/ > ``` > > Why is it that the UNIX socket option worked flawlessly while the other > option failed??? The first option does not have ProxyPass for urls matching /postorius or /hyperkitty so such urls don't work. The second option passes everything (ProxyPass / ) to uwsgi via the socket so all urls that uwsgi can handle will work. You could do something similar with the first option with simply ProxyPass "/" "http://127.0.0.1:8010/" assuming uwsgi is listening on port 8010. -- 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: HyperKitty: discussions not updating, misreporting stats

by Abhilash Raj

On Sun, Nov 12, 2017, at 04:24 PM, Cameron Smith wrote: > These are a couple of HyperKitty issues that I have talked about in > August [1]. I’ve been doing a bit more experimentation in the last few > days and am reporting my findings. > > The two issues are: > > — Missing messages: HyperKitty doesn’t show all of the messages in a discussion > - Misreporting of discussion statistics: HyperKitty doesn’t update the number of participants and comments in a discussion > > > I’m using the latest Docker setup. > > Neither of these issues are solved by updating or rebuilding indexes: > > sudo docker exec mailman-web ./manage.py update_index > sudo docker exec mailman-web ./manage.py rebuild_index > > > However, if I stop and then restart the containers (sudo docker-compose > down; sudo docker-compose up -d), the discussion statistics are updated > and properly display the number of participants and comments in all > discussions. This does not, however, solve the problem of missing > messages. This sounds like there is something wrong with how django_q tasks are run inside container images. Either sum bug in uwsgi, or some configuration error. I do remember Mark having an issue on lists.mailman3.org with django_q tasks not running properly, I wonder if it is the same issue here? I have created an issue[1] to track. [1]: https://github.com/maxking/docker-mailman/issues/196 > > > I have discovered two methods of displaying the missing discussion > messages: > > add a new message to the thread in HyperKitty; I’m not convinced that this works *every* time, but it at least works *most* times > > run the yearly cron job; this seems to work *every* time: > > sudo docker exec mailman-web ./manage.py runjobs yearly I am not sure I have seen this before, but it is possible other MM3 admins might have. Hyperkitty itself doesn't have any yearly jobs though, maybe some dependency does. > > > [1]: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > Cameron Smith > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 10 months

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

by Mark Sapiro

On 6/20/20 1:37 PM, Ruth Ivimey-Cook wrote: > Thanks Mark, Ignore bracketed numbers below ([1], [2], etc.) They come from conversion of the HTML only post to plain text. > On 20/06/2020 03:53, Mark Sapiro wrote: > > What are your Django settings for MAILMAN_REST_API_URL, > MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with > the [webservice] settings for hostname, port, use_https, admin_user and > admin_pass in mailman.cfg in core and is the port open to the outside on > the core machine? > > greyarea-post is the mailman-core and exim server. > > greyarea-web1 is the postorius and hyperkitty server. > > On greyarea-web1, in django-settings.py, > > MAILMAN_REST_API_URL = '[1]http://greyarea-post:8870' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = XXXX > > and both the above-named hosts are also included in ALLOWED_HOSTS along > with localhost. > > On greyarea-post, in mailman.cfg: > > [webservice] > admin_pass: XXXXX > admin_user: restadmin > api_version: 3.1 > hostname: 0.0.0.0 > port: 8870 > use_https: no > > The password and username are as on web1. That all looks good. > Do you see REST requests from the Postorius machine in core's > mailman.log and access.log? > > Yes, there are lots of requests of the form: > > [07/Jun/2020:15:00:01 +0000] "GET /3.1/lists?count=10&page=1 > HTTP/1.1" 200 470 "-" "GNU Mailman REST client v3.3.1" > > I made a new list using the core CLI, and as a result of navigating > directly to the list archive page I get to see: > > [06/Jun/2020:23:00:02 +0000] "GET /3.1/lists/chbcdaily(a)ch-bc.org.uk > HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.1" > > ... but in neither case do I get a complete screen on the browser or > 'follow-up' requests. > > I don't have a file access.log on the greyarea-post. Yes, that's actually a gunicorn log so would only be on greyarea-web1, but the mailman.log tells us the requests are getting to the core REST API, so we don't need that info. > On the greyarea-web1 I have mailmansuite.log with the last few lines: > > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/ba > se.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/co > nnection.py", line 124, in call > 'Could not connect to Mailman API: ', repr(e)) > mailmanclient.restbase.connection.MailmanConnectionError: ('Could > not connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > ERROR 2020-06-03 01:02:06,115 29002 django.request Service > Unavailable: /postorius/lists/ OK. This is telling us that mailmanclient (the REST API Python bindings that Postorius uses to access core) is having trouble establishing a connestion to the core REST server, but it clearly gets there some of the time based on the mailman.log entries. > the uwsgi-error_*.log contains many lines of the form: > > api: url is > [2]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > api: url is > [3]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > > My reason for thinking, in my original post, that the wrong host > address is being used is that the ConnectionError above contains > 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as > the listen address on the core web service and does not appear in the > config for postorius. The ConnectionError above comes from requests.request (docs at <https://requests.readthedocs.io/en/master/>). Client only provides a URL in the call to request and the URL is the baseurl + the path and the baseurl is MAILMAN_REST_API_URL which you have as http://greyarea-post:8870. Entries above have http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? I suspect a DNS lookup issue. How does greyarea-web1 resolve greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS rather than relying on /etc/resolv.conf and/or /etc/hosts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: reset bounce-scores?

by Mark Sapiro

On 10/3/24 01:15, IEM Network Operation Center (IOhannes m zmölnig) wrote: > i'm running a mailman-3.3.8 instance, and would like to reset the > bounce-score for a (number of) user(s). > i searched the internet and this list's archives, but haven't found > anything useful so far. > > due to a misconfiguration of our universities reverse DNS lookup, the > bounce score of some users has rocketed in the last days - some users > have already been unsubscribed because of that. > > could anybody please share how i can reset the bounce score? First of all, there are 3 categories of affected list members - those who are already unsubscribed, those who are still members but have delivery disabled by bounce, and those with delivery enabled but with bounce score > 0. For those that have been unsubscribed, you just have to re-subscribe them. For those that have delivery enabled but a non-zero bounce score, you may not need to do anything because they are presumably not currently bouncing so eventually the old bounce info will become stale and be ignored, but to guard against spurious bounces that may result in disabling, e.g.from an over aggressive user's spam filter, you can add `verp_probes: yes` to the `[mta]` section of mailman.cfg. The effect of this is when a members bounce score reaches threshold the score is reset and a special probe message is sent and delivery is disabled only if the probe bounces. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… That leaves those with delivery disabled by bounce. Assuming you want to enable delivery for all members of all lists with delivery disabled by bounce, the following `mailman shell` interaction will do it. ``` $ 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): ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... >>> commit() >>> ``` Watch out for a possible wrapped line above. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

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

by Stephen J. Turnbull

Kimmo L writes: > Here is the list of processes. That's an unfamiliar format to me. Is this a Linux system running systemd? > Not sure yet, which stores the most memory in the cache. For > example at the moment i have 6GB ram - 250mb free and 3gb cached. "Cache" in the context of Linux kernel operation normally means "data file contents we keep around for possible future use, but if you need memory we will evict some stuff and give you some memory". It's not memory committed to running processes. So a couple hundred MB of memory with lots of cache is to be expected after a Linux system has been running for a while. So if you have 6GB RAM and 3GB cached, that's consistent with a machine that's running Mailman, using about 2.5 GB of RAM and not much else is running except the kernel. This report does not indicate a machine on the edge of OOM-killing processes, and it's quite consistent with Mark's experience that the whole Mailman suite runs comfortably in 4 GB. How much swap do you have, and how much is in use? What other daemons are running on the host besides Mailman? I guess you must have an MTA (Postfix, Exim) running and filtering software, as well as a front-end webserver (you shouldn't be running gnuicorn directly on the web). Systemd, dbus, I guess. How much memory are they using? Have you modified any web pages associated with Mailman, including any of the Django templates? Are there any pages with unusually long load times? I checked, and neither of the errors that you report for the uwsgi configuration ("OSError: write error" and "django.request Internal Server Error") seems to be related to a memory problem, but rather to difficulties serving certain resources, typically non-existent ones, or a user leaning on the "refresh" function in their browser. (Information from checking a few StackOverflow articles.) By the way, Mark is going to be mostly unavailable for about 4 weeks. I'll do what I can to help, but Mark is probably a lot more expert on this than I am, so bear with me. Steve

3 years, 1 month

[MM3-users] Re: Issues sending to gmail and yahoo e-mails

by Thomas Ward

I misspoke on DKIM records. They're DNS records for specifying the public key, but they're cryptographic keys used to sign and verify message integrity, and they do require more work than SPF. Note *also* that for Google mail recipients, and you are sending from your own systems, you need to make sure the **Forward DNS, the Reverse DNS, and the hostname your mail server identifies as** should match, otherwise Google may flag your mail server as misconfigured and reject even with SPF and DKIM records set up. Thomas On 2025-09-09 21:03, Thomas Ward via Mailman-users wrote: > SPF is a DNS record, as are DKIM records, there's numerous guides out > there to create/configure both. It'll partly depend on your mail > system and how it routes mail through what MTA, etc. > > I am not affiliated with any of these blogs: > > "How to Set Up an SPF Record in 5 Simple Steps" - > https://www.validity.com/blog/how-to-build-your-spf-record-in-5-simple-step… > > Cloudflare has a nice explanation of DKIM records - > https://www.cloudflare.com/learning/dns/dns-records/dns-dkim-record/ > > These instructions should still work for doing the DKIM setup on a > Postfix mailer - > https://easydmarc.com/blog/how-to-configure-dkim-opendkim-with-postfix/ > > > If you use a third party sender and not an on-prem Postfix or such > then the configuration gets more difficult, complex, or custom. > > > Thomas > > On 2025-09-09 20:56, jkoral(a)luc.edu wrote: >> Thank you for the reply. Are there a good set of instructions for >> setting up SPF and DKIM? >> _______________________________________________ >> 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 toteward(a)thomas-ward.net > _______________________________________________ > 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 teward(a)thomas-ward.net

1 week, 1 day

[MM3-users] Re: Archives visible to all

by worik

tl;dr location ~ ^/hyperkitty { # Turn off archiving for Mailman3 allow 1.2.3.4; deny all; } There should be a better way (https://gitlab.com/mailman/hyperkitty/issues/219) Problem fixed, but at he cost of no archives and a broken "archives" link. On 22/02/19 9:03 PM, Johannes Winter wrote: > Am Thu, 21 Feb 2019 12:23:41 +1300 > schrieb worik <root(a)worik.org>: > >> When I load my new mailing list system, before I log in, I can see the >> archives of all the lists. Without logging in. Even lists with >> archives set to private archives. >> >> What can I do about that? > Are you sure that you really can see the list contents? In my case only > the listnames are shown, which is not nice, but bearable. Yes, that is true. Since I made my first post on this thread (which was a bit premature) I have researched this further. All messages posted before the archives are made private are displayed for all to ee, and I can find no ay of changing that except by making hyperkitty a dead link, as above. Displaying all lists on the server is unacceptable for my users. My users are involved in political activism and displaying the names of all the lists is a political risk. (As distinct from privacy or security risks). > > There is an open issue about that: > https://gitlab.com/mailman/hyperkitty/issues/197 > > Would be happy for workaround ideas, too. Yes. It has been open for half a year, https://gitlab.com/mailman/hyperkitty/issues/129 for a year. The problem is that Hyperkitty does not "...use the list's |advertised| setting to show or hide it...". IMO this is also a bug in Mailman core. Clearly Archivers need to respect changes in the statius of a list and change the status of archives already collected (not a trivial matter) but Mailman should not hand over the names of lists where archives are turned off. As I write I realise I have not tested creating a list with archives off from the get go... Worik > > > Johannes Winter > -- 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, 6 months

[MM3-users] Re: Error: ConnectionRefusedError at /accounts/login/

by Stephen J. Turnbull

Kim Sunggun via Mailman-users writes: > Have you set any of those to other than default in your Django > settings? > everything is default. What we're doing is not relevant because we're not trying to connect to your MTA. Some of us do because our MTAs expect authentication or are running on a different port for some reason. Many of us don't because our MTAs use the defaults too, at least for local connections. The question *you* need to figure out is why won't your MTA talk to Django *at all*? Any number of reasons, in approximate order of when they arise in the connection process: 0. You can't get there from here because of a firewall (very unlikely on localhost). 1. The MTA isn't listening on that port at that address. The port might work at a different address, another port might work at that address, or maybe both are different. As Mark recommended, check the Mailman configuration at [mta]. If it says anything about smtp_host or smtp_port, use those in your Django configuration too. If it doesn't, they default to 127.0.0.1:25 or localhost:25, and the Django defaults should be OK. 2. The MTA is listening for IPv6 (eg, [::1]). If you specify "localhost", maybe it automatically tries IPv6, but maybe it doesn't. If Django is assuming 127.0.0.1, it won't try [::1]. 3. The MTA expects mandatory TLS (usually port = 465). 4. The MTA expects negotiated TLS (STARTTLS), mostly on port 589 but some sites require it on port 25. 5. The MTA expects authentication in TLS initialization (don't ask me, I've never set this up). I don't recall whether generic SASL applies here, although I know you can use X.509 certificates. (SASL is the authentication protocol that most MTAs use *after* the connection is established, but you aren't getting that far.) I wouldn't be surprised if there are other possible issues, but that's enough for now. ;-) Your MTA logs should show that there was a connection attempt at the right time from the right host (probably localhost), and give the point at which the connection failed and maybe a reason why. If there's nothing at all in the MTA log, the problem is #1 above.

6 months, 3 weeks

[MM3-users] MM3 Docker

by Odhiambo Washington

[Requesting everyone to be patient with me because I am not so good with Linux, Docker is a completely new thing to me, and MM3, well....] So, I have a VM running Ubuntu-18.04. It is in a Data Centre somewhere. It has an IP n.n.n.n (a public IP). Also, it does not have high resources. However, I hope I can at least get to install MM3 and test it using https://asynchronous.in/docker-mailman/ If I could run MM3 using the apt-get install method, perhaps that would have made my life a bit easier, hoping that MM3 can actually be run in parallel with MM2.1 on the same host. Is anyone doing that already?? Anyway, I need some hand-holding using the docker method for now. I am reading the steps as documented on the https://asynchronous.in/docker-mailman/ and somethings aren't clear to me: I have created two files: (a) /opt/mailman/web/settings_local.py: SERVE_FROM_DOMAIN: 'mm3.my.co.ke' ALLOWED_HOSTS: 'my.co.ke' HYPERKITTY_API_KEY: 'Whatever' MAILMAN_ADMIN_USER: 'admin' MAILMAN_ADMIN_EMAIL: 'odhiambo(a)gmail.com' SECRET_KEY: 'Whatever' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '172.19.199.1' EMAIL_PORT = 25 (b) /opt/mailman/core/mailman-extra.cfg HYPERKITTY_API_KEY: 'Whatever' DATABASE_URL: 'mysql+pymysql://mailman:mailmanpass@database/mailmandb' DATABASE_TYPE: 'mysql' DATABASE_CLASS: 'mailman.database.mysql.MySQLDatabase' Questions: Are the formats correct? Do I use quotes or not? My docker-compuse.yaml: version: '2' services: mailman-core: image: maxking/mailman-core:latest container_name: mailman-core hostname: mailman-core volumes: - /opt/mailman/core:/opt/mailman/ links: - database:database depends_on: - database environment: - DATABASE_URL=mysql+pymysql://mailman:mailmanpass@database/mailmandb - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase - HYPERKITTY_API_KEY=someapikey networks: mailman: ipv4_address: 172.19.199.2 mailman-web: image: maxking/mailman-web:latest 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: - DATABASE_URL=mysql://mailman:mailmanpass@database/mailmandb - DATABASE_TYPE=mysql - HYPERKITTY_API_KEY=someapikey - SECRET_KEY=thisisaverysecretkey - DYLD_LIBRARY_PATH=/usr/local/mysql/lib/ networks: mailman: ipv4_address: 172.19.199.3 database: environment: MYSQL_DATABASE: mailmandb MYSQL_USER: mailman MYSQL_PASSWORD: mailmanpass MYSQL_RANDOM_ROOT_PASSWORD: "yes" restart: always image: mariadb:10.3 volumes: - /opt/mailman/database:/var/lib/mysql After all that, I have run the following: wash@lists:~/docker-mailman$ docker-compose up -d Creating network "docker-mailman_mailman" with driver "bridge" Creating docker-mailman_database_1 ... done Creating mailman-core ... done Recreating 4b7bc1ecef65_mailman-web ... done Question - Should I assume everything is okay and proceed to the next steps? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 8 months

[MM3-users] Re: Archive search failing on one list

by Mark

On Sat, 2023-09-23 at 20:28 -0700, Mark Sapiro wrote: > > What if you do something like the following where django-admin is > whatever command you use for the Django admin command. > ``` > $ django-admin shell > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more > information. > (InteractiveConsole) > >>> from hyperkitty.models.mailinglist import MailingList > >>> mlist_name = 'listname(a)domain.com' > >>> mlist = MailingList.objects.get(name=mlist_name) > >>> mlist > <MailingList listname(a)domain.com (listname.domain.com)> > >>> > ``` Hi Mark, I'm still on this problem of one list's archive-search not returning any results. I created a new list today and it also has the same problem. In short, the older lists all seem fine -- their search results are up- to-date so that tells me the cron is okay. It's just these 2 newer lists that have the problem. It's taken me while to get my head around the Django admin command you have suggested, as I kept getting an error when starting: #django-admin shell >>> from hyperkitty.models.mailinglist import MailingList ... django.core.exceptions.ImproperlyConfigured ... That sent me down a rabbit hole which I haven't emerged from yet. But instead, starting with # python3 manage.py shell ... # python3 manage.py shell Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models.mailinglist import MailingList >>> mlist_name = 'thepost(a)example.com' >>> mlist = MailingList.objects.get(name=mlist_name) >>> mlist <MailingList: <MailingList thepost(a)example.com>> >>> The format of my final line is different to yours ... Mine: <MailingList: <MailingList thepost(a)example.com>> Yours: <MailingList listname(a)domain.com (listname.domain.com)> Does this (missing list_id) give any clue as to why the archive-search isn't working, or is just that starting with "# python3 manage.py shell" is the wrong thing to do? By the way, the list_id shows correctly in the SQL query result. select * from hyperkitty_mailinglist where name like 'thepost(a)example.com'; ... name | thepost(a)example.com | list_id | thepost.example.com ... Any ideas appreciated. Mark

1 year, 11 months

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

by eboltz＠lhtservices.com

Mark, Thanks for the assistance thus far. When I create a new Domain within Postorius. If I set the Mail Host to 'example.com' and the Alias Domain to 'lists.example.com', create a new list such as 'staff_test', it'll default to the 'example.com' domain (which is the real domain). Then when I subscribe, I'll get an email from 'staff_test(a)example.com', when I want it to be from 'staff_test(a)lists.example.com' instead, also if I reply back to the 'staff_test(a)example.com' then I"ll get a bounce-back that it doesn't exist, but if I send to 'staff_test(a)lists.example.com' it'll go to the newly created list. I'd like all defaults to be '@lists.example.com', if that makes sense. Here are the settings of my postfix_lmtp and postfix_vmap # AUTOMATICALLY GENERATED BY MAILMAN ON 2023-12-17 20:05:34 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Aliases which are visible only in the @lists.example.com domain. staff_test(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-bounces(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-confirm(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-join(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-leave(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-owner(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-request(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-subscribe(a)lists.example.com lmtp:[127.0.0.1]:8024 staff_test-unsubscribe(a)lists.example.com lmtp:[127.0.0.1]:8024 # AUTOMATICALLY GENERATED BY MAILMAN ON 2023-12-17 20:05:34 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Virtual mappings for the @example.com domain. staff_test(a)example.com staff_test(a)lists.example.com staff_test-bounces(a)example.com staff_test-bounces(a)lists.example.com staff_test-confirm(a)example.com staff_test-confirm(a)lists.example.com staff_test-join(a)example.com staff_test-join(a)lists.example.com staff_test-leave(a)example.com staff_test-leave(a)lists.example.com staff_test-owner(a)example.com staff_test-owner(a)lists.example.com staff_test-request(a)example.com staff_test-request(a)lists.example.com staff_test-subscribe(a)example.com staff_test-subscribe(a)lists.example.com staff_test-unsubscribe(a)example.com staff_test-unsubscribe(a)lists.example.com

1 year, 9 months

[MM3-users] Re: Single-Sign-out for List member

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > > It does not seam to be possible, to put this into effect with mailman 3. > > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. > > > You can set the list's unsubscription_policy to open and set the link as > a mailto: to the list-leave address, but that still requires a second > click to send the mail. > > The solution is to create a web based CGI script which is called with a > URL like > <https://example.com/unsub_script/list.example.com/user@example.net> and > have that script invoke the appropriate `mailman` command to remove the > member from the list. Beginning with Mailman 3.3.2, this would be > > mailman delmembers -l list.example.com -m user(a)example.net -g > > to remove the member and send a goodbye message. In older Mailman, it > would be something like > > echo user(a)example.net | mailman members -x - list.example.com > > I understand you may have a legal requirement do do this, but these > "one-click - no user confirmation" links are a bad idea because usera > will reply to a list post or forward it and not remove the link and > userb will receive usera's reply and click usera's unsubscribe link > either maliciously or thinking it will unsubscribe userb. There is also the issue that these days some Mail clients will try to create a preview of all the URLs if they can and it would inadvertently GET the URL resulting in the un-subscription. > > -- > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: Caching problem with templates

by Mark Sapiro

On 6/26/25 15:12, Mark wrote: > > On 2025-06-26 16:10, Mark Sapiro wrote: > >> What does the database query >> ``` >> SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND >> context = '<IDENTIFIER>'; >> ``` >> return? > > ================================= > > The result of the query is: > +--- > uri > +---- > http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer > +---- > > I should have also said, if I delete the template, emails still use the > old footer -- not the Mailman default as I would have expected. As long as there is an entry in the template table with a uri which is not a `mailman://` scheme, that entry is cached in the file_cache table in the database with a key = the uri and a lifetime set by cache_life in the [mailman] section of mailman.cfg - default 7 days. You can delete the cached entry from the database via `mailman shell as in ``` $ 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. >>> cm = getUtility(ICacheManager) >>> uri = 'the_uri_from_the_template_table' >>> cm.get(uri, expunge=True) >>> commit() ``` You can also delete the entry from the file_cache table, but if you do that, the actual file containing the cached data will remain. To remove it, note that the file_cache table entry has a file_id. This will be a hex digest of the sha256 hash of the uri, something like `c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e` and the file is stored in the cache/ directory in Mailman's var/ directory with a path of `file_id[0:2]/file_id[2:4]/file_id`. I.e. for the above example file_id, the file will be `var/cache/c8/52/c85210810f8824cf9227c1689817e1d081046ff132bf8abe56a7c08a89016e4e`. If you remove the entry from the file_cache table without removing the file, the file will remain forever but will be overwritten if the same uri is cached again. Rather than doing any of the above, if you want to manipulate the database, just set the expires_on column in the file_cache table entry to a date in the past. -- 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: Database running VERY hot

by Darren Smith

Abhilash, Thanks for the response. I'm going over to lists.fedoraproject.org to see if they have done any fine tuning. Our installation is at https://lists.rootsweb.ancestry.com, if you're interested in seeing an installation with over 32,000 mailing lists. As I mentioned, it was big enough that we have disabled the browse experience in Postorius and are hosting our own pages for browsing to a new list. If we get time to work on this we will certainly create a pull request. :) On Thu, Mar 8, 2018 at 11:49 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hi Darren, > > > On 3/8/18 9:43 AM, Darren Smith wrote: > >> 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. >> > > I can say that in general, Postorius doesn't really optimize REST API > queries and so loading a single page can sometimes make things bad. > > Currently, the largest installation of Mailman 3 that we know of runs at > lists.fedoraproejct.org and the administrators of the list would know how > well does our Web UI scale. > > However, I don't think we have anyone actively working on trying to fix > this particular issue. Pull Requests and fixes are welcome :) > > >> 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? >> > > There isn't any configuration that would change how databases are used in > Mailman Core. Django *may* have some, but I don't know about any of them of > the top of my head. > > thanks, > Abhilash >

7 years, 6 months

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

by Abhilash Raj

Sorry for the top post! You don't have to do the export import thing, you just need to delete the index for fulltext search, which is typically in a directory alongside your settings.py called "fulltext_index" ( not 100% on the name of directory). After that you need to build your index (python manag.py rebuild_index) for the search to work. thanks, Abhilash On Sun, Sep 30, 2018, at 11:42 PM, Thomas G wrote: > Hi, > > I would like to migrate my current Mailman3.1/Hyperkitty data to a fresh > install in Mailman3.2. > > I didn't found how migrate the archives. > From : HyperKitty - Version: 1.1.1 - Python2.7 > To : HyperKitty - Version: 1.2.1 - Python3.5 > > I exported a mbox from hyperkitty (web interface) and tried to re-import > it, without result. > """""""""""""""""""""""""""""""""""""""" > xxxx @xxxxxx :/opt/mailman# python3.5 manage.py hyperkitty_import -l > listedetests(a)hatlab.fr /home/admin/listedetests(a)hatlab.fr.mbox.gz > > Importing from mbox file /home/admin/listedetests(a)hatlab.fr.mbox.gz to > listedetests(a)hatlab.fr > Computing thread structure > Synchronizing properties with Mailman > Warming up cache > The full-text search index is not updated for this list. It will not be > updated by the 'minutely' incremental update job. To update the index > for this list, run the 'manage.py update_index_one_list > listedetests(a)hatlab.fr' command. > """""""""""""""""""""""""""""""""""""" > The database stay empty (and web interface): > """""""""""""""""""""""""""""""""""""" > mailmandbnameprod=# select * from hyperkitty_email; > id | message_id | message_id_hash | subject | content | date | timezone > | in_reply_to | archived_date | thread_depth | thread_order | > mailinglist_id | parent_id | sender_id | thread_id | sender_name > ----+------------+-----------------+---------+---------+------ > +----------+-------------+---------------+--------------+-------------- > +----------------+-----------+-----------+-----------+------------- > (0 rows) > """""""""""""""""""""""""""""""""""""" > > Any idea to do this importation ? > > 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, 11 months

[MM3-users] Re: Trouble Installing Mailman3

by Mark Sapiro

On 6/12/25 12:44, Henry Hartley via Mailman-users wrote: > > Here's what I mean when I say I'm doing this "in venv" > > I've become the mailman user: sudo su - mailman > The .bashrc for that user includes: source /opt/mailman/venv/bin/activate > The prompt has (venv) at the left end of it: (venv) mailman@wz-prd-tpmd-1:~$ So your venv is active. That is good. > All pip commands have been run in this state. I did first install setuptools with apt install python3-setuptools and that installed version 68.1.2-2ubuntu1.2. Which installed it in some /usr/<maybe local here>/lib/pythonxx/dist-packages or maybe site-packages directory which is probably not goint to be consulted by the python in your venv. > Note that I'm still not sure the firewall is completely out of the picture, since I do have to include the --trusted-host and --proxy options. Some things install, though, so I think that's OK. > > When I do this at the (venv) prompt, asking to install both setuptools and mailman-web: > > pip install --proxy http://webproxyta.westat.com:3128 --trusted-host pypi.org setuptools mailman-web > > The first line of the output is: > > Requirement already satisfied: setuptools in ./venv/lib/python3.12/site-packages (80.9.0) So setuptools 80.9.0 is installed in your venv which is good. > And that's followed by downloading (or using a cached version) of 11 items before I get the subprocess error. > > (venv) mailman@wz-prd-tpmd-1:~$ /opt/mailman/venv/bin/pip install --proxy http://webproxyta.westat.com:3128 --trusted-host pypi.org setuptools mailman-web > Requirement already satisfied: setuptools in ./venv/lib/python3.12/site-packages (80.9.0) > Collecting mailman-web > Downloading mailman_web-0.0.9-py3-none-any.whl.metadata (3.2 kB) > Collecting django<4.3,>=4.0 (from mailman-web) > Downloading django-4.2.23-py3-none-any.whl.metadata (4.2 kB) > Collecting hyperkitty (from mailman-web) > Downloading hyperkitty-1.3.12-py3-none-any.whl.metadata (3.6 kB) > Collecting postorius (from mailman-web) > Downloading postorius-1.3.13-py3-none-any.whl.metadata (2.9 kB) > Collecting whoosh (from mailman-web) > Downloading Whoosh-2.7.4-py2.py3-none-any.whl.metadata (3.1 kB) > Collecting asgiref<4,>=3.6.0 (from django<4.3,>=4.0->mailman-web) > Downloading asgiref-3.8.1-py3-none-any.whl.metadata (9.3 kB) > Collecting sqlparse>=0.3.1 (from django<4.3,>=4.0->mailman-web) > Downloading sqlparse-0.5.3-py3-none-any.whl.metadata (3.9 kB) > Collecting django-compressor>=1.3 (from hyperkitty->mailman-web) > Downloading django_compressor-4.5.1-py2.py3-none-any.whl.metadata (5.0 kB) > Collecting django-extensions>=1.3.7 (from hyperkitty->mailman-web) > Downloading django_extensions-4.1-py3-none-any.whl.metadata (6.1 kB) > Collecting django-gravatar2>=1.0.6 (from hyperkitty->mailman-web) > Downloading django_gravatar2-1.4.5-py2.py3-none-any.whl.metadata (4.3 kB) > Collecting django-haystack>=2.8.0 (from hyperkitty->mailman-web) > Downloading django_haystack-3.3.0.tar.gz (467 kB) > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 467.3/467.3 kB 22.3 MB/s eta 0:00:00 The above is collecting mailman-web and its dependencies. > Installing build dependencies ... error > error: subprocess-exited-with-error > > × pip subprocess to install build dependencies did not run successfully. > │ exit code: 1 > ╰─> [2 lines of output] > ERROR: Could not find a version that satisfies the requirement setuptools>=61.2 (from versions: none) > ERROR: No matching distribution found for setuptools>=61.2 > [end of output] > > note: This error originates from a subprocess, and is likely not a problem with pip. > error: subprocess-exited-with-error > > × pip subprocess to install build dependencies did not run successfully. > │ exit code: 1 > ╰─> See above for output. > > note: This error originates from a subprocess, and is likely not a problem with pip. And this is all from a pip subprocess which is trying to build install build dependencies. I.e., this error is not necessarily related to django-haystack or any other specific package, but is saying it can't find a setuptools package to satisfy the build requirements. This in turn may be that the subprocess doesn't see your --proxy option. I think the issue may be that normally pip installs build requirements in an isolated temporary directory so as not to create potential conflicts with installed packages. See <https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/#build-…>. Specifying --no-build-isolation on the pip command will disable this. See <https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-no-build-isolation>. If you specify --no-build-isolation on the pip command, it should use setuptools and wheel from your venv. -- 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] Re: Prototype import [was: Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)]

by Mark Sapiro

On 4/19/25 1:55 PM, Mihai Moldovan wrote: > > This eventually led me to realize that passing > mailman.email.message.Message as the factory to mbox() internally calls > factory(msg), and the base class of Message (email.message.Message) has > an __init__ function that takes the policy parameter, so it looks as if > it's registering the mailbox message incorrectly as the policy handler, > which is totally wrong of course. This appears to be a bug in mailbox.mbox. To work around it, try this: ``` from email import message_from_bytes mb = mbox(sys.argv[2], create=False) for key in mb.iterkeys(): msg = message_from_bytes(mb.get_bytes(key), Message) ``` > and indeed, if I let the import actually happen, it works. Still, it's probably better if the message is a mailman.email.message.Message object rather than an email.message.Message object. > The imported messages, do have a Message-ID-Hash, but the Archived-At > and List-Archive headers are empty (literally <>). Those headers are added by the rfc_2369 handler based on the archivers configured for the list. They will never point to the prototype archiver or the message in the prototype archive. Normally they will point to HyperKitty and to the archived message in HyperKitty. This is the case even for messages in the prototype archiver as those messages are just the message as delivered to the list members absent any personalization. > Do you have an example message that was archived through Prototype? What > are the proper header values for this module? I believe that Archived-At > should be the Message-ID-Hash and the List-Archive header contain... > well, given that the Prototype archiver is not meant to be publicly > available, probably a file:// URL? Typically they will be something like List-Archive: <https://example.com/archives/list/listname@example.com/> Archived-At: <https://example.com/archives/list/listname@example.com/message/xxxxxx/> where xxxxxx is the message-id hash value. Note that the generation of these headers by the rfc_2369 handler depends on this script being run in an installation that has hyperkitty and mailman-hyperkitty installed and the hyperkitty archiver enabled for the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 4 weeks

[MM3-users] hosted signup is producing unexpected results

by tokyoprogressive＠mac.com

In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by sending a message to....... I then get a notice: "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" 7) While if they send FROM THE interface it goes through. 8) What I am confused about. Signing up for an account should make them a member, right? Subscribing should make them a non member, no? But here it seems that both make them a non member. And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. Before I can move my actual members over from another mailing list provider, I want to make sure what works and what doesn't. Thanks. paul!!!

6 years

[MM3-users] Re: Error on timeout vs retry values

by Robert Moody

Thank you, that's fixed it. On 19/07/21 7:28 am, Abhilash Raj wrote: > > On Sat, Jul 17, 2021, at 11:23 PM, Robert Moody wrote: >> Hi everyone, >> >> I have recently setup a new mailman3 service using the venv method. >> Everything is functionally working however I keep getting an error sent >> to the mailman email every min which I can not seem to figure out why. >> >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py:142: >> UserWarning: Retry and timeout are misconfigured. Set retry larger than >> timeout, >> failure to do so will cause the tasks to be retriggered before >> completion. >> See >> https://django-q.readthedocs.io/en/latest/configure.html#retry for details. >> See https://django-q.readthedocs.io/en/latest/configure.html#retry >> for details.""" >> >> I have edited the timeout and retry values in the >> /opt/mailman/venv/lib/python3.7/site-packages/django_q/conf.py file and >> restarted both mailman and mailman-web however this still keeps repeating. > You shouldn't edit files in `site-packages` directory as they are part > of the package itself and could cause issues. > > What you want to do is override it in your settings.py (or settings_local.py) file > for Django. I am not sure which guide you followed to install Mailman, but it > should be somewhere in /opt/mailman/ I suppose (not in venv/ for sure). > > It should look something like this > > https://mailman-web.readthedocs.io/en/latest/settings.html#mailman_web.sett… > > Just the value of retry should be just > than timeout as the error says, so > not necessarily same values, but so far 300 and 360 has been working > good for us and I haven't seen any report to increase them. > > >> Any ideas? >> >> Regards, >> >> Robert >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

4 years, 1 month

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

by ieso＠johnwillson.com

So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time. I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner. A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test. The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front. Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?) Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-)

4 years, 8 months

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

by Abhilash Raj

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

3 years, 11 months

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

by Philip Colmer

We've now completed the indexing of our lists, some of which are quite large (100K+ messages per list). I wanted to share our findings of using Xapian to do this. Firstly, using "-v 2", e.g. "mailman-web update_index_one_list -v 2 <email address>", causes the command to print out the progress being made in batches of 1,000 messages. Secondly, Xapian is single-threaded. It only allows one writer at a time. Therefore, we focussed on speed of the hard drives and, on the advice received from the Xapian list, memory. Since we were using AWS EC2 with EBS storage, I elected to move the EBS storage from gp2 to gp3 - which has a higher base I/O figure - and I selected a r6i.8xlarge as this guaranteed 10Gb throughput to the EBS storage. It also delivered 32 vCPU and 256GB RAM. It was possibly overkill but it did the job (see below) and we've now switched back to a t3a.xlarge. Speed-wise, with the above configuration, the system indexed a list of nearly 85K messages in 46 minutes. I hope that is helpful information to anyone else who finds themselves migrating large Mailman 2 archives. Regards Philip On Fri, 14 Jan 2022 at 17:33, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/22 12:38 AM, Philip Colmer wrote: > > 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? > > > > HyperKitty does the indexing by calling the Haystack update_index > command. See > > https://django-haystack.readthedocs.io/en/master/management_commands.html#u… > > This command has options such as --verbosity and --workers. I think > verbosity is set from the option provided to update_index_one_list and > if set to 2 will give some progress info. > > workers could increase parallelism but is unconditionally passed by > hyperkitty as 0 > > > -- > 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, 7 months

[MM3-users] Do not display any lists on index the page (/postorius/lists/) by default (when you create the list it defaults to Hide) - Debian package install

by daniel.botting＠codethink.co.uk

Hi all, I am currently in the process of moving from mailman 2.1 to mailman 3, the basic functions are completed (mailing list and archiving). On our current mailman 2.1 install it advises there are no publicly advertised lists, when I visit mailman3-list.domain/postorius/lists/ I see all the lists that have been created, I require them not to be displayed. I know when you create a list you can on the 'Advertise this list' line select 'Hide this list in list index', but I would like it to default to this in case somebody forgets to select it. I am not a Python expert, though from the description at the top of the below file and the contents further down it looks like you are defining in base.py and then in default.py you are using what was defined, a class of 'Private' which should cause the lists not to be advertised, but they are? File: /usr/ib/python3/dist-packages/mailman/styles/base.py class Private: """Settings for private mailing lists.""" def apply(self, mailing_list): mlist = mailing_list mlist.advertised = False <-------------- mlist.archive_policy = ArchivePolicy.private mlist.subscription_policy = SubscriptionPolicy.confirm_then_moderate File: /usr/lib/python3/dist-packages/mailman/styles/default.py class PrivateDefaultStyle( Identity, BasicOperation, Bounces, Private, Discussion, Moderation): """Style for mailing-lists with private archives.""" name = 'private-default' description = _('Discussion mailing list style with private archives.') def apply(self, mailing_list): """See `IStyle`.""" Identity.apply(self, mailing_list) BasicOperation.apply(self, mailing_list) Bounces.apply(self, mailing_list) Private.apply(self, mailing_list) Discussion.apply(self, mailing_list) Moderation.apply(self, mailing_list) I added the below to /etc/mailman3/mailman.cfg: [styles] # The default style to apply if nothing else was requested. The value is the # name of an existing style. If no such style exists, no style will be # applied. default: private-default I took 'private-default' from /usr/lib/python3/dist-packages/mailman/styles/default.py, this means now when a new list is created the List style is 'Discussion mail list style with private archives so it is not displayed when you are logged out at /hyperkitty. Many thanks Daniel

2 years, 10 months

[MM3-users] Re: Running customized version of Mailman 3

by Alan Kelm

On 2/29/20 9:02 AM, Stephen J. Turnbull wrote: > Alan Kelm writes: > > > Since 2005, our organization has been running a customized version of > > Mailman 2 with extensions that meet our particular needs. The main > > novelty is support for /fixed subscription lists/, in which the list > > members are predetermined (corresponding to a "committee"). > > It's not clear to me that this can't be achieved with existing Mailman > 2 (or 3) features. That is, a committee's list could be populated > using mass subscribe, and unsubscriptions can be prevented by > requiring admin intervention. You are correct in pointing out that fixed lists could be implemented without customizations to Mailman, provided that one is willing to leave intact various references to users subscribing and unsubscribing themselves. Modifications were required in 6 separate places (for Mailman 2) to suppress such references for fixed lists. We had additional extensions to permit programmatic re-syncing of subscriber and permitted sender lists with data sources, an adjustment to suppress monthly subscription reminders for such lists, and lots of other minor tweaks that were not strictly necessary. > I'm not sure why this (or the "hybrid" list) requires patches. If I > am correct that the basic functionality is present, and requires only > small tweaks, it might be possible to include those tweaks in Mailman > 3 itself. (I can't promise; this requirement also seems quite rare, > and if substantial code changes, or multiple configuration options, > were required, we might prefer to avoid them.) Our hybrid lists were implemented using separate lists - an outer /opt-in/ list having a /fixed/ list as one of its subscribers (using a generic parent/child list framework). Quite a few customizations were needed to smooth over the rough points of this arrangement (for example to ensure that only the parent list's subject line prefix appears on message subject lines). Now that I reflect upon it, it would be likely be possible to maintain a mandated list of subscribers as a subset within an opt-in list (provided that one keeps a separate copy of the mandated subscribers, to enable detection of previously mandated addresses that need to be deleted). If I were to implement hybrid lists under Mailman 3, I would be inclined to look for simpler mechanisms that what we used under Mailman 2. > > We are considering moving to Mailman 3 and would like to do this in > > a way which makes it possible to periodically upgrade our > > installation to the newest Mailman version, without clobbering our > > customizations. Thus, I do not think that installing via "pip" is > > the right approach for us. While I'm relatively new to git and > > GitLab, they seem to be ideally suited to this situation. If I > > understand the developer documentation correctly, I start out by > > creating a "fork" and can later "fetch" changes from the master > > branch and "rebase" to bring them into our branch. > > Your understanding is correct in principle. If you don't have > experienced git users around, you might want to find somebody to help > you design a workflow. Eg, in general you want to rebase your changes > on top of the mainline, rather than the other way around. You also > need to be prepared for occasional cases where your patch conflicts > with something we do in the same place of the same file. Thank you for these helpful comments. When the time comes, we'll make sure to get the git configuration worked out properly. My investigations over the past few days have convinced me that we are better off sticking with Mailman 2 for a while longer. One feature which is essential for us is to have the list manager informed of bounces, so that failing addresses can be corrected and important missed messages can be resent by other means. The lack of bounce handling in Mailman 3.2 is therefore a showstopper for us. (One of our customizations for Mailman 2 ensures that bounce notifications are sent to the list manager, but this was just a small tweak to existing bounce handling code). I look forward to returning to take another look at Mailman 3 in the future. Thank you, once again, for your helpful comments. -Alan -- Alan Kelm Manager, Electronic Services Canadian Mathematical Society

5 years, 6 months

[MM3-users] installing mailman3 core

by Ralf Wiegand

Mark - What is the difference between to two install methods? What are my pros and cons? I have been using this: >>>> |# Note: if we are using a dedicated postgresql database server, all postgresql changes need to be done on the actual postgresql server.| |>>>| |sudo yum install postgresql-server postgresql-contrib| |sudo postgresql-setup initdb| |sudo systemctl start postgresql| |sudo systemctl enable postgresql| |sudo -u postgres psql -c ||"SELECT version();"| |sudo useradd -c ||"Mailman User"| |-s /bin/bash -m mailman| |sudo -u postgres create role mailman;| |sudo -u postgres createdb -O $USER mailman| |sudo -u postgres psql -c ||"grant all privileges on database mailman to mailman;"| |sudo -u postgres psql -c ||"ALTER ROLE mailman WITH PASSWORD 'secret123';"| |sudo -u postgres psql -c ||"ALTER ROLE "||mailman||" WITH LOGIN;"| |sudo echo ||"listen_addresses = '*' "| |>> /var/lib/pgsql/10/data/postgresql.conf| |sudo echo ||"# The user mailman will be able to access all databases from a trusted location (any) without a password"| |>> /var/lib/pgsql/data/pg_hba.conf| |sudo echo ||"host all mailman 0.0.0.0/0 trust"| |>> /var/lib/pgsql/data/pg_hba.conf| |sudo systemctl restart postgresql| |sudo ss -nlt | grep 5432| |<<<| |sudo yum install python36* --skip-broken -y| |# check make sure you have both versions| |sudo python --version| |Python 2.7.5| |sudo python3 --version| |Python 3.6.8| |sudo pip3 install psycopg2-binary| |sudo chown mailman.mailman /opt/mailman| |sudo chmod 755 /opt/mailman| |# NOTE: The first initial mailman3 core setup has to be done manually.| |# This is a important step to ensure the user "mailman" will run the actual mailman3 application and not root.| |# switch to user mailman| |mailman# cd /opt/mailman| |mailman# git clone https:||//gitlab.com/mailman/mailman.git| |mailman# cat <<EOT >> /opt/mailman/mailman/src/mailman/config/mailman.cfg| |[devmode]| |enabled: yes| |recipient: root@localhost| |[webservice]| |hostname: localhost| |port: 8001| |show_tracebacks: yes| |use_https: yes| |[mta]| |incoming: mailman.mta.postfix.LMTP| |outgoing: mailman.mta.deliver.deliver| |lmtp_host: localhost| |lmtp_port: 8024| |smtp_host: localhost| |smtp_port: 25| |[database]| |class||: mailman.database.postgresql.PostgreSQLDatabase| |url: postgres:||//mailman:secret123@<IP-ADDRESS or FQDN>/mailman| |EOT| |mailman# python3.6 -m venv venv-3.6| |>>| |mailman# source venv-3.6/bin/activate| |(venv-3.6) [mailman@empire mailman]$ cd mailman| |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| |(venv-3.6) [mailman@empire mailman]$ mailman info| |<<| | | | | |So I was told I don't have to do this, I can just simple do (rhel7) | |yum install pyhton3| |pip install mailman| | | | |

5 years, 3 months

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

by Odhiambo Washington

On Sat, Nov 18, 2023 at 11:48 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > Hello Stephen et al, > > > > Since this topic is relevant to something I am faced with at the > moment, I > > believe it's okay if I piggyback on the thread. > > I think continuing the thread is appropriate, but I personally would > change the Subject to reflect the specifics. > > > I have a server that is already actively distributing Mailman list > traffic, > > and managing users and archives. > > I have offered to take over another community ML (also using MM3) from > > another server and host the list on my server. > > 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. > > > > Any pointers on how to bring in this new site into my current setup?? > > I don't have pointers, in the sense of concrete advice I would not be > horrified if you followed it to the letter. Here's how I would attack > the problem. > > 1. Decide the List-Id and List-Post questions. I disagree with Mark > about List-Id (or maybe he mistyped List-Post?) -- the List-Id > should NOT be changed. I don't know how many users are taking > advantage of List-Id (my filters do!), but they will thank you for > keeping it the same. > > The List-Post question is contingent. Will you be serving their > domain, or will you change the List-Post address? The idea is to (if possible) not change anything at all. I will be serving the list using the original domain. I am hoping for a seamless migration where no one notices any change except for the IP address where the MM3 is running. > Note that with > some additional configuration to Mailman and your MTA they could > set up a forwarding configuration for their lists to your server, > Or if they don't have other email needs, set up an MX. Or they > can transfer their domain name's A and MX records to your host. > As it is, I have been given full control of the domain for this purpose so I can point A and MX records to my server. The ML itself is currently down. I have a dump of the /opt/mailman as well as the DBs used by Core and Web. Alternatively you can change the List-Post address.to your > domain. In that case you will have to edit the List-Post address > in your database. > I am hoping that should not be necessary. I actually had thought it wouldn't be complex doing this until I sat down and said wait - there is a DB involved :) > 2. There are similar issues for mailman-web (especially host names). > I have not thought about them at all, so I'll leave that for the > interested reader. ;-) > Hehee.. Wrapping my head around this has not been easy, to say the least. 3. (If the DB engines are different) Dump both databases in text > format (ie, scripts of SQL commands). Check to see how they > differ. > The DB is MySQL. My running setup uses MariaDB. I am not getting what you mean here by how they differ. 4. Adapt the foreign database to its new environment with search and > replace. (Be verbose about the search terms, include lots of > context to minimize the chance of inadvertantly replacing > something in the wrong context that you missed in step 3.) This > is where you would change the List-Post address, as well. You > will also want to change the 'mailmanweb' database to just 'mailman'. > If going with what I have mentioned above, is this step still necessary? > 5. (Optional if your name is "Daredevil") Create a new Mailman suite > install using your current configs, preferably in a new VM or set > of containers. Configure the MTA to save all outgoing mail to a > file, or maybe firewall off outgoing network traffic to port 25 > and leave all the posts in the MTA queues. Create a new > 'mailman-test' database. Copy all the dumps to the VM, and edit > the names of the databases in the SQL to 'mailman-test'. Restore > the dump of your system into the database, and test. Then do the > same, restoring the mailman and mailmanweb databases from the > foreign system into this new database. > I was thinking about this as one way of testing the situation, much as it is quite involving. 6. Adjust to address any issues discovered in 5. If none, go to 7, > Otherwise go back to 5. > > 7. Apply any changes made in 6 to your configs, and read the foreign > dumps into your system, and you should be ready to go for the > distribution part. Not sure about host and webserver > configuration for mailman-web, though. > Suppose I just do: 1. Create the new list on my server using the inherited domain and configure it appropriately, 2. Configure Django to handle the different domains (there is something that I am yet to understand here around SITE_ID when you have multiple sites!) 3. Extract the users from the list and subscribe them afresh (I can shoot an email to let them know the ML had to be moved so they can set their preferences again) 4. Import the archives of the list I should more or less achieve the migration, no? What about setting up on /opt/mailman2 a complete replica of the list? That'd be the real "Daredevil" :) -- 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: Speed/progress of update_index_one_list?

by Philip Colmer

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? 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: 1. Download the git repo at https://github.com/notanumber/xapian-haystack 2. Run the "install_xapian.sh" script (supplying the version number of Xapian) 3. pip install xapian-haystack 4. Edit the MM3 settings.py file to switch to using Xapian Regards Philip On Fri, 14 Jan 2022 at 07:57, Philip Colmer <philip.colmer(a)linaro.org> wrote: > > > On Fri, 14 Jan 2022 at 07:50, Mark Dadgar <mark(a)pdc-racing.net> wrote: > >> On Jan 13, 2022, at 11:46 PM, Philip Colmer <philip.colmer(a)linaro.org> >> wrote: >> > Yesterday, I ran "mailman-web update_index_one_list" against a mailing >> > list. The command output "Indexing 328077 emails" and that is the last >> I've >> > heard from it. >> > >> > The process is still running but, looking in ~mailman/web/logs, I can't >> see >> > anything happening related to that list. >> > >> > Is there any way to determine how far this process has got, or what it >> is >> > actually doing? (Without stopping it) >> > >> > For future indexing, what makes the most difference to the speed? Does >> it >> > benefit from having multiple cores if I resize the AWS instance to a >> larger >> > processor? What is the bottleneck for this process? >> >> >> Which indexer are you using? Whoosh is interminably slow. Think “days to >> generate a list index” slow. >> > > Yeah, we're using Whoosh. Good to see it lives up to its name :) > > >> I recommend Xapien. It is ridiculously fast. >> > > Thank you. I had been put off using Xapian because the documentation, from > a MM3-perspective, seemed sparse and confusing, but I'll stick with it to > try and get it working if Whoosh is the root problem here. > > Philip > >

3 years, 8 months

[MM3-users] Re: dedicated mailman3 list server on Ubuntu 18.04 LTS - questions after installation

by Mark Sapiro

On 08/05/2018 03:37 PM, John Seifarth via Mailman-users wrote: > > The installation allows me to sign into the web interface, create a host, create mailing lists, and mass subscribe members. When members send email to the list address, the server sends the messages normally to the other members of the list. That's the good news. That's cool. You have raised a lot of questions and I don't have time now to deal with them all. Maybe others can help. I will say a few things now and maybe more to follow. > However, when I look at the list archives, there are no posts. I deliberately mass-subscribed an invalid address, and I can see in /var/log/mail.log that the message bounces, but I get no notification, nor do I see any bounce info when I look at the member info. About Archiving: Are you running django qcluster <http://docs.list.org/en/latest/config-web.html#running-the-task-queue-requi…> and all the scheduled tasks <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>? About Bounce processing: Bounce processing is not functional in Mailman 3 yet. > 5) DKIM and DMARC > > I’ve got OpenDKIM running on inet:12345@localhost and OpenDMARC running on net:54321@localhost. > > How can I get mailman to use these milters and sign messages? How should DMARC munging be configured when signing? Your outgoing MTA should be doing the signing, not Mailman. Your signing outgoing messages won't help with DMARC if Mailman alters the message in any way, e.g. by subject prefixing, content filtering or addition of list headers and/or footers. Minimum DMARC settings would be DMARC mitigation action -> Replace From: with list address and DMARC Mitigate unconditionally -> No > 6) Is there an overview of how mailman3 works? > > Is there documentation which explains the path of an incoming post through the system, including initial reception, list processing, sending to members, processing bounces, and archiving posts? All the docs are at <http://docs.list.org/en/latest/> You may want to see <http://mailman.readthedocs.io/en/latest/src/mailman/docs/8-miles-high.html> amongst the many other things you'll find there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] 'str' object has no attribute 'token_type'

by Marco Marinello

Hi everybody, I'm sorry for being always the strange guy with strange errors here but for some reason... I am. On a Mailman installation that was doing just fine for more than a year, I started receiving error messages per email. It happens when mailman daemon archives a messages. Although the messages is correctly archived, this exception is thrown by Hyperkitty: Traceback (most recent call last): File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/local/lib/python3.9/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 118, in _decorator return func(request, *args, **kwargs) File "/usr/local/lib/python3.9/dist-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/usr/local/lib/python3.9/dist-packages/hyperkitty/views/mailman.py", line 164, in archive add_to_list(mlist_fqdn, msg) File "/usr/local/lib/python3.9/dist-packages/hyperkitty/lib/incoming.py", line 79, in add_to_list from_str = header_to_unicode(message['From']) File "/usr/lib/python3.9/email/message.py", line 391, in __getitem__ the values matching a header field name. File "/usr/lib/python3.9/email/message.py", line 471, in get for k, v in self._headers: File "/usr/lib/python3.9/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/lib/python3.9/email/headerregistry.py", line 601, in __call__ return self[name](name, value) File "/usr/lib/python3.9/email/headerregistry.py", line 196, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.9/email/headerregistry.py", line 343, in parse [Address(mb.display_name or '', File "/usr/lib/python3.9/email/headerregistry.py", line 343, in <listcomp> [Address(mb.display_name or '', File "/usr/lib/python3.9/email/_header_value_parser.py", line 462, in display_name return self[0].display_name File "/usr/lib/python3.9/email/_header_value_parser.py", line 393, in display_name return self[0].display_name File "/usr/lib/python3.9/email/_header_value_parser.py", line 574, in display_name if res[-1][-1].token_type == 'cfws': Exception Type: AttributeError at /hyperkitty/api/mailman/archive Exception Value: 'str' object has no attribute 'token_type' Request information: USER: AnonymousUser I upgraded both to Debian 11 (from 10) and to latest versions of Hyperkitty, mailman-hyperkitty and mailman but still getting the error. Other installations with same specs I'm managing to do not encounter this problem. Any clue of what could have happened, why and how to fix it? Thanks in advance, Marco

3 years, 10 months

[MM3-users] Which folder should I share between pods with kubernetees persistentVolumeClaim ?

by Stephen J. Turnbull

antoine.depoisier--- via Mailman-users writes: > I use mailman with kubernetees, and I have four pods. Mailman is known to work in Docker, but the frequently used configuration is basically divided by application: all of the core mail- and list-handling processes in one container, the web administration processes in another, the archiver in another, and perhaps the RDBMS and MTA each have their own. So I don't understand what you mean by "with Kubernetes", and definitely not the node topology. Are you running any of the 5 applications just mentioned across multiple nodes? > I currently use persistentVolumeClaim for two folders in the > mailman configuration "cache" and "messages". > I share these folders, as mailman needs to be consistent for these > two folders, but I'm wondering if I should share other folders as > well, like locks and such. All of the processes need access to locks and to their relevant queue directories. I can't tell you offhand how which processes need access to which directories. > I ask this question because I often have a problem when creating a > mailing list. I think I have a problem with the locks, but I'm not > sure if the problem is due to the fact that the locks folder is not > shared. I would guess it's related. It's certainly very bad that a file that is supposed to be locked appears to be unlocked when the time comes for the lock owner to unlock it: > flufl.lock._lockfile.NotLockedError: Already unlocked [...] > When I check the lock folder, I have these two files, and I'm > wondering if I should delete these two files : > -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck > -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck|mailman-core-deployment-5f59557b66-bkkf4|16|4268829230172994873 Don't do that. If you want those to go away, stop Mailman. As Obi-wan Kenobi said, "These are not the locks you are looking for." The lock in your trace is specific to the Postfix routing files, The master.lck is used by the master process that controls all that others. > Do you have any answer for me ? Need to know the topology of the network of nodes hosting Mailman processes. Steve

7 months, 1 week

[MM3-users] Re: Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by Mark Sapiro

On 5/3/21 3:27 PM, summersan(a)nclack.k12.or.us wrote: > Hi Mark, > > Thank you for your quick response! > > When setting up Mailman 3, I went through much of this "how to" guide here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10. Which uses gunicorn as the wsgi server for Django. > As far as I can tell, my current setup appears to be proxying from Nginx to Gunicorn, according to the related Nginx and mailman3-project-specific Gunicorn config files. Specifically, I checked the local address:port being used in the Nginx file and compared that to the mailman3-project-specific Gunicorn bind address. It looks like I might have "separated out" the REST API to a different server block in the Nginx config file, so I think I'm looking at the correct server block with this conclusion. Nginx has nothing to do with the REST API. The REST API is accessed by Postorius and HyperKitty via mailmanclient and django-mailmane which are installed by pip as dependencies of Postorius and Hyperkitty. > For what it's worth, I don't recall this type of "slow first visit startup" issue happening in the past when using web applications with uwsgi, and I've had the opportunity to use uwsgi with a variety of programs. I think Gunicorn is fairly new to me. I do, however, remember that something like this might have happened in the past when using Passenger (https://www.phusionpassenger.com/) a long time ago, but that might have been setting related on my part. > > Okay, thanks for the encouragement about the potential solution to periodically accessing the related "example.mailman.site/mailman3/lists/" type location (from my earlier email). Wanted to check on that and was also hoping that there might be some setting I'm missing in the overall Mailman 3 project setup related to the "slow first visit startup" issue. I'm not aware of anything you missed. I think this has to be a gunicorn issue or possibly related to Django, but I'm not specifically aware of any issues. There might be something you can set in gunicorn, but I don't know what. -- 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: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 18/9/21 14:29, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > On 18/9/21 7:10, Stephen J. Turnbull wrote: > > > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > > > > > 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. > > > > > > Not sure what you want here. I don't see how this is supposed to work > > > -- if a subscriber is set to accept, the moderator will never see the > > > posts until they're distributed to the subscribers. > > > > I'll try to explain: > > > > In my experience, the most useful tool to cool down a thread that has > > converted in a flame is to stop free distribution (hold) new mails > > coming from some suscribers > > That's what I was missing. You want moderators to be able to set the > moderation flag on a particular member, or several members. Yes. Exactly. That's the unique capability for moderators (that admins have) that I think mailman lacked ever. From my perspective: there is two complementary "sides" when it comes to managing a list: the admin tasks, configuring, setting rules of suscribing, acceptation mails, etc. AND the management of the flux of messages. Thats what I call "moderation". Warning suscribers when a thread overheat, and being capable to set off a member when his behaviour makes it neccesary. Good you have understand me despite muy poor explanations. In mailman2 I have this second part covered via python scripts (and login via special account from moderators), and I will do in mailman3. If I cannot succeed via python, I'm planning doing it via DDBB. Let's see. > > > A moderator doesn't have to be capable of configuring lists, but > > they would have to be capable to moderate the flux of mails when > > it's necessary. > > As I wrote before, I think this needs to be an option controlled by > the owner, which makes implementation more complicated. But we'll see > what the rest of the core thinks. > > Steve >

3 years, 11 months

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

by Odhiambo Washington

On Thu, 30 Jul 2020 at 00:13, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/20 12:15 AM, Odhiambo Washington wrote: > > > > Yes, the same problem. > > I created the file __init__.py in /opt/mailman/mm > > However, when I run using the wsgi.py I ended up (still do!) with the > error: > > > > [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote > > 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', > > application='mm3-lists.server.name|/mm3'): Loading Python script file > > '/opt/mailman/mm/wsgi.py'. > > What is the contend of the file /opt/mailman/mm/wsgi.py? > [wash@gw ~]$ cd /opt/mailman/mm/ [wash@gw /opt/mailman/mm]$ less wsgi.py """ WSGI config for HyperKitty project. It exposes the WSGI callable as a module-level variable named ``application``. For more information on this file, see https://docs.djangoproject.com/en/{{ docs_version }}/howto/deployment/wsgi/ """ import os # import sys # import site # For some unknown reason, sometimes mod_wsgi fails to set the python paths to # the virtualenv, with the 'python-path' option. You can do it here too. # # # Remember original sys.path. #prev_sys_path = list(sys.path) # # Add here, for the settings module #site.addsitedir(os.path.abspath(os.path.dirname(__file__))) # # Add the virtualenv #venv = os.path.join(os.path.abspath(os.path.dirname(__file__)), # '..', 'lib', 'python2.6', 'site-packages') # site.addsitedir(venv) # # Reorder sys.path so new directories at the front. # new_sys_path = [] # for item in list(sys.path): # if item not in prev_sys_path: # new_sys_path.append(item) # sys.path.remove(item) # sys.path[:0] = new_sys_path from django.core.wsgi import get_wsgi_application os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") application = get_wsgi_application() > You previously posted the setting of WSGIDaemonProcess in your Apache > config as: > > > WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 user=mailman3 \ > > group=mailman3 > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > \ > > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > Is it still that? > This is from wsgi.conf in my Apache Includes/. It's a copy/paste of your version, with the only modification being the change pf python version to 3.7 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

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

by Fabian A. Santiago

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

7 years, 10 months

[MM3-users] Re: Apple Mail encoding again

by David Newman

On 4/14/22 9:50 AM, Mark Sapiro wrote: > On 4/14/22 08:21, Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> >> > That combination at least produces multipart/signed messages with >> > multipart/* parts containing a Content-Transfer-Encoding: header. >> > >> > The Python 3 email library considers this to be a >> > InvalidMultipartContentTransferEncodingDefect() message defect. >> >> Merely containing C-T-E is not an error per RFC 2045, although it >> seems to consider it a stupid thing to do. If present, it may be >> "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). >> >> Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening >> that restriction been published since? (I don't know why it would, >> though.) > > > Yes. The C-T-E on all the multipart parts was quoted-printable, not > allowed under RFC 2045. > > >> Even with a non-cleartext C-T-E, it seems reasonable for Mailman to >> treat it as application/octet-stream and pass it through, unless the >> list is configured to do something like strip application/octet-stream >> or that requires decoding like spam-filtering (Postel principle, >> although one could argue it shouldn't be sent on on the same principle >> -- ah, the joys of being an e-mail Mediator). That would be >> especially true it if were quoted-printable, since any relevant MIME >> headers would (presumably) be pure ASCII and therefore unencoded. > > > The Python email library says the message is defective. Mailman's lmtp > runner in turn rejects the defective message with a 501 status > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… > Yes. To be clear, this is an Apple Mail issue. Mailman 3 accepted PGP-signed messages from Apple Mail on versions prior to 15.0 running on MacOS 12.0.1. Something changed on Apple's part. > > It could accept a defective message or one with specific defects, but > this is problematic for further processing. For example, at least one > MUA, Thunderbird, renders such a message with an empty body. That's not my experience. Mailman 3 accepted without complaint a PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to list subscribers with the message body intact. dn

3 years, 5 months

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

by Mark Sapiro

On 2/11/19 10:01 AM, Abhilash Raj wrote: > > Please create a bug report at https://gitlab.com/mailman/hyperkitty/issues with the affected messages. > > It would help us recreate the problem if you could attach a raw messages in the issue. I am > assuming the messages aren't sensitive since the archive are open. Otherwise, feel free to omit > any sensitive information. > > I haven't looked at the threading code in HK since a long time, but my impression is that it > looks at the 'In-Reply-To' header to figure out if the current email is a response to a previous > email that it received. > > In some cases, the order of the incoming messages can cause this to break, like when the > reply comes in first and the original messages comes in later. I am not sure exactly what is > happening here, but looking at the raw messages should help us reproduce and possibly > fix the issue. I downloaded the February mbox from <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> and imported it to a test list with 'django-admin hyperkitty_import and see the same issue. Examination of the mbox shows for the first message Message-ID: < <SN6PR01MB4719346533C08BF4FF62B880C36C0(a)SN6PR01MB4719.prod.exchangelabs.com>> This will be wrapped, so here's an excerpt Message-ID: < <SN6....prod.exchangelabs.com>> Note the folding of the header and the double angle brackets. The next message has (again excerpted to avoid wrapping) Message-ID: < <BL0....prod.exchangelabs.com>> In-Reply-To: SN6....prod.exchangelabs.com Note again the doubling of the angle brackets in the Message-ID and the absence of angle brackets in the In-Reply-To: The Message-ID: and In-Reply-To: headers of subsequent messages have the same issues. In looking at other mboxes downloaded from Hyperkitty, I see that the absence of References: and the dropping of the angle brackets from In-Reply-To: seem to be usual, and importing such a mbox preserves the threading. However, the doubling of the angle brackets is not usual and is almost certainly the cause of the problem. Do you have any of the original messages? What do the headers look like in those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-30 10:22, Mark Sapiro wrote: > On 11/30/22 08:41, Jan Eden via Mailman-users wrote: > > > > Changing the PATH value to a full path (/opt/mailman/fulltext_index) > > and restarting mailman-web generates a different error: > > > Yes, it should be a full path. I encountered yet another problem with emails not getting archived anymore: > ERROR 2022-12-01 09:18:00,111 1337915 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP XXX.XXX.XXX.XXX, your MAILMAN_ARCHIVER_FROM setting may be misconfigured where XXX.XXX.XXX.XXX is my server's public IP. This was probably caused by the switch to uwsgi_pass/a file socket, and could be fixed by adding MAILMAN_ARCHIVER_FROM = ('XXX.XXX.XXX.XXX', '::1') to /etc/mailman3/settings.py. > > > ERROR 2022-11-30 16:38:37,953 1028315 django.request Internal Server Error: /archives/list/testing@lists.eden.one/thread/T6MCILAVQYV5QIOGHJB3JNJ26Z7E2Z35/reattach-suggest > > > Traceback (most recent call last): > > > File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner > > > response = get_response(request) > > > File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response > > > response = wrapped_callback(request, *callback_args, **callback_kwargs) > > > File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner > > > return func(request, *args, **kwargs) > > > File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 454, in reattach_suggest > > > sugg_thread = msg.object.thread > > > AttributeError: 'NoneType' object has no attribute 'thread' > > > This says that searching the archive for this list for messages matching the > current message subject returns None. It is probably a bug that we don't > test for this, but what exactly are you doing? > See the post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for the only way I've been able to create an error like this. There are currently 5 (test) threads in the archive. After changing the PATH in the HAYSTACK_CONNECTIONS dict to /opt/mailman/fulltext_index, and fixing the issue with MAILMAN_ARCHIVER_FROM above, /opt/mailman/web/logs/mailmanweb.log does not display new error messages, but I do not get any suggestions for reattaching threads, and a search for a specific thread subject ("Third test") does not return any results. So reattachment works in principle, but the suggest/search function does not. - Jan

2 years, 9 months

[MM3-users] Re: Mailman recovery test did not go as planned

by Mark Sapiro

On 8/5/22 09:38, bob B via Mailman-users wrote: > I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. > I need to perform a DR recovery test. > > I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). Does shutting down mailman-web also shut down Django qcluster? If not, this could be an issue. > While Mailman was stopped, I had our database team take a backup dump of the database. > I then restarted Mailman in docker. > I threw some more messages at a test list. > I validated that the new messages were delivered, and showed up in the archive. > I shut down Mailman again. > I had the database team restore the Mailman database from the backup. > I started Mailman > I logged into Mailman > I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. I would expect that too. > When went into the list archive, I get a spinning icon and no messages showed up. I don't offhand know what the issue would be unless Django qcluster was running the whole time. > I quit, restarted my browser, and logged in again, and the same thing. > I then sent a test message to the list and the message was delivered to the list. > Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Possibly one of the Django periodic jobs, maybe cache_cleanup or daily_cleanup would fix it without a message. > Is this normal? After a restore did the new message cause a refresh of archived messages etc? > Is there a way to do this without sending a message to a list after a restoration of the database? > > Are there better steps I should take when restoring the database? I don't know what better you could do as far as the save and restore are concerned as long as shutting down mailman-web stops qcluster. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Odhiambo Washington

On Wed, May 31, 2023 at 4:18 PM <justfixit(a)marilynstrother.com> wrote: > Very interestng! Upon restarting the system (down momentarily for taking a > snapshot) and starting Mailman again, all of these missing [List] messages > emerged from their timewarp and were delivered to the members / > subscribers. Just before shutting down the system I discovered that the > apache2 webserver had been off the air due to a module not being enabled > yet. > As of yet, I was unaware of any requirement for a web server to be online > (beyond possibly gunicorn) in order for Mailman to run its lists. Does that > speculation have a factual basis? Or do I risk starting a vicious rumor > amongst the impatient readers who are not still here once we deduce this > pair of observations were merely correlated in time, with no > cause-and-effect relationship? > Before this situation healed itself, the thought had crossed my mind to > peek and see if anything was stuck in the queues: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > While that could have provided peace of mind that email messages were > merely delayed instead of vanished, even in hindsight I do not see how that > would have led to repairing the situation. > Mailman3 is in two parts which are completely INDEPENDENT: 1. Mailman Core - Details at -> https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… 2. Maiman Web - Details at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-web-… Only Mailman Web requires a web server. To run a mailing list, you need Mailman Core+Database+MTA. No Webserver is required. In the absence of a hypothetical command: > mailman status --verbose > about which diagnostic tools or clues should I learn? > You should learn how to configure the logging for Mailman in mailman.cfg and how to read and interpret the information written to the logfiles :-) PS: I know MM3 is a big animal and isn't easy to understand. I have been through that - and still there. With time you'll just understand the bits so don't despair. -- 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, 3 months

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

by Mark Sapiro

On 1/5/22 4:01 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > In this last point I've received some warnings of this kind: > > *-*-*-*-*-*-* > > WARNINGS: > account.EmailAddress: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > AccountConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > account.EmailConfirmation: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > > ... > > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > 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. ... > 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 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

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

by Brian Carpenter

On 2/13/21 3:03 AM, Stephen J. Turnbull wrote: > How different is this from Mailman 2? (Just "not really different" is > fine, I'll be looking at your specific desiderata for more details > later, including potential GSoC tasks.) It seems to me it's basically > the same, except maybe for some Web 2.0 features like sorting on > fields. (I'm not deprecating those features: obviously sorting would > have helped Allan a lot, for example. It's just that Mailman 2 is > very much a Web 1.0, maybe even Web 0.9, application.) Am I missing > something big? I actually took at lot of ideas from the MM 2 Membership List page simply due to the fact that Postorius' was not helpful in inspiring anything. The one thing that I did do is take MM2's approach and modernized it. So here are more tasks a List Owner can do that MM2 could never offer (and Postorius doesn't even come close): -- Sort Members by Delivery mode (regular vs digest). (MM2 has no sorting abilities at all except by alphabet, Postorius doesn't even have that) -- Reveal which Members are registered with the UI (MM2, everyone was registered, in Postorius nothing is revealed about registration) -- Show in one List Member Management panel List Members, Non-Members, Moderators, and Owners (MM2 and Postorius requires this data to be seen via multiple pages) -- View Member's List Subscriptions to other Mailing Lists on the server and, if that List Owner is List Owner of those other lists, can even access the List Owner board (Affinity terminology) for those other Lists. -- Ban a member -- Promote a member to List Owner and/or Moderator -- Add a new List Member, List Owner, Moderator, and Non-Member from a Single List Member Membership panel. (Again both Postorius and MM2 requires multiple pages. Postorius is an improvement in this regard over MM2. The funny thing with Postorius is you can add a single Non-member, Moderator, and List Owner, but you cannot add a single List Member except through *Bulk* adding.) Features are not the only thing about a modern UI, UX design plays a MAJOR role in the modern UI. Postorius should have at least matched MM2 in features in regards to something as important as Member management but instead it took a step back into the dark ages. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 7 months

[MM3-users] Re: Again, after systemupgrade the log file in /var/log/mailman was owned by list:list instead of mailman:mailman and starting failed for this reason [support request]

by Odhiambo Washington

On Sun, Dec 24, 2023 at 3:35 PM Wikinaut <mail(a)tgries.de> wrote: > This is in > > /opt/mailman/web/logs# dir > total 3164 > 276 -rw-r--r-- 1 mailman mailman 274457 Dec 24 09:05 mailmanweb.log > 2056 -rw-r----- 1 mailman mailman 2100388 Dec 24 09:05 uwsgi-error.log > 832 -rw-r----- 1 mailman mailman 846536 Dec 24 09:10 uwsgi.log > > Looks okay. > > This is my /etc/systemd/system/mailman3.service: > > Unit] > Description=GNU Mailing List Manager > After=syslog.target network.target mysql.service > > [Service] > Type=forking > User=mailman > Group=mailman > PIDFile=/opt/mailman/venv/bin/master.pid > ExecStart=/opt/mailman/venv/bin/mailman start --force > ExecReload=/opt/mailman/venv/bin/mailman restart --force > ExecStop=/opt/mailman/venv/bin/mailman stop > > [Install] > WantedBy=multi-user.target > > > This mailman3web.service: > > [Unit] > Description=GNU Mailman Web UI > After=syslog.target network.target mysql.service mailman3.service > > [Service] > Environment="PYTHONPATH=/etc/mailman3/" > User=mailman > Group=mailman > ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > KillSignal=SIGINT > > [Install] > WantedBy=multi-user.target > > > > > I do use the venv method, but the other issue may be a relict from former > setup, as I said, and difficult to find. > It so very strange, that the log-permisison issue stems from → systemctl > start mailman3. > Because you were referring to /var/log/, can you please share the output of the following: grep var_dir /etc/mailman3/mailman.cfg In my mailman.cfg, I have: var_dir: /opt/mailman/mm/var And in my settings.py I have /opt/mailman/mm/var/logs/mailmanweb.log specified for mailman-web. As you can see, mailman core and mailman-web both log to /opt/mailman/mm/var and given that /opt/mailman is owned by mailman:mailman, I don't see how a file owned by list:list would appear there. I also don't see how anything to do with /var/log/ is in your vocabulary :-) -- 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, 8 months

[MM3-users] The future is here?

by ieso＠johnwillson.com

In my quest to figure out how even us idiots can successfully install a mailman3 server, I keep looking ways to reduce the process to the simplest possible set of instructions. So far, I haven't been doing very well with that, but I've been learning a ton. In particular, while I still haven't got a fully functioning mailman3 server yet, someone pointed me, off list, to Ansible, which I wasn't aware of before and which has completely blown me away by its power and simplicity. For those who aren't aware of it, it's an agentless, multi-platform automation technology. For our purposes, it replaces "how to install mailman3" guides with a single script that aims to actually do the entire thing for you. One of the particularly interesting points is that you can write complex scripts/data structures (or 'collections') that allow for a single collection to cover a broad range of use cases, such as [this person's](https://github.com/rivimey/) exim Ansible collection, which covers 3 very different use cases from a private domain email relay up to a full multi-domain email handler with IMAP integration. I haven't quite got the mailman3 one working yet, but I've just started playing with it. Here are some pointers in case anyone else is interested in trying, and I'd be very interested in whether or not I'm actually the last person to discover this technology, and if one of these solutions succeeds in delivering mailman3 "out of the box". 1. [Install Ainsible](https://docs.ansible.com/ansible/latest/installation_guide/intro_…, make sure you're on at least version 2.9, if not 2.10. Some distributions are still on 2.7, which is not compatible with more recent collections. The "Galaxy" collection is apparently only tested on Debian 10. 2. Pick your mailman3 Ansible collection of choice and install it (https://galaxy.ansible.com/ucr/mailman3, or https://github.com/rivimey/ansible-mailman3) Command to install official collection - ansible-galaxy install ucr.mailman3 3. Write playbook.yml with key variables (mailman3 example below) _________________________ mailman3-playbook.yml _________________________ - hosts: mailman3 vars: mailman3_domain: example.com # It will install and create a certificate using certbot, its nignx plugin and http validation (Public IP required). If false, it will install a self sign cert mailman3_install_certbot: true # install and create certificate # secrets, please change them mailman3_secret_key: "change_secretkey" mailman3_rest_api_pass: "change_api_pass" mailman3_archiver_key: "change_archiver_key" mailman3_db_pass: "change_db_pass" mailman3_web_db_pass: "change_web_db_pass" mailman3_web_admin_pass: "change_web_admin_pass" roles: - ucr.mailman3

4 years, 8 months

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

by Mohsen Masoudfar

Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years

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

by Markus Grandpré

Thank you very much for your answer. Best regards, Markus Am 19.09.24 um 22:03 schrieb Mark Sapiro: > On 9/19/24 05:46, Markus Grandpré wrote: >> Dear list, >> >> I would like to activate the invitation setting for all lists as >> default. In Mailman 2.1 I have done this in the file </etc/mailman/ >> mm_cfg.py>: >> >> >> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >> >> >> How can I do this in Mailman 3? > > There is a draft merge request at https://gitlab.com/mailman/ > postorius/-/merge_requests/930 which implements a framework for setting > Postorius defaults and creates a setting to set the default for pre- > verified on the mass subscription page. Once merged, this can easily be > extended to provide a default for Invitation. > > In the mean time, you can only do this by patching src/postorius/forms/ > list_forms.py like > ``` > --- a/src/postorius/forms/list_forms.py > +++ b/src/postorius/forms/list_forms.py > @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): > > invitation = forms.BooleanField( > label=_('Invitation'), > - initial=False, > + initial=True, > required=False, > help_text=_( > 'If checked, the other checkboxes are ignored and the > users will ' > ``` >> Can I also transfer other default values like: >> >> ... >> DEFAULT_SERVER_LANGUAGE = 'en' >> DEFAULT_SEND_REMINDERS = 1 >> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >> DEFAULT_PRIVATE_ROSTER = 2 >> DEFAULT_ARCHIVE = Off >> DEFAULT_ARCHIVE_PRIVATE = 1 >> ... >> >> from the very same configuration file to Mailman 3? Is there a >> documentation of the default values for lists in Mailman 3? > > This is done by creating a list style with the desired defaults. See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/ > docs/styles.html for documentation of styles and see https://gitlab.com/ > mailman/example-mailman-plugin for an example of creating a plugin in > Mailman core to make a persistent style. > > There is no specific doc for the list settings. You need to look at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/ > base.py for the various settings and https://gitlab.com/mailman/ > mailman/-/blob/master/src/mailman/styles/default.py to see which default > classes are applied for various styles. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

11 months, 4 weeks

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:25 PM, Mark Dadgar <mark(a)pdc-racing.net> wrote: >>> Any thoughts on how to salvage ~20 years of list archives? >> >> >> The archives shouldn't be an issue. I don't think they are involved in >> the corruption, but anyway, hopefully you still have the archive mbox >> you imported. Then for the messages since then, you should be able to >> get a mbox from hyperkitty with something like >> >> https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… >> >> with the obvious substitutions and appropriate start and end dates. >> >> The list is trickier. If you are going to start over with a clean >> install, and if you have a config.pck that you imported from MM 2.1, I >> suggest the following: >> >> Use the `mailman members` command to get a list of all members. Then >> depending on how much work you want to do, also get separate lists of >> plaintext and mime digest members and members with delivery disabled. >> >> Then on the new install, import the config.pck with `mailman import21` >> and import the archive mboxes with hyperkitty_import. >> >> Run `mailman members --sync` with the full current membership list, and >> record the [ADD]s. Then you can match the [ADD]s against the plain and >> mime digest members and those with delivery disabled and set their options. >> >> That's a lot to do, but it should get you close. > > I would probably be satisfied with just exporting the current list of member email addresses + names and letting people go back and change their list settings to switch to digest, etc. if necessary. > >> On the other hand, if you can wait, we might be able to figure out how >> to fix this, and it's even possible the underlying issue isn't database >> corruption. > > > Sure - I can wait. Thank you. I am probably going to go ahead with the list wipe and recreate in the next couple of days. Lack of access to the administration stuff is starting to become a problem. Sigh. So far, migrating from sqlite3 to postgres is looking like a bit of a bust. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: Question about message bounce stats

by Abhilash Raj

> On Aug 30, 2021, at 11:27 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Ruth Ivimey-Cook writes: > >> If Abhilash has a starting point, > > IIRC it was quite primitive, and probably not at the the individual > message level, more like list level. We do keep a bounce score for Member (email, mailinglist pair) that is right now only available in Mailman’s database and is used for the purposes of un-subscriptions or disabling delivery. We haven’t had a chance to expose these values through REST API, but it is something I’d be happy to accept a patch for and isn’t too difficult if someone wants to pick up the task. It might be helpful at some point to expose some of those stats to the list owner or site admin as well in Postorius. > >> and there is acceptance from others to integrate something of this >> sort, then I could possibly help make it happen. > > If you're that interested, I'd say get started, at least on sketching > out requirements. There will probably be some nitpicking about code > style and the like, and there may be delays in integrating stuff due > to the peanut gallery contributing requirements that we decide we want > in the feature, but I don't think there's a problem with the basic > idea. Yep, +1. It would be good to first figure out what more stats do we need/want and if they just need to be exposed through the API or we need to setup some offline setup for calculating those metrics with some mechanism and then expose. > > We won't be putting tracking pixels and the like in outgoing posts, > but as long as it's internal data already generated by normal Mailman > operation, I would be somewhere between very surprised and shocked > (SHOCKED, I tell you!) if it weren't accepted. Yeah, anything that is possible to generate with regular Mailman operation is already possible for a site admin to get from logs with some scripting. So, the idea to expose them in a better UX I guess should be okay. Only thing we might want to consider is how much of that data is exposed to non-server-admins (list owners, mods etc) and the policy enforcement for that if users don’t like the default. -- thanks, Abhilash Raj (maxking)

4 years

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

by Allan Hansen

Once this gets handled, Mohsen, Google has another issue with list servers: If a subscriber who uses GMail posts a message to a list, then that subscriber will not get his/her own message from the server - Google eats it. All other subscribers will get it, but not the author. My subscribers run into this all the time and are up in arms over it. I tell them to complain to Google. Yours, Allan On 9/5/23, 13:18, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com <mailto:xxxx@gmail.com>>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/WZY5IC3OVHVBHIGDT4TE3EWSSGMF6CYI/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years

[MM3-users] Re: rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid

by Kyriakos Terzopoulos

Hi Steve, I'll check runq and let you know. As for the spaces it was just a copy/paste fail from my part since I want to obfuscate the true domain name. *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Wed, 25 Oct 2023 at 20:29, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Kyriakos Terzopoulos writes: > > > No more mail being marked as spam. However I face a (hopefully) new > > problem now. When I mass subscribe the users, they get an initial > > invitation email. However after replying I get this in the exim > > logs, the subsequent mails do not arrive and the users are not > > verified at all: > > > > 2023-10-25 13:36:41 1qvbFh-001kcb-Ig <= myname(a)myproject.eu > > H=localhost (webmail.myproject.eu) [127.0.0.1] P=esmtpa > > A=dovecot_login: myname(a)myproject.eu S=1726 > > id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu > > 2023-10-25 13:36:41 1qvbFh-001kcb-Ig == partners(a)myproject.eu > > < > partners-confirm+6df62cd0f805b2b66b21a43a42ec8ee77487e8ad(a)myproject.eu> > > R=mailman3_router T=mailman3_transport defer (-54): > > retry time not reached for any host for ' myproject.eu' > > It looks like 'myname' has replied to the invitation, and was received > by this MTA (is it Mailman's MTA?). Then delivery to Mailman was > deferred because delivery to ' myproject.eu' has failed, and Exim is > queueing them for future delivery, until the next retry time. Try > using 'runq' then checking the log to see why mail is failing in the > first place. > > I do not understand why there are spaces before the host name in these > lines: > > > id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu > > retry time not reached for any host for ' myproject.eu' > > The first never happens in my Exim instance. (I have no instances of > "retry time not reached" at all in my logs.) That suggests a > misconfiguration, in Exim, in Mailman, or Postorius. You should check > the mailman3_router and the mailman3_transport first because they're > easier. > > Steve > >

1 year, 10 months

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Mark Sapiro

On 4/7/23 14:58, Dave Hall via Mailman-users wrote: > On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 4/7/23 13:43, Odhiambo Washington wrote: >>> On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < >>> as2020+github(a)fam.tuwien.ac.at> wrote: >>>> >>>> I am running MM2 und 3 in parallel without problems, I do have a >>>> special MTA setup though (Sendmail). Can't speak for Postfix etc.. >>>> >>> >>> Your setup can handle list1(a)domain1.name via MM2 and MM3, >> simultaneously, >>> right? :-) >> >> It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` >> simultaneously on the same server, but what is the MTA going to do with >> incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to >> both MM2 and MM3, but I don't see any practical use case for this. >> >> I run Exim4 on my servers so I can comment from this perspective. Exim > had a concept of 'routers' which are stacked and processed in order of > appearance. There is a router for MM2 and one for MM3 that pick off > incoming mail based on whether the email address matches a list name. WIth > this setup, you could have the same list name in both MM2 and MM3, but it > would go to whichever router appears first and the second one would never > see it. So I have the MM3 router first, and as I migrate my lists from > MM3 the email for those lists no longer gets to MM2. And mail.python.org which currently has 189 Mailman 3 lists and 223 Mailman 2.1 lists does something very similar in it's Postfix configuration and also prefers Mailman 3. However, maybe I misunderstood Odiambo's question about simultaneous support for a Mailman 2.1 and Mailman 3 list of the same name. We could certainly have that on mail.python.org, and even have both MM 2.1 and MM 3 web UIs for those lists, but as soon as the MM 3 list is created during migration, mail is only delivered to the MM 3 list. -- 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: ARC

by Marvin Gülker

Am 15. August 2019 um 02:08 Uhr +0900 schrieb Stephen J. Turnbull: > That doesn't help you one bit with your "rejection with no reason" > problem, though. It helps you with one specific reason (DMARC > p=reject). I don't have that problem anymore since I pay for my SMTP relay provider. For me, the issue is solved. Before my personal mail (I'm not talking about mailing lists, just simple direct e-mail) was pretty much always sorted into the recipient's spam folder or directly rejected at the SMTP level (this was the case with both Microsoft and AOL; GMail usually filed my e-mail als spam). I looked up the reasons they gave in the SMTP reject; it was always bad reputation of IPs. Tools like mail-tester on the other hand say my e-mail and IP was fine, and delivery to small providers always went nicely. My mail server has never sent a single spam e-mail. I run it since years, and I am very sure that this never has happened. This mail server only hosts my and my family's e-mail. I have no AOL contacts anymore, so I left that is it was. For Microsoft (i.e. outlook.com) I went through their IP unblocking formula (which at the time contained a CAPTCHA that I'm sure a computer could solve better than me simple human) multiple times, and I received "conditionally mitigated" as a response each time. After a few months, the rejections would start again. Thus, I say they were rejecting my e-mail for no reason. Might be a hyperbole, but from my point of view, there was no reason. Again, the problem is now past with my workaround, so there is no need to investigate any further. I've given up on it. I don't believe you can have a VPS that directly delivers e-mail to the large providers successfully. The workaround with the SMTP relay provider still allows me to self-host, which fulfills my needs. > The answer to that is "why shouldn't they?" I hope it goes like that. > I've never had a problem with any of the big services. There are > reasons why some hosts might have problems due to no misbehavior of > their own, and they wouldn't necessarily know about them either. But > mostly the mail does go through. Lucky you. My experience was the complete contrary, and it's not just me. Take a look: <https://lobste.rs/s/lvajly/google_is_eating_our_mail> > If the mail itself gets through, I see no reason why they wouldn't > trust your ARC fields, so you won't get DMARC rejections, as long as > nobody downstream of you breaks your ARC signatures. So, my situation currently is this. I have no (public) mailing lists on my own mail server, so there is no need for DMARC or ARC. Then, I'm involved in an open-source project that does have a mailing list and I'm considering to add ARC support for the list (one of the reasons why I constantly read this very mailing list). The project is small, so we'd like to avoid any effort that is fruitless anyway. Finally, I moderate the German ruby-de mailing list without any kind of influence on the software stack running it. That mailing list server runs Mailman 2.1.15 and this is not something I have any influence on. All of these list servers currently do not do ARC, hence I've not seen any rejections of ARC-signed messages (as there are none). I'm only evaluating how likely it'd be to see them. Please don't get me wrong; I appreciate all the effort that went into ARC! It looks like a good solution to the DMARC problems. > If you're seeing something different (ARC-authenticated messages > getting rejected for DMARC alignment failure), let us know and I'll > talk to a guy who knows this gal. This is a nice move. Thank you for this offer. When that happens, I'm going to post here! > But the day-to-day tuning of algorithms is targeted at users with > mailboxes, not the lists that fill those mailboxes. I am aware of that. See, when DMARC was spread over the world, ARC was not available. Even the Mailman wiki itself said and still says that DMARC has "negative consequences for mailing lists" and is "breaking long established mailing list norms, standards, and behaviors."[1] The problem still exists. On the ruby-de mailing list I moderate, there was a problem with a person sending e-mail from a p=reject domain to the list[2] (which is, remember, run by Mailman 2.1.15). Two subscribers were force-unsubscribed for the DMARC bounces. I had to manually re-subscribe them and had to explain the p=reject problem to the person sending the e-mails. This was... frustrating. And I think my statements on DMARC show my frustration. > Last I heard the Google folks and the IETF are very happy with ARC. I appreciate it. I hope it solves these problems. It's just that I'm reluctant to believe there's a quick solution available. It sounds to good to be true. > > because it is simply unfeasable to manually maintain a list of all > > open-source project mailing lists in the entire world. I could set > > a new one up tomorrow, how should you know? > > That's not how this works. I'm afraid it does. Fastmail does it exactly like that: manual white list, see <https://www.fastmail.com/help/technical/senderauthentication.html>. Quote of the relevant passage: > Until the list of ARC enabled forwarders grows we maintain lists of > known good email forwarders and mailing lists, which we use to > whitelist known-good mail forwarders, and apply this list when > evaluating DMARC policies for inbound mail. To do them justice, they say a little further down that a failed DMARC check at a p=reject policy domain does not cause an actual reject, but only increases the spam score. What worries me is that other providers might go that whitelisting approach, but don't follow the second part and still obey p=reject. If everything goes well, nobody is going to do that and ARC is successful. I'm all in for that result, but I lack the knowledge to judge what is likely and what not. Which is why I'm asking here. From your answer, I see that you think such behaviour is unlikely. That's good news, and it answers my question. Thanks! [1] https://wiki.list.org/DEV/DMARC [2] See July archive: https://lists.ruby-lang.org/pipermail/ruby-de/2019-July/thread.html -- Blog: https://mg.guelker.eu

6 years, 1 month

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Odhiambo Washington

The virtualenv documentation works just fine with Bookworm AFAICT. I didn't need to do anything out of the documentation in my test VM. On Tue, 27 Jun 2023, 18:04 Eggert Ehmke via Mailman-users, < mailman-users(a)mailman3.org> wrote: > Hello Mark, > > thank you. I did change that entries, and now my mailman runs fine on > Debian Bookworm. > > I did a complete reinstall of the venv directory to have a clean start. > Maybe this was not > needed. What's missing in the documentation: > -the directiories web/logs have to be created manually with the ownership > mailman. > -The debian package pkg-config must be installed. > -the package psycopg2-binary can/must be installed without version > restriction on > Bookworm > Maybe this info helps some other people. > > Cheers, Eggert > > Am Montag, 26. Juni 2023, 22:22:37 CEST schrieb Mark Sapiro: > > On 6/26/23 12:35 PM, Ken Alker wrote: > > > I'm brand new to this, so take this with a grain of sale, but, I had a > > > similar problem a few days ago, however, mine was "flufl.i18n>=3.2". > > > Perhaps the same thing is happening with flufl.lock (but that didn't > bite > > > me). > > > > > > I solved my problem by following this: > > > <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately > > > modifying > > > > "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires. > > > txt" per that thread (see > > > <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by > > > Thomas Ward section called "The WORKAROUND"). Maybe you need to do the > > > same thing, but for flufl.lock. > > Yes, the same issue now affects flufl.lock as well as flufl.i18n. You > > will need to change both flufl.lock->flufl_lock and > flufl.i18n->flufl_i18n. > > > > ___________________________________________ > Mailman's content filtering has removed the > following MIME parts from this message. > > Replaced multipart/alternative part with first alternative. > _______________________________________________ > 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 odhiambo(a)gmail.com >

2 years, 2 months

[MM3-users] Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Jonas Meurer: > Abhilash Raj: >> On Mon, Jan 28, 2019, at 2:39 PM, Jonas Meurer wrote: >>> Abhilash Raj: >>>> On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: >>>>> Hey Abhilash, >>>>> >>>>> Thanks a lot for your work on mailman3! >>>>> >>>>> Abhilash Raj: >>>>>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. >>>>>> >>>>>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that >>>>>> I can think of is non-member management in Postorius. >>>>>> >>>>>> New releases are available on PyPI[3][4]. >>>>> >>>>> For earlier releases, you provided GnuPG signature files to >>>>> cryptographically verify that the release files were not tampered with. >>>>> >>>>> I couldn't find such signature files for the two latest releases. Would >>>>> you mind adding them? When packaging for Debian, I prefer to check the >>>>> GnuPG signatures before uploading new releases. Also, the signature >>>>> files get uploaded to the Debian archive as well so they can be checked >>>>> by everybody. That way we can cryptographically proof that the Debian >>>>> package is based on the original tarball that got packaged and signed by >>>>> upstream. >>>> >>>> >>>> Ah, sorry about that. I completely forgot about that. >>>> >>>> I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. >>> >>> Thanks a lot, that would be awesome. I'll wait for it before doing the >>> Debian package uploads. >> >> If it is not possible to upload signatures, I'll bump up patch versions >> and push out new tarballs with signatures. > > Perfect, thanks a lot! For the record: Abhilash released mailmanclient 3.2.2 and postorius 1.2.4 with tarball signatures in the meantime. Thanks a lot for doing this, Abhilash! Both are uploaded to Debian already. Cheers jonas

6 years, 7 months

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

by Mark Sapiro

On 1/16/23 18:55, 朱超 wrote: > Hi, When I subscribe the email list in Subscription Policy is confirm, Some problems happen in here： > 1.Some mail mua reject send the confirm the message, because the length of recipient is too long. for exmaple: requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, and the mail mua reject to modify about this. The default English template says in part: Before you can start using GNU Mailman at this site, you must first confirm that this is your email address. You can do this by replying to this message. Or you should include the following line -- and only the following line -- in a message to $request_email: confirm $token I.e. It gives an alternative method if `reply` doesn't work. You can provide a custom version of this template with different wording if you think you can improve it. > 2.It is inconvenient for users to use. Many people will mistakenly think that after clicking the subscribe button, it will be successful, and they will not process the email. If you set Subscription Policy to Confirm, you are saying that the user must confirm that that is their email address. This requires sending an email requesting confirmation to that address. If you don't want that step, you can set Subscription Policy to Open, but then anyone can maliciously subscribe third parties to the list. > Regarding the discussion on the subscription method of the mailing list, should we consider optimizing the subscription method of the mailing list, for example: > 1. use the method of sending a verification code to subscribe by email，When you receive the verification code sent by the mailing list and fill it in again, you can subscribe successfully。 How is this different from the present method. If you want, you can make a custom template and include something like: Alternatively, you can confirm by going to the URL https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token We don't include that in the default template because Mailman core doesn't know if you even have a web UI or how to access it if you do. > 2. use the email to send a connection to confirm the subscription，People click the link to be redirected to a confirmation page to subscribe to the email。 See above. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users]Installation issues

by Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST)

Hi folks I was speaking to someone last night on the IRC chat room @ http://webchat.freenode.net/ who suggested sending an email to this address to try and find a solution to my issues. I have been trying to get Mailman 3 installed on an Ubuntu 14.04 server. I thought I had followed the instructions from https://wiki.list.org/DEV/Mailman%203.0/Mailman%203.0%20Suite%20Install%20o… and http://mailman-bundler.readthedocs.org/en/latest/ but am getting an error 500 when I try and browse to http://x.x.x.x:8000/mailman3. I can open http://x.x.x.x:8000/archives and the login button seems to work, but when I click manage lists I get an error 500 again. The entire process I followed is below: * sudo apt-get update * sudo apt-get install git python3-dev python3-pip python-dev python-pip python-virtualenv * sudo apt-get install nodejs npm * sudo npm install -g less * sudo ln -s /usr/bin/nodejs /usr/bin/node * created new user 'mailmanuser' * 'mkdir /opt/mailman' * 'sudo chown mailmanuser:mailmanuser mailman' * 'su mailman' * 'cd /opt/mailman' * git clone https://gitlab.com/mailman/mailman-bundler.git * virtualenv -p /usr/lib/python2.7 venv * source venv/bin/activate * changed password in mailman_web/testing.py * cd mailman-bundler * pip install zc.buildout * buildout * sudo apt-get install ruby-sass * ./bin/mailman-post-update * ./bin/mailman-web-django-admin createsuperuser * ./bin/mailman start * ./bin/mailman-web-django-admin runserver 0.0.0.0:8000 I have attached the django and mailman logs and the top of the page I get back from the server I must have missed something but I don't really know where to go from here... Please can you review and advise if there is anything that I have missed? I look forward to hearing from you in due course. Any pointers greatly received. Kind regards Simon ******************************************************************************************************************** This message may contain confidential information. If you are not the intended recipient please inform the sender that you have received the message in error before deleting it. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Thank you for your co-operation. NHSmail is the secure email and directory service available for all NHS staff in England and Scotland NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and GSi recipients NHSmail provides an email address for your career in the NHS and can be accessed anywhere ********************************************************************************************************************

9 years, 4 months

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

by Mark Sapiro

On 10/23/24 23:36, vogt(a)spamcop.net wrote: > > I have tried anything I could think of but I cannot reproduce the issue using curl as user mailman (or any other for that matter) > > Going directly for localhost:8000, using some or all of the headers I can capture with tcpdump: > > ``` > $ curl -v -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… > ``` > > as well as going through the local httpd: > > ``` > $ curl -v --http1.1 -H 'Accept-Encoding: gzip, deflate' -H 'Connection: Keep-Alive' -H 'Host: lists.example.org' -A 'python-requests/2.32.3' https://lists.example.org/mailman3/api/templates/list/community.lists.examp… > ``` > > Running tcpdump during those runs shows me it's sending the same headers as mailman does. Thus on http protocol level it's the same, but still the server returns immediately. > > What I have just noticed is that the Date header in the delayed response is the "late" time. I have even compared tcp headers from either capture. They look identical down to the frame sizes. > > The only difference the last times is that with curl, the server side sends the ACK for the request and milliseconds later a PSH,ACK with the response headers. When it comes internally from mailman it sends the ACK for the request and then 5 seconds later it sends the PSH,ACK with the response headers. I'm unable to explain what's going on. You could try one more thing in an attempt to duplicate this outside of Mailman. Invoke the same python3 that Mailman does - this may be in a venv or the system python3. If in a venv, you don't need to activate the venv, just run venv/bin/python. Then in response to Python's prompts do ``` >>> import requests >>> res = requests.get('https://lists.example.org/mailman3/api/templates/list/community.lists.examp…', timeout=5) ``` and see what that does? I think it should time out because this is exactly what Mailman core is doing tho get the template, and if it does, perhaps you can determine why from this simple example. -- 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: Timeout error on anonymous subscribe

by Gerald Vogt

On 24.10.24 22:09, Mark Sapiro wrote: > On 10/23/24 23:36, vogt(a)spamcop.net wrote: >> The only difference the last times is that with curl, the server side >> sends the ACK for the request and milliseconds later a PSH,ACK with >> the response headers. When it comes internally from mailman it sends >> the ACK for the request and then 5 seconds later it sends the PSH,ACK >> with the response headers. > > I'm unable to explain what's going on. You could try one more thing in > an attempt to duplicate this outside of Mailman. Invoke the same python3 > that Mailman does - this may be in a venv or the system python3. If in a > venv, you don't need to activate the venv, just run venv/bin/python. > > Then in response to Python's prompts do > ``` > >>> import requests > >>> res = requests.get('https://lists.example.org/mailman3/api/ > templates/list/community.lists.example.com/list:user:action:subscribe', > timeout=5) > ``` > and see what that does? I think it should time out because this is > exactly what Mailman core is doing tho get the template, and if it does, > perhaps you can determine why from this simple example. I have tried it using the fqdn url as well as the localhost:8000 url but in both cases requests.get immediately returns the response. The server side pushes the response within milliseconds. But that made me looking another time at the localhost tcpdump: I have noticed two connections to localhost:8000 where gunicorn with mailman_web.wsgi:application is running. The first one is POST /mailman3/lists/community.lists.example.com/anonymous_subscribe the second one is GET /mailman3/api/templates/list/community.lists.example.com/list:user:action:subscribe Both take 5 seconds. First the first one responds then shortly after the second one. I have noticed that only two gunicorn processes are running which looked like only one is a worker. Thus I have added workers=9 (2xncore+1) to /etc/mailman3/gunicorn.conf and restarted mailmanweb.service. Now it's working. So it must have been some kind of deadlock situation because it only had a single worker running. I have just followed the docs from https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-guni… which doesn't mention anything about workers and I seriously don't have a clue about gunicorn. Maybe that could be added to the docs? Thanks for the help! Cheers, Gerald

10 months, 3 weeks

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

by Jeremy Stanley

On 2023-02-15 18:35:35 -0800 (-0800), Mark Sapiro wrote: > On 2/15/23 07:52, Jeremy Stanley wrote: > > > > Thanks, I'm still doing my best to wrap my brain around how Django > > uses database migrations to create sites (seems like a very strange > > use of a migration, I'm only accustomed to seeing them applied for > > database schema updates). > > I don't think it does. There are a couple of migrations at > django/contrib/sites/migrations, but these are only the initial creation of > the model and an update to make the domain field unique. > > Why do you think it creates sites in this way. [...] Clearly a total misreading on my part of the Django documentation to which you referred earlier. It talks about having to feed Django multiple settings.py files with different SITE_ID values and running migrate to configure them, then links to the document on migrations which starts out explaining how to use makemigrations to create them. I took that to mean creating and configuring Django sites from the command line required supplying customized database migrations. The particularly misleading bits are where it says: "To set the correct name and domain for your project, you can use a data migration." "In order to serve different sites in production, you’d create a separate settings file with each SITE_ID" It doesn't seem to talk about using django_admin at all (or if it does, it's not mentioned by name, maybe assuming the reader knows to use it in order to perform the necessary steps). Thanks for the clear examples! If these are available somewhere in Django's documentation, I did a terrible job of searching for them. > you need to create a domain in Postorius. Look at the code behind > Postorius add new domain. Or you can create the domain in core via > REST, but you then have to modify it in Postorius to associate the > correct site. [...] Much appreciated, this was the other bit that was non-obvious to me. I guess you're saying Postorius's view of domains is independent from what's in Mailman Core, and there's no documented CLI/API for manipulating that in Postorius so I'll need to write one based on a reverse-engineering of its source code? Sounds doable now that I know where to look. Thanks again! -- Jeremy Stanley

2 years, 7 months

[MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors

by Willie Castillo

I saw them. OK, I must be missing several steps. I'll have to start from scratch. Let me carefully follow the link you send me, it should work for Almalinux 9.4 right? We recommend installing Pypi packages in a virtualenv. Doc is at https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/virt… [cid:92ffd146-5b65-4e46-a2f8-021ea40371e9] Willie Castillo Linux Systems Administrator, IT Department - Defense & Security CAE USA T. +1-813-885-7481 E. Willie.Castillo(a)caemilusa.com A. 4908 Tampa West Blvd, Tampa, Fl. 33634 cae.com CONFIDENTIALITY NOTICE This e-mail message is intended only for the above named recipient(s) and may contain information that is confidential. If you have received this message in error or are not the named recipient(s), please immediately notify the sender, delete this e-mail message without making a copy and do not disclose or relay this e-mail message to anyone. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, July 18, 2024 2:55 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors [You don't often get email from mark(a)msapiro.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] 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 7/18/24 11:12 AM, willie.castillo(a)caemilusa.com wrote: > Mark first let me thank you for your assistance with this. I don't believe I mentioned that this is a fresh/new installation I'm performing on an AlmaLinux 9.4 VM. I have searched everywhere for a solid Mailman installation on AlmaLinux document/process but, I haven't had any luck. I tried following documentation on this site and I only found this https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/dist… . Did you see my post at https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… We recommend installing Pypi packages in a virtualenv. Doc is at https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/virt… -- 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://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Outlook-2rvyqd2h.png Replaced multipart/alternative part with first alternative.

1 year, 1 month

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

by Mark London

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. When I go to the Django interface, I don't see them listed in any selection. I thought they would show up under Emails in Hyperkitty, but they are not there. Oddly, somehow I've managed to create multiple duplicates of the same address, under Emails. Figure that one out! Thanks. - Mark 21 mrl(a)psfc.mit.edu April 25, 2023, 4:54 a.m. [Mark] afasdfa mark.lists1.psfc.mit.edu 20 mailman(a)psfc.mit.edu April 25, 2023, 4:44 a.m. [Mark] Re: tet mark.lists1.psfc.mit.edu 19 london(a)mit.edu April 25, 2023, 4:31 a.m. [Mark] tet mark.lists1.psfc.mit.edu 18 mrl(a)psfc.mit.edu April 25, 2023, 3:28 a.m. [Mark] test mark.lists1.psfc.mit.edu 17 mailman(a)psfc.mit.edu April 25, 2023, 3:27 a.m. [Mark] tet mark.lists1.psfc.mit.edu 16 mailman(a)psfc.mit.edu April 25, 2023, 3:22 a.m. [Mark] Re: foobar mark.lists1.psfc.mit.edu 15 mrl(a)psfc.mit.edu April 25, 2023, 3:21 a.m. [Mark] test mark.lists1.psfc.mit.edu 14 mrl(a)psfc.mit.edu April 25, 2023, 2:05 a.m. [Mark] ;jklj mark.lists1.psfc.mit.edu 13 mrl(a)psfc.mit.edu April 25, 2023, 1:53 a.m. [Mark] foobar mark.lists1.psfc.mit.edu 12 mrl(a)psfc.mit.edu April 25, 2023, 1:52 a.m. [Mark] test mark.lists1.psfc.mit.edu 11 mailman(a)psfc.mit.edu April 25, 2023, 1:51 a.m. [Mark] Re: test mark.lists1.psfc.mit.edu 10 mrl(a)psfc.mit.edu April 25, 2023, 1:42 a.m. [Mark] test mark.lists1.psfc.mit.edu 9 mrl(a)psfc.mit.edu April 25, 2023, 1:38 a.m. [Mark] test mark.lists1.psfc.mit.edu 8 mrl(a)psfc.mit.edu April 25, 2023, 1:40 a.m. [Mark] test mark.lists1.psfc.mit.edu 7 mailman(a)psfc.mit.edu April 25, 2023, 1:33 a.m. [Mark] foobar mark.lists1.psfc.mit.edu 6 mailman(a)psfc.mit.edu April 25, 2023, 1:32 a.m. [Mark] test mark.lists1.psfc.mit.edu 5 root(a)psfc.mit.edu April 25, 2023, 1:21 a.m. [Mark] foobar mark.lists1.psfc.mit.edu 4 root(a)psfc.mit.edu April 25, 2023, 1:20 a.m. [Mark] test mark.lists1.psfc.mit.edu 3 root(a)psfc.mit.edu April 25, 2023, 1:11 a.m. [Mark] test mark.lists1.psfc.mit.edu 2 root(a)psfc.mit.edu April 25, 2023, 1:14 a.m. [Mark] test mark.lists1.psfc.mit.edu 1 mailman(a)psfc.mit.edu April 25, 2023, 1:22 a.m. [Mark] test mark.lists1.psfc.mit.edu

2 years, 4 months

[MM3-users] Re: Mailman web Stopped working after upgrade

by David Krantz

Hi, I tried psycopg2-binary and a few other rehashes of that. Now I got it working by downloading the source for psycopg2 manually and building it myself, then I installed it into my venv like any other self-built package. https://pypi.org/project/psycopg2/#files I run mod_wsgi in Apache so I thought it should be enough to restart Apache. I am quite convinced that I did that (and for that matter restart the machine at a few points). But I might have been sloppy and reversed the order in the end when I got it running, this process is a bit to manual. I will use another solution when I rebuild the server one day. The problem with rebuilding the server is that I'd have to install a MTA with all its modules, milters, setups and what not, and mailman. To just reinstall on a fresh machine would be easy, the trick is that I want to rebuild some things in a better way which will take me some time. E.g. using a separate wsgi service and a more modern spam filter than Spamassassin. Otherwise it is easy. But my situation now is a bit short on time so if I can postpone that a bit I will. Thanks. // David // David On Tue, Mar 3, 2020 at 10:02 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/3/20 12:33 PM, David Krantz wrote: > > > > I think that this might be due to some kind of python misfeature where > > compiled code behaves slightly differently to interpreted code, that > > might explain the delay in it working initially before breaking. I > > have no idea of how to solve this. I have tried to uninstall and > > reinstlall psycopg2 in different versions without any luck. > > You need to activate your virtualenv and do > > pip install psycopg2-binary > > it must be psycopg2-binary, not just psycopg2. It's probably best to do > > pip uninstall psycopg2 > > first. > > As far as it working for a while, did you restart your wsgi service > (gunicorn, uwsgi, ??) after upgrading? > > -- > 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/

5 years, 6 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' This looks good to me. > > What should I use in user and password?? Does Django use postfix to send the email??? I think you don't need a password and username as long as your postfix is configured to relay local emails without authentication (which it is by default if you installed from distro packages and if you haven't changed the settings). > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió:>> Hi, >> >> >> >> On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: >> > It's ok now, but still I can't make it send the confirmation email>> > >> > This is from mailman.log: >> > >> > >> > [mailman@localhost logs]$ tail -f mailman.log >> > Aug 01 15:59:18 2017 (2327) lmtp runner started. >> > Aug 01 15:59:18 2017 (2333) virgin runner started. >> > Aug 01 15:59:18 2017 (2332) retry runner started. >> > Aug 01 15:59:18 2017 (2330) pipeline runner started. >> > Aug 01 15:59:18 2017 (2325) command runner started. >> > Aug 01 15:59:19 2017 (2328) nntp runner started. >> > Aug 01 15:59:19 2017 (2326) in runner started. >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET >> > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET >> > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 >> > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200>> > 90 >> > >> > >> > >> > >> > What should I do? >> >> If you are talking about Account confirmation emails, they usually are>> sent out from Django and not Mailman Core itself. >> >> To configure Django you need to edit the `settings.py` file, wherever>> that is one your installation. If you are following the guide mentioned>> at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at>> `mailman-suite/mailman-suite_project/settings.py`. >> >> To configure your Django to send emails, have a look at >> http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required.>> >> That documentation page has pretty much everything you need in order to>> have a running Web Frontend, please go through it and make sure you have>> everything configured. >> >> Finally, the actual emails from Mailing lists are supposed to be handled>> by Core. You need to configure Postorius & Mailman both to communicate.>> The settings are mentioned >> http://docs.mailman3.org/en/latest/config-core.html#configuring-mta >> here. >> >> >> Hope that helps! >> >> > >> > >> > >> > >> > >> > >> > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>)>> > escribió: >> > >> > > On 8/1/17 1:14 PM, Rafael Mora wrote: >> > > > >> > > > Why does it say Address already in use? >> > > >> > > >> > > Because you are starting lm tp runner and it's already running.>> > > >> > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill>> > > any if necessary. Then do '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 >> > _______________________________________________ >> > Mailman-users mailing list >> > mailman-users(a)mailman3.org >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>> >> >> -- >> thanks, >> Abhilash Raj >> _______________________________________________ >> 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 -- thanks, Abhilash Raj

8 years, 1 month

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Mark Sapiro

On 9/21/20 10:49 AM, peterbw(a)gmail.com wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com > cc: listserv(a)lists.test.org; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com > cc: listserv(a)lists.test.org, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org, "Williams, Peter" <peters_real_address(a)example.com> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com cc: other_user(a)gmail.com; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com and other_user(a)gmail.com receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

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

by Stefan Bauer

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. Thank you. Stefan Am Mi., 18. Jan. 2023 um 18:02 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 1/17/23 23:45, Stefan Bauer wrote: > > Dear Users & Developers, > > > > we're running MM3 on Ubuntu 22 and used the venv-installation method. > > Last week we updated via¹ to > > > > Mailman Core-Version GNU Mailman 3.3.8 (Tom Sawyer) > > Mailman Core API-Version 3.1 > > Mailman Core Python-Version 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC > > 11.3.0] > > > > and now mailman attaches mime-attachments to email as text-files. That > > breaks many mails in our environment. > > > > For example: Now we have attachments like > > > > smime.p7s + ATT000001.txt as well as what looks like MM footers > > "mailing list --- test@domain ... To unsubscripbe send an email to ..." > > > > How can we get the "old" processing back? > > I doubt this has anything to do with the upgrade per se. It has to do > with MIME multipart (in this case, signed) messages and how MM > headers/footers are added. The MM 2.1 FAQ article at > <https://wiki.list.org/x/4030707> has some info on this. > > In order to say more, I would need to see the list's settings for > Filter types, Filter extensions, Pass types, Pass extensions, Collapse > alternatives and Convert html to plaintext and the complete MIME > structure of the incoming message. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to cubewerk(a)gmail.com > ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 7 months

[MM3-users] Re: Mixing Mailman 3 with AWS SES

by Andrew Hodgson

Ralph Weber <roweber(a)ieee.org> wrote: >I am moving the website www.t10.org from a private/corporate VM to AWS EC2s. >For many years, t10.org has had very happy results with using Mailman 2 for its email reflector, and I have no real concerns about moving to Mailman 3. My bugbear is the fact that I need the following mixed bag of incoming email addresses to work in concert with each other to receive and handle emails. [...] >My best guess is that the AWS Simple Email Service (SES) needs to sit in front of both Mailman and the home-grown code, to properly direct the incoming emails to the right places. The big worry is as follows... Why do you believe that is the case? In your current setup your mail server acts as primary MX, the server runs an MTA with an interface to Mailman. Why would you believe this to be different in the AWS environment? >All available evidence read to date suggests that the default AWS installation of Mailman 3 assumes that Mailman 3 is the *only* receiver of emails in the configuration. If true, then putting SES in front of Mailman could be a Herculean challenge. Which instructions are these? When I read about using Mailman on AWS, my experience is that getting email into the system is fine because AWS allows incoming connections on port 25, and so long as you have a static public IP address attached to the instance that routes traffic correctly incoming mail is fine. The challenge is with outbound mail from your server, as directly sending outbound email from AWS IP addresses is an issue because the AWS Ips are listed on many spam lists as spammers have been known to set up instances and abuse them by sending out bulk mail. Sending outbound emails via the SES service from Mailman is possible, but it comes with some caveats due to the way that SES validates email addresses on the platform. Some users have been able to get it working on this list, but have had to put the lists into an anonymous mode where the email of the sender is obfuscated so as not to trip up SES. For this reason I haven't moved my Mailman instances onto the public cloud, I instead use a VPS provider who's Ips have a good sending reputation. I am still interested in doing this work however, just need to work out the best option for sending out the email effectively. Thanks. Andrew.

4 years, 5 months

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

by David Newman

On 12/10/21 4:48 PM, Mark Sapiro wrote: > On 12/10/21 3:22 PM, David Newman wrote: >> On 12/10/21 12:57 PM, Mark Sapiro wrote: >>> >>> Are you using uwsgi or some other wsgi server. >> >> uwsgi, per the venv and PDF docs. Thanks for the fix. >> >> Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives >> replace the 'proxy_set_header' ones in the venv doc? >> >> Looking at the uwsgi doc, it seems they might do different things. > > > If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working > for you, then I'm satisfied that the docs are OK now and we don't need > to say anything about uwsgi_pass. > > > >> It's not the situation I have to deal with, though. Short of changing >> a long-standing URL, what I'm looking to do is have "/" continue to >> default to roundcubemail, and have users type in longer URLs for MM3 >> and other services. > > > I think you can set the document root to the roundcubemail root and then > set locations for the Mailman destinations as, e.g. > > location /mailman3/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /archives/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /accounts/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /admin/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /user-profile/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > > I haven't tried anything like this, so I'm not sure it will work, but I > think so. 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. Adding a stanza for 'location /mailman/' to the nginx config above clears the 404 error, but Postorius returns "Page not found" with no entry in the web or MM3 logs, and a 200 OK in the Nginx logs. I think the URL is supposed to go to the list page in Postorius. How to configure this so that list owners and moderators get a valid URL for list management? Thanks! dn

3 years, 8 months

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

by Pierre Malard

Thanks, > Le 28 avr. 2022 à 15:17, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> a écrit : > > Pierre Malard via Mailman-users writes: > >> We must add some (a lot) alias address for members and I don’t find >> any indications on doc to do that with « mailman » command. > > I have no idea what you mean by an "alias address" that can be added > for many members simultaneously. There is no concept of "alias" in > Mailman, and almost certainly no special command for this. These are authorized alternate email addresses. For example A@domain is subscribed to the Z list of which only members can contribute but we also want to authorize some other address of A (A@domain2, …) as an « alternative" email contributor. In the Mailman2 version this was called "accept_these_nonmembers" and it actually got added to that "non-members" list in mailman3. > > The general way to add a lot of addresses for a single list is the > mass add command in Postorius's users tab, or an equivalent script > using mailmanclient. If you need to do this at the user level (rather > than the subscription level), you will need to write a script for it, > and also to update subscriptions if that is what you have in mind. We would like to be able to add these "non-members" addresses with the "mailman" command line, indicating the assigned "role". But, obviously, the only available option managing the role is provided by "mailman members" which declares itself obsolete! :-( As far as the Python mailman libraries are concerned, we lack documentation. For example the possible parameters… Otherwise, working directly in the database seems dangerous to us. > > Steve > -- Pierre Malard « Je n'ai jamais séparé la République des idées de justice sociale, sans laquelle elle n'est qu'un mot » Jean Jaures - 1887 |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 4 months

[MM3-users] Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)

by Mihai Moldovan

* On 4/17/25 12:18, christian.schneider(a)tu-dortmund.de wrote: > I want to set up a new server (Ubuntu-24.04) and install Mailman-3 with the Virtualenv setup method: > https://docs.mailman3.org/en/latest/install/virtualenv.html > As I know from my old Mailman-2.1 the archives could get quite big... ;-) > So it seems very important to provide enough (expandable) disk space at the right place. > (I plan to use a seperate partition with LVM for the path in question) > > But I could find no information about the location where hyperkitty stores the archives on an Ubuntu-/Linux-system. > I assume the archives are stored underneath "/var/..." this is only a guess. > But is this guess right? Not quite. To the best of my knowledge, by default, a venv installation is fully contained under /opt/mailman, with archives and stuff stored at /opt/mailman/var/lib/... > Another question is: > How much space do I have to plan (roughly) for the "/opt"-partition for the mailman install if the archives are stored under "/var/..."? Depends on your archives, the way things are archived (you can choose different database backends, and these might make a difference in how efficiently or inefficiently data is stored) and whether you want to use the full-text search index, which adds another big chunk of data. I can give you a few pointers regarding my setup: my mailman 2.1 data directory takes up about 8.2 GB of disk space, most of which are archives, naturally (8.1 GB). I've imported most of the big archives to mailman 3 already, with a full-text search index, and that uses 5.2 GB disk space currently, but I'm still missing a few archives, so that'll still grow a bit. It will probably end up at about the same size, but I can come back to that once my import is fully done (which sadly will take a few days). Now, the 8.1 GB of mailman 2.1 archives are stored pretty inefficiently, because they are essentially duplicated (as a private mbox archive and public text archives). Mailman 3 doesn't do that - at least not directly - but instead stores archives once into the database, and queries the database whenever the archives are accessed via hyperkitty, so I would *assume* the size you need for the mailman 3 data after a successful migration is just a bit shy of what you needed for the mailman 2.1 data, maybe even a bit less. Mihai

5 months

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

by Stephen J. Turnbull

Simon Handfield via Mailman-users writes: > I have been able to identify a file in the shunt queue that threw a > matching error when I performed mailman qfile on it. > I have run a loop over all remaining files in the shunt queue and > all the remaining files can be accessed by mailman qfile without > error. Good. But there are still a bunch of problems with those files since they got shunted. > I moved this file out of the queue in the hope that I would then be > able to load the held_messages page successfully. Unfortunately I > am still seeing a 500 error on loading the page. If this is a Mailman problem, I don't understand it. The shunt queue is not the moderation queue. The shunt queue is for messages that Mailman cannot handle without throwing an exception. Once a message is sent to the shunt queue, Mailman ignores it, so it shouldn't cause problems for the moderation page. Have you tried restarting Mailman since moving the qfile? If that doesn't work, and if it's the same error message and traceback, the easy suspect is browser caching (although we should be disabling that, I hope). Try a manual refresh (usually Ctrl-R or in the menu). If that doesn't work, try a private browsing window or another browser if you don't want to clear the cache or restart the browser. > I temporarily reenabled debug logging to confirm that the same > error was being thrown. > > Assuming that file was the cause are there other steps I need to > perform in addition to removing the file from the shunt queue > directory? The only one I can think of is the check for browser-side caching. Unfortunately, Mark's out of town (like, on top of a mountain with no bars on his phone), and I am not going to be able to do much with this until Thursday at the earliest. If you do get a new traceback, post it here (somebody else may have an idea). If you like you may send me the qfile at the address in From. I'll see if I can reproduce the bug, and I'm pretty sure I can tell you what's in the file so at least you'll know whether it's important to somebody who isn't a scammer/spammer. Steve

5 years

[MM3-users] Various patches for mm3 stable 3.3.1

by Ruth Ivimey-Cook

Folks, For my own purposes I have created some patches which apply to the current mailman pip package. The first of them is for my purposes necessary, and has been discussed here before: being able to specify the address used to listen for tcp connections independently of the address the server considers it to be accessible at. A possible change to this patch would be to check whether this address was undefined but the old hostname was defined, and use that if so. For me this is not needed, and in any case it is a trivial change to make. The second patch adds a bunch of additional logging calls to various network-related parts of the package. I wrote these into the package because I was seeking the cause of template expansion causing messages to be silently dropped. I eventually found the cause was that I had an incorrect setting of the template root URL, but I regard the lack of anything in the logs as just as much of a bug. One important part of those changes was that I added a try/catch around two parts of the 'decorate' code, which is where the silent dropping occurred. If you only take one part of this patch, I encourage you to take this part. For the third patch, I discovered that the task runner was at one point busy-waiting to the tune of 100% cpu, and the cause was the way that the runner checked to see if there was work left in the queue. I am not quite sure what was the exact problem, but I think it was that there was something to do, but it was not achievable at that time, and the result was continual retry. The third patch changes the logic slightly so that this no longer occurs - retry will happen, but somewhat more gracefully. I hope you find some use in these three. Finally, I am currently experiencing problems with templates and would appreciate any thoughts: 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. 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. Regards, Ruth

4 years, 11 months

[MM3-users] Re: dedicated mailman3 list server on Ubuntu 18.04 LTS - questions after installation

by Abhilash Raj

On Sun, Aug 5, 2018, at 3:37 PM, John Seifarth via Mailman-users wrote: > My goal is to build a stable dedicated list server using mailman3. It > should use all current email authentication techniques to clearly show > that it is an authentic non-spam mail list server. In the future, I may > want to use the REST interface, so that’s why mailman2 is not an option. > > My installation: > > Installed Ubuntu 18.04 LTS server, with postfix, mysql and postgres. I > then installed mail-stack-delivery, postfix-policyd-spf-python, > OpenDKIM, and OpenDMARC. I configured SPF, DKIM, and DMARC records on my > DNS server, and then configured postfix and dovecot to DKIM sign > outgoing mail from local users, and check SPF, DMARC, and DKIM on > incoming mail. > > I then installed the package mailman3-full, which provides version > 3.1.1-9, using postgres 10 as the database. I have looked in Ubuntu > bionic-backports and bionic-updates and do not see a more recent > version. I see that version 3.2 was released in July, are debian/ubuntu > mailman 3.2 packages available somewhere? > > I set up the /etc/mailman3 files: > > I added this to the end of mailman.cfg > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /etc/mailman3/mailman-hyperkitty.cfg > > In mailman-hyperkitty.cfg I copied the api_key: value from mailman- > web.py MAILMAN_ARCHIVER_KEY, but removed the single quotes surrounding > the value in the mailman-web.py file when writing the key in the > mailman-hyperkitty.cfg file. > > I modified /etc/postfix/main.cf with this appended to the end: > # Mailman-postfix integration > owner_request_special = no > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = > hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname, $alias_maps, > hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}} > hash:/var/lib/mailman3/data/postfix_domains > > I ran /usr/share/mailman3-web/manage.py createsuperuser > I ran a2enmod proxy_uwsgi > I made a symbolic link from /etc/mailman3/apache.conf to /etc/apache2/ > conf-available/mailman3.conf, then ran a2enconf mailman3 > > I have read the documentation in /usr/share/docs/mailman3* along with > what I could find concerning mailman3 on the web. > > The installation allows me to sign into the web interface, create a > host, create mailing lists, and mass subscribe members. When members > send email to the list address, the server sends the messages normally > to the other members of the list. > > However, when I look at the list archives, there are no posts. I > deliberately mass-subscribed an invalid address, and I can see in /var/ > log/mail.log that the message bounces, but I get no notification, nor do > I see any bounce info when I look at the member info. > > My questions: > > 1) logging > > A lot of my questions would probably be answered if I could figure out > hot to activate logging correctly. Currently, I see: > > root@mailman:/var/log/mailman3# ll -R > -rw-rw---- 1 list list 0 Jul 29 20:06 bounce.log > -rw-rw---- 1 list list 0 Jul 29 20:06 debug.log > -rw-r----- 1 list list 3298 Aug 4 00:00 mailman.log > -rw-rw---- 1 list list 34606 Jul 30 17:44 smtp.log > drwxr-xr-x 2 www-data www-data 4096 Aug 3 06:25 web/ > ./web: > -rw-rw-r-- 1 www-data www-data 1520 Aug 3 06:25 mailman-web.log > > The bounce log and debug log are empty. I’ve set propagate: yes in the > [logging.debian] section > > From /etc/mailman3/mailman.cfg > # In this section, you can define defaults for all loggers, which will be > # prefixed by 'mailman.'. Use subsections to override settings for specific > # loggers. The names of the available loggers are: > # > # - archiver -- All archiver output > # - bounce -- All bounce processing logs go here > # - config -- Configuration issues > <…snip…> > > Can anyone post an example of a ‘subsection’ to set archiver and bounce > to debug? Do I have to create /var/log/mailman3/mailman.archiver.log and > set ownership to list:list? [logging.archiver] level: debug [logging.bounce] level: debug > > > 2) Where are posts stored? > > For me, this is the biggest mystery in mailman3. Local mail is delivered > to ~/Maildir by dovecot. In the $var_dir hierarchy the directory > messages contains just 2 messages dating to my initial tests. Anything I > send to a list now, and which seems to be sent properly to the member > addresses, I cannot find on the filesystem. > > Any clues as to what may be going on here? Mailman by itself doesn't store anything, it just sends and receives. $var/queue directory should have all the posts that are currently in queue and are waiting to be processed. If you are talking about Archived messages, they should be in the database. > > 3) Archival - Hyperkitty > > How does this work? All the parts seem to be in place, and I can see > from ps > /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=archive:0:1 -C / > etc/mailman3/mailman.cfg > > How can I figure out why this is not working? In the web interface, I > see that each of my lists has zero posts. But posts mailed to the list > address do appear in the list members’ mailboxes! The runner above sends posts to Hyperkitty, which is a running Django app. You should check the logs if the messages are being successfully delivered to Hyperkitty. > > 4) Bounces > > I’ve deliberately put an erroneous email address as a list member. In > postfix’s /var/log/mail.log I see the bounces, but get no notification, > and /var/log/mailman3/bounce.log remains empty. > > 5) DKIM and DMARC > > I’ve got OpenDKIM running on inet:12345@localhost and OpenDMARC running > on net:54321@localhost. > > How can I get mailman to use these milters and sign messages? How should > DMARC munging be configured when signing? > > 6) Is there an overview of how mailman3 works? > > Is there documentation which explains the path of an incoming post > through the system, including initial reception, list processing, > sending to members, processing bounces, and archiving posts? > > Thanks in advance for help and pointers to any available documentation! > > > > John Seifarth > Words & Wires SPRL > Computer Consulting & Language Services > Brussels, Belgium > _______________________________________________ > 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)

7 years, 1 month

[MM3-users]Re: Moderation Emails & Page

by Simon Hanna

> I’m running the current MM3 from the bundler on RHEL7, and most things seem to be working properly. > ERROR 2016-04-20 14:58:05,959 base 3256 140375419246336 Internal Server Error: /mailman3/lists/listname/held_messages > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 22, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/postorius/auth/decorators.py", line 77, in wrapper > return fn(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/postorius/views/list.py", line 413, in list_moderation > paginator_class=utils.MailmanPaginator) > File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 89, in paginate > results = paginator.page(1) > File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 62, in page > number = self.validate_number(number) > File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 39, in validate_number > if number > self.num_pages: > File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 86, in _get_num_pages > if self.count == 0 and not self.allow_empty_first_page: > File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 75, in _get_count > result = self.function(count=1, page=1) > File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 681, in get_held_page > return Page(self._connection, url, HeldMessage, count, page) > File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 333, in __init__ > self._create_page() > File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 363, in _create_page > self._connection, entry['self_link'], entry) > KeyError: u’self_link' This one seems to be a new one. To my knowledge held messages should not work because of this issue: https://gitlab.com/mailman/mailmanclient/issues/10 Your issue seems to be with postorius' paginator. Could you open an issue in postorius? https://gitlab.com/mailman/postorius/issues Please include this trace, and some additional info. * What version of django are you using? * What version of postorius are you using? * What version of mailmanclient are you using? To actually confirm the issue is with postorius and not mailmanclient, you could try to access the held messages through mailmanclient directly The easiest way to do this, is start a django shell. You need to activate the python2 virtualenv for this Replace manage.py with whatever command you use to start the webserver python manage.py shell from postorius.utils import get_client lists = get_client().lists lists[0].held # pick a list that has held messages lists[0].get_held_page() # and you could try getting one specific message lists[0].get_held_message(<held id>) if you can do all this, then the issue is probably in postorius

9 years, 4 months

[MM3-users] OperationalError: database is locked

by cyp＠trojina.si

On our installation, we are often gettting Internal Server Error (500). The logs look like this: ERROR 2018-01-09 13:52:57,640 1604 django.request Internal Server Error: /hyperkitty/list/test(a)seznami.cjvt.si/ Traceback (most recent call last): File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/exception.py", line 42, in inner response = get_response(request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/HyperKitty-1.1.0-py2.7.egg/hyperkitty/lib/view_helpers.py", line 133, in inner mlist = MailingList.objects.get(name=mlist_fqdn) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 379, in get num = len(clone) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 238, in __len__ self._fetch_all() File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 1087, in _fetch_all self._result_cache = list(self.iterator()) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/query.py", line 54, in __iter__ results = compiler.execute_sql() File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/models/sql/compiler.py", line 835, in execute_sql cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/opt/mailman/venv2/local/lib/python2.7/site-packages/Django-1.10.7-py2.7.egg/django/db/backends/sqlite3/base.py", line 337, in execute return Database.Cursor.execute(self, query, params) OperationalError: database is locked Does this suggest I should switch from sqlite to postgres (https://stackoverflow.com/a/26864360)? I'm happy to do that, but how do I migrate the data between the databases (after installing postgres and creating the database)? I've found this doc (http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html#data…) but I don't think I understand this and I haven't used alembic: these instructions are just for when you modify the model within the same database, right? Thanks in advance!

7 years, 8 months

[MM3-users] rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid

by Kyriakos Terzopoulos

Hi all, I'm on the latest mailman installation in a HestiaCP server. The past few days I have been investigating some spam issues and by using dkimvalidator.com I found the following: 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list manager* 3.2 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr 1)* Note the last line on the above debug information which raises the spam score of the email. Some research showed me that I needed a rDNS entry in my server. I'm on a Hetzner cloud VM so I used the Hetzner console to change the rDNS entry from: static.XXX.XXX.XXX.XXX.clients.your-server.de to my initial server hostname for example: *hestia.myserver.com <http://hestia.myserver.com>* However, after some propagation, I found today that even though I can send email to any normal address created in the server's control panel, mailing list emails do not get sent. I see the following in the logs: Mailman SMTP log: Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> *response exception: (550, b'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'*, 'testlist-bounces+myusername=myproject.eu(a)myproject.eu') Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> smtp to testlist(a)myproject.eu for 1 recips, completed in 45.07745146751404 seconds Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> post to testlist(a)myproject.eu from testlist-confirm+07d3315fa11a75588857fc93d1832ba74fb09fdd(a)myproject.eu, 1633 bytes, 1 failures Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> delivery to myusername(a)myproject.eu failed with code 550, b*'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'* Exim4 log: 2023-10-24 14:17:47 H=([127.0.0.1]) [XXX.XXX.XXX.XXX] rejected MAIL <testlist-bounces+myusername=myproject.eu(a)myproject.eu>: *Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid* The weird thing is that when I do a mailman-web sendtestemail this email is sent successfully. Also please note that before the rDNS change I did not have an issue with mail sending. Last but not least, after some search I set in Exim4 the following: PRIMARY_HOST_NAME = *hestia.myserver.com <http://hestia.myserver.com>* Any help would be greatly appreciated. *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

1 year, 10 months

[MM3-users] Re: Archive Policy not reflecting in Hyperkitty

by Nathan Dixon

Update: I have manage to get this working. I had to delete all images in docker that were anything to do with mailman. Docker-compose rm didn't clean up enough stuff. Once there were no other mailman docker images, I then ran $ docker pull quay.io/maxking/mailman-web:0.2 $ docker pull quay.io/maxking/mailman-core:0.2 And docker-compose up didn't show any error messages relating to Hyperkitty this time and the archive policy is reflecting in Hyperkitty as it shows in Postorius. Thanks for your help Abhilash! Regards, On Mon, 13 May 2019 at 12:28, Nathan Dixon <nathan.dixon(a)evadon.com> wrote: > Hi, > I have removed the docker images and pulled the version tagged as 0.2. > > $ docker pull quay.io/maxking/mailman-web:0.2 > $ docker pull quay.io/maxking/mailman-core:0.2 > > Unfortunately I am still getting the error message when trying to run the > sync_mailman job manually: > > # python3 manage.py runjob sync_mailman > > Also running docker-compose up (without -d) I am seeing these errors for > each of the lists that currently exist: > > database_1 | ERROR: null value in column "description" violates > not-null constraint > database_1 | DETAIL: Failing row contains (2, > <listname>@<domain>.com, OMA-COM, null, [OMA-COM], 1, 2019-02-25 > 13:30:03.868072+00, <listuri>). > database_1 | STATEMENT: UPDATE "hyperkitty_mailinglist" SET "name" = > '<listname>@<domain>.com', "list_id" = '<listuri>', "display_name" = > '<LISTNAME>', "description" = NULL, "subject_prefix" = '[<LISTNAME>]', > "archive_policy" = 1, "created_at" = > '2019-02-25T13:30:03.868072+00:00'::timestamptz WHERE > "hyperkitty_mailinglist"."id" = 2 > database_1 | ERROR: null value in column "description" violates > not-null constraint > > All of the lists do have description that I can see in the Postorius > interface. > > Thanks > > On Tue, 7 May 2019 at 16:06, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> Are you using images with "rolling" tags? >> >> If yes, you should try to switch to "0.2" tag and the new release will be >> tagged with the same one. >> >> To update, you can do: >> >> $ docker pull ... >> $ docker pull .. >> >> $ docker-compose stop >> $ docker-compose rm >> $ docker-compose up -d >> >> This should basically get you up and running with the new image you >> pulled. >> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> >> > > -- > > *Nathan Dixon* MEng > Senior Software Architect > m: +44 (0)7402 690311 > > t: +44 (0)20 81231252 > e: nathan.dixon(a)evadon.com > w: www.evadon.com > > This e-mail and any attachments are confidential and may be protected by > legal, professional or other privilege. If you are not the intended > recipient you should not store it, copy it, re-transmit it, use it or > disclose its contents, but should return it to the sender immediately and > delete your copy from your system. The views expressed are those of the > sender and not necessarily those of Evadon. Please note that whilst we scan > all e-mails for viruses we cannot guarantee that any e-mail is virus-free. > Please be advised that we expressly reserve the right to monitor email > content for the purposes of ensuring compliance with legal requirements and > company policies and your sending to, or receiving from, us of any email > constitutes your agreement to these terms. > > > Evadon Dynamics Limited, registered in England No. 09494097. Registered > Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, > S1 2BJ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

6 years, 4 months

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

by Stephen J. Turnbull

朱超 writes: > Yes, I know why 404 is reported，The url should be postorius not be > mailman3, In the stock configuration both "mailman3" and "postorius" invoke the same view, and I'm fairly sure several templates invoke "mailman3" rather than "postorius". I believe the logic was that casual users will recognize "mailman3" more readily than "postorius", and similarly for "archive(s)" vs. "hyperkitty". > https://www.example.com/postorius/lists/$list_id/confirm/?token=$token, > and it report success. I am curious why there is no similar > processing logic for unsubscribing in postorius。 I don't understand what you're suggesting. A subscribed user necessarily has a confirmed address, and if a web administration app is running, they can log in and with a couple of clicks unsubscribe. Unsubscribe by mail does involve a confirmation step. As explained before, the reply confirmation is surely available to core; if you want I believe you can craft email templates to use the web confirmation either as an option or the preferred method. > Can we optimize for this？ What do you mean by "optimize"? If you mean fewer steps for the user, I believe the FAQ explains how to create a one-click unsubscription URL (at least that was possible with Mailman 2). There is a mild denial of service possibility, of course, but it doesn't involve third parties and is usually recoverable since the unsubscribe generates an email to the "victim" who can check archives in the majority of cases and easily resubscribe. > If you use mailman-web (include postorius and django-mailman3 and > django-allauth and so on) to set the template information, the > template obtained by mailman-core is obtained by requesting > mailman-web, No, the templates used by core and by Postorius are stored in different databases. It's true that you can use Postorius to set core's templates, but they're still stored in core's database, not in Django. They *must* be, because core needs to be able to send email even if there is no web interface at all. I suppose you could arrange that one could be set by the other. If you want to define a protocol so that any application that speaks the REST API can do this, I suppose it could be added to Mailman. But we can't depend on web administration being installed at all, and we can't depend on it being Postorius. Steve

2 years, 8 months

[MM3-users] Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Odhiambo Washington writes: > And I don't like this, so I think I will put all my configs into > /opt/mailman/mm/etc/ and link /etc/mailman3 to this path instead. Unfortunately by definition it's impossible to make the search path for the configuration file be configurable. Hm ... I think I know how to do this. ;-) Specifically, we could have a "install_defaults.py" file that lives next to bin/mailman or maybe in site-packages/mailman directory. bin/mailman would import specific variables from it, something like try: from .install_defaults import CONFIG_SEARCH_PATH, USE_CONF_D except ModuleNotFoundError: CONFIG_SEARCH_PATH = ['./mailman.cfg', ...] USE_CONF_D = False # this variable is probably a bad idea except ImportError: log'"your bootstrap.py is missing required variables'") raise Important: `mailman info` would report its location. > What bite me is probably related to this experience by Turnbull: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > I am on FreeBSD where user applications should have config files in > /usr/local/etc/ and not /etc/ so having /etc/mailman3 and > not /usr/local/etc/mailman3 kinda makes me feel weird. I sympathize. While I have no problem with the /etc/mailman3 approach, I think the *BSD approach of putting locally built configs in /usr/local/etc is equally reasonable. More than either, for third party and locally built software, I'm a fan of the /opt approach (ie, a self-contained tree for $APP, with /opt/$APP/bin, /opt/$APP/usr, /opt/$APP/var, /opt/$APP/etc or similar subdirectories). FWIW, Mailman 3's search path looks for mailman.cfg in the following places, in this order: 1. the value of the -C option # run-time option 2. $MAILMAN_CONFIG_FILE # login-time option 3. ./mailman.cfg # run-time option 4. ./var/etc/mailman.cfg # /opt-like 5. $HOME/.mailman.cfg # for developers? 6. /etc/mailman.cfg # traditional 7. /etc/mailman3/mailman.cfg # distro-friendly (Linux, at least) # good place for conf.d (see issue#424) 8. ../../etc/mailman.cfg # /opt-like # (relative to Mailman 3's bin directory) IMO this list is way too long, and ./var/etc is kind of strange. But the thing about creating the file even though it finds one of the other ones is really annoying. BTW the config file creation issue was reported about two years ago: https://gitlab.com/mailman/mailman/-/issues/797 and there are a couple of loosed related issues (ie, if we're going to thoroughly review the configuration files): - Separate config for secrets: https://gitlab.com/mailman/mailman/-/issues/466 - Support conf.d directory: https://gitlab.com/mailman/mailman/-/issues/424 Comments welcome, not really sure what I want to do here. Steve

2 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Postfix is listening on 127.0.0.1:25 is it ok? or should listen on 0.0.0.0:25?? El mar., 1 ago. 2017 a las 16:34, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > > > > On Tue, Aug 1, 2017, at 02:29 PM, Rafael Mora wrote: > > Hello Abhilash, > > I have this in my settings.py file: > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > #EMAIL_HOST_USER = 'mailing(a)labbrands.com' > #EMAIL_HOST_PASSWORD = '******' > > > This looks good to me. > > > What should I use in user and password?? Does Django use postfix to send > the email??? > > > I think you don't need a password and username as long as your postfix is > configured to relay local emails without authentication (which it is by > default if you installed from distro packages and if you haven't changed > the settings). > > > Thanks > > > > > El mar., 1 ago. 2017 a las 16:20, Abhilash Raj (<raj.abhilash1(a)gmail.com>) > escribió: > > Hi, > > > > On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > > It's ok now, but still I can't make it send the confirmation email > > > > This is from mailman.log: > > > > > > [mailman@localhost logs]$ tail -f mailman.log > > Aug 01 15:59:18 2017 (2327) lmtp runner started. > > Aug 01 15:59:18 2017 (2333) virgin runner started. > > Aug 01 15:59:18 2017 (2332) retry runner started. > > Aug 01 15:59:18 2017 (2330) pipeline runner started. > > Aug 01 15:59:18 2017 (2325) command runner started. > > Aug 01 15:59:19 2017 (2328) nntp runner started. > > Aug 01 15:59:19 2017 (2326) in runner started. > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > > 90 > > > > > > > > > > What should I do? > > If you are talking about Account confirmation emails, they usually are > sent out from Django and not Mailman Core itself. > > To configure Django you need to edit the `settings.py` file, wherever > that is one your installation. If you are following the guide mentioned > at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at > `mailman-suite/mailman-suite_project/settings.py`. > > To configure your Django to send emails, have a look at > > http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required > . > > That documentation page has pretty much everything you need in order to > have a running Web Frontend, please go through it and make sure you have > everything configured. > > Finally, the actual emails from Mailing lists are supposed to be handled > by Core. You need to configure Postorius & Mailman both to communicate. > The settings are mentioned > http://docs.mailman3.org/en/latest/config-core.html#configuring-mta > here. > > > Hope that helps! > > > > > > > > > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > > > Why does it say Address already in use? > > > > > > > > > Because you are starting lm tp runner and it's already running. > > > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > > any if necessary. Then do '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 > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > 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 > > > -- > thanks, > Abhilash Raj > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification

by Mohsen Masoudfar

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. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, April 30, 2020 1:15 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification [EXTERNAL EMAIL] On 4/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > This seems to be a very basic question and/or issue, but I could not find a reliable for it: > > Assume a list member with the email address like (just as an example) > joe.student(a)university.edu sends an email to a list, Mailman gets the > email, processes it and would try to send that email to all members > with a sender field as: 'joe.student(a)university.edu'. plus > listname(a)listserver.TLD Are you referring to the envelope sender or to the From: header? The envelope sender will be listname-bounces(a)listserver.TLD or if VERP is enabled, listname-bounces+recipient=recipient.domain(a)listserver.TLD. The From: header will be unchanged from the incoming message. If yo want the From: to be the list, you can apply DMARC "Replace From with list address" unconditionally and the From: will look like From: joe.student via listname <listname(a)listserver.TLD> ... > I found some solution: > > > * Asking the members to add their email to the signature > * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code > * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code > * . . . The DMARC mitigations will do these thing for you. > More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. And they will add the poster's original From: address to Reply-To: -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 4 months

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

by Stephen J. Turnbull

Andreas Barth writes: > I'd even say: these are different flags. They already effectively are, as Abhilash explained earlier (more precisely, four values for one variable). > So basically I'd consider it rather (as seperate boolean ones): I don't think separate booleans is a good idea, since they're basically mutually exclusive states, and in most scenarios you want the user to be able to reenable from any of the disabled states, so having both "member disabled" and "admin disabled" would have no special semantics. > - "disabled by member" (could be set by an admin as well of course) Currently this is determined by whether the logged in user is the subscriber or not. It's an interesting idea to allow it to be set by an admin. Then we could have the semantics that the only transition allowed from this state would be to enabled, so that admins would know the user had intentionally disabled and know not to enable without permission. > - "disabled for administrative reasons" (only by admin but user > should be able to see it) I don't see why a user would need to see the difference. Unless you're suggesting that the user would not be able to reenable without asking the admin? What is the use case for this? > - "bounced" (user and admin could reset it but not set it) Reenable but not set "bounced" is the current situation. > Or is this too complex for normal admins and users? I don't really understand the use case for administrative disable, except at the request of the user. (The only thing I can think of offhand is the "surprise party" scenario, which seems like a stretch. In Mailman 2, you could do it with a topic that only the planners were subscribed to, and I would think that more likely to pass without notice by the guest of honor.) In the current situation, where the state is determined by who is logged in, not by what the user wants, I think it would be confusing for some users to see "disabled by admin" if they requested it. I think that's the overwhelmingly common case for administrative disable. So I'm against showing the user the difference. In your scheme, the question is whether admins would properly distinguish between user requests and the case where the admin disables for some reason. If they do, it's harmless, but it seems like a small burden on the admins. Steve

4 years, 7 months

[MM3-users] Mixing Mailman 3 with AWS SES

by Stephen J. Turnbull

Ralph Weber writes: > I am moving the website www.t10.org from a private/corporate VM to > AWS EC2s. > > For many years, t10.org has had very happy results with using > Mailman 2 for its email reflector, and I have no real concerns > about moving to Mailman 3. My bugbear is the fact that I need the > following mixed bag of incoming email addresses to work in concert > with each other to receive and handle emails. > > > t10(a)t10.org (Primary Mailman Reflector) > > chair(a)t10.org (Mailman Reflector to direct messages to the T10 > > chair and his designates) > * docs(a)t10.org (document posting mechanics - serviced by a small > mountain of home-grown code code > * bbs(a)t10.org (other publicly accessible services - serviced by > code that recalls the days when everything as done on a Bulletin > Board System, BBS) This isn't a Mailman question, to be frank. As Abhilash points out, Mailman doesn't care about other mailboxes served by its host (unless they conflict with list names or adinistrative addresses derived from list names, which evidently yours do not). It's a question about the mail service at AWS. I've not seen any documentation in our project about setting up at AWS; I don't know anybody who has done so. (I haven't looked for either though.) I took a quick look for AWS SES documentation. They don't seem to have any real documentation online for the general public, only lists of features. They also seem to be very focused on sending rather than receiving. Much talk of how much mail you can send, bulk emailing, statistics on responses, and the like. None about setting up for incoming mail. Probably I could get access to online help if I signed up for a free account, but that's above my pay grade. > My best guess is that the AWS Simple Email Service (SES) needs to > sit in front of both Mailman and the home-grown code, I don't know if AWS provides an alternative Complicated Email Service, but yes, something like SES is going to have to sit in front of the various mailboxes. Mailman itself has a certain amount of capability to deal with the main email protocols, but it is definitely not capable of replacing the main mail server. For security reasons I would definitely advise against any Mailman 3 presence directly on the Internet. It was designed on the assumption that it would talk to the Internet via a standard mail server, Postorius (for administration), and HyperKitty (for mail archives)[1], and occasionally to admins logging in with shell accounts. > All available evidence read to date URLs, please. As I wrote above, Amazon's documentation is at best not very discoverable. > suggests that the default AWS installation Whose default installation of Mailman? AWS's? Typical 3rd party configurations? > of Mailman 3 assumes that Mailman 3 is the *only* receiver of > emails in the configuration. That's possible, but it's likely an artifact of the application -- I would expect that many who host Mailman on AWS do so to isolate Mailman from other services they provide. So it seems reasonable that in many such installations Mailman is *the* service for that instance. But mail servers are designed to be many inputs, many outputs services. If SES itself is as restricted as you fear, surely AWS provides an alternative, more powerful mail service. I can imagine quite a few restrictions, other than the backing application, on the SES that Amazon *might* impose. But without access to documentation, we can't say much. > Or... Hercules may have already cleaned the Augean Stables, and > left behind a AWS Lambda function that can serve as a keystone > puzzle piece for solving my dilemma. Good luck on that. I don't know of any, but that would be a quick solution for you. I hope somebody here knows more. As evidenced by Andrew's post, there are folks thinking about it, so maybe somebody's actually tried -- anybody? Successes? Pitfalls to watch for? The other issue Andrew mentions could be important. Since Solar Winds I'm seeing daily attempts to access my O365 server (nonexistent) from AWS. Given the size of AWS, I think they probably actually do a good job of keeping felonious behavior to a minimum[2], but a lot of folks I know are happy to cut off huge netblocks until somebody they know actually complains. :-( Footnotes: [1] Or more precisely, some webservice providing those services mediating between the Internet and Mailman sitting cozily behind a firewall. [2] DigitalOcean, on the other hand, is accumulating blocked /24s, and even /16s, at my firewall. But that's another story.

4 years, 5 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/21/22 10:39, Dan Caballero wrote: > I figured out the correct import based on what was done previously. It worked. Why do you think you need to import anything? > ">>> from mailman.app.moderator import handle_message `handle_message` is not referenced in the following and doesn't need to be imported here. ``` >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... if not requestdb.get_request(req.id): > ... print(f'Bad request id: {req.id}, deleting') > ... requestdb.delete_request(req.id) > ... > Bad request id: 1694, deleting > Bad request id: 2509, deleting > Bad request id: 2727, deleting > Bad request id: 3251, deleting > Bad request id: 3265, deleting > Bad request id: 3371, deleting > Bad request id: 4844, deleting > Bad request id: 6058, deleting > Bad request id: 6201, deleting > Bad request id: 6432, deleting > Bad request id: 6502, deleting >>>> commit ()" ``` I assume after doing this, you were able to access the held messages view for the list. Note that the only names referenced in the above and not defined there are `IListRequests` and `RequestType`, but these are among the many names implicitly imported by `mailman shell` in interactive mode. ``` $ 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 name in dir(): ... print(name) ... ALL_TEMPLATES ALT_TEMPLATE_NAMES ALWAYS_REPLY AcceptEvent AcceptOwnerEvent Action AddressAlreadyLinkedError AddressError AddressNotLinkedError AddressVerificationEvent AlreadySubscribedError ArchivePolicy ArchiveRenderingMode BadDomainSpecificationError BounceContext ChainEvent ClobberDate ConfigurationUpdatedEvent ContinueProcessing DMARCMitigateAction DatabaseError DeliveryMode DeliveryStatus DigestFrequency DiscardEvent DiscardMessage DomainCreatedEvent DomainCreatingEvent DomainDeletedEvent DomainDeletingEvent DuplicateStyleError EmailError ExistingAddressError FilterAction FilterType HoldEvent IAPI IAcceptableAlias IAcceptableAliasSet IAddress IArchiver IAutoResponseRecord IAutoResponseSet IBan IBanManager IBounceEvent IBounceProcessor ICLISubCommand ICacheManager IChain IChainIterator IChainLink IConfiguration IContentFilter IDatabase IDatabaseFactory IDomain IDomainManager IEmailCommand IEmailResults IEmailValidator IHandler IHeaderMatch IHeaderMatchList ILanguage ILanguageManager IListArchiver IListArchiverSet IListManager IListRequests IMailTransportAgentAliases IMailTransportAgentDelivery IMailTransportAgentLifecycle IMailingList IMember IMembershipManager IMessage IMessageStore IMutableChain IOneLastDigest IPendable IPended IPendedKeyValue IPendings IPipeline IPlugin IPreferences IRoster IRule IRunner IStyle IStyleManager ISubscriptionManager ISubscriptionService ISwitchboard ITemplate ITemplateLoader ITemplateManager IUser IUserManager IWorkflowState IWorkflowStateManager InvalidConfigurationError InvalidEmailAddressError InvalidListNameError LinkAction ListAlreadyExistsError ListCreatedEvent ListCreatingEvent ListDeletedEvent ListDeletingEvent MailmanError MemberRole MembershipChangeEvent MembershipError MembershipIsBannedError MissingConfigurationFileError MissingPreferredAddressError MissingUserError NewsgroupModeration NoSuchListError NotAMemberError PasswordChangeEvent PendType Personalization RejectEvent RejectMessage ReplyToMunging RequestRecord RequestType Response ResponseAction RunnerCrashEvent RunnerInterrupt SomeRecipientsFailed SubscriptionConfirmationNeededEvent SubscriptionEvent SubscriptionInvitationNeededEvent SubscriptionMode SubscriptionPendingError SubscriptionPolicy TokenOwner TooManyMembersError UnrecognizedBounceDisposition UnsubscriptionConfirmationNeededEvent UnsubscriptionEvent UnverifiedAddressError __builtins__ abort commit config getUtility m >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Counter-intuitive header filter processing

by Mark Sapiro

On 09/18/2018 01:04 PM, Jonas Meurer wrote: > > Maybe then the description for chain "accept" in postorius needs to be > adjusted. Currently it says "Accept immediately (bypass other rules)". > This gives the impression, that it will overrule the default action. Yes, I agree it's confusing. > A related followup question: what configuration is recommended for an > announcement list where only specific senders (e.g. sender(a)example.org) > should be allowed to post and mail from all (other) subscribers should > be rejected? > > The only way I see to achieve this currently is: > > * Set default action for member posts to "Default processing" > * Add a header filter to accept "sender(a)example.org" > * Add a header filter to reject ".*" > > In my eyes, that's very counter-intuitive and cumbersome to configure. > But maybe I just missed a more obvious and elegant solution to achieve > the same? The way to do that is to set the default action for member posts to Reject and set Member Options -> Administration options -> Moderation for the authorized posters to Accept or Default processing as desired. However, this allows anyone to post by spoofing an authorized address. To avoid that, leave everyone's Moderation setting at List default and post using "pre-approval" (see <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/approved.ht…>. The downside of this is it requires the poster to send a cleartext password in a header or body line of the post. It will be removed from the post delivered to list members, but sending it in cleartext in an email may be an issue. We will eventually do something with PGP signatures instead, but that isn't here yet. > And one more comment: if I make the list an "anonymous list" (i.e. "hide > the sender of a message, replacing it with the list address"), then > header filters for the "from" header don't work any longer. That's kind > of unexpected as well. I would have expected mailman to process the > header filters at reading the incoming mail, not after rewriting headers > of the outgoing mail? Your expectation is correct. All the applicable rules are applied to the incoming message before any message alterations such as anonymizing are applied. Possibly you were confused because some other rule's action took precedence over your header rule. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: moving from sqlite3 to postgresql

by Michael Richardson

Stephen J. Turnbull <steve(a)turnbull.jp> wrote: >> I installed via debian packages, and I'd really prefer to stay with that. >> (Not what many maintainers would say, I know. Essential that it work if >> mailman3 is going to take over) > That's really Debian's problem, and it's a hard one since the whole > point of using Debian packages for mission-critical applications is > that they're stable. Unfortunately, the email and web environments > are not, and dealing with changes in them is often quite impractical > given the Debian release cycle. Yes, I'm aware of this tusscle. There are some ways to split this up. >> I installed with sqlite3, since it seemed if all work was going to >> go through the mailman3 daemon, that it would handle all the >> concurrency issues. > The problem is that sqlite3 is intended to be a single-threaded > system, but Mailman 3 by default spawns around 15 daemons that may try > to access the database. I would expect you would have warnings that > the database is locked frequently. Not sure what you mean by > "Sometimes this goes way on it's own, but sometimes it does not". Meaning, sometimes whatever has the lock releases it everything proceeds. Sometimes, it's still stuck a few days later, and I restart the mailman daemons. > Note that our primary purpose for the sqlite3 configuration is so unit > tests don't have to spin up a full-scale PostgreSQL or MySQL database. Fair enough. It was not obvious when installing that I should not use sqlite3. >> So I tried to switch last week from sqlite3 to postgresql. >> I used pgloader with a configuration file attached below. > Can't help you with that offhand, never used pgloader. Whatever > method you use to load up the pg database, I would recommend doing > some psql cave-diving into the PostgreSQL database to confirm it's > sane before trying to configure Mailman to use that database. Yes, I'm gonna have to do that. At least I'll start by counting number of records in each table, and then see if there is some systematic lack. >> ps: I'd pay some $$ money for email support consulting. > See https://wiki.list.org/COM/Mailman%20consulting%20services > Per my .sig, I'm on the list above but please go through channels > linked there rather than talking to me personally about business. Understood.

4 months, 4 weeks

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

by Alexander Inzinger-Zrock

Am 30.04.25 um 15:36 schrieb Stephen J. Turnbull: > Did you set var_dir or layout in mailman.cfg? If not, you may have an > alternate var_dir which is either the current directory when you start > Mailman or possibly /var/tmp/mailman. That is also where "mailman > aliases" will put the postfix aliases (in the "data" subdirectory). It seems i set both *facepalm* while doing [1] and then adding changes according to [2]: In mailman.cfg i have: [paths.here] var_dir: /opt/mailman/mm/var but also [mailman] layout: local also checking via mailman conf: ''mailman conf -s mailman | grep layout'' Output: [mailman] layout: local ''mailman conf -s | grep var_dir:'' Output: [paths.dev] var_dir: $cfg_file/../.. [paths.fhs] var_dir: /var/lib/mailman [paths.here] var_dir: /opt/mailman/mm/var [paths.local] var_dir: /var/tmp/mailman so i have empty logs at /opt/mailman/mm/var/logs and populated log files under /var/tmp/mailman/logs If i recall correctly, setting layout: local is the suggested way to do for virtualenv install [2], so deleting [paths.here] var_dir: /opt/mailman/mm/var in mailman.cfg should be the next step (what i did). Restarting my services gave me the warnings again, but these are (we remember) wrong paths (hash:/opt/mailman/mm/var/data/postfix_lmtp). so i looked under /var/tmp/mailman/data and here we have populated files: -rw-rw---- 1 mailman mailman 268K Feb 19 12:51 mailman.db -rw-rw---- 1 mailman mailman 377 Apr 30 18:01 postfix_domains -rw-r----- 1 mailman mailman 12K Apr 30 18:01 postfix_domains.db -rw-rw---- 1 mailman mailman 1.8K Apr 30 18:01 postfix_lmtp -rw-r----- 1 mailman mailman 12K Apr 30 18:01 postfix_lmtp.db Now - before changing the /etc/postfix/main.cfg - there is the question that brings us almost back to the start: With respect to [2]: "If you are installing Mailman from source (or using Pip), it is recommended to use paths.local." and [3]: " transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains […] local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/path-to-mailman/var/data/postfix_lmtp " **what is the recommended place to put the files to?** I believe it to be /var/tmp/mailman/data according to [mailman] layout: local and that the above specific /opt/mailman -part is just a leftover from former times (the second and more generic part with /path-to-mailman indicates that to me). If my assumption is correct i would create an issue + merge-request for the docs. lg aiz + [1] https://docs.mailman3.org/en/latest/install/virtualenv.html + [2] https://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem… + [3] https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mta

4 months, 2 weeks

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

by Stephen J. Turnbull

Bottom line, I think Abhilash is right: we should emphasize the pip install (probably into a venv) as the "best supported" install. Perhaps we can prioritize being more systematic about documenting the various approaches, not in term of the details (although that's a "nice to have"), but with respect to the advantages and disadvantages of the various install methods. Comments welcome. A few comments on the distro installs for the Mailman nerds: Mark Dadgar writes: > 2) The package installs are non-standard with respect to the way > the mailman3 community tends to install them, To be fair, *most* of the differences with Linux distros is that Mailman uses a "classic" $prefix-style install into $prefix/usr and $prefix/var, while the distros follow the FHS (File Hierarchy System) layout. The FHS layout in many ways is more closely-specified, and more maintainable at the distro and system levels, but it requires more effort than just throwing files into a set of more or less reasonably organized directories. Mailman 3 now provides an option for (better) FHS conformance at installation, which should reduce this problem over time. Most of the rest have to do with protecting config files from overwriting by distro upgrades. That is annoying, because location of config files is a frequent question in support, and also can lead to duplicate config files (and "great fun had by all" :-/ ) if the admin follows the recommendation of the "wrong" documentation. > > 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. I agree. But I prefer to phrase it as "mission-critical features are evolving" rather than "constantly evolving". I suspect there are a lot of people who have a casual need for a few mailing lists, and will do fine with Mailman 3 from $DISTRO stable or LTS. :-) The thing is, I think those folks will find "apt-get mailman-suite" or "yum mailman-suite" with no help from us. And I agree that the differences between the organic evolution of Mailman setup within the project and the distros' FHS-based installs are a real consideration if Mailman is a mission-critical application for you. On the other hand, Brian's "greenfield setup of a server specialized to Mailman" is probably a minority interest (ie, in terms of the number of site admins involved -- it probably serves a majority of subscriptions!) Steve

4 years, 6 months

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 11. Dezember 2019 um 13:49 Uhr -0800 schrieb Mark Sapiro: >OK. I have verified that this is due to ><https://bugs.python.org/issue32330> and has actually been reported as ><https://gitlab.com/mailman/mailman/issues/441> and worked around in >Mailman by <https://gitlab.com/mailman/mailman/merge_requests/350> which >is included in Mailman 3.2.0 and up. Thanks, and sorry for bugging you about old versions then. I'm going to forward the problem to Ubuntu's bugtracker then. But I now have a different problem. I've removed all offending messages (it were more than just one that caused the UnicodeEncodeError), but I still can't access the page for the held messages queue. It gives an error 500, now with a different exception in the log. I've included it below. It looks to me that the messages haven't properly been deleted. What I did was this: for each offending message hash 1. I ran the DELETE query 2. I deleted the file from the file system 3. I ran the delete_message() function I originally wanted to run only the delete_message() function, but a quick check on the DB and the file system after running it for one hash told me that it neither deletes the message from the DB nor from the file system. So I did everything at once. I do have a backup of both the DB and the filesystem from before I started this, in case this broke something. Is there something left that I have to do now? Here's the exception: Dec 12 08:34:30 2019 (9570) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource resource['msg'] = msg.as_string() AttributeError: 'NoneType' object has no attribute 'as_string' -- Blog: https://mg.guelker.eu

5 years, 9 months

[MM3-users] Re: Docker Support Sucks

by Brian Carpenter

On 7/21/20 8:55 PM, Mark Sapiro wrote: > On 7/21/20 5:40 PM, Brian Carpenter wrote: > > Abhilash (@maxking) is one person and he has a $DayJob. We're all doing > the best we can. Well, I still need support. > This is not a Docker issue per se. It is a consequence of upgrading > Mailman core to 3.3.1+ and processing many old, stale, previously > unprocessed bounces. See > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> I am not worried about the bounce issues at this point. I am just trying to get a membership list exported for a client. > >> So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. >> >> I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: >> >> ### >> The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: >> >> [webservice] >> configuration: /path/to/gunicorn.cfg >> >> and then in the gunicorn.cfg you can add >> >> [gunicorn] >> timeout = 90 >> graceful_timeout = 30 >> ### >> >> I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. >> >> After restarting docker-mailman, I can't access Postorius due to the following error: >> >> ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available > Is Mailman core running? If not, whats in core's mailman.log as to why not? It looks like but no error message in mailman.log. However I noted that the gunicorn process did not start. This is with the configuration line enabled in mailman-extra.cfg: # docker-compose restart mailman-core Restarting mailman-core ... done [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log Jul 22 01:25:17 2020 (22) in runner caught SIGTERM. Stopping. Jul 22 01:25:17 2020 (25) out runner caught SIGTERM. Stopping. Jul 22 01:25:17 2020 (25) out runner exiting. Jul 22 01:25:17 2020 (21) command runner exiting. Jul 22 01:25:17 2020 (22) in runner exiting. Jul 22 01:25:17 2020 (24) nntp runner caught SIGTERM. Stopping. Jul 22 01:25:17 2020 (24) nntp runner exiting. [2020-07-22 01:25:19 +0000] [27] [INFO] Shutting down: Master Jul 22 01:25:21 2020 (1) Master stopped Jul 22 01:25:26 2020 (1) Master started Jul 22 01:25:44 2020 (27) rest runner started. Jul 22 01:25:44 2020 (26) pipeline runner started. Jul 22 01:25:44 2020 (20) bounces runner started. Jul 22 01:25:45 2020 (22) in runner started. Jul 22 01:25:45 2020 (28) retry runner started. Jul 22 01:25:46 2020 (29) virgin runner started. Jul 22 01:25:46 2020 (25) out runner started. Jul 22 01:25:46 2020 (23) lmtp runner started. Jul 22 01:25:46 2020 (24) nntp runner started. Jul 22 01:25:47 2020 (30) digest runner started. Jul 22 01:25:47 2020 (19) archive runner started. Jul 22 01:25:47 2020 (21) command runner started. This is with the configuration line disabled in mailman-extra.cfg: # docker-compose restart mailman-core Restarting mailman-core ... done [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log Jul 22 01:27:49 2020 (1) Master stopped Jul 22 01:27:53 2020 (1) Master started Jul 22 01:28:10 2020 (30) digest runner started. Jul 22 01:28:10 2020 (29) virgin runner started. Jul 22 01:28:10 2020 (24) nntp runner started. Jul 22 01:28:10 2020 (25) out runner started. Jul 22 01:28:10 2020 (22) in runner started. Jul 22 01:28:11 2020 (28) retry runner started. Jul 22 01:28:11 2020 (27) rest runner started. [2020-07-22 01:28:11 +0000] [27] [INFO] Starting gunicorn 19.9.0 [2020-07-22 01:28:11 +0000] [27] [INFO] Listening at: http://172.19.199.2:8001 (27) [2020-07-22 01:28:11 +0000] [27] [INFO] Using worker: sync [2020-07-22 01:28:11 +0000] [32] [INFO] Booting worker with pid: 32 [2020-07-22 01:28:11 +0000] [33] [INFO] Booting worker with pid: 33 [2020-07-22 01:28:11 +0000] [34] [INFO] Booting worker with pid: 34 [2020-07-22 01:28:11 +0000] [35] [INFO] Booting worker with pid: 35 Jul 22 01:28:11 2020 (19) archive runner started. Jul 22 01:28:11 2020 (21) command runner started. Jul 22 01:28:12 2020 (23) lmtp runner started. Jul 22 01:28:12 2020 (20) bounces runner started. Jul 22 01:28:12 2020 (26) pipeline runner started. -- 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, 1 month

Search results for query "dO"