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

[MM3-users] Re: settings sanity check

by Jeremy Stanley

On 2023-02-08 10:50:20 +0300 (+0300), Odhiambo Washington wrote: > Does mailman-web do sanity checks in settings.py? Not that I've seen, other than a traceback if the Python interpreter can't parse it at least. > Suppose I have the following: > > Q_CLUSTER = { [...] > Q_CLUSTER = { [...] > Which setting will it go with? The second one. > And why doesn't it complain about a setting being made 2x? It's a Python script, and Python allows you to redefine variables (as do basically all scripting languages for that matter). -- Jeremy Stanley

2 years, 2 months

[MM3-users] Re: Pd CRON mailman gatenews

by Mark Sapiro

On 3/18/23 01:23, Pierre Malard via Mailman-users wrote: > Hello, > > That’s going again! > > If I understood your advice correctly, if we do not have lists for which the gateway to the mail is set to yes, we can comment on the CRON "gatenew". > > This is what I will do Yes, you can comment or remove gatenews from the crontab. Note that starting with Mailman 3.3.5, gatenews will be run if necessary as a periodic task in the nntp runner rather than by cron. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Installing Mailman for the first time

by comprepair_jimberg＠icloud.com

I am running Debian 11 Server and wanting to install Mailman 3 Will this work for what I am trying to do? https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 If not is there a shorter list of steps to accomplish what I am trying to do? Jim

2 years

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

by Mark Sapiro

On 3/30/23 11:07, Odhiambo Washington wrote: > So the MTA option that doesn't involve any regex is better than no? Partly it's a matter of taste and possibly a matter of necessity. I.e. a list admin can do this with header filters and may not have access to the MTA config. Also, it's not clear to me that doing this in Postfix is less complicated than understanding a regex. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

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

by Andrew Hodgson

Eggert Ehmke wrote: > 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? Yep same here, I just picked a user without a name configured for privacy reasons. Actually most users didn't have a name configured. Thanks. Andrew.

1 year, 11 months

[MM3-users] Help needed to create filters that were working in Mailman 2.

by mrl＠psfc.mit.edu

How do I make a filter that if it matches, it accepts the message and doesn't check the remaining filters? I could do this using the anti-spam filters in mailman 2, as there was a Accept option. But there is no Accept option in Mailman 3 (that I can find). I tried using "Default antispam action", but that didn't stop the rest of the filters from being applied. Thanks for any suggestions. - Mark

1 year, 10 months

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

by Ken Alker

How did you join the split thread? The order of the first two emails is flipped; the original email from 6/23 is showing after the second email on 6/24. Do you know how that happened? Do you have a way to fix that too? This is a good learning experience for my new adminstering responsibilities.

1 year, 9 months

[MM3-users] Re: How do I specify the TCP port number for Postgresql?

by kjohnson＠eclypse.org

Thank you for this helpful and prompt reply! Ken

1 year, 9 months

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

by Danil Smirnov

Hi, On Fri, Jul 21, 2023 at 6:46 AM Franklin Weng <franklin(a)slat.org> wrote: > > You can edit the template for the list information to remove the > > subscription form. > > Could you please tell me how to do it? > There is a better way to do this - via SHOW_ANONYMOUS_SUBSCRIBE_FORM = False in settings, however, you need the latest Mailman 3 version for this to work. With my best regards, Danil Smirnov

1 year, 9 months

[MM3-users] LDAP user email verification

by Tony Deshields

I'm running the docker-mailman setup with LDAP integrated. My users that authenticate against LDAP are still required to verify their email address however, I do not want this functionality. I was looking for guidance on possibly configuring it so my LDAP users do not have to verify their email address.

1 year, 7 months

[MM3-users] Re: Strange password problem

by Stephen J. Turnbull

Roland Miyamoto via Mailman-users writes: > I could easily imagine a situation "Envision" = "imagine". We have limited resources. If you don't have an actual use case, we will postpone even the discussion until someone who says "I do <this> but it sometimes screws up <that way>" comes along. If you do have a real use case with real costs, we may want to have the discussion of whether this is something we should target in the next release. Steve

1 year, 7 months

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

by Wikinaut

Hmmm, regarding POSTORIUS_TEMPLATE_BASE_URL , just as a remark, 'http://localhost/mailman3/', this was the installed default value. Regarding the django issue: I do not remember to have triggered an update or so when suddently the error popped up, I did the pip install -U after that. Do you have a recommendation for me, a hint, how to fix the problem without losing the database and settings of my mailing lists? It is so strange to see the error just right now (while only concentrating on the "template problem"); mailman3 worked for a long time.

1 year, 6 months

[MM3-users] Re: Mailman3 on virtual domains

by Lars Bjørndal

[Mark] [...] > See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… Ok, so I have to create an alias_domain in Mailman. Is it possible to do that from the web interace? I find an Edit button for each domain, and then I may change name and description. But I can't find an option to add an alias_domain. As I'm blind, and using a text only browser, some information may have been missing. Or can I do it from the command line? Thanks, Lars

1 year, 6 months

[MM3-users] Re: ModuleNotFoundError: No module named 'mailman_web'

by Mark Sapiro

On 11/10/23 09:51, gordon(a)dickens.com wrote: > Hi Mark, > > The command "pip install --force-reinstall mailman" ran successfully. Then, the command "/opt/mailman/venv/bin/mailman -C /etc/mailman3/mailman.cfg" generated the following errors: > ... >> return __import__("pymysql") >> ^^^^^^^^^^^^^^^^^^^^^ >> ModuleNotFoundError: No module named 'pymysql' > > What to do now? Apparently pymysql was previously installed globally in python3.9 and is now gone. I suggest with your venv active you do ``` pip install pymysql ``` -- 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] Where do I find the check_hk_archive script

by Lars Bjørndal

In https://docs.mailman3.org/en/latest/migration.html I'm adviced to run the check_hk_archive script found in hyperkitty/contrib. When trying `git clone https://gitlab.com/mailman/hyperkity`I get: Username for 'https://gitlab.com': Is it possible to get the script without an account on gitlab? Thanks, Lars -- Lars Bjørndal <lars(a)lamasti.net> Ostadalsveien 64, 0753 Oslo. Mobil: 958 37 537

1 year, 5 months

[MM3-users] Re: Where do I find the check_hk_archive script

by Lars Bjørndal

[Mark] [...] > If you have HyperKitty installed, > there should be a hyperkitty/contrib directory in your installation, e.g. > /opt/mailman/venv/lib/python3.x/site-packages/hyperkitty/contrib/ containing > the check_hk_import and cleanarch3 scripts. I have /opt/mailman3/venv/lib/python3.11/site-packages/hyperkitty/, but no folder called contrib under it. I did install with `pip install mailman-web mailman-hyperkitty`. Lars

1 year, 5 months

[MM3-users] Re: Where do I find the check_hk_archive script

by Mark Sapiro

On 11/18/23 22:47, Lars Bjørndal wrote: > > I have /opt/mailman3/venv/lib/python3.11/site-packages/hyperkitty/, but no folder called contrib under it. I did install with `pip install mailman-web mailman-hyperkitty`. I see that for some reason the contrib/ directory is missing from the hyperkitty package on PyPI. I'll look into that. -- 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: Editing the "example.org" site

by Stephen J. Turnbull

Odhiambo Washington writes: > This is interesting. However, you meant the default example.com, > right? Whatever it is is fine for me. I was going from memory. > And that link also let's me DELETE the site :-) Don't do that! What happens afterward is not hilarious, it's a self-DOS unless you know exactly what you're doing. Among other things, the next site you create is still #2. It's not really any cleaner just because you got rid of the example site.

1 year, 3 months

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

by Richard Rosner

Good to know, but even SPF isn't broadly enough used. And no, locking out all non-members doesn't work in this case, that's not how these lists are supposed to work. And after some trials with SpamAssassin, seeing that it pretty much doesn't seem to have any good documentation - or it's lacking features left and right, which would be even worse - so I'm sticking with rspamd. Also, what you propose is the exact opposite of what I'm trying to do. I do not want to have the false positive rate skyrocket, that's the whole point of this thread.

1 year, 1 month

[MM3-users] See list of subscribers

by Tom Yates

I'm sure I'm just doing something stupid, but I can't work out what. I have a list, as admin under "Settings" -> "List Identity" -> "Members List Visibility" I have it set to "Only Mailinglist Members". But a random subscriber, who's signed up and authenticated, when she visits the list page she sees her subscription, but no option to list the other subscribers. Is she looking in the wrong place? Do I need to open up more settings? Am I just being an idiot? Thanks for any light anyone can shed. -- Tom Yates - https://www.teaparty.net

1 year

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/22/24 21:29, Mark wrote: > > > And still getting the error in the Postorius webpage ... > > HTTP Error 400: HTTPSConnectionPool(host='lists.mydomain.com', > port=443): Read timed out. (read timeout=5) What do you get if you do ``` sudo -u mailman curl https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… ``` with the template set in Postorius? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-24 03:58, Mark Sapiro wrote: > What do you get if you do > ``` > sudo -u mailman curl > https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… > ``` > with the template set in Postorius? The welcome message is returned. root@hel:~# sudo -u mailman curl https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… Test Welcome message for new subscribers.root@hel:~#

1 year

[MM3-users] Change Dmark settings via command line

by bob B

I need to set all the DMARC settings on are lists to "replace from with list address". Is there an easy want to do this via cli? I could do it by viewing the web interface but we have a lot of lists.

11 months, 4 weeks

[MM3-users] Re: Change Dmark settings via command line

by bob B

No, why do you ask that? If you have even 30 lists and want to make the same change why not do it all at one time instead of individually?

11 months, 2 weeks

[MM3-users] Re: Change Dmark settings via command line

by Odhiambo Washington

On Tue, May 7, 2024 at 10:51 PM bob B via Mailman-users < mailman-users(a)mailman3.org> wrote: > No, why do you ask that? > > > If you have even 30 lists and want to make the same change why not do it > all at one time instead of individually? > Makes sense. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months, 2 weeks

[MM3-users] Re: Trying to save a new style

by Mark Sapiro

On 5/13/24 22:21, Perry Kollmorgen wrote: > > Is there a way to save this style permanently ? What you are doing is fine, but to make it persist you have to create a plugin to do it each time. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… for info and https://gitlab.com/mailman/example-mailman-plugin/-/blob/master/example_mai… for an example. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] bulk deletion of messages from Hyperkitty

by Danil Smirnov

Hi, community! After importing from Mailman 2, thousands of badly compiled messages from the past appeared with empty content on the same date (date of import). Is there a safe way to delete them all? If we delete them from the database - hyperkitty_email table - do we need to do some clean-up of hyperkitty_thread table as well? Any advice? BR, Danil Smirnov

9 months, 1 week

[MM3-users] Strange URL in error message

by waps＠tantalus.jena.thur.de

(Debian 12) I have the problem that the hyperkitty archive is empty. The file /var/log/mailman3/mailman.log show sometimes the message urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.XXXXX-project.demailman3', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa48b43a910>: Failed to establish a new connection: [Errno -2] Name or service not known')) (there is a slash missing between 'project.de' and 'mailman3'). My goal is, of course, to have an running archive. But I think the error message could be a hint about the reason) Do you have an idea what can I do about this?

9 months, 1 week

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

by Roland Giesler

I having a hard time understanding how to create an admin user for postorius (mailman-web). The docs say at https://docs.mailman3.org/en/latest/config-web.html Setting up Admin Account <https://docs.mailman3.org/en/latest/config-web.html#setting-up-admin-account> To create a superuser account in Django, run the following interactive command as|mailman|user: (venv)$ mailman-web createsuperuser However, which user in the mailman user mentioned? I tried to do this as root, but login in as an admin doesn't give me any option to create new lists in postorius. What am I missing / doing wrong? regards Roland

8 months, 3 weeks

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

by Roland Giesler

On 2024/07/30 15:48, Roland Giesler via Mailman-users wrote: > However, which user in the mailman user mentioned? > > I tried to do this as root, but login in as an admin doesn't give me > any option to create new lists in postorius. What am I missing / > doing wrong? > I seem to have solved the riddle. The "mailman-web createsuperuser" command suggest the the mailman user is www-data, which I accepted. That worked and I can now create a new list from Postorius.

8 months, 3 weeks

[MM3-users] Re: New domain cannot set set host

by Mark Sapiro

On 11/27/24 12:18 PM, Alain D D Williams wrote: > > But it is not in table mailman3web.django_site > > Please how do I do this ? Add the domain as a site in the Django web admin UI. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by erik＠dante.de

I stumbled across the same warning, which has been known for at least two years. It can be triggered by the command above. Since Debian Stable still uses version 1.4 of python3-sqlalchemy: Do you know if this warning still happens in a version ≥2.0 of python3-sqlalchemy? Do you know a workaround to generate less noise in the log files without disabling all MariaDB warning messages? We really use the NNTP gateway, turning that off is not an option. Thanks, Erik

4 months, 3 weeks

[MM3-users] Re: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 12/2/24 11:08 PM, erik(a)dante.de wrote: > > Do you know if this warning still happens in a version ≥2.0 of python3-sqlalchemy? This may be https://github.com/sqlalchemy/sqlalchemy/issues/10893 which appears to be fixed in 2.0. > Do you know a workaround to generate less noise in the log files without disabling all MariaDB warning messages? We really use the NNTP gateway, turning that off is not an option. No, but I know nothing about MariaDB. -- 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: Clean-up of non-members

by Mark Sapiro

On December 25, 2024 2:01:27 PM PST, Odhiambo Washington via Mailman-users <mailman-users(a)mailman3.org> wrote: > members --role nonmember LISTSPEC | wc -l > 13 What do you get if you do ``` mailman shell -l LISTSPEC ... >>> len(list(m.nonmembers.members)) ``` -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

3 months, 4 weeks

[MM3-users] Re: Change delivery_status in bulk

by Mark Sapiro

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

2 weeks, 6 days

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

by Mihai Moldovan

* On 4/13/25 17:19, Mark Sapiro wrote: > Do you have a setting for `banner` in the `[shell]` section of your > mailman.cfg? Whoops, yes, I do. Removed it, and the messages appear correctly, of course. It's a downstream packaging bug, the sample config they created only includes the first line: https://git.launchpad.net/ubuntu/+source/mailman3/tree/debian/contrib/mailm… Thanks. Bug report time to Ubuntu it is. Mihai

1 week, 3 days

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

by Abhilash Raj

On Sat, Dec 22, 2018, at 7:01 AM, brian(a)emwd.com wrote: > Hi Mark, > > Merry Christmas (or Happy Holidays!). > > I have the list settings set to Public archives and hyperkitty checked > in the Active archivers box. > > As for the cron jobs. I am not sure how to change the following to > reflect my setup: > > # This goes in /etc/cron.d/mailman > > # Replace "apache" by your webserver user ("www-data" on Debian systems) and > # set the path to the Django project directory > > @hourly apache django-admin runjobs hourly --pythonpath > /path/to/project --settings settings > @daily apache django-admin runjobs daily --pythonpath > /path/to/project --settings settings > @weekly apache django-admin runjobs weekly --pythonpath > /path/to/project --settings settings > @monthly apache django-admin runjobs monthly --pythonpath > /path/to/project --settings settings > @yearly apache django-admin runjobs yearly --pythonpath > /path/to/project --settings settings > * * * * * apache django-admin runjobs minutely --pythonpath > /path/to/project --settings settings > 2,17,32,47 * * * * apache django-admin runjobs quarter_hourly > --pythonpath /path/to/project --settings settings uwsgi handles all the cron jobs in the container images, you don't need to setup anything. See here[1]. [1]: https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/uwsgi… > > For instance, I am using nginx not apache. I also do not know what the > /path/to/project should be using maxking's setup. I also am not sure > how to call django-admin from the command line. I get the following: > > # django-admin > -bash: django-admin: command not found If you do need to run `django-admin` commands, you have to do that inside the container images. So, try this to enter the container: $ docker exec -it mailman-web bash Then to run commands: $ python manage.py <subcommands> -- thanks, Abhilash Raj (maxking)

6 years, 4 months

[MM3-users] Re: non-members issue with held email

by Mark Sapiro

On 7/20/21 2:09 AM, Lars Schimmer wrote: > > We created a new mailinglist, added 3 owner and several members. > Now we want some email addresses to post to that list but not receive > mails from the list. So I added those to the "non-member" area of the > mailinglist and checked every non-member to "acceppt at once". > > But on a test, a email address, which is owner AND non-member, cannot > send to mailinglist, always get a "HOLD: ...... The message is not from > a list member" See https://gitlab.com/mailman/mailman/-/issues/659 If you read through the comment thread, you'll see that the issue is when setting moderation action for an address which is both an owner and a nonmember, it is the owner's action that actually gets set, so that the nonmember's action remains set to list default. You need to set the moderation action for the nonmember via `mailman shell`. If all the non-members are the ones you added, you can do ``` $ mailman shell -l your.list.id Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the ... mailing list >>> for nonmember in m.nonmembers.members: ... nonmember.moderation_action = Action.accept ... >>> commit() ``` If there are other nonmembers whose action you don't want to set to accept, you need to do something like ``` >>> emails = ['first(a)example.com', 'second(a)example.com', <more emails>, ] >>> for nonmember in m.nonmembers.members: ... if nonmember.address.email in emails: ... nonmember.moderation_action = Action.accept ... >>> commit() ``` to only do the ones you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

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

by Abhilash Raj

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 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. 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 --- [logging.smtp] path: smtp.log # The smtp logger defines additional options for handling the logging of each # attempted delivery. These format strings specify what information is logged # for every message, every successful delivery, every refused delivery and # every recipient failure. To disable a status message, set the value to 'no' # (without the quotes). # # These template strings accept the following set of substitution # placeholders, if available. # # msgid -- the Message-ID of the message in question # listname -- the fully-qualified list name # sender -- the sender if available # recip -- the recipient address if available, or the number of # recipients being delivered to # size -- the approximate size of the message in bytes # seconds -- the number of seconds the operation took # refused -- the number of refused recipients # smtpcode -- the SMTP success or failure code # smtpmsg -- the SMTP success or failure message every: $msgid smtp to $listname for $recip recips, completed in $time seconds success: $msgid post to $listname from $sender, $size bytes refused: $msgid post to $listname from $sender, $size bytes, $refused failures failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg --- I'd also recommend looking into MTA logs for anything un-usual. > > I would appreciate any pointers on where to look for the source of the > problem. At the moment, since I can't reliably reproduce it I can't > really test it nor do I know where to look next time things get stuck. > Mailing list in question is high profile thus when event like this > happens I have only limited time amount to spend on > troubleshooting/digging before I just restart the core (which by the way > takes about 45min to fully start... which is another puzzle to solve at How do you measure that it takes 45 mins to start? What database backend are you using? > later time) > > -- > Sr System and DevOps Engineer SoM IRT > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > *Attachments:* > * signature.asc -- thanks, Abhilash Raj (maxking)

6 years, 1 month

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

by Stephen J. Turnbull

Andreas Vetter writes: > A list of all addresses subscribed to all lists owned by the logged > in person. This is starting to take a better form. It's still very specialized, so I'm starting to wonder if trying to add it to Postorius is a great idea. Of course if people are coming in over the network, you don't want to reproduce all the authentication and authorization logic implemented in Django and Postorius. That may as well be done in Django, and if you're doing Django it may as well be Postorius too. But if you're in a single sign-on environment so presence in the network implies strong authentication, you will get more flexibility from local scripts using mailmanclient, or if you're confident in security access to the REST API directly. Just putting that out for your consideration, since implementing what is taking shape here would take quite some time as the folks skilled with Postorius are not so active these days. > Owner is the primary target group for that. But since it should be > a tool for managing subscriptions in a simple way, it might also be > of interest for superusers. For me as a superuser it would make > life easier. [...] > Ah, I see the problem and agree: So, the presentation should have a > sorted and searchable list of addresses and a Button next to each > address, maybe labeled "Subscriptions". Looking at your description above, for superusers that is basically the Users tab, though. Users are identified by primary address, and you'd not see alternate addresses in the list. But presumably your internal users use their @your.org addresses as primary. Can you make clear what could be more streamlined for your use cases as superuser? I give one example below, maybe that's what you're mostly interested in. The caveats about access to User objects still apply for owners, so even if they look the same (which is a good UX idea if owner functionality is a subset of superuser functionality, also they might even be able to share the basic page templates), the implementation is going to be rather different. I suspect you superusers would be quite frustrated if using the "subscribe all these lists" functionality meant you couldn't get at the User object without going to a different page. I do see one weird thing: you can't manipulate subscription itself from the User page as seen by the superuser from that list, only toggle moderation and delivery mode. I guess that's reasonable for a lot of use cases, though. I've never wanted to do a subscribe or unsubscribe from there. I always have a long list of users to subscribe to specific lists, never a list of lists a specific user should belong to, > The presentation given when above "Subscriptions" Button is clicked > should contain the address as kind of Headline. Then a table of > all lists of the logged in owner and next to each mailing list an > indication, if the address is subscribed or not and a Button to > toggle subscription/unsubscription. May be a single Toggle Button > or (maybe better) two buttons, a suscribe and a unsubscribe button, > where one is greyed out. This would not work with the current User page as presented to a superuser, that's true. The current presentation is quite suited to its purpose, with sections for Addresses, Subscriptions, Ownership, and Delete User in that order. But especially for superusers, there are plenty of sites with thousands, even tens of thousands of lists, and even a paged or scrollable presentation would be awful UI, and the potential for a disastrous mistake using "do all" is high. > In addition my owners would like to have a "unsubscribe from all my > lists" button. And a "subscribe to all my lists" button. This might > be visually nicer, when having the two-button approach above. I wonder if your owners really want "subscribe all". "Unsubscribe all" does make sense for separations, of course, and they wouldn't necessarily be terminations. It would be useful in an internal transfer where "delete user" is not a solution. But in my experience specialized channels tend to proliferate but the same people are likely to be running them as run the department-wide lisst. > In our case we would want to (un-)subscribe the address in a "do > it, don't ask anyone" fashion, but maybe this is not a good idea in > general. What do you think? I think we would implement it similarly to the mass subscribe for multiple addresses case, where the list owner can decide how much bureaucracy to require of the subscriber. You'd want to be careful to make sure address verification is done at most once (for your use case, probably not at all). And there would be some things that could be done to arrange that most lists would have sensible defaults. > Yes, I agree, but policy here is to get rid of subdomains, and that > falls on our feet now. Well, once we figure out how to implement domain ownership, it wouldn't be hard to adapt that technology to "departments" that are administratively distinct but share mail and/or web domains. The main problem would be deciding whether and how to nest them. Superuser > domain owner > list owner > moderator is pretty obvious, but how "department owner" would fit in is less so.

1 month, 1 week

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 16:44 -0800, Mark Sapiro escribió: > On 2/13/21 4:08 PM, Victoriano Giralt wrote: > > Mark, please, how do you check when translations happened? Nov 7th is a > > very significant date for me (it is my wedding anniversary) and I'm 90% > > sure that I dedicated time to Weblate after that date... > > With respect to Mailman core, all I'm doing is downloading the .po for > Spanish and comparing it to mailman/messages/es/LC_MESSAGES/mailman.po > from the Mailman core 3.3.3 package on PyPI and they are identical. > > If there are translated strings on weblate that are different from that, > they don't show up in the downloaded > <https://hosted.weblate.org/download/gnu-mailman/mailman/es/>;. And you are very right and I have fallen as a newbee ... and first of all I apologise for the noise. I've been doing diffs with files downloaded from Weblate and those installed on the server by pip. As I should have done from the start. Mailman core and hyperkitty show no differences. Postorius shows a bunch and django_mailman3 just a couple. I leave for others a more detailed check of the strings between downloaded .po files and Weblate online strings, it's too late here. > > And I too want to help. It would be a help to me if you can give me > examples of specific strings whose weblate translation differs from > what's in the distributed .po files. And you have helped me, making me thing twice and stop moaning and going for the facts. Apologetic-thankful-big-mouth-shut-ly, Victoriano. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Ok, I'll install whoosh on env2 Thanks 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

7 years, 9 months

[MM3-users] Re: MM3 generates long lines?

by Mark Sapiro

On 6/23/21 7:45 AM, Andreas Barth wrote: > > Thanks Mark, that's what I did. After the restart I needed to activate > it on a per-list basis. > > However, I'd prefer to be able to do that on global basis. Not a big > issue, but still thought it worth asking. You can do it with a `mailman shell` script. Something like ``` >>> for mlist in getUtility(IListManager).mailing_lists: ... for archiver in IListArchiverSet(mlist).archivers: ... if archiver.name == 'prototype': ... archiver.is_enabled = True ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

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

by Mark Sapiro

On 9/18/24 09:35, Steve Brown via Mailman-users wrote: > > Yes, that is what is happening, but only for messages from the steve@stevebrown address. I can send a screenshot and a .txt of the headers (of the message after sent back to me from MM3 and long!) but didn't see a way to do that on the archive page. Do I need to post from my gmail address? The usual behavior of most MUAs (mail clients) is to set the envelope sender to the same address as From:. In that case, you won't see an issue like this. In your case, when you send via tmdhosting servers, they set that odd bounce+... address as the envelope sender, presumably so they can do something in processing DSNs returned to that address. If you post the full headers of such a message from the list, either inline or as a .txt attachment, I'll look and say what I can. As far as getting headers from HyperKitty is concerned, if you click on a thread containing the message, there is a Download button which will produce a gzipped mbox containing the message(s) in that thread, but the headers are very minimal - only From:, To:, Subject:, Date:, Message-ID:, MIME-Version: and Content-Type:. There is also a From_ separator, but it contains the From: address, not the true envelope sender. > One clue I hadn't spotted before was a bodyhash_mismatch warning in the headers. No idea where that came from. Doesn't appear in emails from me to other addresses. Is that in Authentication-Results:? It is probably saying an original DKIM signature fails to verify because of a body mismatch which is expected if Mailman has filtered any MIME parts or added a message header or footer. -- 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: Member Issue Discovered

by Stephen J. Turnbull

Brian Carpenter writes: > If you mean if they don't have a Django user account, they can't > unsubscribe? The Django user account is more or less a proxy for the underlying Mailman User object, which is what we're concerned with here because that's where the data you want deleted is stored. > I think that is true if they are wanting to unsubscribe via > the web interface. But sending an email to > listname-unsubscribe@listdomain allows them to unsubscribe without such > user authentication. Isn't that correct? They don't need a Django password or social auth, but they'll still have to do the OTK dance. I don't see a reason to distinguish the methods of authentication. They all reduce to the OTK dance to prove ownership of a mailbox, then optional *delegation* to a password in Django or social auth via Gmail etc. I understand that your users don't understand this or care to. Thing is, some of *our* users care about the features that this architecture enables. > My intent in our changes is to give the list owner and member > exactly what they expect: when they explicitly remove a > subscription and/or user profile, that they expect their data to be > totally removed. That's fine, and you're welcome to implement that in Affinity. In fact, as I understand it, you have already done so. *I'm* not saying *nobody* should implement that. I'm saying that *Mailman* shouldn't, because a lot of subscribers to Mailman lists won't like it. The whole point of Mailman 3 is to cater to users who want powerful control over their subscriptions. For Mailman (Postorius), prompting the user "If you delete this subscription, you will have no subscriptions linked to this account. Would you like to delete the account as well?" (as I have proposed three times now) is the right way to go. This can be implemented via email with a second OTK. > I can easily picture a scenario where an older list has a number of > list members move to on to other things in life And I can picture a scenario where they take a summer break and reactivate a decade later. I would be *pissed off* if my data got deleted in that scenario. (Yes, I've done that in the five year variant, if not the full decade.) > and even abandon their email accounts totally. Which is a totally different scenario. I deny your "imperative" in the former case; inactivity from the point of view of a list owner is (usually) not abandonment. I question it in the latter, because "abandon" is an inference drawn from lack of activity or bounces, either of which could be inadvertant (respectively the "summer break" scenario, and separation from an employer). > In those cases it is imperative that those list addresses are > removed either via bounce processing or list owner intervention and > that no legacy data on such members remain. But how do you propose to identify "legacy data"? In Mailman 3, members are *people*, not addresses. Do you really want it to be the case that if Albert signs up with albert(a)example.com, and later gets fired by example.com, then all his subscriptions get bounce-cancelled, and his User profile gets irreversibly trashed? Or some large email provider hosting lots of posters decides to suddenly implement some spam protection that causes a ton of bounces (as DMARC p=reject did in 2014) and hundreds of users have their accounts trashed? You just can't know without asking Albert what he wants done in his case and you can be quite sure you're doing the wrong thing in the DMARC-like case. In either case, resubscribing is a click per list if his data is retained (and Albert needs an OTK confirmation of another address). It's an annoying session of duplicating his configuration (including passwords and social auth links) if not, and probably some months of discovering that a configuration that built up over years wasn't accurately reproduced for some lists. List owners, of course, can do what they want with their lists. If they want to add automation for their subscribers that simplify the lives of people who have simple needs, that's not something Mailman can, should, or will try to stop. That's *why* I support efforts like Affinity, Empathy, and Harmony. Steve

4 years, 5 months

[MM3-users] Advice on migrating to Mailman 3

by Christoph Groth

Dear Mailman 3 users, Currently we are hosting the website [1] and mailing list [2] of our free software project with a shared hosting plan of a webhosting company. As such there is no dedicated server, but we do have SSH access (as a regular user) to the shared server. The mailing list software (Mailman 2) is administrated separately by our hoster on a dedicated machine. We are rather happy with this setup: we pay about 10 USD per month and have only little administration work to do. 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? 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. 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] 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. Thanks Christoph [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/…

5 years, 2 months

[MM3-users] Templates

by David Krantz

Hi. How do I set a template for one specific list? I want one list to have a special footer template. I have tried updating the database (template table) without effect so apparently the database is not used for templates or some kind of fallback is used to set it to the generic footer. Of course I also tried to restart mailman after that operation to try to rule out any caching-related problem. I want to use a file://-path as that is the least painful way of doing it. I also would like a solution to place a file in a special location. My current templates are in a .../var/templates/site/en/ structure with names like list:member:generic:footer.txt Cheers // David

7 years, 7 months

[MM3-users] Re: Bounces

by Mark Sapiro

On 11/05/2017 01:16 PM, David Krantz wrote: > > How do I config mailman 3.1x to send any unrecognized bounces to e.g. > the list owner? Now they just end up in the bounces table but I would > like to see the entire message in this case. The short answer is you can't. See <https://gitlab.com/mailman/mailman/issues/343>. The bottom line is we aren't doing anything with bounces other than storing them. We need to fix that, and we will (It's targeted for 3.2). If you could help with code, that would be great. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: Broken web interface Ubuntu 20.04

by Mark Sapiro

On 9/30/21 2:30 PM, tim(a)thecutts.org wrote: > > When I look at the mailman-web-logs, the urls that postorious puts into the page don't honour the POSTORIOUS_TEMPLATE_BASE_URL variable in the mailman-web.py file any more. I'm not saying there isn't an issue in Postorius, but I don't think it has anything to do with POSTORIUS_TEMPLATE_BASE_URL which is only used for templates and has nothing to do with the rendering of the list pages and shouldn't contain anything beyond the host and port in any case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] An archive/read-only list on a full setup?

by Andreas Schamanek

I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly. After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc. What's the proper way to set up a hyperkitty-only list? -- -- Andreas :-)

2 years

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

by Michael Bakonyi

Dear Stephen, 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. Cheers, Michael > Am 24.08.2022/ 34 um 14:27 schrieb Stephen J. Turnbull <stephenjturnbull(a)gmail.com>: > > kontakt(a)michaelbakonyi.de writes: > >> I have the same usecase as Krešimir and tried the example of >> Mark. So in mailman.cfg I set hostname to >> "https://lists.mydomain.org" and then fire this command > > I don't recall this, and unfortunately Mark is on vacation and > completely offline until mid-September, except for maybe a couple days > next week. > >> curl -urestadmin:mypw --referer https://lists.mydomain.org --request POST -H 'Content-Type: application/json' --data-binary '{"list_id": "thelist.lists.mydomain.org", "subscriber": "user(a)example.net", "display_name": "Joe User", "pre_verified": true, "pre_confirmed": true, "pre_approved": true}' https://lists.mydomain.org/mailman3/postorius/lists/thelist.lists.mydomain.… >> >> But then I get a CSRF-warning. Do I now have to get the token and >> put it in my POST or is there an easier way to do this? > > As far as *I* know there's no way to avoid the CSRF warning. If that > means you can't get the response data you need, you will have to do > the CSRF two-step. > > With luck maybe Mark will see this in a few days but I think he's > going to be busy preparing the 2d half of his trip. > > Regards, > Steve >

2 years, 7 months

[MM3-users] Re: Problem with languages

by Andreas Barth

* Jens Günther (jens.guenther(a)posteo.de) [210319 15:29]: > But for some reason I do have a mixed setup in languages now. Some > strings are in English, some are in German. The settings I changed > are: which package version do you use? Actually I would recommend using the packages from bullseye for mailman3. This should work with e.g. some pinning. (I'm thinking if we should try to get mailman3 into stable-backports, because that might be actually useful.) Also, translations had been the reason for some discussions lately, so this is still some work-in-progress. (Also on the git version I'm using, there are more texts in English than I'd wish for.) Andi

4 years, 1 month

[MM3-users] How to list all nonmembers from a list?

by Jens Günther

Hey there, I wanted to list all nonmembers from a list, I just can't find an easy way to do it. For listing members of a list it is quite clear: mailman members $mylist Is there a similar way for nonmembers!? Actually I'm pretty sure, that one can do it with the shell and I found some documentation on that. But I'm kind of a noob in these things and already tried a little around, but can't get anything to work: dump_members(mlist.nonmembers.members) from https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… Help qould be highly appreciated, thanks in advance! Jens.

2 years

[MM3-users] Re: External MTA incoming mail: configuration

by Roland Giesler

On 2024/08/02 19:02, Mark Sapiro wrote: > On 8/2/24 09:43, Roland Giesler via Mailman-users wrote: > >> Ah, so I just have to figure out why the LMTP runner is not running. > > Stop Mailman core and then start it. You must stop and then start as > opposed to restart. > > If lmtp runner is not running after that check > /var/log/mailman3/mailman.log for possible reasons. You can also check > that log for reasons why it isn't currently running. > > You can also check /var/log/syslog* for events like out_of_memory that > might have killed it. I do now have the lmtp runner on port 8024. # netstat -tunap | grep 8024 tcp 0 0 192.168.161.103:8024 0.0.0.0:* LISTEN 46730/python3 In mailman.cfg I set it to listen on the LAN address instead of 172.0.0.1, since I'm expecting mails from my external MTA server. In the logs of the MTA I see this however: warning: do not list domain fast.za.net in BOTH virtual_mailbox_domains and relay_domains Mailman creates these entries, but postfix doesn't like it. I don't see any mail delivered to the mailman yet. Is this the problem? In the MTA postfix main.cf: relay_domains = hash:/etc/mailman3/data/postfix_domains cat /etc/mailman3/data/postfix_domains # AUTOMATICALLY GENERATED BY MAILMAN ON 2024-08-05 07:20:17 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. fast.za.net fast.za.net and also local_recipient_maps=$virtual_mailbox_maps, hash:/etc/mailman3/data/postfix_lmtp cat /etc/mailman3/data/postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2024-08-05 07:20:17 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Aliases which are visible only in the @fast.za.net domain. test(a)fast.za.net lmtp:[192.168.161.103]:8024 test-bounces(a)fast.za.net lmtp:[192.168.161.103]:8024 test-confirm(a)fast.za.net lmtp:[192.168.161.103]:8024 test-join(a)fast.za.net lmtp:[192.168.161.103]:8024 test-leave(a)fast.za.net lmtp:[192.168.161.103]:8024 test-owner(a)fast.za.net lmtp:[192.168.161.103]:8024 test-request(a)fast.za.net lmtp:[192.168.161.103]:8024 test-subscribe(a)fast.za.net lmtp:[192.168.161.103]:8024 test-unsubscribe(a)fast.za.net lmtp:[192.168.161.103]:8024 Then there's: virtual_mailbox_domains=sqlite:/etc/postfix/virtual-mailbox-domains.cf cat /etc/postfix/virtual-mailbox-domains.cf dbpath=/home/user-data/mail/users.sqlite query = SELECT 1 FROM users WHERE email LIKE '%%@%s' UNION SELECT 1 FROM aliases WHERE source LIKE '%%@%s' UNION SELECT 1 FROM auto_aliases WHERE source LIKE '%%@%s' When I run that query in sqlite3, it returns no records, so I'm not sure how this is supposed to work. %s to me means that first argument, so is this used in python and then %s is the argument sent to this query? The bottom line of this all is that a new signup message that I reply to is being received by box2.gtahardware,co.za, but not by mailman3 and I cannot find the point where it fails in the logs.

8 months, 2 weeks

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

by Bjoern Franke

Hi, > > Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. you could throw away all the distro packages and install all things via PIP. But set [mta] verp_probes: yes because after 3.3.1 bounces are processed now. Kind Regards Bjoern

3 years, 10 months

[MM3-users] Re: Mailman 3 Installation

by Andreas Barth

* Mark Dadgar (mark(a)pdc-racing.net) [210117 19:59]: > Do not "just start with sqlite to get it running and then I’ll > migrate it to something else down the road.” There is currently no > validated way to migrate a mailman3 instance from sqlite to > something else, and by “no validated way” what I actually mean is > “no one has managed to get this to work, me included.” I need to disagree to the last part of the sentence because I did it, but my strong recommendation based on expirence is: save the effort, start directly with postgresql. It's not much more work, and migrating is .. well, just don't try or do it. Andi

4 years, 3 months

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

by Johannes Rohr

Am 10.01.23 um 00:53 schrieb Mark Sapiro: > I recognize it's a significant regression for some, but we are a > small, all volunteer project and can't do everything. A well crafted > merge request would certainly be accepted. You are doing incredibly valuable work, and I sincerely apologize for being a total layman who just whines and doesn't have the skills to contribute any code! I could only explore options for organising a bounty on this. But I have no idea what amount of funding would be required realistically, or I could start nagging other Mailman users who have python skills. Cheers, Johannes

2 years, 3 months

[MM3-users] Re: Trying to get mailman3 in docker working with external Mysql database

by matthew＠alberti.us

Bob, For mailman-core, I use this: environment: - DATABASE_URL=mysql+pymysql://mailman:[realstrongpassword]@database/mailmandb ?charset=utf8mb4&use_unicode=1 - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase - HYPERKITTY_API_KEY=[realstrongkey] - MTA=postfix For mailman-web, I use this: environment: - DATABASE_URL=mysql://mailman:[realstrongpassword]@database/mailmandb - DATABASE_TYPE=mysql Pymysql should be installed in the container(s) via the image. You shouldn't have to do it. If your environment variables are complete and correct in docker-compose.yaml, you should have to interactively configure anything within either container. It is all done at creation/boot time. You might want to run "docker logs mailman-core" after starting the container. Just to see what it is saying about the database connection. In my case, it wasn't working, due to an invalid character in the password. You'd never know unless you look at those logs. -----Original Message----- From: bob B <bader(a)cchmc.org> Sent: Saturday, October 9, 2021 1:45 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Trying to get mailman3 in docker working with external Mysql database Our database group has created the database with (charset=utf8mb4&use_unicode=1) and a user For my docker-compose.yaml I will only have two container sections mailman-core mailman-web which should have these database variables set under each: -DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database. server.ip]:[databseport]/[database_name] - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase Are these all correct? in looking at documentation should it be: DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.s erver.ip]:[databseport]/[database_name]?charset=utf8mb4&use_unicode=1 Or/and should I also use? DATABASE_URL=mysql+pymysql://.... or DATABASE_URL=mysql://... or DATABASE_URL=pymysql://.... Do I have to install pymysql? or is it installed in the dock images? Do I have to run any other commands on the database first? I assume mailman does everything it needs for the database at first launch? _______________________________________________ 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, 6 months

[MM3-users] Re: mailman services under systemd

by Mark Sapiro

On 11/22/20 2:13 PM, Morris Jones wrote: > First post, I'm building a new mail server as my tired old server can > no longer meet security requirements. (It's long overdue.) > I see where Torge Riedel is running the mailman service under systemd, > but I'm having trouble doing that. I don't see a mailman option that > doesn't detach as a daemon. > Did I miss something? Anyone have a systemd service example I might > pilfer? <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, 5 months

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

by David Partain

Hi Gordon (and Mark)! I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } } and restarted stuff, but I cannot tell that it has changed anything. Do I need to do something with the database itself (which is somewhat outside my comfort zone...) to make this work? Thanks very much for any advice you may have. Cheers, David

4 years, 2 months

[MM3-users] Re: Python is updated

by Odhiambo Washington

On Thu, Apr 27, 2023 at 8:40 PM Lars Bjørndal <lars(a)lamasti.net> wrote: > Hi, list! > > As the machine I'm running Mailman on now is upgraded from Fedora 36 to > 37, the Python version is upgraded from 3.10 to 3.11. How do I update > Mailman in the virutal environment? You cannot do that, IIRC. If you need to upgrade, you create a new virtualenv based on the new Python version, then you migrate your configs and data. Did your Mailman stop functioning? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 11 months

[MM3-users] list admin via email

by Christian Stalberg

I'm unclear on how to approve via email a message sent to a list. As list owner you receive a 'requires approval' email. It then says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." Question: if I want to approve the message, where do I "...include an Approved: header with the list password in it" ? TY!

3 years, 5 months

[MM3-users] Re: Whitelist non subscriber

by Stephan Krinetzki

Hello, sorry to post to an old thread, but we have now the same problem with Mailman 3.1. We need this feature because some of our users have used the whitelists very intensively. As far as I understood it, there is currently no way to set this setting via the web interface, so I want to know how to do it via the Admin API. The steps are as follows, right? - Add users to the list and give the role "nonmember" - Set moderation action ('defer' or 'accept') The only thing missing in the documentation is a note on how to do this via the Admin API. Who can explain that to me? Translated with www.DeepL.com/Translator

6 years, 8 months

[MM3-users] Re: ARC

by Marvin Gülker

Am 12. August 2019 um 23:49 Uhr +0200 schrieb David Krantz: > Is the documentation correct that ARC should be as simple to configure > in mailman 3 as to add the private DKIM key and restarting mailman? Do any large e-mail providers actually support ARC? Smaller ones like Fastmail appearently do at least semi-manually[1], but what about the relevant ones -- GMail, Microsoft, Yahoo (and in Germany, GMX et al.)? I infer from the spare results of searching for "ARC suport" that even with a perfectly set-up ARC infrastructure, the large e-mail providers are still going to reject DMARC-protected mailing list e-mail, because they simply don't support ARC. [1]: https://www.fastmail.com/help/technical/senderauthentication.html -- Blog: https://mg.guelker.eu

5 years, 8 months

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

by Barry Warsaw

Thanks for doing the testing Florian. Btw I fixed the venv problem. It was actually a bug in one of the dependencies. I have another small branch to land before spinning the beta but I think the MySQL docker image on ci is having some problems. I can't double check ATM. Sent from my digital lollipop. > On Dec 3, 2016, at 15:22, Florian Fuchs <f(a)florianfuchs.com> wrote: > >> On Fri, Dec 02, 2016 at 11:07:24AM -0500, Barry Warsaw wrote: >> Hello Mailman 3 users and developers! >> >> It's been a long slog but I think we are finally ready to begin the release >> process for Mailman 3.1. I am pretty happy about the state of the Core, and >> Florian is going to do some more integration testing with HyperKitty and >> Postorius. We still have a few issues and a merge proposal or two to address, > > I did some manual integration testing today > (core+mailmanclient+postorius) which looked fine so far. I didn't get > to test HyperKitty and the bundler though, so any help testing those > would be very much appreciated. I will have some more time tomorrow. > > I did all of my testing locally, which has some limitations. So I > started setting up a more realistic environment on one of my dev > machines. But I'm not done yet. Will report back when I'm done... ;-) > >> but I am planning to spin a beta of Core this weekend to facilitate testing. > > I think it's OK to put out a separate beta of the core, because the > version pulled from pypi will still be 3.0 if I'm not terribly mistaken. > > For the real 3.1 we should probably do a coordinated release of all > components, once everything's tested a little more thoroughly. > > Cheers > Florian

8 years, 4 months

[MM3-users] Re: Archives with encoding characters

by Seth Seeger

> On Mar 4, 2020, at 1:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > 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. How do I find the raw digest message? Do you mean asking the member to View Raw Message, and then copy and paste that to me? Seth

5 years, 1 month

[MM3-users] Re: No recent activity discussions and activity overview shown. Only a spinning wheel.

by Freerk bosscha

Thank you for your reply. I Will try to get iT up and running the way I want > Op 30 jan 2025 om 15:58 heeft Stephen J. Turnbull <turnbull(a)sk.tsukuba.ac.jp> het volgende geschreven: > > Freerk Bosscha via Mailman-users writes: > >> I have recently setup a fresh mailman3 installation on my debian12 >> box. > > If this is a Debian package, you should report to them. Debian > maintainers make the patches they think are wise, and often go well > beyond conformance to Debian policy on file locations and the like. > Also, while MySQL is a supported backend database, and the main > problem I know of seems to be addressed with the > "?charset=utf8mb4&use_unicode=1" parameters in the db url, I believe > the developers mostly run PostgreSQL. So if there is a database > communication issue, the Debian developers may be more aware of it. > >> In my opinion this should be ok and the qcluster is running > > I don't know what you meant by "looks like an AJAX problem" -- if you > have specific knowledge of such problems, please enlighten us, but > otherwise it is very unhelpful to guess. > > Also, what do you mean by "the archive files are getting the archived > messages"? If you know what you're doing you may be able to find > archived messages in your RDBMS, but in principle HyperKitty just > stores them as blobs in the RDMBS -- HyperKitty doesn't see them as > files. > > Now, what Sam is pointing out suggests that qcluster is not talking to > qinfo, and therefore it may not be talking to HyperKitty. Since > queues are implemented as files on disk, it's likely that qinfo is > counting them using filesytem utilities, while it's talking to > qcluster over a socket. Anyway, I don't think the "clusters 0, > workers 0" report is good news. Also, I believe the "successful" > queue is a measure of backlog. I've seen backlogs of that size on a > site with thousands of archived lists and hundreds of thousands of > posts per day, but I don't think it's normal for typical scales. I > have seen it take many minutes for the recent activity to show up in > HyperKitty on that huge site. I don't recall what the problem was, > maybe something to do with a backlog in the full-text indexer (Xapian > on that site). Unfortunately I don't recall how that was resolved, > and don't have access to that system any more. > > In general, IIRC, qcluster is a red herring for the activity display. > It's used to manage the incoming queue from Mailman core for the > archive but I don't think it's relevant to fetching data. HyperKitty > fetches that directly from the database. I would guess that the issue > has to do with communication between HyperKitty and the database. > > Steve > >

2 months, 3 weeks

[MM3-users] Re: how do I bulk-remove users from ML in MM3? [SOLVED]

by Dmitry Makovey

On 10/25/2017 12:08 AM, Dmitry Makovey wrote: > > I just realized that "mailman members" only offers to "add members" via > "-a filename" but I see no remove option. I've created an (ugly) implementation of what I needed: https://gitlab.med.stanford.edu/irt-public/mailman-tools tools are built mostly to deal with docker deployment, but don't have to be that way) sync_users.py will take anything from stdin and synchronize member list received on stdin with member list in MM adding/removing users. This should reduce number of calls and execution times. -- Sr System and DevOps Engineer SoM IRT

7 years, 5 months

[MM3-users] Re: Postorius not HTML-decoding < to "<" characters

by Mark Sapiro

On 11/9/24 12:24, Ron / BCLUG wrote: > > Hopefully I've assigned the blame to Postorius accurately and no > formatting nor archiving issues make the issue difficult to understand. This is a HyperKitty issue. Postorius has nothing to do with archiving. Also, it depends on the archive rendering mode and only occurs if the mode is Markdown text rather than Plain text. It is really `mistune`, <https://mistune.lepture.com/en/latest/index.html>, which is doing the markdown rendering and which `escapes` HTML tags. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: changing mail footer

by Simon Hanna

On 10/26/2017 07:51 PM, Dmitry Makovey wrote: > Where and how can I set a footer of the message to include link to > mailing list subsciptio/admin pages to simulate MM2 behavior? You can overwrite a template to do that. You can refer to this issue on how to do that https://gitlab.com/mailman/mailman/issues/426 You can browse the default templates in mailman here https://gitlab.com/mailman/mailman/tree/master/src/mailman/templates/en Below is the default footer template ❯ cat list:member:generic:footer.txt _______________________________________________ $display_name mailing list -- $listname To unsubscribe send an email to ${short_listname}-leave@${domain} You overwrite it by placing a file using the same name as a template in one of the directories mentioned in the issue

7 years, 5 months

[MM3-users] Re: Do not send email "The results of your email commands"

by Hagen Bauer

I could only fix this on the postfix level main.cf: header_checks = regexp:/etc/postfix/header_checks more header_checks /^Subject:.The results of your email commands*/ DISCARD On 07.12.18 15:21, erlonmz(a)hotmail.com wrote: > Hello guys. > > Have to configure the mailman3 for not to send the e-mail " The results of your email commands" when an email is sent to "-leave@" and "-join@" ?? > > Sorry for my English, i from another country. > _______________________________________________ > 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, 4 months

[MM3-users] Re: Changing subscription address

by Mark Sapiro

On 3/15/21 4:16 PM, Allan Hansen wrote: > > Will I now have to tell her to do this for each list she is subscribed to: If you have shell access to the server, you can do this: ``` $ /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> um = getUtility(IUserManager) >>> adr = um.get_address('old(a)examople.com') >>> adr.email = 'new(a)example.net' >>> commit() ``` -- 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: at the finish line of mailman3 docker, but can't sign in.

by bob B

So if I want to start fresh (or resetup my environment and database etc...) how do I do that. I assume I 1. docker-compose down 2. backup these files /opt/mailman/core/mailman-extra.cfg /opt/mailman/web/settings_local.py /opt/mailman/core/mailman-extra.cfg /etc/nginx/conf.d/* /docker-mailman/docker-compose.yaml 3. Delete contents of /opt/mailman/core /opt/mailman/web /opt/mailman/database 4. replace these backed up files ( or edited version with config changes ) /opt/mailman/core/mailman-extra.cfg /opt/mailman/web/settings_local.py /opt/mailman/core/mailman-extra.cfg 5. Then run docker-compose up -d Will that basically let me start fresh and recreate the database and database admin?

3 years, 8 months

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

by kontakt＠michaelbakonyi.de

Hey everyone, I have the same usecase as Krešimir and tried the example of Mark. So in mailman.cfg I set hostname to "https://lists.mydomain.org" and then fire this command curl -urestadmin:mypw --referer https://lists.mydomain.org --request POST -H 'Content-Type: application/json' --data-binary '{"list_id": "thelist.lists.mydomain.org", "subscriber": "user(a)example.net", "display_name": "Joe User", "pre_verified": true, "pre_confirmed": true, "pre_approved": true}' https://lists.mydomain.org/mailman3/postorius/lists/thelist.lists.mydomain.… But then I get a CSRF-warning. Do I now have to get the token and put it in my POST or is there an easier way to do this? cheers, Michael

2 years, 8 months

[MM3-users] Message does not appear in archive

by paul＠arenson.org

Well, I have looked here to see my previous post (and to check how the archives look), but i do not see the below. post. Am I missing something. ARCHIVE I SEARCHED https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> The thread: Re: [MM3-users] Using as a forum Can someone advise? Thank you > On Aug 30, 2018, at 11:18, tokyoprogressive(a)mailbox.org <paul(a)arenson.org> wrote: > > > Our group of 30 plus people have the perennial problem in MM II of not checking previous messages before replying. > > A second problem is starting a new topic rather than responding to a message in the same topic, which makes searching even harder. > > I previously suggested a forum or something like Stack or Flock. People had no interest in a Word Press forum yet moan about the inefficiency of a list, also it is something new and involves leaving email. Stack and Flock make it hard to require all to be a member of all topics in their free versions. > > Then it occurred to me, the threaded view in Mailman III looks good and could help us nudge people back on topic. > > Am I being too optimistic. > > It is a closed group only open to people we approve. > > I would like to migrate to MM III but lack the technical skills to fo this? Anyone who could do this for a fee? > > We probably do not need to bring in the old topics. (I guess there us no way like a forum to limit the topics but at least we could keep things on track). > > Thanks > > Paul Arenson > Japan Association for Language Teaching > > > > Sent from my iPhone > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 7 months

[MM3-users] Re: getting all registered users and their lists

by Mark Sapiro

On 1/26/22 00:16, IOhannes m zmoelnig wrote: > > hi, > > TL;DR > is there a scriptable way to get all users that have registered in my > mailman3 (3.2.1) instance and which lists they are subscribed to (if any)? It's in Postorius >= 1.3.6 > longer version: > > we are running Mailman3-3.2.1 as shipped with Debian/buster (i know that > this is not the newest version; at this point, please refrain from > asking me to upgrade my Debian installation or even to switch to a venv > installation of mailman3: i'll eventually do that but right now i've gt > a problem to solve :-)) See above. ... > for this i would like to get a listing of all users that are not > subscribed to any mailinglist. > i would also like to query, when a given user has signed up (so i can > reduce the number of false positives) > > how would i do that? > ideally i would rather not work on an SQL level. You can do this in mailman shell ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` Or to skip older ones ``` >>> from datetime import datetime >>> um = getUtility(IUserManager) >>> for usr in um.users: ... if len(list(usr.memberships.members)) > 0: ... continue ... if usr.created_on < datetime(2022, 1, 1): ... continue ... adr = usr.addresses[0] ... print(f'Name: {adr.display_name}, Email: {adr.email}, Created: {usr.created_on}') ... ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Hacking attempts?

by Stephen J. Turnbull

Lists via Mailman-users writes: > We are seeing thousands of these emails every day, looks like > someone is trying to hack our Mailman3 but would appreciate someone > with more knowledge of MM3 to confirm. Who is "we"? Specifically, do you have something to do with the Fedora Project (Linux distribution)? To be honest, this looks to me more like collateral damage from a web crawler than a hacking attempt. It's a real service offered by your server (unlike a lot of the bogus requests I see). More below. > Is this a problem with our setup? i.e. the “Internal Server Error” > bit, or are the hackers just sending bad data that is causing the > error? I don't think this is a Mailman message, but from Django, or perhaps the 'django_mailman3.lib.auth.fedora' application (not sure whether that's our code, despite the name it's probably calling into code we borrow from Fedora). I'll look into an upstream bug report if this isn't in our code. > also how do we stop/block this? 1. Put that URL in robots.txt to keep honest crawlers out (see analysis of example report below). 2. Firewall bad bots and script kiddies. That's what I do, anyway. 3. Also, if you aren't associated with the Fedora project, you might want to disable the Fedora social auth login (remove it from the installed applications in settings.py). You should be careful about that, because there's a chance some of your users depend on it. I'm surprised at the "thousands" part. I'd have to see a sample of 10 or 20, and know something about your site, to judge whether *you* are under attack, or if it's just a bunch of low-tech crawleres and kiddies. I see up to a couple hundred a day, with most being attempts to access actual resources via the IP address rather than the domain. Over a couple of years I've banned 772 separate IP addresses (maybe a dozen are netblocks, mostly /24s, but a couple of /16s). I suppose that cuts down the number I see by quite a bit. > Subject: [Django] ERROR (EXTERNAL IP): > Internal Server Error: /mailman3/accounts/fedora/login/ > > Internal Server Error: /mailman3/accounts/fedora/login/ > > TypeError at /accounts/fedora/login/ > _openid_consumer() missing 2 required positional arguments: > 'provider' and 'endpoint' > Request URL: https://mailman.ardc.net/mailman3/accounts/fedora/login/?process=login&next… This looks like somebody tried to access the "44net" mailing list archive, maybe legitimately but for some reason didn't provide credentials. This could be script kiddies or perhaps somewhat clumsy reconnaissance to see what social auth you support (although they're usually more secure than passwords). However, REMOTE_ADDR = '157.90.177.212' resolves to 212.177.90.157.in-addr.arpa domain name pointer ninja-crawler64.webmeup.com., which looks like a legitimate but naive web crawler to me. That would explain why they hit the right address (they got the login URL from your top page, and then the provide credentials URL from the login page, and then the submit button). They were just hitting every URL they could parse. > Traceback: Nothing unexpected there, or in the rest of the diagnostic information. Steve

2 years, 9 months

[MM3-users] Re: Enable delivery

by Hirayama, Pat

Apologies, I should've said my "Mailman 3" server, not listserv. MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs. As for the CLI commands, I keep getting Attribute Error when I try them, like: /opt/mailman # mailman shell -l listname(a)mailman.tld Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the listname(a)mailman.tld mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)domain.com.') >>> print(mbr.delivery_status) Traceback (most recent call last): File "<console>", line 1, in <module> AttributeError: 'NoneType' object has no attribute 'delivery_status' >>> Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, December 9, 2024 18:38 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Enable delivery CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 12/9/24 17:35, Hirayama, Pat wrote: > Greetings, > > I'm finding something a bit odd with our listserv. Please see https://urldefense.com/v3/__https://wiki.list.org/DOC/Mailman*20is*20not*20… > Some of the members of some of the lists are reporting that they aren't receiving messages sent to the list. When I review the member options for the person in question, I see that Delivery Status shows nothing selected (i.e. neither radio button is selected for Enabled or Disabled). If you look in the MTA logs is mail being sent to them. As far as the Delivery Status showing nothing, that means the member's delivery_status is None. The ultimate delivery status is determined by checking first the member's delivery_status, then the address's delivery_status, then the user's delivery_status and finally Mailman's global preferences. The first non-None value is what's used. See https://urldefense.com/v3/__https://gitlab.com/mailman/mailman/-/blob/maste… Also see the various tabs at https://urldefense.com/v3/__https://www.example.com/mailman3/accounts/subsc… > If I select Enabled and Save, then delivery starts working for that user. This should only happen if the users address or user based preference or the global preference is Disabled. > There are other members of the list that have neither Enabled or Disabled selected, but they are working. Which also seems to mean that when I run: > > mailman members --nomail any listname@listserv > > Nothing is returned. Because all members ultimately have delivery enabled. > If anyone has any ideas about why this might be the case, or how I might proactively identify other members who aren't receiving mail, that would be appreciated. Alternately, any thoughts on how I might force all members to Delivery Status Enabled, that would also be great. It shouldn't be necessary to do that. For one of these members, e.g. user(a)example.com, that isn't getting mail, do this in mailman shell ``` mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> from mailman.core.constants import system_preferences >>> mbr = m.members.get_member('user(a)example.com') >>> print(mbr.delivery_status) (this will print the ultimate delivery_status, for the components do) >>> print(mbr.preferences.delivery_status) (output) >>> print(mbr.address.preferences.delivery_status) (output) >>> print(mbr.address.user.preferences.delivery_status) (output) >>> print(system_preferences.delivery_status) (output) >>> ``` The first of the (output) lines which is not None should be the same as the output from print(mbr.delivery_status). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.com/v3/__https://lists.mailman3.org/mailman3/lists/mailm… Archived at: https://urldefense.com/v3/__https://lists.mailman3.org/archives/list/mailma… This message sent to phirayam(a)fredhutch.org

4 months, 1 week

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

by Odhiambo Washington

On Thu, Oct 17, 2024 at 5:32 PM Andy Matthews <andy.matthews(a)zaxiom.com> wrote: > I'm testing locally to try and support additional domains. > > I can add new mailing lists with a domain: announce-123(a)mydomain.com > I can't add a new mailing list with an alternate domain: > announce-123(a)testing.com > > Following the documentation for domains I'm able to successfully add the > new domain (locally) with the following steps: > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… > > 1. Shell into the mailman server > 2. Shell into the mailman Python environment: mailman shell > 3. Add a new mailing list. > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('testing.com') > show_domains() # with method from the above documentation URL > <Domain testing.com> > <Domain mydomain.com> > > But then when I run a cURL command (from the mailman server) to add a list > with that new domain I get an error: > $ curl -k -u restadmin:restpass -X POST -H "Content-Type: > application/json" --data '{"fqdn_listname": "new-list(a)testing.com"}' > https://0.0.0.0:8001/3.1/lists > {"title": "400 Bad Request", "description": "Domain does not exist: > testing.com"} > > Am I doing something wrong, or missing a step? If not, how do I add > support for additional domains such that I can provide mailing list support > for that domain? > I am not sure I understand your question. Do you use Postorius and you can't add new domains from there? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

6 months

[MM3-users] applying patch 1130

by Stephen J. Turnbull

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

1 year, 8 months

[MM3-users] A short link to this page -- TinyURL

by Stephen J. Turnbull

John Griessen writes: > Is it feasible to make TinyURLs for archived list threads such as: It is. Last I checked (Internet-decades ago, I admit) there a lot of third-party URL-compressing services that you can use. So it's certainly possible. An alternative would be to standardize a few one-letter prefixes such as /m/ for a single message, /t/ for a message as thread head, /d/ for date and /a/ for author which would live under the HyperKitty namespace, with the path functioning as a search key. /t/ could also pull the parents of the message to get the whole thread. The message- and thread-oriented URLs would use prefixes of the message ID hash, and return a page with possible messages or threads if multiple ones have the same prefix, or even a "too short" error message. There are two problems to understand and perhaps solve before doing TinyURL in Mailman itself. The first is that a small namespace means a larger possibility of collisions. Not with other TinyURLs, but with other URLs on the same site. So this feature needs to be carefully designed, and often tuned to the site (for example, Twitter's use of the "t.co" domain, and Reddit's use of the /r/ prefix). The second is communicating the TinyURL to its users. What's your use case (why do you need a TinyURL vs. a clickable long URL in a link in a well-known page)? Who requests the TinyURL be created, or is it automatic? What UI do you propose for requesting a TinyURL? How is the TinyURL link communicated to the user who clicks on it or types it? How long does it need to be available? Also, why wouldn't one of those third-party services serve? That's an honest question to help understand the use case(s), not a brush-off. I have a feeling (that I can't yet explain) that it matters to the design. Steve

7 years, 1 month

[MM3-users] delete unverified accounts

by noemi

Hi, I'm noticing that a lot of 'spammers' are registering themself via postorius. They do not send emails, neither they are in any list, so they are not technically spammers, but they are a lot [maybe around 500 subscribed in the last month]. While waiting for a captcha system[0] for the main distribution, I'm looking for a rapid/easy way to delete this accounts; since they are not 'verified', I was wondering if I can locate this information in the mailman3 database or if there is some easier way to delete all unverified accounts. Do some of you any help or indications? I'm using GNU Mailman 3.3.9 (Tom Sawyer). Thanks, noemi for pangea.org [ https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ]

1 year, 4 months

[MM3-users] Re: Required permissions for mass operations

by Mark Sapiro

On 9/15/24 03:12, mailman3(a)werner.by wrote: > > To give them the moderation permission is quite easy: I add the users to the moderators of the lists. But for the user management I've to add the users to the list owners and then is there no restriction anymore to change the full list configuration. What can I do? I link to a documentation for this would help as well, but I found nothing. There is no role that allows a user to do exactly what you want. Implementation of such a role would be a significant effort. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

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

by charlie derr

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 > > > _______________________________________________ > 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 cderr(a)simons-rock.edu -- Charlie Derr Director of Instructional Technology Bard College at Simon's Rock https://simons-rock.edu GPG key: https://hope.simons-rock.edu/~cderr/Charlie_Derr_public_key.txt 413-528-7344 any/all pronouns are acceptable

1 year, 7 months

[MM3-users] Re: changeaddress command and nonmembers

by Mark Sapiro

On 2/2/23 09:28, Mike Wertheim wrote: > > Now that we're on Mailman 3 and the email list was migrated from MM2 to > MM3, we see that newaddress(a)gmail.com is a Member of the list, and we see > that oldaddress(a)hotmail.com is a NonMember of the list. That all makes > sense. > > But now, this person has decided that they actually want to go back to > using the old address. > > So I ran the command "mailman changeaddress newaddress(a)gmail.com > oldaddress(a)hotmail.com". But that gave me this output: > > Usage: mailman changeaddress [OPTIONS] OLD_ADDRESS NEW_ADDRESS > Try 'mailman changeaddress -h' for help. > > Error: Address oldaddress(a)hotmail.com already exists; can't change. > > > Can anyone explain how I can do what I'm trying to accomplish? The user needs to create an account in the web UI for newaddress(a)gmail.com and once that is done and she is logged in, she can add oldaddress(a)hotmail.com to her account. There are alternatives that you as list owner can do such as mass subscribing oldaddress(a)hotmail.com to the list and then disabling delivery to newaddress(a)gmail.com. There are also things you can do in `mailman shell` such as ``` $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> mbr = m.nonmembers.get_member('oldaddress(a)hotmail.com') >>> mbr.role = MemberRole.member >>> commit() ``` > (Also, why is this error displaying the usage message? That seems odd, > since the number and type of arguments was correct.) That's the way the `mailman` command works. All errors start with the usage. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

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

by maszap＠tin.it

Hi everyone, actually, by removing the following lines the lists work. virtual_alias_maps = mysql: /etc/postfix/mysql_virtual_alias_emails.cf, mysql: /etc/postfix/mysql_virtual_alias_maps.cf virtual_gid_maps = static: 5000 virtual_mailbox_base = / var / vmail virtual_mailbox_domains = mysql: /etc/postfix/mysql_virtual_mailbox_domains.cf virtual_mailbox_maps = mysql: /etc/postfix/mysql_virtual_mailbox_maps.cf virtual_transport = lmtp: unix: private / dovecot-lmtp virtual_uid_maps = static: 5000 But it no longer runs the stakes on roundcube. What I would like to do with postfix is to run roundcube and mailman3. For setting up postfix, I followed this example: https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… For this I have used virtual domains. I am certainly wrong. But is there a documentation that explains how to do it? Thank you in advance Max

4 years, 9 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Morris Jones

On 2/26/2021 10:55 AM, Mark Sapiro wrote: > Brian is correct. Essentially, you would need to run database queries to > get all the relevant data from the database and then add it to the > database of the new instance. A tool could be created to do the export > and import, but it doesn't currently exist unless some user has > developed one and not reported it. Would it be unreasonable to do a database dump on the old instance and a restore on the new one? Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 1 month

[MM3-users] Re: Extract a list of the lists and the administrators who manage it

by Mark Sapiro

On 1/22/24 06:33, Stephen J. Turnbull wrote: > pau.baiges(a)csuc.cat writes: > > > Is there a way to extract all the lists and show the administrators > > who manage those lists? > > mailman lists > mailman members -R $ROLE $LIST > > see also "mailman lists -h" and "mailman members -h". And you can do it all with one command like ``` for list in `mailman lists |sed 1d`;do echo ">>> $list"; mailman members -R administrator $list done ``` -- 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: mailman3 vs postfix

by Ralf Wiegand

Mark - I have a hard time following this. /path/to/where/your/settings/are located what settings? what do I am looking for? cd /opt/mailman # all mailman applications are under /opt/mailman ls django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty mailman-suite postorius venv-3.6 settings.py? /opt/mailman/mailman-suite/mailman-suite_project? I do not understand??? Ralf On 4/28/20 3:59 PM, Mark Sapiro wrote: > On 4/28/20 12:42 PM, Ralf Wiegand wrote: >> (venv-3.6) [root@empire mailman]# django-admin createsuperuser >> No Django settings specified. > > In that case, you need to specify additional options: > > --pythonpath /path/to/where/your/settings/are located > --settings name_of_your_settings_file_without_the_.py > > e.g. something like > > django-admin --pythonpath /usr/share/mailman3-web \ > --settings settings createsuperuser > >

4 years, 11 months

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

by Alan So

I am a bit hesitated to somehow fork a branch which deviate from the main branch though it is just a small bit of code changes if we do not have any developers who would claim the ownership of the branch. I do not think that system admin is an appropriate role to take this up. More requests can come from the users which may not simply be "patches". Instead, if the core team believe that the feature is useful and is willing to incorporate the feature to the main branch, I think that it is a better way of handling it. The change is also supposed to be more aligned with the design.

2 years, 4 months

[MM3-users] Re: Installing Mailman for the first time

by Mark Dale

On 2023-03-24 23:43, comprepair_jimberg--- via Mailman-users wrote: > I am running Debian 11 Server and wanting to install Mailman 3 > > Will this work for what I am trying to do? > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > If not is there a shorter list of steps to accomplish what I am trying to do? > > Jim In Tom Kisner's article: "Installing Mailman3 on Debian 11" he uses "Mailman 3 Setup Using Ubuntu Bionic" by Kelly Close. He notes a couple of differences to take heed of. The instructions worked first time around for me (ie. Mailman 3 up and running on Debian 11). https://kn6q.org/installing-mailman-3-on-debian-11/ https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…

2 years

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

by Barry Warsaw

On Jan 16, 2018, at 02:51, Colin Watson <cjwatson(a)ubuntu.com> wrote: > > I possibly should have explained our situation in a little more detail. > The way we have things set up with Mailman 2.1 is that any team in > Launchpad (teams are basically just a collection of people, with varying > policies on who can join them etc.) can have a mailing list if its > administrators want one, and they enable it in the Launchpad web UI. If > you want to subscribe to one of these lists, you join the team in > question and you press the "Subscribe to mailing list" button. Oh yeah, that was another thing that Launchpad inspired: the whole preferred email address thing. Thinking about it again now, I’m actually still kind of amazed that we could fake a one-unified-account-per-user facade over Mailman 2.1’s each-list-is-a-silo view of the world. At least you won’t have *that* mess to worry about any more. :) > I'd been thinking more of a new enum in HyperKitty for the visibility > state, since it does seem like quite an archiver-specific thing. Yep, I think that’s probably the way to do it. Then the question is who and how is HK informed about these state changes? > Well, IArchiver.archive_message sends a message from core to the > archiver. I'd been thinking of something like > IArchiver.set_list_visibility(mlist, visibility) which would send a > message from core to the archiver to instruct it to show/hide the > archives. It doesn't seem too out of line, though I'm not wedded to it > either. I don’t think that’s the right way to do it, because as Steve points out, IArchiver is really a half-duplex interface. It’s there solely to abstract away the different mechanisms for getting messages from MM3 to the archivers of choice. Even the API for getting a permalink is generally not supposed to function by direct 2-way communication with the archiver, although if an implementation of IArchiver wanted to do that, we can’t stop it. > I suppose that one alternative could be that we handle this in a > Launchpad-specific add-on to HyperKitty, since at a minimum we'll need > some of our own code there to deal with sign-in for private lists. So > the same bit of custom code that determines whether a list's archives > are private could hide them from everyone except their owner, or even > deny their existence entirely. It sounds like maybe we'd be better off > pursuing that? Yes, I think so. The other way seems too round about; you’d make a REST call from LP to Core, then Core would call a method in an interface whose implementation then sends a message to HK. Having LP talk directly to HK is much more straightforward, and also gives you the ability to have HK respond with various states or information as needed. The other way, there’d be no good way to get information back up from HK to LP. Hope that helps, and best of luck! I think it would be a fun project… if I was retired or it was 5 years ago. :) Please do come back with any further questions. -Barry

7 years, 3 months

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

by Stephen J. Turnbull

David Krantz writes: > I have just upgraded to mailman 3.2.3. My installation is from the git > sources and I use two different venv:s, one for the web part as I did > not want to compile the web server plugin to a newer python version > than 3.5, I see elsewhere that this is mod_wsgi. I forget exactly what my story was, but I did recompile on Linux and it was straightforward. Of course there are a million reasons why you might not want to do that. I just wanted to take this chance to report that for 3.6 and 3.7 this was very straightforward, in case anybody else is thinking about doing it.

5 years, 8 months

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

by Stephen J. Turnbull

tlhackque writes: > Not sure why you believe this. RFC2822 3.6.4 defines References > for e-mail. Ouch! I went to RFC 5322, searched for "References" and was taken to "Section 7. References". Evidently it was already positioned at the end of the appendices. :-( > As I wrote in later post, the message-ID syntactically requires the <>. > (just one set). > > msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS] > > Look at that for the full syntax and reference. Sure. It's messy because the id-left could be a "local-part", which could be almost anything if quoted, and the id-right could be a domain literal, which is a little more restricted. > 2822 does say: > > Therefore, trying to form a > "References:" field for a reply that has multiple parents is > discouraged and how to do so is not defined in this document. > > But programmers are rarely discouraged - with GUIs, it's pretty easy to > intuit that one might like to check the boxes on several branches of a > thread and respond "Of course, you're all right - see my cat photo". :-) Oh, I've done this by hand! ;-) > 5537 tries to make life easier - until you get to: 5322 has adopted the 5537 language for the abstract construction of the field. It doesn't say anything at all about the logical length issue and trimming. > The best one can do is to come up with a "good enough" > approximation in the available time, and tinker with/improve it > until bored. Which is what Jamie Zawinski did. His algorithm (adopted by IMAP as the standard for threading IMAP servers) has three features (1) it's an algorithm (guaranteed to terminate on finite input :-), (2) it allows for various tie-breaking methods, and (3) if you have enough messages from the thread and all In-Reply-To and References conform to the 5337 language, it will be consistent with all References data. > 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. > Although it has a defined syntax, the semantics are that message-id is > an opaque globally-unique identifier. Attempting to parse it as > anything but '<[^>]+>' is likely to be a mistake. That's true in a world where people actually follow the rules. > I doubt 'striping' is worth doing - when an message-id is present, > I've almost always seen it include the required <>. Since the delimiters are constants and required, consistently stripping them doesn't hurt with a well-formed msg-id (the delimiters aren't allowed in a msg-id). And you do have to strip the whitespace, because it's likely that different MUAs will do different things with it since they edit the old value (space-separated, tab-separated). The point is to get to the unique content. It's also possible to keep the literal content (after stripping whitespace) as well as the "cleaned" version, and use whichever one corresponds to a real message or to a different value of References in the same thread. It would be amusing if *both* were associated with real messages, but that seems unlikely. > Until yesterday's hyperkitty bug, I've never seen <<>>. At least one of my correspondents has a client that frequently creates "addresses" of the form "<a(a)b.net <a(a)b.net>>". I don't recall seeing "<<...>>" before, but I rarely look at Message-IDs. > I've rarely seen the <> missing - but I'd consider that a warning > that the message format is suspect. As in this case. Agreed. > My suggestion is that if you can't find a message-ID, A Message-ID field, or a valid msg-id in the References or In-Reply-To fields? > keep the message in an "unthreaded" bucket. If you sort that by > subject (omitting "[listtag]" and "Re:*" (case insensitive, and in > multiple languages) then by date, you probably have a useful > presentation. And a list of MUAs that need bug reports :-) The thing is that a message without a Message-ID (which I believe should not happen in Mailman, Mailman will assign one before distributing IIRC) is going to end up being a singleton thread. If there are replies to it, I don't see why they would be likely to be temporally adjacent. If they have proper replies, they will end up as proper thread roots, not in the unthreaded bucket. Am I missing something? If it's an unusable munged reference in References, the munged reference may be visible as a placeholder (no real message) in a separate subthread, or pruned (and invisible) because no real message is indicated by it. The indicated message will be in a separate subthread if it has a valid References (including no References, in which case it will be a thread root). And, of course, if it's not the immediate parent, other messages' References fields will likely allow the message to be threaded corrects. AFAICS "stripping and cleaning" an invalid msg-id is highly unlikely to duplicate a valid msg-id associated with a different message, athough there's a good chance it won't allow identification of any message at all -- which is where we started. -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

6 years, 2 months

[MM3-users] Moderating posts via email

by Dmitry Makovey

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. Since there's no place we could find in interface to change ML password I did it through the mailmanclient: ml=client.get_list('mylists(a)lists.some.com') ml.settings['moderator_password']='password123' ml.settings.save() after which we've used above password trying to approve messages following the steps outlined above. What are we doing wrong, or where to look for further information? -- Sr System and DevOps Engineer SoM IRT

7 years, 5 months

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

by Mark Sapiro

On 7/27/20 3:38 PM, Brian Carpenter wrote: > I recently imported a number of MM2 lists into MM3. Unfortunately, the person had emergency moderation turned on for these lists. Since EM is not exposed to Postorius what can be done to reverse this? To do one list: mailman shell -l <list-id> m.emergency = False commit() To do several lists: mailman shell from mailman.models.mailinglist import MailingList mlist = MailingList('first.list.id') mlist.emergency = False commit() mlist = MailingList('second.list.id') mlist.emergency = False commit() And so on for more lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: FILTER_VHOST for 3.2.1 not working after install

by Mark Sapiro

On 1/8/20 2:33 AM, Élodie BOSSIER via Mailman-users wrote: > > I would like with Mailman 3.2.1 see into : > - "example1.com/postorius/lists/" only the mailing list related to example1, > - and into "example2.com/postorius/lists/" only the mailing list related > to example2 as Mailman 2.1.x do it. > > I don't understand what I missed, could you help me please ? It works for me. I suspect in your case it has something to do with how ngnix is set up to forward to Django. What are your nginx settings for this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is there a way to see via the web GUI which subscribers were disabled? Correspondingly, can I re-enable delivery for them via the web GUI? Thank you in advance. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 5:51 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote: > I added the additional hosts to ALLOWED HOSTS in settings_local.py and > mailman is distributing mail to subscribers again. However, I then > received many emails of valid users subscriptions being disabled. What > would cause that? Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U 5ZW6X5QLQRXUOMD2DN77CYCOLKVMUXJ/ > Can subscriber management be done via command line? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/commands.html for description of the available mailman subcommands. If you are interested in re-enabling delivery for members whose delivery is disabled by bounce, you can do this fairly easily in an interactive `mailman shell` session. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/shell.html Something like the following session: $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print('Re-enabled delivery for bouncing member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() -- 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: Struggling with log rotation in Docker context

by skenny＠scss.tcd.ie

Hi Danil, Firstly, thank you so much for your reply, and I do apologize for taking so long to respond to your message. I understand your approach, and it sounds reliable and sensible. I'm still a bit confused by something though. In your example, you create the file /etc/logrotate.d/mailman - I presume that it must live in, or be available in the container - but which one? You've created a single file, with entries for both the mailman-core and mailman-web logs. But the logs of -core are not available in -web and vice-versa. Did you mean to do separate "cat <<EOF > /etc/logrotate.d/mailman" operations for each container? Thanks again Stephen

4 years, 7 months

[MM3-users] Re: Adding users

by horvath.arpad.szfvar＠gmail.com

Hi All, From Mark Dale, I've got a suggestion to use mass subscription. I've tried it before without success, but it worked now. I've done it before, but the user from the yahoo.fr domain didn't get the email, we've not found it neither in the normal folder nor in the spam. He is still hanging. And now this new member wrote to me, that she replied to the email, but it didn't work. But it worked in the end when she tried it next time. In mailman 2 there was an option to just add users without sending email out and trusting the users to do exactly what they need to do. I miss it very much. Thanks, Arpad

2 years, 5 months

[MM3-users] Re: Is there a way to see all the list's held messages

by Mark Sapiro

On 10/15/22 02:47, Martin Lorenz wrote: > Mark Sapiro wrote: >> On 10/11/22 07:04, bob B via Mailman-users wrote: > [...] >> run mailman' mean you are an admin of the server on which it is >> installed? If so, you can do this in mailman shell, but what do you > > in my case: yes > >> want to see? I.e., just a summary by list of subject, sender and hold >> reason > > how would I do this? For example, a `mailman shell` interaction like this ``` $ /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager): ... requests = IListRequests(mlist) ... first = True ... for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(mlist.list_id) ... print(f"""\ ... Sender: {data['_mod_sender']} ... Subject: {data['_mod_subject']} ... Date: {data['_mod_hold_date']} ... Reason: {data['_mod_reason']} ... """) ... ``` > Additional question: how would I set/change the owner of a number of lists identifyable by a regular expression? Something like this: ``` >>> import re >>> newowner = 'newowner(a)example.com' >>> user_manager = getUtility(IUserManager) >>> # get the address record for the new owner >>> address = user_manager.get_address(newowner) >>> # create one if necessary >>> if address is None: ... user = user_manager.create_user(newowner) ... address = list(user.addresses)[0] ... >>> for mlist in getUtility(IListManager): ... if not re.search('the criterion', mlist.list_id): ... continue ... # remove existing owners --- for owner in mlist.owners.members: ... owner.unsubscribe() ... # add new owner ... mlist.subscribe(address, MemberRole.owner) ... >>> commit() >>> ``` -- 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: Importing mbox files into archive defect with lines with From

by Stephen J. Turnbull

Alex Schuilenburg via Mailman-users writes: > Nope, apologies.� I'm happy to add the list back in - I thought I > hit reply-to-list. No apologies necessary. > As an email separator agreed, provided the body has all "First " > (preceded by a blank line and nothing preceding on the same line) > suitably escaped. That's not the way this works. You don't get to choose, only to defend your system. See https://www.jwz.org/doc/content-length.html > I have to move the lists onto a new Debian 12 server using the > native mailman 3.3.8 & mailman-web 0+20200530-2 packages. I think the relevant package version is HyperKitty's. Mailman-Web should just be a wrapper around HyperKitty and Postorius. > > The preferred way is to dump the database to SQL, and then load > > it in to the new database directly rather than downloading the > > mbox files and importing. > > Thats what I thought initially, but that failed as per > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…. > > As my old installation appears to have the django_migrations table > inconsistent with the state of the database, and Debian have been > unresponsive so far. Hm. I think it's more likely that the load overwrote the django_migrations table with the old migrations table, but the Debian-supplied database already had migrations applied on the assumption that you're either creating a new Mailman instance or upgrading in place. When you load the dumped database, that is probably smart enough to delete tables before creating them (or perhaps you just get lucky that the load doesn't try to delete or rename columns) BUT new tables do NOT get that treatment. They just sit around waiting for you to apply the migration that creates them and "what migration doing?" KA-BOOM. I suspect that "DROP DATABASE mailmanweb;" and then loading the dumped database, followed by `mailman-web migrate` will work. (Usual caveat of you should have a backup onsite, a backup in a bank vault, and a backup store on the dark side of the moon before trying this!) Thank you for going to Debian first (at about the same time is fine), by the way. We really appreciate that. We try hard to make sure Mailman works in all *our* common use cases, but distros have a different set. It's very common that a distro will do something that makes sense for their usual use cases that just fail badly for cases they didn't anticipate. > Then I guess that is the case in Debian 12. Maybe, it's often hard to tell where distros go wrong. If my guessalasys above is correct, it's simply the assumption that the user is either doing a greenfield installation or an upgrade in place. Surely those are the great majority of cases. > I thought that ">From " would be escaped to ">>From ", and so on, > so the escape could easily be reversed when imported. Ah, you are an honest person. Do not commit crimes, my friend, you will get caught. More devious thinkers quote messages by prepending only ">" to the line. Or, knowing about From-stuffing when sending signed mail then might pre-stuff From lines so that signature validation succeeds by default. Either way if you unstuff you will break the message. Maybe ChatGPT-10 will get it right. ;-) The only way to win is to not play the mbox game. > After all, I would expect that an export of the archive to mbox, > followed by a delete of the archive, followed by a > hyperkitty_import of the archive, should leave you at the same > place. You would expect, for sure. You would be wrong, because mbox is a lossy format by design. (Or by lack of design, if you prefer.) > Not with ">From " escapes in the new archives.� In fact I > also had a number of messages with "Message-ID: <>" and worse: all > messages with attachments had the text/plain content empty. I don't EVEN want to think why that might be. > The following dump and import worked. > > oldhost> mysqldump --no-create-info --no-create-db --disable-keys > --complete-insert mailman3web > mailman3web.sql > > newhost> mysql > MariaDB [(none]> use mailman3web > MariaDB [mailman3web]> source mailman3web.sql Yeah!! Except I forgot how to update the FAQ. Now I have to learn again! :-) Steve

1 year, 7 months

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

by Allan Hansen

Hi Mike, Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. I tried your script again, with nothing happening. So I tried this: >>> >>> a = 1 >>> b = 1 >>> for l in lm: ... print(a) ... a = a+1 ... for nm in l.nonmembers.members: ... print(b) ... b = b + 1 ... nm.unsubscribe() ... >>> commit() >>> print(a) 1 >>> print(b) 1 It appears that lm can't see the lists (I have 50+ of them). 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/

2 years, 7 months

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

by Mark Sapiro

On 11/10/20 12:30 PM, Brian Carpenter wrote: > Hello everyone, > > We had a new client come on board that brought a list that had the > largest out-going mail volume that I have ever dealt with. So I did what > any sane server administrator would do that is running Mailman 3: I ran > to Mark Sapiro for help! Here is what the Sage of all things Mailman > counseled me to do: Thank you <blush> > 1. Disabled VERP delivery. VERP can help improve mail delivery by > delivering 1 message per SMTP transaction (I think I got that right). > Using VERP is counter-productive as it can seriously delay outgoing mail > delivery for a high-volume list. So you can use something like the > following in the MTA section of your mailman.cfg: Actually, I mentioned VERP, but I don't think I recommended disabling it. Also note that these settings: > [mta] > verp_confirmations: no > verp_personalized_deliveries: no > verp_delivery_interval: 0 are the defaults. Further, verp_confirmations is a holdover from MM 2.1 and has no effect, although prior to Mailman 3.3.2 confirmations were sent with `confirm <token>` as the Subject: and beginning with Mailman 3.3.2, confirmations are sent with `Your confirmation is needed ...` as the Subject:. Actually, I think enabling VERP with [mta] verp_delivery_interval: 1 is generally a good idea for more reliable bounce detection. > 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. > This action was the game changer. It allows Mailman to handle 4 incoming > messages at a time instead of 1. My client's incoming list volume was > high enough where it was overwhelming the single outgoing runner. Here > is what I added to the mailman.cfg file: > > [runner.out] > instances: 4 > > Doing this step immediately solved the backlog in var/queue/out. -- 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: Mailman, etc. upgrade woes and persistent bugs

by Stephen J. Turnbull

Ruth Ivimey-Cook writes: > What I mean by per-user permissions is that some transitions, for > example bounce-disabled to enabled, should be only possible by someone > with appropriate permission to do so Right. So what you mean is "ok, we have group permissions, and maybe someday there will be a case for ACLs down to arbitrary subsets of the user population," but you don't have a concrete use case for arbitrary ACLs at the moment. BTW, I'm fine with that. Normally I'd take mere intuition of somebody like Brian (who interacts with large numbers of admins, and probably subscribers too) as a strong argument for at least experimental implementation, but I see anything more complex than the current system as likely to be a huge mess and developer time sink indefinitely, unless we keep it to the minimum necessary feature set. UI improvements based on the current permissions structure are definitely needed, though. > Do you see where I'm at? Yes, thank you for replying. > In writing this up it occurs to me that being able to see/edit rules > such as these, stored in per-list config, would probably be a good > thing. Don't know how practical that is though. I don't think it's hard at the proof-of-concept level. Eg, just use ACLs and allow arbitrary groups of Mailman User objects. But have you ever used Zope 2? That UI was based on that design, and ended up being a complete disaster. I suspect that's why permission structure is one thing that Barry did not import from Zope. Designing a way to do rules that doesn't end up like something like Zope2 sounds like a monstrously hard problem to me, and probably application-specific. Which is why I'm pushing back on Andreas and Brian -- without a good "rules definition framework", I think it's better to get it pretty close with a minimal number of moving parts. Regards, Steve

4 years, 2 months

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

by Brian Carpenter

On 2/12/21 8:41 AM, Gilles Filippini wrote: > I run a mailman3 instance with mainly private lists for which I know > and trust every single member. Some of them have Hotmail email > addresses, and the messages they send though our lists are rejected as > being spam by most of the recipients' mail servers, while these are > legitimate emails. > > I'd welcome any pointer to best practices / howtos regarding mailman3 > / exim4 configuration to mitigate this problem. What does the non-delivery long entries say are the reasons for the rejections? Do you have a SPF record setup for your list domain? Do you have DMARC mitigation enabled for your list? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

[MM3-users] Re: Customise Postorius templates?

by Stephen J. Turnbull

Duane Raymond writes: > Is anyone out there working on an overhaul of the web interface > templates Yes. There's a big accessibility project being done by a well-resourced organization. If you're going to be doing the kind of substantial work you describe, write me off-list and I'll do some introductions. (That applies to anybody reading this; project participation is by introduction, "well-resourced" doesn't mean "infinite" ;-), but anybody making a substantial contribution has need-to-know.) I'm not sure how much is still publicly available since the ownership change, but you might want to look at the Affinity and Empathy projects at emwd.com. The code is PHP but you may get some ideas from the UIs. Steve

3 years, 2 months

[MM3-users] Re: Discard all mail with the subject "The resutls of your email commands"

by Mark Sapiro

On 9/28/20 7:43 AM, w.schoener(a)alp.dillingen.de wrote: > Hello Mark, > thank you for your hint. This is not my choice but is wanted by my collegues. I discussed it already... > > I commented out the line in command.py and the "result of email commands" mail still was send. > Exists there a kind of cache, or do I just have to wait some time, until this works? > Thank you so much, > Wolfgang Did you restart Mailman core? You need to do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

As Abhilash said I checked the django configuration for email but nothing happens when the program sends the confirmation email. Is there any other configuration file for django emails? On Tue, Aug 1, 2017, 23:18 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

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

by Abhilash Raj

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

5 years, 7 months

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

by Darren Smith

Well, using the mailman shell we were able to find the request that was causing the problem - it was apparently a spam message that had some chinese characters in it. We used the shell to delete the held request... And postorius is still giving me an error 500. If I'm not mistaken the held messages are kept in .pck files - do you know if when postorius asks for held messages through the API, does mailman go to the database or to the .pck? I would actually suspect the latter, or removing the request should have fixed the problem. I'm hoping this makes sense... On Mon, Apr 23, 2018 at 3:39 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Very good, I'll give that a try and let you know! > > > On Mon, Apr 23, 2018 at 3:37 PM, Simon Hanna <simon(a)hannaweb.eu> wrote: > >> On 04/23/2018 11:29 PM, Darren Smith wrote: >> > "It's in Mailman's database in the 'message' table." >> > >> > I can see the message table - is there a way to see where it is marked >> as >> > "held"? All I'm seeing in that table is id, message_id, message_id_hash, >> > and path. >> > >> > I'm wanting to be able to query for held messages for a given mailing >> list, >> > as there are currently over 98,000 entries in the message table. >> This should be possible using the mailman shell >> http://mailman.readthedocs.io/en/latest/src/mailman/model/do >> cs/requests.html?highlight=held >> >> I haven't used the shell extensively and didn't read the whole docs, but >> it looks like it's the right place to look. If you can't do that using >> the shell, I'd say it's worth a bug report :-) >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years

[MM3-users] Re: Disabling the footer on a mailing list: Is this how?

by Mark Sapiro

On 3/28/24 07:13, David Partain via Mailman-users wrote: > From what I've read, I thought the following would do the trick: > > # sudo -u mailman -s /usr/bin/bash > $ source /local/mailman/venv/bin/activate > $ cd ~/var/templates/ > $ mkdir -p lists/test-list.our.domain/en/ > $ cp /dev/null "lists/test-list.our.wee.domain/en/list:member:regular:footer" The file is list:member:regular:footer.txt or if you have no other list:member:*:footer* files, list:member:generic:footer.txt will do both regular ad digest footers. I.e., you are missing the .txt extension. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] New domain cannot set set host

by Alain D D Williams

I have created a new domain - via postorius I want to set the 'Web Host' to be the same as the new domain but I cannot see that domain in the drop down list. Even if I save it and then edit the domain I still cannot see it. I went into mailman3-web/settings.py and added it to ALLOWED_HOSTS - no joy. I can see the domain in table mailman3.domain and mailman3web.django_mailman3_maildomain But it is not in table mailman3web.django_site Please how do I do this ? Thanks -- 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>

4 months, 3 weeks

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

by 朱超

thank you for your reply 1. It is not the MTA that refuses to send emails because the recipient's mailbox is too long, but the MUA that refuses to send the email because the recipient's mailbox is too long. Of course, you can use the confirm $token message to dev-request@domain for confirmation. This is a comparison Troublesome process, by visiting https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token, but he reported 404. 2. It is recommended to modify postorius, in order to keep the logic function of the underlying mailman-core unchanged, and optimize postorius at the application layer to increase user experience; even if there is no mailman-web service or postorius service, mailman-core can still run normally. If you look at the separation of the application layer and the underlying software, I think it is possible From: Tom At 2023-01-17 19:44:20, "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: >朱超 writes: > > > Yes, You got it. It is too cumbersome to ask the user to write a > > reply email for email confirmation. > >Surely clicking on "reply" then "send" is not cumbersome (unless >there's a way to get rid of confirmation altogether). Your problem is >that some of your subscribers can't do that. > >I have not previously heard of a MTA that refuses to *send* mail >because the addressee's mailbox is too long. IIRC there's a limit of >256 characters on domains, but only the (long-obsolete) recommendation >that lines in the message be 998 bytes or less restricts the length of >the local-part. > >I don't really see a good reason to change this default because there >are a number of configurations where there is no web service >available. I suggest a partial remediation in the issue I just filed. >(I think dealing with the rest of the issue is a Simple Matter of >Programming, but the question of determining existence and status of >an appropriate web service is more complex so I did address that.) > > > Why do you need to modify the mailman-core service， > >I suggest we should modify the code of the postorius, > >We are not going to do that, because >1. Mailman provides no guarantee that any web service is present, and > we're not going to make changes that require one. >2. Mailman provids no guarantee that the web service is Postorius > even if there is one, and we are definitely not going to make > creating compatible implementations more annoying than necessary. > > > Currently I have achieved it this way。 > >We encourage you to use your code. ;-) But using it exclusively to >accomplish this change would go against several of our goals in term >of separation of concerns. If we can do it in an alternative way that >serves those goals, there's no point in complexifying Postorius in >this way as well. > >Regards, >Steve >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >This message sent to tom_toworld(a)163.com

2 years, 3 months

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

by Philip Colmer

On Thu, 23 Sept 2021 at 06:19, Torge Riedel <torgeriedel(a)gmx.de> wrote: > Am 22.09.21 um 11:20 schrieb Philip Colmer: > > why don't you let Mailman3 do the DMARC mitigation? > > I do have DMARC mitigation activated in mailman3, so that all mails sent > are coming from a unique mail for each list. Some list members have strict > SPF setups forcing me to do that. > Just to confirm, the DMARC mitigation action is "Replace From: with list address" and DMARC mitigate unconditionally set to Yes? > Following the config, I use rspamd from http://rspamd.com/apt-stable/ I was using the ASAN build but I've switched back to the normal build just for consistency. Version is 3.0-2~focal > rspamadm configdump arc > *** Section arc *** > sign_networks [ > "127.2.4.7", > ] > use_domain = "recipient"; > allow_envfrom_empty = true; > allow_hdrfrom_multiple = false; > allow_username_mismatch = true; > sign_inbound = true; > sign_local = false; > symbol_sign = "ARC_SIGNED"; > path = "/var/lib/rspamd/dkim/$selector.key"; > try_fallback = true; > use_redis = false; > key_prefix = "ARC_KEYS"; > allow_hdrfrom_mismatch = true; > sign_authenticated = false; > use_esld = true; > selector = "2019"; > > *** End of section arc *** > > rspamadm configdump dkim_signing > *** Section dkim_signing *** > sign_authenticated = true; > use_esld = true; > selector = "2019"; > try_fallback = true; > use_domain = "header"; > allow_hdrfrom_mismatch = false; > symbol = "DKIM_SIGNED"; > allow_username_mismatch = true; > allow_envfrom_empty = true; > allow_hdrfrom_multiple = false; > key_prefix = "DKIM_KEYS"; > use_redis = false; > sign_local = true; > sign_networks [ > "127.2.4.7", > ] > path = "/var/lib/rspamd/dkim/$selector.key"; > > *** End of section dkim_signing *** > Thanks for sharing that. There wasn't anything of substance that was different. I'm still hitting a problem though where the final receiving MTA says that the ARC header provided by Rspamd is invalid (BodyHash is different from the expected one). I have now submitted an issue on GitHub against Rspamd because I am concerned it is trying to apply ARC before it applies DKIM, which is incorrect. Regards Philip

3 years, 7 months

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

by Simon Liebold

Am 30.05.2017 um 02:06 schrieb Mark Sapiro: > Do you have django_q in INSTALLED_APPLICATIONS in your Django config and > do you have > > # > # Asynchronous tasks > # > Q_CLUSTER = { > 'timeout': 300, > 'save_limit': 100, > 'orm': 'default', > } > > in your Django config and are you running > > django-admin qcluster > > at startup? > > See > <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>. Thanks Mark. After adding django_q, running python manage.py migrate and starting the runners it now works nicely: Successfully deleted 2 messages. Simon

7 years, 10 months

[MM3-users] Re: Message Personalization: embed User name in header/footer

by Mark Sapiro

On 05/06/2018 11:30 PM, Johannes Winter wrote: > Am Sun, 6 May 2018 07:26:45 -0700 > schrieb Mark Sapiro <mark(a)msapiro.net>: >> >> We're working on getting template editing in Postorius for release >> later this month. >> > > Cool! I hope you also fix this issue > https://gitlab.com/mailman/mailman/issues/409 while doing do? The two things are related only in that they both involve templates which is not to say that we won't come up with something for https://gitlab.com/mailman/mailman/issues/409 but only that they aren't a "package". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

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

by Ugnius S

Hi, Mark. Thank You for trying to help me. I do not remember how exactly I installed mailman or by apt-get or: $ sudo pip3 install mailman ---I think, have tried this way, but it already was installed. ~/mailman-suite$ mailman info GNU Mailman 3.2.2 (La Villa Strangiato) Python 3.5.3 (default, Sep 27 2018, 17:25:39) [GCC 6.3.0 20170516] config file: /home/user/mailman-suite/mailman.cfg db url: sqlite:////home/user/mailman-suite/var/data/mailman.db devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:Rest_password MTA works correctly. Yes, I understand the error is very strange, but this exactly happens when I add footer custom template to list's regular message via web interface. "telnet loclhost 25" answers correctly. Messages about new members adding and new list creating works and reach the recipients. But Mailman for some strange reasons could not to sent messages from member to other list's members. And nothing to do more: it is enough to delete template and mailman starts send new messages correctly. One remark all messages during with customs template was active remain somewhere in between and do not go out even if template is deleted. I can't even imagine how to debug that. I have noticed that by experience - method to check does mailman work after every small update. This system is so easy to make not working, and then is so hard to understand what did happen. It would be good to read about working example how to setup, and which moments are important. There are many places documented about separate packages, but not full example. I have found one here https://lab.uberspace.de/guide_mailman-3.html, but here part of steps seems are not written as well. For example uwsgi ini and pre required environment. It could happen that for author these steps were trivial, but for person from side some small explanations are very important to understand whole picture of setup and why small parameters where set exactly that way. Of course I am very thankful for authors of that example, because that helped me as well. 2019-08-23, pn, 20:28 Mark Sapiro <mark(a)msapiro.net> rašė: > On 8/23/19 8:11 AM, ugniusviln(a)gmail.com wrote: > > I have read documentation, but still have stupid questions, could You > please help, because I can't make it working. I do not understand something > important. I have no experience with python at all. I have mailman 3, > python 3.5 in my debian OS system, and additional packages like uwsgi and > ect. using > https://buildmedia.readthedocs.org/media/pdf/gnu-mailman/latest/gnu-mailman… > about till chapter 6. I understand mailman suite has hyperkitty already. > But I am not sure about: > > > > 1. Does mailman-suite have hyper-kitty inside? Because if I run $python > manage.py runserver - it runs. In installed it under dedicated OS user home > and fonfigured to run. > > I can create lists, event add lists to hyperkitty page using: > $django-admin runjob new_lists_from_mailman list server sends messages to > list members as well. But nothing happens more. No emails come to > hyperkitty, arciver log 0 size. > > $ python manage.py runjobs -l shows the lists of the jobs, so seems > nothing to add. > > > > How exactly did you install Mailman? The document you reference gives > alternatives. You don't say exactly what you did. > > > > 2. If I (using Postorius web interface) add footer template to my list > under regular message, something strange happens. Mailman stops to send > messages for list members. No any entries in the logs. Just Mailman log > writes: "unable to connect localhost port 25" and no more explanation. If > I delete list's footer template (web interface), mailman starts working > again. What is bad here? How to add custom footer? In mailman 2 if was > working so good and was easy to setup. > > > It appears that no MTA is listening on localhost port 25. Is your MTA > even running? It is extremely unlikely that this has anything to do with > adding a termplate in Postorius. > > You might be better off installing Debian's 'mailman3-full' package > < > https://packages.debian.org/search?keywords=mailman3-full&searchon=names&su… > >. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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, 8 months

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

by Abhilash Raj

> On Mar 13, 2021, at 1:09 PM, John Covici <covici(a)ccs.covici.com> wrote: > > On Sat, 13 Mar 2021 14:46:55 -0500, > Mark Sapiro wrote: >> >> On 3/13/21 11:14 AM, John Covici wrote: >>> >>> Now one thing came up while trying to create the database, I got a >>> traceback complaining about a revision error because gentoo had a >>> slightly different version (3.3.2) instead of 3.3.3 using pip. When I >>> upgrade mailman, am I going to have to do something to the database as >>> well and why should the database have some kind of reference to the >>> mailman version? >> >> >> I don't know why this is an issue. You shouldn't need to do anything >> with the database when you upgrade. Please post the full traceback and >> error message. > > Sorry I can't reproduce it, after dropping and recreating the database > the error went away, but it was in alembic and it was talking about an > invalid revision and gave a long hex string. > 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). But that’s just my guess without looking at the traceback. > -- > 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 <mailto:covici@ccs.covici.com> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

4 years, 1 month

[MM3-users] Re: ARC issues

by David Krantz

On Mon, Mar 2, 2020 at 7:07 PM Mark Sapiro <mark(a)msapiro.net> wrote: > I've been trying openarc > <https://github.com/trusteddomainproject/OpenARC> with Postfix as well > as Mailman's ARC. I still haven't got it all worked out - I have a > fairly convoluted mail flow with the possibility of messages being > altered before they ever get to Mailman. I do not have that problem. The ARC implementation in Mailman accepts incoming DKIM signatures etc. so that is not a problem. > There is an issue with Mailman's ARC signing in a supporting library. > See <https://github.com/ValiMail/authentication-headers/issues/5>. I have not had that issue yet, I do not think any of my users format their name that way. Good to know, though. Cheers. // David

5 years, 1 month

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

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

1 year, 11 months

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

by Odhiambo Washington

On Mon, May 29, 2023 at 2:36 PM Tibor Molnar < tibor.molnar(a)waltoninstitute.ie> wrote: > Can archiving be changed anywhere in mailman3 configs, so then all new > lists created do not archive by default? > Off the top of my head, I think the following can do it: [archiver.hyperkitty] enable: no [archiver.prototype] enable: no I believe the 'enable: no' is the default. Without enabling any of the possible archivers, I believe there will be no archiving, but I could be wrong. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

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

by paul＠arenson.org

Is there a how to on how to configure a list? For example, using a hosted option, I see this menu: Subscription requests Held messages Users Templates Settings Mass operations Banned addresses Header filters And cling on settings, for example. I have already removed my list from the list of lists on the server since I want my website users to only see my list. They can either do that here https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… or here https://list.tokyoprogressive.org/accounts/signup/ I actually do not WANT people to join without being able to use the web interface because it is intended to be a discussion list. So the option to subscribe without creating an account. is confusing to me, which is why I prefer the latter. BUT...using a test of signing up myself (using 3 other email addresses I have), some using the subscription option and some using the bottom one (no account), all the email addresses end up in my members list and non end up in my non members list. (So I am wondering what a non member is. I had thought it was someone who signed up without registering (just name, no password), but if so i wonder why all 3 of my addresses end up in the members place. Lastly, I want to configure it as a discussion list. However, I do not see that option, which was clear in MAILMAN 2. (And I understand that if someone registers without making an account, I cannot set them myself to have an account enabling them to see the archives and post from the web? If it IS possible, that would be great, because the purpose of the archives in my case is to enable better discussions than if one has only to refer to their past emails.) That is about it for now, but I am stuck on this right now and a user manual for non techie people, if it exists, would be nice. I see one for list members but not administrators. Maybe I am looking in the wrong place? Thanks paul

5 years, 7 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by David Newman

On 1/7/22 2:48 PM, Mark Sapiro wrote: > On 1/7/22 1:51 PM, David Newman wrote: >> >> However, there's no evidence test messages to the list are going out. >> (Nondelivery was the reason I was mucking around in the admin panel in >> the first place.) >> >> The Postfix log shows delivery to the list address. >> >> MM3's smtp.log shows the usual handshake. >> >> However, I do not then see messages going out to subscribers in the >> Postfix log, and as one of those subscribers I do not receive a copy >> even though my preferences are set to receive my own posts. > > > Are the messages in Mailman's var/queue/shunt queue? There are 24 messages in the shunt queue, the most recent of which is a digest from 0000 hours today. The test messages I sent later today are not there. There are also 13 messages in the out queue. I can't read these as the filenames appear to change on every invocation of ls. > Are there errors > and tracebacks in var/logs/mailman.log? Not in response to today's test messages. Here is an entry of a test message I sent going to Hyperkitty. Jan 07 12:49:03 2022 (252309) HyperKitty archived message <6e88ec49-1326-92f9-aa17-1d4c1d6828be(a)domain.tld> to https://lists.domain.tld/archives/list/listname@lists.domain.tld/message/FH… But the Postfix log doesn't show it being distributed to me or anyone else. Oddly, neither of the two list owner emails (me and someone else) show this message in the archive via the admin panel. However if I log in as the list owner directly to the archives: https://lists.domain.tld/archives/ I can see today's test posts if logged in as the list member, but do not see the posts if logged directly into the archive as the Django superuser. The nondelivery of list mail is more serious than the archive problem, though. Thanks in advance for further troubleshooting clues. dn > >

3 years, 3 months

[MM3-users] Re: Bounces

by Mark Sapiro

On 11/05/2017 01:29 PM, Mark Sapiro wrote: > > The bottom line is we aren't doing anything with bounces other than > storing them. We need to fix that, and we will (It's targeted for 3.2). > If you could help with code, that would be great. As an interim work around, if you wanted to send ALL bounces to the list owner instead of what little we currently do, at about line 65 in mailman/runners/rest.py, you'll see SUBADDRESS_NAMES = dict( admin='bounces', bounces='bounces', confirm='confirm', ... If you change the bounces='bounces', line to bounces='owner', that will cause all bounces to be just sent to the list owner(s). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

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

by Mark Sapiro

On 12/25/21 5:03 PM, William Oliver wrote: > > In any case, I added a line for "virtual_alias_domains" in my main.cf > for postfix. But it doesn't do anything, apparently, except generate > another error line (see the syslog output below). So, just for a lark, > I created an empty /opt/mailman/mm/var/data/postfix_vmap file and ran > postmap on it to create a postfix_vmap.db file. Have you added an Alias Domain for your domain? After doing that did you run `mailman aliases` or restart mailman to (re)generate the files. postfix_domains postfix_lmtp postfix_vmap postfix_domains.db postfix_lmtp.db postfix_vmap.db -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

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

by Richard Rosner

Stephen J. Turnbull wrote: > announce that you're going to start discarding posts that don't > satisfy From alignment, give it a week, and start doing it. That will > ensure that the Sender is always in the From field. No more, and no > less. I wouldn't do it, but it's a perfectly effective way to achieve > what you seem to believe is ideal. Not an option. It's not an internal list. It's a list for "outsiders" to have a single address to write to and reach several relevant people. I wish I could enforce good practices on the world, but that won't be happening any time soon. > it also doesn't take "significant resources" or thousands of emails > for training (your current spambucket and INBOX will be a decent > start) and you can train it on the fly as mail comes in. The only > resources required are a couple of hours to install it and learn how > to feed ham and spam corpuses into it, and a few minutes every so > often to feed increments of ham and spam to it. You can even avoid > that amount of effort by feeding the spam and ham it outputs back into > it.[2] Almost certainly you can plug it into rspamd. Sounds interesting, but seems quite unusable. Development has stopped almost two decades ago, as it seems. So it requires Python 2 and I doubt it's capable of handling Python3. Sorry, but I'm not turning my mail server into a dumpster fire. > > Please stop. These claims are not going to pass on this list. We > know better.[3] If you are in a special situation where they bear some > resemblance to the truth, please explain. Maybe we can come up with a > solution for that situation together. But they are wildly wrong in > the context of Internet email in general. Guess what, I do not care about what you think the "internet email in general" is. That's only your view point that doesn't match what I see going through my publicly addressable mailing lists. Sure, I'm not keeping books about every single mail that comes in and what it has in its headers. And sure, the vast majority of mails - that can't have a DKIM signature in the first place because of infrastructural reasons - are already accepted by whitelisting rules so they are irrelevant. At least as long as the whitelisting in rspamd keeps doing its job. The journey to that was hard enough. But still, the number of mails having at least either DKIM or ARC isn't that large. And even worse, DKIM is more common in the spam mails I have in my spam folder right now. Sure, those didn't have manipulated sender addresses, the biggest manipulation there was the almost boring method of putting whatever into the From field before the address so it would be shown as the name. But then you have badly written mail clients that make it easier with such lazy tricks to get by. But in the end, this simply wasn't the topic of this thread. The question was if reversing at least some of the most ridiculous manipulations of emails was possible through mailman settings.

1 year, 1 month

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

by Allan Hansen

Thank you, Mark. That makes sense. And, as you suggested, this will not work for me, because a lot of people log in and then apply to more lists. I can't exhort them to get the accounts set up and do their subscription maintenance while logged in, and they tell them that if they want to sign up for another list they have to log out first. __ I do need to find another way. I suggested these options: a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. c. That the current 'list:user:action:subscribe' be changed in published Mailman 3 source to 'list:user:action:confirm' and a new template ''list:user:action:subscribe' be set up to be sent when any subscribe request is made. This is more work, of course, so not likely a good thing to hack locally. It could be useful to other users. Of course, (a.) and (b.) are preferred in the short term, as I'd like to get our procedure simplified. Any idea which file to change for either, and some suggestion as to what to change? Yours, Allan On 3/28/23, 10:18, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 09:19, Allan Hansen wrote: > Mark, > > I tried doing this. > I unsubscribed myself from a list, set the policy as you suggest and re-applied. > I got no confirmation messages but as moderator I got the moderate message. How did you reapply? with the subscribe policy confirm then moderate a new subscriber should get the list:user:action:subscribe message and have to confirm before the request waits moderation? However, see below. > I then tried a bogus email and saw that a message was sent to that and no moderator message to me. > Would the server skip the verification message because I'm a moderator/admin? It's not because you are an admin. It's because you were logged in when you subscribed from the list's info page. You will need to confirm if you subscribe anonymously without logging in or subscribe via email, but if you are logged in to Postorius when you request subscription, that is sufficient confirmation that the request really comes from you, so you don't get an email confirmation. So, depending on your circumstances, this may or may not work for you. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/D4WXXVOHXTDLRDGXV66GV4BAMWBRYEPF/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years

[MM3-users] Re: Mailman runners missing - nothing in logs

by Torge Riedel

Am 18.01.20 um 23:14 schrieb Mark Sapiro: > On 1/18/20 6:13 AM, Torge Riedel wrote: >> So now back to good. I checked all the logs prior to restarting the >> service in directory /opt/mailman/var/log, but I do not see any errors. >> And the master was still running, I would expect that the master will >> start / restart a runner in case it died? > > What's in /opt/mailman/var/log/mailman.log? There should be entries like > > Jan 18 13:51:11 2020 (11700) xxxx runner started. > > for each runner every time it starts and like > > Jan 18 13:47:31 2020 (10096) xxxx runner caught SIGTERM. Stopping. > Jan 18 13:47:31 2020 (10096) xxxx runner exiting. > > for each runner every time it stops, but with perhaps a reason other > than `caught SIGTERM` > > That should at least tell you when they stopped. Also, if they stopped > for some reason. The master will only restart runners that exit if they > exit because of SIGUSR1 or some internal error and even then, only the > configured max_restarts number of times. > > Do you have a logrotate script for the logs in /opt/mailman/var/log, and > if so, does it have a postrotate script that signals Mailman to reopen > logs other than by a `mailman reopen` command, perhaps by signaling the > master with other than SIGHUP? > Hi Mark, I checked the logs for such entries and I do only see them when the logrotation runs and from yesterday where I restarted the service by myself. So - yes, I have logrotation configured. The logrotation has a postrotate script configured which executes `systemctl reload mailman` and I see in the logs, that it handles SIGUSR1. This happens daily in the morning and runs - for what I see - without any problems. If I understand you right I should change it to "reopen" instead of "reload". I think this is something I have to pass to mailman executable itself instead to systemctl, right? Best regards Torge

5 years, 3 months

[MM3-users] Re: Change Dmark settings via command line

by Mark Sapiro

On 4/24/24 10:34, bob B via Mailman-users wrote: > I need to set all the DMARC settings on are lists to "replace from with list address". > > Is there an easy want to do this via cli? I could do it by viewing the web interface but we have a lot of lists. With mailman shell: ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager): ... mlist.dmarc_mitigate_action = DMARCMitigateAction.munge_from ... >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

[MM3-users] Re: Changing subscription address

by Abhilash Raj

> On Mar 22, 2021, at 7:53 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Abhilash Raj writes: > >> Well a couple of stars have to align for it to work unfortunately. > > I'm not going to wait for the stars; I have backward-incompatible > surgery in mind. > >> Add to that you can’t set an address as primary using just email >> commands, you end up with what you are seeing. > > Right. The idea is that the first time an address is used, a User > will be created and that address will be primary for that User. When > the person wants to claim that address, they go to Postorius, create a > Postorius account, do the address verification dance and set > credentials, which links the Postorius account to the User via the > Address. > > This is why the ability to merge Users becomes an urgent need: people > who subscribe via email are going to end up with multiple Users. Well, it doesn’t change the situation much from status quo. You also have multiple users today, even if you subscribe via individual address since an address always has a User. And like we were discussing over on the other thread, when the owner decides to join in P and control both the addresses from single P account, we’ll merge both users. > >> We don’t necessarily need the flag on user to set an unverified primary >> address, we might be able to get away without that. We could set the >> address as primary *after* we verify it. We always verify addresses >> regardless of the choice of the subscription mode (user or address). > > I'm not clear what you're saying. In general admins can't read your > mail, so they can't verify you on a mass subscribe or an import. What I meant was, we can set the address as primary after the verification dance with the user and then subscribe the primary address. The existing subscription workflow is a multi-step process that can be paused and resumed. We pause when we send out a confirmation email and then resume when that confirmation token is somehow processed via email or API. So, post receiving the confirmation and before actually subscribing, we can se the address as primary if the user doesn’t have one and subscribe user as inhert. We don’t do any of that if user already has chosen a primary address and it doesn’t match the current address. Also, mass-subscribe and import does allow you to verify an address by clicking this “Pre-verified” checkbox, which can be useful if you are migrating from a different service or you exported a list of users from somewhere you know to be valid. > >> Right now, P is explicit about it. You can choose if you want Primary >> Address or one of the explicit addresses added to your account. The >> primary address is the pre-selected choice, so if you go and just click >> on subscribe button, you get the primary address being subscribed. If >> you choose the explicit address then we subscribe the explicit address. >> >> Is that something you think needs modifying? > > No. The option to set a subscription to the literal primary address > should still be available. I don't see a good reason to complicate > the UI logic by comparing primary to literal addresses just to remove > that one. I just want the primary address to be populated > automatically, and inherit-from-primary be the default subscription > address when the subscription address matches primary, *unless* the > subscriber explicitly chooses that literal address in Postorius. > > This is backward-incompatible, but I think it will be overwhelmingly > popular with new users and old. There would be no behavioral change for users using email commands. For those using P, I think will be able to manage and switch rather easily. > >> The email join command does the first part you suggested, (if the lookup >> succeed and matches primary address, use inherit) but doesn’t do the >> second part (it will create a user, add the address to it and then use the >> address to subscribe). We can and should fix that. > > I think that's all we need to do going forward. > > We do need a better UI for setting options (including address) for a > selection of subscriptions, but that's an independent task. > > Thanks for looking at this, Abhilash! Of course :) > > Steve -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Re: Disabling the footer on a mailing list: Is this how?

by David Partain

Hi Mark, >> From what I've read, I thought the following would do the trick: >> >> # sudo -u mailman -s /usr/bin/bash >> $ source /local/mailman/venv/bin/activate >> $ cd ~/var/templates/ >> $ mkdir -p lists/test-list.our.domain/en/ >> $ cp /dev/null >> "lists/test-list.our.wee.domain/en/list:member:regular:footer" > > The file is list:member:regular:footer.txt or if you have no other > list:member:*:footer* files, list:member:generic:footer.txt will do > > both regular ad digest footers. I.e., you are missing the .txt > extension. THANK YOU! Changed to list:member:generic:footer.txt (with the .txt ... sigh) and it works like a charm. Cheers, David

1 year

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Barry Warsaw

On Aug 9, 2017, at 16:00, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Can this be done using the REST API? If not, maybe we should do that so that > Postorius can take of the periodic tasks? It certainly could. Right now you can do effectively `mailman digests —send —bump` through the REST API, so if you wanted to leave the periodicity to Postorius, that would work right now. If we added the —periodic option to the CLI, then we should also add it to the REST API. The one thing is that —periodic and —send should be mutually exclusive for both. I’ve updated the issue with those comments. Cheers, -Barry

7 years, 8 months

[MM3-users] Re: Number of archives in list

by Simon Hanna

On 02/15/2018 08:17 PM, kawhite(a)ancestry.com wrote: > Hi, I am importing hundreds of thousands of mbox archive files and I want to know if there is a way to call a list and see how many archives got imported / are in the list now (is there a hyperkitty command to gets stats such as number of archives on a list?) > If you want to know the email/thread count you can do the following: open a new django shell ( python manage.py shell) the do the following: from hyperkitty.models.mailinglist import MailingList # you can get a specific list with MailingList.objects.get(pk=1) read django docs on how to query. # or for all: for list in MailingList.objects.all(): print('{}: {} threads, {} emails'.format(list.name, list.threads.count(), list.emails.count()))

7 years, 2 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Do not append original mail to moderation mail

by Mark Sapiro

On 1/18/20 7:11 AM, Torge Riedel wrote: > > I agree. So how to proceed on that? Get developers involved, post > somewhere a feature request? To be honest I don't know how this is > handled in development community of mailman3. You can post to mailman-developers(a)python.org, but such things tend to get put aside and forgotten. The best way to report a bug, feature request, issue, etc is to use the trackers at gitlab.com. In the case of Mailman core, this is <https://gitlab.com/mailman/mailman/issues> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

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

by testeur

Hello, I have installed mailman3 and i want to administrate it with rest api, i ve read https://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usi… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… i tryied with mailman command, but it don't do some actions (eg. delete held messages...). i tryied mailman shell... i tryied with curl to manage it, i can see if there is a pending message with : curl --user restadmin:restpass http://localhost:8001/3.1/lists/ml@domain.tld/held/count|| python3 -m json.tool| but how to delete all held messages ? is it possible in one time ? And how to select a specific message to discard /accept / defer ? do i have to use a POST ? Regards, PatG

1 year, 7 months

[MM3-users] Trying to get mailman3 in docker working with external Mysql database

by bob B

Our database group has created the database with (charset=utf8mb4&use_unicode=1) and a user For my docker-compose.yaml I will only have two container sections mailman-core mailman-web which should have these database variables set under each: -DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.server.ip]:[databseport]/[database_name] - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase Are these all correct? in looking at documentation should it be: DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.server.ip]:[databseport]/[database_name]?charset=utf8mb4&use_unicode=1 Or/and should I also use? DATABASE_URL=mysql+pymysql://.... or DATABASE_URL=mysql://... or DATABASE_URL=pymysql://.... Do I have to install pymysql? or is it installed in the dock images? Do I have to run any other commands on the database first? I assume mailman does everything it needs for the database at first launch?

3 years, 6 months

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

by Andrew Hodgson

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

1 year, 11 months

[MM3-users] Re: Mailman3 core didn't start after reboot, because mysql wasn't running yet.

by Stephen J. Turnbull

mrl(a)psfc.mit.edu writes: > Roland - Thanks, but I don't think that will help. Because > systemctl doesn't actually check to see if a service properly > started. I.e., see below. > Jul 26 04:52:11 psfcmail2 mariadbd[938]: 2023-07-26 4:52:11 0 [Note] InnoDB: Completed initialization of buffer pool > Jul 26 04:52:12 psfcmail2 mariadbd[938]: 2023-07-26 4:52:12 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=9811536157,9811536157 > Jul 26 04:52:13 psfcmail2 systemd[1]: Starting GNU Mailing List Manager... > Jul 26 04:52:25 psfcmail2 mailman[1313]: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] Connection refused)") If that's after making the "After: mariadb" change, that looks like a systemd or mariadb bug to me. If systemd is representing to Mailman that it's OK to start, but connection to the database is refused, it's NOT OK for Mailman to keep trying to start. Something is broken in the system, and Mailman's primary responsibility when it recognizes that something is broken is to *not lose mail*. So it should shut down and let the MTA queue up mail, while the system administrator fixes what's broken. > Mailman3 core needs to keep trying to access mysql, rather than > stopping. You're welcome to create a local vendor branch, but I don't see any reason to make any change in the distributed Mailman, which is not at all broken according to your story. > I could create a cron script that runs every 5 minutes, that checks > if mailman3 is not running, and tries to start it. But that's a > hack. :) That's the hack you want Mailman to implement, even though Mailman is doing everything right. There are a number of packages that do exactly this kind of thing, probably more cleanly than we could implement it. Install one of those and be done with it. In fact, almost surely systemd can do it. Steve

1 year, 8 months

[MM3-users] Migration from 2.1 to 3

by brunol＠agro.uba.ar

Hi, I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1) Following the 2.1 to 3 docs: - Create a new list - Use the import21 command The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members. In a fresh 3 new list (not imported from 2.1) this does not happen. I already tried looking for clues in the logs [logging.smtp] path: debug.log level: debug [logging.smtp-failure] path: debug.log level: debug [logging.error] path: debug.log level: debug But i haven't seen anything useful yet. Any hints on this?

5 years, 4 months

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

by Mark Sapiro

On 4/18/25 9:37 AM, Michael Richardson wrote: > > My problem, on lists.sandelman.ca aka lists.tcpdump.org, is messages that > appear to have been processed by my MTA (according to postfix logs), but > which are never delivered, nor held. Lost somewhere in mailman3 queue. > Sometimes they show up after a host reboot. It seems that maybe not all the runners are running. What's in Mailman's various var/queue/* directories? What's in Mailman's var/logs/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 days, 17 hours

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

by Mark Sapiro

On 11/20/23 00:58, Odhiambo Washington wrote: > > What is the command to export the archive as a mbox from the DB? > I can't figure out which option it is by looking at 'mailman-web -h'. Normally you do this on the old server via the HyperKitty web UI which has download buttons which do things like https://example.com/archives/list/list@example.com/export/list@example.com.… or for a partial archive https://example.com/archives/list/list@example.com/export/list@example.com-… However, in your case I don't think you have the old installation working any more so the above won't help. > BTW, how will ' mailman addmembers' treat a file containing: > ``` > Firstname Lastname <email@address> > Onlyname <email2@address> > ``` Correctly. It will import email@address with display name = 'Firstname Lastname' and email2@address with display name = 'Onlyname'. > I have opted for the simple way to do this: > 1. Create the site in Django Admin and create/configure the list in > Postorius > 2. Add the members from the file dump, with delivery set to regular. > 3. Send the members an email informing them that they need to set their > delivery preferences. > > I am stuck on the issue of exporting the archives to mbox file as already > stated above. Perhaps you can export the mbox via the web UI on the old server or maybe temporarily create a second mailman-web on your server with the old mailman-web database and use that web UI. Otherwise, if you have a working mailman-web that can access this database, you could try something like ``` $ mailman-web shell >>> from hyperkitty.lib.compat import get_list_by_name >>> mlist = get_list_by_name('list_name_only', 'list_domain') >>> with open('output.mbox', 'wb') as fp: ... for email in mlist.emails.order_by("archived_date").all(): ... fp.write(email.as_bytes() + b'\n') ... >>> ``` -- 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] Archives with encoding characters

by Seth Seeger

Hello everyone, I have a few (but not all) members complaining that their digests are full of coded characters. Two examples below were forwarded to me: > What I ended up doing was creating 2 "practice lines" in the centre of=20 > our big teaching circle (I always teach new figures in a big circle) -=20 > which each had 3 people set up in a line with generous space between,=20 > and first=C2=A0 I walked through one of those lines myself starting first= > =20 and > Robins pass Right=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Larks Loop L= > eft What is the cause? Is there anything I can do about it? Thanks, Seth

5 years, 1 month

[MM3-users] Re: How do I specify the TCP port number for Postgresql?

by Mark Sapiro

On 6/28/23 11:36 AM, kjohnson(a)eclypse.org wrote: > The mailman.cfg file on the system I am working on includes this line: > > url: postgres://mailman3:mailman3:@localhost/mailman3 First, you should change `postgres` in the url to `postgresql`. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… Also, the second colon shouldn't be there unless it's part of the mailman3 user's password. Then the docs don't say so, but you can change `localhost` to `localhost:pppp` to specify port pppp. The syntax is defined in RFC 1738. See https://datatracker.ietf.org/doc/html/rfc1738#section-3.1 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

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

by Odhiambo Washington

On Thu, Feb 8, 2024 at 4:57 PM Jeremy Stanley <fungi(a)yuggoth.org> wrote: > On 2024-02-08 10:43:37 +0300 (+0300), Odhiambo Washington wrote: > [...] > > Looking at Postorius, they do have different mail hosts. > [...] > > Are you using the magic SITE_ID=0 in your settings file? For our > deployments, that was necessary to get it to auto-detect which > filter to apply based on the domain name used by the browser. > -- > Jeremy Stanley > Yes, I do have that in settings_local.py -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: 421 - Too many sessions from source IP

by Allan Hansen

Much appreciated, Stephen and Torge! Really! Yours, Allan Hansen hansen(a)rc.org > On Mar 27, 2020, at 0:47 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > hansen(a)rc.org writes: > >> The link gives just this: >> >> 421 - [too many sessions from <source IP>] The sending IP address >> has exceeded the five maximum concurrent connection limit. >> Configure your sending server to establish no more than five >> concurrent connections. >> >> 1. Is that a legitimate excuse to refuse passing on emails or is >> cox.net too stingy? > > Very stingy (Postfix default is 50) but possibly legit. From > http://www.postfix.org/postconf.5.html (edited for brevity): > > smtpd_client_connection_count_limit (default: 50) > > WARNING: The purpose of this feature is to limit abuse. It > must not be used to regulate legitimate mail traffic. > > Note the warning. Cox may have had trouble with their MXes getting > DoS'ed, either intentionally or by poorly configured remote MTAs. > > Modern MTAs all can do connection caching, which means they can stream > multiple messages over one connection. Permitting many simultaneous > connections might be (a) a courtesy to legacy and unconfigured modern > systems that don't cache, or (b) an optimization that might be > appropriate among a collection of mutually trusting MTAs in a cloud > "mail cannon" service. > >> 2. Is that a setting we need to change in Mailman somewhere? >> Or should this be handled in some Postfix setting? > > I see Torge already suggested smtp_destination_concurrency_limit, > thanks Torge! That is the obvious setting, but there are some other > possibilities which I'll mention here, as the Postfix default is 20, > so this may affect other mail traffic adversely. > > I think you should prefer MTA setting. IIRC, Mailman 3 doesn't have > any self-throttling capability anymore, but relies on the MTA to tell > it when to stop. Even if it does, it is very likely to be more > efficient all around to have the MTA do the throttling. What should > happen (unless you're a very high-volume server talking to an MTA you > own) is that Mailman jams as many messages as possible into the MTA's > queue, and the MTA takes care of throttling. This is more efficient, > because the MTA can do a (very :-) limited amount of negotiation with > its remote peer, which Mailman cannot do. > > Check the configuration of the following options in your Postfix > configuration (documentation at postconf.5.html URL above): > > smtp_connection_cache_destinations (default: empty) > smtp_connection_cache_on_demand (default: yes) > Note: this default presumably means that, unless somebody told it > NOT to, your Postfix "should" try to cache the connection when > Mailman sends a ton to cox.net. If it's yes, try putting cox.net > in smtp_connection_cache_destinations (see documentation for > correct syntax). > smtp_connection_cache_time_limit (default: 2s) > smtp_connection_reuse_count_limit (default: 0) > smtp_destination_concurrency_limit (default: $default_destination_concurrency_limit) > smtp_destination_recipient_limit (default: $default_destination_recipient_limit) > > Hope this helps, and feel free to ask more questions. Note I probably > can't help more with Postfix (my host is Exim), but Mark and I believe > Abhilash are quite familiar with production Postfix installations. I > can't promise their availability; the Postfix channels may be more > prompt and helpful.

5 years

[MM3-users] Re: MASS mailing list import - 900 ezmlm lists to Mailman

by grant＠horizonsunlimited.com

Stephen, wow a wealth of information there! Thanks! To answer / explain a few things in more detail: 1: GDPR - we don't archive any lists, period, ever. Once an email goes through, it's done. So that shouldn't be a big issue. (that also takes care of the redact issue you mentioned) We are as compliant in all respects as possible, and we have had little issue with anyone, maybe 10-15 requests for GDPR level removal since it came out. It seems to me that Mailman 3 is the way to go, perhaps it will last as long as 2 did, so one less upgrade to do. 2: FWIW - we're trying very hard to REDUCE effort, and reduce costs. We're getting off a mixed Drupal 6 /8 and vBulletin environment for just that reason. That's ALSO part of the reason for the move. And we've been running this for 25 years, and I'm technically well past retirement age, so I'm looking to have some time for me. Time to get out and ride my motorcycles more. :) 3: Batch script to mass convert - not me! I suspect I COULD - but the time involved is no way worth it to me. 4: MySQL is available for as many db's as needed, so that's fine. Hosting the lists is a thought, but again, trying to reduce costs, and since my server already HAS mailman 2, that seems unnecessary. So, it comes down to, in my mind: A script to convert my ezmlm lists to EITHER Mailman 2 or 3 If 2, there is apparently a script to upgrade to 3 anyway, and cPanel will eventually upgrade to 3. If 3, need to install 3 on my server (VPS) - not sure how involved that is, but should be doable. I did get a couple of DM's re hosting a list, one even suggested they can do the conversion, so will check out if they will do the conversion for a reasonable fee. thanks for your help, and to anyone else who has ideas!

2 years

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

by Stephen J. Turnbull

Diana von Bidder writes: > > You can look at those using "mailman qfile <file>" [..] > > These files looked pretty normal... Are they addressed to the problematic list? What's in them? Do you actually know what's normal for email, that is, RFC 822 conformance? Do you know how to find out what characters are producing the whitespace you see? Do you know how to find non-printing characters? > What then happens is the following: > 1) I see the connection in /var/log/mailman3/smtp.log and a bak-file in > /var/lib/mailman3/in. > 2) I see an ACCEPT in /var/log/mailman3/mailman.log and the bak-file in > /var/lib/mailman3/pipeline > 3) I get the following error once a second in The only reason I can think of at the moment for this to happen so frequently is that you have the list owner set to the list's posting address, or perhaps one of the list's administrative addresses, and each error sends a mail which triggers another error, etc. Please check that. > /var/log/mailman3/mailman.log > ------ > Aug 29 11:35:06 2022 (936) HyperKitty failure on > http://localhost/mailman3/hyperkitty/api/mailman/urls: <!DOCTYPE HTML > PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>404 Not Found</title> > </head><body> > <h1>Not Found</h1> > <p>The requested URL was not found on this server.</p> > <hr> > <address>Apache/2.4.54 (Debian) Server at localhost Port 80</address> > </body></html> > (404) suggests you have mailman-hyperkitty installed but HyperKitty is either not running, or running on a different host, or Apache doesn't know how to proxy for HyperKitty, or HyperKitty is configured to serve a different base URL (ie, other than http://localhost/mailman3/hyperkitty/) Are the other lists that seem to be working configured to archive posts? Can you access the archives of the working lists from that URL? If not, mailman-hyperkitty is misconfigured. If you can, I can't think of a reason for this offhand. The relevant configurations are

2 years, 7 months

[MM3-users] Re: Do not show archives to public

by Mark Sapiro

On 6/18/19 5:21 PM, Andrew Bernard wrote: > > This resulted in dozens of messages about Django errors, when I turned on > Private Archives, and then accessed the page. Is that to be expected? [Hard > to imagine.] Perhaps you have to wait? But how long typically? This is definitely not expected. What are the errors? Including tracebacks from logs if any. As far as waiting is concerned, I think the thing you might be waiting for is the Django sync_mailman job which, if you have set up cron to run the periodic Django jobs, runs daily, but you can run it manually via the Django admin `runjob sync_mailman` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Django site - how to create programmatically - new install

by daniel.botting＠codethink.co.uk

Hi all, I've mainly setup mailman3 to replace our mailman 2.1 install using Ansible, a point I could do with some assistance on is setting the fqdn used programmatically. I've been doing alot of reading before creating this thread. To create a domain I currently navigate to: https://serverfqdn.com/postorius/domains/ and click 'Add Domain'. I believe this is setting the name of the Django site, please accept my apologies if I'm wrong and the SITE_ID=1 is then used, I am only planning to use one domain only. I'm using Postgres and when I check the contents of the Django_mailman3_maildomain table as below afterwards: mailman3web=# TABLE django_mailman3_maildomain; id | mail_domain | site_id ----+--------------------------------------+--------- 1 | mailman3-test2.guest.codethink.co.uk | 1 Many thanks Daniel

2 years, 6 months

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

by Stephen J. Turnbull

Brian Carpenter writes: > I was going to respond in detail but it will be an effort in futility. > My opinions are DEFINITELY not valued by you But they are. I 100% buy the part about providing full option data and controls in the list format (as in Mailman 2). Isn't that the most important aspect of your proposal for Postorius? In the rest of the discussion, all I did was ask what are the use cases for distinguishing admin-disabled from user-disabled. I don't know anybody better to ask than you! IMO, these use cases matter, because as I explained in another post, it seems it would be useful to provide the admin with *more* information than just the disabling agent in cases where an admin is considering reenabling a disabled subscription. I could be wrong, that's why I ask. I apologize for not ending with a question mark, I should have done so. I ask again, please, if you know, explain when admins are reenabling disabled subscriptions (other than the OP's mass disable case, which I think we understand pretty well). I personally have never reenabled a subscription except at user request. I understand my experience is extremely limited AND biased, but it is what it is, and it's all I have right now. I wouldn't be surprised if Mark's and Abhilash's are similar (although Mark does have his bicycle club list, and they're mostly not power users). So, please share yours. As for the abandoning Postorius part, do you think that hurts my feelings? On the contrary, if you can do that, I feel pride. Affinity being proprietary hurts my feelings (even though I understand perfectly well why it's necessary), but list admins and subscribers benefitting from Affinity is vindication of Barry's decision to split out the UIs from the core, despite the pain that causes some site admins. I had nothing to do with that decision, but I'm happy to be associated with a project that cares enough for users to enable such progress. Sincere regards, Steve

4 years, 2 months

[MM3-users] Re: The doubled entries issue

by Lars Bjørndal

I wrote: > I've got the problem Multiple rows were found when one or none was > required. I don't have much experience with databases. I did: sudo -i -u postgres psql mailman 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? The issue occured after creating a new list and imported from an old 21 list. Thanks Lars

1 year, 5 months

[MM3-users] mailman3 not working for mailman21 lists

by Stephen J. Turnbull

blup(a)fortytwo.ch writes: > I installed mailman3 on a server where mailman21 was installed > before. Newly created mailinglists work fine. But if I create > mailinglists with a name that was previously used on mailman21 > nothing works Your logs below show that *something* is working because Mailman 3 is logging the incoming message. > (same behaviour with and without import of old configs and > archives; no logs). Archives should have nothing to do with it (except that if there are no members with delivery enabled, you might see posts delivered to the archives, but nothing in outgoing SMTP logs). I don't understand what you mean by "without import of old configs". Do you mean you just create the list with the old name? Did you do any further configuration and set up of that list? > I purged all old mailman21 config and data This should not be necessary. Mailman 2 and Mailman 3 can even happily coexist on the same host as long as you don't try to reuse /etc/mailman, /usr/lib/mailman and /var/lib/mailman (or whatever they happen to be) from Mailman 2 for Mailman 3. > and also old postfix aliases (or at least I do think so). Since Mailman 3's SMTP logs below show incoming LMTP for both lists, I don't think there's a problem with Postfix. > If I send a mail to old list list1(a)a.b and new list list2(a)a.b I get the following logs Logs edited for brevity: > /var/log/mail.log > 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list2(a)c.a.b>, status=sent (250 Ok) > 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list1(a)c.a.b>, status=sent (250 Ok) So this is one message with two lists as addressees. > /var/log/mailman3/smtp.log > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'LHLO c.a.b' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'MAIL FROM:<....>' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list2(a)c.a.b>' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list1(a)c.a.b>' Postfix has the right alias, since it's sending messages for list1 to Mailman's LMTP port. It also appears list1 was accepted here. > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'DATA' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'QUIT' > Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) connection lost > Aug 21 22:17:40 2022 (934) Connection lost during _handle_client() > Aug 21 22:17:46 2022 (936) smtp to list2(a)a.b for 1 recips, completed in 3.14 seconds I don't see any good reason to believe either Postfix or Mailman 3 is misbehaving from the above. > How can I get more info on why the mail for list1 isn't processed? First check the queues (normally /var/lib/mailman/qfiles/*/* where the first * is a wildcard for list names and the second is a wildcard for message objects, the '/var/lib' part may be different in your installation) for a "stuck" message. Second, have you checked the other Mailman logs for information? Third, are both lists visible in the message header as addressees? Is the 'outgoing' qrunner still running? (ps ax | grep outgoing) Are there any subscribers with delivery enabled on 'list1'? Is list1 configured to accept only member posts? If so, is the sender a member whose posts are accepted? Is there a sibling list setting that would prevent the message from being sent to the same address if it is on both lists? Are the spam filter settings the same? > How can I diff the config between list1 and list2 from the command > line? This doesn't seem to be implemented. I need to prep for some meetings, but here's the basic strategy I'd follow: 1. Use "mailman withlist -i -l list1". This puts you in a Python interpreter command line. 2. Next "attrs = dir(m)" to get the list attributes as a list. 3. Check "attrs" for things like the roster of subscribers that you're not interested in printing out, and delete them. 4. Open a file as 'f', then loop over attr in attrs using "print(f'{attr}: {getattr(m, attr)}', file=f)". Then do the same for list2 (sorry, I don't know if there's a way to change lists in the middle of withlist), and diff the two files. No promises that will work exactly as written above, but it should be close. If you don't get it quickly, feel free to come back and ask for more help, I just am out of time and wanted to at least give you the basics. Steve

2 years, 8 months

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: > On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Since I made all the mailman3 enviroment wide server open (not using >> venv) I already executed the migration doing a >> >> su -m mailman3 -c "python3 manage.py collectstatic" >> su -m mailman3 -c "python3 manage.py migrate" >> >> Being mailman3 the user who runs all of mailman3 related stuff >> >> I had problems doing the migrate part, showing an error of lacking >> perms. I solved it running the migration under root (I know it could >> be trouble after, but...) > > It would be much better to identify the problem files/directories and > adjust their ownership. It is possible that running stuff as root in > the past left things owned by root causing the issue. The problem was in the intent of execute one of the migrate parts and showed about python files. I'm pretty sure that I've been very carefull not running things as root before as I know it can mess all up. But this time it was an dead end and I needed to go through. In a few days I will upgrade another server. I will document the error if I find it again. > >> >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS > I will try to trace it and comment what I find. Thaks a lot for your support. -- ___________________________________________ 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, 5 months

[MM3-users] Re: Reset digest number and volume

by Andrew Bernard

HI Mark, I get: >>> commit() Traceback (most recent call last): File "<console>", line 1, in <module> NameError: name 'commit' is not defined Andrew On 26/6/19 11:49 pm, Mark Sapiro wrote: > On 6/26/19 3:08 AM, andrew.bernard(a)gmail.com wrote: >> How to do this? After lots of testing on my pre-release beta testing list, I want the first production digest to be reset toVolume 1, Number 1. > > You can do this in `mailman shell` by setting the list's `volume` and > `next_digest_number` to 1. E.g., > > > $ ./mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > The variable 'm' is the list(a)example.com mailing list >>>> m.volume = 1 >>>> m.next_digest_number = 1 >>>> commit()

5 years, 9 months

[MM3-users] Re: Mailman/Django-allauth integration with Yahoo

by Дилян Палаузов

Hello Mark, thanks for your answer. So I had in the past registered that yahoo address withing mailman. Then I added oauth/openid to yahoo, then gave it a try. I have receieved as resut two email in the yahoo mailbox. One is sent by yahoo, notifying about account activity. The other, which I have not overseen as it was evaluated as spam, contains: You are receiving this email because you or someone else tried to signup for an account using email address: zzz(a)yahoo.com However, an account using that email address already exists. In case you have forgotten about this, please use the password forgotten procedure to recover your account: https://…/accounts/password/reset/ So the text "we have sent you an email for verification” but the email stating ”there is already such an account within mailman” is misleading, especially after the first message is shown to an yahoo-authenticated user. Greetings // Дилян -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman/Django-allauth integration with Yahoo Date: 06/08/24 03:01:24 On 8/4/24 03:35, Дилян Палаузов wrote: > > Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: > > Messages: Confirmation of email address sent to ...(a)yahoo.com > Menu: Entrance \r\n New registration > > Confirm your email address: > > We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm. > I have indeed received an email, which states: > New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo > > So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. > > Any idea what can I improve? This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue. Once you have gone through this dance, what happens the next time you sign in via Yahoo. > In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: > > SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} > > which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? I don't think it would matter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to dpa-mailman(a)aegee.org

8 months, 2 weeks

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

by Mark

On 2023-10-11 04:38, Mark Sapiro wrote: > > 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 ... > It is not a clue as to the problem. The format of that > `representation` changed in HyperKitty 1.3.5. What is your version? > HyperKitty version 1.3.4 > What happens if you do, with the appropriate Django admin and list > name, > ``` > python3 manage.py update_index_one_list thepost(a)example.com > ``` > Thank you Mark and Steve, That worked a treat! python3 manage.py update_index_one_list thepost(a)example.com Running that command returned the message "Indexing 12 emails", then returned to the shell prompt when done. It successfully indexed the messages in the archive, and I could then do a search on the existing messages. On 2023-10-11 00:54, Stephen J. Turnbull wrote: > The process of search index construction is both CPU and wall-clock > time intensive. For this reason, the cron jobs that do regular > index updating (I think once an hour?) are separate from the utility > that constructs the index in the first place when you have existing > archives (either migrated from another MLM such as Mailman 2, or if > you're upgrading to better archive software). The messages in the archive came directly from the list (ie. they weren't imported). It looks as though running that command flushed out a cobweb, as the hourly indexing is now happening. Some time after I had run that indexing command, a new message was posted to the list, and appeared in the archive. I searched (a)immediately, (b) 15 mins after, and (c)an hour and a bit after. As Steve said, the newer messages are automatically indexed hourly. So it wasn't until after that hourly index that the search terms in the newer messages were showing up in the search results. I can't say I understand the inner workings of the process yet, but we have a working archive search and I'm very happy about that. Thank you again, Mark

1 year, 6 months

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

by Abhilash Raj

On Fri, Jul 30, 2021, at 12:23 PM, bob B wrote: > ok > > ./manage was the piece I was missing so getting closer :). > > I set the MAILMAN_ADMIN_EMAIL in the .yaml, but what url do I use to login ? > > > http://mailman.domain.com/postorius/lists/. **This url does not like > the email address I used for forget password. Your email has to be confirmed by Postorius for you to login at /accounts/login. MAILMAN_ADMIN_EMAIL requires you to go through the forgot password process to set an actual password, it doesn't set a default password. If you email setup is broken for some reason and you can't get it working, one thing you could do is ask Django to simply print the outgoing emails to stdout by adding the following to the settigns_local.py (and restarting mailman-web container): EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend' You can find the emails in `docker logs mailman-web` output (or whatever the command for container's stdout is) and click on the link to verify and login into your account. > or > http://mailman.domain.com/admin **** this url has no > password reset option To reset, you want to go to /accounts/password/reset/. URL should be findable from the Sign In page. > > I added that environment variable "MAILMAN_ADMIN_EMAIL" after i already > upped my containers, > > But I then ran "docker-compose down" then "docker-compse up -d". Does > that reload and setup everything again? or could that be the issue? It reloads the configuration, but the admin is created in database, so that isn't re-created. > > > When I tried to send the test email it said "socket.gaierror: [Errno > -2] Name does not resolve" sp maybe my mailman-web container can get > dns??? Yeah, seems like something is wrong with the DNS setup there. What version of container images are you using? Also, what is the value of SMTP_HOST? Do you have that setup to point to the MTA? -- thanks, Abhilash Raj (maxking)

3 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Yes, that was the problem, DEBUG was set to True, then it was changing to filebased the EMAIL_BACKEND. But after turning DEBUG to False I'm not getting the HyperKitty UI formatted, why is that happening?? Thanks El mar., 1 ago. 2017 a las 23:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/01/2017 02:40 PM, Rafael Mora wrote: > > Why isn't it sending emails? > > > > What do you think? > > > What exactly are you doing that you think should result in sent mail? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Timeout in Postorius when trying to approve or reject moderated messages

by Brian Carpenter

On 8/27/20 10:33 AM, Sebastian Hagedorn wrote: > In case it matters, I'm trying to moderate the list using the "root" > account. Discarding works, but when I try to either accept or reject a > message, there is a timeout. Is there an error message displaying in Postorius or do you receive an Apache timeout error? When you say root account, do you mean the Django superuser account? Also have you made sure all of the permissions are owned by the mailman user in /opt/mailman? -- 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/

4 years, 7 months

[MM3-users] Getting connection timed out

by Stephen J. Turnbull

blackout69 writes: > After writing to postmaster(a)simail.it, today I was contacted by the > technical assistance of mail.simail.it > From today we are back in the whitelist :) Great! I'm glad we could be of help. Thank you for the update. It's always nice to hear about the successes, and I guess we can add simail to the "good guys or at least responsive" list. :-) > The problem was caused by them. > For some reason our server mail.catania.linux.it was in their > blacklist. That happens, even if you do everything right. I think you are doing everything right, so don't worry. And if you happen to have a similar problem, or a colleague or friend does, now you know how to deal with (even though it's still annoying. Regards, Steve

3 years, 10 months

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

by Stephen J. Turnbull

Michael Richardson writes: > Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > > that they're stable. Unfortunately, the email and web > > environments are not, and dealing with changes in them is > > often quite impractical given the Debian release cycle. > > Yes, I'm aware of this tusscle. > There are some ways to split this up. Sure but that's work for the Debian maintainers. > > Not sure what you mean by "Sometimes this goes way on it's > > own, but sometimes it does not". > > Meaning, sometimes whatever has the lock releases it everything > proceeds. Sometimes, it's still stuck a few days later, and I > restart the mailman daemons. This sounds to me like your runners are crashing, as Mark suggested. But even if that's resolved, you're still going to have a performance issue (lock contention for seconds or even minutes maybe[1]) even if you don't get stuck for days. > Fair enough. > It was not obvious when installing that I should not use sqlite3. Yeah, there's a sort of warning somewhere that we strongly recommend a full-featured RDBMS system, but we should probably make it a lot more prominent and explain why. > Yes, I'm gonna have to do that. > At least I'll start by counting number of records in each table, > and then see > if there is some systematic lack. I wonder if the routines in SQLAlchemy are expecting features (such as indexes) from your PostgreSQL DB that sqlite3 doesn't have, and so don't get copied across by pgloader. That kind of thing is why Mark suggests creating the DB by hand, then using Mailman to initialize, and finally do an SQL dump and load of the tables. Footnotes: [1] Mailman "shouldn't" be holding on to locks while doing time- consuming processing such as sending mail, but I can't promise it doesn't. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 days

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

by Mark Sapiro

On 07/31/2018 12:39 PM, Ryan McClung wrote: > I do see the output of the script and it shows the mailing lists being > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > Also, to that end, the output of lists changes depending on which directory > I am in which makes 0 sense. That is the problem. Either your mailman.cfg does not specify a fixed directory for var_dir or the mailman command(s) you run do not specify a fixed mailman.cfg. If you look, you will probably see a var/ directory is every directory in which you ran a 'mailman' command and they will all have different databases, etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] LDAP user email verification

by Stephen J. Turnbull

Tony Deshields writes: > I'm running the docker-mailman setup with LDAP integrated. My users > that authenticate against LDAP are still required to verify their > email address however, I do not want this functionality. I was > looking for guidance on possibly configuring it so my LDAP users do > not have to verify their email address. If your lists are not exposed to the outside world, go to Settings > Member Policy and set Subscription Policy (optionally Unsubscription Policy too) to "open". If your lists are exposed to the outside world, I can't recommend this alone. Perhaps Mark or Abhilash can help with a configuration that allows you to automatically authenticate against LDAP (without email configuration) and only LDAP. It's probably not hard, but I'm not familiar with the LDAP authentication channel.

1 year, 7 months

[MM3-users] Re: Rootkit issues

by peter＠chubb.wattle.id.au

> 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

1 year, 6 months

[MM3-users] Running customized version of Mailman 3

by Stephen J. Turnbull

Alan Kelm writes: > Since 2005, our organization has been running a customized version of > Mailman 2 with extensions that meet our particular needs. The main > novelty is support for /fixed subscription lists/, in which the list > members are predetermined (corresponding to a "committee"). It's not clear to me that this can't be achieved with existing Mailman 2 (or 3) features. That is, a committee's list could be populated using mass subscribe, and unsubscriptions can be prevented by requiring admin intervention. I'm not sure why this (or the "hybrid" list) requires patches. If I am correct that the basic functionality is present, and requires only small tweaks, it might be possible to include those tweaks in Mailman 3 itself. (I can't promise; this requirement also seems quite rare, and if substantial code changes, or multiple configuration options, were required, we might prefer to avoid them.) It's certainly good you posted here, and might be a good idea to post to the Mailman 2 users' list, to get others' opinions on your changes. > We are considering moving to Mailman 3 and would like to do this in > a way which makes it possible to periodically upgrade our > installation to the newest Mailman version, without clobbering our > customizations. Thus, I do not think that installing via "pip" is > the right approach for us. While I'm relatively new to git and > GitLab, they seem to be ideally suited to this situation. If I > understand the developer documentation correctly, I start out by > creating a "fork" and can later "fetch" changes from the master > branch and "rebase" to bring them into our branch. Your understanding is correct in principle. If you don't have experienced git users around, you might want to find somebody to help you design a workflow. Eg, in general you want to rebase your changes on top of the mainline, rather than the other way around. You also need to be prepared for occasional cases where your patch conflicts with something we do in the same place of the same file. Steve

5 years, 1 month

[MM3-users] bypassing rules on an individual basis

by Stephen J. Turnbull

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: > I also added header filters to immediately accept the message, but > they still get held. Specifically, the rules I defined are: > [...] Those were all incorrect. What you want is > Header, Pattern, Action > > subject, ^\s*([[{(]?no[_ ]subject[]})]?)?\s*$, Accept Immediately I believe the surrounding whitespace is stripped, so the "\s*" are unnecessary but do no harm since they match 0 spaces. However this has two potential flaws: it doesn't work if there is no Subject field at all, and it allows anyone to bypass all of Mailman's checks. Finally, there is the "pre-approved" mechanism. It's a little bit complicated because it requires setting a moderator password, which has to be done using the Python interpreter; there's no option in Postorius. It also requires a small bit of clue from the poster to add the password to the post, preferably in the header (but it can also be the first line). In either case the password is removed before distribution. For details, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs… > Is there a better way to bypass this rule? Each of the three approaches has advantages and disadvantages, so you'll have to decide. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 5 days

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

by Zaheer Abbas

I have a situation where I need to add / remove 10-20 non-members to a particular list every week and set the moderation bit to 'accept immediately (bypass other rules). I do the above via postorius because I couldn't find a way to do this via mailman shell. Can anyone help me please to achieve the above? I know how to remove all non-members via /opt/mailman/mm/bin/mailman shell -l list.example.com for nonmember in m.nonmembers.members: ... nonmember.unsubscribe() ... commit() I am just having difficulties adding the non-members and setting the moderation bit to 'Accept' Currently I am using Mailman 3.2.2 (La Villa Strangiato) and Postorius Version 1.2.4 so cant use 'postorius => settings -> message acceptance -> id_accept_these_nonmembers' -- Regards, Zaheer

1 year, 2 months

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

by Mark Sapiro

On 10/24/24 11:01, dgoldsmith--- via Mailman-users wrote: > 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. Mailman's import21 process creates Mailman users for the list memberships, but it does not create the Django user used for access to HyperKitty and Pustorius. Your users can't reset their Django (web UI) login password because they don't have a Django account. They need to `Sign up` rather than `Sign in`. > Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? It did create Mailman users, but these have nothing to do with the users that can log min to the web UI. It doesn't create these Django users. > 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? Just tell the users to go to the web UI and `Sign up` rather than `Sign in`. Removing and resubscribing a user will not help. The users that are members of mailing lists are completely separate from the users that can log in to the web UI. This is in part due to the modular nature of Mailman 3 and the fact that a Mailman 3 installation doesn't necessarily even have a Django based web UI. You may also be interested in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 4 weeks

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

by Mark Sapiro

On 3/13/21 11:14 AM, John Covici wrote: > > Now one thing came up while trying to create the database, I got a > traceback complaining about a revision error because gentoo had a > slightly different version (3.3.2) instead of 3.3.3 using pip. When I > upgrade mailman, am I going to have to do something to the database as > well and why should the database have some kind of reference to the > mailman version? I don't know why this is an issue. You shouldn't need to do anything with the database when you upgrade. Please post the full traceback and error message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] hi, how to deal with arc with using mailman+exim4?

by Stephen J. Turnbull

朱超 writes: > hi, how to deal with arc with using mailman+exim4? > Thanks for your suggestion. The preferred way to use such protocols is to deal with it entirely at the MTA level. I recommend asking about it on the Exim channels. If for some reason that is not possible, you can do it in Mailman, but this has a number of disadvantages, including inability to authenticate the peer using SPF. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d… for basic information about using ARC in Mailman, and see the file schema.cfg for the settings used in configuring it (they probably won't be in your mailman.cfg yet because the recommended approach is to do DKIM, ARC, SPF, and optionally DMARC in the MTA).

2 years, 10 months

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

by eboltz＠lhtservices.com

Mark, Here is my postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases always_add_missing_headers = yes append_dot_mydomain = no biff = no compatibility_level = 2 default_destination_concurrency_limit = 15 default_destination_recipient_limit = 30 header_checks = regexp:/etc/postfix/header_checks header_size_limit = 409600 inet_interfaces = all inet_protocols = ipv4 local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp mailbox_size_limit = 0 mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain myhostname = lists.example.com mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + relay_domains = hash:/var/lib/mailman3/data/postfix_domains relayhost = [mail.smtp2go.com]:587 smtp_always_send_ehlo = yes smtp_sasl_security_options = noanonymous smtp_tls_CApath = /etc/postfix/o365_smtp_cert.pem smtp_tls_security_level = may smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_security_level = may transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp unknown_local_recipient_reject_code = 550 virtual_alias_maps = hash:/var/lib/mailman3/data/postfix_vmap I think that I may try to start from scratch with postfix, as it doesn't seem to do what I want. This is what I'm trying to do based off the clients existing MM2 setup, which I'm building MM3 from scratch on an entire new system. I wasn't involved with their old MM2 setup from years ago, so not quite sure how it was fully setup to route emails from the mailman.example.org (virtual domain) Current client setup: - MM2 is hosted on a separate system, then relays emails through an on-prem SMTP relay (physical server) - example.org (their email domain) but routes through mailman.example.org - They have contacts configured in their existing example.org email system, which route on a 1:1 to their matching mailman.example.org counterparts New client setup: - MM2 is hosted on a separate system, but relays emails through either SMTP2GO or O365 (whichever is easiest) - example.org (their email domain) but will use lists.example.org for the MM3 lists What would I have to do to ensure that MM3 and postfix (same new server) use the newly created lists.example.org domain, which only exists within Postfix when setting up the Postorius domain and lists? I want to have it so that whatever the list name is, for example 'Staff(a)lists.example.org' will route through Postfix correctly.

1 year, 4 months

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

by Philip Colmer

On Tue, 21 Sept 2021 at 17:59, Torge Riedel <torgeriedel(a)gmx.de> wrote: > > Am 21.09.21 um 15:20 schrieb Philip Colmer: > > sharing your configuration > > I do. What configuration do you need? There is no special rspamd config in mailman3 on my setup. I'm specifically after the full configuration for arc and dkim_signing, i.e. the output from "rspamadm configdump arc" and "rspamadm configdump dkim_signing". I'm having a lot of trouble getting DKIM headers rewritten by Rspamd after Mailman 3 has altered the subject line and added the signature to the body and that, in turn, seems to then be causing Rspamd to not add the ARC headers. I'm hoping that if I can see a working config, I'll then be able to get it all sorted out. Many thanks. Philip

3 years, 7 months

[MM3-users] Re: Mailman3 core didn't start after reboot, because mysql wasn't running yet.

by Mark London

Stephen - I just looked at a Sympa mailing list running on one of our other VMs. It ran into the same problem with MYSQL, when it also was rebooted. However, it was able to eventually restart on it's own, because of these lines in it's service files. Restart=always RestartSec=15 I think that is the solution? Now I understand why I never had a similar problem with Sympa. Thanks. - Mark On 7/28/2023 12:51 AM, Stephen J. Turnbull wrote: > There are a number of packages that do exactly this kind of thing, > probably more cleanly than we could implement it. Install one of > those and be done with it. In fact, almost surely systemd can do it.

1 year, 8 months

[MM3-users] mailman transfer from 2to3

by Daniel Germer

Hello all, I am new to mailman3, once upon a time I had mailman installed on my server, but had trouble with many things, especially virtual hosts not possible in mailman2... However on https://docs.mailman3.org/en/latest/pre-installation-guide.html#what-do-i-n… are no system requirements for the installation. I assume, that I cannot just install mailman3 on a regular webhoster, but there is no section: You need to have root access to a Linux system with at least 8/16/31/64GB RAM and at least 1/2/5/7 GB of free diskspace (ssl or hard-disk?) You need so and so much for 100/1000 Lists with 10/100/1000 Users each and 5/50/500 Mailings per day... where do I find that information? what is the smallest possible machine to run mailman3 on? Can I run it on a raspberry pi? regards, Daniel

3 months, 3 weeks

[MM3-users] Re: Mailman 3 Installation Assistance

by brian＠emwd.com

Ok I am trying this again. I am not sure why my last questions were not answered. Please let me know if I am doing something wrong in asking them. Here they are again: "Please explain "You'd have to manually change the docker-compose.yaml file to use the on-host database though." Even though I run docker-compose-mysql -d I still need to update the docker-compose.yaml file? See that is confusing for me. Again it is probably due to my inexperience in using docker." I think that is a legitimate question. There are two files being referenced here. If docker-compose-mysql.yaml has the correct setup then why do I need to manually change the docker-compose.yaml? It seems both files perform the same function except one references a Postgre DB and the other a MySQL DB.

7 years

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

by Mark Sapiro

On 3/3/20 12:33 PM, David Krantz wrote: > > I think that this might be due to some kind of python misfeature where > compiled code behaves slightly differently to interpreted code, that > might explain the delay in it working initially before breaking. I > have no idea of how to solve this. I have tried to uninstall and > reinstlall psycopg2 in different versions without any luck. You need to activate your virtualenv and do pip install psycopg2-binary it must be psycopg2-binary, not just psycopg2. It's probably best to do pip uninstall psycopg2 first. As far as it working for a while, did you restart your wsgi service (gunicorn, uwsgi, ??) after upgrading? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/31/2018 11:57 AM, Peter Münster wrote: > On Wed, Jan 31 2018, Mark Sapiro wrote: > >>> I have verp_delivery_interval = 10 ... >> >> Which says only every 10th message will be VERPed. You want >> verp_delivery_interval = 1 to VERP every message. > > Hi, > > Why? The smtp relay host would get much more outgoing messages. With > verp_delivery_interval = 10, only 10% of the messages would be > personalized. Shouldn't this be enough to detect sooner or later, that a > recipient address is no more valid? Or is it important, to detect such > failure immediately? Yes, VERP does increase the number of SMTP transactions to deliver the mail from mailman to the outgoing MTA, but in general it has mush less effect on deliveries from the outgoing MTA to the recipient MXs, but with modern hardware, most people seem to find the added overhead of VERP to be minimal. Also, it is possible to have the MTA do the VERPing rather than Mailman. See <https://bugs.launchpad.net/mailman/+bug/558067> for a way to do this in Mailman 2.1. There's nothing for Mailman 3, but all that's needed is to configure Postfix to do it and add an appropriate mail_options= to the smtplib.SMTP.sendmail() calls to enable it. In any case, consider (assuming automated bounce processing is working, which it currently isn't) a list with bounce_info_stale_after = 7 days that gets even a post per day and has a member who is bouncing with a DSN that can't be successfully parsed for the member address (maybe because the bounce is from a forward to a different address) so only a VERPed bounce will be successfully scored. At some point a VERPed post bounces for this member and the member gets a bounce score of 1. Now, the next 9 posts to this list will not be VERPed and by the time the 10th post bounces it's more than a week since the first bounce and the score is reset so this member's delivery is never disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 2 months

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

by Thomas G

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

by Mark Sapiro

On 6/26/23 11:00 PM, Allan Hansen wrote: > > I also see this in queue/shunt: > > mailman@list:~/var/queue/shunt$ ls -ltr > total 88 > -rw-rw---- 1 mailman mailman 7168 Feb 17 23:03 1676703781.903885+fdcba88c680f50a0799c672cd0abe82e4bfe19b3.pck > -rw-rw---- 1 mailman mailman 19821 Apr 2 07:08 1680444501.0831451+e110b8c5c20ba3f87c1cea1c5f38e74a6cf8f1c5.pck > -rw-rw---- 1 mailman mailman 19489 Jun 18 11:52 1687114364.41209+1684717da96ff76d1ce773a0cf39c5f8b63e9078.pck > -rw-rw---- 1 mailman mailman 20274 Jun 18 19:01 1687140067.64057+7f77c1ebca490831f58ef9cfde06109081a4e7d6.pck > -rw-rw---- 1 mailman mailman 20085 Jun 26 17:18 1687825091.8457294+478565324778f2eb6f0fecaeccbd29596edaef53.pck > > The three last entries coincide with the captured messages. I suggest you examine those with `mailman qfile` and remove any irrelevant or duplicate messages. If you have mailman.log from Feb or Apr, you could find the error that caused the shunting and maybe fix it. > Finally, in the captured message source (the last which was Cc'd to me) I do see this: > > Content-Type: text/plain; charset="iso-8859-8-i" > > Which matches the complaint in the mailman log. If you want to fix and unshunt any of these, you could do, e.g., in `mailman shell` (watch out for wrapped lines) ``` >>> import pickle >>> file = '1687114364.41209+1684717da96ff76d1ce773a0cf39c5f8b63e9078.pck' >>> with open(file, 'rb') as fp: ... msg = pickle.load(fp) ... msgdata = pickle.load(fp) ... >>> msg.replace_header('Content-Type', 'text/plain; charset="iso-8859-8"') >>> with open('/path/to/.pck/file', 'wb') as fp: ... pickle.dump(msg, fp) ... pickle.dump(msgdata, fp) ... >>> ``` > Another difference: > The posted message shows > Content-Transfer-Encoding: base64 > The shunted message shows > Content-Transfer-Encoding: quoted-printable That's not important. > My question thus changes to: > > a. Should she be doing something special when sending to the lists? Get her mail client to send utf-8 or iso-8859-8 encoded messages, not iso-8859-8-i. > b. If not, is my setup in need of change? See Steve's reply. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] List rename

by Joel Lord

I'm in an odd situation where I need to rename a bunch of lists. They were all created on mailman2 originally and migrated to mailman3 (very successfully, TYVM) but the names were all originally discuss-<foo>@domain and it's very confusing to be sure you're always sending to the correct <foo>. We want to completely rename the lists to <foo>-discuss@domain. These lists do not keep archives, so if I have to resort to extracting the subscriber lists and the configs and building new lists, I'm completely fine with that. Problem is, I'm really used to MM2 and config_list and could do this without thinking using those tools... that I don't have. Running MM3 3.2.2 trying to make this happen. Any assistance I could get will be greatly appreciated. THANKS! -- Joel Lord Web Administrator, Alpha Psi Omega Grand Cast etc... etc... etc...

5 years, 6 months

[MM3-users] Re: REST Runner (and other runners) taking long time to boot up

by Abhilash Raj

On Mon, Mar 18, 2019, at 10:46 AM, Dmitry Makovey wrote: > splitting this discussion into it's own thread from "MM3 occasionally > chokes (?)". > > Re-iterating background info for posterity: > > we have been experiencing increasingly long boot ups from mailman-core > over the past year to the point where it's at about 45min for the > sequence to complete. We run couple of mailing lists (20+) that are > anywhere between 100 and 10K+ members and most of them are low traffic. > > From what I can tell all that time is spent doing some sort of indexing > operations, I'm writing from memory since I can't restart the system to > confirm that. Can you go back and check the logs from the last time you re-started? Also, can you check the output of `docker logs mailman-core` and `docker logs mailman-web` to see what happens before you see "Rest Runner was started" or similar message? I wonder if it is waiting for Postgres to come up. Core shouldn't be doing any indexing. We compiles the static files during bootup, but that should take no more than few seconds. > > sizes of directories that containers use: > 3.6G core > 352M database > 285M web > > state of my queues (as far as I understand how to evaluate them: > > $ for q in core/var/queue/*; do echo ${q}; ls ${q}/ | wc -l ; done > core/var/queue/archive > 1 > core/var/queue/bad > 3845 > core/var/queue/bounces > 0 > core/var/queue/command > 0 > core/var/queue/digest > 0 > core/var/queue/in > 0 > core/var/queue/nntp > 0 > core/var/queue/out > 7 > core/var/queue/pipeline > 0 > core/var/queue/retry > 1 > core/var/queue/shunt > 958 > core/var/queue/virgin > 0 > > what kind of tuning should we be looking into to speed up our boot-ups? > > > > -- > Sr System and DevOps Engineer SoM IRT > > > Attachments: > * signature.asc -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Mailman 3 with AWS auto scaling and potentially load balancing

by Chris McMacken

After doing a lot of googling I can't seem to find solid answers to a couple of basic mailman hosting questions so I thought I would ask here. I'm looking to build an auto scaling group so that my mailman services can self heal if the EC2 instance goes away. What state if any is stored locally on the filesystem that would need to be backed up and restored when an instance is replaced? I'm also interested in a high availability deployment so I would like to do some basic load balancing to ensure that this requirement is met but I haven't been able to find much on this topic for mailman 3. Can someone point me in the direction of a write up on this problem or comment on it?

7 years

[MM3-users] Re: Do not show archives to public

by Andrew Bernard

Hi Abhilash, This resulted in dozens of messages about Django errors, when I turned on Private Archives, and then accessed the page. Is that to be expected? [Hard to imagine.] Perhaps you have to wait? But how long typically? Andrew On Tue, 18 Jun 2019 at 22:37, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Tue, Jun 18, 2019, at 4:32 AM, andrew.bernard(a)gmail.com wrote: > > Is there a way to have list archives only visible to list subscribers? > > Presently, they are world visible - unless I have configured my site > > incorrectly. > > You can set archives to be private in Postorius under > > Settings -> Archiving -> Private Archives > > It might take some time for the changes to sync back to Archiver > after you have updated the settings. > >

5 years, 10 months

[MM3-users] Re: Postorius web issues after upgrading mailman 3

by Mark Sapiro

On 10/19/21 2:33 AM, Tibor Molnar wrote: > /var/lib/mailman3/web/static/hyperkitty > > /usr/local/lib/python3.8/dist-packages/hyperkitty/static/hyperkitty If you examine the source of your HyperKitty pages that have the issue, what do you see for the hrefs in the `<link rel="stylesheet"` tags in the <head> section. Also, I don't know if it is significant or not, but https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade says to run ``` (venv) $ mailman-web compress (venv) $ mailman-web collectstatic ``` I always run those in the other order. I suggest you do mailman-web collectstatic --clear mailman-web compress (or whatever your django admin command is) in that order and see if that helps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: [Mailman-Users] MM3 startup issues

by Mark Sapiro

Restoring original Subject:, and doesn't this thread belong on mailman-users(a)msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > Thanks again, Mark! > My responses below. > >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in >>> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? >> >> >> What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST = True >> >> in settings_local.py >> > > Yes, Brian told me to do the same. This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST = True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the > setting. > Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> >>> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a ‘mailman’ string. If you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. > > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen > chunked=chunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests to the previous domain’s lists. No more. > > Yours, > > Allan -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Invalid confirm text

by w.schoener＠alp.dillingen.de

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. 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 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. Do you have any idea, whats going wrong here? I dont know what to do any more. Thank you :-) Wolfgang

4 years, 8 months

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

by Danil Smirnov

Ron, I'm aware of the tools you mentioned and they were properly used. Please let us focus on the question I asked - how do we delete messages of a particular date if there are too many of them so using Hyperkitty UI isn't an option? Thank you. On Wed, Jul 10, 2024 at 10:18 PM Ron <admin(a)bclug.ca> wrote: > On 2024-07-10 12:05, Danil Smirnov via Mailman-users wrote: > > > After importing from Mailman 2, thousands of badly compiled messages > > from the past appeared with empty content on the same date (date of > > import). > > > > Is there a safe way to delete them all? If we delete them from the > > database - hyperkitty_email table - do we need to do some clean-up > > of hyperkitty_thread table as well? > > Per https://docs.mailman3.org/en/latest/migration.html, there's a tool > with mailman2 that can clean messages *prior* to import: > > > all mailboxes should be checked for defects before importing. Certain > > defects such as missing Message-ID: headers or missing or unparseable > > Date: headers will be corrected or ignored by the import process. The > > one defect that will definitely cause problems is lines beginning > > with From in message bodies. These will be seen as the start of a new > > message. There is a Mailman 2 script at $prefix/bin/cleanarch. > > > I'd try deleting the corrupt list, running `cleanarch` on the old list, > and re-importing. > > > If the new list has messages that are not in the old list (i.e. it's in > live production), then I'm not sure of how to proceed. > > > Note the linked page also mentions a tool called check_hk_import script > in hyperkitty/contrib folder. > _______________________________________________ > 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 danil(a)smirnov.la >

9 months, 1 week

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

by David Partain

On Thu, 2021-01-28 at 12:03 -0800, Mark Sapiro wrote: On 1/28/21 5:33 AM, David Partain via Mailman-users wrote: I wrote: I have the same issue, and have changed the configuration in /etc/mailman3/mailman-web.py to: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': 'xxxxxxxxxxxxxxxxxx', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } } and restarted stuff, but I cannot tell that it has changed anything. You responded: That should do it. I think the original message should have been saved as a queue entry in Mailman's var/archives/hyperkitty/spool/ directory. That directory has all of the messages sent to that list: # ls /var/lib/mailman3/archives/hyperkitty/spool/ 1611827925.8030825+925c996b9b6020ee18e9a689ce23384855159f77.pck 1611827926.1923075+e728f3c29c1fe6eeeca641314cdba7007cb6e132.pck 1611827925.8917305+d16b7004bdbbef98ce40fb8ee70e492715d1607d.pck 1611827926.2623458+1aac13b50d8e7f32eb14d13e6559656aa8f3bd10.pck 1611827925.9594557+7ad2a910b5ee9142c88f0bf26c60c6df960d4262.pck 1611827926.3488555+04a540651c5f829751518433e1c54168ab63a38b.pck 1611827926.0404096+a5e745f51a9f7d541aeb770a89604be17019f3c5.pck 1611827926.4206145+de861eec6404d0c8f9f8bdb180e29bff2de7c52b.pck 1611827926.1167526+0aa63639a4ec102bf63522827637e75e6a2b092a.pck This is what's expected since the underlying issue isn't yet fixed. Yes, I'm still seeing the errors. When I send mail to a list with a cute emoji, I see the following in /var/log/mailman3/web/mailman-web.log: ERROR 2021-01-28 10:58:45,708 16923 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive (bunch of python errors omitted) DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column 'content' at row 1") OK. The issue is with your database it doesn't like '\xF0\x9F\x98\x8A' which is a 4-byte utf-8 encoding for a smiley face emoji. The issue is with MySQL and MariaDB which do not accept 4-byte utf-8 encodings by default. The settings you show above should be sufficient to allow 4-byte utf-8 encodings. I'm not that familiar with how the Debian/Ubuntu package sets things up. Are you sure that /etc/mailman3/mailman-web.py is the settings file used by Django, and if so does it have at the end something like ``` try: from settings_local import * except ImportError: pass ``` and if so is there something there that overrides the DATABASES setting? If all that is OK, you may need to do something like ``` ALTER DATABASE mailman3web CHARACTER SET utf8mb4; ALTER TABLE hyperkitty_email CHARACTER SET utf8mb4; ``` on the database itself. Hi Mark (and others), I'm now looking at this again after having to focus on other stuff. I'm befuddled, and I don't really know what to do now. I did the above. If I send mail to my list with those bleeping emojis, I see the same errors. In /var/log/mailman3/web/mailman-web.log I see DataError: (1366, u"Incorrect string value: '\\xF0\\x9F\\x95\\xB5\\xF0\\x9F... new mail to root, /var/lib/mailman3/archives/hyperkitty/spool/ has a new file, etc. The mail gets delivered, of course. If I then look at the database itself, I see: mysql> use mailman3web; mysql> SELECT @@character_set_database, @@collation_database; +--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8mb4 | utf8mb4_general_ci | +--------------------------+----------------------+ 1 row in set (0.00 sec) mysql> SHOW TABLE STATUS where name like 'hyperkitty_email'; +------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+----------------+---------+ | Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment | +------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+----------------+---------+ | hyperkitty_email | InnoDB | 10 | Dynamic | 133 | 11949 | 1589248 | 0 | 196608 | 4194304 | 150 | 2021-01-29 17:23:13 | NULL | NULL | utf8mb4_general_ci | NULL | | | +------------------+--------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+---------------------+-------------+------------+--------------------+----------+----------------+---------+ 1 row in set (0.00 sec) So, I go look elsewhere... In /etc/mailman3/mailman.cfg I see: class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 Should I change the latter to be something like: url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 ? Cheers, David

4 years, 1 month

[MM3-users] Report problems NOW if you're not *sure* it's *not* a bug

by Stephen J. Turnbull

Nathan Dixon writes: > Am I missing something in my install? Or is this a bug? One of us will get to it specifically "soon" (we're all at PyCon YEAH! so not paying much attention BOO!) Right now I HAVE SOMETHING I WANT TO SAY TO YOU ALL: Sprints are coming up! This is your chance to report bugs and maybe get something done quickly. (Not all bugs get fixed quickly, sorree. But this is the best chance ) RFEs are welcome, too. What's a bug? Well, if you're sure it's NOT a bug, don't report it, post to this mailing list and get help on what you can do to make your life better. That's the best way, because some of the users are smarter and more experienced and more available than the developers. If you're pretty sure it is a bug, report it at https://gitlab.com/mailman/mailman/issues https://gitlab.com/mailman/postorius/issues https://gitlab.com/mailman/hyperkitty/issues Do your best but don't get too frantic about picking the right one. We can move (close and re-report on the correct component) issues. If it's somewhere in the middle, do both! First, report on the issue tracker so you can cite it in the mailing list post. Then post to the mailing list because it might not be a bug, and the logic above applies. If you've got the time, Google for "howto report bugs". It is time well-invested, because the more useful information you provide up front, the faster we can diagnose the harder bugs, and thus the faster we can fix them or provide a workaround. Again, don't get frantic about it, we'll ask for more information if we need it. And yes, I should ensure there's a HOWTO-BUG on the sites with both generic advice and common Mailman requirements for diagnosing bugs. 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

5 years, 11 months

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

by Mark Sapiro

On 1/22/24 13:05, Thomas Schachtner via Mailman-users wrote: > Hi there, > > But that's not the full deal. Postfix needs access to some hashed > configuration files containing the transport maps and the domains of the > mailman installation, and mailman needs the contents of the postfix > configuration file. Why do you think Mailman needs the contents of the postfix configuration file.. I don't think so. > As a quick and dirty solution, I've established a process which > periodically copies the /var/lib/mailman3 directory from the mailman box > to the postfix box using rsync. It appears you are using the Debian/Ubuntu package or at least have configured `layout: fhs` in the `[mailman]` section of mailman.cfg. This is OK, but in any case, all Postfix needs is /var/lib/mailman3/data/*. > But I would like to have a more professional solution, like a directly > shared directory between both. > I did not yet find any suggestions on how to achieve this. Are there any > best practices recommendations? > I already tried sharing the directories using sshfs, but that did not work. > > I connected the remote directory postfix.example.com:/var/lib/mailman3 > to my local directory /var/lib/mailman3 using > > sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 I would suggest the opposite. I.e. on the postfix machine ``` sshfs user@mailman_machine:/var/lib/mailman3/data /var/lib/mailman3/data ``` > This seemed to work pretty fine, as all files and directories seemed to > be available, but when starting mailman 3, the following error message > was shown: > FileExistsError: A race condition might have happened. /var/lib/mailman3 > actually exists and is not a directory. > > Any idea why this message is shown? Possibly because the uid and gid of /var/lib/mailman3 on the postfix machine do not map to the appropriate Mailman uid and gid on the mailman machine. > So, is it a bad idea to use sshfs? If you do it the other way, it might work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] The future is here?

by Stephen J. Turnbull

ieso(a)johnwillson.com writes: > For our purposes, it replaces "how to install mailman3" guides with > a single script that aims to actually do the entire thing for > you. If a single script would work, we'd have one already, I'm pretty sure. The problem is that a large proportion (I'm tempted to say "almost all" ;-) Mailman 3 installations need to fit in to an existing system configuration or pre-conceived design. I'd say that that the "standard" Mailman stack is: 0. Intel server box (not a VM) 1. Linux kernel 2. any distro 3. Postfix MTA 4. Apache webserver with wsgi module enabled 5. PostgreSQL database manager 6. Python 3 >= 3.6 7. Mailman core 8. Postorius 9. HyperKitty 10. All the above on a single host with a single public IP address and canonical domain. So 2 and 7 brook no controversy (2 because you can't argue with "anything goes", and 7 because, well, if you're arguing about 7, you're not ready to install Mailman nohow!) But every single one of the rest of those is *very* debatable -- there are already people using all of the options mentioned below (and more) in production. VMs and containers are frequently used for 0, BSDs (including MacOS) are fine for 1, Exim4 and Sendmail have varying degrees of support already for 3 (and I'll bet there are people running qmail), people do use other webservers such as nginx for 4, aside from PostgreSQL there are the MyQSL databases that are supported and some crazy folks will try to use SQLite or Oracle in production for 5, Postorius is optional and there is a commercial alternative that is used in production in a hosting service and may eventually be available for installation on your own host for 8, ditto 8 for 9 and there are yet other options such as mailarchive.com, and for 10, some people for either security or performance reasons or both want a multihomed system. So there are a minimum of 3 MTAs * 3 production-ready RDBMSes (my understanding is that there are Mailman config tweaks for standard MySQL that MariaDB doesn't need or vice-versa) to deal with, and possibly some optional options we'd like to deal with. The alternative is to say: here's the deal, spin up a Linux VM and run this script ... but that's basically what Abhilash's Docker install is (except the obvious that container != VM) -- and even that requires tweaks that are less than obvious to a lot of people to get the necessary network connectivity. So I don't see Ansible (or any such system) as a panacea. Rather, I see it as a standard language that might help us in systematically tracking variables in provisioning Mailman systems. One Ansible role would be a useful reference, and if that grows into a family of roles that are easy to compare and implement "turn-key" Mailman 3 installations for a ton of users, that would be great. That's my motivation for encouraging research into it. Now, I could be wrong -- Ansible could be more powerful than I'm giving it credit for, or that "standard" configuration might not be merely what several Mailman core devs run, it might actually be the majority of systems new to Mailman. In that case just one script would be a major contribution. So don't let me discourage anybody. But do be aware that you probably do have to make a choice between a quagmire of options and mandating a particular stack (or small set of them) for simplicity.

4 years, 3 months

[MM3-users] Customise Postorius templates?

by Duane Raymond

Hi, I'm looking to do some radical customisation of the Postorius (and Hyperkitty) templates over the next 6 ish months and was wondering if there is a 'best practice' way to do this that will survive updates to MM3. I've searched around and not found much and also tested copying venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html to var/templates/lists/summary.html As suggested in some posts - but it didn't seem to pick up the customisation - only customisations in the venv path worked - and they get overwritten on update. Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!)

3 years, 2 months

[MM3-users] Re: Verification links to localhost

by Mark Sapiro

On 2/4/23 22:50, Lars Bjørndal 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 https://localhost:8000/accounts/confirm-email/Mw:1... > > Where do I change that? This message comes from Django allauth and is probably using what it thinks is the host that is doing the add. This is based on your web server configuration which I would need to see to be more specific. I suspect you are proxying requests to https://localhost:8000/ and you are missing a directive to pass the host. For Apache I think you want ``` ProxyPreserveHost On ``` and for nginx ``` proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: postorius only show 50 owner lists

by Abhilash Raj

On Fri, Mar 1, 2019, at 3:14 PM, elalelopez(a)gmail.com wrote: > Hi, > > I have installed mailman3 suite on Debian 9. > > And postorius only lists up to 50 addresses when filter by owner: > > https: //lists.domain/mailman3/postorius/lists/? role = owner > > A first query in the database returns all the lists, but then, when it > makes the subsequent queries for each list, it ends when it reaches 50. Which database do you mean here? I think it is because it is paginated, do you see the pagination on the index page below the list of 50 lists? > Any ideas? > > regards > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

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

4 years, 5 months

[MM3-users] Re: Mailman import of 2000 lists

by Stephen J. Turnbull

Bryan Loniewski writes: > We have noticed similar slowness when importing/creating/deleting > lists. We have ~2600 lists and the bottleneck does seem to be the > MTA alias code that reads from backend (sorts by domain and then > list names?) and subsequently writes the (lmtp,vmap,etc) files. Is there a GitLab issue for this? If not, will somebody file one for us? I'd do it but I don't really understand the issue and diagnosis except for S-L-O-W, that part I get. > We're running AWS aurora serverless DB on the backend and have > split core/web hosts. For example, "is this relevant to the problem, or just to your workaround?" is a question I can't answer myself without a lot more work than I can afford to do for a week or so.

3 years, 6 months

[MM3-users] Re: Welcome message template errors

by Mark

> On 2024-04-24 03:58, Mark Sapiro wrote: > >> What do you get if you do >> ``` >> sudo -u mailman curl >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… >> ``` >> with the template set in Postorius? > ******************* > The welcome message is returned. > > root@hel:~# sudo -u mailman curl > https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… > Test Welcome message for new subscribers.root@hel:~# ******************* Making progress... I edited settings file again, replacing the domain name with the IP address () POSTORIUS_TEMPLATE_BASE_URL = 'http://12.34.56.78' (no SSL) The URI in the template table now has this. http://12.34.56.78/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/list… Now, when Mass subscribing a new member, a Welcome email is sent to the new member with the correct Subject and From, but the message is blank.

1 year

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

by Mark Sapiro

On 3/29/20 6:46 PM, Abhilash Raj wrote: > Do you have something like this[1] in your settings.py file? > > [1]: https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… > > `EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'` > > `This is a dummy email backend which will basically only print the email to stdout, which seems to happen in your uwsgi-error.log. If you do, please comment it out and see if that solves your issue.` I know Ralph previously posted > $ grep ^EMAIL settings.py > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 but is this perhaps overridden in a settings_local.py file? -- 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] Using external services for deliverability?

by tom＠gather.coop

I have a Mailman 3 server up and running but I'm terrified to migrate to it from my existing Mailman 2 provider for fear that services like Gmail will randomly start blacklisting my IP with little I can do about it. I have SPF records set up so I'm hoping I'll be Ok but I'd like to have a backup plan. Has anyone ever tried using an external service like Mailgun or Sendgrid as a relay? I tried both but couldn't get either to work due to their sender authentication mechanism. They want all 'From:' headers to be from domains that are pre-authenticated as senders. But Mailman keeps the 'From' header from the original sender so it won't match any authenticated domains. Right? Is there anything to be done here or do I just have to migrate and pray?

4 years, 9 months

Search results for query "dO"