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

[MM3-users] Re: trying to clean up the "held messages" mess

by Mark Sapiro

On 5/28/21 12:37 AM, Bjoern Franke wrote: > Hi, > > I migrated a Mailman3 installation on Debian10 yesterday evening from > Debian packages to PIP (thanks to [1]). > > I think some bugs which existed before are now cleaned out, but mailman > still threw exceptions when trying to get the "held messages". What exceptions? Note that there is a lot of cleanup in the as yet unreleased core 3.3.5. You might consider installing that. To do so, in your virtualenv as the Mailman user do ``` pip install --upgrade git+https://gitlab.com/mailman/mailman ``` > The amount of held messages is now reduced, but e.g. a list with 120 > held messages before has till 59 held messages. And now I'm confused: > where are they? The held message entries are in the _request table with `request_type` = 1. For those entries, `key` is the message-id and `data_hash` is the `token` in the pended table and the `id` in the pended table is the `pended_id` of the related entries in the pendedkeyvalue table. The message itself is stored in the file system and is pointed to by the entry in the message table with the corresponding message-id. The exceptions you see are because entries are missing from the pended, pendedkeyvalue and/or message tables. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

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

by Eric Broens

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/

5 years, 2 months

[MM3-users] Re: redirecting -bounces replies

by Mark Sapiro

On 6/25/25 10:53, Hirayama, Pat wrote: > Thanks, Mark. > > I (finally) started working on this ... and in trying to implement your suggestion — ran into a problem, I think. > > The current postfix_vmap has entries like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24 This looks very strange. It should be something like ``` list-bounces(a)lists.domain.info list-bounces(a)alias.domain ``` where alias.domain is the configured alias domain for the mail host lists.domain.info. > So, when I try adding entries to a separate vmap file, like: > > list-bounces(a)lists.domain.info lmtp:[mailman-core]:24, user(a)gmail.com > > It only goes through normal bounce processing. > > If I do: > > list-bounces(a)lists.domain.info user(a)gmail.com, lmtp:[mailman-core]:24 > > Then it goes to the gmail address, and no bounce processing happens. The issue here is the value `lmtp:[mailman-core]:24` is completely wrong. It should be an email address with a syntactically valid domain name. The domain name isn't a real domain. It is only a name exposed to Postorius in the postfix_vmap and postfix_lmtp files. What do you have configured for the alias domain for the lists.domain.info domain? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… If you have this properly configured, adding user(a)gmail.com in either order in postfix_vmap should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

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

by Mark Sapiro

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 issue is that unlike mm_cfg.py and Defaults.py in Mailman 2.1, the recommended way to set up Django in Mailman 3 is to point Django at settings.py for the default config, and the last thing in settings.py is try: from settings_local import * except ImportError: pass Thus,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. 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. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

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

by Abhilash Raj

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)

5 years, 6 months

[MM3-users] Re: Template Ignored?

by Stephen Daniel

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

4 years

[MM3-users] Re: Mailman shell tutorial

by Andrew Bernard

Thanks Mark, The omission of the code to make the examples work seems to need correction. Perhaps I can submit an update to the project. Had me scratching my head for a long time. Obviously I knew there were imports etc missing, but what to put? I have this going, and it is great. But I recall seeing something called mmclient or similar which has simple commands like show user, show lists, and so on. Is that still available? Now knowing how mailman shell works, anybody could write their own commands, but I don't want to reinvent wheels. Andrew > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, 11 June 2019 1:26 PM > To: mailman-users(a)mailman3.org > > Perhaps you saw the `command('mailman shell --details')` line in the docs at > <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/s > hell.html#getting-detailed-help> > in any case, that requires two things to precede it. The first is part of the > doctest infrastructure and is not evident in the docs. that step is > > from mailman.testing.documentation import cli > > The second step is in the docs and is > > command = cli('mailman.commands.cli_withlist.shell') > > If you do those two steps within `mailman shell`, then the step > > command('mailman shell --details') > > will work, but as I said, this is just the same as doing `mailman shell --details` > at a command prompt.

6 years, 8 months

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

by Mark Sapiro

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

2 years, 6 months

[MM3-users] Re: Handling of Mail from non-subscribers

by Mark Sapiro

On 5/8/20 5:32 PM, Peter Adebahr via Mailman-users wrote: > > May 09 01:22:38 2020 (1235) SHUNTING: 1588980158.3151...... > > But immediately before I find the "module 'time' has no attribute > 'clock'" which I remember from a thread a couple of days ago, though I > cannot remember a solution when mm3 has not been installed from source > but via apt-get. > > My core is V 3.2.2, core python 3.8.2, by the way. That is exactly the issue. Mailman 3.2.2 is not compatible with Python 3.8. This is a Debian/Ubuntu packaging bug. What has happened is the post encountered the exception shown in the Traceback that preceded the SHUNTING message and the message that triggered the exception was placed in the shunt queue. The thread you remember is <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> The fix is to patch your Mailman installation with the changes at <https://gitlab.com/mailman/mailman/-/merge_requests/552/diffs?commit_id=ea0…>. Or, at the very least change x = random.random() + right_now % 1.0 + time.clock() % 1.0 to x = random.random() + right_now % 1.0 + time.process_time() % 1.0 in mailman/utilities/uid.py. After doing that and restarting Mailman core you can do `mailman unshunt` to reprocess the message or if you prefer, `mailman unshunt --discard` (or just remove it from the shunt queue) to discard it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Archives with encoding characters

by Mark Sapiro

On 3/4/20 8:55 AM, Seth Seeger wrote: > Hello everyone, > > I have a few (but not all) members complaining that their digests are full of coded characters. Two examples below were forwarded to me: > >> What I ended up doing was creating 2 "practice lines" in the centre of=20 >> our big teaching circle (I always teach new figures in a big circle) -=20 >> which each had 3 people set up in a line with generous space between,=20 >> and first=C2=A0 I walked through one of those lines myself starting first= >> =20 > > and > >> Robins pass Right=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= >> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Larks Loop L= >> eft > > What is the cause? Is there anything I can do about it? The cause is a quoted-printable encoded message body not being decoded. This may or may not be a Mailman bug, but if as Mark Dadgar suggests, it only happens with some MUAs, the issue might be in the MUA. To understand more we'd need to see the actual raw digest message from the list, or maybe just a raw incoming message that winds up like that in the digest. -- 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: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by kisner＠live.com

Mark Sapiro wrote: > On 7/8/22 8:28 AM, kisner(a)live.com wrote: > > I tried to follow that guide ( https://docs.mailman3.org/en/latest/install/virtualenv.html ), but I couldn't get it to work. I'd have to try it again to see where it broke. One thing that I got past was I had to change: > > (venv)$ pip install wheel mailman psycopg2-binary<2.9 > > to > > (venv)$ pip install wheel mailman psycopg2-binary==2.8.6 > > and that got me past that part, > > I don't understand why that would make a difference since the latest > psycopg2-binary<2.9 is 2.8.6 > > but hyperkitty/mailman-web pip install has components that failed to install. I'm not sure why, someone smarter than me could probably have figured it out, but as written it wasn't working for me. > > If you do try again, post the specific issues/error messages and we will > try to help. Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros.

3 years, 7 months

[MM3-users] Re: Member Issue Discovered

by Jörg Schulz

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

5 years, 4 months

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

by Mark Sapiro

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

3 years, 1 month

[MM3-users] Re: Rootkit issues

by Kyriakos Terzopoulos

Hi Peter, The rootkit had already been removed up to that point. The user of the Blitz process was the mailman user. Taking steps to secure the server more now. On Tue, 17 Oct 2023, 22:23 , <peter(a)chubb.wattle.id.au> wrote: > > > Some more info on the issue after running RKhunter: > > [09:47:54] Warning: Network TCP port 47018 is being used by > > /tmp/.X291-unix/.rsync/c/blitz64. Possible rootkit: Possible Universal > > Rootkit (URK) component > > You need to remove the rootkit. Someone has hacked into your system. > This has nothing to do with Mailman3 as such. > > If you do a > ps axfu | grep blitz64 > > you should be able to find which uid is being used (first column of > output). You'll then be able to find the bits of the rootkit by > looking at that user's processes and open files, and delete them. > > And then you can fix that user's permissions/password so it's less > likely to be compromised again, or delete the user entirely if the > user isn't being used for anything else. > > > -- Peter C > _______________________________________________ > 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 kyriakos.terzopoulos(a)gmail.com >

2 years, 4 months

[MM3-users] question about recommended postfix configuration

by Marc Sluiter

Hi, im trying to setup mailman and have an issue: first my environment: - I’m running postfix etc with "mailcow-dockerized": https://mailcow.github.io/mailcow-dockerized-docs/ - I’m running mailman with "docker-mailman": https://asynchronous.in/docker-mailman/ I got almost everything working besides confirm mails (see my other mail), but I had to use another postfix configuration than recommended, I’m wondering why the recommended way didn’t work. Sidenote: I’m not a postfix expert. This is recommended: transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains This didn’t work, all mails to mailman were rejected. Postfix did not even check the “local_recipient_maps”. After a lot of reading that made sense to me, because when I understand it correctly, “local_recipient_maps” is only checked for domains in “mydestinations”. And there I only have localhost. My first change then was to use “relay_recipient_maps” instead of “local_recipient_maps”, because the domains were also added to the relay configuration "relay_domains". That worked. But then I noticed warnings by postfix about having the same domain in “virtual_mailbox_domains” and “relay_domains”. Made sense again because I used the same domain in my “normal” mail setup (with “virtual_mailbox_domains”) and in mailman. So finally I ended up with adding the mailman files to “virtual_mailbox_domains” and “virtual_mailbox_maps” instead of “relay_domains” and “local_recipient_maps”. Do my findings and changes make sense to you? Or do I miss something important? Good thing is that at least “transport_maps” worked for whatever configuration I used :) Thanks and greetings, Marc

8 years, 5 months

[MM3-users] Re: Importing archive from mm21

by Mark Sapiro

On 11/27/23 13:01, Lars Bjørndal wrote: > I imported an archive from a list created in September 2013 with the > following command: > > mailman-web hyperkitty_import -l annonsering(a)hodr.no --since 2013-09-01 <mbox file> If it's a new list with no current archive, I typically don't use --since. If there might be messages in the archive, I normally use something like `--since 1970-01-01` just to be sure I get everything. > No errors reported. And this should have imported all messages with Date: header dates >= 2013-09-01 plus any without Date: headers. > I then did > > mailman-web update_index_one_list annonsering(a)hodr.no > > No, when I go to https://hodr.no/archives/list/annonsering@hodr.no/, I > cannot choose mails earlier than January 2023. > > What's the problem, do you think? The messages are there. I went to https://hodr.no/archives/list/annonsering@hodr.no/ and only saw messages from 2023, but then I went to https://hodr.no/archives/list/annonsering@hodr.no/latest?count=200&page=2 and started seeing all the messages even at https://hodr.no/archives/list/annonsering@hodr.no/. What do you see now? I also note your pages seem to be missing the styling as the references to the styles, etc at https://hodr.no/static/* all return 404. Is the issue fixed for you now? I don't understand what caused the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

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

by tokyoprogressive＠mailbox.org

Thank you Mark. I will need to find time tomorrow to create two totally new email accounts that I can use in tests so I do not inadvertently sign up again with the same address. Also will double check my settings. Best regards Paul Sent from my iPhone > On Sep 17, 2019, at 14:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/16/19 9:22 PM, Paul Arenson wrote: >> 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 > > > You have to approve it or the user has to confirm her email address? > Maybe you have to approve it because the lists Subscription Policy is > Moderate. > >> 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? > > > No. They will be a member, they just will not have a Django account that > they can log in to. > > >> 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" > > > Because when you create a Django account, you have to confirm your email > address. > > >> 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" > > > What is Message Acceptance -> Default action to take when a member posts > to the list ? > > You get the notice or the user gets the notice? > > >> 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? > > Signing up for an account is just signing up for a Django account. You > can sign up for an account and log in and then subscribe to the list. > > Subscribing makes one a member whether or not you subscribe from a > logged in account or subscribe without creating an account. > > >> But here it seems that both make them a non member. > > If an address which is not a member posts to the list, that address > becomes a non-member. This is the only way other than being explicitly > added by an admin that an address becomes 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. > > > If by sending from the interface, you mean posting via hyperkitty, the > user must have an account and be logged in to do that. > > Your "same person" may have multiple entities within Mailman, possibly > subtly different email addresses, one of which is a member and one of > which isn't. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 5 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/4/21 1:02 AM, Simon Coggins wrote: > > All I’m doing is literally appending a subset of a hash of the mailing list rcpt address to the front of the message-id, so that if it gets moderated, each instance of the email has a different message-id and each moderation action has it’s own copy of the email to operate on. This seems to have gotten us out of the immediate issues. But I’m eager to find a better solution that might be more permanent. As you have seen, this is new in 3.3.5. I recognize this is a problem. Previously, attempts to accept the message on the second and subsequent lists would throw an uncaught exception - see https://gitlab.com/mailman/mailman/-/issues/914 and this was a fix for that. Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better. -- 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: Can't subscribe on new site/domain

by Stephen J. Turnbull

Jeremy Stanley writes: > It's all stored in a relational database, This isn't quite true: - order of shutdown matters because you want to be sure queues are flushed - several queues (bad, shunt, queues internal to archiver plugins, specifically HyperKitty) do not get flushed (bad cannot be flushed) - some database items (eg, custom templates) get cached on disk, and people sometimes modify them on disk and/or add new template directory to the template search path > which you should be able to extract with a tool like mysqldump and > then later source that same dump into a new empty database. This is often unnecessary. If you're going to be running the new Mailman on the same host, you can probably keep the old database running, and point the new Mailman applications to it. > You can find some information on database setup in the documentation > here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/datab… > Some familiarity with backing up, restoring and manipulating > databases is a big help for these sorts of tasks, otherwise it may > have a fairly steep learning curve. Let me second Jeremy's advice above. Consider the skills you have available to you when deciding how to do the migration, and feel free to discuss your plans here. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 3 weeks

[MM3-users] Re: Django logins for new subscribers

by Abhilash Raj

On Fri, Jan 12, 2018, at 8:41 AM, Alex McLean wrote: > Hi all, > > I'm moving our groups to mailman3 (http://we.lurk.org) Enjoying it so far! > > I've mass-subscribed people via postorius. However the subscribers don't > have django (postorius/hyperkitty) logins. It seems they only exist on > the mailman side, not the django side. > > If they go through the process of creating an account in postorius, they > can configure their mailing list subscriptions, but this is a bit > fiddly. > > Is this expected behaviour? It would be great if they could be sent a > temporary link to set a password and go. Yes, that is the expected behavior. Postorius is just one of the front-end for Mailman (and only one, for now), so we didn't think it would make sense to create account for every Mailman User in Postorius as well. So, basically everyone has to go through the sign-up process, which isn't really hard if you choose one of the social logins. It wouldn't be very hard to write a script that "creates" User accounts for everyone and then users go through the "Forgot Password" workflow to set their passwords. You'd get the list of all users from Mailman's API and then do a `get_or_create()` on each one of them (simplest of all approaches, you can ofcourse better ways to do the same). -- Abhilash Raj maxking(a)asynchronous.in

8 years, 1 month

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/26/20 12:33 AM, Alan So wrote: > Thanks. Just filed an issue: > https://gitlab.com/mailman/mailman/-/issues/725 Thank you for your "well formed" issue. I have started to work on this, but I have run into a snag. The patch at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> doesn't work. The problem is msg.get_all(header, []) does not parse the header and return a list of addresses. It just returns a list, the items of which are the raw values if the header instances in msg. I.e., if there is only one Cc: header, msg.get_all('cc', []) returns a list of one string which is the raw value of that header. If there were two Cc: headers in the message it would return a list of two strings with the two raw values. Thus, we would need to parse the strings returned into the individual email addresses. The simple minded way to do that is addrs = [] for hdr in msg.get_all(header, []): for addr in hdr.split(','): addrs.append(parseaddr(re.sub('[\r\n]', '', addr))) but that will fail if the header contains a quoted display name containing a comma such as "last, first" <user(a)example.com> So, I need to go back to using getaddresses, but do the unfolding first. Watch the issue for the final fix. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: List in list, mutiple reply-to addresses

by Mark Sapiro

On 11/25/21 11:00 PM, Stefan Bauer wrote: > Mother: > Anonymous list: No > First strip reply to: No > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > > > > Daughter: > Anonymous list: No > First strip reply to: Yes > Reply goes to list: No Munging > DMARC mitigation action: Replace From: with list address > DMARC mitigate unconditionally: Yes > Because of DMARC mitigation, you can't do what you want. With the settings you have the mother list puts the original From: in Reply-To: and it's own address in From:. Then regardless of what the daughter does with the incoming Reply-To:, it will add the incoming From: to Reply-To: so the Reply-To: of a message from the daughter will always contain the address of the mother. The best you can do, unless you are willing to set DMARC mitigation action: to No DMARC mitigations is what you started with which is First strip reply to: No on the daughter which will at least put the original From: to the mother in Reply-To: from the daughter along with the mother's address, but you can't remove the mother's address from the daughter's Reply-To: because DMARC mitigation will always put it there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 4/28/22 10:59, bob B via Mailman-users wrote: > We had an issue where a program went rogue and sent out 30k email alerts to one of our lists, so now I have a few questions. > > When the issue happened I turned on emergency moderation and we have resolved the issue so.. > > 1. How do I easily delete 30k of held messages? It looks like the GUI only allows me to do 200 at a time? is there a way to flush all held messages easily? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and the thread containing it. > 2. When I enabled Emergency moderation, I expected it to stop notifying the admin on every held message, but it appears that is not the case? Also, does it reply to the sender of every held message when Emergency moderation is on? > > it seems like the steps are: > turn on "Emergency moderation" > turn OFF "Notify users of held messages" > turn OFF "Admin immed notify" MM 2.1 didn't notify the admins of emergency holds. This is not the case in MM 3. It probably should be, but isn't. Senders are or aren't notified per "Notify users of held messages". So the steps above are correct. -- 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: copies of sent "admin" messages

by Stephen J. Turnbull

David Bremner writes: > As far as I can tell, people (bots? mindless corporate firewalls?) > are complaining about the initial confirmation email. So I think an > additional approval step won't really help. Then you can go to approval only, or subscription by admin only. That's probably not what you want, but on the off chance it's better than the current situation I mention them. I'm not sure what you plan to do with these messages if you get them. Do you think the content is likely to reveal anything about the problem agents that are conducting this apparent attack? You could try adding [logging.subscribe] level: debug or [logging.smtp] level: debug to 'mailman.cfg' get more output in the logs. Note that the latter will be *very* verbose and fill up the 'smtp' log very quickly. This will not get the content of the messages. With Mailman 2 there was a neat dodge: you move the 'mailman' executable wrapper aside and put another executable in its place. I guess you could stick an lmtp server such as Postfix's smtpd on localhost:8024, configure mailman to listen on 8025, and have the smtpd dupe it for you (ie, deliver both to a file and to localhost:8025. Maybe you want to put an instance of a filter like procmail in there so it only looks at -subscribe mailboxes. I don't really know what to say beyond that.

2 years, 3 months

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

by Abhilash Raj

On Thu, May 13, 2021, at 7:18 AM, Torge Riedel wrote: > Am 03.02.21 um 02:59 schrieb Abhilash Raj: > > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Dear MM3 releasers, > > after successful update to latest versions I realized that Mailman Core > change log links are stable (I requested this some time ago and it was > changed - thanks for that), but Postorius and Hyperkitty change logs do > not have stable header ids. > > Can this be changed too? > > It makes it easier for me (and hopefully for others) when communicating > changes to the users. At the moment they see the upcoming changes for > Postorius first, which always introduces confusion for some of them. > The stable headers are sometimes missed when creating a new NEWS section. There isn't an automation that I've found to add a new section in the news.rst file yet which will do that for me. So I just forget sometimes :-) Adding headers is a trivial thing though. If you find one missing on any project please feel free to submit a MR to fix that. It can be done after the release has been made too. See this[1] that Mark just made to fix it for Postorius. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/636/diffs -- thanks, Abhilash Raj (maxking)

4 years, 9 months

[MM3-users] Re: Trouble Installing Mailman3

by Henry Hartley

Thanks to all who responded for your feedback. Unfortunately, the firewall blocking outbound traffic isn't something I can do anything about. Servers in our "web zone" must have specific rules allowing outbound access. That's fine for Red Hat or Ubuntu repositories but this is the first machine where we are trying to install using pip, so getting the right rule in place took some experimentation and adjustment. I did eventually get the install to work with the firewall opened for me and with a --proxy option added to the command (although I'm not 100% sure --proxy was needed). The other thing I had to do that was different to the instructions was to use pip to install setuptools. I got to a point where I had an error message that said "ERROR: Could not find a version that satisfies the requirement setuptools>=40.8.0" but when I ran "apt install python3-setuptools" it reported that it was "already the newest version (68.1.2-2ubuntu1.2)". However, running pip install setuptools (on a whim) installed version 80.9.0. After that "pip install mailman" worked. Perhaps I should have known this. I feel that making sure setuptools is properly installed might be something to add to the installation instructions. The next step in the instructions has me create /etc/mailman3/mailman.cfg. The first thing in that file is shown as: [paths.here] var_dir: /opt/mailman/mm/var Looking in /opt/mailman, there is no mm directory. Should that have been created, or is that something I need to create myself? -- Henry Hartley Westat RB 2151 -----Original Message----- From: Gerald Vogt <vogt(a)spamcop.net> Sent: Tuesday, June 3, 2025 12:29 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Trouble Installing Mailman3 CAUTION: External Email * On 03.06.25 17:22, Henry Hartley via Mailman-users wrote: > I'm having problems installing mailman3 following the instructions on https://secure-web.cisco.com/1lGZ6VhIpDXnBDYduOpQfdrz5vzmVmUu1Ox4qpxrEdA3f2… Everything goes well until I get to the Installing Mailman Core<https://secure-web.cisco.com/1XnIv9oM-wXrdCe9VFieDJykhtB-NNf5h-UB4ysN7pvWtA…> step, which has me do the following in my venv environment: > > (venv)$ pip install wheel mailman psycopg2-binary > > Ubuntu 24.04.02 LTS > Python 3.12.3 > pip version 24.0 > > First, I was getting problems because my company firewall was blocking outbound traffic. I got that taken care of. Next, I was seeing certificate errors, saying there was a self-signed certificate: > > WARNING: Retrying (Retry(total=0, connect=None, read=None, > redirect=None, status=None)) after connection broken by > 'SSLError(SSLCertVerificationError(1, '[SSL: > CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed > certificate in certificate chain (_ssl.c:1000)'))': /simple/wheel/ > Could not fetch URL > https://secure-web.cisco.com/149I_kjrnLhuIpr1APuB8udvv8jCJuk0lqcI_esQ- > dqwmKVpgaw1Y6LT5_dF8kBkxoIp3E5cH7c8E3NU5TFqaenv2yCcBV0jBYVDBuHgpqP9oRU > OfJ6XZruLMDf2pqH2ydyrnAxjJ_ZTs59eeLe69Iy0jFuoA5d_XpSiBVdVvGKbBN13EkyH2 > HNcgmruVikAcwrT6sN52QPqQIesisnHaK6MvxqVRbMuHjoY3vpvMzLsJaSrN6_XOSx3oGf > DZgAOV/https%3A%2F%2Fpypi.org%2Fsimple%2Fwheel%2F%3A There was a > problem confirming the ssl certificate: > HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded > with url: /simple/wheel/ (Caused by > SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] > certificate verify failed: self-signed certificate in certificate > chain (_ssl.c:1000)'))) - skipping There is no self-signed certificate in the chain, when I check it. I guess, there is a proxy somewhere which has a different certificate. Run $ openssl s_client -connect pypi.org:443 -showcerts to check what certificate is presented. It should be something like: Connecting to 2a04:4e42::223 CONNECTED(00000003) depth=2 OU=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign verify return:1 depth=1 C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 verify return:1 depth=0 CN=pypi.org verify return:1 --- Certificate chain 0 s:CN=pypi.org i:C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: Feb 24 04:28:22 2025 GMT; NotAfter: Mar 28 04:28:21 2026 GMT ... 1 s:C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 i:OU=GlobalSign Root CA - R3, O=GlobalSign, CN=GlobalSign a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256 v:NotBefore: Oct 16 03:08:04 2024 GMT; NotAfter: Oct 16 00:00:00 2026 GMT ... Server certificate subject=CN=pypi.org issuer=C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 DV TLS CA 2025 Q1 ... > When I added --trusted-host pypi.org that error went away but I'm still unable to install anything: Never ever do that. Find out what is happening. Either something bad is interfering with your network traffic. Or there is a proxy and the chain is different. In the latter case, you will see lots of issue until you have configured your system correctly for the proxy in place... But never ever simply turn off security and try to install something through broken security. It defies the whole purpose of security and certificates if you simply turn it off or try to ignore it. -Gerald _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://secure-web.cisco.com/18iP3uSUcjHSqrMHO0qp7xLDZfU6UEQCIjFnQjNhiuLqlv… Archived at: https://secure-web.cisco.com/14EbakuFKJzXm1e5mfHMqLgTjYS9LSvDFEBHhhf-pvIniT… This message sent to henryhartley(a)westat.com * Please use caution when responding and/or clicking on links as this email originated from outside of Westat.

9 months

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/19/25 14:28, Cathryn McGuire wrote: > Hi Mark, > > 1. Since this post in July, I've been trying to work with EMWD to get the cc's blocked. I've tried every rule configuration in the Header Filter to no avail. EMWD can't seem to help. The setting options are as follows: > > Acceptable aliases > > This is a list, one per line, of addresses and regexps matching addresses that are acceptable in To: or Cc: in lieu of the list posting address when 'require_explicit_destination' is enabled. Entries are either email addresses or regexps matching email addresses.Regexps are entries beginning with '^ and are matched against every recipient address in the message. The matching is performed with Python's re.match () function, meaning they are anchored to the start of the string. What is the content of this? Probably should be empty. > 2. Require Explicit Destination (this is a checked box. Could it be interfering with the Header filters?) No, it doesn't interfere with header checks. > This checks to ensure that the list posting address or an acceptable alias explicitly appears in a To: or Cc: header in the post. > > 3. Default action to take when a member posts to the list > > Accept immediately (bypass other rules) > Default action to take when a member posts to the list. > Hold: This holds the message for approval by the list moderators. > Reject: this automatically rejects the message by sending a bounce notice to the post's author. The text of the bounce notice can be configured by you. > Discard: this simply discards the message, with no notice sent to the post's author. > Accept: accepts any postings without any further checks. > Default Processing: run additional checks and accept the message. NOTE - when set here, all members are blocked. What does Blocked mean? If you mean held for moderation, what is the reason they are held? > 4. We also have the problem of large image file sizes being let through no matter what setting we have. We have it set to 500KB, but everything is accepted. > > Maximum message size > 500 > The maximum allowed message size in KB. This can be used to prevent emails with large attachments. A size of 0 disables the check. > > Perhaps some settings are over-riding others? If you have Default action to take when a member posts to the list set to Accept, that bypasses this check and many others. > What do you think? What do you have in your header filter rules? More importantly, what are you trying to accomplish? I.e. what do you want to happen in the following cases? 1. Message To: the list, no Cc: 2. Message To: the list, Cc: to other address 3. Message To: somewhere else, Cc: to the list 4. Message To: elsewhere, Bcc: to the list (require explicit destination will hold this one) Maybe others? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Installing mailman 3

by Kyle Richardson

You shouldn't need to wipe all of the other directories. If you're following Simon's steps, the only one being used will be /var/lib/mailman. I would also double check that you don't have an instance of mailman3 running. The presence of the /run/lock/mailman file has me thinking you do. You can check with: # ps -elf | grep -i mailman If it returns results, you have an instance running and should stop or kill it. You can use the sledgehammer approach with: # kill -9 <pid_of_mailman_process> -Kyle On Thu, Jul 13, 2017 at 11:19 AM, Rafael Mora <rafael.mora.guti(a)gmail.com> wrote: > Dear Kyle, > > I did what you suggested and this is what I got: > [root@localhost ~]# rpm -qa | grep -i mailman > [root@localhost ~]# rm -rf /var/lib/mailman > [root@localhost ~]# find / -name mailman > /run/lock/mailman > /etc/selinux/targeted/active/modules/100/mailman > /etc/selinux/targeted/tmp/modules/100/mailman > /root/mailman > /root/mailman/src/mailman > /root/mailman/venv/bin/mailman > /root/dev/mailman > /root/dev/mailman/venv3/bin/mailman > /root/dev/mailman/mailman > /root/dev/mailman/mailman/src/mailman > /var/log/mailman > /var/spool/mailman > /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman > /mailman > /mailman/mailman > /mailman/mailman/src/mailman > /mailman/mailman/build/lib/mailman > > How do I wipe all other mailman directories? using rm -rf??? > > I don't think I can start with a brand new centos 7 for the moment. > > Thank you > [excessive, redundant quoting removed by moderator]

8 years, 7 months

[MM3-users] Re: No e-mail distribution after import of archive

by Mark Sapiro

On 11/12/24 00:52, Markus Grandpré wrote: > > In smtp.log I found: > > Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO > mailman-app-test.kim.uni-konstanz.de' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL > FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: > markus.grandpre(a)uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT > TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: > Import_mm3_testliste(a)mailman-test.uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost > during _handle_client() > > I have no idea why there is a "connection lost". What do you think? How > can I increase the log level? This is delivery of the message to Mailman. `connection lost` is normal and not a problem. This has nothing to do with your issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Creating superuser - problem with documentation or it's just me?

by Odhiambo Washington

On Tue, 28 Jul 2020 at 07:03, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 6:48 AM, Odhiambo Washington wrote: > > > So now I have tried to see if there is such option from django-admin, > but: > > > > (venv) [root@gw /opt/mailman/mm]# django-admin --help > > > You must run /opt/mailman/mm/bin/django-admin. If you run these commands > in your venv, you run the ones in /opt/mailman/mm/venv/bin which dont > have all the pointers to configuration and settings. It's OK to run > /opt/mailman/mm/bin/* with your venv active, but if you just give the > command name, you get the wring one. > So, I should run /opt/mailman/mm/bin/django-admin with a valid argument, right? Like /opt/mailman/mm/bin/django-admin createsuperuser ... How do I get all the available arguments for django-admin? That is what I was attempting to do by passing --help to it. > You also must have the empty /opt/mailman/mm/__init__py so that imports > of /opt/mailman/mm*.py modules will work as I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > This is quite clear now. Thank you. It wasn't clear at what point in the installation process this file needs to be created. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 7 months

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/2/21 12:48 AM, klillipuu(a)gmail.com wrote: > Hello All! > > I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. > So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). > I also mention, that hyperkitty is a pretty old version - 1.1.4. > The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. > Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? It would be good to upgrade. Current HyperKitty/Postorius/Django is Python3 which will remove your dependency on Python 2.7. Also, there have been many performance improvements in more recent versions which may solve your issue. Your gateway timeout issue is a uwsgi time limit. You can increase that in your uwsgi configuration. > Extra information: > * I have also noticed some memory violation issues which has caused by uwsgi. > * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Are these coincident with the gateway timeouts or do they occur at different times? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] DKIM header not added to subscribe/unsubscribe notification email

by Stephen J. Turnbull

Philip Colmer writes: > Everything seems to be working fine *except* when the system sends a > notification email to the list owners of someone subscribing or > unsubscribing. *Those* emails do not have the DKIM header added and are > getting trapped by anti-spam systems as a result. My guess is that the address Mailman uses for From in those messages is not in OpenDKIM's SigningTable. This is probably the $LIST-owner@$LISTDOMAIN address. You should also add the mailman@$LISTDOMAIN address. > I cannot see anything in the configuration for OpenDKIM or Postfix > that might allow just those messages to go out unsigned. Neither can we, although for a different reason. ;-) Please don't hesitate to send full configuration files to us on the grounds of absolute size or bandwidth. Such reports are relatively rare, they're not actually that big, and almost everybody on our lists are admins who know that it could be them tomorrow. Unfortunately at present I don't think you can send it as attachments. If you're worried about system security, you can either redact sensitive information such as passwords, domain names, mailboxes, and IP addresses, or you can send it to one of the developers directly (me, at the moment; Mark, when he gets back in a few weeks -- I believe Mark prefers a zipfile if there are multiple files, and I know I do) if you're willing to trust us. Steve

3 years, 6 months

[MM3-users] Re: Moving existing lists to a new domain

by Mark Sapiro

On 9/18/24 10:13, Jeremy Stanley wrote: > > Since all the lists for the given domain will be moving to the same > unused new domain on the existing server, and can move at the same > time, I suppose this could be done through (offline if necessary) > backend database update queries. Yes. For the mailing list, the only changes needed are to the mailinglist table; A query like ``` UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = 'old_domain'; ``` would do, but this leaves the question of list_id. According to RFC 2919, section 4, the list_id should not change, but this is problematic in that if it isn't changed, a Postorius URL like https://example.com/mailman3/lists/list_name@new.domain will retrieve the list, but https://example.com/mailman3/lists/list_name.new.domain will not work. It would need to be https://example.com/mailman3/lists/list_name.old.domain so to reduce confusion, it may be better to update the list_id values A query like the following after the above should do it ``` UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE mail_host = 'new_domain'; ``` For HyperKitty, similar changes need to be made to the hyperkitty_mailinglist table. The `name` column entries need to be changed from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column entries need to be changed from `listname.old.domain` to `listname.new.domain` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Confirmation emails aren't sent to users.

by Mark Sapiro

On 2/13/26 05:41, Ibiam Chihurumnaya via Mailman-users wrote: > Mark Sapiro wrote: >>> OK, this is Django. The default EMAIL_BACKEND from >> mailman_web/settings/base.py is >> django.core.mail.backends.smtp.EmailBackend and unless you've changed >> that or added overrides various other defaults are >> EMAIL_HOST = "localhost" >> EMAIL_PORT = 25 >> EMAIL_HOST_USER = "" >> EMAIL_HOST_PASSWORD = "" >> EMAIL_USE_TLS = False >> EMAIL_USE_SSL = False >> EMAIL_SSL_CERTFILE = None >> EMAIL_SSL_KEYFILE = None >> Are those appropriate? Do you have an outgoing MTA listening on >> localhost:25? What's in it's logs? > > I don't have any of those set, didn't realize I needed to have them set, the docs didn't make it obvious too. > I also didn't notice them in schema.cfg in mailman. You normally don't need to set any of those. The defaults should be fine for a local MTA listening on port 25, however what's in /etc/hosts for localhost. If it's the IPv6 address ::1, I suggest changing it to 127.0.0.1. > smtp_port is currently set to 25, and I do have an outgoing MTA listening on localhost:25. > Nothing shows up in the MTA logs about this particular email. Again, whats the address for `localhost` in /etc/hosts? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks

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

by Abhilash Raj

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

5 years, 7 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Onyeibo Oku

On Wed, 14 Oct 2020 08:53:23 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > > #!/bin/bash > exec /opt/mailman/mm/venv/bin/mailman \ > -C "/opt/mailman/mm/mailman.cfg" \ > $@ > Greetings Mark, I gave up on setting up mailman using option #2 while following https://docs.mailman3.org/en/latest/install/install.html (there are lots of unknowns on that route. Certainly, the packagers are considering a lot of things that are not immediately apparent to users). Perhaps, we will see elaborate guides/docs soon. In the meantime, I moved to option #3 (recommended for production). I hit a grey area when setting up the virtual environment. At https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, I see: $ cd /opt/mailman $ python3 -m venv venv The documentation imply that a 'user' creates the virtual environment but is not explicit about that 'user'. OUTPUT: Error: [Errno 13] Permission denied: '/opt/mailman/venv' This is expected. Which makes me wonder ... hmm, how did you do it? (1) Is it better to have a dedicated user (say 'mailman') then use that while following the docs? I see a lot of docs referring to a 'mailman' user. Installing mailman3 from distribution repository introduced a 'mailman' user to my box (with special UID). There has to be reasons for that. (2) Should the setup proceed with 'root'? (why do I get the feeling that this is not the design?) (3) How about using an already existing local user? What are the implications? Regards Onyeibo

5 years, 4 months

[MM3-users] Re: Installing Mailman3 on Debian Bullseye

by Franklin Weng

Hi Charlie, charlie derr 於 2023/8/26 19:43 寫道: > On 8/26/23 04:59, Franklin Weng wrote: >> Hi, >> >> >> After several times attempts I finally successfully build a (reliable >> enough) mailman3 instance on Debian. >> >> I had a blog article describing how I did it. Maybe there were >> something you find it ridiculous, but they are all what I found >> important and may not be shown in the current documents. >> >> >> https://blogs.slat.org/node/1012 >> >> >> Hope this helps. >> >> >> Franklin > > > Thank you Franklin. And also of course, thank you to all the folks who > work on and support mailman, as it's really wonderfully robust and > excellent software. > > TL;DR: we're interested in whether anyone has run into problems with > mailman3 on debian bookworm. > > Franklin, I'm curious as to why (at this point, with debian bookworm > having been available for several months as the current stable > platform) you wanted to do this. I'm asking specifically because the > team I'm a part of has worked with mailman for many years (but not yet > engaged with mailman3) as our main listserv answer for our users. We > do have a need to spin up a new mailman instance soon, and we were > planning on doing this with mailman3 on debian bookworm. If your > choice to stick with bullseye was because of problems with trying to > get things configured successfully on bookworm, we would definitely > like to know any specific details which have created issues. > > thanks so much in advance for any additional info, > ~c The problem was reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041681 AND here: https://gitlab.com/mailman/django-mailman3/-/issues/68 Not sure which it should belong to. There are screenshots in the bug report, but some users said they couldn't open our Nextcloud instance. If you have problems opening the screenshots too you can give me a private mail I'll send pictures to you. And - honestly I ran a mm3 instance on Debian Buster (10) a few years ago, and when I tried to upgrade my Buster to Bullseye the mm3 was totally broken. Fortunately I made a VM snapshot before upgrading so I reverted it back. However that instance was unstable too - it would run out of memory about every two weeks, so I had to setup a cron to reboot the VM every week. I have no idea what happened. It was pretty frustrated. Then we moved all our services to another server hosts and I decided to rebuild the mm3 instances. I tried to build-remove-rebuild several times, including building it on Bullseye but got a lot of database locked errors, then tried it on Bookworm and got a broken django admin page, and finally set up a pretty stable instance on Bullseye which has run for about 6 weeks without any problem. So I decided to share the progress and what I found. Hope it helps. Franklin

2 years, 6 months

[MM3-users] Re: Posting replies vs starting a thread via email

by paul＠arenson.org

Ugnius wrote: > Hi, Paul. For configuration, I would recommend to create separate list with own > addresses only, and to play a little. Thanks, but I am on hosted and cannot afford to create other lists. Just wanted to see what others did, or what Mailman 2 or 3 recommends. I am using https://www.emwd.com/mailman-3-shared-list-hosting/. I am not expert. I started to use DMARK option in > mailman version 2. Because I started to get issues with the Yahoo members. Yahoo stopped > to deliver messages from the list, when "reply to" was list address. DMARK made change in > "From:" Messages started to come for example from: "Paul via list" list(a)example.com. You should use setup good to your case, 1) Ah, I remember when we had that issue with a group I was hosting on Mailman 2. So maybe that is what I did. I guess to avoid problems with Yahoo and Gmail etc., it would be ok to use DMARC option. 2) It there a place where I can read about all the options? 3) then the latter part of my question had to do with DMARC MITIGATIONS. I do not understand the difference between selecting DMARC in ALTER MESSAGES and the choices available in DMARC MITIGATIONS. an you advice what settings to use or recommend a place where I can read about these? I currently have REPLACE FROM: with list and YES OR NO I have NO. Thanks!!!

6 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I installed whoosh, ran the server and got this: DisallowedHost at / Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Request Method: GET Request URL: http://192.168.1.42:8000/ Django Version: 1.11.3 Exception Type: DisallowedHost Exception Value: Invalid HTTP_HOST header: '192.168.1.42:8000'. You may need to add u'192.168.1.42' to ALLOWED_HOSTS. Exception Location: /var/lib/mailman/env2/lib/python2.7/site-packages/django/http/request.py in get_host, line 113 Python Executable: /var/lib/mailman/env2/bin/python2 Python Version: 2.7.5 Python Path: ['/var/lib/mailman/env2/lib/python2.7/site-packages/django_q', '/var/lib/mailman/mailman-suite/mailman-suite_project', '/var/lib/mailman/env2/lib64/python27.zip', '/var/lib/mailman/env2/lib64/python2.7', '/var/lib/mailman/env2/lib64/python2.7/plat-linux2', '/var/lib/mailman/env2/lib64/python2.7/lib-tk', '/var/lib/mailman/env2/lib64/python2.7/lib-old', '/var/lib/mailman/env2/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7', '/usr/lib/python2.7', '/var/lib/mailman/env2/lib/python2.7/site-packages'] Server time: Fri, 21 Jul 2017 23:35:16 +0000 Where's the ALLOWED_HOSTS file???? El vie., 21 jul. 2017 a las 16:32, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 02:27 PM, Rafael Mora wrote: > > > > it says it needs whoosh > > > > How do I install that? on env2 with python2 or env with python3 ??? > > > In env2 do 'pip install whoosh' > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

[MM3-users] Re: Confirmation Mail not getting after logging in

by Odhiambo Washington

On Thu, Oct 9, 2025 at 3:18 PM nirmal--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > I have installed mailman3. But after logging in I am not getting > confirmation mail. The message displayed is hereby follows:- > example.com > Search all lists > Sign In > Sign Up > Manage lists > ×Confirmation e-mail sent to nirmal(a)iitm.ac.in. > Verify Your E-mail Address > We have sent an e-mail to you for verification. Follow the link provided > to finalize the signup process. If you do not see the verification e-mail > in your main inbox, check your spam folder. Please contact us if you do not > receive the verification e-mail within a few minutes. > I would say the fact that you are still seeing example.com also means you haven't strictly followed the installation instructions. That domain, example.com, while not such a major issue, means you've not edited your settings.py. Besides that, you should have tested your Postfix configuration (or your MTA) to ensure that it is capable of sending emails to the outside world. In fact, a functional MTA is a prerequisite for MM3. So at this juncture, check your MTAs logfile. -- 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, 3 weeks

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

by Mark Sapiro

On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: > I'm trying to set up mailman3 on two hosts, one of which runs core + > exim, the other runs postorius (&possibly hyperkitty). > > I have I think got core set up correctly, and postorius is sort of > usable, but anything in the web ui that talks to core ends up with a > white screen. > > I think what is happening is a postorius URL ends up with the core (or > perhaps no) hostname, and as there's nothing there to answer it fails. 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? > I've checked the settings and I don't think I have misconfigured > postorius. Is it possible that the bad url is being passed from core to > postorius in some way and reused without changing the host? > > In the config at present, both hosts are visible to the browser, and > each host can communicate with the other. > > Any ideas on how to pin down the problem better? Do you see REST requests from the Postorius machine in core's mailman.log and access.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Change Member's Address

by Mark Sapiro

On 1/13/26 9:08 AM, dap1--- via Mailman-users wrote: > I got a different user set up as superuser using a gmail address. However, I get to the member's management page but cannot change anything. I see update buttons but they don''t seem to so anything although I get a banner at the top saying the user was updated. What am I doing wrong? You can't change the user's address that way. You can only update the display name, the verified status of the address and the moderation and delivery mode of subscriptions. I think you can do it in `mailman shell` like this ``` $ 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. >>> um = getUtility(IUserManager) >>> addr = um.get_address('address_to_change') >>> addr.email = 'new_address' >>> commit() ``` However, the preferred way is for the user to log in, go to https://whatever/accounts/email/, add the new address to their account, make it primary, go to the list info page at https://whatever/lists/LIST, and if their Subscription Address is still the old address (because they weren't subscribed by primary address), click Manage Subscription and change it, and then possibly remove the prior address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Odhiambo Washington

On Thu, Mar 30, 2023 at 6:55 PM Zaheer Abbas <zaheer.psg(a)gmail.com> wrote: > Hi All, > > I need to whitelist a domain for a specific mailing list on your platform. > Only *(a)example.com email addresses should be allowed to post messages to > this list. > > Could you please provide me with documentation or instructions on how to > achieve this? I have already searched the knowledge base and user manuals > without success. > > I believe it was previously available in mailman2 > via Accept_these_nonmembers attribute. > > But I cannot find this attribute anywhere on postorius. > > I am using mailman 3.2.2 > > Any help would be really appreciated. > > Best regards, > I would do this at the MTA level with either a router or a filter (milter in Postfix lingo): IF $sender_address_domain IS NOT "example.com" AND $recipient is "listname@domain" THEN send-to-dev-null. Exim (MTA) has a filter plugin to do this. I don't know about Postfix and Sendmail (as I am not willing to read on your behalf). It is easier that way. I don't remember is Mailman3 has the logic to deal with that, but maybe it does. If you did not manage to find it, then my solution is plausible, no? Filter at the MTA level. -- 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: Does mailman2 regular_exclude_list equal mailman3 receive_list_copy ?

by Stephen J. Turnbull

Did you ever get an answer to this? I was short of round tuits so left this in the inbox, but maybe you already have the answers. sunil soprey writes: > Do you plan to reintroduce the de-duplication feature so that if a > mail list subscriber is on multiple email lists that are cc'd/bcc'd > they only get the message one time? Yes, it's desirable. However, the question is actually quite complex because a 'User' may have many 'Address' entries. Here, does "subscriber" mean 'User' or 'Address'? I can see it going both ways. Some users have many addresses, all except one are pure forwarding, and they only want to read the email once. Other users have separate addresses for separate roles, and they want to have that message for context in each role even if they have read it before. Hashing this out means it will take us some time to get it into a release. (That's IMO, I defer to Abhilash as project leader and Mark as having more experience if their opinions differ.) Of course we could implement "de-dup" with the subscriber = 'Address' interpretation immediately, which provides substantial relief for many users, and later add a User config option for "Also de-dup equivalent addresses" for some definition of "equivalence" (I can think of two implementations already, that's what I do, complexify things ;-). > Are you aware of solutions feature outside of Mailman3 core? Say > filtering in postfix-mta? (might complicate tracking of dups in > postfix) I'm sure there are no such. It's much simpler to implement in Mailman core because you don't need to deal with transporting Mailman to filter and filter to MTA, and more reliable to implement in core because Mailman knows a lot more about both subscriptions and messages than you could deduce from the message itself. It's not impossible, of course, but I think it would be hard to implement well. > For "mailman core", could we filter in outbound send of mailman? > Example - could the processing pipeline be modified to > track/discard duplicate msgs? I'm not sure what you mean by modifying the processing pipeline, but the basic idea is pretty clear. At some point the list name has to be expanded into a list of addresses. This is done by a specific handler in the pipeline, and the filtering will be done at that time. There are a number of possible implementations. We'd start by looking up all of each subscription's list affiliations when we look up the subscription configuration. In some cases we could create addressee lists for all the relevant mailing lists at that time, then send the message to the outgoing pipeline of each list to be decorated appropriately, but I'm not sure whether it's worth trying to do that. We'd also have to keep a record of lists of addresses (or Users) wanting de-duplication identified by Message-ID for some period of time in case the sender's MTA sent the message multiple times rather than providing multiple recipients in one transaction. Steve

5 years, 8 months

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

by Stephen J. Turnbull

joseverde(a)gmail.com writes: > 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…) That's not our guide, we don't support it, and at least I don't recognize the author offhand, can't speak for the rest of the team. Now that our NO WARRANTY notice is out of the way, I will say that guide is written in very good style, with great attention to detail and appropriate warnings about delicate parts of the procedure. If you end up succeeding with it, I'll add a link to it to our docs. > to install the Mailman3 package and got to the configuration screen > (the one with all the DOS-esque GUI). That's Ubuntu's UI, not ours. Your questions so far are all really Ubuntu questions, not Mailman questions. We'll do what we can to answer, but I don't think any of the core developers use Ubuntu packages to manage their Mailman installations. You are likely to get more help, more accurate help, and faster help in Ubuntu (or perhaps Debian) channels. > I ran it but it kept saying the DB wasn't installed. Mailman can use any of several database backends (at least SQLite3, PostgreSQL, and MySQL). It seems possible that Ubuntu Mailman is configured for one, and the preinstalled one is another. Which SQL implementation was preinstalled, and which one are Mailman and Django configured to use? > 1. Does that guide actually work? Ask the author, not us. Internal evidence (quality of presentation, dates, the NOTE at the top) strongly suggests it works for somebody. > Did I just foul up the database part? Not clear what got fouled up or where in the process, but clearly getting database installation and configuration right is necessary to proceed. > 2. Is there a better way to install mailman3 with some nice > step-by-step directions to follow? Don't know. We provide docker containers, but I don't know if those are compatible with Digital Ocean's droplets. Our docs are at mailman.readthedocs.io, but they're not step-by-step the way the guide you reference is because they're distribution- agnostic, and generally oriented toward a build from source. > 3. Is there a way to completely wipe my previous installs without > wiping the server? ( I didn't back up...silly I know ). Just wipe the server and create a backup image. Multiple, if you have the space for one every time you successfully install and configure a subsystem. You will save yourself a lot of time. dpkg --purge will wipe out the Mailman stuff, but if your config process touched anything else (the database, the MTA config) rerunning the process is not guaranteed to do the right thing. It probably will do the right thing, but why not be sure you have a reset to known state? Steve

5 years, 7 months

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

by Odhiambo Washington

On Tue, 28 Jul 2020 at 06:50, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/20 4:29 AM, Odhiambo Washington wrote: > > On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Is there an empty /opt/mailman/mm/__init__.py file? > >> > > > > No. > > > There has to be one. Create it and then Django will be able to import > your settings. > > See the first line after > > Create directories: > ... > and files: > > at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69 > > > I don't know why I didn't see that initially :-) > > Yes. However, that also means the /opt/mailman should be owned by > mailman3, > > right? So I wasn't quite mistaken. > > > It doesn't matter what user actually `owns` this directory and its > subordinates as long as the Mailman user, mailman3 in your case, can > read and write there. Of course, making everything owned by the Mailman > user is the easiest way to ensure this. > True. > > Note also that any commands in /opt/mailman/mm/bin need to be run as the > Mailman user and not root. Running them as root can create things owned > by root the can't be read by the Mailman user. > So, now I remember why I had to chown -R mailman3 /opt/mailman Then now it seems like I have been doing things incorrectly, because I have been doing a lot of operations as root by simply: cd /opt/mailman/mm virtualenv venv source venv/bin/activate Looks like the correct way is to start with su - mailman3 > > PS: There is the issue with qcluster, which doesn't seem to have been > > documented in details from your "experience". > > I see the configuration file and the init script, but not how to install > > it, or whether the procedure already installed it. > > > qcluster is part of Django. If you have this > > # > # Asynchronous tasks > # > Q_CLUSTER = { > 'timeout': 300, > 'save_limit': 100, > 'orm': 'default', > } > > or similar uncommented in your Django settings, and also 'django_q' in > your INSTALLED_APPS, it's there and all you need to do is run > > /opt/mailman/mm/bin/django-admin qcluster > > to run it, but it should be run as a service via init or ?? > I have run it from supervisord. It has forked 30 processes and refuses to kill them when I stop supervisord. I will look for options around it. Answering my own question I asked earlier, I have found "django-admin help --commands" to answer it. PS: Did you by any chance find time to look into the issue about wsgi.py that you had mentioned - the one that has me stuck using it?? Thanks again. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 7 months

[MM3-users] Re: No e-mail distribution after import of archive

by Odhiambo Washington

On Tue, Nov 12, 2024 at 11:52 AM Markus Grandpré < markus.grandpre(a)uni-konstanz.de> wrote: > Dear Mr Odhiambo, > > thank you very much for your reply. > > In mailman.log I see: > > Nov 12 09:46:02 2024 (698086) ACCEPT: > <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de HTTP/1.1" > 200 486 "-" "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de/config > HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/users/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU > Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner > HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/addresses/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 436 "-" > "GNU Mailman REST client v3.3.5" > [12/Nov/2024:09:46:03 +0100] "GET > /3.1/lists/ > import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator > HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" > Nov 12 09:46:03 2024 (698083) HyperKitty archived message > <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> to > > https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_te… Is that ALL you have from mailman.log for today,? I was expecting more - like some task runners being logged. In smtp.log I found: > > Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO > mailman-app-test.kim.uni-konstanz.de' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL > FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: > markus.grandpre(a)uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT > TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: > Import_mm3_testliste(a)mailman-test.uni-konstanz.de > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost > Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost > during _handle_client() > > I have no idea why there is a "connection lost". What do you think? That 'connection lost' is normal. So there seems to be communication from mailman to your MTA. What do you see in your MTA (Postfix?) logs when you send an email to the list? > How can I increase the log level? > Actually, you do not need to, but mailman.cfg complete documentation is here: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… -- 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: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:36 -0800, Mark Sapiro wrote: > > Why do you say the .mo files are old. The timestamps are all Feb 3 > 02:47 which is when the package was built for PyPI. Because my brain goes faster than my fingers and I say the reverse of what I mean. I meant .mo files, all .po where properly dated, and I reversed the meaning of my thoughs while typing. Thanks for brining my confussion to my (and everybody's) attention, and my appologies for the noise. > When things are changed on weblate, we get automatically generated > merge requests to update our source. We don't always merge them > immediately, but we certainly do merge all the outstanding ones > before making a release. I'm 95% certain that I edited messages after Nov 7th in the Spanish translation of both mailman, postorius and hyperkitty, but the .po file is dated Nov 7h. Actually, I did a review of outstanding strings when Abhilash annonced the RC for the current version. That is why I was bit surprised. But then, it may be me and my faint memory. And, of course, I'm very grateful and happy with all the work that is being done on Mailman3. -- 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 ?

5 years

[MM3-users] Re: Advice on migrating to Mailman 3

by Mark Sapiro

On 2/13/20 2:02 PM, Christoph Groth wrote: > > The only problem is that our list runs on Mailman 2. We would like to > move to Mailman 3, but this does not seem to be that simple. Perhaps > someone here would be so kind to give us advice? I think it's pretty simple, but I've been a Mailman developer for 15 years ;) > The number of (shared) hosters who offer Mailman 3 seems to be very > limited [3]. Would it be a good idea to book a virtual private server > (VPS) somewhere, that runs, say, Debian, and simply install Mailman > 3 through the distribution’s package system? I’m already running > a small personal box with nginx on it, and this is very little work, but > running Mailman would require sending out up to a few thousand email > messages per day (our list has a few hundred subscribers). Is this > something that one is commonly allowed to do on a VPS system? Most VPS > offers that I see are silent about mail. This list is on a VPS hosted by RackSpace. mail.python.org which hosts hundreds of lists is a VPS hosted by DigitalOcean, and my bicycling club's web site, email and mailing lists are on a VPS also hosted by DigitalOcean. These servers all run some version of Ubuntu, but because we are developers, they do not use the Debian/Ubuntu packages. They are all installed from the heads of the GitLab branches and kept pretty much up to date with those. All three servers use Postfix as an MTA. We have no issues with mail volume per se. What you will see with a new VPS is your IP being blocked by various ISPs. It takes a bit of communication and patience to work through these blocks, but once you develop a good reputation, they tend to go away. > If we setup such a system, can we assume that it will silently operate > without causing much administration work most of the time (like my nginx > server)? Or is maintaining a Mailman 3 server a significant burden ([2] [2], or [3]? > seems to imply that)? If yes, are you aware of organizations that > propose Mailman 3 hosting for open source projects? Python.org seems to > host some lists for third party projects, but otherwise I haven’t seen > much. I don't think a Mailman 3 installation needs an undue amount of baby sitting. I do run daily reports that list the contents of mailman's queues (normally empty, but messages in the shunt queue need investigation) and grep a couple of logs for errors. mail.python.org hosts lists for Python related open source projects. Kwant seems to be eligible. Ask postmaster(a)python.org specifying the desired list name and name and email address of the initial list owner(s). However, we don't normally import lists or archives from elsewhere. > [1] https://kwant-project.org/ > [2] https://mailman-mail5.webfaction.com/listinfo/kwant-discuss > [3] > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Log rotation

by Darren Smith

Hey everyone, So I have a question about log rotation... Our mailman.log has grown to over 5 gigs. It's time to add this to log rotation. We added what we thought might work to the /etc/logrotate.d/mailman script, but when we ran it with a -f, we learned that the -f flag doesn't keep old logs. That in itself is fine - a normal scheduled log rotation won't have that problem. My problem is that doing the rotation caused the mailman not to be able to write to the log anymore. It appears that it no longer has a handle to the file. To overcome this with, say, nginx, there is a command in logrotate that you can add that restarts the service. I have found, however, that restarting the mailman service can be VERY problematic. There is so much going on that it takes a very long time to stop, and I have seen several instances where the service never shuts down cleanly - even after 3-4 minutes. The service thinks it is shut down, but there are several threads that haven't yet completed. If they are killed, then you have to go clean up the master.lck files etc. It seems like a bad way of doing things and a good way to somehow corrupt data. Anyway - after rambling... 1) Has anyone come up with a good log rotation strategy that doesn't necessitate a restart of the service? 2) Has anyone seen problems stopping and restarting the service? Is there a way to help with this problem? Thanks, Darren

7 years, 10 months

[MM3-users] 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 working through other threads that indicate the same > symptom (500 error when loading held_messages for a list). You want threads that deal with Unicode: > Error reported in log with debug enabled: > > Traceback (most recent call last): And that last call is:: > File "/usr/lib/python3.6/email/message.py", line 315, in set_payload > payload = payload.encode(charset.output_charset) > UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) It appears that the message is improperly constructed, and either a Content-Type field has a omitted or inappropriate charset parameter, or perhaps the Content-Type field is omitted entirely (ASCII is the default charset). This is frequently a problem created by spam messages. The message should be in the shunt queue. You can examine it with the command "mailman qfile /path/to/message_file.pck". Unfortunately it's not clear from the backtrace where in the message this is: it's at the beginning of a part ("position 8-9") or maybe line, but the part could be late in the message. If it's spam, you can just delete the file (and do whatever else you do about spam, of course). If it's not spam, it would help if you can guess what language and charset are being used in the message, and we can go from there. If this is unclear, feel free to ask more.

5 years, 6 months

[MM3-users] Re: Strange password problem

by Eggert Ehmke

Am Freitag, 22. September 2023, 19:34:41 CEST schrieb Mark Sapiro: > On 9/22/23 09:50, Eggert Ehmke via Mailman-users wrote: > > -I try to log in as admin > > -rejected because of wrong password (password is stored in browser) > > -used forgotten password function, using my email address > > -reset password to the stored value from browser > > -login works now. Works also when logged out/in again > > -however, the next day this behaviour repeats. > > So apparently the issue is that although you reset your login password > to a known value, it doesn't stick and reverts overnight to some other > value. Yes that it looks like. > Is this the Debian package or installed following > https://docs.mailman3.org/en/latest/install/virtualenv.html or something > else. Yes it is a virtualenv installation following that guide. > All I can think of is some cron may be resetting the password. If that's > it, it's probably a Debian thing. Can you see if there's any cron > running the Django admin changepassword command? Will try to find that. > If you set the password with the Django admin changepassword command, > does it stick? Never tried that, how do I do that? > Can you create another superuser with the Django admin createsuperuser > command and does that user's password stick? Will try that. So I can create another superuser? Does it need a separate email address? I guess yes Thank you for your ideas.

2 years, 5 months

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

by Stephen Daniel

TL;DR: Listening to the advice, I will create and manage user/address pairs. I am in the process of porting a web site that is used to manage a small organization. The web site maintains a directory of users of that organization, and also allows them to subscribe/unsubscribe to a small set of interest-group mailing lists for that organization. The users are not tech savvy, and are not expecting or expected to manage their subscriptions through Postorius, nor do they have access (normally) to the archives. Indeed, the URL to Postorious will normally be turned off at the reverse proxy server that sits in front of both Postorious and the organization's website. The one-source-of-truth is the website's database. The website code has callouts for "subscribe <address> to <list>" and "unsubscribe <address> from <list>". I am trying to minimize the amount of code I write to implement the web site's callouts, to initialize the mailing lists when I port the organization to this new implementation, and make it relatively easy to keep the website's database and mailman3's database in sync. The impression I had from the docs was that unlinked addresses were a first class object. Since my website callouts only deal with addresses, this seemed a good mapping. However, I understand from this email thread that unlinked addresses are not the way to go, so I'll map <address> in the website database to <user>/<address> in mailman3. Thanks for the advice and feedback! -- Stephen Daniel On Sat, Jan 15, 2022 at 2:27 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/15/22 10:03 AM, Stephen Daniel wrote: > > > > The only way I've found to create a standalone address (not linked to any > > user) is to create a user with that address, unlink the address, then > > delete the user. > > > > Is there a more straightforward way to just create an address with no > user? > > > The more straightforward way is via the IUserManager create_address > method. This method is not exposed directly in REST, so you can't do it > via REST. > > My question is why do you want to? > > Granted when an unknown nonmember address posts to a list we create a > standalone address record, but maybe we should be creating a user too. > We don't because it's tricky. Suppose User A with address A posts to a > list from nonmember address B. We create the standalone address B record > as a nonmember, but now user A can add address B as another address. If > we also created User B, this would not be possible. > > But again, what is your use case for creating standalone addresses? > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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] My Server is unable to connect to Mailman REST API few times

by Stephen J. Turnbull

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.

5 years, 5 months

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

by John Covici

I have a couple of questions about the container, if its OK. First, it says to run you create the directory /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the git clone. What directory should the git clone be in? A couple of more questions -- is there a way to install the web server and the mta in the container, this way I could make the whole thing be independent of my host configs? On Fri, 30 Jul 2021 16:04:48 -0400, bob B wrote: > > is this the info you need for the container version > > [root@..... docker-mailman]# docker ps > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1 > > > for smtp host > ------------ > cat /opt/mailman/web/settings_local.py > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > ALLOWED_HOSTS = ['*'] > DEBUG = True > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'smtp.example.com' > EMAIL_PORT = 25 > --------------------------- > cat /opt/mailman/core/mailman-extra.cfg > # mailman-extra.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > # mailman-core hostname or IP from the Postfix server > lmtp_host: localhost > lmtp_port: 8024 > # Postfix server's hostname or IP from mailman-core > smtp_host: smtp.example.com > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: my_real_email_is_in_the_file.com > __________________________________ > > My docker most machine /etc/postfix/main.cf has > > transport_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = > regexp:/opt/mailman/core/var/data/postfix_domains > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > ------------------------------ > > > > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server? > > > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 7 months

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

by Mark Sapiro

On 10/9/23 22:50, Mark wrote: > > 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: Steve has addressed your issues with multiple Django admin commands, some of which apparently don't reference the correct settings. > 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? It is not a clue as to the problem. The format of that `representation` changed in HyperKitty 1.3.5. What is your version? What happens if you do, with the appropriate Django admin and list name, ``` python3 manage.py update_index_one_list thepost(a)example.com ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: The Use of Hyperkitty as a Forum and Archiver

by Allan Hansen

I can echo Mark’s responses exactly, as well as the sentiment that it’s WAY WAY WAY better. One additional item of praise: The ability to post/respond to messages from within HK(I guess what you refer to as the ‘forum’ feature) is way cool. While I’m at it here are also some small and not so small gripes: a. The link for visit ’the archives’ is embedded in a sentence. It should be an icon like ’Unsubscribe’. While we’re on that page, the same goes for ‘your list options page.’ b. On entering HK, when listing ‘Recent’, etc, the author is not listed. c. Why is ‘Manage subscription’ an option on this page? The ‘Manage this list’ in the header already has this link. And it appears in the list of options on which threads to show. ????? d. When listing ’Threads by month’ and ‘All threads’, the left panel is taken over. e. When I log in as admin, I get a ‘Delete’ button on this page as well. There is no mention of what it does. Does it delete the list, the archive or the shown threads (I assume the list, but why is this button here???). f. The activity summary here is irrelevant to most users and should be just an optional display. g. Sometimes the lists are listed by Postorius and at other times (at login) by HK. The displays by Postorius are much better and cleaner. The listings by HK use too much real estate for the ‘Activity in the past 30 days’ graphs, which really are just fluff. The difference in presentation between Postorius and HK is confusing and confounding. Thank you for the reminder, Brian. I’ll send out a note to my lists’ members to remind them of this very improved tool. Yours, Allan Hansen hansen(a)rc.org > On Jul 14, 2020, at 8:48 , Mark Dadgar <mark(a)pdc-racing.net> wrote: > > On Jul 14, 2020, at 6:51 AM, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >> - Has the forum feature (Hyperkitty) of MM3 been received well by your list members or is it mostly ignored? > > Pretty sure no one even knows its there, even though I told them when we migrated to MM3 originally. > >> >> - Do you see an increase in the use of HK as a forum from your list members? > > No. > >> - What kind of feedback have you received from your list members considering the forum function of MM3? Positive or negative? > > None. > >> - Do you think HK is received well by your list members as an archiver and do you think it provides a better user experience for viewing/searching archives vs Pipermail of MM2? >> > > WAY WAY WAY better experience than Pipermail. The single most common feedback about the archives under MM2 was “the archives are broken - search can’t find anything.” htdig was not a great indexer. > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > _______________________________________________ > 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, 7 months

[MM3-users] Re: Run a mailman program outside of mailman shell

by Odhiambo Washington

On Tue, Jul 23, 2024 at 11:18 PM Greg Newby <gbnewby(a)petascale.org> wrote: > Hi again folks. I have hundreds of lists to convert from MM2.1 to MM3, and > intend to write a Python program do this this rather than running commands > in mailman shell (and rather than running 'command()' functions in mailman > shell, if possible). > > However, when I write a simple Python program to run the types of commands > found in the Mailman docs, such as these > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > >, > I get errors. This is a venv installation, following these instructions > <https://docs.mailman3.org/en/latest/install/virtualenv.html>. The > Mailman3 > installation is working fine and I have a handful of lists in production > that I set up manually. > Okay. Not to go against your favorite method, but looks to me that you're killing a feal with a hammer! I had some 10 lists to migrate from MM2 to MM3 and I simply did the migrations using bash a shell command line. for l in list1 list2 list3 ...listN; do blah blah; done ...as documented here: https://docs.mailman3.org/en/latest/migration.html -- 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, 7 months

[MM3-users] Using it with the "smtp2go" email relay service that has special deliverability rules

by golden_rock＠hotmail.com

Hi, Smtp2Go relay service enforces a few rules for deliverability: The From: address domain has to be verified in smtp2go The sender envelope address also has to be verified in smtp2go So emails sent by mailman don't get relayed because mailman sets From: to be the original sender of the message, and it means anyone that wants to send to the list would have to approve themselves with smtp2go first, which is not workable. To make it work, I would have to have something like: Sender: bounce-address(a)lists.mailman3.org - untouched From: original.sender@gmail.com@lists.mailman3.org - change #1 having the From address to be From the list Reply-To: original.sender(a)gmail.com - change #2 - if someone replies Then smtp2go will send the email. I looked in the settings and I didn't find a readily available option to do that. I'm new to customizing mailman3 , but have been using it in production for a little more than 1 year. I've seen other software do the solution proposed above, namely DIvi contact forms set the "From" to be something @website.com and the Reply-To: as the form submitter. I am told that the standards is moving away from forging the DATA From: that doesn't have a predictable domain, and instead put the variable email address in Reply-To, for things like contact forms or automated sending. Can someone guide me on where I could start looking?

3 years, 1 month

[MM3-users] Re: Can't add emails to accept_these_nonmembers

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/25/26 2:43 PM, Ibiam Chihurumnaya via Mailman-users wrote: > > I need to set some nonmembers to a list as these members send message to the list, but don't need to receive any message from the list. > > I've used list_name.settings['accept_these_nonmembers'].append to add members to the list, but it gets discarded once I run list_name.settings.save(). accept_these_nonmembers is a list hence the append, I didn't add the argument to append, maybe that's what caused the confusion. > > I don't understand what you are doing. The above makes no sense to me. > Please provide more detail on exactly what it is you are doing. > However, accept_these_nonmembersis an artifact from Mailman 2.1 and > only exists in Mailman 3 to support patterns as opposed to individual > email addresses. > In Mailman 3, there are two ways to accomplish this. One way is to > subscribe the user as a member and set the member's delivery to > disabled. The other way is to add the user as a nonmember and set the > nonmember's moderation_action to default processing. I had done the members part in the past, but the issue with it was I wanted certain members to not receive messages from the list, but only send to the list. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 1 day

[MM3-users] Re: Migrating mailman3 to latest ubuntu lts

by Stephen J. Turnbull

Helio Loureiro writes: > Well... not that good. Now it is mailman3-web that doesn't work. > > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check > System check identified no issues (0 silenced). > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate > Traceback (most recent call last): [omitted] > LookupError: No installed app with label 'migrate'. > > Any idea why migrate isn't working and saying it is installed? Management commands aren't applications, so they wouldn't be valid arguments to "mailman-web check" in any case. Try "mailman-web check postorius" or "mailman-web check hyperkitty" to see how the application argument works. You should get the report "System check identified no issues (0 silenced)." as above. Then try "mailman-web migrate -h". If that returns help output, the migrate command is installed and can be run (the help string is part of the migrate module, not part of mailman-web itself). Why do you think "mailman-web migrate" isn't working? Most likely "migrate" is working as designed, but it is doing nothing because something about the way you transported the database originally caused mailman-web to think its database schema is up-to-date even though it is not (as happened with the mailman database). Unfortunately this database is managed by Django, not by Alembic, and I don't know offhand how to discover and tell Django the actual schema version and then ask it to run any new migrations. Steve

2 years, 2 months

[MM3-users] Mailman3 Docker persmission denied

by Commander456

Hello everyone, I recently installed the mailman-core Docker image (Version 0.5) and tried to create a list using the mailman commands inside the container. I used the --notify argument but doesn't receive any mail (I'm the list owner), However, inside the mailman.log I get the following error: Jan 06 20:54:25 2025 (156) Uncaught runner exception: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' Jan 06 20:54:25 2025 (156) Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/mailman/core/runner.py", line 164, in _one_iteration msg, msgdata = self.switchboard.dequeue(filebase) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mailman/core/switchboard.py", line 150, in dequeue with open(filename, 'rb') as fp: ^^^^^^^^^^^^^^^^^^^^ PermissionError: [Errno 13] Permission denied: '/opt/mailman/var/queue/virgin/1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8.pck' Jan 06 20:54:25 2025 (156) Skipping and preserving unparseable message: 1736196864.6488764+2c5d24f89f86715d3deb3d0032735050cb9e29f8 These are my file permissions: mailman-core:/opt/mailman/var/queue# ls -l total 48 drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 archive drwxrwx--- 2 mailman nogroup 4096 Jan 6 20:54 bad drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 bounces drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 command drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 digest drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 in drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 nntp drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 out drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 pipeline drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 retry drwxrwx--- 2 mailman nogroup 4096 Jan 6 17:11 shunt drwxrwx--- 2 mailman nogroup 4096 Jan 6 20:54 virgin mailman-core:/opt/mailman/var/queue/virgin# ls -l total 0 Do you have any idea what I'm doing wrong? Thank you

1 year, 2 months

[MM3-users] Re: Creating superuser - problem with documentation or it's just me?

by Odhiambo Washington

On Mon, 27 Jul 2020 at 02:01, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 9:39 AM, Odhiambo Washington wrote: > > Hi, > > > > In my quest to create a superuser, I followed another HOWTO - > > https://docs.mailman3.org/en/latest/devsetup.html > > > > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# > > python manage.py migrate > > Traceback (most recent call last): > > manage.py migrate (or django-admin migrate) is part if the > mailman-post-update script. It doesn't work here because when you run it > this way, it doesn't get your settings.py. > I have taken note of that. Thank you. > ModuleNotFoundError: No module named '_sqlite3' > > And it's looking for sqlite3 because that's the default database. > > *<==============================================================* > > (venv) [root@gw /opt/mailman/git/mailman-suite/mailman-suite_project]# > pip > > install pysqlite3 > > You don't need this. You need to run django-admin with the correct > settings. > Thanks for clarifying. > So I figured out that I need to put my own settings_local.py into the > > directory and let the command rely on MySQL as the database backend since > > by default, it uses sqlite3 backend. > > > > But the question then is WHY is this not documented on the above page??? > > > Because that's not relevant to what you are doing. You are trying to > install Mailman for production, not development. > Okay. That is true. > > How can I delete the superuser after creating it?? > > > The only django-admin or manage.py you should run is > /opt/mailman/mm/bin/djhango-admin. You can run `django-admin > createsuperuser` to create a superuser. If you want to delete one, you > need to go to the Django admin web UI - should be > http://your.server/admin - login as a superuser and go to the Users page > and delete it. You should probably do this as a different superuser > The reason I asked for how to delete superuser came from the fact that from the above confusion, I needed to create a superuser. So now I have tried to see if there is such option from django-admin, but: (venv) [root@gw /opt/mailman/mm]# django-admin --help Type 'django-admin help <subcommand>' for help on a specific subcommand. Available subcommands: [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate runserver sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver *Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.).* (venv) [root@gw /opt/mailman/mm]# So is something wrong with my settings???? I do not see the command to create the superuser listed. My settings_local.py has got only the bits from settings.py that I have customized. Thank you for your patience. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 7 months

[MM3-users] Re: Trying to configure a list (hosted)

by Abhilash Raj

On Sat, Aug 31, 2019, at 7:05 PM, paul(a)arenson.org wrote: > Thank you for the very quick response, Abhilash Raj. Being non > technical (and therefore opting for hosted Mailman 3), I can partly > understand your kind response. > > 1) I can understand that I cannot disable the different ways to sign up. > > 2) I am still struggling to understand the difference between the two > web choices as shown here. > > WAY # 1 TO GET AN ACCOUNT > https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… > > VS > > WAY # 2 YOU CAN GET AN ACCOUNT WITHOUT SIGNING UP > at the bottom of > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > (I was under the impression making only WAY #1 allows one to post, but > are you saying that the bottom option also allows one to post, but only > by email?) That's right. Mailman is a mailing list manager and is primarily based around discussions using Emails. You can subscribe to mailing lists and send email to the list address, which then gets distributed to all the members. All the emails sent to the mailing lists are also archived usually in an archiver. The official archiver, a.k.a the one supported by us, also additionally supports posting to the mailing list via the Web interface. If anyone wants to use the web ui to post, they need to have an account and need to verify that they own the email address they are signing up with. Then, anything they post is sent as an email, on their behalf, to the mailing list and that's how you can get 2 ways to post. You don't need any account on the web interface if all you want is to post through email. > If I am confused, I know my users will also be confused. I think I > understand I can qualify their subscription in the ways you suggest: > "Confirm where all users would have to confirm their subscription using > an email sent to them. Optionally, you can also enable moderation where > each subscription needs explicit approval too." > > So to put it simply: > > 1) I want to make it a discussion list. Not available to people who are > not signed up? It is slightly confusing, but let's separate sign-up into two terms and let me know if that is still confusing, "sign up to web interface", "subscribe to mailing list". - sign up to web interface: This is optional. This allows you, as an administrator to operate the mailing list and it's configuration. A user can sign up to the web interface and manage all the subscriptions they have, and also subscribe to mailing lists. - subscribe to mailing list: This is a user participating in a Mailing List. For this, they don't necessarily need to sign up via web interface as there are other ways to subscribe to a mailing list, like anonymous subscribe (which is your #2 above). Once they are subscribed, they are called "subscribers". Users will always have to "subscribe" before they can participate on a mailing list. There is currently no way to mandate "sign up on the web interface" for all "subscribers". > > 2) This is dependent on all having access to the archives so they can > see what they are responding to If the archives are set to be private, only the "subscribers" can view the archives. > > 3) What settings do I make to insure that all who sign up via WAY #1 > can see the archives and post. You have to set the archives to be private and that's all. You can do that from: List -> Settings -> Archiving Options on that page should be self-explanatory > > 4) What settings do I make to insure that all who sign up via way #2 > can do the same? They will receive emails and will be able to reply to them. If they want to post via the web interface, they will have to create an account and sign up, same as #1. > > Last, in my account settings what is the difference between a member > and a non member? "non-members" are people Mailman remembers who interacted with a MailingList in past. For example, I can ask an list owner to let my post through, without actually subscribing(because I don't want to get all the emails, just send a single email) by allowing me to be a "non-member" who is allowed to post. > > Thanks and sorry I was not clear the first time. > _______________________________________________ > 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, 6 months

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

by Stephen J. Turnbull

Dave Hall via Mailman-users writes: > I have seen this with several open source projects lately. There's no big > picture, just 'hundreds' of cross-linked little bits of disjointed > information that almost seem like documentation for individual > modules. It is documentation for hundreds of individual modules. That's, like, the point of open source software. ;-) > So, a challenge for us all: When writing and reviewing your documentation, > imagine that you're explaining your whole project face-to-face to your > grandmother, or to anybody who never learned to program. From experience I > promise that it's easy once you get the hang of it. I agree in principle, and for greenfield projects I agree that many/most developers can get the hang of it and it's easy (fsvo "easy") once you do. But in decades-old open source development projects at Mailman 3 scale (which isn't even all that big), most of is not our job. For example, the HAYSTACK_CONNECTION variable that incited this thread is buried deep in a Django extension that's distributed independently of Django. The best we can do with modules like that is cookbook explanations (I'm pretty sure there is at least one and likely two or more in the official docs on list.org or readthedocs). If the cookbook recipe doesn't work, I doubt anybody here can write anything deeper off the top of their head.

3 years, 1 month

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Mark Sapiro

On 8/3/25 00:09, Odhiambo Washington via Mailman-users wrote: > I wonder what this means and whether it's fatal. > > How do I fix it? > > ``` > ERROR OCCURED IN JOB: sync_mailman (APP: hyperkitty) ... > *allauth.account.models.EmailAddress.MultipleObjectsReturned: get() > returned more than one EmailAddress -- it returned 2!* It appears you created a new list, and that list' owner email address has two Django user records with emails differing only in case. See https://www.msapiro.net/scripts/UC_fix for a script to fix this or you can just go to the Django web UI and delete the mixed case user. > I suspect it's something to do with my action yesterday while attempting to > reply to a thread from HyperKitty. Possibly, if hyperkitty was looking at a mixed case email address that it didn't recognize as a list member and subscribed it. > The superuser account uses my address - odhiambo at gmail dot com.I am also > the listowner for most lists. > I tried unsuccessfully to create an account on Postorious using the same > email address. > I kept getting sent links to verify the account, over and over. > Finally, I was able to verify the account, but cannot login with it. This too is probably because there are two accounts with email addresses differing only in case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Rubén Rivero Capriles

Hi! sorry for updating one last piece of info provided by Thomas Woerner of firewalld. He seems interested in our issue of python 2 / python 3: Thomas Woerner <notifications(a)github.com> 4:12 (hace 3 horas) para t-woerner/fire., mí, Author Do you want to use python2 or python3? In the firewalld repo there is a firewalld.spec file. With this it is simply to generate packages for Fedora and also RHEL >= 7. For RHEL-7 it is still using python2, for Fedora >= 23 python3. TO build a package with it you can simple do the following in the root directory of the firewalld source tree: ./autogen.sh make test-rpm Or you can use rpmbuild -ta firewalld-0.4.2.tar.gz with a release from https://fedorahosted.org/released/firewalld/ or https://github.com/t-woerner/firewalld/releases I am still stuck with awstats. Have been able to watch them through lynx linux browser, but stats are not being generated. I enrolled in a local linux academy where I will take an apache course and maybe they''ll be of help. However I don't like software that does not provide support themselves, especially if good folks such as mailman or firewalld team are around. Is there any alternative statistics generation package for apache that you could recommend and I would be able to use without so many installation issues Rubén Rivero Capriles http://www.rubenrivero.net (blog global - español) http://www.rroopstr.com (global blog - English) http://www.riverocooper.com (art & mining)

9 years, 9 months

[MM3-users] Re: bypassing rules on an individual basis

by dlb-ml＠anl.gov

Stephen J. Turnbull wrote: > via Mailman-users writes: > > I have a mailing list that, due to specific circumstances, has a > > requirement to allow messages from a user that sends messages with > > no subject. > > Do you mean "any user who sends a message with no subject", or are > there specific users who do this? If there is one such user (or a > handful), and you trust that user not to abuse the privilege, you can > directly pre-approve that user from Users menu in the list > configuration (see Mark's post for details). This also works if there > is no Subject field at all! > If you don't know who might post with no subject (or there are > annoyingly many, especially if some are less than clueful), you could > use the header match: The address in question is from an automated process, so there's no immediate expectation that it will be abused, so I'm utilizing the recommendation that Mark provided. I'll see if that works as expected. And, out of curiosity, why is the "accept_these_nonmembers" collection not applicable here? Is its use deprecated or is there a very particular use case for it? """ While non-regexp addresses can be entered here, it is preferred to add the address as a nonmember and set the nonmember's Moderation to Default Processing. """ I should have paid more attention to this part. Thanks!

11 months

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

by Ryan McClung

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

7 years, 7 months

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 18:53, Bryan Fields wrote: > On 7/26/24 4:01 PM, Mark Sapiro wrote: > >> If this returns just the one message_id, I would then >> >> DELETE FROM hyperkitty_thread WHERE id = 35670; >> DELETE FROM hyperkitty_email WHERE id = 150555; > > It's giving an error due to a fk constraint on another table. I'm not > familiar with the db structure enough to be certain how to clean/fix it. Yes, you need to do these first. DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; DELETE FROM hyperkitty_vote WHERE email_id = 150555; Not all those will exist, but then you should be able to DELETE FROM hyperkitty_thread WHERE id = 35670; DELETE FROM hyperkitty_email WHERE id = 150555; > I'm actually thinking I need to fix the archive mbox, then delete them and > re-import them once they are cleaned. Actually, that would be safest. Fix the mbox, delete the entire archive and re-run the import. >> Also, FYI, assuming those messages with very old Date: headers had >> reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script >> would fix them, except you have to get the script from >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… >> or https://www.msapiro.net/scripts/cleanarch3 because the script in the >> latest release has a bug. > > I tried the dry run option on your script and it gave a bunch of output > for bad > dates. This was absent on the one shipping with the source. What's > interesting > is that pipermail seems to have no issue with this, detecting the date > correctly. If I recall correctly, pipermail checks date skew and 'fixes' the dates in the archive, but they remain off in the mbox. > https://mailman.nanog.org/pipermail/nanog/2000-January/137630.html > One other thing, I did notice a number of archives not showing up in > sequence > due to missing "In-Reply-To:" headers from the source. The first > message in > this is one like this, and pipermail in mmm2 seems to handle this by > referencing > the subject, > https://mailman.nanog.org/pipermail/nanog/2002-April/151325.html, > where as in hyperkitty it's an orphaned thread. Yes, HyperKitty does not do threading by subject matching. It only threads based on In-Reply-To: and absent In-Reply-To:, only the last entry in References: if any. > Is the archive tool in pipermail's import more robust in this manner? > I'd argue > it's common to have missing In-Reply-To: headers where the subject and time > would need to be used to infer the likely thread. I'll agree this is a > major > violation of the relevant RFC's to be missing this, but many MUA's (M$) are > famous for doing just this. Yes, it's arguably a defect in HyperKitty to not implement Jamie Zawinski's threading algorithm <https://www.jwz.org/doc/threading.html>, but it doesn't. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: configuring moderators per list

by Mark Sapiro

On 11/06/2017 02:33 PM, Dmitry Makovey wrote: > We're trying to configure moderator per list and so far we were only > able to add "superuser" accounts that can handle "Held messages", > "Members", "Banned addresses" etc. You can add ordinary users as Moderator or Owner of a list. I'm not sure what is and isn't currently working, but Moderators and Owners get notices of things like held messages and subscriptions and can approve or deny them. I think only Owners, not Moderators, should be able to change various list settings. Have you tried these things? Is it not working? > Is there a way to create special account per-list to manage some of the > aspects of particular ML without giving them all the permissions that > Superuser comes along with? An Owner of one list should not be able to do things to other lists. If you're looking for more granularity in permissions on a single list, Owners can do anything, and Moderators should only be able to deal with held requests, but there's no granularity beyond that. > In MM2 there was a ML password that moderator/list admin would use to > login to perform operations. > > Current setup allows list admins to add/delete existing lists which is > not desired. This was a site option in MM 2.1. I'm not sure about MM 3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

8 years, 7 months

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

by Brian Carpenter

Make sure you have a SPF record setup for the sending domain. Also if this is a new IP address then ISPs such as Gmail and Yahoo recommend you "warm" up the IP address until its reputation is built up. However none of this has anything to do with Mailman 3. Just a FYI. Have a great day! Brian Carpenter EMWD.com brian(a)emwd.com -----Original Message----- From: worik <root(a)worik.org> Sent: Monday, February 11, 2019 5:25 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Gmail emails bouncing - anybody seen this problem? Friends On a fresh install (docker) on a fresh VPS I am getting all Mailman messages to Gmail addresses bouncing telling me I am sending too many messages. Has anybody else have this problem? I am getting the following error in mail.log: "Our system has detected an unusual rate of 550-5.7.1 unsolicited mail originating from your IP address. To protect our 550-5.7.1 users from spam, mail sent from your IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" I have been to the URL mentioned and exhausted my options there. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years

[MM3-users] Re: spanish localization

by Abhilash Raj

On Sat, Feb 13, 2021, at 9:21 PM, Stephen J. Turnbull wrote: > Victoriano Giralt writes: > > > I've visited Weblate, all Spanish strings are translated. Spanish > > is 100% translated, but, none of them have been "approved", > > whatever that is. It seems that a reviewer needs to approve the > > translation in order for them to be incorporated or released or > > whatever. I was sure I had reviewed everything between November 7th > > and the day Abhilash announced the release candidate and asked for > > translation review, but nothing has made it to the released > > version. > > > > Maybe there's something in the translation flow that we are doing wrong. > > I'm starting to miss the good old days when Mailman 2 translators just > > downloaded the .po files and returned them :-) > > Probably all it needs is for someone other than the submitter to check > a box. I doubt there is an assigned reviewer/owner, just any > translator registered for that language. That's the way Debian used > to work, anyway, and it seems like a good way for open source to work. > > @Abhilash, you set up Weblate, right? Do you know anything about this? https://docs.weblate.org/en/latest/workflows.html This is the documentation from Weblate about the whole workflow. There is a Project level setting which mandates that a Reviewer review and approve all the translated strings, but that is turned off for GNU Mailman project. -- thanks, Abhilash Raj (maxking)

5 years

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

by Abhilash Raj

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

6 years, 11 months

[MM3-users] Re: Disabling the version disclosure.

by ninad＠iitb.ac.in

Steve from another mailman list suggested the below solutions. 1st method suggested worked. This is just for this group's information. Thank Steve for the solution. --------------------------------------- Suggested solution ------------------------------------------------------- It helps to explain why you don't want to change the HTML code, because there are several ways to do this, with different implications both for the page's appearance and for future maintenance. The visually cleanest way to do this is to copy the files site-packages/postorius/templates/postorius/base.html site-packages/hyperkitty/templates/hyperkitty/base.html to /etc/mailman3/templates/postorius/base.html /etc/mailman3/templates/hyperkitty/base.html search for '_VERSION' and delete or edit the version stanzas near the end of those files, add TEMPLATES[0]['DIRS'].append('/etc/mailman3/templates') somewhere in /etc/mailman3/settings.py, and restart mailman-web (typically as root, using 'systemctl restart mailmanweb'). Alternatively and less visually appealing you can clear the version variable itself with a file 'site-packages/version_hack.py' containing the lines def suppress_version(request): return {"HYPERKITTY_VERSION": "Wouldn't you like to know?", "POSTORIUS_VERSION": "Wouldn't you like to know?"} ... you probably want to change the strings to empty strings ... and add the lines TEMPLATES[0]['OPTIONS']['context_processors'].append( 'version_hack.suppress_version' ) somewhere in /etc/mailman3/settings.py, and restart mailman-web. The former method of overriding the templates is a supported API, and very unlikely to be obsoleted any time soon. The latter method of patching the variables is something of a hack, and also leaves the tags like "Postorius version" visible in the page. Steve ----------------------------------------------------------------------------------------

11 months, 1 week

[MM3-users] Re: Hyperkitty performance problem

by Stephen J. Turnbull

Tobias Diekershoff writes: > On 22.11.24 07:59, Tobias Diekershoff wrote: > > so far we could not find the reason behind the performance > > problem. Since you're already running two allegedly identical systems, have you tried hitting the experimental one with the "do what the developers recommend" hammer? That is, blow away the Debian packages in favor of a vanilla installation from source in a virtual environment (and without --system-site-packages!)? It's impossible to be sure what's going on in a Debian package environment because not only Mailman, but any of the scores of packages that Mailman 3 depends on may have been patched or reconfigured by Debian. > To rule out virtualization problems Do you mean a VM, which should not cause a problem, or a container, which is known to be tricky to configure? (Note, I've not heard of it causing the kinds of problems you describe.) > in our setup, we tried to migrate MM3 to a bare metal server in the > data center. After importing the database for MM3 and Hyperkitty to > the new postgresql server MM3 wcomplained about > > MultipleResultsFound: Multiple rows were found when one or none > > was required [in the listarchiver table] I've seen that in a migration from a Mailman 2 site to Mailman 3. Once I removed the duplicate rows in the archiver table, it stopped. I don't know why it happened, but it was a small number of lists (4 or 5 out of 20k), and at most one extra per (list, archiver) pair. I suspect it carried over from the Mailman 2 instance. I no longer have access to that system to confirm, sadly. > However the duplicates are added back to the listarchiver table for > all archivers (mhonarc, hyperkitty, mail-archive and prototype) > even though only hyperkitty is activated. By "duplicates are added back" do you mean something like this: mailman=> select * from listarchiver; id | mailing_list_id | name | _is_enabled ----+-----------------+--------------+------------- 1 | 1 | mhonarc | f 2 | 1 | mail-archive | f 3 | 1 | prototype | t 4 | 1 | hyperkitty | t 5 | 2 | mhonarc | f 6 | 2 | mail-archive | f 7 | 2 | prototype | t 8 | 2 | hyperkitty | t where each list has one of each archiver whether or not that archiver is active? This is correct behavior, as long as the archiving/*.py and mailman_hyperkitty.py files are importable by Mailman core. Or by "duplicates are added back" do you mean this? mailman=> select * from listarchiver; id | mailing_list_id | name | _is_enabled ----+-----------------+--------------+------------- 1 | 1 | mhonarc | f 2 | 1 | mhonarc | f 3 | 1 | mail-archive | f 4 | 1 | mail-archive | f 5 | 1 | prototype | t 6 | 1 | prototype | t 7 | 1 | hyperkitty | t 8 | 1 | hyperkitty | t 9 | 2 | mhonarc | f 10 | 2 | mhonarc | f 11 | 2 | mail-archive | f 12 | 2 | mail-archive | f 13 | 2 | prototype | t 14 | 2 | prototype | t 15 | 2 | hyperkitty | t 16 | 2 | hyperkitty | t (don't take the id -> (list_id, archiver) mapping too seriously). In the multiple instances of an archiver per list case, which are enabled? > We tried to add a constrain on the table to only allow one entry > per list and archiver, but that caused the runner to fail and the > message to be shunt. > > > Uncaught runner exception: (raised as a result of Query-invoked > > autoflush; consider using a session.no_autoflush block if this > > flush is occurring prematurely) (psycopg2.errors.UniqueViolation) > > duplicate key value violates unique constraint "workaround" > > DETAIL: Key (mailing_list_id, name)=(98, mhonarc) already > > exists. This doesn't make any sense. That appears to be the listarchiver table. As far as I can tell in a quick grep, the only place that is mutated is in mailman/models/mailinglist.py:643 (line number is current HEAD), which happens whenever the list checks for its active archivers. It's initialized lazily for each list in that place. @public @implementer(IListArchiverSet) class ListArchiverSet: @dbconnection def __init__(self, store, mailing_list): self._mailing_list = mailing_list system_archivers = {} for archiver in config.archivers: system_archivers[archiver.name] = archiver # Add any system enabled archivers which aren't already associated # with the mailing list. for archiver_name in system_archivers: exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() if exists is None: store.add(ListArchiver(mailing_list, archiver_name, system_archivers[archiver_name])) As you can see, the .add is protected by "if exists". That code has not changed since v3.3.8, which is what is in Bookworm according to "apt list mailman3". If that is so in your installation, I'm pretty sure the problem is somewhere between the SQLAlchemy API and the RDBMS, not in Mailman itself. And if that's true, that might explain the weirdness in archiving as well. What version of PostgreSQL are you using? of SQLAlchemy? Are both the original system with performance problems and the new one accessing the same PostgreSQL server, or is there are separate PostgreSQL instance for each? Steve

1 year

[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

/ I saw output like:/ <User "Real Name1" (250400693957149667060114911620088407125) at 0x7f9435096640> deleted from Mailman <User "Real Name2" (52978839424924170731978420609240089133) at 0x7f9435096760> deleted from Mailman So your users had no real names configured? Cheers, Eggert Am Dienstag, 25. April 2023, 23:14:27 CEST schrieb Andrew Hodgson: > 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? > > 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 > /BTJUT6FGNGK5ARADPD6VW37VMHQG2GWJ/ > > 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, 10 months

[MM3-users] Re: Hyperkitty import from mailman2

by Simon Hanna

On 12/22/2017 03:39 PM, Sten Aus wrote: > Hi > > I have installed mailman3 - it looks very great! > > Now I wanted to try import from mailman2 mbox, so i did: > > python2 manage.py hyperkitty_import --settings settings --ignore-mtime > -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > > It shows that it have sucessfully imported all emails and I can see > them from database (sqlite3), but I cannot see them from GUI > (hyperkitty). Only thing I can see is this inactive "test" list. > How did you try to access them using Hyperkitty? Can you try doing that while logged in as a django superuser? Could you try using a permalink for a message? If you can access the files from the database you should be able to construct the urls using the list name and the message_id_hash of a message. You should try this using DEBUG=True in the settings.py. The URL would be similar to http://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/… Another option would be to check if you can access the data using a python shell. `python manage.py shell` to open a python shell preconfigured for Hyperkitty and then input the following two lines: from hyperkitty.models.email import Email Email.objects.all() This should print out all the messages that are stored in the database. (You can limit them by appending "[10:]", or any other python slice) What do you see in the UI? Is it somewhat similar to http://lists.mailman3.org/archives/list/mailman-users@mailman3.org ?

8 years, 2 months

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/23/23 06:24, Jens Günther wrote: > > I find those changes, but: in the merge request there is mentioned a > /usr/lib/python3.10/site-packages/mailman/testing/mailman-fr.po > > -> but I don't find a mailman-de.po ... is it maybe that? That file was for a test only. The German message catalog is at mailman/messages/de/LC_MESSAGES/. That directory should contain a mailman.po and a mailman.mo. If there is no mailman.mo, it needs to be created. The source distribution contains a generate_mo.sh script to generate these for all languages, but you can do the German one by changing to the mailman/messages/de/LC_MESSAGES/ directory in the running installation and doing msgfmt mailman.po -o mailman.mo >> Please be more specific than `all types of system mails`. Which >> specific message subjects are not translated. > > It's exactly as mentioned in issue 993 the welcome and goodbye-messages > that I don't see translated. > > But also other examples: > - bounce-mail for the user that moderator approval is necessary (there > the text is in german, but the reason is in english) > - approval-mail for moderator (also text is in german, but subject and > reason in english) I'll look into these. If you don't have the mailman/messages/de/LC_MESSAGES/mailman.mo file, this could be the reason, but there may be a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Verification links to localhost

by Odhiambo Washington

On Sun, Feb 5, 2023 at 2:16 PM Lars Bjørndal <lars(a)lamasti.net> wrote: > Hi! > > You wrote: > > > On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <[1]lars(a)lamasti.net> > wrote: > > > > Hi, and than you for your quick reply! > > > > You wrote: > > > > > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1][2] > lars(a)lamasti.net> > > wrote: > > > > > > The verification link I get back when trying to add an account, > > referes > > > to localhost, e.g. > > > > > > To confirm this is correct, go to [2][3] > https://localhost:8000/ > > accounts/ > > > confirm-email/Mw:1... > > > > > > Where do I change that? > > > > > > > > > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings? > > > > I don't have this variable anywhere in /etc/mailman3. However, I > found it > > here: > > > > ./venv/lib/python3.10/site-packages/mailman_web/settings/ > > mailman.py:POSTORIUS_TEMPLATE_BASE_URL = '[4]http://localhost:8000' > > > > In which config file should that variable be set, and how do I set > it so > > that mailman can works for multiple domains? > > > > > > Because it is still too early in your quest to get to run Mailman3, I'd > advise > > that you take your time to follow this guide: > > [5]https://docs.mailman3.org/en/latest/install/virtualenv.html# > > > It is the official installation guide. > > Yes, I've followed it, maybe with some errors. > > > There is a step where it tells you to create a file named settings.py, > in a > > particular path. You really need that step. > > Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't > have the variable in question. > Oh, in that case, it does not appear in settings.py. I have followed that guide, but I always login to the /admin UI to create a site (and a mail domain tied to a site) before I create my lists. Perhaps that's why I haven't encountered the problem you are seeing. > > > Regarding your question about multiple domains, that is already well > taken care > > of when you create a list either via Postorius or the cli: > > (venv) [mailman@gw /opt/mailman]$mailman create [6]list1(a)domain1.name > > (venv) [mailman@gw /opt/mailman]$mailman create [7] > another-lis(a)domain2.name > > > > Mailman will know how to handle this in conjunction with your MTA. > > That's right. But, still, when I set the SITE_ID = 0, I get an server > error when trying to connect. I also get mail from Django that states the > error. I'm not sure how to fix it. > How many sites did you create already? IIRC, this SITE_ID = 0 should be accompanied with FILTER_VHOST = True -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

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.) 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. > multipart/signed > multipart/mixed * > text/plain > message/rfc822 (the attached message) * > multipart/signed * > text/plain > application/pgp-signature > text/plain (an empty plain text part) > text/plain (a quote of my message to you) > application/pgp-signature It's true that Apple Mail is horked if it produces that structure with C-T-E in the indicated places (but we already knew that :-( ). Steve

3 years, 10 months

[MM3-users] Re: redirecting -bounces replies

by Nelson Strother

If you are using Postfix with mysql you could use an entry in the virtual_aliases table by doing something like: MariaDB [mailserver]> REPLACE INTO mailserver.virtual_aliases (id,domain_id,source,destination) VALUES ('N', '1', 'ListNameHere-bounces(a)example.org', 'person(a)example.org'); Query OK, 1 row affected (0.010 sec) where the value 'N' is one larger than the largest id entry already present in said table .... Cheers, Nelson On 10/31/24 19:17, Hirayama, Pat wrote: > Greetings, > > Is it possible to redirect the -bounces alias of a specific list so that it also goes to a person, in addition to the normal bounces processing for that list? > > In Mailman2, I know that I could do that by modifying the aliases table. > > I've been poking around in Mailman3, but haven't managed to figure out which container I need to be looking at. And rather than keep spinning, I figured that I'd ask the hive mind, since I'm sure one of you can quickly point me to the correct location. > > Thanks! > > -p > > > > Pat Hirayama > Pronouns: he/him/his > Systems Engineer > IT | Systems Engineering - Infrastructure > Fred Hutch Cancer Center > O 206.667.4856 > > phirayam(a)fredhutch.org<mailto:phirayam@fredhutch.org> > > > _______________________________________________ > 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 tojustfixit(a)marilynstrother.com

1 year, 4 months

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

by Stephen J. Turnbull

bob B writes: > Anyone have any ideas? First, what docker configuration are you using? One supplied by the Mailman project? If not, you need to tell us more about what's going on. If so, are there any containers other than those running the Mailman suite (Mailman 3 core, Postorius, HyperKitty)? In mydestination you have mydestination = $myhostname, localhost.$mydomain, localhost, mydomain.mydomain.com I do not understand the "localhost.$mydomain" entry. I guess that's a Postfix-ism, but I can't find any documentation about it. You could try taking it out (this is a very random suggestion). You say you have no /etc/postfix-mailman.cfg. Where are you looking for it? That file will only exist in the container, not in the host OS. (If it were in the host OS, it would be located somewhere like /opt/mailman/core/postfix-mailman.cfg.) Try `find /opt/mailman/core -name postfix-mailman.cfg`, although "automatically" might mean it's generated in the container when it starts. Abhilash would know, but he doesn't seem to be available. I really don't think it's the issue because I assume "bmimailmandr1" is the Docker container running Mailman core. If so Postfix is connecting to the configured LMTP port on localhost which is what it's supposed to do from the configuration. Since the container's Postfix appears to be connecting to the right place but the connection is refused, that Mailman core may not be running. For more help you'll have to wait for Abhilash. Steve

4 years, 7 months

[MM3-users] Re: Timeouts

by Mark Sapiro

On 4/25/21 4:37 PM, tlhackque via Mailman-users wrote: > The described timeouts are something that hyperkitty ought to be able to > avoid. For apache, the timeout is idle time between blocks of output. > Hyperkitty can avoid this by generating the archive in segments (based > on size, or elapsed time), flushing its output buffer, generating a > multi-file archive, and/or using Transfer-Encoding: chunked (chunked > doesn't work for http/2). It ought to be able to break the work into > blocks of "n" messages & do something to generate output. Besides > avoiding timeouts, working in segments allows the GUI to display > meaningful progress (e.g. if you're loading with XMLHttpRequest, > "onprogress") It really oughtn't be up to the user to break up the > request. It is not the web server that times out. I'm not sure about uwsgi because I don't use it, but the timeouts I see are on servers that use gunicorn as the WSGI interface to Django and the timeout is in a gunicorn worker. This is controlled by the timeout setting in the gunicorn config. <https://docs.gunicorn.org/en/stable/settings.html#timeout> Note that even 300 seconds is not enough to download the entire <https://mail.python.org/archives/list/python-dev@python.org/> archive. It may be possible to get HyperKitty to chunk the output to avoid this, but it doesn't currently do that. Care to submit an MR? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

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

by Marvin Gülker

Hi, Am 22. October 2017 um 11:47 Uhr -0700 schrieb Abhilash Raj <maxking(a)asynchronous.in>: > As Simon mentioned, try using DEBUG=False, if you don't already have > that. With DEBUG=True, you should see emails printed in a `emails` > directory under `mailman-suite_project` directory. Bingo! Man, I was not seeing the forest for the trees. I should have peeked inside that emails folder. And yes, changing the DEBUG flag resolves the problem and emails now go out as they should. My bad! Thank you! > > That being said, the enormous number of configuration files to consider > > and dozens of cross-references to other pages in the docs make the > > installation guide hard to follow; it also lacks logical structure in my > > opinion, when it refers to parts of the configuration which are later > > explained. For someone like me who never programmed a Django application > > (Ruby dev) this is all pretty cryptic. Especially, that some parts of > > information are on <http://docs.list.org/en/latest/index.html> whereas > > other parts are scattered over readthedocs.io makes it very > > complicated. > > There are only two primary configuration files (there are a few more for > finer configurations ;-): Mh, mailman.cfg, settings.py, and hyperkitty.py are three. But I agree, I exaggerated. > All the settings mentioned in the documentation go to either of these > files, except, when configuring web server and mail server. Please open > an issue[2] if it is not clear where a particular configuration snippet > goes and we will fix it. I'll open an issue later; for now off the top of my head so I won't forget I came over these problems with the docs: * The linked installation guide for Sass (<http://sass-lang.com/install>) does not include any C/C++ implementation you speak of. * The mailman-suite's settings.py includes a handler for Less, which is not mentioned in any documentation. * It's officially suggested to use the "fhs" filesystem path layout. It's not documented that you need to create the exact directories and change permissions accordingly; even worse, if one uses this layout, Mailman tries to write into /sbin, which only the package manager is allowed to do. Thus, don't recommend that layout in <http://docs.list.org/en/latest/config-core.html>. * This page: <http://docs.list.org/en/latest/config-core.html> does not mention that the "postfix_lmtp" and "postfix_domains" files are *generated* by Mailman. I spend quite some time looking for these files before I found in the Mailman Core docs that they're generated and it was not an error in my installation. * This page: <http://docs.list.org/en/latest/config-core.html> configures the LMTP server and the REST API server for the same TCP port (8024). This clashes. * This page: <http://docs.list.org/en/latest/config-web.html> should mention the thing with the DEBUG variable we've successfully worked through in this thread. * There's no mention of how to create the initial superuser on <http://docs.list.org/en/latest/>, it is hidden down in <https://postorius.readthedocs.io/en/latest/setup.html>, where however there's no mention of the mailman-suite, but some kind of "example_project". It was unclear to me whether this now applied to me or not. * <http://docs.list.org/en/latest> contains quite some pip install commands (duplicated from the postorius/hyperkitty/core docs), but it's missing "$ pip3 install mailman-hyperkitty", which is only mentioned in <http://hyperkitty.readthedocs.io/en/latest/install.html> in the text body (but not as a command block). * This page: <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> uses "configuration: python:mailman.config.postfix" in the introductory text without explanation, but down in the Postfix-specific block the directive is missing with no explanation. I opted to include it, but I don't know whether that's now correct or not. The overall problem I had with the docs is that they can't be followed top-down. One has to refer to the subproject docs if something is unclear, then searching in them until one finds what one was looking for (even if one doesn't know what one is looking for, as with the superuser creation command). I totally appreciate the detailed subproject-docs approach, but you should follow it consequently then. That is, do not duplicate some information from the subproject docs in the mailman-suite docs. It creates the impression as if the mailman-suite docs are complete, which they aren't. Instead, the mailman-suite docs should use explicit references, for example: 1. Do this... 2. Now follow the procedure outlined in [Postorius Installation link] 3. Do something else... 4. Follow the procudedure in [Hyperkitty installation link] That way, the Mailman installation guide would be less of a puzzle. It however might just be me. I apologise if I sound silly. Greetings Marvin -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 4 months

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

by Nelson Strother

As you had suggested, the `in` runner/queue was missing in action. Given your insight about the limitations of `mailman restart`, I looked back at the log from the time of the preceding `mailman start`, and found that there was NOT a line such as: in runner started. in that instance! Watching the logs on each subsequent `mailman start`, the good news is that the `in` runner/queue has been started each time; the bad news is that slightly more than half of the time one or two runners are NOT shown as starting. The other runners/queues sometimes missing in action per the log file have been `retry`, `task`, `nntp`, `archive`, and `pipeline`. 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? 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? On 6/1/23 11:16, Mark Sapiro wrote: > When you issued a restart and the logs show runners restarting, did > all the runners restart or was one or more missing.

2 years, 9 months

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Stephen J. Turnbull

M.Ede via Mailman-users writes: > Mark Sapiro wrote: > > > The following patch will remove the header. > > Thanks for the hint, I removed authentication-results header as > well as arc-authentication-results with your patch, but rspamd > still results in SPOOFED_UNAUTH. I don't think Mark was suggesting that would help with the SPOOFED_UNAUTH problem. I read his mail as saying that it needs to be fixed because it breaks anonymous_list. I don't think that rspamd is paying attention to any of the smtp.*from information because the one that matters is the one in the SMTP MAIL FROM command, which only appears in the message header by accident. (It could be some kind of machine learning thing, but I doubt that would get dinged for 50 points.) If you're still having issues 1. Does your problem resemble any of those in the links Mark sent? 2. Where is rspamd running? On your host or at Mailcow? 3. Who is sender(a)t-online.de, is it a placeholder for a random user, or is it an address associated with your Mailcow account? 4. Are my.mailserv.er and lists.list.domain the same host? If not, what is their relationship? 5. Where are you running the ARC and DKIM processors? 6. Do you have Mailman set to strip DKIM signatures? (I find it hard to believe that a major ESP like t-online doesn't sign outgoing email.) 7. What is the list address? Specifically, is it @lists.list.domain, or is it @list.domain? You need a DKIM public key record in DNS for the exact domain of the list as it is added to From. 8. Do you have a non-permissive DMARC policy for lists.list.domain? 9. How do you send list mail to Mailcow? (a) Regular SMTP directly to the Mailcow MX (b) Regular SMTP indirectly via a different host that is not authorized in SPF to send mail for your list domain (c) Authenticated SMTP (usually SASL on port 587)? Something is definitely odd about your ARC installation. It should not be possible for ARC verification to fail within the administrative domain that applied the ARC headers, because in theory the ARC signature and seal are performed on the *outgoing* message at the administrative boundary. Also, in the example in your third post[1] the server names in the ARC headers doesn't match: ARC-Message-Signature: i=1; d=lists.serv.er; ARC-Authentication-Results: i=1; mailserv.er; ARC-Seal: i=1; s=dkim; d=lists.serv.er; Maybe that's just a typo, but if not that could be the problem, I'm pretty sure those are expected to match. I think the missing DKIM signature may be important. One interpretation of "SPOOFED_UNAUTH" is "I think it's spoofed because I can't authenticate it". In question 9 above, if you send mail via (a) SPF *could* authenticate it, and via (c) that's pretty good authentication, but DKIM is best and Mailcow may insist on it. [1] <175750349214.87167.13924287800652306747(a)mail.mailman3.org> Aaargh, gmx.de has a non-permissive DMARC policy -- hope you're not deleting dupes because that almost always means you don't get the list version. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months, 3 weeks

[MM3-users] Docker Support Sucks

by Brian Carpenter

Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. 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 Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 160, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 84, in create_connection raise err File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 74, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 677, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 392, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/lib/python3.6/http/client.py", line 1254, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1300, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1249, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1036, in _send_output self.send(msg) File "/usr/lib/python3.6/http/client.py", line 974, in send self.connect() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 187, in connect conn = self._new_conn() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 172, in _new_conn self, "Failed to establish a new connection: %s" % e urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f96340a2e10>: Failed to establish a new con$ During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 449, in send timeout=timeout File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 725, in urlopen Commenting out "configuration: /opt/mailman/gunicorn.cfg" brings Postorius back up. I am really frustrated here. All I want to do is export a 3000 member list and I can't. Updating Mailman 3 using new Docker images shouldn't break a stable installation either. Please help. Brian

5 years, 7 months

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

by Dmitry Makovey

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

7 years, 5 months

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

by Stephen J. Turnbull

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

3 years, 1 month

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

by tlhackque

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.

8 years, 7 months

[MM3-users] Re: The doubled entries issue

by Stephen J. Turnbull

Lars Bjørndal writes: > select * from listarchiver where name = 'mhonarc'; > > and get: > > id | mailing_list_id | name | _is_enabled > ----+-----------------+---------+------------- > 1 | 2 | mhonarc | f > 9 | 4 | mhonarc | f > 13 | 5 | mhonarc | f > 17 | 6 | mhonarc | f > 21 | 8 | mhonarc | f > 25 | 9 | mhonarc | f > 29 | 10 | mhonarc | f > 33 | 7 | mhonarc | f > 37 | 11 | mhonarc | f > 41 | 12 | mhonarc | f > 45 | 13 | mhonarc | f > 49 | 14 | mhonarc | f > 53 | 16 | mhonarc | f > (13 rows) > > mailman=# > > So which lines should I remove, and how do I do that? None of them? You have one entry per mailing list, which is as it should be. Also, your preceding message doesn't complain about the database, it complains > raise ComponentLookupError(interface, name) > zope.interface.interfaces.ComponentLookupError: > (<InterfaceClass mailman.interfaces.listmanager.IListManager>, '') That says that "python scriptname.py" need the IListManager interface but can't find it. You didn't provide enough information to explain why that might be, so I'm not going to guess. Tell us more about the "duplicate entries" error, and if possible copy it exactly from where you found it originally, including any traceback. Also tell us more about your installation. Is it a distro installation? If so, which one, what version of Mailman? Is it a venv installation? If so, did you activate the venv before invoking "python scriptname.py"? If you didn't, try that and run scriptname again. Steve

2 years, 3 months

[MM3-users] Re: Office365 posts shunted (authres.core.SyntaxError)

by Stephen J. Turnbull

brylon(a)oit.rutgers.edu writes: > Thanks for the response. You are correct in the fact that I've > enabled/configured the ARC module, however, I don't think Mailman > is adding that (malformed) header considering I'm now HOLDing the > test email(s) sent to our postfix inbound MX servers *before* they > are LMTP'd to the Mailman server and its already there when I > postcat it. OK, thanks for that clarification. I feel better (but will still check it! just a bit less urgently ;-) What do you still need from us? I guess the easiest thing for us would be to catch the Exception in our ARC module, and ignore nonconforming Authentication-Results, so that there will be no ARC signature from Mailman on those posts. Will that do? (Note that "ignore and/or delete" is the RFC recommendation. I'd need more than "it would be nice" as a reason to try to parse non-conforming A-R. Mark's experience with parsing *conforming* (non)delivery notifications is quite a deterrent to that.) > At the same time I also can't fathom that Office365 has this wrong > (still?) and no one has noticed/complained? I guess I would say, how would we know if there were complaints? ARC is a very recent addition to Mailman, so you wouldn't necessarily see it here yet, and Office365 doesn't have a public bug database AFAIK. ;-) Microsoft (and other > 1G$ corporations) have a long history of "embrace, extend, and drive conformant implementations out of business".

5 years, 5 months

[MM3-users] User account issue after importing data from Mailman 2.x server

by dgoldsmith＠sans.org

We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. I just started looking at a user and a list in both the Postorius and Django admin web UIs and found: - in Postorius: - list exists, has 20K plus subscribed members and has 3 list owners - user exists and is subscribed to this list - in Django: - in HyperKitty section - in the Mailing lists page, the list exists, no idea about members BUT it has 147 owners (also the same 147 moderators) - in the Emails page, there are 149K plus entries - in the Profiles page, there are 147 entries - in the Accounts->Email addresses page, there are only 155 entries - in the AUTHENTICATION AND AUTHORIZATION->Users page, there are 147 entries Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Thanks, David Goldsmith

1 year, 4 months

[MM3-users] Re: Using REST with CLI using curl .... help needed

by Stephen J. Turnbull

Michael Bakonyi writes: > allright, thx a lot for your quick answer! After fiddling around > some more time, I guess I had some misunderstandings regarding the > REST-API. I guess if we reach the API correctly, we will not be > confronted with the CSRF-Error. We will continue to try but > nevertheless: What would be a cleaner approach to reach the API > from an external IP? I didn't found any examples in the web so far. If you mean the core REST API, you won't find any useful examples on the Internet. Anything you do find should be considered a form of self-harm and/or an insider threat. Access to the REST API is not securely authenticated, and therefore should never be exposed to the Internet. This API is expected to be contained either to localhost, or to a subnet behind a firewall that prohibits access to that port except from the host(s) serving HyperKitty and/or Postorius. If that's what you're trying to do, I would suggest a secure tunnel (not a generic VPN, but a specific tunnel to the API port). If you're talking about the Django administrative API to Postorius, you'll probably get a better answer faster from Django channels. Mark may know but he won't be available until mid-September most likely. As I wrote earlier, as far as I know you need to access the Postorius port, provide credentials, get the CSRF token, and then access Django. Regards, Steve

3 years, 6 months

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

by William Oliver

On Tue, 2021-12-28 at 20:05 -0800, Mark Sapiro wrote: > On 12/28/21 5:58 PM, William Oliver wrote: > > On Tue, 2021-12-28 at 17:50 -0800, Mark Sapiro wrote: > > > The recommended uwsgi.ini includes > > > > > > pythonpath = /etc/mailman3/ > > > > > > according to > > > https://uwsgi-docs.readthedocs.io/en/latest/Options.html?highlight=pythonpa… > > > > > > this should work. Did you have that? If you did and it doesn't > > > work, > > > perhaps adding > > > > > > env = PYTHONPATH=/etc/mailman3 > > > > > > > Yes, I had the first, and does not work. The second entry works. > > > I updated the doc to use > > env = PYTHONPATH=/etc/mailman3 > > I don't know enough about uwsgi to know for sure, but the issue may > be > that setting pythonpath in a running python process doesn't work - > it's > too late as the path is already set in python's initialization. > You might add that it may be necessary to do it in .bashrc for linux folk -- I got it to work but as I've demonstrated, I can sometimes make mistakes and leave detritus around. I may not have successfully cleared my previous setting. That being said, I think it works. I am, I am afraid not a details-oriented guy, which is a bit of a drawback for someone doing system admin...

4 years, 2 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Mark Sapiro

On 10/14/19 7:03 PM, Paul Arenson wrote: > > MAILMAN 2 > What I got from the Mailman 2 Wiki is "How to restrict the list so only authorized persons can post (moderation). If there is an option like that in Mailman 3 I want that. There is, but you can't do it the best way. See below. > SUMMARY > I want to be able to reply personally to the user if necessary without his or her message going to the list. So something like moderation. > > So let me take a guess: > > Default action to take when a non-member posts to the list AND > Default action to take when a member posts to the list > > should be set to HOLD FOR MODERATION? That will work and is probably what you want anyway. Your own posts will also be held, but you can just accept them. Alternatively, you could set your own Moderation setting to Accept or Default Processing so your posts won't be held, but don't do that as it allows anyone to post by spoofing your address in From:, Sender: or Reply-To: or the envelope sender. The best way to post without the post being held is pre-approval with an Approved: <password> header, where <password> is the list's moderator_password, but you can't set that in postorius so it won't work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Syncing Real Name between user account and membership

by Abhilash Raj

On Sat, Dec 19, 2020, at 10:42 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > a user was mass-subscribed (with a wrong name) and now registered > > and changed his name via the web interface but the list entry is > > not changed. > > I don't recall the design discussion, but I'm pretty sure that this > distinction was intentional. The idea was that people might want to > have different display names associated with different addresses (eg, > you probably don't want your User display name associated with an > address you use on anonymized lists). I'm not sure that option has > any merit in practice. > > @ Abhilash: > > Since Postorius doesn't provide a way to manage address-specific > display names, we should probably have Postorius propagate display > name changes. I believe that is normally what the user wants. > > What does everybody think? +1, I've been thinking the same. I am just wondering if Core's API should do this (probably not by default, but with a bool parameter that P can use every time), or should we iterate over all addresses and PATCH the display names in them (would be slower, with multiple API requests). I am leaning towards the first option. What do you think? > _______________________________________________ > 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] Change to content filtering collapse alternatives - was: Re: Mailman shutting down Hyperkitty: Request too large

by Stephen J. Turnbull

Mark Sapiro writes: > 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" Ouch, that's a mess. First, unless you elided it, it's missing the required type parameter. Despite being required, it's basically an optimization and in most cases will not be much of one. So that's not really a big deal. Second, the Content-IDs are malformed. They are supposed to have the form of message IDs. Also not a big deal, they're close enough for government work. The big problem is I have no idea what the semantics of multipart/related text/plain image/jpeg should be. Throwing away the image data seems like it would be the right thing to do according to RFC 2387, which delegates rendering of the entire multipart/related entity to the root entity. But if that were the desired result of the author of the original message, it's straightforward to achieve by inverting the related and alternative parts. And (at least for image content) I would think that would be a rare intention. I don't see an obvious way to resolve this without checking what popular MUAs do with the various possibilities. So as long as your patch does the expected thing, it's the minimal solution. Steve

1 year, 1 month

[MM3-users] Re: Moderation action "None" is misleading

by Stephen J. Turnbull

Markus Grandpré writes: > Hopefully we won't have to wait too long with Debian Debian has traditionally been quite slow to update Mailman, and they're following tradition. Both the testing and unstable distributions are still on Mailman 3.3.8. Regarding your specific issue of Kein/None, testing has the same version of mailman-web (dated 2020-05-30), while unstable has a much newer version of mailman-web (dated 2024-03-12). That should resolve that issue, but you will have to wait a full Debian development cycle at least. Our standard recommendation is to do a source installation in a Python virtual environment, point the new installation at your $SQLDB, review the content of /etc/mailman3 (I think Debian puts mailman3 configs there and that's what we recommend), test the new installation, and if that works, remove the Debian installation after preserving the /etc/logrotate.d/mailman*, /etc/cron.d/mailman*, and /usr/lib/systemd/system/mailman*.service files which are probably generally appropriate for Mailman 3 installed in a Debian system. There is also a containerized distribution of Mailman 3 suite, but I don't know how straightforward it is to port over a Debian packaged system to that environment. It may sound pretty fearsome, but you can hire people to do the installation and testing (maybe for as little as a pizza and a mug of beer ;-). After that you will get a more reliable system and better support (really, almost all the Reply Guys here run up-to-date systems of that kind, so we're much more familiar with it than with distro installations). Steve

1 year, 1 month

[MM3-users] Re: Null sender?

by Mark Sapiro

On 6/28/20 6:58 AM, tom(a)gather.coop wrote: > Does Mailman generally send email with a null sender? > > This is what I see in the log: > > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) handling connection > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'LHLO mail.example.coop' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'MAIL FROM:<>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) sender: <> > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'RCPT TO:<techque-bounces(a)example.org>' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) recip: techque-bounces(a)example.org > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'DATA' > Jun 28 02:37:45 2020 (14588) ('127.0.0.1', 52726) Data: b'QUIT' > > Notice the empty MAIL FROM. > > Sendgrid seems to be choking on that because it needs to check if sending domain has been validated. If there is no sending domain it seems to reject. > > Why does Mailman do this? Can it be changed? I've been trying to find the relevant section of the code to no avail. It isn't Mailman doing this. It is the MTA at mail.example.coop that is reporting the bounce of some message from the techque(a)example.org list. The log messages you see are Mailman's receipt of the bounce DSN. Bounce DSNs are always sent with a null envelope sender so if they are undeliverable, it doesn't result in another bounce. See <https://www.rfc-editor.org/rfc/rfc3461.html#section-6.1>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Issues with Mail delivery after Mailman 3 installation

by Stephen J. Turnbull

Chihurumnaya Ibiam via Mailman-users writes: > On Wed, Feb 4, 2026 at 4:21?PM Stephen J. Turnbull <steve(a)turnbull.jp> > wrote: > > > Chihurumnaya Ibiam via Mailman-users writes: > Not uninstalled it, commented out from postfix master.cf the line; > # dovecot unix - - y - - lmtp [...] > systemctl shows the service is still active, Life will be a lot easier if you shut that service down, and fix whatever configuration in Postfix that's needed to talk directly to Mailman (probably nothing since that configuration is in postfix_lmtp, and if you put that table in transport_maps it's highest priority so should work). You don't need a mailbox transport since you have no local users who should be getting mail on the Mailman host, except maybe root. > I didn't end the service itself, I assumed the line above I > commented out would prevent the dovecot service from running under > postfix. The fact that there is a systemd service implies that dovecot will be running by default unless it is disabled. If Mailman and Dovecot are running, each will try to open a socket with parameters IP address and port number. The IP address is 127.0.0.1, and the port number of Mailman is 24 according to the "mailman info" output you provided. I don't know what the port number for Dovecot is, but its default is also 24. If so, the one that opens that listening socket first will win, and the other is going to be unable to open its socket. I'm not sure if Mailman can even open a privileged port (number less than 1024), since it should be running as 'mailman', not 'root'. > Yes, that's how it's configured. Sure, but something is wrong with the configuration, and it might not be just one thing. > I'll have to look at user authentication in lmtp then, because the > earlier passwd-file arguments seems to have no effect, I probably > didn't configure it properly. I don't understand why you have authentication for Mailman in any case. From what you wrote before, there should only be one active user on that host, and it's you, either as root or an ordinary user with sudo. If anybody else can get in there, you have bigger problems than connecting to ports 24 and 25. It may make sense for Postfix to authenticate to servers on other hosts if it is purely internal to your network and does not talk to the Internet. Similarly, it may make sense for Postfix to require authentication for incoming messages if all your posters are expected to send mail only from internal hosts. But if your Postfix talks to hosts outside of your network, authentication should be off, because almost certainly you have no way to configure it on the remote hosts. > The listener on 24 is lmtp via postfix, the port opened after I > added this line to postfix; > mailbox_transport = lmtp:inet:localhost:24 > > Dovecot also has lmtp as a running protocol, but that didn't open > the port. This doesn't make sense. Mailman and Dovecot are LMTP servers, both *must* open ports in order to receive connections. On the other hand, Postfix is an LMTP client, it opens a connection to the port only when it is delivering a message. What does "lsof -i @127.0.0.1 -i '@[::1]' | grep 24" output? > [mta] lmtp_host: *.*.*.* That should be 127.0.0.1. Mailman should not be listening on network interfaces other than the loopback (localhost). > [mta] lmtp_port: 24 This can't work if Dovecot is configured to use the same port, as is Dovecot's default. > [mta] outgoing: mailman.mta.deliver.deliver > [mta] smtp_host: 127.0.0.1 > [mta] smtp_port: 25 Those are normal. > [mta] smtp_pass: ************** > [mta] smtp_user: mailman This is going to cause Mailman to try to authenticate to Postfix. That's OK if it's what you want and Postfix / saslauthd has been properly configured to accept Mailman's credentials. Otherwise, they must be left empty to disable authentication. > I used the virtualenv method. Good. That's the preferred method, as distro packages generally lag substantially, often a year or more. > The Message-ID being the way it is doesn't seem like a > configuration issue, if it is then how do I look into it? Probably you don't have the full hostname in Postfix's myorigin or myhostname parameter. > Yes, it points to a configuration problem, the recipient_delimeter > for postfix is set to + OK, then I don't know why mail is looping in that way. > How do I disable outgoing authentication? I don't remember enabling > it. As mentioned above, you leave smtp_user and smtp_pass empty. > I also just noticed this in the logs; > > NOQUEUE: reject: RCPT from unknown[141.98.11.11]: 554 5.7.1 > <allenmccathyesq(a)gmail.com>: Relay access denied; > from=<marketing(a)lists.sugarlabs.org> to=<allenmccathyesq(a)gmail.com> > proto=ESMTP helo=<LS57X2JsBM> Reverse lookup for 141.98.11.11 returns axon-stall.riddlecamera.net, but that doesn't roundtrip (the lookup on that domain goes to a different customer address in Google Cloud). The IP address appears to be in Lithuania. Is any of that expected? If not, I would guess that's a spammer who is somehow spoofing the PTR record. > I turned submission back on, totally forgot it was used that way. What do you mean by "submission"? This entry in Postfix's master.cf? submission inet n - y - - smtpd (along with any -o options you are using) If so, Mailman isn't going to use it, because Postfix's submission service is an smtpd that listens on port 587 (unless you've changed that in /etc/services). But you've specified that Mailman talk to Postfix via port 25. > I also added permit_auth_destination to smtpd_relay_restrictions for the > Relay access denied issue. I don't think permit_auth_destination does what you think it does. Here's the Postfix doc: permit_auth_destination Permit the request when one of the following is true: - Postfix is a mail forwarder: the resolved RCPT TO domain matches $relay_domains or a subdomain thereof, and the address contains no sender-specified routing (user@elsewhere@domain), - Postfix is the final destination: the resolved RCPT TO domain matches $mydestination, $inet_interfaces, $proxy_interfaces, $virtual_alias_domains, or $virtual_mailbox_domains, and the address contains no sender-specified routing (user@elsewhere@domain). I thought this host is dedicated to Mailman? If so, you just want permit_mynetworks in relay restrictions, and mynetworks_style = host. This does what you want because Mailman is *not* an MTA. As far as Postfix is concerned, delivery to Mailman is a *local* delivery (LMTP, yes?), and the messages being delivered to subscribers are *new* messages being sent by a *local* user. It is not a relay as far as Postfix can tell. And $relay_domains should be empty, you don't want anything else permitted. From Postfix docs: smtpd_relay_restrictions (default: permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination) which is mostly what you want on a dedicated Mailman host. In fact, once I know things are working I would normally delete permit_sasl_authenticated, since I don't want third parties coming in through submission and relaying directly out through Postfix without going through the malware checking done by the milters that should be attached to Postfix's smtp service. I would also change defer_unauth_destination to either reject_unauth_destination or reject, since I don't want relay attempts to be retried. > I usually set postfix user authentication through saslauthd, which is > configured to use /etc/shadow for user lookup. But there shouldn't be any users with passwords on that host except you. You can set one and authenticate the 'mailman' user if you want, but there's little point to it. Furthermore, any system users that might send mail (eg, cron) won't be able to do so since there's typically no provision for them to do the SASL AUTH dance. > I was just reminded that it's needed though, the log entry above reminded > me of that. Well, there's always the alternative of doing what I suggested, which is to reconfigure the system to be as simple as possible, and add complexity only when the simple configuration is working. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month

[MM3-users] Re: Creating and placing custom templates

by Mark Sapiro

On 5/2/19 12:45 PM, kelly.close(a)lrewater.com wrote: > > Here's what I'm doing: > > I found my templates folder and verified it matched what is set in the mailman.cfg file - on my Ubuntu Bionic system it is /var/lib/mailman3/templates/ What is the setting, if any, for 'layout' in your mailman.cfg? If, for example, you have layout: fhs The default var_dir in that layout is /var/lib/mailman, not /var/lib/mailman3, although that could be changed in a [paths.fhs] section. > In that folder I created the following folders and made sure they were properly owned (by list:list) > /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/ > > Into that en/ folder I placed a file called "list:member:regular:footer" It is a text file with just one line of text in it (a link to a website). Also, because there was a mention in one of the earlier posts that this file should have a .txt extension, I also put the same file in there named "list:member:regular:footer.txt". Yes, you do need the .txt extension. If this doesn't work, it's possible you have a different URI for the template. Try bin/mailman shell Welcome to the GNU Mailman shell'list:member:regular:footer', >>> tm = getUtility(ITemplateManager) >>> tm.raw('list:member:regular:footer', 'f2p2-test.udfcd-lists.org') This should return something like 'mailman:///$listname/$language/list:member:regular:footer.txt' Does it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

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

by Mark Sapiro

On 1/10/22 4:00 AM, Paul Paulchen wrote: > > So without adding all nonmembers with postorius step by step 8x20 times, there is an easier way to do it. > I thought so, because the import21 command did this as well when we migrated to mailman3. You could script it with `mailman shell`. If you really want this, I'll help. > I read about the command "mailman addmembers" https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… > > I am guessing, that I need to create a file like in the example of the addmembers, adding all my nonmember users with their email addy. > But how can I add/ tell the command in this massimport that the new members are nonmembers in the existing lists?! You can't without modifying the code. > Hope I explained my case properly. I appreciate your responds! Thanks in advance. My question is why do you want to add these nonmembers. The only thing gained by adding a nonmember is the ability to set the nonmember's moderation action to other than the default, and you can handle that with the legacy * these non-members settings which take priority over the nonmember's moderation action anyway. Note that if a nonmember posts to a list, she will automatically be added to the list as a nonmember with default moderation action if she isn't one of the list's nonmembers already. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: How to keep virtualenv install secure?

by Mark Sapiro

On 11/7/24 01:31, Lichtinger, Bernhard wrote: > Hi, > > I am looking for some advice: If we use the virtualenv install method, how does one keep track of security updates for all the installed dependencies? > > I can think of: > - Upgrade regularly all installed packages inside the virtualenv. This might break mailman3 if there are incompatible updates. You can do in the venv ``` pip install --upgrade --upgrade-strategy eager mailman psycopg2-binary mailman-web mailman-hyperkitty ``` I'm not sure if this will update dependencies if there are no updates to the named package, but in any case, incompatibilities should be avoided because if a newer version of a dependency in incompatible, the dependency should be pinned to a compatible version in the project's requirements. > - Try to track all dependencies and check if there are security updates published. This might be impossible to achieve. It shouldn't be too difficult to script this. ``` Get the output from `pip freeze` in the venv for each line split it on `==` into PACKAGE and VERSION get https://pypi.org/rss/project/PACKAGE/releases.xml find the first <title>VERSION</title> and compare that VERSION to the VERSION from `pip freeze` ``` This won't tell you if the newer version is a security update, but it will tell you which packages have newer versions. > - Security updates are so rare, we do not need to bother. ;) For the Mailman dependencies, this is probably true. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] MM3 templates

by Odhiambo Washington

I followed this: https://gitlab.com/mailman/mailman/-/issues/901 I created a similar template which I placed in /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ I also restarted Mailman. However, when I test, the mail I get is not what I expected. The template used is different than the one referenced above. <CUT> From: < kictanet-confirm+e486c811933b179525ed673751e9b817c4b4b2e4(a)lists.kictanet.or.ke > Date: Wed, Feb 15, 2023 at 4:01 PM Subject: Your confirmation is needed to join the kictanet(a)lists.kictanet.or.ke mailing list. To: OdhiamboW <myaddress(a)outlook.com> Email Address Registration Confirmation Hello, this is the GNU Mailman server at lists.kictanet.or.ke. We have received a registration request for the email address myaddress(a)outlook.com 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 kictanet-request(a)lists.kictanet.or.ke: confirm e486c811933b179525ed673751e9b817c4b4b2e4 Note that simply sending a `reply' to this message should work from most mail readers. If you do not wish to register this email address, simply disregard this message. If you think you are being maliciously subscribed to the list, or have any other questions, you may contact kictanet-owner(a)lists.kictanet.or.ke </CUT> The part that has the URL from the referenced template is here. 1. Where is this template that the system used and can I edit it? 2. Why is it not using the template I created? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

[MM3-users] Re: Customizing Postorios web templates

by Stephen J. Turnbull

Stefan Bethke writes: > I understand. Would you be open to some documentation about the > general approach and a few pointers in the right direction? For > people who are not familiar with Django this is not very obvious. Yes, Without seeing your contribution, I think something like what I wrote with a more precise pointer to Django documentation on overriding templates would be optimal. But I would be open to suggestions. > And also, would you accept a change that enables replacing the icon > in the nav bar and (extending/replacing) the footer, by defining a > block each for these places with the current content as the > default? I would have to see the proposed change. As I said before, I am generally opposed to making it easier to replace our branding. Making the footer extensible while preserving our branding would be fine with me, but it seems to me that it would be hard to do that in a way that would satisfy most use cases and be reliably attractive. > My rationale is that I do not want to track changes to > postorius/base.html manually, Yeah, I understand that. Still I'm reluctant to approve it (espcially sight unseen), but I won't veto it, or any of the parts you've mentioned. So I recommend you consult Abhilash Raj <maxking(a)asynchronous.in>, who is the committer most recently active on Postorius as far as I know, specifically base.html. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 week, 5 days

[MM3-users] Re: Mailman 3 stops delivering to a domain after too many bounces

by Julian Kippels

(sorry, I did not reply to the list with this at first) Hi, I'm quite positive that Mailman 3 is the culprit here. The problem did not exist with Mailman 2 and both versions used the exact same MTA. This MTA is even set up in a way to explicitly circumvent spam filtering (mails are filtered on the way in to mailman, there is no need for an additional check on the way out) . Additionally if the MTA would reject connections from IPs that generate too many errors, then why is Mailman 3 still able to deliver to domain B and C when domain A has already failed? Currently I am trying to write a script to check if mail aliasses are alive and remove users if that check should fail. I plan to run this as a cron job for every list every night. I don't think that this is a good option, but I don't see anything better right now. Julian Am Tue, 12 Jul 2022 10:45:16 +0100 schrieb Tim Cutts <tim(a)thecutts.org>: > Are you sure that’s mailman doing that? What do your MTA logs say? > I’ve certainly seen behaviour that looks like that in the past, but > usually my MTA logs show that the first few are accepted by the > remote site, and then the subsequent messages get rejected, usually > as a result of over-zealous spam filtering. My approach to that has > usually been to adjust my MTA settings to be a bit friendlier to the > sites that tend to do this, and only send a few messages at a time. > > Tim > > > On 12 Jul 2022, at 08:34, Julian Kippels <kippels(a)hhu.de> wrote: > > > > Hi, > > > > We have recently upgraded from Mailman 2 to Mailman 3. Since then I > > have observed many user reports that mails to mailing lists don't > > reach all members. My suspicion is that there are too many "dead" > > members on those lists. This was not a problem on Mailman 2, but > > has become a problem on Mailman 3. It seems to me that for example > > Mailman 3 sends mails to the first 5 existing member addresses from > > domain A, then encounters several (20 or so seems to be the > > threshold) "dead" member addresses from domain A that generate a > > bounce and then does not even attempt to reach the remaining 800 > > member adresses from domain A and only sends to members on domain B > > and domain C. > > > > Is there a way to globaly ignore bounces and send out mails to all > > members of a list, no matter what? > > > > Thanks, > > Julian > > _______________________________________________ > > 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/ > > > -- --------------------------------------------------------- | | Julian Kippels | | M.Sc. Informatik | | | | Zentrum für Informations- und Medientechnologie | | Heinrich-Heine-Universität Düsseldorf | | Universitätsstr. 1 | | Raum 25.41.O1.32 | | 40225 Düsseldorf / Germany | | | | Tel: +49-211-81-14920 | | mail: kippels(a)hhu.de ---------------------------------------------------------

3 years, 7 months

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

by Stephen J. Turnbull

hansen(a)rc.org writes: > We have had to reboot the list server almost every week and wonder > if there is something leaking and eating up resources. That's something you would have to check yourself, using Unix tools like ps, df, and lsof or Activity Monitor on Mac. I don't recall any cumulative resource problems like this. Some old reports indicate certain configurations and activity patterns put a lot of instantaneous pressure on the system, but this doesn't sound like that. Also those problems were specific to the software stack (databases, caches, search engines) that was used. The current recommended stacks do not have those problems as far as I know. The only current performance problem I'm aware of is in using the REST API directly to get large collections (eg, 10,000 member subscriber lists). (My currect thinking is that those are best addressed by using the corresponding paged endpoints, but still researching.) However, that is not a cumulative problem, it's a size-of-list problem, so it doesn't sound related. Are you running all of Mailman core, Postorius, and HyperKitty on the same server? For Postorius and HyperKitty, what webserver are you using? What database backend? What other applications are running on the server? What operating system and version? Recent hardware? > I does not appear to be memory, though. The server is slow to > respond (could be because it's overseas) and then after some time > we get intermittent gateway errors and finally we cannot access the > lists online because of the gateway errors. What does "gateway errors" mean? If problems with Internet routing or firewalls, I don't understand how network errors could be arise from a problem in Postorius. Why do you think Postorius could be responsible for those, aside from them appearing after switching to Mailman 3? Are you sure you weren't having them before? > It appears to me that the issue is with Postorius, but I could be > wrong. Do files get closed after opening? Yes, as far as we know. No reason to think otherwise since this is not something that has been reported that I can recall, and Python 3 helps us to code in a style that is not so vulnerable to such leaks. > Are we alone having such issues? So far, yes. > PS: My old MM2 installation could (and did) run without any > help. Not so with MM3. I don't think any of *our* feelings would be hurt if people decided to keep their Mailman 2 installations. :-) It's still great software for what it does. But it took more than 10 years to get there (the first production installations were in about 1994! and it's been feature- stable since about 2005 I'd guess. Unfortunately it wasn't possible to bring in the kind of features that many people need nowadays without a complete rewrite (partly a matter of manpower -- Python 3 brings a lot of power and fun to programming, partly a matter of technical debt making Mailman 2 code hard to change in big ways, and partly a matter of the need to port to Python 3 for the very long run), and the new features themselves changed the way that Mailman (and Mailman's users and administrators) interact with the network.

5 years, 10 months

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

by Allan Hansen

Thank youi, Stephen. Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still show up as 'B'. Now, for the workaround: " If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists." I modified the above workflow to: Removed the address from all the lists. Set the account display name to 'A' in Django. Verify that she is not subscribed to any list at all. Deleted the email address in Django (under 'Email addresses'). Resubscribed her as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still has 'B' when I list it in Postorius. Further: When I search for 'Email addresses' in Django's list of emails (by account or email), it no longer exists. When I search under 'Users' (by account or email), it exists with 'A' as the display (which she entered when she created the account). Then since the email does not exist, under 'Email addresses' in Django, I go to 'Add email address', enter her account name and address. This gives and error: 'Select a valid choice. That choice is not one of the available choices.' I get this error no matter which 'Save...' button I press. I then tried to get into REST as per your advice here: " I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) " I get this, after setting myself up as user mailman (which works when entering mailman commands): mailman@list:~/scripts$ python3 Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> from mailman.testing.documentation import dump_json Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'mailman' Looking around, I found mailman related stuff in /opt/mailman/mm and a file called 'mailman' in opt/mailman/mm/bin but hesitated editing your command above to: /opt/mailman/mm/mailman.testing.documentation (I don't want to mess up my system). So no go... Sorry for ranting. __ Please: 1. Always use the display name and email set up in the account everywhere. 2. Allow the member to change her display name using the account UI. 3. Allow the member to change her address and apply the new address to all list subscriptions. Yours, Allan On 1/11/22, 7:20 , "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: Allan Hansen writes: > When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' > <a(a)foo.com>. If I recall correctly, this issue occurs because Subscription objects have no display name attribute, but User and Address objects do. First, the advice part: > What can I do to help this member? Unfortunately the mailman command line utility doesn't seem to allow changing the display name. The REST interface does, though. I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) should do what you want. Note the numbers "8001" (Mailman core's REST port) and "3.1" (the API version) may be different on your system, I'm assuming the default install of a recent Mailman release. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information about accessing the REST API and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for a few more details on the update process. On to the rants, if you care. > I went into Django and added the name 'B' to the subscriber's > account (the name was empty). > > I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' > <a(a)foo.com>. > > The subscription again lists as 'B' <a(a)foo.com>. Does the user need to have different display names for different addresses? (I don't think it's possible to have different display names for the same address on different lists because there's no display name at all for Subscription objects.) If the answer is "no", the correct thing to do is to set the desired display name on the user's account. If the answer is "yes", there doesn't seem to be any way to do this with current Postorius/HyperKitty. Postorius doesn't expose the display name anywhere that I can see, and HyperKitty only manages the account's "real name". > This brings up a previous discussion of display names on this list, > but I have not been able to find any solution to the need to change > Mailman3's display names for a subscriber. It is beyond weird that > unsubscribing, setting the account display name and resubscribing > the member fishes back up the old and wrong display name. Unless you explained what you did incorrectly this is not weird, it's the expected result. You set "B" in the account, that's what's going to show up as the display name. It is not obvious that a new subscription should change an existing display name for a user or an address, given that there is no way to set a list-specific display name. It could go either way, and for the user I would definitely not change it, for the address I tend to agree that a new subscription should not change the address's display name. I agree that it's weird that neither Postorius nor HyperKitty seems to expose a way to set Address display names, though. If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists.

4 years, 1 month

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

by Mohsen Masoudfar

Hi Mark, Thanks again for the helpful hint. It seems that I still miss something. I am running Mailman3.1.1. I ran the following on my test server. I am trying, for test purpose only, to filter PDF attachments. First I just used the pass_type, assuming once this is set, everything else is filtered. # mailman withlist testlist3(a)x.com >>> m.pass_types = ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>> commit() >>> print(list(m.pass_types)) ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] This let PDF be send by Mailman3. Well, I need to add filter_types too, so I did this: >>> m.filter_types = ['application/pdf'] >>> commit() >>> print(list(m.filter_types)) ['application/pdf'] Mailman3 still distributes PDF files as attachment. What am I doing wrong? This is the final settings: >>> print(list(m.pass_types)) ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>> print(list(m.filter_types)) ['application/pdf'] Thanks Mohsen Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, September 30, 2020 1:07 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list [EXTERNAL EMAIL] 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail > man.readthedocs.io%2Fen%2Fstable%2Fbuild%2Flib%2Fmailman%2Fhandlers%2F > docs%2Ffiltering.html%3Fhighlight%3Dcontent%2520filter&data=01%7C0 > 1%7Cmmasoudf%40aaas.org%7Ceb728218f9884b4bfc1a08d865635075%7C2eebd8ff9 > ed140f0a15638e5dfb3bc56%7C0&sdata=mGUdz5NfrJgEyPmd5Isa0l01WWPQMpTA > 9thyWLZ0qbU%3D&reserved=0 > > 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.r…> 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.…> 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 _______________________________________________ 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, 5 months

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

by Mark Sapiro

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

4 years, 5 months

[MM3-users] Re: Add rule to auto-discard "AutoReply" messages from list members

by Abhilash Raj

On 11/16/23 01:07, Thomas Ward via Mailman-users wrote: > When people are communicating on Mailman3 lists, some set up automatic > responders for out-of-office, etc. and get let through the system to > list recipients. > > Unfortunately, this is bad behavior and appears to not be caught by > default. I'd like to set up some kind of rule globally rather than > per-list that would check if a message is an automatic reply (based on a > set of criteria we've come up with programmatically on our previous > custom implementation of lists) and then default-discard those messages. > > Is there a way with custom rules to implement this? We're looking for > certain strings on the subject line or other headers to determine > "Discard" cases in our custom list implementations, but we are hoping we > can implement this with customized rules in Mailman3 to achieve this > goal. How would we structure that type of rule, and do we check the > message object or the msgdata instead? You can implement a custom rule and a custom chain to do this, but you'd need to set that as the default chain on every existing list. Setting the default chain can be scripted using `mailman shell` pretty easily though. For any new lists, you can setup a custom style(s) and ensure that your new chain is the default chain for new lists. https://gitlab.com/mailman/example-mailman-plugin/-/blob/master/example_mai… ^ is an example plugin you can use as a starting point for your plugin and you will also see example rule at `rules/rules.py`. https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/rules The above existing rules in Mailman's source code should serve as examples on how you can look at a header or body of the email. For example, approved.py looks for certain headers (var HEADERS in the file) or iterates through the body to look for something that looks like a header too ("Approved: <password>"). Once you have the rule, you can insert it in the right place in the chain. You can use the default-posting-chain https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/builtin… as your starting point (example plugin doesn't have an example chain yet, but it would look similar to inbuilt chains, under a "chains/" directory in the plugin). In the chain, you can also define what happens if rule matches. Rules only return True/False, based on whether the rule matched and chain can define if that should put the message into a separate queue (e.g. ('my-new-rule', LinkAction.jump , 'hold'), etc. or do nothing ('my-new-rule', `LinkAction.defer`, None). There are also example styles defined in the plugin https://gitlab.com/mailman/example-mailman-plugin/-/blob/master/example_mai… You mostly want to update `posting_chain` property on the 'mlist' object for the style. You can find examples again in the source tree under `src/mailman/styles` directory. To configure the default style for new lists, you can add the following to your mailman.cfg: [styles] default: my-new-style ref: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/config/doc… Let us know if you have any questions on the same. -- thanks, Abhilash Raj (maxking)

2 years, 3 months

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

by Simon HANNA

On August 3, 2017 8:50:41 PM GMT+02:00, Rafael Mora <rafael.mora.guti(a)gmail.com> wrote: >El jue., 3 ago. 2017 a las 13:21, Mark Sapiro (<mark(a)msapiro.net>) >escribió: > >> On 08/03/2017 10:42 AM, Rafael Mora wrote: >> > >> > I've found the MX records on my cpanel but how do I redirect the >emails >> > going to my list to my private server? >> >> >> You have to configure the MTA that is the MX for the domain to relay >the >> mail to the Mailman server. >> > >Our domain is: LABBRANDS.COM We have that domain config in a Hosgator >hosting. The emails sent to labbrands.com go to our hosting, so how do >I >tell cpanel in hostgator hosting that the mails sent to the list ( >mailing(a)labbrands.com) are redirect to the MTA (postfix) in my private >server (we have static public IP address) ?? > You can't redirect one email address using DNS! If you don't want to host an entire domain on your own server, I suggest using a subdomain (lists.example.con) instead. You could probably also redirect one email in cpanel to the subdomain, but I'm not sure how mailman and clients like emails with different domains... In theory postfix can send emails using any domain. You just have to make sure spf, dkim and PTR records are properly set. Otherwise you'll most likely get issues with rejected mail... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 7 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 5/7/19 1:54 AM, Henrik Rasmussen wrote: > Do I have to make a commit or something? Even m.accept_these_nonmembers.remove removes the member from the list, it is right back when I return to the Mailman shell: > >> bash-4.3# mailman shell -l [LISTNAME].lists.example.com >> Welcome to the GNU Mailman shell >> The variable 'm' is the [LISTNAME].lists.example.com mailing list >>>>> m.accept_these_nonmembers >> ['listadmin(a)senderdep.example.com'] >>>>> m.accept_these_nonmembers.remove('listadmin(a)senderdep.example.com') >>>>> m.accept_these_nonmembers >> [] >> quit() There are potentially two issues here. First, the entire interaction is in the context of a database transaction and quit() exits without committing the transaction. abort() will also abandon the changes but not exit. commit() will commit the changes and not exit, and control-D will implicitly commit and exit. Thus, you need to exit with control-D or commit() before quit(). However, there is another potential issue and that is the one described at <https://stackoverflow.com/questions/37310770/sqlalchemy-committing-pickle-t…>. What this says is the way the *_these_nonmembers attributes are defined in the SQLAlchemy data model results in changes due to mutating the list (which .remove() does) aren't recognized. See <https://gitlab.com/mailman/mailman/merge_requests/505>. I think in your case, if you just do m.accept_these_nonmembers = [] commit() and then look at m.accept_these_nonmembers again which will show you what's in the database, you'll see that you have what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

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

by Odhiambo Washington

On Sat, Jan 14, 2023 at 11:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 11:44, Odhiambo Washington wrote: > > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Nothing in those releases per se would affect this. This is Django and > >> django-allauth. Perhaps when you updated the Mailman packages, you also > >> updated these dependencies. > >> > > > > Which dependencies would those be? > > Django and django-allauth. > (venv) [mailman@gw ~/mm]$ pip freeze | grep jango Django==4.1.5 django-allauth==0.52.0 django-appconf==1.0.5 django-compressor==4.1 django-extensions==3.2.1 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.9 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 > > > > When I upgraded, the command I ran was: > > > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > > mailman-hyperkitty django-mailman3 > > > Do you mean --force-reinstall? pip has no --force option. I *think* > --force-reinstall will upgrade dependencies. Depending on your pip > version, --upgrade alone may or may not upgrade dependences. Older > versions of pip will, but newer versions, at least without > --force-upgrade require --upgrade-strategy eager to update dependencies. > I have used --force-reinstall. > > And how do I find out what is suppressing the logging for the social > > accounts? > > That's a django-allauth question. > Let me go RTFM again :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

[MM3-users] Re: applying patch 1130

by David Newman

On 8/20/23 9:34 PM, Stephen J. Turnbull wrote: > David Newman writes: > > > I tried patching all importlib.resource references by hand, and MM3 > > starts ? but that can't be the "right" way to do this. Also, the > > diff references a src directory that doesn't exist under > > /opt/mailman. > > The "right" way to do this kind of thing is to clone the git > repository, apply the patch there, make a branch for it and commit it, > build a wheel, and use pip to install that wheel to the venv. > > > Thanks in advance for patching clues. > > I'm in a hurry so that's all the clue for now, but further inquiries > are welcome if you need more detail or something doesn't go as > expected. Thanks for your response, Steve. One detail that doesn't seem right is that the 1130.patch from GitLab references at least one file, .gitlab-ci.yml, that doesn't exist in the 3.3.8 production release that's installed when using 'pip install mailman' in the venv installation docs. Just running 'git apply 1130.patch' on a local copy of the production 3.3.8 code fails because the file .gitlab-ci.yml isn't part of that code. There may be other errors too but the patch fails on that first one. I'm looking to patch an existing production server running 3.3.8 so it will be able to start under Python 3.11 on Debian 12. Thanks in advance for additional clues on what seems like a fairly standard problem. dn

2 years, 6 months

[MM3-users] Rolling releases for Container Images and Funding Campaign for Mailman

by Simon Hanna

>>> These images are built using git-heads *only* if they are passing our >>> test suite and are re-generated weekly. You should be aware that while >>> all these components are tested with their individual test suites, their >>> combination might sometimes not be stable. This will get you >>> updates/bug-fixes much faster :) >> This contradicts what you said in my merge request for Postorius >> https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 >> >> You either use released versions, or make sure that the master branches >> are always compatible. You can't have both with the current development >> model. > Not exactly, I still believe all our git-heads should be compatible with > released (i.e. stable) versions of dependencies, regardless of the fact > that we maintain those dependencies. > > Also, there is at least one test per-project which tests with git-heads > of dependencies we maintain, so that we know if we make any incompatible > changes. > > I am not sure what in the current development model prevents us > to do both? > > The story for container images is different than testing with git-heads. > We need better integration testing for the entire suite to be stable in > conjunction, rather than independently. In fact, containers might be the > perfect way to actually do the integration testing. Scenario: Core changes something about rest that is backwards incompatible. The change is commited to master. Since your containers use the master branches, all future builds will fail until mailmanclient and postorius/hyperkitty. If you want to always have Postorius (and others) compatible with the latest release of master, development for Postorius will be a Pain, because you can't use the master branch of mailman for testing and quick changes. Also your containers and all integration tests that can be done with them will always fail. Until you fix Postorius and the other clients... So why not just have the master branches always compatible and make life easier for developers. I don't see a good reason why you want to do it the other way round... Any bug in core that affects Postorius will also just remain there until you release a new version of core. If you really really want to have it your way, there have to be more frequent releases. >>> - Improve the container images to work with new micro-services >>> architecture, >>> to achieve scaling and redundancy in services. >> The current bottleneck is the rest api from core. IMO bulk actions, >> filtering and sorting should be added there before trying to have >> multiple postorius/hyperkitty instances serving the same core... > I didn't say they will be served from the same core ;-) > > Yes, the Core's API can be further improved to be more efficient. But > that > doesn't prevent us from scaling. I understand there are issues around > multiple > instances of containers, but I have ideas to get around most of them. I just don't want that people that have issues with big installations get the answer: We know of that issue, please deploy Mailman on X containers/machines as a workaround

8 years, 3 months

[MM3-users] dkim failing

by Stephen J. Turnbull

Abhijith PA writes: > I am seeing dkim fail in mail that people send to lists > /dkim=fail reason="signature verification failed"/ It sounds like you mean at the final destination. This is expected if Mailman alters the portions of the message that are signed. This depends on the configuration of DKIM at the message sending MTA, but typically is triggered if - Mailman adds a header or footer - Mailman adds a list tag or post serial number to Subject - Mailman alters From to avoid DMARC problems. If you're sure it is new and Mailman is configured to do none of the above, it's not a Mailman problem. > but it is not happening when the list solely sending mail to subscribers > (like digest, or subscribe/unsubscribe messages etc). Mailman has nothing to do with DKIM in this case. It's all handled by the MTA after Mailman passes the mail to it. > I recently added a new domain to the mailman3. After this I started > noticing this issue. Any help ? This could happen if the new domain does not have DKIM configured correctly in the DNS or the MTA. If it is new, this is not a Mailman problem based on your description. If you stil think it's a Mailman problem, we need more information. A complete copy of the headers of a message that failed DKIM is the minimum. You MUST preserve the addresses. If it bothers you to send such information to a public list (this one), you can send it to me, Mark, or Abhilash personally. (You can get their addresses from past mails to this list.) Regards, Steve

7 years, 4 months

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

by David Newman

On 7/8/22 6:34 AM, Stephen J. Turnbull wrote: > David Newman writes: > > > Interesting -- that does produce two directories with names starting > > with a tilde: > > > > /opt/mailman/venv/lib/python3.9/site-packages/~jango: > > /opt/mailman/venv/lib/python3.9/site-packages/~jango-3.0.14.dist-info: > > I would guess that those are the previous versions before the upgrade, > moved out of the way in case a revert-to-previous was needed. Again, > guessing, they should have been removed by the upgrade process once > the new package was fully installed. Was there an interrupted or > partially successful upgrade in the past? Yes > > So I would guess you can remove them. Probably you have the relevant > Ubuntu packages cached somewhere, and they're probably available from > Ubuntu if you really wanted them. This system runs Debian 11, with everything installed in a venv. I'm unclear on the relationship between the usual apt* tools and pip, and just do everything Mailman-related using pip. On 7/8/22 7:47 AM, Mark Sapiro wrote: > When pip is doing an upgrade of the xyz package, it renames the existing > package as ~yz and then ultimately deletes the old ~yz package after > successfully installing the new xyz. In this case, the upgrade was > aborted because of the Django<3.1 constraint in mailman-web and > apparently pip then installed Django<3.1 and left the ~jango* > directories behind. Ahhh, that explains it. Thanks for your replies. I've deleted the ~ directories and so far have not noticed any adverse effects. dn

3 years, 7 months

[MM3-users] Re: accept mails from several Users, not list members beside members, howto

by Lars Schimmer

On 12/07/2021 20:14, Abhilash Raj wrote: > > > On Mon, Jul 12, 2021, at 6:23 AM, Lars Schimmer wrote: >> Hi >> >> I do look out for a method to accept mails from list members and a >> number of 20-30 Email addresses (not list members) to a mailing list. >> All others should be denied to post to the list. >> >> I can add those as non-members, but AFAIK I cannot define a special rule >> for them in "message acceptance". > > You can go to Users -> Non-Members and find the non-members you want > to allow posting for and then go into their preferences and set their Moderation > Action to "Default processing". > >> Under "message acceptance" the line "non-members" is set to deny, but if >> I set it to "default procesessing" - will it allow ALL email addresses, >> or just the group of "non-member" users? > > Yes, that will allow all non-members to post, which probably isn't what you > want from what I gather. You want the default policy to be deny and then set > moderation action on each individual non-member. Thank you. I would have hoped for a extra input box to enter a list of ~100 email addresses, but ok, lets do it this way. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years, 7 months

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

by Ruth Ivimey-Cook

On 03/01/2021 15:47, Stephen J. Turnbull wrote: > ieso(a)johnwillson.com writes: > > > Here's an interesting suggestion I received that I'm going to kick > > around a bit.. has anyone tried using Ansible to assist the > > installation process? > > > > https://github.com/rivimey/ansible-mailman3 > > rivimey is very competent. That would undoubtedly be a good place to > start. However, her setup may be more complicated than most folks > need (IIRC, she has a multi-homed setup with Mailman core, Postorius, > and HyperKitty on three separate IPs on a separate subnet in the DMZ, > while Mailman was really designed for three Mailman applications > running on the same host, along with the database server and MTA). Thank you for your compliment. I have only split mailman in two: mailman-core with the email-related parts, and postorius for the UI. As yet, although Hyperkitty "works", I haven't addressed the fact that mails get archived in folders on the email host and so (for me) hyperkitty can't see them. Ideally, they would be on the postorius/hyperkitty host, or possibly network shared The Ansible role linked to above includes a lot of options but doesn't impose splitting the components as I've said: it merely enables it. If anyone wants to further refine the ansible role I am happy to consider updates, especially sorting the archive! In an earlier post on this thread (that I now see was only sent to ieso@ -- sorry!) I linked to the role I used as a starting point for my work, which does indeed do most of the "simple out-of-the-box" implementation of mailman. > the "ansible-mailman3" role by "natefoo": Mailman 3 installation, > configuration, and management for Linux > > There are other ansible roles which will install mysql etc as needed. > If I didn't need to split the host for mailman3-core from > mailman3-web, I think it would have worked out of the box. > > I hadn't heard of Ansible before, but it looks perfect for this > > kind of situation. > > I'm not sure we want to maintain an Ansible configuration, but I > imagine we could stick it in contrib as "an example that works for > somebody YMMV unsupported NO WARRANTY". :-) Ansible is very good at describing deployments and I would definitely suggest investigating it if you are doing that sort of thing. One of the nice parts of Ansible is that you do not have to describe whole hosts - it will happily manage a small part without compromise. Another really nice part is that it requires very little of the host. If Ansible is not to your liking, you may find "Salt" and "Saltstack" an improvement, though for me it was not as good. Ansible has a role archive in the form of the Ansible Galaxy website; I would suggest simply that Mailman docs mention the role's existence. As an Ansible user, that is where I would look first, so the main point of mentioning it in mailman docs is to let people who don't use Ansible know about it. Regards, Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 2 months

[MM3-users] Re: Is there an option to "disable" a list temporarily? (feature request?!)

by Washington Odhiambo

On Mon, Feb 2, 2026 at 2:27 PM Christian Schneider < christian.schneider(a)tu-dortmund.de> wrote: > Hello dear Mailman Team, > > I scanned through the web interface of my mailman instance... > and I did not find an option to disable a list temporarily ("sending" and > "access to web interface")... > This might come in handy when a list is abused for sending spams > or when a list owner wants his/her list to be removed... > Instead of removing the list instantly I would disable it for three months > first... > (You never know with users... ;-) ) > Preferably I would backup the list (settings and members) and the archives, > but as seen in the discussion there is actually no backup mechanism for > lists... > > Is there an option to disable a list (except from resetting passwords and > remove/disable mail aliases)? > To disable access to Postorius, you can achieve that using the web server. To disable mail processing, you do that by disabling the mail aliases or just redirect a list address to /dev/null. > If not I'd like to hand this in as a feature request... xD > I always see the Devs say that you do that by creating an issue in gitlab. -- 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

[MM3-users] Re: Hyperkitty import from mailman2

by Mark Sapiro

> > Now I wanted to try import from mailman2 mbox, so i did: > > python2 manage.py hyperkitty_import --settings settings --ignore-mtime > -v 3 --since 2010-01-01 -l test(a)list.domain.com /tmp/test.mbox > > It shows that it have sucessfully imported all emails and I can see them > from database (sqlite3), but I cannot see them from GUI (hyperkitty). > Only thing I can see is this inactive "test" list. > > I have tried that I create list before importing, still same result. I have done this several times for several different lists and it has always worked with no problems. I have always created the list first. I do not use any of the options other than -l. My settings location is built in to the django admin script I run. So what I run is equivalent to python2 manage.py hyperkitty_import --settings .. -l .. mbox Do you have cron set up to run the periodic django tasks as in @hourly python2 manage.py runjobs --settings settings hourly @daily python2 manage.py runjobs --settings settings daily @weekly python2 manage.py runjobs --settings settings weekly @monthly python2 manage.py runjobs --settings settings monthly @yearly python2 manage.py runjobs --settings settings yearly 0,15,30,45 * * * * python2 manage.py runjobs --settings settings quarter_hourly * * * * * python2 manage.py runjobs --settings settings minutely If not, did you run python2 manage.py update_index --settings settings after the hyperkitty_import? I'm actually not sure any of this will help since it should only affect the search index, not the message display. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: User settings triggers error

by Mark Sapiro

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. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Moderator Approval Subscription template

by Mark Sapiro

On 2/8/21 5:55 PM, Brian Carpenter wrote: > Hey all, > > I am seeing a strange issue with the Moderator Approval Subscription > template. > > 1. First problem is that this template by default does not include a URL > to the list admin page of said mailing list. Mailman 2's notifications did. Mailman 2 was monolithic. Mailman 3 is Modular. Core, which sends this notice, doesn't know if you even have a web admin UI, much less how to access it. It has been suggested that we add a config setting for the web base URL and if that is set, include URLs in these messages and we may eventually do that, but in the mean time > 2. Problem 1 can be solved by editing the template and adding the List > Owner (admin) url to moderate the subscription. This is what you need to do. > However in the case of > long URLs, the URL is getting cut-off in Thunderbird. Not sure about > other email clients. That is an issue because the expanded template is filled and wrapped at column 70 with mailman.utilities.string.wrap(). However, you can avoid wrapping the URL by preceding it in the template with a space. Something like > Your authorization is required for a mailing list subscription request > approval: > > For: $member > List: $listname > > Visit > > https://list.redeacted.org/admin/list/oligodendroglioma.list.redacted.org > > to act on this request. Lines beginning with spaces aren't wrapped. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

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

by Mark Sapiro

On 2/17/22 15:15, Élodie BOSSIER via Mailman-users wrote: > Hello, > > My mailman3 installation is now functional, but the config "FILTER_VHOST > = True" doesn't work fine when I define "alias_domain" for the 2 > domains. I need to define that because I need to get "postfix_vmap" file. > > As you can see, list from others domains are visible on this URL : > https://ml.franceserv.fr/postorius/lists/ > > I would like https://ml.franceserv.fr/postorius/lists/ and > https://ml.viticreation.fr/postorius/lists/ with their own lists. There are issues with FILTER_VHOST due to the fact that mailing lists do not have a web host attribute. This means when you go to HyperKitty or Postorius when FILTER_VHOST is True, we look up the domain record for the web host you are visiting and show you all the lists whose mail host matches the mail host for the web host domain. This has nothing to do with alias domains. What that means is if all your domains records have a unique mail host, FILTER_VHOST will work as you expect, but if multiple domains have the same mail host FILTER_VHOST will show you the lists for the current web host plus all those with a matching mail host. I.e. if in your case, the ml.franceserv.fr domain and the ml.viticreation.fr domain have the same mail host, FILTER_VHOST won't separate them. If they have different mail hosts FILTER_VHOST will separate them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

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

by Mark Sapiro

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. -- 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: 3rd Party Account is not working

by Stephen J. Turnbull

kwp.klein(a)gmail.com writes: > Here is my /mailamn/config/mailman-web/settings_local.py. I get an error message > > curl http://172.19.199.3:8000/postorius/lists/ > curl: (7) Failed connect to 172.19.199.3:8000; No route to host > Please comment out all the lines that are not necessary. This is not a Mailman problem; curl can't connect to the Mailman host because there's no way to get there from here. We may not be the best place to ask about network problems. That said, we'll do what we can. We need to know what your network configuration is. I assume that 172.19.199.1 and 172.19.199.3 are on the same subnet, and that 172.19.199.3 is the host for Postorius. Where is Mailman core? Do you have HyperKitty installed? On what host? I assume that 172.19.199.1 is the host with the MTA for this network. I don't know if this is related to your original problem "Server error An error occurred while processing your request." However, if the network is not working properly Mailman is going to be very unhappy. > MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = '172.19.199.1' > EMAIL_PORT = 25 > USE_SSL = False > > INSTALLED_APPS = ( [...] > 'allauth', > 'allauth.account', > 'allauth.socialaccount', I think you may want to disable allauth.socialaccount as well. > #'django_mailman3.lib.auth.fedora', > #'allauth.socialaccount.providers.openid', > #'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > #'allauth.socialaccount.providers.google', > ) > _______________________________________________ > 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] Mailman 3 installation, no mails in hyperkitty, unable to add footer.

by ugniusviln＠gmail.com

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. Except uwsgi.ini, I have only 2 configuration files in mailman-suite project directory: settings.py and mailman.cfg So I do not understand what did I configured badly. 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.

6 years, 6 months

[MM3-users] Re: Subscription Request asking for Confirmation instead of Moderation

by Stephen J. Turnbull

Henry Hartley via Mailman-users writes: >>> 1. Are there particular headers that are causing the email >>> to go to the Confirmation page instead of the Approval page? Or >>> are there particular headers we can add that will help with this? No. That's entirely determined by the list's configuration. You cannot change that behavior via a user's subscription request whether by email or web. IIRC, the only overrides are either through the REST API, "mailman shell", or the "mass subscribe" page on the web. (I guess it's possible that the moderator can "pre confirm" at approval time, do you see such an option when you approve? I've never managed a "moderate" list so I don't know without groveling through the code.) Do you really only have one list? Is it possible that the misbehaving list is not configured as you expect (ie, the list subscription policy is "confirm" or "confirm then moderate")? Unlikely, but if you haven't checked since the problem started, please confirm. Are you sure that the members have not been approved by some moderator? I forget exactly how this works, but unless you use mass subscribe with the "pre confirm" option set, the user will have to confirm before they can receive mail. I believe that all outgoing messages from Mailman should be logged. So you should check for outgoing confirmation notices. Posts are given a summary log like "smtp to somelist(a)example.org for 225 recips". IIRC notices (such as confirmations) are logged as "smtp to FirstLast(a)SCHOOL.org" for each individual notice. (My own production lists were all "mass subscribe" lists so I don't have any notice examples.) Notice logs are usually in $log_dir/smtp.log, but some sites configure them to a separate log. After the Mailman logs, they should show up in the MTA logs. Posts are always logged with the Message-ID, I think notices are as well. > > > 2. Is there any way for us to move an address from the > > > Confirmation Pending page to confirmed on the backend > > > (preferably through the web interface, but on the server > > > itself, if necessary)? Not that I know of, but what you can do is mass subscribe those addresses. I think that you'll still end up with them waiting for confirmation as described above. You can confirm them by accessing the database directly, but that's more fraught than I want to deal with at bedtime :-). > > > Here are the headers sent with the subscriber's email address > > > changed to FirstLast(a)SCHOOL.edu and our BCC mailbox domain > > > changed to COMPANY.com. Is FirstLast(a)SCHOOL.edu in the Confirmation Pending page? [...] > > > X-Mailer: Drupal Good, this is the Drupal script. Saves me from asking for confirmation. > > > Return-Path: FirstLast(a)SCHOOL.edu > > > Sender: FirstLast(a)SCHOOL.edu > > > From: FirstLast(a)SCHOOL.edu Pretty sure that only From is consulted by the subscription machinery. Since they're all the same this shouldn't matter. Since this is an on-behalf-of message, most likely Return-Path and Sender should *not* be the user -- if something goes wrong, they can't do anything to fix it. > Note also that the mailto: links above (and below, if applicable) > are not in the text I'm pasting but have been added somewhere along > the line. Presumably you did a screen copy from the presentation version rather than the raw text of the message. > Authentication-Results: spf=fail (sender IP is 192.168.0.0) > smtp.mailfrom=SCHOOL.edu; dkim=none (message not signed) > header.d=none;dmarc=fail action=oreject > header.from=SCHOOL.edu;compauth=fail reason=000 This requires some care. DMARC is failing, and necessarily will fail. If SCHOOL.edu has a p=reject policy, this mail should not get to Mailman at all. Also, your Drupal host is not signing its mail. This doesn't necessarily matter for this script, since it can't pass DMARC, so you need to have an alternative way to trust mail from it. But it is really important that your Mailman host sign its mail, especially mail it originates, because many hosts will discard, reject, or quarantine unauthenticated email that looks like it was generated by a robot and contains links. This could explain some cases of subscribers apparently not receiving confirmation notices. You could check the "shunt", "bad", and "virgin" queues to see if confirmation messages are hung up in one of those. If the Drupal host is the Mailman host, then you could use the PHP script to talk to the REST API instead of using email. Cutting out the long list of middlemen, so to speak. (It would also be possible if they're different hosts, but the security precautions I would recommend are quite a bit more severe.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months

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

by Abhilash Raj

On Sun, Feb 10, 2019, at 6:54 PM, Nick Wynja wrote: > On 02/10/19 at 08:57, brian(a)emwd.com <brian(a)emwd.com> wrote: > > > "In your `settings_local.py` copy the whole INSTALLED_APPS section from [default settings](https://github.com/maxking/docker-mailman/blob/master/web/mailman… and add/remove the auth providers you want/don't want. Notice the `allauth.socialaccount.providers.<provider>` in the list below." > > Another option, which seems more future-proof, is to strictly remove > the account providers you don't want from INSTALLED_APPS rather than > defining INSTALLED_APPS locally. > > First, you have to access INSTALLED_APPS by importing settings into > settings_local.py: > > ``` > from settings import * > ``` > > Then, you can set INSTALLED_APPS to everything it already is minus the > social providers: > > ``` > INSTALLED_APPS = [a for a in INSTALLED_APPS if not > a.startswith('allauth.socialaccount.providers') and not > a.startswith('django_mailman3.lib.auth.fedora')] > ``` > > This way if Postorius ever adds any apps you won't need to update your > local settings. Anyone see any downsides to doing it this way? Please don't do that, it will create a circular import since settings_local.py is imported by settings. Postorius (actually, allauth) adding more providers won't affect the INSTALLED_APPS list, which is a static setting defined in the container images. Unless the image changes that list, it won't affect you. Having the list customized is actually good for you, since there is some extra configuration required for adding a new provider, so you don't want something to just show up without you knowing. -- thanks, Abhilash Raj (maxking)

7 years

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

by Allan Hansen

They need to resubscribe to each list they want the new address to be used for. Subscriptions involves permissions from the moderators. It’s not a simple process, especially if you are on many lists. Yours, Allan Hansen hansen(a)rc.org > On Feb 12, 2021, at 8:47 , Andreas Barth <aba(a)ayous.org> wrote: > > * Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210212 12:04]: >> hansen(a)rc.org writes: >>> b. The ability of members to change their addresses for all lists >>> they are subscribed to. >> >> What exactly do you want here? I can think of a number of ways to >> implement that, depending on whether the old address is to be >> deactivated from the lists, unsubscribed from the lists, or deleted >> from the Mailman and/or Postorius Users. There may be other >> variables to consider, as well; I haven't thought about this. AFAICS >> this is not a trivial feature, and I'd really like to hear from people >> who want "something like" this about exactly what they want and their >> use cases. Or we'll release an insufficiently designed feature that >> causes somebody hundreds of problems.... > > I thought user could do that if they have an web account, and multiple > mail addresses are associated with the account? Or does my memory > serve me wrong there? > > > Andi > _______________________________________________ > 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: [Mailman-Developers] Rolling releases for Container Images and Funding Campaign for Mailman

by Abhilash Raj

On Wed, Nov 8, 2017, at 04:38 AM, Simon Hanna wrote: > On 11/08/2017 12:03 AM, Abhilash Raj wrote: > > New images are available on quay.io and, moving forward, the rest of > > the image builds will also be moved to Quay[4][5]. > Since docker deployment is currently the recommended install, with > manual installs using the master branches for "experts" I wonder why you > are using Quay. For those who don't know about it, Quay is a container registry offering from CoreOS. The main reason why I chose to move to Quay, from DockerHub that we are currently using, is security. Some parts of both Dockerhub and Quay are open source and some aren't. There isn't a very clear boundary/transparency in what technologies they use. Both are free to use for open source projects. However, Quay provides an improved security model with RBAC to push images from build server, without having to put my account password on the build server. It also includes a (open source) security scanner for images, which looks for vulnerabilities in packages included in the image so that I can re-build them if one is found. There are open source registries available, most popular of which I know is provided by Gitlab. However, I feel Quay is better for my current workflow, which involves lots of bash scripts for building and testing images on public CI system for rolling releases. Given more free cycles, I do intend to have a better build pipeline and possibly use Gitlab's own registry to distribute images. > It looks like it's a non-free system. Why use Quay but refuse to use a > non-free translation system like transifex? > > These images are built using git-heads *only* if they are passing our > > test suite and are re-generated weekly. You should be aware that while > > all these components are tested with their individual test suites, their > > combination might sometimes not be stable. This will get you > > updates/bug-fixes much faster :) > This contradicts what you said in my merge request for Postorius > https://gitlab.com/mailman/postorius/merge_requests/232#note_43388756 > > You either use released versions, or make sure that the master branches > are always compatible. You can't have both with the current development > model. Not exactly, I still believe all our git-heads should be compatible with released (i.e. stable) versions of dependencies, regardless of the fact that we maintain those dependencies. Also, there is at least one test per-project which tests with git-heads of dependencies we maintain, so that we know if we make any incompatible changes. I am not sure what in the current development model prevents us to do both? The story for container images is different than testing with git-heads. We need better integration testing for the entire suite to be stable in conjunction, rather than independently. In fact, containers might be the perfect way to actually do the integration testing. > > If this campaign succeeds, here is a road map of what I intend to get > > done: > Sounds great, what is the limit where the campaign succeeds? What will > happen to the funds if it doesn't? > > - Add Admin Dashboard project from GSoC 2014 (maybe?) > Didn't find anything using google. What is that project about? https://www.google-melange.com/archive/gsoc/2015/orgs/gnu_mailman/projects/… > > - Add better testing of container images and provide deployment > > instructions for Kubernetes & Docker Swarm > To be honest, I don't think we should all in on containers. > Yes they are nice, but I guess most people would prefer distro packages. > Even if people want containers, I for instance would prefer plain > systemd-nspawn Like Barry mentioned, it doesn't have to be all-or-nothing. There is work being done on distro packaging for Debian and I am ready to help others trying to do the same for other distros! Systemd-nspawn isn't really a production grade tool to use containers. I am not sure about how much it adheres to the OCI specs, but if it does, it should not matter which deployment tool you are using with images. I wouldn't mind adding configurations for systemd-nspawn in the documentation, contributions are most welcome. > > - Improve the container images to work with new micro-services > > architecture, > > to achieve scaling and redundancy in services. > The current bottleneck is the rest api from core. IMO bulk actions, > filtering and sorting should be added there before trying to have > multiple postorius/hyperkitty instances serving the same core... I didn't say they will be served from the same core ;-) Yes, the Core's API can be further improved to be more efficient. But that doesn't prevent us from scaling. I understand there are issues around multiple instances of containers, but I have ideas to get around most of them. -- Abhilash Raj maxking(a)asynchronous.in

8 years, 3 months

[MM3-users] Changing subscription address

by Allan Hansen

All, I need help with this. A subscriber is a member of 14 of the lists on my system (others have more subscriptions). This member needs to change the address and is dyslexic, so I’ve been asked to help. I added the new address to her account in Django and set it as the preferred address. However, when she was subscribed, the system set her old address as the list subscription address, instead of her ‘preferred’ address. Well, I’m not sure of this as I cannot access her Settings, but that’s how it worked with one of my own addresses. Will I now have to tell her to do this for each list she is subscribed to: Select ‘Mailman Settings’ in dialog pulldown. Select one of the lists listed. Click on ‘Manage Subscription.’ In ‘Select Emai’, select the ‘Primary Address’ pulldown option Click on ‘Change email used for subscription.’ Please note that the “Global Mailman preferences’ nor the ‘Address-based preferences’ have the option to select the preferred address. I realize that once a member has an account in Django AND has preferred address set AND has selected the ‘Primary Address’ for each list, then this will be easier. However, I have 10000+ subscriptions by some 1500 members, most of whom were moved over from MM2 and have no Django accounts. Someone on list some time ago advised me that it was possible to do this easily globally. I have spent a couple of hours on the system trying to find that way but the above per-list procedure is all I found. Please make this easy, as I get these requests all the time and some, like this one, are on many lists. Yours, Allan

4 years, 11 months

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

by David Newman

On 11/25/21 10:28 AM, Mark Sapiro wrote: > On 11/24/21 10:17 PM, David Newman wrote: >> On 11/24/21 2:36 PM, Mark Sapiro wrote: >>> >>> To import archives run the Django admin command with arguments >>> >>> hyperkitty_import -l alist(a)example.com >>> /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox >> >> Good up to here, but ... hyperkitty_import not found. >> >> This wasn't covered in the venv docs: > > It is covered at > https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy > > Your issue is probably that the Django admin command you ran is not > accessing your `settings.py`. You may need to do > ``` > export DJANGO_SETTINGS_MODULE=settings > export PYTHONPATH=/path/to/directory/containing/settings.py > ``` > before running the Django admin command. These can also be given as > --settings and --pythonpath options to the Django admin command. Thanks for this. After setting these variables and restarting mailman3 and mailmanweb, the mailman user still cannot find a hyperkitty_import command (neither can root, btw). Again, I installed MM3 and Django/Postorius/Hyperkitty using the venv and web docs previously referenced. On the plus side, all lists now appear in the admin web page. However, lists created from the admin page do not appear in a site list page, even though all lists are in the same site/domain. Finally, how to make these exports permanent? I did not see this covered in the migration doc above. This is on a Debian system where the mailman user's shell is bash. Is this simply a matter of adding environment variables in the mailman user's .bashrc file? Thanks dn

4 years, 3 months

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

by Ruth Ivimey-Cook

Thanks Mark, On 20/06/2020 03:53, Mark Sapiro wrote: On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: I'm trying to set up mailman3 on two hosts, one of which runs core + exim, the other runs postorius (&possibly hyperkitty). I have I think got core set up correctly, and postorius is sort of usable, but anything in the web ui that talks to core ends up with a white screen. I think what is happening is a postorius URL ends up with the core (or perhaps no) hostname, and as there's nothing there to answer it fails. 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. 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. 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/ 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. I hope this helps, Ruth -- -- Software Manager & Engineer Tel: 01223 414180 Blog: [4]http://www.ivimey.org/blog LinkedIn: [5]http://uk.linkedin.com/in/ruthivimeycook/ References 1. http://greyarea-post:8870/ 2. http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 3. http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 4. http://www.ivimey.org/blog 5. http://uk.linkedin.com/in/ruthivimeycook/

5 years, 8 months

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

by gordon＠dickens.com

Thanks to David and everybody else that have replied to my problem. I have proceeded to uninstall the debian mailman3 packages and then endeavored to install everything with venv. I have implemented all of David's configuration suggestions which were very helpful. Now, mailman3 (core) appears to be working properly in that I can start/stop/restart/status the service. Also, the command "mailman info" from the venv prompt yields output which appears to be correct and the same as in the venv instructions. However, I have not been able to get mailman3-web working. All of my configuration files may be viewed here: https://dickens.com/etc-mailman3/ The above files are basically a mirror of the contents of my /etc/mailman3 directory except that I have obfuscated sensitive info such as keys, passwords and email addresses. Executing the mailman3-web service script with the command "systemctl start mailman3-web" starts everything without errors, however, the command "systemctl status mailman3-web" then generates the following output with errors: ● mailman3-web.service - GNU Mailman Web UI Loaded: loaded (/etc/mailman3/mailman3-web.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-01-25 17:10:30 EST; 6s ago Process: 1718478 ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini (code=exited, status=1/FAILURE) Main PID: 1718478 (code=exited, status=1/FAILURE) CPU: 12ms Jan 25 17:10:29 slc.mailhub4u.com systemd[1]: Started GNU Mailman Web UI. Jan 25 17:10:30 slc.mailhub4u.com uwsgi[1718478]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Jan 25 17:10:30 slc.mailhub4u.com systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE Jan 25 17:10:30 slc.mailhub4u.com systemd[1]: mailman3-web.service: Failed with result 'exit-code'. Also, /var/log/syslog and "journalctl | grep mailman3-web" contain these two lines of errors: Jan 25 14:00:46 slc systemd[1]: mailman3-web.service: Main process exited, code=exited, status=1/FAILURE Jan 25 14:00:46 slc systemd[1]: mailman3-web.service: Failed with result 'exit-code'. Also, other commands in the venv instructions do not work such as "mailman-web migrate" which produces volumes of error dialog starting with: Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/template/utils.py", line 66, in __getitem__ return self._engines[alias] KeyError: 'django' Then these two lines are then followed by over 50 lines of django and python error messages. I have not been able to find any hints or suggestions as to what I am doing wrong in my server's logs. FWIW, I have been working in the Unix/Linux command line environment for over 35 years and I have extensive LAMP, EXIM and Mailman2 experience. However, I have not ever worked with Django. I am usually able to resolve issues like this quickly, however, I am at a total loss as to what to do now with this mailman3 installation. I suspect that my unfamiliarity with Django may be my achilles heel. So, I am hoping that somebody here will soon be able to offer suggestions that might help me get everything working properly. I have several organization's mailings lists on this server and I need to get this fixed ASAP especially since my mailman installation has been down now for almost 3 weeks. As you might imagine, this is causing me alot of grief with my mailman3 users. So, please let me know any suggestions that you folks may have to get my mailman3 installation working again. Many Thanks, Gordon

4 years, 1 month

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

by Stephen J. Turnbull

Thanks for your patience with our team; I had already received your second "ping" and Mark's response, but due to the way my MUA presents my INBOX I didn't see it (aside to self: *don't* answer Mailman traffic from the inbox, use the "Mailman 3 virtual folder" view! :-). I would have written very differently if I had seen it.... Stephan Krinetzki writes: > Then we should maybe move to gunicorn, if this is the better way > (or at least better supported way) That's definitely a possibility. Among other things, gunicorn is a Python application, so all the Mailman devs have some hope of debugging it or at least localizing it. That's not true of uwsgi. The other possibility if you don't need high performance is to use the Apache mod_wsgi plugin which seems to be quite stable (that's what I do out of laziness -- I really should have uwsgi and gunicorn setups for testing -- my own throughput and admin needs are very modest). > After we enabled the "slow query log", we got in the postgresql > database the following output: > > 2022-01-25 12:49:41.538 CET [16126] LOG: unexpected EOF on > client connection with an open transaction Ouch. That is a database problem but I don't think it's a problem with the database. There are two database connections involved, one is Mailman core, the other is Django, but this > > > the message is delivered to the list immediately, says that core has finished at least some of its business. I guess it's possible that core drops the transaction on the floor, but that seems weird because I don't think this is a common problem. I'm not going to guess further, maybe Mark or Abhilash has something. ISTR other delay issues that have to do with very large databases. Do you have huge numbers of users, lists, or subscriptions to particular lists? Of course it could be Postorius/Django, but I think Postorius delegates all the logic and database work to core for this. Django's databases are user- and authentication-oriented, I don't recall any list-management logic in it that would induce this: > 2022-01-25 15:34:36.047 CET [16864] LOG: duration: 30760.028 > ms statement: DELETE FROM pendedkeyvalue WHERE > pendedkeyvalue.id = XXX Next log: > ERROR 2022-01-25 18:55:55,037 2599 django.request Service Unavailable: > /postorius/lists/games.lists.rwth-aachen.de/held_messages > ERROR 2022-01-25 18:58:24,325 2588 postorius Mailman REST API > not available Not sure about this. It could indicate a deadlock where each of core and the backend database is waiting for the other, so core isn't able to respond to Postorius. It looks to me like the rest of the traceback is a natural consequence of unavailability of the REST API. > * The venv is in /opt/mailman/mailman-venv > * The settings are in /opt/mailman/mailman-venv/mailman-suite/mailman-suite_project I don't see much to flag here. I don't recall whether allauth.socialaccount is supposed to be enabled or disabled if you have no allauth.socialaccount.providers enabled, but it's probably OK (and I don't see how it could be related to this problem): > contenten of settings.py > # Application definition > > INSTALLED_APPS = ( [...] > 'allauth', > 'allauth.account', > 'allauth.socialaccount', Database looks fine: > # Database > # https://docs.djangoproject.com/en/1.8/ref/settings/#databases > > DATABASES = { > #'default': { > # Example for PostgreSQL (recommanded for production): > 'default': { > 'ENGINE': 'django.db.backends.postgresql_psycopg2', > 'NAME': 'mailman', > 'USER': 'mailman', > 'PASSWORD': '<PASS>', > 'HOST': 'localhost', > } > } This shouldn't have anything to do with slow Postorius (full-text search is relevant only to archives, ie, HyperKitty), but Whoosh is known to be slower than Xapian: > # > # Full-text search engine > # > HAYSTACK_CONNECTIONS = { > 'default': { > 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > 'PATH': os.path.join(BASE_DIR, "fulltext_index"), > # You can also use the Xapian engine, it's faster and more accurate, > # but requires another library. > # http://django-haystack.readthedocs.io/en/v2.4.1/installing_search_engines.h… > # Example configuration for Xapian: > #'ENGINE': 'xapian_backend.XapianEngine' > }, > } > Nope, the virtual machine is dedicated to Mailman3. Mailman3 as > venv, uwsgi as Webservice, Apache as Webserver, Postfix as > Mailserver and PostgreSQL 10 als Database, all on the same host Oh, well, I guess the case against Mailman gets a little stronger.... > At moment i think its a slow database. Because of the slow > database, the Mailman API is slow and so on. We are trying now to > solve the database part with postgresqltuner - maybe we will see > more details then. OK, keep us posted. I will say that it looks from the logs discussed above that PostgreSQL is waiting for Mailman, not vice versa (but that doesn't rule out a deadlock where both are waiting for the other). I hope my message trims things down enough that it rings a bell for somebody. Steve

4 years, 1 month

[MM3-users] Re: I don't get my posts with Gmail

by Allan Hansen

I was pleased to see the advice below on how to get your own list messages sent from a Google client, as my subscribers complain about their messages going AWOL all the time. Alas, it has the following note at the bottom: "I have tested this and while it seems to work, it doesn't. What the filter does is put a copy of the sent message in your inbox as it is sent so it appears that you received the list post, but the message in your inbox is the same message that's in your sent folder. It's not the message received from the list.” Do those messages really show up in the spam folder without this filter? (I don’t use Gmail). If so, then the server is, indeed, sending the message to the mail client, and the mail client is doing the message ID linking locally, discarding the incoming duplicate. Would a change in mail client solve that? If so, then problem solved by a work-around. If not, then how can the filter above work? And pardon my top-posting. :-) Yours, Allan Hansen hansen(a)rc.org > On Oct 18, 2020, at 3:35 , Massimo Zappalà <maszap69(a)gmail.com> wrote: > > Thanks Stephen for your reply, > I tried creating the filter on GMail as described in Mark's suggested Wiki > > https://wiki.list.org/DOC/I%20don%27t%20get%20my%20own%20posts > > and it worked. > > Thank you > Max > _______________________________________________ > 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, 4 months

[MM3-users] Re: mailman break DKIM signature by modifying body

by Mark Sapiro

On 6/5/23 07:06, Peter Münster wrote: > Hi, > > I'm using mailman 3.3.8. > > Some messages with attachments from Google users get rejected by spam > filters because of invalid DKIM signatures. > > It seems, that mailman alters some lines in the body. Here an example: > > Original message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2031 > > --000000000000f846c505fc494b7a-- > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > Altered message: > > --8<---------------cut here---------------start------------->8--- > Lines: 2032 > > --000000000000f846c505fc494b7a-- > > --000000000000f846c705fc494b7c > Content-Type: application/pdf; > [...] > Content-Disposition: attachment; > [...] > --8<---------------cut here---------------end--------------->8--- > > An empty line is added, and the spaces after the semicolons are removed. > > Perhaps related to https://gitlab.com/mailman/mailman/-/issues/1079. > > What could I do please, to prevent such modifications of the body? Changes like those above are due to Python's stdlib email module. Short of actually modifying the email module, there's nothing you can do to prevent them. Instead, you should be DKIM signing your outgoing mail and perhaps applying Mailman's DMARC mitigations if DMARC is an issue. If you are DKIM signing your outgoing mail and mail is being rejected because of prior invalid signatures, you can remove those by adding `remove_dkim_headers: yes` to the [mta] section of mailman.cfg. Also, ARC signing <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…> may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

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

by Stephen J. Turnbull

Quanah Gibson-Mount writes: > But really, the documentation needs to be updated further to point > out the the Django ADMIN INTERFACE as the best way to do user > management, and not the python shell. The Django admin interface is something that most sites are not going to want to expose in addition to Postorius, and Postorius is needed for the users. If you have access to the host (another thing that most sites are not going to want to expose to list owners, who are most relevant to user management), you want to use the Mailman shell, not the Python shell (I assume Mailman shell is what you meant, but other readers may not). The bundled administrative interface *is* Postorius. The Mailman shell is basically a quick hack (sorry Abhilash; if you want to call it a masterwork and say the speed of development is testimony to your skills, I won't deny it ;-) to give more convenient access to internals to experienced Mailman hackers. More administrative features is something we plan to work on, but the Mailman project will focus on Postorius for the forseeable future. For alternatives to Postorius and the Mailman shell, Brian Carpenter (follow Allan's subthread) is working on a new management UI (using PHP), and I believe there's a working node.js API "out there somewhere". Please be very considerate of Brian's time; he and EMWD constitute a bulwark of the Mailman ecosystem and will be even busier with the UI project. But do pass on your suggestions to him as well as to us, he's indicated he's open to that. Steve

5 years, 11 months

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 3:48 PM, Mark Sapiro wrote: >> Is there a way that I can "dump" the configuration from an existing >> mailman3 server, and "import" it into a new instance? I'd really like >> to avoid re-doing all of the configuration, etc, as there are quite a >> few lists and everything is set up pretty much the way I want it. > > If you use the same database manager it should be no problem to get a > dump of the existing Mailman database to load into the new instance, or > if these are on the same server, just point the new instance to the > existing database. In either case, the database should be loaded and the > Django commands `migrate`, collectstatic`, `compress` and > `compilemessages` run[1] before starting Mailman services. Mailman core > will run any necessary updates to its database upon startup. > > You may also need to rebuild the HyperKitty search index with the > `update_index` Django command, but you may be able to use the existing > one if the search engine is the same. > > [1] See > https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=colle… > et seq. Understood. I am not at all fluent in django interactions (I'm still not entirely sure of what django actually *is*) so I have some reading to do. Any pointers on "django wrangling for n00bs" would be great. As I mentioned, I've not been hacking on mm3, just using it. I'm an accomplished programmer, but embedded C and assembler are a few galaxies away from python and web services! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 7 months

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

by marcus＠mbautze.de

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 [Errno 111] Connection refused May 16 01:48:15 2024 (61252) NNTP error for list vereinsmitglieder(a)ludothek.de: [Errno 111] Connection refused 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 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? Does anyone else have an idea what I need to change to get my mails out? 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.

1 year, 9 months

[MM3-users] Post-installation documentation?

by Stephen J. Turnbull

David Newman writes: > I am looking for a high-level "do these steps next to get a list > working" document rather than an API command reference. There's no such documentation. "Get a list working" depends on what you mean by "working". The basic answer is 1. Install Mailman 3 suite. 2. Log in to Postorius as an admin user and create the list. After that, it's case-specific. > - why do the venv docs and admin FAQ give different nginx configs for > the reverse proxy? Because the FAQ is providing a short snippet to solve a specific problem, the venv docs provide what I guess is somebody's full working config. Setting up a Mailman server is complex; usually any example you see in the docs is somebody's "works for me" configuration. > - Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides > /opt/mailman/mm/mailman-hyperkitty.cfg? It needs to match MAILMAN_ARCHIVER_KEY in HyperKitty's settings.py. There are a couple of reasonable ways to organize HyperKitty and Postorius configs, I'm not sure where the appropriate settings.py would be on your server. > - For Django (presumably in /etc/mailman3/settings.py, but the docs > don't say), what values to use with Postfix to set up the email back end? The answer is "that depends on your mail environment". As far as I know, normally it just works with the default settings, but if your Postfix requires secure, you need to set that up: https://docs.djangoproject.com/en/3.2/ref/settings/#std:setting-EMAIL_USE_T… and possibly the following 3 or 4 variables if authentication is needed. There was a thread on this a couple of weeks ago.

4 years, 3 months

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

by Bryan Kartzman

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

2 years, 3 months

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

by Alan So

Stephen J. Turnbull wrote: > Hi Alan, > It occurred to me that Django template widgets are very flexible. It > may be possible to customize the template to accomplish this task. In > that case, the customized template would be kept in a place that > doesn't get overwritten in an upgrade, reducing the maintenance cost > (unless either Postorius or Django changes the template in a way that > seems unlikely to me). I'll try to take a look at that over the > holiday break -- that has the advantage that I just document how we > did it for you, and tell any future requests to RTFM and DIY. ;-) Many thanks for your effort especially during the long holiday. Really appreciate. > I agree, you need to be disciplined about what changes you are willing > to develop and maintain. This one seemed to me to be over that bar, > especially since you can put it in and not suffer too greatly if it > gets reverted in a upgrade and the maintainers don't notice. We do not always have full control of what we are willing to do. It is kind of a Pandora's box. Opening it up may lead to other requests which may no longer be patches but changes potentially conflicting with future upgrade. It is ok if people here recognize that we should have our own developers to participate in this kind of changes and also the maintenance but it is not the culture here. Particularly developers here are much more experienced in Win, C#, .NET than Linux, Python.

3 years, 2 months

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Elias Rudberg

After some more digging into this I found a way to reproduce it using a much simpler URL, like the following (but with the real name instead of example.org) https://example.org/mailman3/postorius/lists/?items=x The error comes when Django is trying to process the template django-mailman3/django_mailman3/templates/django_mailman3/paginator/pagination.html which contains two for-loops of the following kind: {% for key, value in request.GET.items %} [... doing something with key and value here ...] {% endfor %} It seems like Django then gets confused by the different "items" variables involved, I think the value from the "?items=x" part of the request URL gets used instead of the "request.GET.items" (both are called "items" but they contain different things. I don't know if the for-loops in that template could be done differently to avoid this. There is something similar at https://github.com/django/django/blob/main/django/views/templates/technical… where the corresponding for-loop looks like this instead: {% for k, v in request_GET_items %} [...] {% endfor %} So there they write "request_GET_items" instead of "request.GET.items" for some reason. I don't know if doing it like that is possible in case of the mailman template, just mentioning it because it looks like it could be another way to achieve the same thing. I wrote a question about this in the Django forum also, here: https://forum.djangoproject.com/t/getting-error-need-2-values-to-unpack-in-… Hoping for an answer there to help figure out if this should be seen as a bug in Django or not. / Elias

1 year, 7 months

[MM3-users] Re: virtual_alias_domains

by Johannes Rohr

Please ignore my previous message! I understand, alias domains can be added through the web interface. (took me quite a while of searching...) Johannes Am 06.01.23 um 08:37 schrieb Johannes Rohr: > Dear all, > > I have to set up mailman3 in an environment where postfix uses virtual > alias domains. This is described in > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > I don't understand, though, what I need to do to have mailman generate > > $PREFIX/var/data/postfix_vmap > > > > I have tried to follow the instructions at > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > with the purpose of setting an alias domain. However, things go > sideways quickly: > >>>> from mailman.interfaces.domain import IDomainManager >>>> from zope.component import getUtility >>>> manager = getUtility(IDomainManager) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File > "/opt/mailman/venv/lib/python3.8/site-packages/zope/component/_api.py", > line 165, in getUtility > raise ComponentLookupError(interface, name) > zope.interface.interfaces.ComponentLookupError: (<InterfaceClass > mailman.interfaces.domain.IDomainManager>, '') >>>> > > > So, something is missing. But, being a complete python layman, I do > not know what and how I fix it. > > Can someone give me a headsup? That would be greatly appreciated! > > 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

3 years, 2 months

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

by David Partain

> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: > > 1. Am I correct in assuming that I can just use my favorite editor > > (vi) to remove the offending characters from the file? > No. The file is a Python pickle and you can't edit it. You would need > to get the message and the metadata from the pickle (you could at least > view it with the `mailman qfile` command), edit the message and then > re-pickle the message and metadata. And, in my impatience, I tried it before receiving your response and now I seem to have done silliness in my database :( New error in mailman-web.log: AttributeError: 'NoneType' object has no attribute 'subject' Sigh. Stupid me. If you have suggestions on fixing that... Right now, my plan is simply to remove the first message in the queue (since I assume it'll be the "broken" one) and it'll just not be in the archive. Life's hard. Even if I unpack 'em to edit, I'll find mail in, for example, in base64, and I'm not going to fix the mail by decoding, editing, re-encoding, ... Nope. > > 3. Can I do something to make hyperkitty go through the spool? > > > > I don't know what you mean. Sorry I wasn't clear. I simply meant, "Is there a way to start hyperkitty going through the spool manually?" It sounds like, though, that I don't need to do that if it's going to happen that often anyway. Cheers, David

5 years

[MM3-users] Re: Moderating posts via email

by Abhilash Raj

On Thu, Oct 26, 2017, at 02:52 PM, Dmitry Makovey wrote: > On 10/26/2017 02:46 PM, Abhilash Raj wrote: > > On Thu, Oct 26, 2017, at 02:21 PM, Dmitry Makovey wrote: > >> Hi, > >> > >> we are trying to figure out what is that we're doing wrong as we can't > >> use instructions that mailman sends with information on held messages as > >> referenced in: > >> https://gitlab.com/mailman/mailman/blob/master/src/mailman/chains/hold.py#L… > >> > >> In particular - replying to the message with "Approved: listpassword" we > >> were not able to approve any message. > > > > Did you add it to the body/subject of the email? > > We have added "Approved: listpassword" to the body of the message as a > first line as advised. > > > > AFAIK, Mailman looks for "Approed" header to approve the held messages. > > We did not try to inject "Approved: listpassword" header into the > message body itself though. And if that is the way it is supposed to > function I'm questioning whether average user would be able to operate > it. I am sorry, it does indeed say that you can add it to the first line of the body. I haven't tried doing it so I am not sure if it works, maybe someone else can comment on it. Given how emails are not so good at being secret, I'd not advise using it despite it's current state. Although, if it is a feature, it should work regardless! -- Abhilash Raj maxking(a)asynchronous.in

8 years, 4 months

[MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples.

by David Partain

Thanks! I can also be happy knowing that the next person who Googles the same error will find an answer, even if my silliness will also live on. I can take that 🙂 David ________________________________ From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Thursday, March 21, 2024 17:04 To: David Partain <david.partain(a)ericsson.com> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples. David Partain via Mailman-users writes: > And do I feel silly. Please don't. You made a good report with all the information needed to point out a fix, even if it was obvious *in hindsight*. Of course we appreciate the effort of those who figure it out for themselves and save us a bug report, but a good report and a quick fix for it has a lot of educational value, too. Steve ________________________________ From: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Sent: Thursday, March 21, 2024 17:04 To: David Partain <david.partain(a)ericsson.com> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: ValueError: The ADMINS setting must be a list of 2-tuples. David Partain via Mailman-users writes: > And do I feel silly. Please don't. You made a good report with all the information needed to point out a fix, even if it was obvious *in hindsight*. Of course we appreciate the effort of those who figure it out for themselves and save us a bug report, but a good report and a quick fix for it has a lot of educational value, too. Steve

1 year, 11 months

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

by David Newman

On 12/10/21 12:57 PM, Mark Sapiro wrote: > On 12/10/21 10:22 AM, David Newman wrote: >> >> 1. At least on my system, the proxy_pass statement will only run >> without errors if I change this to a fully formed URL, e.g., >> 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs? > > > I changed it at > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > but I wonder if we shouldn't be using `uwsgi_pass` instead of proxy_pass. > > See https://nginx.org/en/docs/http/ngx_http_uwsgi_module.html#uwsgi_pass > > 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. >> 2. What document root(s) and alias(es) to use for Postorius and >> Hyperkitty and the Django admin on a server that also runs other >> services (e.g., Postfix for non-list mail and Roundcubemail)? > > > If you can separate Mailman from other services by subdomain Alas, I can do that for all but one of the subdomains I have in production. For the past 15 or so years, users of that subdomain have used mail.domain.tld for MM2, roundcubemail, and an admin web UI that manages regular mail. The "/" has gone to roundcubemail, and users to go other directories for the other services. For example, MM2 users currently go to /mailman. , you can > configure them separately and for Mailman, root is irrelevant as > everything is proxied or aliased in a location directive. For example, > Mailman on the server that supports this list uses the > lists.mailman3.org domain and we have (excerpted) > ``` > server { > listen 443 default_server; > root /usr/share/nginx/html; > index index.html index.htm; > # root and index are probably irrelevant as we never go there > server_name lists.mailman3.org; > ssl on; > #ssl stuff > location / { > proxy_pass http://127.0.0.1:8000/; > # other proxy stuff In this example, / goes to MM3. The assumption here and in the MM3 docs is that we're standing up a dedicated server where MM3 pages should be served as the default. That's a totally valid design decision, and one could argue it's superior to running a bunch of other services on one machine. 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. You're right that the root and index directives above are irrelevant since / goes to MM3 via proxy. What I'm asking is what root(s) and location(s) to use with nginx where MM3 isn't the default. Thanks again! dn > } > location /static/ { > alias /var/spool/mailman-web/static/; > } > location /robots.txt { > alias /usr/share/nginx/html/robots.txt; > } > location /favicon.ico { > alias /var/www/listorg/images/favicon.ico; > } > } > ``` > And for the other stuff we have > ``` > server { > listen 443; > server_name .list.org mirror.list.org mirror.mailman3.org; > root /var/www/listorg; > ssl on; > # ssl stuff > } > >

4 years, 2 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 11:19 AM, Mark Sapiro wrote: > Here's a thought. For Affinity/Empathy at least, how about using Mailman > core's user as the Affinity registered user. I.e., if someone's first > interaction is to register with Affinity, have that registration create > a core user to keep the Affinity registration data. This core user > already accommodates a display_name and password and email address(es). > > If the person already is a core user when registering for Affinity, just > update the core user as needed, probably only a password reset or just > setting it if it is currently None. > > Then you don't have the issue of another, separate registration for > Affinity. > > This would be more difficult for Postorius/Hyperkitty because those > users are Django users, but that isn't an issue for Affinity. > > -- 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/ How would a person already be a core user outside of a registration with Affinity? Via a list subscription or the import21 script? I do agree overall that we can more easily address some/all of these issues more easily and quicker due to not being tied to Django. I hope to get all of this address in our Nov development cycle. I do want to apologize for my tone Mark. I was wrong in the way I communicated. > -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

[MM3-users] Creating and placing custom templates

by kelly.close＠lrewater.com

I know there are previous threads related to this topic but none were very recent so I thought I'd start a new one. I've referenced two of the old ones below. I am attempting to implement a custom footer on one of my lists. This seems like it should be straightforward but I'm clearly doing something wrong, since the default footer keeps coming through despite my efforts. I've referenced the docs as well as these two posts, to no avail. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Here's what I'm doing: I found my templates folder and verified it matched what is set in the mailman.cfg file - on my Ubuntu Bionic system it is /var/lib/mailman3/templates/ In that folder I created the following folders and made sure they were properly owned (by list:list) /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/ Into that en/ folder I placed a file called "list:member:regular:footer" It is a text file with just one line of text in it (a link to a website). Also, because there was a mention in one of the earlier posts that this file should have a .txt extension, I also put the same file in there named "list:member:regular:footer.txt". I have two of my own emails subscribed t my "f2p2-test" list at the domain udfcd-lists.org. When I post to the list, and check my other email for the disseminated post, it still has the default footer. I have restarted the mailman3 service. Can anyone spot an obvious error here or offer troubleshooting suggestions? Thank You! ~Kelly

6 years, 10 months

[MM3-users] Problems configuring hyperkitty

by Alain D D Williams

I am having another go at installing mailman3 - I seem to have mailman3 & postorius working - although basic testing, much more needed to confirm that I understand it. I want to get hyperkitty working before I start full testing. 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 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 config file is: /etc/mailman3/mailman-hyperkitty.cfg This does not contain any comment about databases. Where does hyperkitty get its database parameters from ? • 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 ? 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 ...] Is there some better documentation that I have failed to find ? Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 3 months

[MM3-users] Re: compatibility of mailman 3.3.10 with mariadb 11.4 LTS

by Stephen J. Turnbull

Michael, if you're going to "correct" people in public, you really should try for a higher degree of accuracy. Michael Bayer writes: > support for different databases is the responsibility of GNU > Mailman, Not so. First, "responsibility" is something we explicitly disclaim ("no warrantee", "as is", etc). Second, if code that works perfectly well with other MySQL-family databases fails with a specific product and version, we would be well within accepted practice to say "tough luck, use a compatible version". And third, SQLAlchemy advertises that it provides a common API independent of vendor and version of the backend database ... that's *why* we use it. Not to "avoid responsibility", but because the product does it very well. But it does mean we have almost no information about version quirks, and only very rarely do we see vendor-specific issues. > SQLAlchemy is a database access library that does not guarantee an > application works with a particular database as it supports > vendor-specific behaviors and constructs. Sure, but we don't ask it to do anything vendor-specific, We use only APIs common to all RDBMSes we claim to support. To the extent that SQLAlchemy opts to use vendor-specific features to support those APIs, we don't know about it. > please dont mislead users into thinking the SQLAlchemy project is > providing support for GNU Mailman, I didn't. I said it *should* work, and if that's not good enough for the OP, I told them where to find people who would have data on their specific question. > thanks You're welcome. Steve

11 months

[MM3-users] Re: Join a Mailman 3 list?

by Cathryn McGuire

Hi Mark, Stephen & Thomas, We've successfully merged our Mailman 2 list into Mailman 3. EMWD worked over the weekend to get it done for our members. We're pretty grateful. There are a few things we're trying to get our heads around, specifically to do with the Affinity Web UI. Most of it is pretty self explanatory, and I can see where it will be more aesthetically pleasing to manage, but a few things that aren't so intuitive. Is anyone working with Mailman 3 and Affinity that could help us through the set up? For instance, when I log in as owner and go to change my password, it won't take a new one and asks me (with a pull down menu box) which account I want to change the password for, and it gives me a list of my emails, and also the other owner's email address. When I choose the email I'm logged in under, it says it's not the correct "credentials." Has anyone had this issue? Another thing is, and Stephen J. Turnbull prepared us for this, that the transferred membership are all "enabled" but not "registered." I understand we have to send a membership wide notification with a link to the Affinity log in page, and instructions going to the top right hand and clicking on the login icon, putting in their email address (the one in the system) and adding a password OR do they have to "create" a new sign in? Thanks for any info you can give us about Affinity. (I see Brian Carpenter was beta testing it 4 years ago.) Cheers, Cathryn

8 months, 3 weeks

[MM3-users] Re: Mailman and Postfix Conflicting Information

by Mark Sapiro

On 2/6/26 09:00, dap1--- via Mailman-users wrote: > I've been going in circles between mailman and postfix trying to get things working. My current condition is that either mailman is putting incoming mail in the bit bucket or postfix is not sending incoming mail to mailman. What does your mail.log say? There should be an entry like ... postfix/lmtp ... to=<lllllllllll(a)gmail.com>, relay=127.0.0.1[127.0.0.1]:8024 ... for mail to the list. > According to the postfix forum my mailman configuration is messed up but it was auto generated by the installer. Supposedly these entries should not be in /opt/mailman/mm/var/data/postfix_lmtp or rather transport_maps and/or local_recipient_maps. > > # Aliases which are visible only in the @gmail.com domain. > lllllllllll(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-bounces(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-confirm(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-join(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-leave(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-owner(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-request(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-subscribe(a)gmail.com lmtp:[127.0.0.1]:8024 > lllllllllll-unsubscribe(a)gmail.com lmtp:[127.0.0.1]:8024 > > And relay_domains shouldn't have this entry either in /opt/mailman/mm/var/data/postfix_domains in relay_domains: > > gmail.com gmail.com > > Clearly my postfix configuration is messed up but since this was all auto generated I don't know what to do. I think the Postfix people are confused by the fact that your list domain is gmail.com and expect gmail.com mail to be delivered to Google, not Mailman. What you post above seems OK to me for what you are trying to do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

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

by Nelson Strother

Neither .../logs/mailman.log nor /var/log/syslog contain any recording of "Master detected ..." nor process exits other than at the time of `mailman stop` commands. Watching during these transitions with `vmstat` shows a decrease in free pages and an increase in swapping, but no definitive hint of the OOM reaper running. I did not intend to imply that `mailman start` (predictably) consumes more time than `mailman restart`. Both are lengthy and variable; I think one cause for `mailman stop` consuming more time than usual is when mailman receives a message as it is trying to stop, which is understandable. Interestingly if I use `systemctl start mailman` thus far the results are: - the wall clock duration is shorter than when `mailman start` is issued from the command line, and -- either that all of the runners remain present once they are started, -- or I can see in syslog a traceback from each missing runner process starting from .../mailman/.local/bin/runner and ending with "flufl.lock._lockfile.NotLockedError: Already unlocked". I do not yet understand how to make use of these clues, but at least one can see an epitaph from each deceased process. On 6/6/23 14:47, Mark Sapiro wrote: > 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. >

2 years, 8 months

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

by Brian Carpenter

On 2/13/21 10:53 AM, Jim Popovitch via Mailman-users wrote: > But how do you display a "Membership List page" for admins in MM3 > (choice of wording is specific to other emails you've posted today) > without third-party application(s), and isn't that too a shortcoming in > MM3 due to that functionality being present in MM2? Look, without a > doubt the REST API of MM3 Core is cool, but let's be honest, all the 3rd > party wrapping and baggage is, well, not so cool. But, again being > honest, you can't have a MM3 system without all of those things. With > MM2 we have all those things, and we are happy with them.:) Affinity is just a UI that sits on top of Mailman 3 core. Most of its functions and displays come from Mailman 3 core. Everything I mentioned about how Affinity displays List Member Management to List Owners uses MM3's REST api to do so. In my opinion, Postorius is nowhere near in taking advantage of all that Mailman 3 core offers along with free tools such as Bootstrap 4. The only thing that is holding Postorius back is time to improve it and that is not the fault of MM3 or the developers. The thing to take away from this however is Postorius still has the potential (because the foundation is there) to be a great modern UI for Mailman 3 core. MM2 does not have that potential and never will. Sure it works until it doesn't. I am pretty sure Pipermail is a wrapper and not an inherit part of MM2. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

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

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

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

by Stephen J. Turnbull

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

2 years, 4 months

[MM3-users] Re: Moderating posts via email

by Barry Warsaw

On Oct 26, 2017, at 17:21, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > > we are trying to figure out what is that we're doing wrong as we can't > use instructions that mailman sends with information on held messages as > referenced in: > https://gitlab.com/mailman/mailman/blob/master/src/mailman/chains/hold.py#L… > > In particular - replying to the message with "Approved: listpassword" we > were not able to approve any message. I’m pretty sure you’re not doing anything wrong, it just doesn’t work. There are two use cases for Approved: header. The first is that the list admin can send a pre-approved message to the mailing list, which bypasses all rule checks except for dmarc-mitigation and no-senders. At least, that’s what happens with the default, built-in chain. But that’s not what you’re talking about here. The second use case is where you reply to the subpart with the ‘confirm <token>’ Subject. This should go to the -confirm@ or -requests@ subaddress (both of which are processed by the command runner). As that bit of text says, the held message should be discarded if there’s no matching Approved: header (in the first non-blank line of the message body, or in a header). The held message will be accepted if it has a matching Approved: header. The problem is that the current implementation of the ‘confirm’ command doesn’t distinguish the operation based on the “pend key” of the record matching the token. Meaning, those tokens are used to represent held messages *and* held subscriptions, and the ‘confirm’ command only routes its message to the subscription handler. So I’d say this is a bug in the ‘confirm’ command handler. -Barry

8 years, 4 months

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

by Abhilash Raj

On Sat, Oct 5, 2019, at 7:27 AM, Stephen J. Turnbull wrote: > Jonas Meurer writes: > > > > This is the issue. I don't know how the Debian packages do this, but I > > > recommend having a 'mailman' user that owns everything and running > > > commands as that user. > > > > The Debian package uses user `list` for this. It also provides a command > > `mailman-wrapper` which takes care of running mailman commands as this user. Is this wrapper a sort of alias to `sudo -u list mailman` or something more than that? > > > > It would be awesome if the upstream /usr/bin/mailman command could take > > care of this automatically, making the wrapper command obsolete. > > What precisely is "this"? We already have the mailman command; are > you suggesting it should be suid/sgid mailman/list/whatever? That's > pretty obviously a vulnerability. If there are any RCEs *anywhere* on > your host, your Mailman is pwned. If you know your installation is > secure enough or you just don't care, fine, chmod it yourself. > > If not, how do you propose upstream "take care of it?" > > Steve > > > -- > Associate Professor Division of Policy and Planning Science > http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information > Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba > Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN > _______________________________________________ > 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, 5 months

[MM3-users] Re: Things I miss about mailman2

by Quanah Gibson-Mount

--On Wednesday, March 18, 2020 2:58 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This was implemented by > <https://gitlab.com/mailman/postorius/-/merge_requests/397> and released > in Postorius 1.3.0. Ok, that would be the issue... Debian 10 only has 1.2.4-1 bundled. I'll see if I can find a backport for 1.3. >>> This was not "removed". It just hasn't been implemented in MM 3 yet. >> >> So in terms of available functionality that was present in MM2, it was >> removed. It may need to be re-implemented, but this was a core feature >> that was present in the prior version that is no longer available. > > > Yes, we are aware of many things that are not yet exposed/implemented in > Postorius and elsewhere. There are currently 580 open issues at > <https://gitlab.com/groups/mailman/-/issues>. We are working on these > things as we can. We would love to have your help in fixing these. In > the mean time, there are really only 2 or 3 core developers working on > this and we are all volunteers, so it takes time. I fully understand and would love to contribute. The problem being that I already am doing this for multiple other projects where we're facing the same issue -- Lots of people use the software and there are the occasional contributions, but few people who are willing to be core members to really help drive the projects, and I can only drive so many and do my paying job. :/ Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 11 months

[MM3-users] Re: Database running VERY hot

by Abhilash Raj

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, 11 months

[MM3-users] Re: Memory footprint

by Stephen J. Turnbull

After I wrote this, I see that the OP has a usecase where they've got a shrunk to fit AWS instance. So this is more useful than I thought, but I still don't think that's a huge audience. (The OP himself just upgraded the instance, after all.) Barry Warsaw writes: > I can imagine different ways of doing it. For example, systemd > socket activation on OSes that support that for the REST and LMTP > servers. And maybe use inotify in the master watcher to spawn > queue processing runners on demand. These would all be interesting > things to explore, although they may not be universally appropriate > (i.e. not all *nix systems supported by Mailman run systemd, nor > support inotify). Not to mention that spawning is typically a heavyweight action, so if you're heavily loaded enough to care about load, you'd need to add complex logic like that used by Apache to ensure you have same processes/threads hanging around to answer frequent calls, rather than one-shot "CGI" style. We do have thread and process pools in Python, but they wouldn't necessarily be compatible with this use case combined with systemd or inotify without additional logic in Mailman. If somebody wants to mess with this specifically, it could be useful. But I think it's kind of a long shot given the kinds of scenarios Mailman is typically used in (lightweight Mom & Pop shops, virtual servers with Mailman-as-a-Service, and hard-core 5,000-list 100,000 message per day university settings be the not unusual extremes). Sort of like gilectomy efforts in Python itself (maybe //arry would like to work on this? ;-) ;-) nudge nudge say-no-more, eh?) Regards,

8 years, 10 months

[MM3-users] Re: Django logins for new subscribers

by Alex McLean

On 12 January 2018 at 19:19, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Yes, that is the expected behavior. Postorius is just one of the front-end for Mailman (and only one, for now), so we didn't think it would make sense to create account for every Mailman User in Postorius as well. Ok thanks. From my perspective this is confusing behaviour though, especially for people new to the concept of mailing lists. There are three things to understand in the suite - mailman, postorius and hyperkitty. It seems that hyperkitty is trying hard to be a web forum and actually does a really good job (one reason why we're switching), but postorious links to it as an archive rather than a full interface to the discussion. The default welcome email didn't contain any web links to postorius or hyperkitty. I realise I can change such texts and will spend some time on this. I'd be interested to hear advice from others who have done this sort of thing. > So, basically everyone has to go through the sign-up process, which isn't really hard if you choose one of the social logins. Yes true. > It wouldn't be very hard to write a script that "creates" User accounts for everyone and then users go through the "Forgot Password" workflow to set their passwords. You'd get the list of all users from Mailman's API and then do a `get_or_create()` on each one of them (simplest of all approaches, you can ofcourse better ways to do the same). Ok, I'll look into this. Thanks for the https nudge also by the way, it is on my todo! cheers alex

8 years, 1 month

[MM3-users] Re: Moving mm2 mail archives to mm3

by Abhilash Raj

On Tue, Aug 29, 2017, at 05:43 AM, Henrik Rasmussen wrote: > > See 'django-admin hyperkitty_import --help' for more info. This command is incomplete, you need to specify --settings path-to-settings.py or have DJANGO_SETTINGS_MODULE environment var setup. (I think settings.py in the previous command should be on PythonPATH). Alternatively, you can use `python manage.py hyperkitty_import --help`. > Is this also valid using Docker-mailman? I don't have a hyperkitty_import > django command. How do I import MM2 archives in Docker-MM3? > > # docker exec -it mailman-web bash Here you can do: bash-4.3# python manage.py hyperkitty_import --help You'd also need to put the archives somewhere it can be seen from insider the container. The best place I guess would be `/opt/mailman/web/` which is mounted at `/opt/mailman-web-data` from inside the mailman-web container. > bash-4.3# django-admin help > > Type 'django-admin help <subcommand>' for help on a specific subcommand. > > Available subcommands: > > [django] > check > compilemessages > createcachetable > dbshell > diffsettings > dumpdata > flush > inspectdb > loaddata > makemessages > makemigrations > migrate > runserver > sendtestemail > shell > showmigrations > sqlflush > sqlmigrate > sqlsequencereset > squashmigrations > startapp > startproject > test > testserver > Note that only Django core commands are listed as settings are not > properly configured (error: Requested setting INSTALLED_APPS, but > settings are not configured. You must either define the environment > variable DJANGO_SETTINGS_MODULE or call settings.configure() before > accessing settings.). > > -- > Henrik Rasmussen > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 6 months

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

by Mark Sapiro

On 1/9/22 3:26 AM, Michael Heseltine wrote: >> This isn't your immediate problem, but it is an issue. The above isn't >> too informative. What do you get if you run >> >> /opt/mailman/mm/bin/django-admin qcluster >> >> manually? > > I get the following: > >> # /opt/mailman/mm/bin/django-admin qcluster >> 11:50:41 [Q] INFO Q Cluster autumn-sixteen-tango-march starting. >> 11:50:41 [Q] INFO Process-1:1 ready for work at 3725610 >> 11:50:41 [Q] INFO Process-1:2 ready for work at 3725611 >> 11:50:42 [Q] INFO Process-1:3 ready for work at 3725612 >> 11:50:42 [Q] INFO Process-1:4 ready for work at 3725613 >> 11:50:42 [Q] INFO Process-1:5 monitoring at 3725614 >> 11:50:42 [Q] INFO Process-1 guarding cluster autumn-sixteen-tango-march >> 11:50:42 [Q] INFO Process-1:6 pushing tasks at 3725615 >> 11:50:42 [Q] INFO Q Cluster autumn-sixteen-tango-march running. > > And then nothing until I end the command with Ctrl-C. This is what I would expect. It seems to be working. I'm not sure why it fails when run from systemd. Are you running memcached? systemctl status memcached.service That needs to be installed and running for qcluster. > Sorry, I didn't realize that they were truncated. Here are ( I hope) the full logs from /var/log/syslog: > >> Jan 8 21:24:57 lists systemd[1]: Started GNU Mailman web interfaces. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! WARNING: configuration file should have a valid Python extension. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 209, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.sleep() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 357, in sleep >> Jan 8 21:24:57 lists gunicorn[3707354]: ready = select.select([self.PIPE[0]], [], [], 1.0) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:57 lists gunicorn[3707354]: During handling of the above exception, another exception occurred: >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/bin/gunicorn", line 14, in <module> >> Jan 8 21:24:57 lists gunicorn[3707354]: sys.exit(gunicorn.app.wsgiapp.run()) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/wsgiapp.py", line 67, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 231, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: super().run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 72, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: Arbiter(self).run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 229, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.halt(reason=inst.reason, exit_status=inst.exit_status) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 342, in halt >> Jan 8 21:24:57 lists gunicorn[3707354]: self.stop() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 393, in stop >> Jan 8 21:24:57 lists gunicorn[3707354]: time.sleep(0.1) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Main process exited, code=exited, status=1/FAILURE >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Failed with result 'exit-code'. I'm not sure about this one either. You might want to look at https://stackoverflow.com/questions/24488891/gunicorn-errors-haltserver-hal… or other hits from https://www.google.com/search?q=gunicorn+worker+failed+to+boot Are your files /etc/systemd/system/gunicorn.service /opt/mailman/mm/bin/gunicorn opt/mailman/mm/gunicorn.conf the same as recommended at https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Mailman 3 localization

by Stephen J. Turnbull

Simon Hanna writes: > > We would like to contribute further german translations, since there > > are still some parts missing, e.g. in the postorious interface. Would > > https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate > > be the right place to do so, so that everybody could use our > > translations? I don't think that is the right place to do it, because I'm sure Ubuntu lags our releases by quite a bit. Obviously on Launchpad you should translate for their releases. > I wanted to set it up, but the requirement is to use a free hosted > solution. If by "free" you mean we can't afford to pay for a service, that's probably not true. If by "free" you mean the services you mention operate on non-free software, yes, RMS would indeed give us bat-guano about that, but it's not a 100% requirement. We did use Jira for some services for several years. So the main issue would be how long Abhilash is willing to put up with rms-guano. > I tried out zanata.org but it's extremely slow... > The other option at the time was pootle > (http://pootle.translatehouse.org) which doesn't offer hosting but some > folks at gnu had a customized instance set up, but they discontinued the > service. > I [...] found weblate.org. We (fvo "we" not limited to Simon) should keep an eye on these. However, I don't think translations are a high priority for the developers in general yet. But with Abhilash saying a release of 3.2 in the near future, we should strongly consider making it a priority for 3.3. (IMO YMMV TINLA ;-) Steve

7 years, 8 months

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

by Mark Sapiro

On 8/13/20 7:45 PM, Stephen J. Turnbull wrote: > > That said, I have some ideas for how to make this safe for corporate > Germany, specifically, keep a database of user-specific OTKs. (These > could be time-limited -- with the server returning a "use a more > recent message's URL message -- or permanent.) For the usera/userb > reasons Mark gives, and the preview-url reason you give, this is > *still* not going to be safe for discussion lists. But if the From: > is <noreply(a)DeutscheKompany.co.de>, so you have to shoulder surf and > have a photographic memory to get the user's unsubscribe URL, it > should be reasonably secure for announce lists and newsletters. I have experience with a one way email newsletter from Constant Contact. These have a link to unsubscribe and also a link to forward the email to someone else. We ultimately added our own ``` If you want to forward this email, please press the Constant Contact "Forward this email" link below. If you use your "forward" button, you might be unsubscribed. ``` note just above those links because people were forwarding the mail and getting unsubscribed when the person they forwarded it to clicked the unsubscribe link. The real pain is once a user is unsubscribed in this way, the mailing manager can't add her back. She has to personally deal with Constant Contact do get them to remove her from their "do not mail this address" list. FWIW, our note seems to help reduce if not eliminate the problem. -- 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] Problems with mailman core translation and other details

by celi＠dieese.org.br

Hi. We did a fresh install of the Debian Mailman 3 full package. I'd like all components to be translated into pt_BR. I downloaded the latest updated translations from weblate, which says that 100% of the project (all components) are translated. I checked and recompiled mailman.po with msgfmt without errors. I followed all instructions I saw, included the ones from the topic How to change the language in mailman3 in this list. Everything almost OK, except from the fact that none of mailman's core email messages are being translated, even though mailman.po shows the right messages. Also, strange things happen to these .po files. The web interface is almost perfect, but some messages (just some) are not correct - although the corresponding django.po appears to be OK. It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. #: templates/postorius/lists/summary.html:88 #, python-format msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the " "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" " " msgstr "" "\n" " Para se inscrever você pode enviar um e-mail com o assunto " "'subscribe' para\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " ou use o formulário abaixo:\n" What am I doing wrong? Or what can I do to make things suitable? Additional info: GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Postorius v. 1.3.4 HyperKitty v. 1.3.4 Thanx for any help

2 years, 1 month

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

by John Seifarth

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

7 years, 7 months

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

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 2:05): > On 4/6/25 16:00, MegaBrutal via Mailman-users wrote: > > I get a composition dialog and can type my message, but when I click > send, > > I get the error message: „This list is moderated, please subscribe to it > > before posting.”. Upon reply, a red rectangle appears to enclose this > > message. Upon trying to create a new thread, a white page loads which > only > > contains this error message. > > In that composition dialog below the text box, it should say > ``` > This message will be sent as: user(a)example.com Link another address > If you aren't a current list member, sending this message will subscribe > you. > ``` > > No, it doesn't say anything like that. It says if I'm not subscribed, sending the message would subscribe me – no address is shown there at all. > > What do you see in Django's logs when you do this? > >> > > > > I don't know where to look – I don't see anything outstanding, only a few > > HTTP requests appear in mailman.log on mailman side and uwsgi.log on web > > side. None of these indicate any error. > > > If you configured your settings.py per > > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > your Django log which is where HyperKitty logs is at > /opt/mailman/web/logs/mailmanweb.log. However, I don't think there will > be anything useful there. Yeah, I checked that, nothing useful.

11 months

[MM3-users] Correct way to filter auto-replies to list?

by Stephen J. Turnbull

Gary Holman writes: > I have seen a few messages on this list regarding handling 'out of > office' auto-replies. However I do not see a final resolution. This problem is as hard as spam. There won't be a final resolution as long as people use out-of-office auto-replies. They're all different. If you are using a spam filter, I would suggest adding the offender's out of office message (or at least the spike protein :-) to your filter's body text blacklist. > What is the best practice to filter auto-replies to list: header > filter or postfix milter-reject or something else? You write "auto-replies" below. Set the subscriber to no-mail, or unsubscribe them for a second offense. Remind them that we put a huge amount of effort into creating and maintaining Postorius to make that as convenient as possible, and we at Mailman are "shock, SHOCKED, I tell you" that this courtesy was neglected. :-) > We are running dockerized Mailman 3 version 1.3.4. A list user > auto-replied their vacation message to list and then the listserv "listserv" is a trademark. Please don't use it to refer to Mailman. > created a chain-reaction of continuously replying to auto-replies > by that user. What do you mean by "chain reaction"? Other subscribers replying to the "out of office" message, or an auto-reply from the Mailman server? > There isn't really a good header option to filter > from, as the subject seems to be randomized. Vacation programs conforming to https://tools.ietf.org/html/rfc3834 https://tools.ietf.org/html/rfc5230 should provide some header fields to filter on. HTH, Steve

4 years, 10 months

[MM3-users] Re: Migrating Mailman 3 lists

by Abhilash Raj

On Mon, Apr 27, 2020, at 8:52 AM, Brian Carpenter wrote: > Hello Mailman users, > > I know how to migrate mailman 2 lists to a new mailman 3 server. However > I do not know how to migrate a mailman 3 list from one mailman 3 server > to another one. Are there any instructions or protocol on how to > accomplish this? The Mailman 3 server I want to migrate *from* was setup > using Docker. The Mailman 3 server I want to migrate these lists *to* > was setup using a python virtual environment via pip. If you can backup and migrate the database, that should do all of the Web stuff (except search index & logs) and most of the Core data. You'd need to additionally move the `var/` directory if you want to digests/logs/pending emails. If you don't need any of the digests/logs/pending emails in various queue, you should be able to migrate just by moving the database. There was an issue[1] that was created recently where the digests would fail if the directory structure in the `var/` directory wasn't re-created automatically, so you might have to preserve that data structure. [1]: https://gitlab.com/mailman/mailman/-/issues/699 > > -- > 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/ > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 10 months

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

by John Covici

On Sat, 13 Mar 2021 22:51:46 -0500, Mark Sapiro wrote: > > On 3/13/21 7:08 PM, John Covici wrote: > > On Sat, 13 Mar 2021 16:22:59 -0500, > > Abhilash Raj wrote: > >> > >> My guess is that you updated the database (perhaps, by invoking the mailman > >> command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes > >> up and sees a new revision for the database migration added from 3.3.3 but > >> can’t find the same migration in its source (because it is 3.3.2). > > > > That is sort of what happened, except in the opposite direction, it > > was from 3.3.3 to 3.3.2. My question is therefore, do I have to > > update this alembic_version when I upgrade mailman to a newer version? > > That is what I was getting at. > > > Abhilash's conjecture is that the error was due to a Mailman version > accessing a database that had been previously accessed by a newer > version so that the version_num in the alembic_version table didn't > exist in mailman/database/alembic/versions/. This normally would not > occur on an upgrade of Mailman, but if you went from a gentoo Mailman > core to a version obtained by pip, it's possible that the gentoo Mailman > had an alembic version that wasn't known to the pip Mailman even though > the pip Mailman was newer. > OK, thanks. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 11 months

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

by Andrew Hodgson

Hi Stephen. Based on the conversation we had last week regarding you using Google Workspace as your smarthost, are you sure that it can't do the DKIM signing for you? With my Office365 acting as smarthost (see other post I made today), I had to turn off DKIM signing in my MTA as the Office365 was adding its own DKIM headers. Thanks. Andrew. -----Original Message----- From: Stephen Daniel <swd(a)pobox.com> Sent: Wednesday, May 17, 2023 3:05 PM To: Jeremy Stanley <fungi(a)yuggoth.org> Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Re: spf/dkim/dmarc Thanks all! On Wed, May 17, 2023 at 10:03 AM Jeremy Stanley <fungi(a)yuggoth.org> wrote: > On 2023-05-17 09:56:06 -0400 (-0400), Stephen Daniel wrote: > > Duh. I use Postfix running on the same machine as mm3 as my MTA. > [...] > > I don't use Postfix, but I asked a Web search engine (DuckDuckGo) for > "configure dkim signing in postfix" and got many informative hits for > various versions, platforms and distributions. Perhaps if you do that > you'll get similar results and can find instructions which most > closely match your deployment specifics. Best of luck! > -- > Jeremy Stanley > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org To > unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/me > ssage/B3J7FLZMVKFX35UWJSPQ5Y2MN2F46WND/ > > This message sent to swd(a)pobox.com > _______________________________________________ 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 andrew(a)hodgson.io

2 years, 9 months

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

by Prasanth Nair

Hi Mark, As you know, we can edit the individual messages using the message_id_hash. Is there any possibility that we can edit the original message which then updates all of the threads it has (for example, if someone already replied to the original message)? Or do we need to edit each message manually? Kind regards, Prasanth On Wed, 29 Sept 2021 at 15:46, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Many thanks for your help. I have managed to modify some of the messages > after following your instructions. > > Kind regards, > Prasanth > > On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> > wrote: > >> 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/ >>> >>

4 years, 4 months

[MM3-users] Mailmanweb RAM Usage

by Stephen J. Turnbull

Odhiambo Washington via Mailman-users writes: > Using the uwsgi.ini from the virtualenv method documentation, > mailmanweb is constantly using 2GB RAM on my server. Do you mean only HyperKitty + Postorius? That seems like a lot. My experience is that even on an insanely heavily loaded server (20k+ lists) the whole suite uses about 2.0G. Since on that server, Mailman core was forking 22 processes at ~83MB each (very little shared, not sure the technical reason for that, maybe the Python heap just can't be shared?), core was taking up about 1.8G. HyperKitty and Postorius took a little more (I don't recall exactly, maybe 250MB?) My more standard setup (that one had like 2 IN queue slices and 8 OUT queue slices) I ran Mailman suite + PostgreSQL (dedicated to Mailman) + Postfix + nginx (also mostly dedicated to Mailman) + Cyrus IMAPd in a nominal 2GB Digital Ocean droplet. It didn't run "comfortably", adding any serious load that chewed up 100s of MB RAM would get things OOM-killed, but 2GB total (including kernel and all) was barely enough for that system in normal situations. > My database (MariaDB) size is 2GB. Do you mean in memory or on disk? Either way that should have ~0 effect on the size of the Mailman core and web processes. > Is this expected? Depends on if you mean exactly what you said ("mailmanweb"). If so, no, I would expect mailmanweb (only) to run in 500MB easily and probably be OK in 250MB. If you mean "when I start Mailman and mailmanweb, memory usage jumps by about 2GB", then yes, that's what I'd expect. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 3 weeks

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

by Stephen J. Turnbull

tlhackque writes: > No. It's not an address. "local part" has to do with an address. in a > Message-ID, It's syntactically a local-part or other stuff. RFC 5322: 4.5.4. Obsolete Identification Fields The obsolete "In-Reply-To:" and "References:" fields differ from the current syntax in that they allow phrase (words or quoted strings) to appear. The obsolete forms of the left and right sides of msg-id allow interspersed CFWS, making them syntactically identical to local-part and domain, respectively. > It's in "id-left", which is a supposed to be something generated by the > host that makes the message unique within the namespace defined by > "id-right". Right, those are the *semantics recommended to implementers*, for the reasons which you summarize accurately. But a validating parser doesn't care about that. > Treat the whole thing as an opaque string. Nothing else is safe. s/else// and I'll agree with you. But safety is not an issue in threading (except for DoS if the procedure might be non-terminating; I suppose you could argue DoS if a user misses out-of-order mail from their boss and gets fired). > Yes, but did you fix the References header to match? Of course I did. That was long before I was a Mailman developer and started reading the RFCs, of course. > My quote was verbatim. 5537 does say you must trim. The point is > that the news rfcs may have introduced References, but they have > different obstacles to reconstructing threading. I don't think that's right, because mail suffers from the same line length restriction, with no exception for References. Mail has strictly more specification bugs. :-( > I haven't looked at that. Given the trimming in 3.4.4 of 5337, I > don't see how this can be produce the whole thread, unless you are > guaranteed to have the complete thread to fill the gaps. It can't because you aren't. But it seems unlikely that anybody is producing msg-ids longer than 74 characters, so 998/(74+1) = 13 is a long enough gap that you probably don't care that they're the same thread. At least not in any forum I participate in! > Plus, you can lose messages for strange reasons: The moderator > deleted one for inappropriate content. A message was copied to the > list and the poster. The response to the list is lost. But a > reply from the poster happens later. So the response in question > is never seen by the server, though the reference is. Life is hard > :-) > Sure, but Jamie's algorithm *will get that right* as long as all messages have a semantically correct In-Reply-To or References, and at least one descendent of the missing message mentions both it and its parent. What remains is a UI question: missing message placeholder, to display or not to display? > Heuristics are fine. Guaranteeing that the resulting algorithm > terminates is important. But real life doesn't get you to "enough > messages" 100% of the time. 100% isn't necessary. If the thread is sufficiently broken that Jamie's msg-id-based procedure doesn't work, his full algorithm falls back to your idea of collecting the singletons by subject and sorting. (He doesn't specify the ordering criteria, rather what objects (= subthreads of the same parent) are to be compared. Your suggestion of date seems most appropriate for the leftovers.) > > > See my other post. The left and right halves can, besides being atoms, > > > be non-folding quotes or literals. So you have to handle that. > > > > Of course, but that's just a SMOP. The harder problem is figuring out > > what to do about non-conforming input. > And, as I've noted: lost input. Lost input does not prevent thread reconstruction as long as (1) all messages have a Message-ID, (2) "enough" messages have a non-empty References containing "enough" msg-ids, (3) those References do not misorder the msg-ids or introduce msg-ids corresponding to messages not in the thread. It should be obvious why I don't want to define "enough" (except in terms like "enough means Jamie's algorithm can reconstruct the thread" ;-), but in particular losing *one* message will certainly not prevent reconstruction. > When they don't, trying to guess at the semantics of an opaque ID will > seem to work for a while. But it amounts to the halting problem. There > are lots of variants of "generate a globally unique ID with an '@' in > the middle". I may have created a new one today :-) The problem I'm trying to address with the "stripping" is incorrect copying of msg-ids by MUAs that try to parse them, as we saw here. Apparently the bug was in Mailman itself, so it's not required (and a bad idea, I guess). > Yes. But if they're well-formed, the <> are there, so stripping them > only saves a couple of bytes. > > If they're not, all bets are off. <two<three(a)example.net> - stripping > the outer <>s doesn't help. > > <"two<three"@example.net> is a valid message-Id, > and distinct from <"twothree"@example.net. Sure. Is it likely? > <twothree(a)example.net> distinct from <"twothree"@example.net>? > (unnecessary quoting, or a distinct message-ID) If you treat it as > opaque, you don't care. Take the whole thing, <@> included, as given > and look for it in the other fields. The most you might do is remove > quotes (and escapes) and use the left and right parts as your key. Which is basically what my stripping and cleaning procedure would do. The question is "does it help or hurt, on net?" If there was a widely distributed MUA out there that doubled the delimiters, it would help. Since it was Mailman doing that and it will be fixed, it's a bad idea. > You could also fingerprint the user agent (e.g. by the order of headers, > format of message-ID), and correct for its bugs. But I'm inclined to > report client bugs and get them fixed. Meantime, their messages are > unthreaded (but not lost). It's just not worth working around other > people's bugs - there are better uses for your time. That's not my experience. See Reply-To munging. Depends on the bug, of course, but all too often people think it's our job to help them deal with bad MUA design. > Yes. A message ID should exist. These days I think all MTAs will assign > one if the client doesn't. > What I tried to say was that there will be times where you can't figure > out where to put a message into the thread graph (or forest). Because it > references message that you can't find, or it doesn't have a references > or reply-to, or those fields are corrupt. None of those prevent you from threading that message. The only reasons you won't be able to thread a message at all are when no other available message references it (eg, if several MUAs in a row supply In-Reply-To but not References, and the middle messages are missing or their identification fields are corrupt), and when there are References that have conflicting opinions on where that message belongs. Of course if a message lacks References and In-Reply-To it will be identified as a thread root (unless some descendent manually corrects References ;-). Even then it could be grafted into the tree more or less correctly using your sort on subject and date procedure. > These are heuristics - you might come up with better ones. Yours are already implemented in Pipermail, I believe, I'm not sure about HyperKitty. I don't think Jamie's algorithm messed with [name] and [serial number] because they weren't common at that time, but he stripped Re: and its nonconforming variants, as well as "Fwd:". > At least with an orphans bucket, you don't end up with "invisible" > messages. Nothing I suggested produces invisible messages, just a different set of orphans or occasionally a misthreaded message that seems to be a duplicate if different msg-ids are munged to the same string. At least not in Jamie's algorithm. I don't know exactly what algorithms are used in Pipermail and HyperKitty. Interesting discussion, but I've reached the point of diminishing returns. I will be checking to see if any of your suggestions are improvements over what HyperKitty currently does, for sure! Steve

7 years

[MM3-users] Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/24/20 2:10 PM, Massimo Zappalà wrote: > Hi everyone, > > My Version installed on Debian buster: > mailman3: 3.2.1 > postorius: 1.2.4 > hyperkitty: 1.2.2 > > All interfaces work well in Italian language, but "Welcome message" is in English. First question: Is the Subject: in English or Italian? If the Subject: is in English you need to compile the Italian message catalog as I described in my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Then, as far as the message body is concerned, it is built from a template. At present, in the Mailman source distribution, the only templates that are translated are French and German You will find the complete set of English templates at /usr/lib/python3/dist-packages/mailman/templates/en/. You have choices. 1) You can create /usr/lib/python3/dist-packages/mailman/templates/it/ and make Italian translations of all the English templates in the it/ directory in files of the same names, and submit a merge request at <https://gitlab.com/mailman/mailman/-/merge_requests> to merge them into the source distribution. If you are not familiar with software development in general and Mailman development in particular, this is probably beyond what you can do. 2) Find Mailman's var/ directory. This is the directory containing archives/, data/, etc/, lists/, locks/, logs/ and perhaps other sub-directories. You then need to create the full path to var/templates/site/it/ and place Italian translations of some or all the templates there. When doing so, you can add site customizations. 3) You can use Postorius to create templates for individual lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Guillermo Hernandez (Oldno7)

El 2/4/23 a las 11:12, Odhiambo Washington escribió: > On Sun, Apr 2, 2023 at 11:35 AM Guillermo Hernandez (Oldno7) via > Mailman-users<mailman-users(a)mailman3.org> wrote: > >> It seems that FreeBSD is handling IPv6 in a way that other OSs dont. It >> surprise me, because FreeBSD was the first OS where IPv6 was deployed, >> but it is what it is. >> >> Thaks to everybody for your patience, specially Odhiambo and Mark. >> > @Guillermo Hernandez (Oldno7)<guillermo(a)querysoft.es> > > Thanks for the update. However, I don't think I would entirely blame > FreeBSD for this. As Mark pointed out, something did not upgrade completely. I'm NOT blaming any of the parts involved... Sure, most probably is my fault. But the last upgrade shows that the process that fail is involved with mailman upgrade. The last server was working smoothly and it has higher traffic than the first I tried. It cannot be that I missed that something was not working for weeks (since the last upgrade of the OS) > This could be some quirk within your FreeBSD ports and you may need to > ensure everything related to your Python version is updated. It could be... but since a year ago I configured a poudriere repository and Im updating from packages, not from ports. But this do not discards your guess > Why am I saying this? > I am running MM3 in a virtualenv on FreeBSD (13.1-p6) and I did upgrade to > the bleeding-edge MM3 by running all components from git, and I don't have > this problem you had. Not the same version exactly though. But similar enough > Could you possibly fully update your Python libraries by following the > entry dated 20220626 in /usr/ports/UPDATING? Could you run all the steps, > do away with the workaround, and see if that fixes the issue? I switched to python 3.9 in early 2022 (or it could be 2021?), that updating point is not applicable here. All my python apps are 3.9. And therefore it would not explain why a server which was working perfectly before this mailman3 upgrade, was falling in this strange IPv6 problem after. > > PS: I don't even think many people are running MM3 on FreeBSD, leave alone > from the ports. Well... leaving FreeBSD for apparently greener paths in my servers is not something I'm planning to do. They are running some FreeBSD version since 1993... and then, they are working. I'm not running MM3 from the ports, I installed every bit of it from python tools. > I have come to learn that even in Linux, using the distro's > packages is usually problematic. Again, I don't install from any distro package > Running MM3 from virtualenv is quite safe and to be honest, you can migrate > your setup from where it is now to a virtualenv and you will not lose > anything. And I cannot deny it... but I'm already under one layer of virtualization... the mailman servers run in a jail environment. I don't want to add more layers if I can avoid it. Thank you very much for your pointings. Regards > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 11 months

[MM3-users] Re: import21: A string literal cannot contain NUL (0x00) characters.

by Stephen J. Turnbull

Henrik Rasmussen writes: > It seems that this issue is still unsolved. Is there any estimated > date for a fix? https://gitlab.com/mailman/hyperkitty/issues/155 . Problem-oriented executive summary: Why do you think this is a problem that Mailman should solve? What is your desired treatment of this data? tl;dr for Unicode wonks and wonkabees: My personal take is similar to Simon's. Unicode NULs are rather dangerous, because any time you convert to an ASCII-compatible encoding and store it where a C routine can get at it, you risk data corruption when a C string function decides that the NUL is end-of-string, and ignores the tail of the string. To deal with NULs embedded in an array of C chars, you have to forego the whole suite of str*[1], *printf, etc stdlib functions and either (A) dive down to mem* functions, keeping accurate char[] lengths on the side, or (B) create a complete suite of array-handling functions that deal with this for you. I agree with Simon's guess that you probably have corrupted data or metadata that you're passing to HyperKitty. (By "corrupted metadata" I mean that you've got binary data labelled with "text", or that you have text encoded in something like UTF-16 that normally includes 0x00 *bytes* as a component of non-NUL *characters*, but labelled with an ASCII- compatible encoding such as ISO 8859/1. The latter is a common hack to insert binary data, or "any-encoded" text, into text databases.) This is based on the long tradition of avoiding NULs in string data based on both their standard interpretation as ASCII (memory padding which is to be *ignored*[2]) and the danger that they pose to C programs that use the C stdlib to handle "character" data. It's true that both Mailman 3 suite and Django are written in Python, which has implemented NUL-handling strategy (B) for us. However, Mailman suite eventually calls into a few C (or C++) libraries, especially the database backends, as in this issue. We can't do anything about those backends, of course. Filtering the incoming data is something we could do, I guess, but as Simon points out that would be pretty expensive, and filtering erroneous NULs silently would likely result in inserting corrupt data in the databases. If you're really sure that you have valid ASCII (or Unicode) NULs embedded in your text data, you could try configuring an alternative backend (both for Mailman core and for Django) that handles NULs as valid characters. I don't know if there are any, let alone whether we support any, though. Footnotes: [1] Including the strn* functions! They protect against buffer *overruns*, but NUL is still end-of-string. [2] Here's what ECMA-48 "Control Functions for Coded Character Sets", which I believe to be identical to ISO 6429 except that ECMA standards are free to read and ISO charges about $100 for this, says about NUL: 8.3.88 NUL - NULL Notation: (C0) Representation: 00/00 NUL is used for media-fill or time-fill. NUL characters may be inserted into, or removed from, a data stream without affecting the information content of that stream, but such action may affect the information layout and/or the control of equipment. Unicode doesn't say how to interpret NUL at all, but does recommend ISO 6429 as one good way to interpret control characters not otherwise dealt with in Unicode (and it's the only way that Unicode mentions).

8 years

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 11/5/20 12:20 PM, Stephen J. Turnbull wrote: > Brian Carpenter writes: > > > I think everyone should care that data should be removed when there is > > an expectation that it is being removed. > > I do care, and I agree that everyone should care. > > The difference is that I also think that everyone should care that > data *should not* be removed when there is an expectation that it > *will be retained*, and, therefore, that the base Mailman we > distribute should at least ask before deleting data as a side effect > of some other action. > > I don't see how I can make it plainer than that, so I'm done here. Well I am having the same difficulty. *With your statement here, let me ask you this:* 1. If someone subscribes to a public list, are they being notified that a user account is being created (by Mailman 3 core) as part of the subscription process? 2. When someone unsubscribes from mailing list, are they being notified that their data is being retained when they unsubscribe (by Mailman 3 core)? 3. When someone subscribes to a public list, are they being made aware that there is no way, for them, the subscriber, to remove their user data *except* if they also register an account through Postorius and then proceeds to delete that account along with them unsubscribing from a list? 4. Am I correct to assume when someone unsubscribes from all lists, AND deletes their Postorius/Django account, that all data on them is being removed? So please understand that questions 1-3 are for a scenario of a subscriber that is only subscribing to a SINGLE list and has not registered with Postorius/Django. Question 4 is dealing with someone who has multiple subscriptions AND is also a registered Postorius/Django user. *This is what I believe are valid reasons for an expectation that data being retained:* 1. A subscriber who is NOT a Postorius/Django user but has multiple subscriptions to various lists on the same Mailman 3 instance subscribes from a single list. They should expect their user data to be retained because they still have active subscriptions to other lists. 2. A subscriber who IS a registered Postorius/Django user is subscribed to a single list and unsubscribes from that single list but did NOT delete their Postorius/Django account. 3. A combination of 1&2. All I am requesting is that for single list subscribers who are not registered users of Postorius/Django, to have their user data totally removed when they unsubscribe. I simply fail to see how someone could claim a right to data retention when they unsubscribe from the one list that they were subscribed to. This is important to me because almost all of the list members of the lists that I host fall into this category: single list member who is not a registered user of Affinity/Postorius. > If you need help implementing the "delete everything" policy in > Affinity because of some insufficiency in the REST API, let me know > and I will make sure the REST API allows you to do that. But I'm > pretty sure it's already possible. It has already been done with Affinity and the REST API was sufficient to allow us to do that. Thanks for offering. > _______________________________________________ > 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/ -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/14/20 9:24 PM, Alan So wrote: > Just FYI. > > I omitted the "<" and ">" when I replace the real testing address with name(a)example.com. > > It should be, > > CC: "ABC DEF > (XYZ)" <name(a)example.com> Actually, you didn't omit them. It's just the way HyperKitty renders what it thinks is an email address that makes it appear they aren't there. If you download the thread from HyperKitty, you'll see they are there. Anyway I am unable to duplicate your issue with your example data. I sent this raw message ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Cc: abc def (ghi) <abc(a)example.com> "abc def (ghi)" <def(a)example.com> Subject: test Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 Hi ``` and the message I received from the list included these headers ``` To: test(a)example.com From: Mark <mark(a)msapiro.net> Message-Id: <msgid(a)example.com> Date: Sat, 16 May 2020 09:22:12 -0700 CC: "abc def (ghi)" <abc(a)example.com>, "abc def (ghi)" <def(a)example.com> Subject: [List] test ``` I do observe something similar to what you report that has nothing to do with folding. If I omit the trailing ">" in an address as in ``` From: Mark <mark(a)msapiro.net ``` the address becomes ``` From: "Mark <mark"@msapiro.net ``` So possibly your issue involves missing angle brackets. In order to say more, I'd need to see the actual headers as sent and received or at least an accurate munged representation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

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

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > On 6/22/20 6:23 PM, Stephen J. Turnbull wrote: > > By design, Mailman core doesn't need to talk to the Internet or to the > > secure internal network -- Internet functions are delegated to the MTA > > and the webapps, and local configuration is via shell access which in > > principle could be console. > > Sorry, I missed this earlier. I was more or less trying to describe what I thought you were trying to do, and noting that Mailman is designed for it. Thank you for the confirmation. > I am using exim and there is a big benefit when exim can see the > list directory names. Indeed. (I wrote the proof of concept Exim config for Mailman 3 on Debian.) But that's *all* it needs to see. It should be possible to get that information to Exim in some other way, perhaps through a small app that talks to the REST API. If that's generalizable to other MTAs (especially Postfix, but also Sendmail and maybe qmail) it's worth us looking into (and if it's Exim-specific, at this stage I'd say "patches welcome"). This is also the kind of thing that an NFS read-only mount does fine (of course you may not want NFS on a system in the DMZ :-/ ). > However, I find the mailman shell program not very intuitive, and so > would prefer to have the web app for admin purposes. By "local configuration" I mean anything that requires access to the .cfg files or installing code. Anything you can do via Postorius (or soon, via Affinity, hi Brian!) is not local configuration in this sense.

5 years, 8 months

[MM3-users] why am I seeing "Access to the archiving API endpoint was forbidden"

by Dmitry Makovey

Running docker-based MM3 I get quite a few messages in mailmanweb.log: ERROR 2018-01-19 19:09:07,467 401 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.19.199.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured which points to the docker host making those requests. But I have no scripts/code dunning on host to do that. I've posted to this list earlier (see "mailman-web: ResponseNotReady" and "Getting connection refused on postfix trying to connect to mailman-core:lmtp") my woes with public vs private IPs in my setup and my "hack" was to set up docker-compose with explicit domainname and hostname: mailman-core: domainname: my.com hostname: mailman ... networks: mailman: aliases: - mailman.my.com where mailman.my.com is the public IP of the service. so I think I'm in the weird state where mailman-core container starts off communication on a private docker IP and finishes it off on what it thinks is public someplace... not sure where is that coming from. I ran a cross-ping for all containers to confirm they all see only private IPs and they do: core, web & nginx cross-pinging each-other and mailman.my.com all show private docker IPs so why would any packet be routed from external? can I allow more than a single IP for MAILMAN_ARCHIVER_FROM ? ITMT I've moved MAILMAN_ARCHIVER_FROM to settings_local.py and hardwired it to be 172.199.19.1 and I believe there are no errors in log files... but again - that's a lot of tiptoeing and tapdancing around the IP assignment in docker so I'm looking for input to simplify the setup. -- Sr System and DevOps Engineer SoM IRT

8 years, 1 month

[MM3-users] Re: HyperKitty/Mailman3 issues

by Mark Sapiro

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? > 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. > 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

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

by Mark Sapiro

On 11/25/21 10:56 AM, David Newman wrote: > > Thanks for this. After setting these variables and restarting mailman3 > and mailmanweb, the mailman user still cannot find a hyperkitty_import > command (neither can root, btw). Again, I installed MM3 and > Django/Postorius/Hyperkitty using the venv and web docs previously > referenced. Don't run mailman or django admin commands as root. This causes issues when files are created by root and can't be read by mailman. What django admin command are you running? If you don't set DJANGO_SETTINGS_MODULE in the environment and you have activated your virtualenv and run `mailman-web` as the django admin command it will set /etc/mailman3/settings.py as the settings. > On the plus side, all lists now appear in the admin web page. However, > lists created from the admin page do not appear in a site list page, > even though all lists are in the same site/domain. By default, only lists that you are owner, moderator or subscriber for are shown. What if you click Filter by Role and select All? > Finally, how to make these exports permanent? I did not see this covered > in the migration doc above. This is on a Debian system where the mailman > user's shell is bash. Is this simply a matter of adding environment > variables in the mailman user's .bashrc file? You can do that but as I note above, if you run `mailman-web` you shouldn't need to. You can add a `source /opt/mailman/venv/bin/activate` command as mentioned at https://docs.mailman3.org/en/latest/install/virtualenv.html#activate-virtua…. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

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

by Diana von Bidder

Hi Stephen On Mon, 2022-08-22 at 23:51 +0900, Stephen J. Turnbull wrote: > blup(a)fortytwo.ch writes: > > Try queue/, especially look for the out[going], pipeline, and shunt > subdirectories. I have several entries in /var/lib/mailman3/queue/shunt/ with Aug 21 timestamps, and several entries in /var/lib/mailman3/queue/shunt/ with current timestamp (i.e. everytime I ls -l there is a new timestamp with the current time). > > > Is the 'outgoing' qrunner still running? (ps ax | grep outgoing) > > > > no > > Sorry, I got that wrong. Mark recommends this: > > ps -fwwA|grep runner=|sed s/.*runner=// > > and gave this as sample output: [..] My output looks exactly the same. > > I have more or less no Python knowledge (i.e. I can read and > > understand Python but can't write it). Could you please give me > > detailed command by command instructions. Thanks. > > I'll take a look at it tomorrow, but I can't promise results until > the weekend if I can't write a script in 30 minutes. Normally Mark > Sapiro would handle this kind of thing, but he's offline for a couple > weeks so you've got me. My knowledge is mostly on the email > protocols side of things (Internet message format, authentication > protocols), not the internal processing. I'll do what I can, but if > I can't do it real quick it's probably going to take me several > hours, which I'm not going to have until the weekend. Having something by the weekend would be perfectly fine. Thanks for your time! Regards Diana

3 years, 6 months

[MM3-users] Re: How to delete non-users

by Allan Hansen

Hi Mark, Thank you for looking into it. We are very strict about memberships, which we are because of spam, bots and malicious contributors and because we don't want anyone to think that our lists are used for spam: When a user applies, the server sends a message to the moderator. The moderator communicates with the potential member and accepts or does not accept the application. At this point, if the user has not been accepted, but tried to send a message to the list, a non-member membership is created. When he/she logs in to list his/her account, the list to which he/she holds non-memberships will be listed and the user will think that he/she has been properly subscribed (why else are the lists listed). Noone notices the column that shows the role as 'nonmember.' So he/she thinks that the subscription request has been accepted, but nothing is working. That's why the 'non-member' record is an issue. I also don't see why non-members are automatically added, filling up the database with junk (at least from our point of view, with all respect). But our lists don't accept messages from non-members. Such messages are quietly discarded, as most are spam, as mentioned above. So now the user is neither getting emails from the lists nor is unable to send messages to the list. The next step for the user is to complain to me. ☹ I have looked for a template that could be used to warn someone when he/she is added as a non-member, but did not find one. It's also not clear that I'd want one, as most of these non-subscriptions are by spammers and I prefer not to reply to spammers. __ I tried your suggestion below, Mark. Here's my transcript: ********** Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> ********** I did this twice, once with commit() and once typing ctrl/d (ctrl/D) just gave me a beep. Calling commit() did not return to the ... as in your example, but showed the >>> prompt, so I tried ctrl/D (beep) and then ctrl/d (exit). I then went to the Postorius page for one of the lists and found that all the non-members were still present. Yours, Allan On 9/16/22, 15:01 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/16/22 11:19, Allan Hansen wrote: > Hi all, > > This is a bit of an emergency: > > I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. > For individuals I have been able to delete their non-membership and they then could subscribe properly. I don't understand. the fact that an address is a non-member of a list should not impact subscribing that address as a member. > I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. What is actually happening when the non-member attempts to subscribe as a member? What do they do and what it the result? > I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). > > Can anyone help me find out how to > a. delete all non-members of all my lists If you have access to `mailman shell` you could do: ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> commit() ``` > b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) nonmembers are an integral part of Mailman 3's architecture. The basic idea is a nonmember has a moderation action and setting a nonmembers moderation replaces MM 2.1's adding that address to one of *_these_nonmembers (The legacy *_these_nonmembers attributes still exist, but only to support regexps). It would require extensive modification to not create nonmembers. However, I still don't understand why the presence of a nonmember record is an issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 5 months

[MM3-users] Re: Huge performance issue: Mailman doesn't (seem to) receive any mails.

by Abhilash Raj

On Wed, Sep 18, 2019, at 8:14 AM, Mark Sapiro wrote: > On 9/18/19 3:32 AM, Henrik Rasmussen wrote: > > I am running maxking/mailman-*:0.2 (GNU Mailman 3.2.0 (La Villa Strangiato)). > > > > It looks like Mailman is not receiving (enough) mails, but are keps in the Postfix queue and I can't figure out why. > > > > I get a lot of "mail for [172.19.199.2]:8024 is using up 7841 of 7841 active queue entries" in the postfix container log (more postfix log at the buttom. > > > I know nothing about Docker containers and how they communicate with > each other, but Postfix is trying to deliver mail via lmtp to > [172.19.199.2]:8024. Mailman's lmtp runner should be running and > listening on port 8024. Either that is not the case or that port is not > exposed to Postfix on IP 172.19.199.2. Right, that is what I was wondering, you verify that by using telnet on the specified IP and Port (172.19.199.2:8024). `docker-compose ps` lists all the running containers, do you see all the containers running? You mentioned that Mailman is not receiving enough emails, do you get *any* emails from Mailman? I am trying to see if this is a perf problem or if Mailman's LMTP isn't reachable at all. > > -- > 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)

6 years, 5 months

[MM3-users] Re: Invalid confirm text

by Mark Sapiro

On 8/17/20 4:53 AM, w.schoener(a)alp.dillingen.de wrote: > One thing I forgot to mention: > a week ago, the confirmation-mails still worked. > > And now: > All attempts to confirm the subscribe message failed. I used the list-request(a)list.domain and sent text-only message with the "confirm token" in the subject and/or in the body. This should work. What's in your MTA's logs? > So today I tried and used the Mailman shell to change the pending state to "confirmed", as you described here: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > After I submitted the command util.confirm('hex_token') and restarted mailman with > mailman stop > mailman start It isn't necessary to stop/star/ or restart mailman. How did you exit mailman shell. You must exit with ctrl-D or issue commit() or your transactions won't be committed. In particular, if you exit with exit() without first issuing commit(), nothing will be done. > the pending user wasnt confirmed but cleared, as if he never sent a subscribe-message. The only way to subscribe seems to be by logging in and using there the subscribe-form. What is the list's subscription_policy? It seems you successfully confirmed that token, but that may not be the last step if the list's subscription_policy is confirm_then_moderate. > Do you have any idea, whats going wrong here? I dont know what to do any more. Clearly something is broken, but I don't know what unless it is some permissions issue on the template directories/files you created. Have you looked at Mailman's mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

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

by Andy Smith

Hello, 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. > 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. Cheers, Andy

3 years, 8 months

[MM3-users] Re: Installation Wooes

by Mark Sapiro

On 5/3/20 8:43 PM, Samir Faci wrote: > Inline. > > On Sun, May 3, 2020, 20:32 Mark Sapiro <mark(a)msapiro.net > <mailto:mark@msapiro.net>> wrote: > > You are sending from a remote machine 198.199.98.177 to a presumably > remote domain domain.com <http://domain.com> so relay access is > denied as it should be. > > You need to add 198.199.98.177 to mynetworks in Postfix. > > > I can but domain.com <http://domain.com> is basically my Gmail I just > regex-ed the logs. If that's the fix is have to add every recepients > domain to mynetworks. You absolutely don't want to do that. The log entry is confusing. Between your munging domains and my MUA adding mailto: links to every email address, it's a mess. Let's try again: May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com>: Relay access denied; from=<booh-bounces+csgeek=domain.com(a)lists.domain.org> to=<csgeek(a)domain.com> proto=ESMTP helo=<[127.0.1.1]>. This says Postfix received a RCPT command from 98.199.98.177. It looks like it comes from Mailman, i.e., the envelope sender loogs like a Mailman VERPed address <booh-bounces+csgeek=domain.com(a)lists.domain.org> for a message to <csgeek(a)domain.com> and that is the envelope recipient and the sender identified itself in EHLO as [127.0.1.1]. So Postfix thinks it is asked to relay from 98.199.98.177 to domain.com. Note that 98.199.98.177 is a Comcast network IP. It has nothing to do with gmail. So is the connect comes from Mailman on the Postfix machine, why does Postfix think it comes from 98.199.98.177. That's the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

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

by Stephen Daniel

Nate -- A few months ago I, a total novice with Mailman, set out to install Mailman3 on a Debian server. I used these instructions: DOC/Howto_Install_Mailman3_On_Debian10 <https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10> It took me several tries, but with some help from people on the list it is now up and running. It was also a *much *bigger investment of my time than I expected. I cannot say I completely understood what I was doing every step of the way, and some of the steps are like: go edit the config file so that it is right, which can be daunting. However, even for someone who's never touched mailman before, it can be done. Best of luck -- Stephen On Mon, Jan 24, 2022 at 7:19 PM nate <mailman-list(a)linuxpowered.net> wrote: > Hello mailman users out there - > > I have been a casual user of mailman for 21 years now I think it is. > Most of my > lists were super small (my only current lists have no more than 8 > members each), > super low volume. It's "just worked" over the years, no issues. I have > been > using Linux since 1996, not a newbie here. 21 years ago I deployed > mailman as > part of our corporate email and then there were a lot more users. Since > that > time I just use mailman on my personal server. > > I did a apt-get dist-upgrade on my system and was surprised to see > mailman had > vanished. Wasn't expecting that.. not a big deal, or so I thought. > > I am running Devuan 4, which is based on Debian. Investigating further > it seems > Debian at some point dropped Mailman 2.1 and started including Mailman > 3. OK, > not too bad I thought.. > > I was/am prepared to start my mailing lists from scratch again, manually > copy/paste over settings/users/etc. Don't care about archives etc. I > setup mailman > 2.1 on another Devuan 3.x system and copied my mailman configs over to > it, and > can view them fine via the mailman cgi scripts through Apache, I was > planning > on just copy/pasting list settings between the two systems for each > list. > > Roughly 10-15mins into trying to get mailman3 off the ground I just find > myself > overwhelmed. That doesn't happen often. I'm honestly completely shocked > at > how it seems the complexity of the system has increased by orders of > magnitude. > > I have been browsing around > https://docs.mailman3.org/en/latest/pre-installation-guide.html > (and other links on that documentation site) > > But as much information as there is, to me there really isn't any > information > there. If that makes sense. I'm sure it doesn't make sense so let me > give an > example. > > On this page: > https://docs.mailman3.org/en/latest/config-web.html > > I assume that would lead me to how do I configure the web interface so I > can do stuff with it. > > I setup an admin account, then it goes into scheduled tasks(which appear > to > be handled by the Debian package already but don't know what these tasks > would have to do with a web interface). I tried sending a test email but > that failed, I looked at the setting up email portion but it does not > give any indication where that config would be stored, a recursive grep > on /etc for EMAIL_BACKEND turns up nothing (there is a /etc/mailman3 > directory with some files in there). > > Then it goes into other things like task queues, full text searching, > here I am just looking for info on where this web interface is, where > is the config, what port does it listen on? Is it a cgi like mailman2? > It seems like it could be a standalone service. > > Then it shows a bunch of other settings, not indicating what file these > are stored in(or what directory the file is in), etc etc etc. Debian's > own documentation is severely lacking in this department as well, > normally > I am used to going to /usr/share/doc/<package>/ and there is some useful > stuff. There is stuff for mailman3 but it's minimal at best. > > So I'm thinking mailman3 is not the package for me. I've really > appreciated > mailman 2.1 (and earlier versions) as I said they always just worked, > never > had to think about them. I'm sure a lot of good hard work has been put > into 3, I just don't recall the last time I looked at a project and just > honestly didn't even know where to begin which surprised me so much > given > my 20+ year history of mailman as a user and as an admin. > > Is there some document(s) out there that would be more beneficial to > me in setting up mailman3? I see that mailman 2 looks like it's still > being maintained, I assume mailman3 is the result of python3 code and > mailman2 perhaps uses python 2.7? I am unsure on the ability to run > mailman2 on a modern Debian-based distro since of course Python 2.7 > is pretty obsolete at this point (or maybe Mailman 2.1 doesn't use > python I don't recall). I could try to install the older mailman 2.1 > package on Devuan 4 and see what happens I don't know if it would > be that simple or not. > > Or is there a better MLM for simple use cases? I used Majordomo back in > the 90s and was happy to get onto Mailman from that. Something similar > to > Mailman 2.1 in features/functionality. Worst case I could just use > aliases > in my postfix config at the end of the day that is all that is really > needed, though I do like some level of access control on who can email > the lists(even if nobody outside the list knows the list exists), I've > had some of these lists for 2 decades, old habits die hard right? > > I did some searches for mailing list software on the Debian package > archives and saw a few options, nothing really stood out at me as > something super interesting yet though. > > I don't mean to come across as harsh or complaining or anything I'm > just here in shock kind of. Thinking about what the best solution for > me would be. My mailing lists have been broken for a couple of weeks > but that's really not a big deal. > > thanks > > nate > _______________________________________________ > 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

Search results for query "dO"