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

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Odhiambo Washington

Check your log file for mailmanweb for clues. On Mon, 26 Jun 2023, 10:01 Ken Alker, <mailman3.org(a)alker.net> wrote: > When I view a list via Postorius the "Held Messages" menu item has an > inverse-red-"2" next to it, as if there are two held messages. There are, > in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held > messages should be in "pipeline" subdirectory). When I click on "Held > Messages" I get "Something went wrong" followed by "HTTP Error 500: > {"title": "500 Internal Server Error"}". How do I fix this? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 2 months

[MM3-users] Re: HyperKitty Question

by Mark Sapiro

On 5/4/20 6:11 PM, Samir Faci wrote: > > I have nginx running with multiple website being serviced from the same > server. > > I updated the config where port 80 gets redirected to SSL. > > I tried setting mailman3-hyperkitty.conf to both: > > base_url: http://localhost/hyperkitty> base_url: https://lists.domain.com/hyperkitty/ > Either should be OK, possibly dependent of your nginx config. > But neither seem to be working. Does hyperkitty require traffic to be > going over port 80? No. https should work. Can you go to https://lists.domain.com/hyperkitty/ in a browser? Do you have api_key: set in mailman3-hyperkitty.conf and is it set to the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django settings. Note the value needs to be quoted in MAILMAN_ARCHIVER_KEY = 'the_value' and not in api_key: the_value because the former is a Python string and the latter is a config value. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/25/22 05:26, mailman--- via Mailman-users wrote: > Dear All, > I have a similar issue. Also on Debian 11. Also installed as Debian PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) > I am using sqlite3. When I do the SQL-query I get an URI which is in multiple reasons wrong > http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… The initial part of that URL is set from the Django setting `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to `http://localhost/mailman3/`, it should probably be just `http://localhost/`. > OK - the hostname could be changed but the path is not existing at all. > There is no file "list:member:regular:footer" on the complete filesystem. It's not a file. It refers to an entry in the postorius_emailtemplate table in the database which is retrieved via the Postorius API. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Held messages page not rendering the message

by Odhiambo Washington

On Sun, Mar 19, 2023 at 1:12 PM <mike-mailman(a)earth.li> wrote: > Thanks - may be on to something. > > The sources tab shows everything ok except for > /mailman3/static/postorius/js/script.js for which it says "Unable to fetch > script source" > However the network tab shows it successfully retrieving it. > > /var/lib/mailman3/web/static/postorius/js/script.js exists and contains > only comments > Is anything showing up in your webserver logs that is related to this? Just maybe. I have tested on my setup (although I use a virtualenv setup) and I see as a click on a held message corresponds to a log entry in my webserver log. I do get a pop-up like this: ``` https://imgur.com/a/esxmDsK ``` And that is the same across all my browsers. My Desktop is running Winblows11 though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 12:01 AM, Ken Alker wrote: > When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this? The held messages are not in any queue. They are stored in Mailman's var/messages/ hierarchy. They can be examined with `mailman qfile` Also, there is a long thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and maybe others that might be relevant. -- 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] Import old mails into list

by franklin＠slat.org

Hi, I just built a new mailman3 instance. I installed directly on Debian using mailman3-full and follow /usr/share/doc/mailman3/README.Debian to set up database/web. Then I'd like to import some old mail (in a mbox file) into this list. I searched for any documentation but all I got is Import list data (from 2.1): https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… How do I import an archive into a new mailing list: https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%2… The first is import list data, not list contents (mails). The second is very old, written in 2007, and now I even can't find bin/arch commands. Also, this post in this mailing list: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Which nobody replied yet. And when I tried `django-admin hyperkitty_import` it even told me "Unknown command: 'hyperkitty_import'". Could anyone please tell me how to import old mails from mbox file into a new mailing list? Thanks, Franklin

2 years, 1 month

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

by Odhiambo Washington

On Wed, 29 Jul 2020 at 02:58, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/28/20 2:34 AM, Odhiambo Washington wrote: > > > > So, now I remember why I had to chown -R mailman3 /opt/mailman > > Then now it seems like I have been doing things incorrectly, because I > have > > been doing > > a lot of operations as root by simply: > > cd /opt/mailman/mm > > virtualenv venv > > source venv/bin/activate > > Looks like the correct way is to start with su - mailman3 > > > Yes. All those things should be done as the Mailman user. > > > >>> PS: There is the issue with qcluster, which doesn't seem to have been > ... > > I have run it from supervisord. It has forked 30 processes and refuses to > > kill them when I stop supervisord. > > I will look for options around it. > > > I know nothing about supervisord, but there should be a parent process. > E.g., here > > > msapiro@mail:~$ ps -fwwu mailman|grep qcluster > > mailman 2885 1 0 Jul18 ? 00:00:00 /bin/bash > /opt/mailman/mm/bin/mailman-web-django-admin qcluster > > mailman 2889 2885 0 Jul18 ? 00:01:57 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 2930 2889 0 Jul18 ? 01:21:03 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 2944 2930 0 Jul18 ? 00:04:17 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 2945 2930 3 Jul18 ? 07:11:14 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 6467 2930 0 15:39 ? 00:00:03 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 12337 2930 0 15:00 ? 00:00:07 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 12639 2930 0 11:08 ? 00:00:11 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 14658 2930 0 Jul27 ? 00:00:22 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 15860 2930 0 01:41 ? 00:00:21 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > mailman 19205 2930 0 Jul27 ? 00:00:29 > /opt/mailman/mm/venv/bin/python /opt/mailman/mm/venv/bin/django-admin > qcluster > > msapiro@mail:~$ > > pid 2885 is the parent which forked 2889 which in turn forked 2930 which > forked all the others. stopping (sigterm) 2885 in this case will stop > them all. > > I have seen an issue on one server where some of the qcluster workers > become orphaned and their parent pid is 1. These are left when I stop > the upstart service so I have this script. > > #! /bin/bash > if echo `status qcluster` | grep -q 'running' ; then > echo qcluster is running > exit > fi > ps -fwwu mailman|grep '[a]dmin qcluster'|awk '{print $2}'|xargs kill > > to kill them. > I found some obscure option for supervisord that enabled the killing of the process(es). Obscure because it's not documented in the sample configuration for supervisord, but it's out there in the wild. > > PS: Did you by any chance find time to look into the issue about wsgi.py > > that you had mentioned - the one that has me > > stuck using it?? > > If you're referring to the issue at the end of > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > I think that was caused by your not having the __init__.py file in > /opt/mailman/mm/. > > If not, I probably need more information. > Yes, the same problem. I created the file __init__.py in /opt/mailman/mm However, when I run using the wsgi.py I ended up (still do!) with the error: [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', application='mm3-lists.server.name|/mm3'): Loading Python script file '/opt/mailman/mm/wsgi.py'. [Wed Jul 29 10:08:51.872461 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] mod_wsgi (pid=79132): Failed to exec Python script file '/opt/mailman/mm/wsgi.py'. [Wed Jul 29 10:08:51.872507 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] mod_wsgi (pid=79132): Exception occurred processing WSGI script '/opt/mailman/mm/wsgi.py'. [Wed Jul 29 10:08:51.872754 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] Traceback (most recent call last): [Wed Jul 29 10:08:51.872827 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/wsgi.py", line 38, in <module> [Wed Jul 29 10:08:51.872835 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] application = get_wsgi_application() [Wed Jul 29 10:08:51.872847 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/wsgi.py", line 12, in get_wsgi_application [Wed Jul 29 10:08:51.872852 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] django.setup(set_prefix=False) [Wed Jul 29 10:08:51.872862 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/__init__.py", line 19, in setup [Wed Jul 29 10:08:51.872868 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Wed Jul 29 10:08:51.872878 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 76, in __getattr__ [Wed Jul 29 10:08:51.872884 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] self._setup(name) [Wed Jul 29 10:08:51.872893 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 63, in _setup [Wed Jul 29 10:08:51.872899 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] self._wrapped = Settings(settings_module) [Wed Jul 29 10:08:51.872909 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/conf/__init__.py", line 142, in __init__ [Wed Jul 29 10:08:51.872914 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] mod = importlib.import_module(self.SETTINGS_MODULE) [Wed Jul 29 10:08:51.872923 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "/usr/local/lib/python3.6/importlib/__init__.py", line 126, in import_module [Wed Jul 29 10:08:51.872929 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] return _bootstrap._gcd_import(name[level:], package, level) [Wed Jul 29 10:08:51.872938 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "<frozen importlib._bootstrap>", line 994, in _gcd_import [Wed Jul 29 10:08:51.872949 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "<frozen importlib._bootstrap>", line 971, in _find_and_load [Wed Jul 29 10:08:51.872960 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked [Wed Jul 29 10:08:51.872984 2020] [wsgi:error] [pid 79132] [remote 197.232.81.246:64709] ModuleNotFoundError: No module named 'settings' -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 1 month

[MM3-users] Re: no mails to list members

by Stephen J. Turnbull

Thomas Stein writes: > Thanks for your answer. So the the file in queue/shunt contains > information too? I will have a look. The file in queue/shunt is the message plus some Mailman metadata, as a Python pickle. You can find out what is in it using "bin/mailman.py qfile", but probably the log and traceback will tell you (or us) everything needed to fix the problem. If it's a Mailman bug (somewhat unlikely), we send you a patch and you use "bin/mailman.py unshunt" to reinject the message into the mail system via Mailman. If it's a nonconforming mail message (somewhat more likely -- typically this happens when you have raw UTF-8 or other 8-bit characters in the message header), then the easiest thing to do is to edit a saved copy of the message and resend from your mail client. (It's theoretically possible to edit the pickle and use "unshunt", but Mailman currently does not provide that feature.)

6 years, 8 months

[MM3-users] Re: Resetting users' password for them?

by Stephen J. Turnbull

Duane Raymond writes: > Regarding emails not reaching some users, the logs seem to indicate > the emails are being sent fine and in communication with users it > isn't in spam or bulk emaIL folders. Some emails arrive hours after > despite being sent on time. This may be greylisting, the practice of sending an artificial temporary SMTP failure in hopes that spammers won't come back but a legit MTA will automatically retry. IIRC the traditional first retry comes after 4 hours, although most greylisters will allow the transaction after 15 minutes. I think modernized sites do retry a lot quicker, but I don't know what MTA defaults are nowadays. If the mail is not being delivered direct from Mailman's MTA to the recipient's MTA, you wouldn't be able to tell from the sender and recipient times alone, you'd need the whole Received trace from the recipient's copy to find the point where the delay is happening. Steve

4 years, 5 months

[MM3-users] Re: changing the main template for subscriptions and more

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210622 14:22]: > It isn't necessary to patch the source in this way. If you put the > modified templates in Mailman's var/templates/site/de/ directory, > ensuring that the Mailman user can read them, they will be used and > you won't have to patch the source every time you upgrade. Thanks Mark for pointing that out. I also should have mentioned that this would be the recommendation for operations, especially if mailman is install by some normal means (pip, distribution packages, etc). I perhaps took it for granted too much to never touch files coming out of automated systems by hand (except where the automated system caters for, e.g. debian conffiles), because that is a sure way to get into trouble with the next upgrade. (My mailman installation is the exception and not the rule, so unless you know what you're doing and have done similar before, just follow Marks advice) Andi

4 years, 2 months

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

by Mark Sapiro

On 7/15/21 2:11 PM, Sarah H wrote: > I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get: > > curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number A 301 from http will be an issue always. I'm not sure where the `wrong version number` comes from. This could be the issue. If I do for example, curl -X POST https://lists.mailman3.org/archives/api/mailman/archive I get the response <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> This is the expected response. You need to figure out what base_url will give you a similar response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [220315 23:31]: > I understand that, but even Debian sid has mailman3 3.3.3-1 and > mailman3-web 0+20200530-2 which are quite old for a package like > Mailman 3 which is still in active development. If we speak about unstable, that's something else. However, Debians next stable release won't release with mailman 3.3.3, as this package is removed from testing at the moment. I'd be happy if someone would update this package, however, I don't think I should get myself also involved there. ('Removed from testing' means: the current unstable package is considered not to be in shape to be released with the next stable release). So, if someone wants to get involved into Debian package maintainership with mailman3 (and related packages), that would be great, and I'm happy to support. As said, the most easiest way to get things fixed in Debian is by doing it. Andi

3 years, 6 months

[MM3-users] Re: moving list from mm3 -> mm3

by Jens Günther

This here would be best if I could list them by Domain!? But seems to me a little nonsense ... but maybe it's registered, through which VHOST the user registered. Am 08.12.23 um 17:01 schrieb Jens Günther: > > ## registered users > > This part is somehow tricky, since I have no clue how to do it. Some of > the mailinglist-admins don't want to bother their list-owners again with > registering newly on the other system. Is there a way to export all > users (I think I found them in the DB in the table auth_users, somehow > in combination with account_emailaddress) and get them over to the new > instance (actually I just need part of them, but that's another question > that I might solve lateron on my own). > > Maybe the answer is already here: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but can somebody help to get this working (import/export)?

1 year, 9 months

[MM3-users] Re: Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)

by skenny＠scss.tcd.ie

Hi Stephen, Yes, everything *does* work if I delete and create the database afresh prior to importing - I see all my lists, with the correct memberships, settings etc. I was afraid that by removing the default database that comes with the database container, I'd be losing some vital information that may have been added or changed in the database config since I first got my production server working 2 years ago - changed field values, extra table columns ... ? Does that make any sense? I've a hazy understanding at best of the minutiae of databases, being honest. I had actually started to mull over creating all my lists afresh on the new server, and populating them using scripting/mailmanclient, but I'm now encouraged by your answer :-) - so maybe I'll just wipe and recreate mailmandb, and then do the import. Thanks a lot for your reply Stephen

3 years, 1 month

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 04:26, Odhiambo Washington wrote: > > > > Okay. This is a bit off from my understanding. > > > > What is the cause and how do I mitigate it? > > The cause is the monthly hyperkitty update_and_clean_index job runs for > a long time, i.e. hours, because it is rebuilding the entire search > index so during the time it's running multiple hourly hyperkitty > update_index jobs are started and they are competing for the same lock. > > See > > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > for mitigation. What is the danger of replacing my settings.py with this one, seeing as it differs in a number of ways with mine? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Mark Sapiro

On 1/24/24 02:38, amg hsn wrote: working packages with exact version. > for me each time i build venv i have different warning or erro. I understand your frustration and I'm sorry. The problem is that the current release of django-mailman3, 1.3.11, just requires django-allauth>=0.56, so a new install will get the latest django-allauth==0.60.1, but django-mailman3==1.3.11 is not compatible with django_allauth>=0.59. This will be fixed in the next release, but in the mean time, you can apply https://gitlab.com/mailman/django-mailman3/-/merge_requests/237/diffs and https://gitlab.com/mailman/django-mailman3/-/merge_requests/243/diffs to update django-mailman3 for compatibility with the latest django-allauth. This can be an issue when any of our third party dependencies is upgraded in an incompatible way. Short of pinning all the dependencies to a specific version, there's not much we can do about it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

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

by David Newman

On 1/7/22 12:06 PM, Mark Sapiro wrote: > On 1/7/22 11:06 AM, David Newman wrote: >> >> 1. In Users/Members, moderation action for the newly resubscribed >> users shows as "None". Is there a method, either in the UI or the >> command line, to change this to "Default processing" for all users? > > > I assume you don't want to set `Default action to take when a member > posts to the list` to Default Processing because you want new member > posts to be held. This is a good practice. To set all members to default > processing in mailman shell .. OK, thanks >> 2. Although Delivery Mode shows as "Regular" for all users in >> Users/Members list, clicking on a member's name shows all options such >> as delivery status, delivery mode, etc., as undefined. > > > They show as undefined, but if you look at your own settings by > selecting `Mailman settings` from the dropdown under your username at > the upper right in Postorius, you will see you have Global Mailman > preferences, Address-based preferences and List-based preferences. If a > list based preference is unset for a list, it falls back to the address > based preference for the address and if that's unset, to the global > preference. > > When you as an admin look at a user, you only see the user's list based > preferences. Thanks. This makes sense, but something's wrong with this particular list. I was able to change preferences using the shell commands you kindly provided. All list member now have regular delivery and default moderation. 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. The admin panel shows 0 messages held for moderation. Another mailing list in the same domain on the same server delivers mail to all subscribers OK. This is surely config problem on my end, but which log(s) and/or admin panel setting(s) to check? Thanks again. dn > >> Similar question: How to set subscriber options for all members in one >> go? > > > Per the above, you only need to set the user's preferences if they don't > have address based preferences and the preference differs from the > global (default) preferences. > > However, if you want to set the member's list preferences, you could add > to the beginning of the above: > ``` > >>> from mailman.interfaces.member import DeliveryMode, DeliveryStatus > >>> english = getUtility(ILanguageManager).get('en') > ``` > and to the `for` loop in the above: > ``` > ... mbr.preferences.acknowledge_posts = False > ... mbr.preferences.delivery_mode = DeliveryMode.regular > ... mbr.preferences.delivery_status = DeliveryStatus.enabled > ... mbr.preferences.hide_address = False > ... mbr.preferences.preferred_language = english > ... mbr.preferences.receive_list_copy = False > ... mbr.preferences.receive_own_postings = True > ``` > Or whatever you think these settings should be. > >> 3. As a subscriber to this list, I received email notification that >> I'd been unsubscribed. Where is the control for enabling/disabling >> subscription notifications? > > > Settings -> Automatic Responses > > >> Settings/Member Policy/Un-subscription Policy is set to Confirm, but I >> don't think that's relevant here since I unsubscribed users as the >> Django superuser. > > > Correct. >

3 years, 8 months

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

by Odhiambo Washington

On Thu, Apr 17, 2025 at 3:14 PM Christian Schneider < christian.schneider(a)tu-dortmund.de> wrote: > Thank you for your instant reply! > > Mihai Moldovan wrote: > > > But I could find no information about the location where hyperkitty > stores the archives on an Ubuntu-/Linux-system. > > > I assume the archives are stored underneath "/var/..." this is only a > guess. > > > But is this guess right? > > > Not quite. > > To the best of my knowledge, by default, a venv installation is fully > contained > > under /opt/mailman, with archives and stuff stored at > /opt/mailman/var/lib/... > > This information is very helpful! > Actually I have about 45GB of archives and these archives only hold > messages of the last year... > I run a clean-up script every first day of a month which deletes posts > older than 365 days... > So there is lot of disk space needed... ;-) > (and even more if I plan to keep posts around for a longer time) > > > > Another question is: > > > How much space do I have to plan (roughly) for the "/opt"-partition > for the mailman install if the archives are stored under "/var/..."? > > > Depends on your archives, the way things are archived (you can choose > different > > database backends, and these might make a difference in how efficiently > or > > inefficiently data is stored) and whether you want to use the full-text > search > > index, which adds another big chunk of data. > > I can give you a few pointers regarding my setup: my mailman 2.1 data > directory > > takes up about 8.2 GB of disk space, most of which are archives, > naturally (8.1 > > GB). I've imported most of the big archives to mailman 3 already, with a > > full-text search index, and that uses 5.2 GB disk space currently, but > I'm still > > missing a few archives, so that'll still grow a bit. It will probably > end up at > > about the same size, but I can come back to that once my import is fully > done > > (which sadly will take a few days). > > Now, the 8.1 GB of mailman 2.1 archives are stored pretty inefficiently, > because > > they are essentially duplicated (as a private mbox archive and public > text > > archives). Mailman 3 doesn't do that - at least not directly - but > instead > > stores archives once into the database, and queries the database > whenever the > > archives are accessed via hyperkitty, so I would *assume* the size you > need for > > the mailman 3 data after a successful migration is just a bit shy of > what you > > needed for the mailman 2.1 data, maybe even a bit less. > > Perfect! :-) > If I mount an extra partition of 250Gigs at /opt this should carry me for > a longer time... > And - if I setup a logical volume with LVM - there is an option to stack > up the space with ease... ;-) > Does your DB backend also store the data files in /opt? I doubt it. The archives will be stored in the DB backend. So unless you use SQLite backend, the data will go where you configure your DB to store data- whether it's MariaDB or PostgreSQL. -- 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]

5 months

[MM3-users] Re: Query on how to change moderator message to non-members

by Simon Hanna

Yes you can. But you can't do it thought the web ui yet. https://gitlab.com/mailman/mailman/issues/426#note_43861203 has pointers to what needs to be done On 07/01/2018 12:19 PM, robert.kydd(a)gmail.com wrote: > Hi > My users are upset that when their mail is waiting moderation release they receive this message: > > 'Your mail to 'Members' with the subject > > AW: [Members] Hamburg 2019 > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list' > > Is their a way to change the text "post by a non-member to a members-only list" as they are registered members of the Joomla site > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 2 months

[MM3-users] Re: Mailman Suite installation on CentOS 7

by Mark Sapiro

On 11/8/21 4:18 AM, Kimmo L wrote: > Hello! > > I want to install fresh Mailman, which is combined with hyperkitty+postorius. After checking documentation i found, that Mailman Suite is perfect for me. > But i have some misunderstandings about installation. I only found this part in documentation, which explains how to clone and start using Mailman Suite (https://docs.mailman3.org/en/latest/devsetup.html#run-the-mailman-suite-com…) > > But am i correct, that before doing so, i need to install mailman core, mailman client, django-mailman3 ? > Or what would be the correct steps to build up my first Mailman Suite on CentOS? The docs you want to look at are https://docs.mailman3.org/en/latest/#the-pre-installation-guide and https://docs.mailman3.org/en/latest/install/install.html. There is also information at https://wiki.list.org/x/17891998 and in docs linked from thefirst paragraph thereof. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Messages not picking up header or footer template

by Mark Sapiro

On 2/26/23 13:04, benjamin(a)tougshire.com wrote: > > I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… > > I can do a wget on that uri and download a copy of the footer, and it looks right > > But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive > > Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message Can you see an attempt to GET /mailman3/api/templates/list/testing.comms.sdcvirginia.org/list:member:regular:footer in your web server's logs? Is there anything in Django's log? -- 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: Social signup?

by Mark Sapiro

On 3/15/23 05:08, Duane Raymond wrote: > > I'll jump over to the developers list when I start this (I'm about to > travel for a week to run an annual event in Oxford - so the far removed > from programming)...but which chatGPT suggested so far was > > 1. Extending postorius/signups.html with a loop to get the configured > social login providers PLUS adding a csrf_token field to the form > 2. Modifying postorius/views.py (which doesn't seem to exist but there > is a postorius/views folder) - so perhaps this is views/urls.py This is not what you want to do for this. The changes need to be in django-mailman3, not postorius. I have attached a patch which might work for you. I think it is good, but some of the wording is stuff that may not be appropriate. See what you think. -- 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: unrequested unsubscription

by Mark Sapiro

On 6/14/23 19:40, Mike Wertheim wrote: > I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. > > A few of the list members are reporting that they received Email Address > Unsubscription Confirmation emails, but claim that they never requested to > be unsubscribed. (All are Gmail users. but they might be coincidental, > since most list members are Gmail users.) > > Has anyone seen this behavior before? Any ideas on what might be happening? Yes. This is someone sending an email `leave` or `unsubscribe` command for the user in question. This may be malicious, i.e. someone doesn't like a user's posts and tries to unsubscribe them, or it may be just spam of some sort. the user should just ignore the email. Beyond that, there's not much you can do unless you can identify from mail logs the source of the requests. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

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

by Jeremy Stanley

On 2023-09-09 01:21:32 +0900 (+0900), Stephen J. Turnbull wrote: [...] > We could easily have an option to not attach the messages to the > notifications, just a list of most useful headers, or simply a > statement of how many if you really want to be minimal. A number of our lists would probably make use of that if it were an option, though sadly my dance card is too full to code the feature any time soon. Checking list moderation pages directly isn't a huge deal anyway, I mean I have something like 20 browser tabs perpetually open to the moderation queues for lists I personally handle and just refresh them every morning to see if there's anything that needs attention (I do get the notifications but tend to only skim them in case there's something urgent, though I also run my own MTA for my personal mailboxes so there's no risk of the postmaster getting concerned and banning them). -- Jeremy Stanley

2 years

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

by Markus Grandpré

Dear Mr Odhiambo, that is what i see in mail.log 1) when sending an e-mail to list that owns an *imported* archive. This list does *not* distribute a received e-mail to any list member: 2024-11-12T10:42:25.921700+01:00 mailman-app-test postfix/smtpd[736246]: connect from mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962093+01:00 mailman-app-test postfix/smtpd[736246]: EACD47C: client=mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962943+01:00 mailman-app-test postfix/cleanup[736250]: EACD47C: message-id=<523343bc-3789-443e-8404-98a13d1e0adf(a)uni-konstanz.de> 2024-11-12T10:42:25.967472+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: from=<markus.grandpre(a)uni-konstanz.de>, size=9650, nrcpt=1 (queue active) 2024-11-12T10:42:25.967630+01:00 mailman-app-test postfix/smtpd[736246]: disconnect from mailout.uni-konstanz.de[134.34.240.38] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:42:26.059198+01:00 mailman-app-test postfix/lmtp[736251]: EACD47C: to=<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.11, delays=0.02/0.01/0/0.08, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:42:26.059525+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: removed 2) when sending an e-mail to list that does *not* own an (imported) archive. This lists distributes a received e-mail to all list members: 2024-11-12T10:42:25.921700+01:00 mailman-app-test postfix/smtpd[736246]: connect from mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962093+01:00 mailman-app-test postfix/smtpd[736246]: EACD47C: client=mailout.uni-konstanz.de[134.34.240.38] 2024-11-12T10:42:25.962943+01:00 mailman-app-test postfix/cleanup[736250]: EACD47C: message-id=<523343bc-3789-443e-8404-98a13d1e0adf(a)uni-konstanz.de> 2024-11-12T10:42:25.967472+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: from=<markus.grandpre(a)uni-konstanz.de>, size=9650, nrcpt=1 (queue active) 2024-11-12T10:42:25.967630+01:00 mailman-app-test postfix/smtpd[736246]: disconnect from mailout.uni-konstanz.de[134.34.240.38] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:42:26.059198+01:00 mailman-app-test postfix/lmtp[736251]: EACD47C: to=<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.11, delays=0.02/0.01/0/0.08, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:42:26.059525+01:00 mailman-app-test postfix/qmgr[736016]: EACD47C: removed 2024-11-12T10:44:11.500683+01:00 mailman-app-test postfix/smtpd[736314]: connect from mailout.uni-konstanz.de[134.34.240.59] 2024-11-12T10:44:11.531183+01:00 mailman-app-test postfix/smtpd[736314]: 81A2B7C: client=mailout.uni-konstanz.de[134.34.240.59] 2024-11-12T10:44:11.532139+01:00 mailman-app-test postfix/cleanup[736316]: 81A2B7C: message-id=<802848fd-713b-4318-af7b-f868728edae3(a)uni-konstanz.de> 2024-11-12T10:44:11.535226+01:00 mailman-app-test postfix/smtpd[736314]: disconnect from mailout.uni-konstanz.de[134.34.240.59] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 2024-11-12T10:44:11.535529+01:00 mailman-app-test postfix/qmgr[736016]: 81A2B7C: from=<markus.grandpre(a)uni-konstanz.de>, size=9595, nrcpt=1 (queue active) 2024-11-12T10:44:11.564063+01:00 mailman-app-test postfix/lmtp[736317]: 81A2B7C: to=<nochntest(a)mailman-test.uni-konstanz.de>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.01/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) 2024-11-12T10:44:11.564429+01:00 mailman-app-test postfix/qmgr[736016]: 81A2B7C: removed 2024-11-12T10:44:14.144185+01:00 mailman-app-test postfix/smtpd[736314]: connect from localhost[::1] 2024-11-12T10:44:14.149134+01:00 mailman-app-test postfix/smtpd[736314]: 245CC7C: client=localhost[::1] 2024-11-12T10:44:14.150698+01:00 mailman-app-test postfix/cleanup[736316]: 245CC7C: message-id=<802848fd-713b-4318-af7b-f868728edae3(a)uni-konstanz.de> 2024-11-12T10:44:14.155543+01:00 mailman-app-test postfix/qmgr[736016]: 245CC7C: from=<nochntest-bounces(a)mailman-test.uni-konstanz.de>, size=11569, nrcpt=2 (queue active) 2024-11-12T10:44:14.155843+01:00 mailman-app-test postfix/smtpd[736314]: disconnect from localhost[::1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 2024-11-12T10:44:15.883334+01:00 mailman-app-test postfix/smtp[736318]: 245CC7C: to=<christian.mack(a)uni-konstanz.de>, relay=thurn.uni-konstanz.de[134.34.240.38]:25, delay=1.7, delays=0.01/0.02/0.04/1.7, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4XnhML1WGSz1q) 2024-11-12T10:44:15.883517+01:00 mailman-app-test postfix/smtp[736318]: 245CC7C: to=<markus.grandpre(a)uni-konstanz.de>, relay=thurn.uni-konstanz.de[134.34.240.38]:25, delay=1.7, delays=0.01/0.02/0.04/1.7, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4XnhML1WGSz1q) 2024-11-12T10:44:15.883730+01:00 mailman-app-test postfix/qmgr[736016]: 245CC7C: removed Postfix and mailman configurations for 1) and 2) are the same. With kind regards, Markus Am 12.11.24 um 10:27 schrieb Odhiambo Washington via Mailman-users: > On Tue, Nov 12, 2024 at 11:52 AM Markus Grandpré < > markus.grandpre(a)uni-konstanz.de> wrote: > >> Dear Mr Odhiambo, >> >> thank you very much for your reply. >> >> In mailman.log I see: >> >> Nov 12 09:46:02 2024 (698086) ACCEPT: >> <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de HTTP/1.1" >> 200 486 "-" "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/import_mm3_testliste(a)mailman-test.uni-konstanz.de/config >> HTTP/1.1" 200 3446 "-" "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/users/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 285 "-" "GNU >> Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/import_mm3_testliste.mailman-test.uni-konstanz.de/roster/owner >> HTTP/1.1" 200 789 "-" "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/addresses/markus.grandpre(a)uni-konstanz.de HTTP/1.1" 200 436 "-" >> "GNU Mailman REST client v3.3.5" >> [12/Nov/2024:09:46:03 +0100] "GET >> /3.1/lists/ >> import_mm3_testliste.mailman-test.uni-konstanz.de/roster/moderator >> HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.5" >> Nov 12 09:46:03 2024 (698083) HyperKitty archived message >> <d6723f50-7ca8-4ba9-85ef-bb5575dacd75(a)uni-konstanz.de> to >> >> https://mailman-test.uni-konstanz.de/mailman3/hyperkitty/list/import_mm3_te… > > > Is that ALL you have from mailman.log for today,? I was expecting more - > like some task runners being logged. > > > In smtp.log I found: >> >> Nov 12 09:46:02 2024 (698087) Available AUTH mechanisms: LOGIN(builtin) >> PLAIN(builtin) >> Nov 12 09:46:02 2024 (698087) Peer: ('127.0.0.1', 57230) >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) handling connection >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'LHLO >> mailman-app-test.kim.uni-konstanz.de' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'MAIL >> FROM:<markus.grandpre(a)uni-konstanz.de> SIZE=9649 BODY=8BITMIME' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) sender: >> markus.grandpre(a)uni-konstanz.de >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'RCPT >> TO:<Import_mm3_testliste(a)mailman-test.uni-konstanz.de>' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) recip: >> Import_mm3_testliste(a)mailman-test.uni-konstanz.de >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'DATA' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) >> b'QUIT' >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) connection lost >> Nov 12 09:46:02 2024 (698087) ('127.0.0.1', 57230) Connection lost >> during _handle_client() >> >> I have no idea why there is a "connection lost". What do you think? > > > That 'connection lost' is normal. > So there seems to be communication from mailman to your MTA. > What do you see in your MTA (Postfix?) logs when you send an email to the > list? > > > >> How can I increase the log level? >> > Actually, you do not need to, but mailman.cfg complete documentation is > here: > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > > > > > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

10 months

[MM3-users] Bounce processing

by Andrew Hodgson

Hi, Just upgraded to Mailman 3.3.1 at the beginning of the week and its very refreshing to have bounce processing working after all this time, stops the continued delivery to dud email addresses causing problems with junk email scoring. Anyway after a few days of using this I have noted the following feedback: When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. Thanks. Andrew.

5 years, 4 months

[MM3-users] Equivalent of listadmin Perl script for Mailman 3?

by Stephen J. Turnbull

Philip Colmer writes: > We're preparing to migrate about 4 Mailman 2 servers to Mailman 3. In doing > so, one of our list administrators has informed us that he uses "listadmin" > Does anyone know if there is an equivalent tool that works with Mailman 3? I don't know of one, but perhaps someone does. It probably wouldn't be hard to write a bare-bones workalike if the admin has shell access to the mailman host. UIn theory, shell access could be restricted to running the tool by using a 'command' option in the sshd authorized_keys file for the user's key. But I'm not competent to judge how secure that could be in principle, and of course if the tool is buggy in certain ways, all bets are off.) I can't estimate how hard it would be to write one without shell access, as I'm not sure how amenable the Postorius web UI is to scripting. Steve

3 years, 9 months

[MM3-users] Re: Pd CRON mailman gatenews

by Pierre Malard

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

2 years, 6 months

[MM3-users] Re: Where is postorius.wsgi?

by Simon Hanna

On 01/26/2018 11:18 AM, Peter Münster wrote: > On Fri, Jan 26 2018, Peter Münster wrote: > >> ImportError: No module named settings > Ok, I've found the solution: > > In wsgi.py: > > import sys > sys.path.append('/srv/www/htdocs/ckc3r/postorius/example_project') > > > But now, I get another error: > > File "/usr/lib/python2.7/site-packages/postorius-1.1.2-py2.7.egg/postorius/views/rest.py", line 33, in <module> > from django_mailman3.lib.scrub import Scrubber > File "/usr/lib/python2.7/site-packages/django_mailman3-1.2.0a1-py2.7.egg/django_mailman3/lib/scrub.py", line 26, in <module> > from email.message import EmailMessage > ImportError: cannot import name EmailMessage > > What should I do please? You appear to be using a prerelease version of django-mailman3 which is not compatible with the other parts. Install an earlier version and it should work. You also appeared to have used Python3 for the frontend in earlier posts. Currently Python3 is not yet supported. The next stable releases will most likely support Python3 and drop support for Python2

7 years, 7 months

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

by Manos Pitsidianakis

Hello, I've been getting "Cannot connect to SMTP server localhost on port 25" from runner "out" in mailman.log over some mails stuck in shunt queue, postfix logs show nothing when this happens, tcpdump on lo interface port 25 shows nothing. The log shows up when I start mailman, and then it seems not to show up again. This is my mailman.cfg's relevant parts: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix I can do 'telnet localhost 25' just fine, including as mailman user. I can send and receive mail on my mail server. I tried making a test list and sent/received messages fine. smtp debug logs show "Using agent: <mailman.mta.deliver.Deliver object at 0x7fdd9793c940>" and "IndividualDelivery to: <email(a)address.tld>" on repeat, where the email address is one of the addresses of the shunted mails. version 3.2.2

5 years, 11 months

[MM3-users] Re: Python is updated

by Mark London

Because of my own personal horror stories of waking up to finding high priority linux servers broken, due to nightly automated updates, I now prevent automatic updates on my servers. I only do manual security updates. In addition to implementing modern security techniques for our network. That is just my personal belief system. It's worked for the past 25 years. The only time we ever got hacked, was because of some stupid php scripts that our developers had put online, or because people's passwords had become leaked. And some of those situations were nightmares also. In two case of which, happened while I was away on vacation, and I had to fix everything remotely. But that was never due to updates. I probably shouldn't express my opinion. But I have a lot of empathy for the guy who discovered his mailman broken due to upgraded Python. Which triggered my nightmares. But it's great though to have a very responsive community here, to bring people back from the dead. - Mark

2 years, 4 months

[MM3-users] Re: Ready to try installation: use "normal" install or docker.

by Tom Browder

On Tue, Aug 1, 2017 at 12:28 Abhilash Raj <raj.abhilash1(a)gmail.com> wrote: > Hi Tom, .... > On Tue, Aug 1, 2017, at 07:54 AM, Tom Browder wrote: > > I'm leaning toward installing using the docker method but I would > > appreciate any recent thoughts about which method to choose. > > It really depends on what way you want to go, container images will be > much less hassle to use right now, mostly because all the dependencies > are bundled in and the moving parts are already configured to work with > each other. Abhilash, thanks for the response. My goal is to use the installation in production immediately (production meaning using some interested friends as testers before opening lists to "real" subscribers). If I understand properly, the docker way will be a good path to do that and it should make my volunteer maintenance life easier in the future, too. Does that sound reasonable? -Tom

8 years, 1 month

[MM3-users] Re: How to store additional information about lists?

by Stephen J. Turnbull

Andreas Barth writes: > Not sure if this is the right approach, or if it wouldn't be more > appropriate to "just" replace the dependency on allauth in postorius, > and do all the magic in the frontend only (because that's where people > actually subscribe). If it's purely a matter of managing subscriptions by individual users, that's the path of least resistance, I think. I would not be surprised if there are things you don't actually need, but you'd need to implement so that Postorius doesn't blow up if some IMember feature you haven't implemented gets accessed. If in the future you might have an external personnel database with other stuff in it, and you want Mailman automatically synced to that, then IMember now might make sense to avoid technical debt in the future. But I don't know enough about IMember or your use case at the moment to make a useful recommendation. Steve

4 years, 3 months

[MM3-users] Adding users

by horvath.arpad.szfvar＠gmail.com

Hi, I've tried to add new members to the mailing list, but I failed even if I tried 3 ways: - manage.py shell - invitation letter - sending a letter to subscribe. I try to solve it with the Python shell now. Based on this site: https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode… I tried this one from Debian bash command line, but there is an error message, as you can see at the end. # pwd /usr/share/mailman3-web # ./manage.py shell In [1]: from mailman.interfaces.usermanager import IUserManager In [2]: from zope.component import getUtility In [3]: user_manager = getUtility(IUserManager) --------------------------------------------------------------------------- ComponentLookupError Traceback (most recent call last) <ipython-input-3-9500ce4250f0> in <module> ----> 1 user_manager = getUtility(IUserManager) /usr/lib/python3/dist-packages/zope/component/_api.py in getUtility(interface, name, context) 167 if utility is not None: 168 return utility --> 169 raise ComponentLookupError(interface, name) 170 171 def queryUtility(interface, name='', default=None, context=None): ComponentLookupError: (<InterfaceClass mailman.interfaces.usermanager.IUserManager>, '') What do I wrong. Should I stop all my mailman processes first? Thanks, Arpad

2 years, 10 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 12/5/19 1:40 PM, ikemulder(a)hotmail.com wrote: > > In the script I am filtering for 'mhonarc' ListArchivers, since the duplicate ListArchivers always seem to be mhonarc archivers. > > If this is not the appropriate place, please let me know - I would like to get to the bottom of this :). I see you've also filed <https://gitlab.com/mailman/mailman/issues/657>. Thank you for that. We are as puzzled as you are by this. It would help if you could detect this duplication when it happens and try to get more information. The problem is I can't see how to do that. I would start by adding some logging to the patch_put method of the ListArchivers class in mailman/rest/lists.py to log the list and the request. Then when you see the duplicate, you can check this log to see if anything suspicious happened just prior to that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 12:21 PM, Mark Sapiro wrote: > On 10/29/20 8:51 AM, Brian Carpenter wrote: >> On 10/29/20 11:33 AM, Mark Sapiro wrote: >>> The real question is if a user has a subscription waiting confirmation >>> and the policy is changed to moderate, is a second request rejected >>> because of the request waiting confirmation. If so, I think this is a >>> bug which should be fixed. >>> >> Do you think this is a bug with Mailman core or my system? > > If the current policy is moderate and the user has a prior request > waiting confirmation and a new request is rejected because of the prior > request waiting confirmation, I think that is a bug in core, but I don't > know if that is the case or not. I think it is a bug in Mailman 3 core. I am seeing the same behavior on my Postorius server. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 10 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 2/8/21 1:22 AM, r.woithe(a)callassoftware.com wrote: > Hello, > > i did try the script and unfortunately there is a problem. The script is deleting django-users are not member,nonmember ... of any lists.But thats not the point. Its ok if a user want to be only a django-user to see the archives and work with them. If a user sign's up for an account at /accounts/signup/ and then confirms her address, she will then be a Mailman user with a user and an address record even though not a member of any lists. > The script should delete django-users who dont confirm your email address. Change one line in the script from ``` if mm_user is None or len(list(mm_user.memberships.members)) == 0: ``` to ``` if mm_user is None: ``` And it will do what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] DMARC DNS settings for MM3?

by Jay Hamilton-Roth

Emails from our list are currently being blocked by Google & Yahoo because of the "Dmarc policy of the sender domain" (according to Google Postmaster). Our list doesn't do any munging for "Reply goes to list" and our DMARC Mitigations is set for "No DMARC mitigations" and we're not DMARC Mitigating unconditionally. Given this is our MM3 policy, it's not clear what the DMARC DNS policy should be for consistency (note: we currently don't have a DMARC DNS setting). MM3 documentation doesn't have enough info, and reading up on DMARC Records it's not clear if we should be: v=DMARC1;p=reject;pct=100;rua=mailto:postmaster@ourdomain.com -or- v=DMARC1;p=quarantine;pct=100;ruf=mailto:postmaster@ourdomain.com -or something else- Our DNS' SPF record is: v=spf1 ip4:aa.bb.cc.dd +a +mx ~all [Note: aa.bb.cc.dd is a redacted address] I'd rather not experiment on DMARC record settings for fear of making a bad situation worse. Thanks in advance for any assistance.

3 years, 7 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect: - I put the variable in the mm-web-container-environment: mm-web: environment: - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org - Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' What am I missing, where do I have to set this value correctly? Thanks for the help! Jens. Am 08.06.23 um 01:57 schrieb Mark Sapiro: > On 6/7/23 14:13, Jens Günther wrote: >> >> The more important question would be, where :-) since I already >> checked if I can set it to something alse, I might need a hint where >> exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not >> stumble upon it. If you don't know it, no problem, let's just wait for >> somebody who does, thanks. > > > It's the EMAIL_CONFIRMATION_FROM setting in your Django settings. >

2 years, 3 months

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

by Mark Sapiro

On 3/20/24 14:25, Helio Loureiro wrote: > Hi, > > I keep receiving a lot of errors like this: > > --- Logging error --- > Traceback (most recent call last): ... > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > line 55, in unsign > raise BadSignature('Signature "%s" does not match' % sig) > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > does not match ... > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY > on setting.py are the same. Of those three, the api_key on mailman-hypperkitty.cfg and MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django thing and has nothing to do with the others. See https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key If you changed it, that's the issue. If you know what it was previously, you could set the previous value in SECRET_KEY_FALLBACKS, see https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: Bulk delivery status change?

by Mark Sapiro

On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: > >> Mistakes were made, and for while every single outbound email bounced. >> I've fixed the mistakes, but now in my largest and most active email list, >> every single user's delivery status is "Disabled by Bounces". >> >> Is there a way to bulk fix this? Or do I have to go into each user, one at >> a time, and fix them? > > Please see this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… The script in that post does all lists. For a single list see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… but note that the command line ``` $ shell -l list(a)example.com ``` should be ``` $ mailman shell -l list(a)example.com ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

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

by christian.schneider＠tu-dortmund.de

Hello, actually I am running the latest available Mailman-2 Version on Ubuntu 20.04! Now it is really time to move on! :-) I want to set up a new server (Ubuntu-24.04) and install Mailman-3 with the Virtualenv setup method: https://docs.mailman3.org/en/latest/install/virtualenv.html As I know from my old Mailman-2.1 the archives could get quite big... ;-) So it seems very important to provide enough (expandable) disk space at the right place. (I plan to use a seperate partition with LVM for the path in question) But I could find no information about the location where hyperkitty stores the archives on an Ubuntu-/Linux-system. I assume the archives are stored underneath "/var/..." this is only a guess. But is this guess right? Another question is: How much space do I have to plan (roughly) for the "/opt"-partition for the mailman install if the archives are stored under "/var/..."? Any guidance ist very much appreciated! Thank you very much Chris

5 months

[MM3-users] Re: New platform administrators

by Abhilash Raj

On Tue, Sep 18, 2018, at 1:14 PM, Simon Hanna wrote: > On 9/18/18 5:42 PM, Hellen Cubero wrote: > > Hello! > > I would like to know how to add a new site administrator to the mailman 3.2 > > platform. Can you help me please? > > You are probably referring to Postorius the webui? > > If yes, you just add another superuser. If the admin is enabled, you can > just visit https://you-url/admin sign in, and create a new user with > staff and superuser permissions. > > You can also do that on the cli using ./manage.py createsuperuser A better way would be to ask them to sign-up as a regular user and then you can go into the Admin Console (/admin) and add flags for Superuser for the user you want to promote. Create Superuser and Django's create user interfaces don't tie up with all-auth, which creates problems because their EmailAddress records aren't created, like they should be. -- thanks, Abhilash Raj (maxking)

6 years, 11 months

[MM3-users] Python error, debian package, again

by Lars Schimmer

Hi! I did filed #248 in https://gitlab.com/mailman/hyperkitty/issues and tried to resolve this issue. Furst converted the database as noted in the ticket, no solution. Second search all unicode subject lines in DB for the specific mailinglist, and delete them all via hyperkitty web interface, no success, error still appears. As the error happens 10-12 time on strange times (6am 2:20 pm, 4:20pm), it does not look like a fixed cron job. Abhilash Raj (maxking) mentionend, it maybe a issue with mailman core trying to deliver the message to hyperkitty. But how can I remove those broken messages, or twitch hyperkitty to accept and discard them? Those 30-60 error messsages/day are really annoying and on the other side do not look fine for mailman3 to break at such a easy task. (could have discarded those messages, also). So, please, howto fix this? thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

5 years, 10 months

[MM3-users] hidden list is hidden even to the owner

by Mohsen Masoudfar

Hi, I am not sure, if it is designed this way, or I am doing something wrong. I created a list in MM3 as a hidden list, meaning: Show list on index page: NO and assigned the owner. When I login as Postorius web admin, I see the list on the list page which is listed as: (unadvertised*). This is fine. But when the owner or moderator login to Postorius they don't see the list at all. Of course if they add the list name at the end of the URL, they get to the list and as the owner can manage it too. My question is: I am just not sure, if I am missing something or this is how it is supposed to work? You could expect, that the owner or the moderator should see the list as (unadvertised*) too. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

5 years, 2 months

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

by Mark Sapiro

On 10/10/22 15:31, Mark Dale via Mailman-users wrote: > > Where and how do I set the default setting of "Delivery status" to be > "Enabled". It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… > I'm not seeing any clues in mailman3-web/settings.py > > At the moment, a new subscriber is neither "Enabled" or "Disabled". That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 19:09:20 CEST schrieb Mark Sapiro: > On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > > > All packages were upgraded fine. I applied the patch to > > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > > It shouldn't have been necessary to apply any patch. The head of the > GitLab hyperkitty master branch is already compatible with mistune 2.0.4 strange, I still had the line with the (not working) from mistune.scanner import escape_html, escape_url maybe because the migration step was not working at that time? > I'm guessing at some point you installed something which required you to > manually make this migration and that produced this conflict. Do you > have both 0017_alter_emailtemplate_language.py and > 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, > probably just removing 0017_auto_20220628_1132 will fix this? That's what I did in the meantime, and it works now! Thank you.

2 years, 11 months

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

by Mark Sapiro

On 4/29/25 00:17, Alexander Inzinger-Zrock via Mailman-users wrote: > [Status] > > Suggestion: > > It seems, we are wasting to much time with a probably messed up system. > I suggest, that i do as initially suggested [1] and start over with a > reinstall. > > Last idea before that would be to > > 1. delete the files: > > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_domains > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_domains.db > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_lmtp > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_lmtp.db > > 2. restart services > > 3. test if programms make new files > > 4. report to mailinglist > > Would that be of interest to someone? Yes. Also, is there anything in Mailman's logs from the time you ran `mailman aliases`? -- 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: Setting up on ubuntu server 22.04

by Stephen J. Turnbull

Kyriakos Terzopoulos writes: > Firstly, thank you for your kind support. It seems that there is > some misunderstanding there from my side, since I did not use the > github repo to install mailman - I did it through pip install. Right, I understood that. The point is you can create a requirements.txt file by using "python -m pip freeze > requirements.txt", edit that file as suggested in the GitLab issue, and run "python -m pip install -r requirements.txt". I prefer this method because it documents exactly what I had in the venv at any given point in time. I think that should only reinstall the package with the new constraint, but it may refuse to do any installation because everything is already installed. In that case you have to either use "--force-reinstall" in the pip command (which will reinstall *all* packages) or you can use "python -m pip remove importlib_resources" followed by "python -m pip install 'importlib_resources>=1.1.0,<6.0'". Steve

1 year, 11 months

[MM3-users] Re: subscribing to a list from a WordPress site

by Odhiambo Washington

On Mon, Dec 25, 2023 at 1:08 PM Johannes Rohr <johannes(a)rohr.org> wrote: > Dear all, > > is there a wordpress plugin/widget allowing visitors to subscribe to a > mailman3 hosted mailing list? Else, what is the most convenient way? Sure, > I > could just link to the maiman site, but since joining a list is as easy as > sending mail to LISTNAME-join, there should be a simple way to impement > this. > What is the best practice? > Such plugins existed 10 years ago and aren't maintained. I just checked by doing a search in the "Add new plugin" window. However, isn't it just as easy as creating a CTA button on your WP site, which you then link to your MM3 subscription page? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 8 months

[MM3-users] Re: Disable "confirmation emails"

by Jonas Meurer

Am 18.09.2018 um 23:25 schrieb Mark Sapiro: > On 09/18/2018 01:46 PM, Hagen Bauer wrote: >> >> even after a lot of google search I could not find a way to disable the >> Confirmation Mails like >> .... >> The results of your email command are provided below. >> >> - Original message details: >> ....... >> >> Is there a way to do this? I have users who would be irritated and I >> dont want them to recieve this > > > Where are you seeing these? There were changes in this area in Mailman > core v. 3.2.0 and I think these now should only be sent in response to > mail to the -request address that contains a command other than > (un)subscribe or confirm. I can confirm that these mails are sent in response to messages to -subscribe (not only to -request) with Mailman 3.2. I experienced the same as Hagen and I also wonder how to turn them of. Cheers, jonas

6 years, 11 months

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

by Mark Sapiro

On 9/18/21 2:52 PM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 18/9/21 22:59, Mark Sapiro wrote: >> On 9/18/21 11:56 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> >>> Just a one more silly question: >>> >>> Where do I can find the diferent values that memb.moderation_action >>> can take? (I want to prepare the "unhold" script too) >> >> >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/act… >> > > Thanks: It's perfect One more thing. It isn't obvious, but generally you want Action.defer rather than Action.accept. Action.defer will pass the moderation check, but still continue to check other rules such as administrivia, implicit-destination, max-recipients, max-size, no-subject and header filters whereas Action.accept will accept the message unconditionally and bypass those subsequent checks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Stephen J. Turnbull

Onyeibo Oku writes: (backtrace reformatted for readability) > Oct 22 04:13:55 mail.server.tld mailman[9253]: > File "/usr/lib/python3.10/site-packages/pkg_resources/__init__.py", > line 1616, in _get > Oct 22 04:13:55 mail.server.tld mailman[9253]: with open(path, 'rb') as stream: > Oct 22 04:13:55 mail.server.tld mailman[9253]: PermissionError: [Errno 13] > Permission denied: > '/opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO' That's just an ordinary attempt to read a file, nothing special about zope. It seems that that package was installed with the wrong ownership or permissions. Most likely you installed the package as root rather than the mailman user. Everything in a venv should be owned by the user:group it is intended for.[1] Assuming that the user that Mailman processes are running under is "mailman" with group "mailman", then chown -R mailman:mailman /opt/mailman/venv should do the trick. Steve Footnotes: [1] Probably there are applications where this is not true. But it is true for Mailman.

2 years, 10 months

[MM3-users] Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/23/23 08:42, Odhiambo Washington wrote: > On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Thanks both of you. I didn't know Debian11 version is out of date. I will >> try using pip. >> > No. Debian 11 is _not_ out of date. It's just that the preferred and easy > to support installation method is using the virtualenv. The Debian stable mailman packages definitely ARE out of date. bullseye (stable) has Mailman core 3.3.3 and django-mailman3 1.3.5 (current releases are 3.3.8 and 1.3.9 respectively) It is unclear what Postorius and HyperKitty versions are in mailman3-web 0+20200530-2. bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would install. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Managing users in postorius

by Lieuallen, Thomas Otis

In our environment, people have multiple email addresses, any/all of which might be used as members or admin addresses. I try to steer people in the right direction, but inevitably, we end up with people registering the ‘wrong’ address or even both addresses. I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. Thank you Tom Lieuallen Oregon State University

11 months, 3 weeks

[MM3-users] Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Mark Sapiro

On 3/31/25 06:26, Philip Bondi wrote: > My /etc/mailman3/urls.py is empty. > > Should I, like it indicates in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > cp /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py /etc/mailman3/urls.py > chown mailman:mailman /etc/mailman3/urls.py > and add to /etc/mailman3/settings.py > > ROOT_URLCONF = 'urls' You can do all of that, but it's probably unnecessary. What is in /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py? compare it to https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py > After completing above, https://systemdatabase.ca/mailman3 still gives > Service Unavailable It appears that https://systemdatabase.ca/postorius works so the issue is almost certainly that your urls.py is missing path('mailman3/', include('postorius.urls')), -- 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: Relay Access Denied

by Mark Sapiro

On 7/22/25 10:25 AM, jkoral(a)luc.edu wrote: > Here is what I have in postfox_lmtp. Do I need to add another line for joetest(a)lists.luc.edu as well? > > joetest(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-bounces(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-confirm(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-join(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-leave(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-owner(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-request(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-subscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-unsubscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 If you want to address the lists @lists.luc.edu, the list names should be, e.g. joetest(a)lists.luc.edu, not joetest(a)listservnew.luc.edu. If you want to be able to use either domain for list mail, that's more involved. If you want this, say so and as I have time I can make suggestions., but I suspect you really only want to use the lists.luc.edu domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: Member Issue Discovered

by Mark Dadgar

On Oct 20, 2020, at 9:13 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/20/20 8:53 PM, Mark Dadgar wrote: >> On Oct 20, 2020, at 8:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> Even in mailman 2.1, while a list admin could go to a user's options >>> page for the list and change things, the "change globally" check boxes >>> only worked for the user, not for the list admin. >> >> That was by design!? >> >> As an admin, that was so irritating. > > Yes, it was by design. Do you really think that list owners should be > able to enable or disable mail delivery, set digest format, user's > password, etc. for a user's subscription on lists that they don't own? Yeah, that makes sense for very large installations. Good point. IIRC, mm2 had the concept of a site-admin. It would be nice if it had worked for them, though. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 10 months

[MM3-users] Error message from monthly cronjob

by Johannes Rohr

Dear all, Mailman3 on my system is installed in virtualenv. Each month I get the following error message. This error does not seem to have a serious impact on the functioning of mailman, still, what does it mean and how do I get rid of it? Thanks for any hints! Johannes -------- Weitergeleitete Nachricht -------- Betreff: Cron <mailman@*** /opt/mailman/venv/bin/mailman-web runjobs monthly Datum: Fri, 1 Dec 2023 05:56:40 +0100 (CET) Von: Cron Daemon <root(a)mail.rooot.de> An: mailman@*** ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", line 177, in run_with_lock with lock: File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ self.unlock() File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 420, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

1 year, 9 months

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

by Ken Alker

As an aside, for anyone else who is trying to do the same (and to give some background into my procedures so far), I have been following these references: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-virtualenv> My goal is to create the least change to file locations and configuration files as possible (I may move things into more "source-installed centric" locations once I have things working again), thus, many files are still in the original Debian package-allocated directories. That said, I was forced to move mailman3web.db to /opt/mailman/web as sqlite (and, hence, mailman-web) simply could not open the database as user mailman from my virtual environment (even with mailman3web.db file permissions set to 777 and owner.group set to mailman.mailman). So far I've gotten mailman running properly and handling the mailing lists, however, I have not gotten the web interface working again.

2 years, 2 months

[MM3-users] REST API for list owners/moderators

by Stephen J. Turnbull

mathias(a)koerber.org writes: > Does Mailman 3 have an REST API that allows list-owners/moderators > to perform list-management functions without having access to the > whole server/other lists etc? No. You can provide selective access to a selection of REST API endpoints via a front-end webserver such as Apache or nginx, but it would be rather painful, and possibly also rather insecure.[1] > The documentation seems to only indicate a single one-admin-user > REST API that should not even be accessible from outside? That's right. If the documentation only "indicates" that, we should fix the documentation. The point of separating Postorius from core was to put authentication and authorization in the hands of people who know how to do it (ie, Django). Footnotes: [1] That depends on what threats you're worried about. But the endpoint hierarchy is designed to make sense to application programmers, not to make it easy to disable access to "dangerous" endpoints that allow deleting lists or extracting user information.

1 year, 8 months

[MM3-users] Re: How to get Mailman core to provide more debug info in a running environment

by Henrik Rasmussen

> From: Barry Warsaw [mailto:barry@list.org] > Sent: 28. september 2017 16:38 > >On Sep 28, 2017, at 07:28, Henrik Rasmussen <her(a)adm.ku.dk> wrote: > >> [logging.smtp-failure] >> path: smtp.log > > That’s a typo/leftover in the schema.cfg comments. There is no longer an smtp-failure log so [logging.smtp-failure] can’t be used. Oh okay. I suppose that smtp failures will be logged in the smtp.log by default then? Or otherwise, how do I increase logging if needed. For now I found the problem by consulting the mailman.log. > However you said that “stopped incoming mails”. Can you provide more information on exactly what happened? Bogus logging sections should effectively be ignored. Actually I think my Postfix docker container got confused when restarting the Mailman core container. I just associated it with my change in mailman-extra.cfg. -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

7 years, 11 months

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 6/6/19 6:02 AM, Henrik Rasmussen wrote: > > Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. You have to add the MIME types for the attachments you want kept the the list's pass_types. You need to do this via mailman shell or REST as it isn't currently exposed in Postorius. Here's an example from a list that wants to accept PDFs as well as word processing and spreadsheet documents. Note that nappdf and x-pdf are uncommon PDF subtypes that I have seen. ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword' ] -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: I like your style, but what is it?

by Mark Sapiro

On 1/26/21 9:12 PM, Stephen Willey Mats Mats wrote: > > How do I get a dump of list settings for each style. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py> and <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/default…>. > Thanks, > steve > > p.s. the search on https://mailman.readthedocs.io/en/latest/README.html gives results but every link needs to have ‘projects/mailman/‘ removed from the url to work. Or have its domain changed from `mailman.readthedocs.io` to `docs.mailman3.org`. If you start at <https://docs.mailman3.org/en/latest/> or just go to <https://docs.mailman3.org/projects/mailman/en/latest/README.html>, I think everything works. Granted, search from <https://mailman.readthedocs.io/en/latest/README.html> should work too, but I'm not sure offhand whether its a Sphinx or a Read the Docs issue or how to fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Mailman and Exim 4.94.2 (Debian Bullseye)

by Andrew Hodgson

Hi. I moved Mailman instance to a machine running Debian Bullseye last week. Ran into an issue with the Exim transport from this doc: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… The issue I ran into was that Exim wasn't able to resolve localhost in order to connect to the LMTP listener. I changed VPS provider at the same time (moved from Bytemark to Gandi) so not sure if they were doing anything different with DNS, but by default Exim doesn't use standard libraries to lookup hosts: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_dnslookup_… I solved the issue by using the following configuration on the Mailman router: # /etc/exim4/conf.d/transport/55_mm3_transport mailman3_transport: driver = smtp protocol = lmtp allow_localhost gethostbyname hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true I haven't defined the lmtp settings at all in mailman.cfg meaning they are using the default settings of 127.0.0.1:8024. Is this the best modification to make to the Exim config or should I go an alternative route? Thanks. Andrew.

3 years, 10 months

[MM3-users] Re: mailman3 digest sending questions and also adding docker to the mix

by Abhilash Raj

On Wed, Apr 13, 2022, at 3:35 PM, bob B via Mailman-users wrote: > No worries, I hoping Abhilash will respond to the docker, > > But for non docker installs I assume that it sends out digest daily? > when "Send Digest Periodically " is set to yes, is that correct? Docker install currently doesn’t run routine cron jobs in Core like it does in Hyperkitty. Part of the problem is that there is no engine to run the cron jobs in the container. I _should_ figure out a way to do that using supervisord or something similar inside the image, but that is still not there yet. There is https://github.com/maxking/docker-mailman/issues/420 which could use some help with fixes or even simply documentation udpates. > _______________________________________________ > 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)

3 years, 5 months

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

by Pierre Malard

Everithing is in the subject. We must add some (a lot) alias address for members and I don’t find any indications on doc to do that with « mailman » command. Is their a way? -- Pierre Malard « Il faut créer en même temps les élites et les débouchés, le syndica- lisme et les usines. Faire l'un sans l'autre, c'est travailler pour le malheur du peuple. » Romain Gary - "Les racines du ciel" |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 4 months

[MM3-users] Re: Which documentation to follow for installation

by Abhilash Raj

On Sun, 20 Aug 2017 20:50:39 +0200 (CEST) Ruben Ibanez <ribanez(a)sciops.esa.int> wrote: > Hi Abhilash, > > Thanks for your reply. > > The point is, I think I'm missing something. I'm just a sysadmin who wants to deploy Mailman 3.x to be used for an operational environment, like any other software. Is this software actually ready for that? There are production environments running Mailman 3.1 right now if that is your questions, see https://lists.mailman3.org. Although, I guess you already saw that when subscribing to this list ;) > Of course, I'm not asking for .rpm, .deb, etc... because I understand that's > quite complex, but I tried it following all available guides, including the > Contributor's Guide, and it seems impossible to get it running at the first > time (or just to get it running) without getting crazy or fixing lots of > unexpected errors during installation. It would be helpful if you send in those errors here. It will help us debug your problem and also improve the guide for the people using it in future. One small problem about the configuration, off the top of my head, can cause some problems in the "Mailman Suite Installation" Guide[1]. I have that on my todo to fix. But, apart from that everything else should work! [1]: http://docs.mailman3.org/en/latest/prodsetup.html You would have to do some additional configuration for the web frontend to work and for the mail servers to talk to Mailman and Frontend separately, both of which is also mentioned in the documentation under "Configuring Mailman Core" and "Configure Web Frontend". Contributor's guide is not focused on deploying but just setting it up locally to play with and modify the source itself. > Have you tried to deploy Mailman 3.x strictly following the documentation? I think people have used it in past to successfully deploy Mailman 3.x, but without looking at the errors you are facing I don't have any clue as to why it doesn't work for you! > > By the way, many thanks for your hard work! > > Cheers, > RI > > > From: "Abhilash Raj" <maxking(a)asynchronous.in> > To: ribanez(a)sciops.esa.int > Cc: mailman-users(a)mailman3.org > Sent: Saturday, August 19, 2017 8:55:20 AM > Subject: Re: [MM3-users] Which documentation to follow for installation > > On Fri, 18 Aug 2017 09:40:37 -0000 > ribanez(a)sciops.esa.int wrote: > > > Hi everyone, > > > > I'm trying to deploy Mailman 3.1, but it seems there isn't a clear place to > > look for documentation. I found two different sites: > > > > https://mailman.readthedocs.io/en/latest/ > > http://docs.mailman3.org/en/latest/ > > Both of the above are actually latest documentation, > > docs.mailman3.org should be the one to look for installations guidelines for > the entire Mailman 3.x Suite, > > mailman.readthedocs.io is the documentation of Mailman 3 Core, which handles > the mail. > > http://docs.mailman3.org/en/latest/prodsetup.html > > This should be the best place to start, be sure to look at the Pre-Installation > Guide if you are new to the Python ecosystem. > > > > > Do you know which one should be followed? Both at the same time? I find it > > quite unclear... and this installation will be for an operational environment. > > > > Also, there are some (official?...) docker images, but all images are for > > mailman 3.0 but not mailman 3.1, and of course updates are not guaranteed. > > It is meant for Mailman 3.X series and is maintained by me. It currently > includes the latest releases for all the Mailman's sub-projects, also Mailman > 3.1. > > > Hope that helps! > > -- thanks, Abhilash Raj

8 years

[MM3-users] Re: Mailman 3 api php

by Mark Sapiro

On 03/14/2017 05:24 AM, david.terni(a)gmail.com wrote: > Hi, > I apologize if this is't the right place but I don't understand how connect mailman 3 with api and php/CURL. It's possibile to do it? I tried to use the same url used with mailman2 but doesn't work. Mailman 3 is completely different from Mailman 2 in this respect. While it would be possible to use php/CURL to post to Postorius analagously to posting to the Mailman 2 web UI, this is not how it is done. Mailman 3 core exposes a RESTful api on localhost. Both Postorius and HyperKitty use this UI to communicate with the core and you should too. Start at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/rest/docs/basic.ht…>. The "Previous" link will take you to the section on Addresses and the "Next" links will take you through the rest of the REST api. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: Mailman 3 on RHEL 7 help

by Abhilash Raj

On Thu, Oct 25, 2018, at 4:24 PM, A Almeda wrote: > Hi. I am trying to install mailman 3 on RHEL7. Docker install is not a > possibility. I am trying to install it using a bundler by following > https://media.readthedocs.org/pdf/mailman-bundler/stable/mailman-bundler.pdf, > but after logging in as mailman, I can't do virtualenv venv. It works if > I login as root, but still fails during buildout. That document is quite a bit old. You can find the latest instructions here[1], if you face issues with instructions in there, please let us know. [1]: http://docs.mailman3.org/en/latest/prodsetup.html > > In short, I need help. Has anyone of you guys installed mailman 3 on > RHEL 7 or CEntOS 7? If so would you share me detailed instructions? > Thank you in advance. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

6 years, 10 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On 4/16/19 9:18 AM, brian(a)emwd.com wrote: > Thanks Mark. I added the POSTORIUS_TEMPLATE_BASE_URL to my settings: > > /opt/mailman/web/settings_local.py > > Now I get the following errors: ... > requests.exceptions.SSLError: HTTPSConnectionPool(host='mailman3.emwd.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/testlist.mailman3.emwd.com/list:user:notice:welcome (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)'),)) > Apr 16 15:38:44 2019 (28) 172.19.199.3 - - "POST /3.1/members HTTP/1.1" 500 59 > > I am confused by the SSL errors. I have a valid SSL certificate installed on mailman3.emwd.com. These errors occur whether the POSTORIUS_TEMPLATE_BASE_URL is using http or https. I'm confused too. What happens if you just do in a python3 interactive session >>> import requests >>> response = requests.get('https://mailman3.emwd.com/postorius/api/templates/list/testlist.mailman3.em…') and if you get this far >>> response.status_code >>> response.text -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Customising hyperkitty and postorius

by Mark Sapiro

On 11/18/20 5:16 PM, peter(a)chubb.wattle.id.au wrote: > > Hi, > I've put up a mailman3 instance, with hyperkitty enabled, and > imported all my mailman2.1 archives -- it all seems to be > working. > > How do I now customise the look and feel of my site? > > In particular, I'd like to render archived emails with a > monospace font, and I'd like to change the colour scheme and > styles of all the pages to match other pages on the same website. HyperKitty will display a message in monospace if you click the 'A' icon at the bottom of the message. I don't know offhand how you would make that the default. For styles, they are mostly SCSS in the directory hyperkitty/static and CSS in the directory postorius/static/postorius. I think you'd have to find the relevant styles and edit them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Brian Carpenter

On 3/26/21 6:13 PM, Mark Sapiro wrote: > Absolutely. At first MM3 wasn't processing bounces at all. A GSOC student did the bulk of the current implementation and we were happy to get that even though this piece was missing. We know we need it. If you don't think we're working fast enough, you can submit a merge request or dock our pay. I don't understand the sarcasm here at all. I am just trying to figure out what the PRIORITIES are from the Mailman 3 developers. That's all. BTW, I still haven't figured it out. It still doesn't explain why Postfix is not recording the delivery issues which I assume has nothing to do with Mailman 3. I see successful deliveries with Postfix and bounces with Mailman 3 core. I never seen that with Mailman 2 and Exim. They always matched. If you can help me to understand that with out the petty sarcasms then that would be great. If not, then ok. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 5 months

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

by Odhiambo Washington

On Sun, Oct 1, 2023 at 1:41 PM Wikinaut <mail(a)tgries.de> wrote: > > Maybe you can make your life a little more bearable by abandoning the > use of Debian packages and embracing the virtualenv.... > > I fully understand. Need to look up how to smoothly backup the mailman3 > settings and list databases in order to make that move with losing stuff... > (kinda "mailman3 backup all" and mailman3 restore all" :-) > You do not really need to change much. The /etc/mailman3/* are almost usable as it with a little modification to file paths. The databases are also usable as-is. You may need to move a few files to the virtualenv directory tree and change permissions accordingly. -- 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] Cannot setup announce-only mailing list

by Alberto Granzotto

Dear all, I don't understand how to set up an "announce only" mailing list using Postorius Version 1.2.4. What I do is the following: - Click on "Create New List" - From "List Style", select "Announce only mailing list style." - Fill all other fields in the form - Click "Create list" At this point people can subscribe to the newly created announce mailing list. If they add themselves they end up in "List Members", and if they email the announce mailing list, their email is relayed to all other members, just like a normal mailing list :/ Moreover, subscribers get this message, inviting them to post to the announce only mailing list: > Welcome to the "Test-announce" mailing list! > > To post to this list, send your email to: > > test-announce(a)lists.dist0rtion.com Of course, I want to keep this mailing list "read only" for members, and I want only selected people to post to that mailing list. Any idea on how to achieve that? Best, Alberto

5 years, 7 months

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

by Mark Sapiro

On 12/10/2016 12:52 AM, Barry Warsaw wrote: > > Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. Done. There is one "temporary" commit in my MR to work around <https://github.com/sphinx-doc/sphinx/issues/3212> and get "docs" to pass. >> I can also work on Postorius. Also in this vein I have a question. >> Should the DMARC settings be added to the Alter Messages tab in the List >> Settings view or would it be better to have a separate DMARC Mitigations >> tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I have a WIP MR at <https://gitlab.com/mailman/postorius/merge_requests/194> that adds a tab. Maybe Florian and Terri can look at that and chime in. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command

by Mark Sapiro

On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- 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: Alias for a list name

by Mark Sapiro

On 10/6/23 09:49, Lars Bjørndal wrote: > > To run mm 3 through Postfix, I use local_recipient_maps and > transport_maps. > > What I want to achieve, is alias medlem(a)list.saf-org.no to > saf-medlem(a)list.saf-org.no > > I tried to put > > medlem(a)list.saf-org.no: saf-medlem(a)list.saf-org.no > > and get the following error when running newaliases: > > postalias: warning: /etc/aliases, line 231: name must be local > > Is it possible to do this aliasing in a simple way? If list.saf-org.no is a local domain, i.e. in mydestination, the alias would be medlem: saf-medlem(a)list.saf-org.no or more simply medlem: saf-medlem If list.saf-org.no is not a local domain it needs to be a Postfix virtual (alias or mailbox) domain and you need a virtual_alias_maps with an entry like medlem(a)list.saf-org.no saf-medlem(a)list.saf-org.no -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Help! Duplicate DKIM key

by Jose Bernal

Hi all, I'm having *sudden* issues with our SMTP server (Amazon SES) erroring out while trying to send from our most active Mailman3 mailing list (~1,000 subscribers; modest Mailman3 (v 3.3.3) installation (10+ lists, Ubuntu). Here is the message. We've got several thousand log entries like this now: *554 Transaction failed: Duplicate header 'DKIM-Signature'* Mar 10 08:31:10 mail1 postfix/smtp[217753]: 738B53F15E: to=< brian(a)brianmichaelslaw.com>, relay=xxx.org[44.225.xxx.xx]:587, delay=37, delays=2/35/0.16/0.13, dsn=5.0.0, status=bounced (host said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) As we don't do any DKIM key signing on the related Postfix machine I've opened up a case with Amazon. However, if there is a troubleshooting I should adopt on this issue with regard to Postfix/Mailman I'd like to know what your recommendations are, or what steps I can follow to better help the vendor ensure that this issue isn't coming from either the Postfix machine or the Mailman machine. Much thanks, --------------------- José Bernal Web/Application Engineer

6 months, 1 week

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sat, Dec 24, 2022 at 1:51 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/22 22:26, Odhiambo Washington wrote: > > On Fri, Dec 23, 2022 at 9:21 AM Odhiambo Washington <odhiambo(a)gmail.com> > > wrote: > > > >> And now I am having a problem with mod_wsgi. > >> First, the URL displayed when I load the page looks bogus to me. > >> While I expect the URL to be > >> https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me > >> https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is > an > >> extra /mailman3! > > > See below: > > > >> So I have; > >> 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - > working, > >> or appears to. > >> 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - > working, > >> or appears to. > >> 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, > or > >> appears to > >> 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, > or > >> appears to > >> 5. > >> > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… > >> - This throws an exception error when I click "Manage Subscription". > >> > >> -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ > > > messages like these > > [Fri Dec 23 09:10:55.393386 2022] [wsgi:error] [pid 74857] [remote > 197.232.81.246:14181] File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", > > line 160, in call > [Fri Dec 23 09:10:55.393390 2022] [wsgi:error] [pid 74857] [remote > 197.232.81.246:14181] raise HTTPError(params.get('url'), > response.status_code, > [Fri Dec 23 09:10:55.393394 2022] [wsgi:error] [pid 74857] [remote > 197.232.81.246:14181] urllib.error.HTTPError: HTTP Error 500: {"title": > "500 Internal Server Error"} > > Indicate an uncaught exception in Mailman core. What's in mailman.log? > A good catch here! mailman.log was mostly having a complaint about a missing config file - /etc/mailman3/mailman-hyperkitty.cfg I then just did a symlink: ln -s /opt/mailman/mm /etc/mailman3, which then made things start working. And I don't like this, so I think I will put all my configs into /opt/mailman/mm/etc/ and link /etc/mailman3 to this path instead. What bite me is probably related to this experience by Turnbull: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I am on FreeBSD where user applications should have config files in /usr/local/etc/ and not /etc/ so having /etc/mailman3 and not /usr/local/etc/mailman3 kinda makes me feel weird. >> And while I do not quite understand the error itself, there is also one > >> particular line that I also saw that has left me baffled: > >> [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client > >> 197.232.81.246:13865] AH00128: File does not exist: > >> /usr/local/www/apache24/data/archives/list/ > >> kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, > >> referer: > >> > https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke > > This is because something is doing an HTTP GET for > `/archives/list/ > kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/` > <http://kictanet@lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJE…> > and the URL is not recognized as one handled by mod_wsgi so apache tries > to get it from its DocumentRoot. > > mod_wsgi has to serve a number of URLs. Look in /opt/mailman/mm/urls.py > for urlpatterns. You will probably see things like > > url(r'^accounts/', include('allauth.urls')), > # Django admin > url(r'^admin/', admin.site.urls), > url(r'^mailman3/', include('postorius.urls')), > url(r'^archives/', include('hyperkitty.urls')), > > Those are all things that need to be handled by mod_wsgi > > In your apache config, you only have a WSGIScriptAlias for /mailman3. > Thus paths need to be prefixed with /mailman3 in order to be handled by > mod_wsgi. I'm not sure what is doing this prefixing, but without it > paths that don't begin with /mailman3 don't work unless you also have > things like > > WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > > in your apache config. > These are my files: 1. urls.py <CUT > from django.conf.urls import include from django.urls import re_path from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView urlpatterns = [ re_path(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')), re_path(r'', include('django_mailman3.urls')), re_path(r'^accounts/', include('allauth.urls')), # Django admin re_path(r'^admin/', admin.site.urls), re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), ] </CUT> 2. apache.conf <CUT> ... Alias /static "/opt/mailman/mm/static" <Directory "/opt/mailman/mm/static"> Require all granted </Directory> # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py WSGIScriptAlias / /opt/mailman/mm/wsgi.py <Directory "/opt/mailman/mm/"> <Files wsgi.py> Order deny,allow Allow from all Require all granted </Files> WSGIProcessGroup mailman-web </Directory> <CUT> > > I also need to add the fact that at the point where I am clicking "Manage > > Subscription", the URL has changed to > > > https://mm3-lists.kictanet.or.ke/mailman3/archives/list/kictanet@lists.kict… > > (just a single /mailman3). > > > > > Something is adding mailman3/ to URLs. In the above the URL should be > > https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k…, > > but an extra /mailman3 is added. The others are like > https://mm3-lists.kictanet.or.ke/mailman3/lists/ and an extra /mailman3 > is added. > I have tested with creating all those commented out aliases and that ended up still giving me /mailman3/mailman3/* which I did not like, although everything appeared to work. I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" and now when I type https://mm3-lists.kictanet.or.ke I end up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course something has appended "/mailman3" So this has resulted in all URLs having /mailman3/ appended, except for the /archives link. Now my question is about what could be adding the /mailman3. Is it possible that I installed something out of the ordinary? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

Mark Sapiro wrote: > I just did a test on my development system and I see the same timeout > error, so it's not just you. I'll work on this. This is very strange. In my test, I see this in the apache log: 127.0.0.1 - - [26/Apr/2024:08:59:25 -0700] "GET /mailman3/api/templates/list/test.msapiro.net/list:user:notice:welcome HTTP/1.1" 200 4215 "-" "python-requests/2.28.1" I.e., apache gets the request and serves the template, and then 5 seconds later I see Apr 26 08:59:30 2024 (2592) deque: Traceback (most recent call last): ... socket.timeout: The read operation timed out I also note that this timeout only occurs when it is a subscription via REST. I.e. subscription via email or `mailman addmembers` sends the proper welcome message. So it has something to do with the retrieval being done by a rest runner, but I still don't know what the underlying issue is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: How to see the admin password reset in docker with mailman3

by Mark Sapiro

On 4/6/23 13:48, bob B via Mailman-users wrote: > I am setting up a new environment of Mailman3 in docker. I understand I have to reset the password to set the password for admin. I go to forget the password, in the GUI and I put in the address I have listed in the docker-compose.yaml and I never get the email. I look at the mail log on the host and I do not see the smtp connections. I assume Django is not using the docker host but sending the mail directly?? > > Basically, where can I see the password email rest mail logs to make sure an email was sent out and where it is going? I can't answer that question, but you can set an admin user and password with the django admin createsuperuser command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Apache shows No Lists

by Odhiambo Washington

mailman3 createsuperuser? On Mon, May 22, 2023, 22:58 <ceo(a)sartrack.nz> wrote: > Postorius is running. > I just removed all mailing lists, and created new empty ones. > These now show in the Apache2 website, via the link to Postorius I assume. > Then I imported members from the old mailing list "Templist" into the new > one. > Now the "templist" is no longer visible on the website! > It is here: > https://sartrack.nz/mailman3/ > Note that the existing list "Templist" is missing. > > Now I need to login as 'superuser' or whatever it is called, so I can > manage all the lists. > Where do I set up my login and password for access via the web browser? > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 3 months

[MM3-users] Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 1:10 PM, Brian Carpenter wrote: > > Ok. The first thing however is did I miss a step? Not really. The problem is FILTER_VHOST = True doesn't work for web hosts that aren't email hosts. > Here is the complete error that is sent to me via email as superuser: > > > Internal Server Error:/mailman3/lists/ > > KeyError at/mailman3/lists/ > 'file' > > Traceback: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" > in inner > 34. response = get_response(request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 115. response = > self.process_exception_by_middleware(e, request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 113. response = wrapped_callback(request, > *callback_args, **callback_kwargs) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in list_index > 755. paginator_class=MailmanPaginator) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in paginate > 71. objects = paginator.page(page_num) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in page > 46. number = self.validate_number(number) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in validate_number > 48. if number > self.num_pages: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in num_pages > 97. if self.count == 0 and not self.allow_empty_first_page: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in count > 56. return self.function(count=0, page=1).total_size > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in _get_list_page > 751. advertised=advertised, mail_host=mail_host, > count=count, page=page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/client.py" > in get_list_page > 181. return Page(self._connection, url, MailingList, count, page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in __init__ > 37. self._create_page() > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in _create_page > 62. response, content = self._connection.call(self._build_url()) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py" > in call > 112. error_msg, response, None) > > *During handling of the above exception (HTTP Error 404: {"title": "404 > Not Found"}), another exception occurred:* The above 404 is the underlying problem. In the traceback above we see that /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py at line 751 calls client to get the view for lists for this host. The full code is def _get_list_page(count, page): client = get_mailman_client() advertised = not request.user.is_superuser mail_host = request.get_host().split(":")[0] if ( getattr(settings, 'FILTER_VHOST', False)) else None return client.get_list_page( advertised=advertised, mail_host=mail_host, count=count, page=page) The issue is the FILTER_VHOST = True setting is broken. This is <https://gitlab.com/mailman/postorius/-/issues/394> The broken code tries to get the lists for the domain in the requesting URL which here is the web_host but the web_host has no lists. This is a complicated issue. See the whole comment thread in the issue where I am trying to mentor someone to a fix, but he apparently has given up. The issue is we don't have a method for retrieving lists by web host. It is simple enough to get all the email hosts associated with a web host, but what do we do if that's more than one email host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Josef Dietl

Dear Mark, Dear all, >> (Asterisk makes a difference, see at the bottom) > ??? I didn't see what. Sorry, my bad. While chasing the issue, I had thought I had seen a difference but can't reproduce it anymore. Then I forgot to remove the pointer. >> I'm running a fresh package installation from Debian Bullseye with >> certificates from Certbot with nginx, so Certbot may have messed with >> my nginx config, but even that seems to be OK: Yes, Certbot has >> inserted >> http->https redirection, but I'd expect that a https base_url and >> ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. > It should. > > Note that your primary resource for help with issue with Debian packages should be Debian. The state of the Debian Bullseye packages suggest a certain feeling of priority on that matter ☹ If I can't get this going "soon", I'll wipe the entire server, install a fresh Bullseye and install mailman3 through pip. Out of bad experience, I'd like to avoid mixing software lifecycle managers, but it seems to be the lesser evil. >> To provide all possible information, I'm also adding the nginx log that >> seems to correspond to that request (no other requests at that time, give or >> take five minutes): Yes, everything yields 403 response codes. >> >> >> >> [.] - - [19/Jan/2022:22:43:27 +0000] "GET >> /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] >> HTTP/1.1" 403 175 "-" "python-requests/2.25.1" > > >The issue here is accessing the hyperkitty API. The base URL for these >accesses is configured in mailman-hyperkitty.cfg. From what I see here, >that is something like `http(s)://host.example.com/hyperkitty/` If you >append `api/` to that base URL and go there in a web browser do you get >a page of documentation of the HyperKitty API? If so, then figure out >why it works from a web browser and not when Mailman core does it. If >you get the 403, figure out why. This is probably an nginx issue. Seems like an nginx issue indeed. However, I'm an apache guy, trying to re-educate myself on nginx. OK, here's the result of changing mailman-hyperkitty.cfg from `http(s)://host.example.com/hyperkitty/` to `http(s)://host.example.com/hyperkitty/api/` Yes, if I open things from the web browser, I do get the HyperKitty API doc. With what follows below, I guess it's a timeout: Processing a message takes longer than rendering a HTML document. Jan 22 20:26:27 2022 (149435) ACCEPT: <AM0PR04MB4785365CA1BB735884E149CEC25C9(a)AM0PR04MB4785.eurprd04.prod.outlook.com> Jan 22 20:26:28 2022 (149439) HyperKitty failure on https://[FQDN]/hyperkitty/api/api/mailman/urls: (what follows is a lengthy HTML document, essentially a 404 not found message). That corresponds to the nginx logfiles: access.log: [IP4] - - [22/Jan/2022:20:26:29 +0000] "POST /hyperkitty/api/api/mailman/archive?key=6xpENHLEHQ0kD53vXt5RpKzPDOsKbcN9 HTTP/1.1" 404 1342 "-" "python-requests/2.25.1" 9 And error.log: 2022/01/22 20:26:29 [error] 128720#128720: *4375 readv() failed (104: Connection reset by peer) while reading upstream, client: [IP4], server: [FQDN], request: "POST /hyperkitty/api/api/mailman/archive?key=[key] HTTP/1.1", upstream: "uwsgi://unix:/run/mailman3-web/uwsgi.sock:", host: "[FQDN]" So it all seems consistent in a way, except that error.log suggests that this could be a timeout. Question: What happens if nginx issues a 403 "Forbidden" in that spot? - Does the mailman system as a whole (whichever subsystem is responsible...) _assume_ that there is an error with MAILMAN_ARCHIVER_FROM (as suggested in the mailman3 logfile) - so other possible reasons for 403 are theoretically possible, or are other possible reasons for 403 explicitly (e.g. a timeout) ruled out somewhere, somehow? Following that, I've set the timeout in nginx to five minutes, but it doesn't change anything. I'm sorry that I can't contribute any news. I guess I'll start over, using pip and virtualenv for installation. Thank you for your help!

3 years, 7 months

[MM3-users] Re: Tracking from gravatar

by Mark Sapiro

On 2/14/19 2:31 PM, worik wrote: > Privacy badger reports one tracker (for which it disables cookies) on my > Mailman installation. It is: > > secure.gravatar.com > > What is this for and how do I get rid of it? If you go to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> and look around the archives you will see that all users have some sort of graphic image associated with them. In many cases such as yours, the image is just a rudimentary silhouette, but others have a picture or other graphic. Those are things the user has published at gravatar.com. You can disable them by setting GRAVATAR_SECURE_URL = '' in your local settings. See <https://github.com/twaddington/django-gravatar> Setting the URL to the null string is not completely satisfactory as there will still be a 'missing image' where the image used to be, but it should remove references to secure.gravatar.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Rendering HTML for moderation

by Mark Sapiro

On 10/28/19 1:37 AM, Gila Halpern wrote: > Hi, new member here doing some research for my boss. Does Mailman 3 allow > HTML rendering in the moderation queue, or only plain text? I'm asking > because our list mod doesn't have time to check each image in a submission > individually, so we currently don't allow images, but the boss wants to > allow them. Postorius displays only plain text of a held message with HTML and images shown as attachments, and clicking an HTML attachment link will download the HTML and what happens depends on the browser, but if there are image parts referenced in the HTML, they will be separate links to download and won't render along with the HTML. However, is the list is set to notify the moderators of held messages, the notice will imclude the entire message which should render properly in the moderator's MUA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Stephen J. Turnbull

Marcus Granath writes: > Sorry, but actually I can not find any "Users dropdown" to select > "Non-Members" at any Postorius in my web interface. :-( > Maybe, could it be that I am actually not the admin of the mailman3 > server, I'm "just" the admin of my mailman-list - so just admin for > my mailman-list and not for the mailman server? I think if you are *moderator* you should be able to see the Subscribers list, but maybe you need to be *list owner*. You definitely do not need to be *server admin* to see the Subscribers list. I'm not sure if the *server admin* has a way to see a sitewide Users list (other than using the mailman command line tool or directly from the database). Is it possible that you have multiple logons on the server, one of which you have subscribed to lists and the other is a user with administrative privileges? I know that burns me regularly. Steve

4 years, 5 months

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

by Guillermo Hernandez (Oldno7)

On 18/9/21 20:42, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 18/9/21 20:27, Mark Sapiro wrote: >> from mailman.interfaces.action import Action >> def moderar(mlist, member): >> memb = mlist.members.get_member(member) >> if not memb: >> print('{} is not a list member.'.format(member)) >> return >> memb.moderation_action = Action.hold >> print('{} moderation_action set to hold.'.format(member)) > Just a one more silly question: Where do I can find the diferent values that memb.moderation_action can take? (I want to prepare the "unhold" script too) Thanks in advance. > That completely did it. The problem about finding the module was > completely gone when I made a soft link in the same directory where > mailman command is (in /usr/local/bin, for your info). > > Thank you very, very much. > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 11 months

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

by Michael Heseltine

> Did you see my post at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/... > and did you run > > /opt/mailman/mm/bin/django-admin migrate > > before starting services? As mentioned above: yes, I did; and yes, I did it before starting the services. > Do you have all of these apache modules enabled, proxy.conf, > proxy_http.load and proxy.load, in particular proxy_http.load? Well, mostly: > # a2enmod proxy_http.load > Considering dependency proxy for proxy_http: > Module proxy already enabled > Module proxy_http already enabled > # a2enmod proxy.load > Module proxy already enabled > # a2enmod proxy.conf > ERROR: Module proxy.conf does not exist! Did a "systemctl restart apache2", but nothing has changed - still get an internal Server error. Btw, I the ProxyPass(Reverse) supposed to point at the URL listed in MAILMAN_REST_API_URL? Because that one is set to port 8001 in settings.py, and if I try to "telnet localhost 8000", i get "Connection refused". Cheers, Michael

3 years, 8 months

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

by Stephen J. Turnbull

Kimmo L writes: > I was able to found the cause of the issue. Under list settings > > Alter Messages there is a option called "anonymous list". > It seems that if i set this to YES, im not able to send email > out. If i set this to NO - everything works fine. > Is there some other option, that might affect anonymous option > effect ? No, it has to be something about the message, because looks like Mailman is throwing exceptions when it tries to turn the anonymized email.Message Python object into an RFC 822 message it can send to the MTA. Can you send a test message to the list, also CC: me at "stephen(a)xemacs.org" (do not copy-paste my Gmail address, I will never see it, that's where I sign up for vendor spam and read it once a month)? Also send me the pickle (.pck object from the shunt queue). Steve

3 years

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 6:40 PM, brian(a)emwd.com wrote: > > Also Kelly are you sure this is correct: > > "There are two configuration files that have a key in them that must match for Hyperhitty to authorize and be able to store archives (the paths should be as follows): > /etc/mailman3/mailman-hyperkitty.cfg (set the api_key without any quotes) > /etc/mailman3/mailman-web.py (set the ‘SECRET_KEY’ - include single quotes around the key)" > > It was the MAILMAN_ARCHIVER_KEY that I needed to make sure it was being matched by the API key in mailman-hyperkitty.cfg. I believe the SECRET_KEY setting has nothing to do with the auth errors that Hyperkitty was displaying. Yes. SECRET_KEY is used internally within Django. See <https://docs.djangoproject.com/en/2.1/ref/settings/#secret-key>. It is the MAILMAN_ARCHIVER_KEY setting that must match the api_key setting in mailman-hyperkitty.cfg (modulo quoting). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

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

by Paul Arenson

I have found that my users in the discussion list are creating their own topics rather than using the existing ones, so decided to make it a read-only list and use WordPress moderated comments. Since I do not have the original settings for READ ONLY (this is a hosted version), I want to make sure that these are correct. Can someone comment. Thanks MOST IMPORTANT—> What setting makes it a discussion list as opposed to read only? ALTER MESSAGES ----------------------- Filter content Now YES Collapse Alternatives Now yes Convert html to plain text Now NO Anonymous NOW YES Include RFC2369 headers Now Yes Include the list post header Now Yes Reply Goes to List Now No munging Pipeline Default DMARC MITIFGATIONS ----------------------- Replace From with list address DMARC mitigate unconditionally Now NO MESSAGE ACCEPTANCE ----------------------- Require Explicit Destination Yes Administrivia YES Default action to take when a member posts to the list Hold for moderation Default action to take when a member posts to the list Hold for moderation OTHER? ------------- Thanks Paul Arenson

5 years, 11 months

[MM3-users] Unknown templates being used

by Tom Stoddard

I'm a list owner who has recently (within the last week) had my lists migrated from mailman 2 to mailman 3. The UI that we are using is Affinity. I've reviewed all of the list templates and begun to customize some of them. My issue is that I'm receiving messages that don't match any of the templates. Here is an example of one that I just received this morning. (The x's are inserted by me. The actual message provided valid addresses.) The xxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. Held Subscriptions: User:xxxxxxxxxx@gmail.com Please attend to this at your earliest convenience. When I log in to review the request it appears to be a subscription request awaiting approval. I had previously modified the "Moderator Approval Subscription" template, which is what I would expect to have received in this circumstance. I administer several lists and have received some messages that do use the newly modified template so I assume I did it correctly. Any idea where the template for this message came from? Thanks!

4 years, 7 months

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

by Mark Sapiro

On 2/18/22 09:53, Élodie BOSSIER via Mailman-users wrote: > > Now, I need to find how to set it automatic when I will add a new list. > Perhaps I could do it with an an SQL command if there are no bash > command ? I will check with "mailman create" and the --domain argument. Part of adding a new list is specifying the domain. If it's one of the existing domains, i.e., ml.franceserv.fr, or ml.viticreation.fr, that's all that needs to be done. e.g. `mailman create newlist(a)ml.franceserv.fr`. If it's a new domain, you need to add the domain to the django_site table perhaps directly or via the django admin UI and then after `mailman create newlist(a)new.domain` you may need to edit the domain via Postorius' domains view to specify the correct Web Host. -- 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: Issues with @gmail.com addresses

by Stephen J. Turnbull

Mohsen Masoudfar writes: > I created a new list with this setting. This new created list can > send to Gmail addresses, this is very strange, because I have > changed the problem list (The list that cannot send to @gmail > addresses) settings to match the new one, but still the issue is > there. The problem may also be that Google has decided that your existing list has a bad reputation, that is, it had too many posts rejected in the past. The new list doesn't have that problem. The problem that mailing lists face with the biggest email providers is that they don't have acceptance policies any more because they use algorithmic reputation engines. *They* don't know why your email was rejected. (Truth be told, none of us do since we use Bayesian spam filters. But at least if you use SpamBayes you know what features are being evaluated. Machine learning algorithms use "features" that are too tiny to be connected to spam except with big data.)

2 years

[MM3-users] Re: Internal Server Error: /archives/

by Mark Sapiro

On 11/29/24 7:51 AM, Christian via Mailman-users wrote: > What is this error and how can I fix it please? Running Debian 4.19.316-1 ... > Request Method: GET > Request URL: https://lists.domedoman.ie/archives/?sort=active%22%27! ... > Traceback (most recent call last): > None ... > GET: > sort = 'active"\'!' Some remote user has requested `https://lists.domedoman.ie/archives/?sort=active"'!` The `"'!` appended to the sort=active query fragment caused the error. This sort of thing happens when bots and script kiddies crawl your web site. You can find the request in your web server logs for more information about where it came from, but the bottom line is this will happen from time to time and it's not an indication that anything is broken. It would be possible to harden HyperKitty to defend against malformed URLs like this, but without a traceback it is not clear where to do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

[MM3-users] Re: Postorius fails to show list because of a large message being held

by Brian Carpenter

On 7/14/20 6:49 AM, Gilles Filippini wrote: > Mailman Core logs: > [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) > [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) > [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 I am pretty sure that timeout is related to gunicorn. If it is, then increasing the worker out timeout setting for gunicorn should work. You tend to get such errors when doing an export of a large membership roster. This is the first time I have seen it related to a held message. I have this in my setup: mailman.cfg: [webservice] configuration: /opt/mailman/mm/gunicorn.cfg gunicorn.cfg: [gunicorn] workers = 4 timeout = 900 You will need to restart gunicorn after adjusting the timeout setting. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 2 months

[MM3-users] Migration of the e-mail templates

by Stephen J. Turnbull

Markus Grandpré writes: > When migrating the lists and archives from Mailman 2.1 to Mailman > 3, the e-mail templates were obviously not migrated. Which templates? Headers and footers are in the database, and they should be migrated. The standard templates for autoreplies, moderator notifications, and so on will have versions appropriate for Mailman 3, and as far as I know all of the languages standard in Mailman 2 have been translated to Mailman 3, or the Mailman 2 version crudely adapted to Mailman 3. Do you mean custom templates (such as moderator noifications) that overwrote stock templates in the Mailman 2 installation? I would think you would have to copy those by hand, because the upgrade process would not know that they're customized, and would just assume the new installed versions are good for you. I'm pretty sure you can copy them to a different place that has higher precedence in the search path so you don't have to worry about them being overwritten by upgrades. Unfortunately Mark is on vacation. Steve

6 months, 1 week

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

by Mark Sapiro

On August 20, 2025 4:37:18 AM EDT, "Stephen J. Turnbull" <steve(a)turnbull.jp> wrote: >Odhiambo Washington via Mailman-users writes: > > > > > The superuser account uses my address - odhiambo at gmail dot > > > > com. I am also the listowner for most lists. > > > > I tried unsuccessfully to create an account on Postorious using the same > > > > email address. > >I don't see how you can do this. It's the same user database, and >email addresses are accepted as identifying a unique User object in >the database for authentication and authorization purposes in Django. That is correct. You can't have two accounts in Postorius/Django with the same email address. But why would you want to? There should be no problem with a single Django user being subscribed to a list with more than one role. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I did this: (env) [mailman@localhost mailman-suite_project]$ pip install Django Requirement already satisfied: Django in /var/lib/mailman/env/lib/python3.6/site-packages Requirement already satisfied: pytz in /var/lib/mailman/env/lib/python3.6/site-packages (from Django) Does Django is already installed?? with python3.6 ??? El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:33 PM, Rafael Mora wrote: > > > > I'm getting an error doing: > > > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py > migrate > > Traceback (most recent call last): > > File "manage.py", line 8, in <module> > > from django.core.management import execute_from_command_line > > ImportError: No module named django.core.management > > > Have you installed Django in your 'env' virtualenv? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Prometheus mailman_exporter

by Ruth Ivimey-Cook

Folks, I have recently been playing with Prometheus metrics, and having now coded a mailman3 Prometheus exporter in python I thought I'd mention here that it exists. It's not fancy and there is more to do. It works using the rest api. Source available at https://github.com/rivimey/mailman3_exporter Metrics exposed: 'mailman_up' (does the API /system/versions return http 200) and 'mailman_queues' (queue lengths for each queue, plus 'status' for the http status code of that query) Suggestions for other metrics would be interesting if accompanied with info on how to extract it. I'm currently contemplating including the number of 'to be moderated' messages. It would be possible to include the number of lists or domains but not sure it's useful enough to be worth the cost of fetching it. It is passed the api auth data separately. It would be better to read it from mm config: is there existing code I can call? Regards, Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years, 4 months

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

by Mark Sapiro

On 6/2/25 10:55, Cathryn McGuire wrote: > Hi, > > We’re currently hosted by EMWD who upgraded the Mailman 2 cPanel/Python and have been unable to resolve the issues we’re experiencing. > > We would like to join a Mailman 3 list to see how it all looks and works. > > Do you have any recommendation? Welcome to the mailman-users(a)mailman3.org list. As far as your EMWD migration from cPanel Mailman 2.1 to Mailman 3 is conerned, I think you'll find little if any change as far as email posting to the list and email from the list is concerned, but EMWD has their own proprietary web UI for list management and archiving, so the web UI at EMWD is quite different from that for this list. I'm not sure if we can help with the issues you're having, but if you tell us what they are, we can try. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: out queue backlog and delivery rate

by Mark Sapiro

On 3/25/22 16:17, dancab(a)caltech.edu wrote: > > Mail delivery is continuing at a snails pace and it is now 4 hours behind. > > I noticed that the system isn't overloaded either via CPU or Memory. It's just slowly "working on it". > > Are there rate limits that can be tuned for Mailman queues such as the "out" queue? Could this be IO related somehow? I'd expect there to be a CPU spike in that case. There are things that can be done. One big performance killer is MTA recipient checks during SMTP from Mailman. Look too at the various hits at <https://wiki.list.org/?action=fullsearch&value=performance&titlesearch=Titl…>. These are written for older Mailman, but the MTA advice is relevant. One thing you can do is enable an alternate SMTPD port in the MTA with minimal checking and configure Mailman to use that port. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

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

by tlhackque

On 03-Oct-17 03:58, Abhilash Raj wrote: > > > The container images have stable releases of Mailman components, so > those changes will make in to the container when a new Core release > happens. > > The next image release is pending a version upgrade of Hyperkitty, to > 1.1.3, but other changes are just meant to make the process of setting > up Mailman better. They do not include changes from git repo after the > release. > > Considering the evolving state of MM3, the complexity of installing it, and the problems that people have trying to use it for testing/production: you might consider packaging an 'unstable' Docker version from git 'head', perhaps weekly. Building it ought to be something that you can script...and a regular cycle would give developers a target for merges. This would get you early testing & would help those trying to be early adopters - waiting months for the next point release will turn off the enthusiasm. FWIW .

7 years, 11 months

[MM3-users] Re: Remove PDF attachents

by Mark Sapiro

On 3/4/20 7:42 AM, Eduardo Costa via Mailman-users wrote: > Hello, > > How do I configure the list to remove attachments of type pdf and others. You need to set the list's filter_types and or pass_types. For example, to filter out everything except HTML and plain text, collapse alternative parts and convert remaining HTML to plain text, you would set filter_content = True collapse_alternatives = True convert_html_to_plaintext = True pass_types = ['multipart', 'text/plain', 'text/html'] The first 3 of these can be set in Postorius -> Settings -> Alter Messages, but the last has to be set in mailman shell as in $ /opt/mailman/mm/bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell m. The variable 'm' is the list(a)example.com mailing list >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

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

by Mark Sapiro

On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Problem with list creation

by Mark Sapiro

On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > We increased timeout in mailman.cfg > ``` > [gunicorn] > workers: 4 > timeout: 900 > ``` This doesn't do it. In order to pass configuration settings to the REST gunicorn servers, you need to put in mailman.cfg ``` [webservice] configuration: /path/to/gunicorn.cfg ``` and then put settings like these ``` [gunicorn] workers: 4 timeout: 900 ``` in /path/to/gunicorn.cfg. Some settings, but only hostname, port and workers can be put in mailman.cfg, but in the [webservice] section, not in a [gunicorn] section. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/gunicorn.…> for more detail. > And we increased timeout in nginx > > ``` > http { > > # MODIF UNICORN > proxy_connect_timeout 300s; > proxy_read_timeout 300s; > # MODIF UNICORN > > ``` nginx is not involved. These are not proxied requests through nginx. They are requests to Mailman's REST API which use a separate gunicorn server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: certain msgs not archived

by Sandor Dibuz

Meanwhile going ahead slowly. This resolved issue helped a lot: https://gitlab.com/mailman/hyperkitty/-/issues/248 'charset': 'utf8mb4' into /etc/mailman3/mailman-web.py helped and now a message with utf8mb4 emoji char is archive properly. But reading that particular msg in Hyperkitty spits out a new error: Internal Server Error: /mailman3/hyperkitty/list/test1(a)dwatt.com/thread/OIHKKHNGNL6HF2SMFJZXSS6TABO2VK6Z/ AttributeError at /hyperkitty/list/test1(a)xxxxx.yyy/thread/OIHKKHNGNL6HF2SMFJZXSS6TABO2VK6Z/ 'NoneType' object has no attribute 'subject' Request Method: GET Request URL: https://xxxxx.yyy/mailman3/hyperkitty/list/test1@xxxxx.yyy/thread/OIHKKHNGN… Django Version: 2.2.25 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: Wed, 16 Feb 2022 21:27:14 +0100 Googling the mailman-users list I found another case where hyperkitty_thread table had a NULL starting_email_id and yesss! It has a NULL in starting_email_id really! Now the billion$ question: what this particular msg with an utf8mb4 char has to do with starting_email_id?? Sanyi

3 years, 7 months

[MM3-users] Re: [migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite

by Mark Sapiro

On 10/20/23 14:04, Wikinaut wrote: > I also solved this issue. > How? > > By adding columns to two tables in the database mailman3web: > > alter table hyperkitty_mailinglist add column archive_rendering_mode varchar(255) default null; > alter table socialaccount_socialapp add column `provider_id` varchar(200) NOT NULL; > alter table socialaccount_socialapp add column `settings` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL CHECK (json_valid(`settings`)); The proper fix is just to run `mailman-web migrate`. See https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… You should also run that and `mailman-web collectstatic` `mailman-web compress` and `mailman-web compilemessages` any time you do any kind of update. See https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-… et. seq. Running `mailman-web migrate` at this point may fail because of the changes you made manually. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 8/18/25 12:06 PM, Wikinaut wrote: > Thank you. > As I need to go through ~20 mailing lists, is there any way to programmatically also modify the templates? > > I could not find a script for doing this but it would nice to have, as I managed, as known, to write and to run scripts, which is very helpful (because we re-generate the _whole_ mailsystem daily if there are changes in our membership database). If you want to use default templates for everything, just remove everything under /opt/mailman/mm/var/templates/. If you want a custom footer for all lists, remove list:member:generic:footer.txt from all the /opt/mailman/mm/var/templates/lists/LIST_ID/LC/ directories and create the footer at /opt/mailman/mm/var/templates/site/LC/list:member:generic:footer.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 weeks, 2 days

[MM3-users] Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius

Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple writable. SQLite version 3.16.2 2017-01-06 16:32:41 Enter ".help" for usage hints. BR Ugnius > On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >> >> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? > > No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. > > The doc mentions that it is "development" server[1][2]. > > [1]: # Run the Django's "development" server at localhost:8000 > [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project > > Perhaps it should be more descriptive about what does it mean. > >> >>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> >>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>> >>> You only need one of those, since they both do the exact same thing. Please remove >>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>> >>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>> May mailman processes are next: >>>> >>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>> >>>> Looks like there are no double. Nothing more is running. >>>> >>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> >>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>> >>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>> $ sudo pip3 install mailman >>>>> $ sudo pip3 install postorius >>>>> $ sudo pip3 install hyperkitty >>>>> $ sudo pip3 install mailman-hyperkitty >>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>> >>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>> >>>>> >>>>> >>>>> >>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>> >>>>> >>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>> > Hi. All the project installation is under the same user / path and >>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>> > to set in postorius, hyperkitty shows list as public) >>>>> > I have found work around - it is possible to change list as private in >>>>> > "admin" page. >>>>> > I started to get issues with runjobs after I have created couple of >>>>> > new lists with "no archive" option. >>>>> >>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>> >>>>> > >>>>> > If as owner user from project home I run: >>>>> > >>>>> > django-admin mailman_sync >>>>> > >>>>> > Traceback (most recent call last): >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>> > line 84, in _execute >>>>> > return self.cursor.execute(sql, params) >>>>> > File >>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>> > line 383, in execute >>>>> > return Database.Cursor.execute(self, query, params) >>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>> > >>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>> > "django-admin runjob new_lists_from_mailman" >>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>> > END TRACEBACK >>>>> > >>>>> > I did not find information how to fix this. It was worked without errors >>>>> > before. >>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>> > to work. >>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>> > again. >>>>> > I did not check other jobs, but I think what is related to database, >>>>> > will get errors. >>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>> > >>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>> > mailman creates database file size 0, django-admin runjobs start >>>>> > working, but of course postorius stops working. I did it for testing. >>>>> > I have returned this database file back, postorius started to work >>>>> > again, but django-admin runjobs does not work, error: "database read >>>>> > only". >>>>> > Please help me how to fix this issue. >>>>> > _______________________________________________ >>>>> > 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) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> >>>> >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>> > > -- > thanks, > Abhilash Raj (maxking) > >

6 years

[MM3-users] Re: Mailman shell tutorial

by Mark Sapiro

On 6/11/19 6:00 PM, Andrew Bernard wrote: > > I have this going, and it is great. But I recall seeing something called > mmclient or similar which has simple commands like show user, show lists, > and so on. Is that still available? Are you thinking of the mailman command itself? Things like `mailman lists` and `mailman users`. Try running the `mailman` command itself with no arguments to see a list of sub-commands and then `mailman sub-command --help` to get the details of a particular subcommand. > Now knowing how mailman shell works, anybody could write their own commands, > but I don't want to reinvent wheels. I don't know what it is you are trying to accomplish, but yes, you can create scripts which you run via `mailman shell -run ...`, but is there something specific you are trying to do that is not currently available via the `mailman` command or the Postorius wb UI? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Help with troubleshooting mailman3 DNS lookups

by Mark Sapiro

On 2/23/21 3:11 PM, Simon Handfield via Mailman-users wrote: > However when messages are sent to mailman3 lists we're still seeing hits on the old DNS servers. > > I have tried to find a config that references the old servers but have not been able to find one. Because Mailman doesn't directly access DNS. As far as I know, there are only two pieces in Mailman core that indirectly access DNS. DMARC mitigations look up sending domain DMARC policy via the dnspython package <https://pypi.org/project/dnspython/> and if you have enabled ARC signing in Mailman via [ARC] enabled: yes it uses authheaders <https://pypi.org/project/authheaders/> I don't know what these packages might be looking at to see the old servers, but as far as I know, nothing else is doing DNS lookups. The modules that invoke these are mailman/rules/dmarc.py and mailman/handlers/arc_sign.py. -- 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: problem configuring mailman3 on debian bullseye

by Mark Sapiro

On 3/15/23 09:55, Odhiambo Washington wrote: > On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione > territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: > >> Hi, >> >> I created a template but after some tests I deleted it. >> >> Now I created only a standard list without modifying any templates. >> >> So they are the standard templates coming with the distribution. I did not >> change also the language >> > Maybe you can start by deleting any templates in postorius_emailtemplate > table in the DB? There shouldn't be any, but if the issue is with accessing postorius templates, that might make it worse. If you want only the system default templates, you could do this database query to remove any non-defaults: DELETE FROM templates; That will ensure that you aren't accessing Postorius for any templates. -- 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: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Stephen J. Turnbull

Odhiambo Washington via Mailman-users writes: > > > The superuser account uses my address - odhiambo at gmail dot > > > com. I am also the listowner for most lists. > > > I tried unsuccessfully to create an account on Postorious using the same > > > email address. I don't see how you can do this. It's the same user database, and email addresses are accepted as identifying a unique User object in the database for authentication and authorization purposes in Django. I doubt that Django understands the Gmail "punctuation doesn't exist" concept, and I don't think Mailman does either, so you can probably use ohdiamb.o(a)gmail.com for the new address. (Or you could create a new superuser to use the ugly address, delete the old one, and then claim the pretty address for your ordinary user.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 weeks

[MM3-users] Re: disable sign-ups

by Simon Hanna

On 01/31/2018 09:59 PM, Peter Münster wrote: > Hi, > > I would like to add new accounts only manually, the mailman3 site should > not be open for sign-ups. So I've added this code to settings.py: > > --8<---------------cut here---------------start------------->8--- > from allauth.account.adapter import DefaultAccountAdapter > > class MyAccountAdapter(DefaultAccountAdapter): > def is_open_for_signup(self, request): > return False > > ACCOUNT_ADAPTER = 'MyAccountAdapter' > --8<---------------cut here---------------end--------------->8--- > > It seems to work, but the user experience is not optimal: the user can > click on "Sign Up", and then gets to "Server Error (500)". This is the > log: > > --8<---------------cut here---------------start------------->8--- > ERROR 2018-01-31 21:53:47,116 6769 django.request Internal Server Error: /accounts/signup/ > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 34, in _wrapper > return bound_func(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper > return view(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 30, in bound_func > return func.__get__(self, type(self))(*args2, **kwargs2) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 210, in dispatch > return super(SignupView, self).dispatch(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 79, in dispatch > **kwargs) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 182, in dispatch > if not self.is_open(): > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 191, in is_open > return get_adapter(self.request).is_open_for_signup(self.request) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 501, in get_adapter > return import_attribute(app_settings.ADAPTER)(request) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/utils.py", line 150, in import_attribute > pkg, attr = path.rsplit('.', 1) > ValueError: need more than 1 value to unpack > ERROR 2018-01-31 21:53:47,116 6769 django.request Internal Server Error: /accounts/signup/ > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 34, in _wrapper > return bound_func(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper > return view(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 30, in bound_func > return func.__get__(self, type(self))(*args2, **kwargs2) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 210, in dispatch > return super(SignupView, self).dispatch(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 79, in dispatch > **kwargs) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 182, in dispatch > if not self.is_open(): > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 191, in is_open > return get_adapter(self.request).is_open_for_signup(self.request) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 501, in get_adapter > return import_attribute(app_settings.ADAPTER)(request) > File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/utils.py", line 150, in import_attribute > pkg, attr = path.rsplit('.', 1) > ValueError: need more than 1 value to unpack > --8<---------------cut here---------------end--------------->8--- Not sure how this error happens. You might want to ask the allauth guys about that... > Do you have any hints, how to avoid such errors please? You probably don't want to display the signup link in the first place. You can do that by overwriting templates. https://docs.djangoproject.com/en/2.0/howto/overriding-templates/ Overriding the base template(s) should be enough for that I guess...

7 years, 7 months

[MM3-users] Re: Timeouts

by tlhackque

On 25-Apr-21 20:34, Mark Sapiro wrote: > On 4/25/21 4:37 PM, tlhackque via Mailman-users wrote: > >> The described timeouts are something that hyperkitty ought to be able to >> avoid. For apache, the timeout is idle time between blocks of output. >> Hyperkitty can avoid this by generating the archive in segments (based >> on size, or elapsed time), flushing its output buffer, generating a >> multi-file archive, and/or using Transfer-Encoding: chunked (chunked >> doesn't work for http/2). It ought to be able to break the work into >> blocks of "n" messages & do something to generate output. Besides >> avoiding timeouts, working in segments allows the GUI to display >> meaningful progress (e.g. if you're loading with XMLHttpRequest, >> "onprogress") It really oughtn't be up to the user to break up the >> request. > It is not the web server that times out. I'm not sure about uwsgi > because I don't use it, but the timeouts I see are on servers that use > gunicorn as the WSGI interface to Django and the timeout is in a > gunicorn worker. This is controlled by the timeout setting in the > gunicorn config. <https://docs.gunicorn.org/en/stable/settings.html#timeout> > > Note that even 300 seconds is not enough to download the entire > <https://mail.python.org/archives/list/python-dev@python.org/> archive. > > It may be possible to get HyperKitty to chunk the output to avoid this, > but it doesn't currently do that. Care to submit an MR? > > I'm afraid (u)WSGI, Django, and gunicorn are not technologies that I work with. It sounds as if hyperkitty is compiling the entire archive before sending the first byte. The gunicorn doc that you pointed to says Workers silent for more than this many seconds are killed and restarted. Setting it to 0 has the effect of infinite timeouts by disabling timeouts for all workers entirely. "Silent" sounds like the standard webserver "you have to push some bits, or we assume you're stuck". My understanding is that gunicorn is a Python persistence server that is run behind a webserver proxy. So the (proxy) webserver (apache, nginx, ...) timeouts also apply and would need to be increased. Might be interesting to try 0 (gunicorn) / 1200 (webserver) with your python-dev archive, time it and see how much (encoded) data is transferred... (I would expect most mailing list archives to compress nicely, though those with binary attachments wont.) But fiddling with timeouts is treating the symptom, not the root cause. The right solution is to stream, segment (or chunk) the output, because in the general case, no timeout is long enough. It'll always be possible to find an archive that's just one byte (or second) longer than any chosen timeout. (See the halting problem.) You want the timeout to catch a lack of progress, not total time that's a function of transaction size. (Webservers may also have limits on transaction size - e.g. mod_security, but they're only useful when the upper bound on a response is knowable.) Thus, the timeout(s) should be roughly independent of the archive size; on the order of time-to-first-byte (which ordinarily is longer than time between segments/chunks). Also note that streaming requires fewer server resources than compiling a complete archive before sending, since you don't need to create the entire archive in memory (or in a tempfile). You only need enough memory to efficiently buffer the file I/O and to contain the compression tables/output buffer. Except for trivial cases, this will be independent of the archive size. The only downside is that if the comm link is slow, you may hold a reader lock on the source data for longer than necessary with the current scheme. Seems as though this deserves an issue. I guess I could open one - but you have the experience/test cases.

4 years, 4 months

[MM3-users] Re: Mails from Django are not sent

by Abhilash Raj

On Fri, Oct 13, 2017, at 02:36 AM, Simon Hanna wrote: > On 10/12/2017 12:27 PM, Bjoern Franke wrote: > > Hi, > > > > I'm using the "mailman-suite" setup for Postorious and Hyperkitty. > > > > I've set > > > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > > EMAIL_HOST = 'localhost' > You can just remove the settings to fallback to the defaults > (that's what I do) The default setting is set to 'django.core.mail.backends.console.EmailBackend'[1] in mailman-suite, so that wouldn't help. [1]: https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… > > in settings.py, but no mails are sent. Files with the e-mails are in the > > emails folder, but nothing happens, also no errors regarding emails are > > logged. It looks like an issue because you probably have DEBUG=True, which will make Django use 'django.core.mail.backends.filebased.EmailBackend'. See [2]. [2]: https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

[MM3-users] Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Fri, Feb 3, 2023 at 6:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 21:25, Odhiambo Washington wrote: > > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > >> See > >> > >> > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > >> for mitigation. > > > > > > What is the danger of replacing my settings.py with this one, seeing as > it > > differs in a number of ways with mine? > > > If your's works, don't do it. The danger is the differences might be > significant and break things. Also, that one is for HyperKitty only and > doesn't include Postorius settings. > So in my case, I should at least increase the value of HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

[MM3-users] Re: How to edit default 'Reject (with notification)' message

by Mark Sapiro

On 5/26/23 7:57 AM, Zaheer Abbas wrote: > > I have created a template with the option, "Notice sent to a poster when > their message has been rejected by the list’s moderator." but it only works > if message acceptance is set to 'Hold for Moderation' and then the > moderator rejects the post manually. > > Is there any source file, which I can modify to replace the default > rejection text mentioned above? The template you want is described in Postorius as [list.user.notice.rejected] Notice sent to a poster when their message has been rejected automatically You can set it in Postorius per list or per domain or you can set it sitewide by putting it in Mailman's var/templates/site/en/list.user.notice.rejected.txt and if you do that, be sure the Mailman user has access to read it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Spam sent to list owner causes bounce increment for list owner

by Allan Hansen

Hi Mark, Thank you for the explanation, and it all makes sense. I prefer your verp_probes solution, as I do prefer to have my list work concentrated in one place. I did have 5 bounces on the list - I guess a lot of spam is happening due to the holidays. I noticed a big uptick myself. Thanks again, Allan > On Dec 18, 2023, at 10:30, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 12/18/23 9:59 AM, Allan Hansen wrote: >> Hi all, >> Someone sent a spam message to the list owner (me) of one of my lists. Then I got booted from the list. >> The scenario in more detail: >> The list server forwards the message to me, as I’m the list owner. This message is sent from <list>-bounces+hansen=rc.org(a)list.rc.org to hansen(a)rc.org. >> My service provider’s spam filter rejects the spam (correctly) in a message and informs the list server. >> The list server sends a message to <list>-bounces+hansen=rc.org(a)list.rc.org (the fake sender) saying that the message to hansen(a)rc.org (the recipient) could not be delivered because it was spam. >> The list server also blames hansen(a)rc.org (me) for the bounce and increments my bounce score, which, to me, is unfair. >> So I wonder: >> Is the Mailman host at list.rc.org at fault for not catching the spam before it reaches the list server? (One could argue that) > > Depends on what kind of spam filtering if any you have on incoming mail to list.rc.org. > >> Is my rc.org service provider at fault for sending the bounce message to the server instead of the to the original sender? > > Absolutely not. The envelope sender of the mail was set by Mailman to <list>-bounces+hansen=rc.org(a)list.rc.org in order to enable automated bounce processing. rc.org correctly sent the bounce to the envelope sender. > >> Is Mailman at fault for thinking that the bounce message was caused by a list message FROM me, instead of a bounced message TO the list owner? > > Arguably, yes, but not based on FROM. FROM has nothing to do with it. The message was sent TO you so if it bounces, it is a message to you that bounced, so you are the one bouncing this message. All Mailman knows is a message was sent to you and it bounced so it's your address that is bouncing. It doesn't matter whether this was a post to the list that bounced or a message to <list>-owner. A bounce is a bounce. > > Note that this list's bounce processing is very aggressive. If you got removed from the list after one bounce, the list must have Bounce score threshold = 1 and Bounce disable warnings = 0. You might consider adjusting these. > > There is an easy fix for this. Set `verp_probes: yes` in mailman.cfg. Then when your bounce score reaches threshold, instead of disabling/removing you, Mailman will send a probe message to you. It will only disable/remove you if the probe bounces which it presumably won't. > > Another avoidance would be to use an address for the owner which is not the address of a member. Then if the owner address bounces, nothing is done because the bouncing address isn't a list member. > > -- > 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 hansen(a)rc.org

1 year, 8 months

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

by Andrew Hodgson

Hi, I completed this on a Debian Buster server instance during last year and have got some notes on the process. I decided to go down the venv route rather than use Docker, but I already had it up and running using the Docker instance on another machine. I found getting it up and running on Docker helped me understand how everything hung together, but ultimately I wanted to run it under a venv so I could understand it a bit more and also I wasn't using Docker in the rest of the environment on that server. I also got caught out earlier on with the Docker containers changing the search engine from Woosh to Xapian which is why I wanted more control over what was going on. Here is a copy of those notes for interest. I used package managers to provide PostgreSQL support as that was what the Docker install gave me to start with. I may have chosen another DB engine but as I was already using Postgres I stuck with that. I also installed Xapian using the package manager as well as Exim, Nginx, Sassc and Python using the package managers. I didn't install Memcached. I mainly followed the instructions at: https://wiki.list.org/DOC/Mailman%203%20installation%20experience My directory structure uses /opt/mailman as the base, the instructions on this web page use /opt/mailman/mm and I didn't have this extra subdirectory. I ensured this directory was owned by list:list. I installed my venv under /opt/mailman/venv choosing to copy over the existing distribution installed Python packages and installed the following packages via Pip after activating it: Upgrade packages that are already installed which need an upgrade to work with Mailman3: pip3 install -U pip zope.interface Get the rest installed: pip3 install mailman mailmanclient django-mailman3 mailman-hyperkitty hyperkitty postorius psycopg2-binary xapian-haystack This also installs Gunicorn which I use as the backend wsgi server. The reason I chose to use existing system packages as part of the venv is because I wanted to use the Xapian installation I had installed via system packages as I ran into issues installing it via Pip. In future I think I will try and install the PostgreSQL driver this way as well. Once deactivating the venv I recommend getting the directory structure and files copied to the right places from the links on the wiki, noting that in my cases I had to edit the files to change the relevant paths to suit my new layout, and also where necessary (Systemd units) change the user/group. . You should then run all the Mailman specific commands using these scripts in /opt/mailman/bin. I learnt the hard way that you will run into problems if you try and run Mailman from the venv directory as it will look for files in the wrong place and create data files in the wrong directory. As I went down this road my configuration files mailman.cfg and mailman-hyperkitty.cfg are actually located in /opt/mailman/etc but that isn't a requirement if you follow the wiki and use the scripts provided. I obtained manage.py, settings.py, urls.py and wsgi.py from the Gitlab Mailman-suite project instead of the wiki site to ensure I got the latest versions and put these files in /opt/mailman. Regarding /opt/mailman/bin/mailman-post/update, I removed the references to Memcached as I didn't use it. I also didn't symlink /opt/mailman/logs to /opt/mailman/var/logs as advised by the wiki but will do this on a reinstall. I generated a new Mailman PostgreSQL user and restored my existing database to the new server (which also upgraded the DB to a newer Postgresql version as the Docker-Compose from the Mailman Docker project uses an older Postgresql container). I copied the Mailman runtime files from the Mailman core container data volume to /opt/mailman/var. I generated a Hyperkitty API secret key and also a Django secret key. Taking the mailman.cfg file from the wiki as a base, I updated the following parts: [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:[password]@localhost/mailmandb [mailman] site_owner: mailman-owner(a)lists.domain.com [mta] incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4 [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/etc/mailman-hyperkitty.cfg In /opt/mailman/etc/mailman-hyperkitty.cfg add the following: [general] base_url: http://localhost:8000/hyperkitty/ api_key: [generated-hyperkitty-api-key] Using systemctl see if you can start Mailman and observe logs etc. In terms of the Django stuff you need to create /opt/mailman/settings-local.py which will be read in by the system and will overwrite the default settings in /opt/mailman/settings.py obtained from the Mailman-suite project. This directly configures the Django framework which the Mailman web components Postorius and Hyperkitty run under. Here is a outline copy of my file: import os BASE_DIR = os.path.dirname(os.path.abspath(__file__)) SECRET_KEY = '[generated-django-secret-key]' MAILMAN_ARCHIVER_KEY = '[generated-hyperkitty-api-key]' DEFAULT_FROM_EMAIL = 'mailman-owner(a)lists.domain.com' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' DEBUG = False USE_X_FORWARDED_HOST = True SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') ALLOWED_HOSTS = [ 'localhost', 'lists.domain.com' ] INSTALLED_APPS = ( # Copy the installed apps from the settings.py and remove the social provider logins you don't want to support. ) DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailmandb', 'USER': 'mailman', 'PASSWORD': '[password]', 'HOST': 'localhost' } } HAYSTACK_CONNECTIONS = { 'default': { 'PATH': os.path.join(BASE_DIR, "fulltext_index"), 'ENGINE': 'xapian_backend.XapianEngine' }, } LOGGING = { # Copy the complete LOGGING section from settings.py and change the path as follows, if there is a way of just adding the relevant path override to this file let me know. I am doing this only because I didn't create a symlink for /opt/mailman/logs. 'version': 1, 'disable_existing_loggers': False, 'filters': { [...] } }, 'handlers': { 'mail_admins': { [...] }, 'file':{ 'level': 'INFO', 'class': 'logging.handlers.WatchedFileHandler', 'filename': os.path.join(BASE_DIR, 'var/logs', 'mailmansuite.log'), 'formatter': 'verbose', }, 'console': { [...] }, }, 'loggers': { 'django.request': { [...] }, 'django': { [...] }, 'hyperkitty': { [...] }, 'postorius': { [...] }, }, 'formatters': { 'verbose': { [...] }, 'simple': { [...] }, }, } Try running /opt/mailman/bin/mailman-post-update and choose to rebuild indexes, see if the static files get saved to /opt/mailman/static and the search indexes get saved to /opt/mailman/fulltext_index. In my case I had plenty of indexing to do, not sure if these files are created on a green-field installation with nothing archived. This command will also populate the Postgresql database schema. See if the Systemd units for mailman-web and mailman-cluster come up. Observe logs. If everything ok the Gunicorn should be listening on localhost:8000. For Nginx integration I followed the wiki, only change I had to make was to send the host header to the backend server, here is a partial config file: server { server_name lists.domain.com; root /var/www/lists; access_log /var/log/nginx/lists-access.log; error_log /var/log/nginx/lists-error.log warn; listen [::]:443 ssl; # managed by Certbot listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/lists.domain.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/lists.domain.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot location = /favicon.ico { log_not_found off; } location = /robots.txt { log_not_found off; } location / { proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $host; proxy_pass http://localhost:8000/; } location /static { alias /opt/mailman/static; } } server { if ($host = lists.domain.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80; listen [::]:80; server_name lists.domain.com; return 404; # managed by Certbot } For Exim integration I followed to the letter the information here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#exim Here is a Logrotate script which is not in the Mailman wiki: /opt/mailman/var/logs/*.log { missingok sharedscripts su list list postrotate /opt/mailman/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/var/gunicorn.pid ]; then PID=`cat /opt/mailman/var/gunicorn.pid` kill -s USR1 $PID fi endscript } I have been running this setup since March 2020, I run around 10 lists on this server with around 10 mails per list per day. I actually had more issues when moving from Mailman2 to Mailman3 using the Docker containers and actually this process made me understand a lot more how everything hangs together and where to troubleshoot issues. Hope this helps someone out there. Andrew. -----Original Message----- From: Matthew Alberti <matthew(a)alberti.us> Sent: 01 January 2021 02:48 To: ieso(a)johnwillson.com Cc: 'Mailman users' <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Easiest way to install a new mailman3 deployment? I had a very similar experience. I don't mean to knock the dev team; Mailman3 is an awesome tool that really meets a need. It is really much much more than a 'tool.' A very comprehensive software suite. For me, I ended up using the docker option on Ubuntu 20.04. My advice is to give up on the idea of using OS package managers. They just aren't current enough (certainly for Ubuntu LTS), or updated frequently enough, for the current development of Mailman3. Nothing but problems for me on Ubuntu, and Debian is about the same. Pypi, or installation in a virtualized environment, was equally challenging. I strongly recommend the docker installation method. It is not quite turnkey, but the documentation is close enough where it might 'just work' in your environment. I used MariaDB, and that introduced some challenges. If you are using postgre, postfix, and nginx, you are pretty close to a very easy installation. This list is very supportive, with very frequent responses from the core dev team. And there are guys like me who really struggled to get to a production instance. Please let us all know what isn't working in the docker approach, and we will try to help I'm sure. - Matt Alberti ⁣Get BlueMail for Android On Dec 31, 2020, 8:15 PM, at 8:15 PM, ieso(a)johnwillson.com wrote: >So I've been trying for the last two weeks to get a new mailman3 server >running on a virtualized server (any server), and I'm turning to this >list after having failed many times and running out of holiday time. > >I started trying a non-docker installation on Ubuntu 18.04 >(https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V >5PlantPTs/edit#) , which got me the closest. Except I had a problem >with inbound email only being triggered when it came from certain >accounts. But that clearly wasn't good enough for production, so after >many attempts to figure out where it was failing, I decided to turn to >docker as a solution that should be cleaner. > >A few attempts at doing a docker installation on digitalocean.com >failed, which I realized might be due to it not routing private IP >addresses, so I moved to AWS after checking that their VPC policy would >fit mailman's docker requirements. I found a great but slightly >outdated guide on how to do this >(https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) >By this point I knew enough to correct a number of places where the >environment had changed since the procedure was written, but postorius >still failed at the curl test. > >The challenge for me has been the difficulty to know how to >troubleshoot the different different systems and network infrastructure >that are used to keep mailman3 humming. I've tried about 7 different >installation walkthroughs (there are no recent ones on Youtube by the >way, in case anyone wants to seize that opportunity!), and the good >guides provide ways to check each stage to try to help you a bit on >that front. > >Nonetheless, I feel stuck and thought I'd ask the simple question... >for a completely basic, barebones new installation, what's the easiest >way to get a mailman3 installation up-and running? (e.g. Which server >provider? Which operating system and version? Docker or otherwise?) > >Any pointers highly appreciated. Google Groups is clearly on its way >out, as it no longer allows for people to easily join groups by sending >an email or clicking a link, so that should be a big opportunity for >mailman3 to step up and help give those mailing list migrants a new >home... which is what we're looking for. We're just not quite as smart >as you guys. ;-) _______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe >send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 8 months

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

by Stephan Krinetzki

Hi Mark, Mark Sapiro wrote: > On 2/3/22 08:01, Stephan Krinetzki wrote: > > Hello all, > > we now have at least one mailing list (there may be more affected) that generates a 500 error when calling the held_messages page. After looking at the held messages via the mailman shell, we have identified three mails that have neither a subject nor a message body. How can we remove these three mails from the database? > > This shouldn't be an issue, at least with Mailman core 3.3.5, unless I > don't understand. > Note that there are 3 tables involved. The request (IListRequests), the > pendings (IPended and IPendedKeyValue), and the held message > (IMessageStore). > > This is the mailman shell command we used: > > mailman shell -l listname(a)lists.example.com > > <removed> > > Welcome to the GNU Mailman shell > > Use commit() to commit changes. > > Use abort() to discard changes since the last commit. > > Exit with ctrl+D does an implicit commit() but exit() does not. > > Die Variable 'm' ist die listname(a)lists.example.com Mailingliste > > >>> msg_db = getUtility(IMessageStore) > > >>> req_db = IListRequests(m) > > >>> reqs = list(req_db.held_requests) > > >>> for req in reqs: > > ... print('{}: {}'.format(req.id, req.request_type)) > > ... > > 32598: 1 > > [...] > > 107656: 1 > > 107737: 1 > > 107758: 1 > > > > OK, you have requests. > > >>> from mailman.app.moderator import handle_message > > >>> handle_message(m, 107758, Action.discard) > > >>> reqs = list(req_db.held_requests) > > >>> for req in reqs: > > ... print('{}: {}'.format(req.id, req.request_type)) > > ... > > 32598: 1 > > [...] > > 107656: 1 > > 107737: 1 > > > > OK, you discarded the message held with request id 107758. > > >>> handle_message(m, 92927, Action.discard) > > Traceback (most recent call last): > > File "<console>", line 1, in <module> > > File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/app/moderator.py", line 112, in handle_message > > key, msgdata = requestdb.get_request(id) > > TypeError: 'NoneType' object is not iterable > > >>> > > > > There is no request with id 92927. Why do you think there should be? Well, i truncated the list above (marked by [...]) but this message is there: 32598: 1 107788: 1 22449: 1 95736: 1 108279: 1 66937: 1 108367: 1 68261: 1 108379: 1 108411: 1 108587: 1 108596: 1 108723: 1 107881: 1 107891: 1 108814: 1 92927: 1 107963: 1 106486: 1 106488: 1 106526: 1 106577: 1 106682: 1 106818: 1 106857: 1 108076: 1 106926: 1 107044: 1 107146: 1 107152: 1 107153: 1 107204: 1 108199: 1 107210: 1 107329: 1 107394: 1 107447: 1 107531: 1 107562: 1 107594: 1 107656: 1 107737: 1 > If by remove them from the database, you mean just from the > messagestore, you can do (using your above) > msg_db.delete_message('the_message_id') Ok, thanks. With this code lines the message is deleted, right? > To delete a pending request for which there is no request id, e.g. the > id 92927 above, you could do > pendings = getUtility(IPendings) > for token, data in pendings.find(pend_type='held message'): > if data and data['id'] == 92927: > pendings.confirm(token, expunge=True) > That didn't helped: mailman shell -l list(a)lists.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. Die Variable 'm' ist die list(a)lists.example.com Mailingliste >>> msg_db = getUtility(IMessageStore) >>> req_db = IListRequests(m) >>> reqs = list(req_db.held_requests) >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... 32598: 1 107788: 1 22449: 1 95736: 1 108279: 1 66937: 1 108367: 1 68261: 1 108379: 1 108411: 1 108587: 1 108596: 1 108723: 1 107881: 1 107891: 1 108814: 1 92927: 1 107963: 1 106486: 1 106488: 1 106526: 1 106577: 1 106682: 1 106818: 1 106857: 1 108076: 1 106926: 1 107044: 1 107146: 1 107152: 1 107153: 1 107204: 1 108199: 1 107210: 1 107329: 1 107394: 1 107447: 1 107531: 1 107562: 1 107594: 1 107656: 1 107737: 1 >>> for req in reqs: ... print(req.key) ... for line in str(msg_db.get_message_by_id(req.key)).split("\n"): ... print(line) ... print('\n') ... <1b35d982.85b92.16abbe857a6.Coremail.lusong(a)lsec.cc.ac.cn> None <08539546582c0560693f58ab0101bd83(a)airotrader.com> <Mail Content, shorted out> <1545090824.237969198(a)f452.i.mail.ru> None <tencent_41D5C02D27CAA4DD59BDF1A2(a)qq.com> <Mail Content, shorted out> <292716975.841376.1597725820301.JavaMail.zimbra(a)rri.res.in> <Mail Content, shorted out> <5d74c171c32303e88c9d8b86ac60ba48(a)blackroseradio.com> <Mail Content, shorted out> <DM6PR04MB38208B40539F3861A613098DB1260(a)DM6PR04MB3820.namprd04.prod.outlook.com> <Mail Content, shorted out> <eaefd169fb428442d9e3ce31b72bfdb4(a)wordenonwine.com> <Mail Content, shorted out> <2108728073.11037004.1643524877756.JavaMail.zimbra(a)caxias.rs.gov.br> <Mail Content, shorted out> <CANvwqssiPV7HgupqrYkgxGoFsKph=TW-mwNucs+NBwxs3Uw1bQ(a)mail.gmail.com> <Mail Content, shorted out> <c0b951ee190727163bce555a3a030f9f(a)optiboxes.com> <Mail Content, shorted out> <144a5727a850fea01910dfe9c427427e(a)licensedappraisal.com> <Mail Content, shorted out> <61ef2070.1c69fb81.f2f7e.23fc(a)mx.google.com> <Mail Content, shorted out> <b037941f4318324ab23a3ee7efcbf970(a)hollymillrun.com> <Mail Content, shorted out> <929ad585ea426a3835cf63058c22782c(a)airotrader.com> <Mail Content, shorted out> <180a36ee.2b.17afe0b825e.Coremail.carmark3(a)163.com> None <24abca1072b83535bbf2e39b6a825fc8(a)optiboxes.com> <Mail Content, shorted out> <CAK69=c9mFvOZq9ro7HavgYdOeo-oJ2_6h8SjQsBfcrxnpf_etA(a)mail.gmail.com> <Mail Content, shorted out> <5d7b548ab086bb47c0c6caacbff92c54(a)licensedappraisal.com> <Mail Content, shorted out> <062dfa1a2deb3ac136ecdfde1b4c6d74(a)optiboxes.com> <Mail Content, shorted out> <d517a99e8e9db94ddc8ecd1c6d226788(a)spiritsestates.com> <Mail Content, shorted out> <043051c1d7a64c04ce8c83c7a5e54eec(a)krswim.com> <Mail Content, shorted out> <2c42b1d628a43b1fc78471e873a0691d(a)totallyneat.com> <Mail Content, shorted out> <CALQ9jAcqu9yRj=EYn=DgA8unYRWkfUgFiL54bMiLxovc+JXcBw(a)mail.gmail.com> <Mail Content, shorted out> <1ffa446361bfdf49a71b8669165e6350(a)wordenonwine.com> <Mail Content, shorted out> <b9afc5d32f87320a8333093ffd0635f5(a)infnitsolutions.com> <Mail Content, shorted out> <f486ea12a6bcecec1b1e4a51f1be0719(a)penshaver.com> <Mail Content, shorted out> <CAPOYRqVmrwcdRQXwm56sM+0Ov1bcLqxFXFCrx5Rf3gVqj9nOgA(a)mail.gmail.com> <Mail Content, shorted out> <1412096130.6666950.1642348478679.JavaMail.zimbra(a)gorontaloprov.go.id> <Mail Content, shorted out> <40f51428847f7874d06b8b5ad50c745d(a)wordenonwine.com> <Mail Content, shorted out> <2a82c4a5e577658efc189f02fc13f520(a)nutriholding.com> <Mail Content, shorted out> [And a lot of more messages] As you can see, there a some messages, that have no message body and i think that's the issue. In the httpd.log of mailman: 2022-02-04 10:01:09 [FALCON] [ERROR] GET /3.1/lists/list(a)lists.example.com/held?count=10&page=1 => Traceback (most recent call last): File "falcon/app.py", line 361, in falcon.app.App.__call__ File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/rest/post_moderation.py", line 182, in on_get resource = self._make_collection(request) File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/rest/helpers.py", line 182, in _make_collection entries = [as_dict(resource) for resource in collection] File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> entries = [as_dict(resource) for resource in collection] File "/opt/mailman/mailman-venv/lib64/python3.6/site-packages/mailman/rest/post_moderation.py", line 173, in _resource_as_dict assert resource is not None, resource AssertionError: None [04/Feb/2022:10:01:09 +0100] "GET /3.1/lists/list(a)lists.example.com/held?count=10&page=1 HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.3" Maybe that helps to identify the issue. > Mailman core 3.3.5 has a lot of changes to address this issue. > Also see https://gitlab.com/mailman/mailman/-/issues/946

3 years, 7 months

[MM3-users] Re: Issues with migrating from Mailman2 to Mailman 3

by Uwe Grasshoff

Hi, > I'm not sure about the error, but the import21 process registered you so > what you need to do is go to the Login page, click "Forgot Password?" > and then request a password reset. The reset also failed with the error message that okay I have finished a few more steps on the way to containerized mailman ;-) The mailman-web container also needs the environment variables which tells mailman-core to use postfix on an other host for delvery. But still I can't recover a password. It always tells me "Diese E-Mail-Adresse ist keinem Konto zugeordnet" which means "This e-mail address is not assigned to any account". But when I now register I can see all the lists which I'm assigned to. So basically my problem was the missing environment variables > - MTA=postfix > - SMTP_HOST=mail I though it's only needed for the core container but they also need to be assigned to the web container. With best Regards Uwe Grasshoff

5 years, 11 months

[MM3-users] Re: Migration from old server to new server failed

by Mark Sapiro

On 2/16/24 07:12, Helio Loureiro wrote: > - start mailman3 and mailman-3web > - run mailman3-web migrate You should run mailman3-web migrate when mailman-3web is not running. > django.db.utils.OperationalError: (1050, "Table > 'hyperkitty_mailinglist_moderators' already exists") > > I tried to drop the table, but then it complained about another one. I > dropped all the complained tables and as result hypperkitty never > started. So I went back to see why the first error happened. The errors occurred because you had recently added tables in your database so they couldn't be added by the migrations. Dropping the tables was the correct thing to do. Did you ultimately successfully run all the migrations? When you say `hypperkitty never started`, what exactly does that mean? What happens when you try to access the archives? Can you access postorius? Are any errors logged in mailman3-web's log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Mohsen Masoudfar

I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. I get in the logs messages like below with several Queue-ids: Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed Mohsen ________________________________ From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 7:47 AM To: Andrew Hodgson <andrew(a)hodgson.io>; Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Is there a way of recording bounce messages? [EXTERNAL EMAIL] Hi. Seems other people have had this on Office365 when I searched the specific error. I have enabled VERP now on probes and all list messages so lets see if that improves things. Thanks. Andrew. -----Original Message----- From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 12:22 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to andrew(a)hodgson.io _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

1 year, 11 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Mon, 7 Jan 2019 at 23:07, <brian(a)emwd.com> wrote: > Did you change your settings_local.py file to match mine? > > Yes, almost everything. > For the docker-compose.yaml file: > > For the mailman-core, yours looks just like mine except I have: > > stop_grace_period: 30s > So you just added: - stop_grace_period: 30s to the block?? > I don't know if that setting makes any difference. I am also using the > included postgres database instead of mysql. > > For the mailman-web section, you need to add the following: > > - SERVE_FROM_DOMAIN=yourdomain > - MAILMAN_ADMIN_USER=youruser > - MAILMAN_ADMIN_EMAIL=youradminemailaddress > The mailman-web section has sub-sections. Under which one do I add these? environment?? Or networks below the IP address? > I have no quotes in the above 3 settings. > > What webserver are you using with your MM3 installation. > I have apache2 and nginx on the server. Apache listens on 80 and 443 while nginx listens on 8080 and 8443. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 8 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/29/20 5:17 AM, Brian Carpenter wrote: > > On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >> On 29/10/2020 01:57, Brian Carpenter wrote: >>> With Mailman 3, every list owner has the ability to remove a reply in >>> a thread, a complete thread, and even the entire archives. That is a >>> welcome difference from MM2 in my opinion. >> >> A very welcome difference, only I don't see this option in the web >> interface of my debian 3.2.1 installation. Is this a shell only >> option, 3.3 feature or configuration option I have missed? > It is not a shell option. It can be done via Hyperkitty but I am not > sure when that feature showed up. Actually, with current HyperKitty, only site admins can remove messages or threads or the archive. The ability for list owners to do it is <https://gitlab.com/mailman/hyperkitty/-/issues/261>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Mark Sapiro

On 11/11/20 4:18 PM, Brian Carpenter wrote: > > Some sort of auto-discard procedure after a number of retries? Is it > possible to detect a message with a null characters and automatically > discard them? Do such messages make it into the thread table? The message has been delivered to the list, but it is not archived. The list post has an Archived-At: header with a URL, but the message isn't there at all. The only way to get it archived is to correct the message defect. Thus, I don't think it's good to just discard the message at that point. I'm fine with moving out of or not queueing it in the first place in var/archives/hyperkitty/spool, but I think it should be preserved somewhere, say in var/archives/hyperkitty/bad, and along with that, some kind of notice sent to the site admin so bad messages don't just accumulate without being seen. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Odhiambo Washington

Which script? I think it should run easily as long as it relies on mailman-web. I run mailman-web with several arguments from a single bash script in my several MM3 setups. On Sat, Apr 1, 2023, 00:18 Andrew Hodgson <andrew(a)hodgson.io> wrote: > Hi. > > Has anyone managed to get this script running using the Mailman-Web setup > in a venv? It was working when Settings.py was in the /opt/mailman/mm > directory but since moving to Mailman-Web has it in /etc/mailman3. I have > been trying to import Mailman-Web to get the Django environment running but > every time I do this I get a not configured exception raised. > > Thanks. > Andrew. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 5 months

[MM3-users] Re: Importing mbox files into archive defect with lines with From

by Mark Sapiro

On 9/19/23 2:25 AM, Alex Schuilenburg via Mailman-users wrote: > > Prefixing the line with '>' allows the hyperkitty_import to partially succeed - partially as the line and everything below it is omitted from message in the archive. Presumably because the archiver thinks the remainder is a quote which it omits? > > Prefixing with a single whitespace was the best work-around, since the renderer ignores it when viewing the message from the archive. As discussed earlier in this thread, issues with unescaped 'From ' lines in message bodies exist because of the format of *nix mbox files where lines beginning with 'From ' are message separators by definition. Escaping such lines by prefixing them with `>` is a defacto standard. As far as this causing HyperKitty to ignore the rest of the message is concerned, I do not see that with current HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/12/2016 09:26 PM, Barry Warsaw wrote: > On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: > >> It is the intent that Postorius will eventually expose all these >> settings. We're not there yet. At present you could possibly do this by >> interacting with mailmanclient, although I'm not certain the settings are >> exposed there. > > I'm not sure if they're exposed in mailmanclient, but they are exposed in the > core's REST API, on the member resource. It's the `delivery_mode` attribute > and it takes as legal values one of 'regular', 'plaintext_digests', > 'mime_digests', and 'summary_digests' (IOW, the enum item names for the > DeliveryMode enum). They are exposed in mailmanclient and are used in postorius. They can be found in the users personal subscription settings https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > Cheers, > -Barry > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

9 years, 4 months

[MM3-users] Immediate notification to the administrator

by pau.baiges＠csuc.cat

Hello In Mailman, I have all the lists marked with the "Immediate notification to the administrator" option. Should list moderators receive immediate notification of new requests as well as daily reminders about the pending ones? List moderators (and list administrators) receive daily reminders of pending requests for approval, such as subscriptions to a moderated list or submissions that are held for some reason. Enabling this option results in immediate notifications being sent upon the arrival of new requests. When there's a message being held because it needs approval, it automatically sends an email to the list owners. However, it also states that it sends a daily reminder if the email remains unapproved, but it's not doing that. I'll show you how I have /etc/postfix/transport configured. I receive the first "owner" email, but not the daily one. list-owner(a)llistes.csuc.cat relay:[ip]:25 list(a)llistes.csuc.cat .. list-admin(a)llistes.csuc.cat ... list-bounces(a)llistes.csuc.cat ... list-confirm(a)llistes.csuc.cat ... list-join(a)llistes.csuc.cat ... list-leave(a)llistes.csuc.cat ... list-request(a)llistes.csuc.cat ... list-subscribe(a)llistes.csuc.cat ...

1 year, 10 months

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 19:33, Mark Sapiro wrote: > On 8/6/21 10:28 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > >> Thanks. Now it's no showing errors (and nothing at all) but >> apparently it does nothing. The non mebers of the list (the few that >> remains: I've been deleting one at a time from the web) aparently >> still are there.. >> >> Knowing the correct procedure will ease me to try tomorrow with a >> clean head. > > It doesn't report anything, and if you don't commit() or exit with > control-D, any changes will be rolled back. I think I did a typpo. (forgot to add "()" after the "commit" sentence). And exit with quit() maybe not helps. I've done it exactly as you wrote it and it worked like a charm. Thank you very very much > > What does > > list(m.nonmembers.members) > > show before doing the unsubscribe() and commit() and then what after? >

4 years, 1 month

[MM3-users] Re: Sending to mangled 'From' addresses.

by Jeremy Stanley

On 2024-06-01 09:49:54 -0700 (-0700), Mark Sapiro wrote: [...] > If this is the result of a `reply` and not `reply-all` the client > is not behaving reasonably. [...] I haven't seen it with replies, but rather mail clients recording every address they see into their address book, and then when the user of such a client wants to send new mail to someone they start typing that person's name and their mail client happily auto-completes it with the mailing list's address instead of the intended personal address. This is one of the reasons we don't use DMARC mitigations for most of our lists, and instead we just try to make Mailman avoid altering anything in the message headers or body that might invalidate DKIM signatures (so no changing From or Reply-To, no adding list-specific subject prefixes, no appending list unsubscribe info to the end of messages...). It's an unfortunate trade-off, but some of our users do tend to get confused by address book pollution. -- Jeremy Stanley

1 year, 3 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen and in > the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Immediate notification to the administrator

by Mark Sapiro

On 11/2/23 07:48, Stephen J. Turnbull wrote: > > Until then, here's the crontab template distributed with Mailman 3.2.2: > > # At 8AM every day, mail reminders to admins as to pending requests. > 0 8 * * * @PYTHON@ -S @prefix@/cron/checkdbs > # > # At 9AM, send notifications to disabled members > 0 9 * * * @PYTHON@ -S @prefix@/cron/disabled > # > # Noon, mail digests for lists that do periodic delivery. > 0 12 * * * @PYTHON@ -S @prefix@/cron/senddigests > # > # Every 5 mins, try to gate news to mail. > */5 * * * * @PYTHON@ -S @prefix@/cron/gate_news > # > # At 3:27am every night, regenerate the gzip'd archive file. Only > # turn this on if the internal archiver is used and > # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py > 27 3 * * * @PYTHON@ -S @prefix@/cron/nightly_gzip This Mailman 3.2.2 cron/crontab.in.in file is is an artifact from Mailman 2.1. Nothing there is relevant to any Mailman 3 version -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Abusive user creation - ideas for mitigating

by Andy Smith

Hi, My mailman3.auth_users table contains 131 rows, of which 113 of them were created in the last week. All of these users have a 10 character long random string of lowercase letters as their chosen username. Their email addresses are all over the place. I only noticed this was happening because an unusual number of the subscription confirmation messages were bouncing back to me as postmaster, and I saw the unlikely user names. I matched up some of the date_joined timings with logs of HTTP POST to /mailman/accounts/signup and every single one so far was a unique IP address. So I am not going to get very far with firewalling. Does anyone have any suggestions what I can do to avoid this? Specifically what I would like to avoid is sending a confirmation email to these potentially innocent addresses. … Hmm, actually I've just noticed that all of them are Tor exit nodes. Looks like I could probably autogenerate an Apache ACL that lists all Tor exit nodes and bans them from posting to /mailman/accounts/signup. Thanks, Andy

10 months, 2 weeks

[MM3-users] Re: Mailman 3 Installation Assistance

by Abhilash Raj

On Sat, Mar 31, 2018, at 9:33 AM, brian(a)emwd.com wrote: > I am making a serious attempt at installing Mailman 3 using docker. I > have a CentOS 7 server setup via Linode. I am using the following > documentation to setup a Mailman 3 server: > > https://xiaoxing.us/2018/01/02/Deploy-Mailman-3-on-AWS-using-Docker/ The official docs for container images sits here[1]. Although, I wen through the above blog very quickly and it seems to me that most of parts related to Mailman are pretty straightforward and similar to official docs. [1]: https://asynchronous.in/docker-mailman/ > > I have Docker, Postfix, and Nginx installed and working fine. The > installation of the Mailman 3 container went fine. However I am getting > the following error when I go to test Posterius via shell: > > curl http://172.19.199.3:8000/postorius/lists/ > curl: (7) Failed connect to 172.19.199.3:8000; Connection refused There are few things you can do to debug: 1. check if mailman-web container is even running $ docker ps 2. check if there are anything in /opt/mailman/web/logs/ . -- Abhilash Raj maxking(a)asynchronous.in

7 years, 5 months

[MM3-users] Re: Strange issue with bounce processing

by Brian Carpenter

On 12/25/20 10:07 PM, Mark Sapiro wrote: > On 12/25/20 6:36 PM, Brian Carpenter wrote: >> Dear List, >> >> First of all Merry Christmas to those of you that are observing it. >> >> I have an issue on one of my Mailman 3 servers. The bounce runner is not >> running, even after restarting mailman core. All the other runners are >> working fine. Here is the problem, after restarting it, a number of >> messages show up in queue/bounces from a single list. > > What happens if instead of restating core, you stop and then start it? Same behavior. > I don't really understand what's going on. The only messages which get > queued in queue/bounces/ are messages to the LIST-bounces address > delivered from the MTA, unless possibly they are somehow in queue/retry/ > and being retried. What do you see in the MTA logs? > The mail logs shows bounce notifications being sent out as per the list settings. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Mark Sapiro

On 10/24/23 3:56 PM, Thomas Ward via Mailman-users wrote: > > When I DO NOT have the module loaded in the configuration, `mailman > shell` works. Since that was functional, I went into the shell and > executed this: > > > from mailman_customizations.hooks import MailmanCustomizations > > This worked fine, but obviously importing the class doesn't necessarily > *activate* the class. So something is up with how I'm *supposed* to > activate the plugin in the config, and we know that it's visible to > Mailman in its shell, but it can't autoload it. I'm past the limit of my knowledge here and only stabbing in the dark, but what happens after you import it. Can you instantiate it, e.g. ``` instance = MailmanCustomizations() dir(instance) ``` I'm not saying this should succeed, just that it may possibly provide useful information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Cannot show archives

by Mark Sapiro

On 9/26/19 5:48 PM, Qiuhong.Su 蘇秋紅 wrote: > Hi all, > > After I setup mailman3 and run mailman-suite, I can do: > > 1. Register user > > 2. Login > > 3. Create new Domain > > 4. Create new List > > 5. Subscribe to the list > When I try to send email to the list by run command: echo “test email” | mail –s “test email” test(a)example.com > User test can receive this email, but I cannot find it on Archives, and other members cannot receive this email too. You say "User test can receive this email". Is test(a)example.com a user or the list's posting address? If you are saying that test(a)example.com should be the list's posting address, but the mail is instead delivered to the user test(a)example.com, you have not set up your MTA to properly deliver list mail to Mailman. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Docker mailman3 delete social logins, did something change?

by bob B

for version tag you mean the docker images? 509940b4c44f maxking/mailman-web:0.3 mailman-web maxking/mailman-core:0.3 Also this works for /opt/mailman/web/settings_local.py ************** #allowed_hosts = ['127.0.0.1', 'localhost','Redacted]'] ALLOWED_HOSTS = ['127.0.0.1','localhost','[Redacted]','172.19.199.3','172.19.199.1','172.19.199.4','172.19.199.1'] #ALLOWED_HOSTS = ['*'] DEBUG = True #DEBUG = False EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'Redacted' EMAIL_PORT = 25 ******************* But, if I even add in one line like MAILMAN_WEB_SOCIAL_AUTH = []. so i would have ************** #allowed_hosts = ['127.0.0.1', 'localhost','Redacted]'] ALLOWED_HOSTS = ['127.0.0.1','localhost','[Redacted]','172.19.199.3','172.19.199.1','172.19.199.4','172.19.199.1'] #ALLOWED_HOSTS = ['*'] DEBUG = True #DEBUG = False EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'Redacted' EMAIL_PORT = 25 MAILMAN_WEB_SOCIAL_AUTH = [] *********** When I try to add the items in tot remove social media, It basically acts like my /opt/mailman/web/settings_local.py. file is ignored and does not load. I do not get debugging. the log says my domian name is not an allowed which is a sympton that this file did not load. So it appears that adding a section to remove the social media apps, stops this file from being loaded???

4 years

[MM3-users] Re: URLs in moderation messages

by Mark Sapiro

On 3/3/23 01:55, Tim Cutts wrote: > > I’ve clearly got something wrong in my configuration, but I can’t work out what. > > All my URLs seem to have the “mailman3” part duplicated, i.e. > > Https://example.com/mailman3/mailman3/lists > > Is where I have to go to get a list of my mailing lists, which just doesn’t seem right. > > In my settings.py file I have: > > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com/mailman3/' > > If I change the value of this to just https://example.com/ it doesn’t change this, That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… for Apache. -- 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: clicking on a username when viewing a thread results in "Page not found"

by Mark Sapiro

On 6/26/23 12:20 AM, Ken Alker wrote: > If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? This is a problem. That link goes to, e.g., https://example.com/archives/users/<user_id>/. What do you get if you strip the user_id and just go to what https://example.com/archives/users/ translates to on your system? You should get a page saying ``` Not implemented This feature has not been implemented yet, sorry. ``` If you get a 404, there is an issue with your web server configuration or maybe your top level urls.py. > Also, why is it that some usernames are not clickable (ie. black text with no hyperlink)? I'm not sure without research. -- 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: Displaying addresses in emails from a Mailman 3 installation

by Mark Sapiro

On 7/4/25 11:08, Steve Brown via Mailman-users wrote: > Yes, I intended to post to the list. I now see that if I use the archives > to post (as I'm doing now), I have to use "reply all". On my Outlook, it's > the other way around. If I want to reply off-list, I have to click on > reply all and then remove the list address. Sorry. I only use the Gmail > address for a few limited purposes. I don't understand. When I reply from HyperKitty, the reply just goes to the list whether I enter the reply in the web UI or "Use email software". There is no "reply all" option and no way to reply to the poster other than using the "Use email software" method and manually adjusting the recipient addresses. Is this not the case with you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 2:11 AM, Paul Arenson wrote: > Hi > > The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. It should be the same as Mailman 2.1. What are your settings for content filtering. In Postorius the only thing exposed are Settings -> Alter Messages -> Filter content, Collapse alternatives and Convert html to plaintext. If this Filter content Yes, content is filtered according to the other two settings and MIME parts may be removed according to the list settings filter_types, pass_types, filter_extensions and pass_extensions. These settings exist in core, but aren't exposed in Postorius. For a new MM3 list these settings are empty, but for a list imported from Mailman 2.1, they are set according to the corresponding MM 2.1 settings. I suspect in your case the issue is Filter content and Collapse alternatives are both Yes. Or perhaps the issue is HyperKitty's rendering of the message > As well, links were weird. > > LINKS > ===== > Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). > > URL > === > So while I typed > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... > > It came out double as > > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") I think the doubling is due to your MUA. The truncation of the displayed link in HyperKitty is expected, but the link itself should reference the full URL. > The embedded one did not come out embedded buy showed the text like this: > Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか > <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... What do these look like in the message received from thge list as opposed to HyperKitty? > QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? > (Even the web archive shows this problem though): > > https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See what this looks like at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > See the top item Homeless man drowns in river during Typhoon and what I mean. The first of those 3 links actually works. The other two don't work because the Japanese characters have been encoded as hex values by your MUA (which may be HyperKitty if you are posting via HyperKitty. To answer your question, you can just type the URL as you did above in your thread link, or you can surround it with angle brackets as I did in my message link. If you don't use angle brackets, it should be surrounded by whitespace to avoid ambiguity. See <https://www.rfc-editor.org/rfc/rfc3986#appendix-C> > IMAGE > No image appears though one was added inline. > > And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). > > So are there guidelines one whether/how to attach an image so that it makes it? Are you posting via email or HyperKitty? If by email, I suspect the issue is Filter content and Collapse alternatives are both Yes. If by HyperKitty you can only post plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: eccentric setup question

by Mark Sapiro

On 3/21/23 02:05, Jeff Berry wrote: > > The problem we're having is that if the mailman domain of the list is listserver.domain.com then spamfilters start to flag the mail since it looks like spoofing/malformed headers and so on. If the mailman domain is just domain.com then postfix rejects it with an unknown local recipient error. I though I might be able to just tweak the incoming mail headers in postfix via header_checks but that's not working, either because I've got the wrong check or it's the wrong approach, or both. > > postfix relay_domains might do it, I think, but if it maps listserver.domain.com to domain.com that would break the listserver domain mailing lists (I think). Is Postfix on the mailman server set up per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… and did you run `mailman aliases` to regenerate mappings after changing Exchange to relay to list(a)domain.com? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Thread matching query does not exist

by maria-haider＠hotmail.com

Hi, I had the same errors after I deleted a couple archives using the mechanism below from manage.py shell. from hyperkitty.models import MailingList ml = MailingList.objects.get(name="yourlist(a)example.com") ml.delete() The errors in the mailman3-web logs were such. INFO Process-1:1 processing [rebuild_thread_cache_votes] 12:10:34 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. 12:10:34 [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] 12:10:34 [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. Running the daily/monthly/yearly runjobs by hand did not solve the issue. Then I logged into the django admin from the web interface and deleted the queued tasks with the same names of the processes which were failing. I even deleted the failed tasks, but I am guessing it was unnecessary. I don't see the errors anymore. But I still have the other issues which were mentioned in other posts that have to do with not updating the number of messages and participants and not showing the messages sent from the email client of the subscribers in the hyperkitty archive.

5 years, 5 months

[MM3-users] Re: adding imprint / private policy link to postorius

by Abhilash Raj

On Tue, Sep 1, 2020, at 11:17 PM, Thomas Stein wrote: > > Hello one and all. > > Is it possible to add an imprint link to the postorius start page? I > guess it is, but it would be > nice if someone could me point to the right direction / documentation. > Something like they have: > > https://lists.openrailwaymap.org/mailman3/postorius/lists/ > There isn't an official way to do that, but you can patch your installation to update the footer. This[1] is the location and file you want to update and you can insert simple HTML there. If you are using system packages it should be somewhere in the `/usr/lib/python3/dist-packages` directory and in `lib/site-packages` if you are using a virtualenv based installation. https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/… > cheers, t. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years

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

by Mark Sapiro

On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: > > 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 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. -- 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: How To Install Mailman 3 on Debian 10 (Complete Guide)

by jonathan.mailing.lists＠gmail.com

> -----Original Message----- > From: Abhilash Raj <maxking(a)asynchronous.in> > > Is there a specific reason that you chose to go with an entirely new doc > rather than helping to improve the existing one? Several parts of it (at > least the ones that official guide covers) seems similar to me and is > duplicate information that at least two people are going to spend time > writing and maintaining in future. The official guide is for people who really know what they are doing (including those wanting to use Mailman on various existing systems). Mark's helpful articles are useful but also assume a certain amount of prior knowledge. I just need instructions I can follow to start from scratch on a new VPS. I don't mind whether it is for Linode and Debian, Digital Ocean and Ubuntu, or whatever. If this is the "idiot-proof" guide I mentioned in an earlier thread then it's a very welcome development for Mailman 3. Best wishes Jonathan

4 years, 6 months

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

by Stephen J. Turnbull

Odhiambo Washington writes: > Hello Stephen et al, > > Since this topic is relevant to something I am faced with at the moment, I > believe it's okay if I piggyback on the thread. I think continuing the thread is appropriate, but I personally would change the Subject to reflect the specifics. > I have a server that is already actively distributing Mailman list traffic, > and managing users and archives. > I have offered to take over another community ML (also using MM3) from > another server and host the list on my server. > I am scratching my head bald trying to figure out how to bring in this > other MM3 site and list into my existing server, especially with regard to > the DB backend. > > The list - let's call it users(a)domainX.name was using MySQL backend and > had a separate DB for Mailman core and Mailman web. > I believe combining these into one isn't a problem. But getting to merge > this DB into my current one is what I am not sure about. > > Any pointers on how to bring in this new site into my current setup?? I don't have pointers, in the sense of concrete advice I would not be horrified if you followed it to the letter. Here's how I would attack the problem. 1. Decide the List-Id and List-Post questions. I disagree with Mark about List-Id (or maybe he mistyped List-Post?) -- the List-Id should NOT be changed. I don't know how many users are taking advantage of List-Id (my filters do!), but they will thank you for keeping it the same. The List-Post question is contingent. Will you be serving their domain, or will you change the List-Post address? Note that with some additional configuration to Mailman and your MTA they could set up a forwarding configuration for their lists to your server, Or if they don't have other email needs, set up an MX. Or they can transfer their domain name's A and MX records to your host. Alternatively you can change the List-Post address.to your domain. In that case you will have to edit the List-Post address in your database. 2. There are similar issues for mailman-web (especially host names). I have not thought about them at all, so I'll leave that for the interested reader. ;-) 3. (If the DB engines are different) Dump both databases in text format (ie, scripts of SQL commands). Check to see how they differ. 4. Adapt the foreign database to its new environment with search and replace. (Be verbose about the search terms, include lots of context to minimize the chance of inadvertantly replacing something in the wrong context that you missed in step 3.) This is where you would change the List-Post address, as well. You will also want to change the 'mailmanweb' database to just 'mailman'. 5. (Optional if your name is "Daredevil") Create a new Mailman suite install using your current configs, preferably in a new VM or set of containers. Configure the MTA to save all outgoing mail to a file, or maybe firewall off outgoing network traffic to port 25 and leave all the posts in the MTA queues. Create a new 'mailman-test' database. Copy all the dumps to the VM, and edit the names of the databases in the SQL to 'mailman-test'. Restore the dump of your system into the database, and test. Then do the same, restoring the mailman and mailmanweb databases from the foreign system into this new database. 6. Adjust to address any issues discovered in 5. If none, go to 7, Otherwise go back to 5. 7. Apply any changes made in 6 to your configs, and read the foreign dumps into your system, and you should be ready to go for the distribution part. Not sure about host and webserver configuration for mailman-web, though. Steve

1 year, 9 months

[MM3-users] Re: ValueError: ...:EVP_DigestInit_ex:disabled for fips

by Ralf Wiegand

Hello Mark, Can I substitute Django with something that will be FIPS complaint? Can I do without it? Thank You, Ralf On 5/19/20 1:02 PM, Mark Sapiro wrote: > On 5/19/20 5:57 AM, Ralf Wiegand wrote: >> (venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate >> Operations to perform: >> Apply all migrations: account, admin, auth, contenttypes, >> django_mailman3, django_q, hyperkitty, openid, postorius, sessions, >> sites, socialaccount >> Running migrations: >> Applying contenttypes.0001_initial...Traceback (most recent call last): > ... >> File >> "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", >> line 221, in names_digest >> h = hashlib.md5() >> *ValueError: error:060800A3:digital envelope >> routines:EVP_DigestInit_ex:disabled for fips* >> >> >> >> Hello group, I am running into this error. any idea what is going >> wrong here? > This is a Django issue, not Mailman per se. The migration that's failing > is django/contrib/contenttypes/migrations/0001_initial.py. A brief > search seems to indicate that this won't work with NSS FIPS. >

5 years, 3 months

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Mark Sapiro

On 3/27/21 2:08 PM, Brian Carpenter wrote: > I was testing out the process of rejecting an incoming subscription > request. Choosing the reject option for a moderated subscription request > does send out a rejection notice but it gives no reason for the > rejection. ... > Is there a place somewhere in Postorius to provide a rejection reasons > for moderated subscription requests? Does Mailman 3 core provide this > via its REST api but it is just not revealed in Postorius yet? It's in Postorius since 1.3.3. If in the held message view, you click the subject of a held message, you get a popup dialog the shows the message with options to also show headers or the raw message. There is also a dropdown t=o set the poster's moderation action and a box for a reject reason if you click the reject button in the dialog. Do you not see this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] logrotate

by Christian

I noticed that my mailman logfiles are not being rotated. I followed the instructions in https://mail.python.org/archives/list/mailman-developers@python.org/message/ FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ Now when I try and run logrotate I get the following error root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file or directory error: stat of /opt/mailman/mm/error.log failed: No such file or directory error: stat of /opt/mailman/mm/mailman.log failed: No such file or directory error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file or directory error: stat of /opt/mailman/mm/smtp.log failed: No such file or directory root@zarathustra: What am I doing wrong please? -----Original Message----- From: bob B via Mailman-users <mailman-users(a)mailman3.org> Sent: Tuesday, May 2, 2023 5:14 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: looking for more detailed traceback for shunted message Ok, thanks for looking. _______________________________________________ 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/ FLCRIRLKXM3VIT3VAN7TQNJLIB3LRXLR/ This message sent to csa(a)web-analysts.net

2 years, 4 months

[MM3-users] Configure new list via REST API - trying to add moderators

by Andy Matthews

I'm stepping into some existing code which creates a new list via the REST API. I know this works because I can shell into the mailman3 box and run `mailman lists` and it shows the newly created list. We're also submitting list config options via the `/lists/<list id>/config` endpoint, but there's a specific key that we have in our config map that doesn't appear in the REST API docs and I'm wondering about it. We have an array of strings called `moderator` that appears to send successfully. But looking at the docs for "Mailing list configuration" (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) I don't see anything named `moderator` The "Managing owners and moderators" docs (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…) indicate that we can perform add owners and moderators via a Python shell, but don't indicate that it's possible to do it via REST. Is this true?

1 year

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

by Mark Sapiro

On 7/30/25 07:27, Stephan Krinetzki wrote: > Hi all, > > I'm running into an issue with Mailman 3. Mails sent to a list are being held due to moderation settings — which is expected — but after approving them, they are not delivered to list members. Are there any regular members with delivery enabled? ``` mailman members --regular --nomail enabled LISTSPEC ``` > The message does not end up in the shunt queue, and nothing is delivered. > > Here's what I see in the Mailman log: > > Jul 30 16:12:23 2025 (213300) HOLD: mm(a)lists.example.com post from sender(a)sub.example.com held, message-id=<20250730141221.5VVrn%sender(a)sub.example.com>: The message is not from a list member > Jul 30 16:12:39 2025 (213338) held message approved, message-id: <20250730141221.5VVrn%sender(a)sub.example.com> This is expected. Is there anything relevant in Mailman's smtp.log? Do any posts to this list get delivered, e.g., posts which aren't held. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

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

by Thomas Stein

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

1 year, 4 months

[MM3-users] Re: Setting for archiving multi email domains?

by Duane Raymond

On Wed, 10 Mar 2021 at 15:52, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > Update: the other person on the test list has indicated they are > receiving the emails now - and that gmail may be the cause of the issue by > filtering out copies of the message I had sent. (my fairsay.com address > is gmail hosted, but another is not and is simply forwarded there). > > > > ...so perhaps the problem is solved (will do a little more testing to > verify!) > > It's Gmail. Just check the mail.log and look for status=sent > Thanks Brian - then I think it is fixed :-) Thank you Mark and Brian for your patience and persistence. I'll keep monitoring the situation as new subscribers (not sure if all) seem to also be missing the user id in the members table and I then need to run an update query to fix it - but at least I know what to look for and how to resolve it! (this last week was painful!) Cheers, Duane

4 years, 6 months

[MM3-users] Strange behaviour when SSL (https) is activated

by fr-mm3＠tourde.org

Hi, I do a fresh install of Mailman3 and Mailman3-web on Debian 11 and all seems working fine using non-ssl access. But if I activate SSL on the web server, I'm unable to login. I go to the /admin, prompted for the user/pass, and got a Firefox error page saying "Échec de la connexion sécurisée". Main django account was created with: mailman-web createsuperuser --username XXXX --email xxxx(a)xxxx.xx extract of /var/log/mailman3/web/mailman-web.log : [pid: 103142|app: 0|req: 40/40] 192.168.200.252 () {48 vars in 1039 bytes} [Mon Jan 3 11:26:32 2022] GET /accounts/login/ => generated 9321 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 429 bytes (1 switches on core 0) Mon Jan 3 11:26:40 2022 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /accounts/login/ (192.168.200.252) OSError: write error [pid: 103142|app: 0|req: 41/41] 192.168.200.252 () {54 vars in 1008 bytes} [Mon Jan 3 11:26:40 2022] POST /accounts/login/ => generated 0 bytes in 704 msecs (HTTP/1.1 302) 9 headers in 0 bytes (1 switches on core 1) All is working fine on non-ssl connection. Any hint appreciated ;)

3 years, 8 months

[MM3-users] CSS Hyperkitty ERROR

by Johan Alsina

Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. Here you can see what i see when loading hyperkitty https://freeimage.host/i/3n6kXKQ and mailman(postorius) https://freeimage.host/i/mailman.3n6kVix When i run my server with verbosity it shows like all is loading ok: https://freeimage.host/i/3n6SViG Any ideas? :/ My static files are loading from /static/CACHE/css/output.a0f71925131b.css and /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css It seems like the real error are in the /static/CACHE files, because hyperkitty is the only one who load files from this directory.. postorius uses /static/postorius and all the css files are working fine. I checked permissions for the directory, cleared cache, etc.. i dont know what to do. This is my config for staticfiles: STATIC_URL = 'static/' STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles') STATICFILES_DIRS = [ os.path.join(BASE_DIR, 'static'), '/opt/mailman/projectes/mailman3web/static/CACHE', Thank you so much in advance.

6 months

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

by Abhilash Raj

On Tue, Mar 20, 2018, at 2:47 PM, Mark Sapiro wrote: > On 03/20/2018 02:13 PM, jwhathaway(a)locklaw.com wrote: > > > > /opt/mailman/core/var/templates/site/en/list:member:generic:footer > > > > But this is not being honored by the mailman container. I have restarted all of the containers. Is there something else I need to do? > > > That's only one place the template is looked for. The search is first > list, then domain then site. > > So the search will be first in > /opt/mailman/core/var/templates/list/<list-id>/en/ followed by > /opt/mailman/core/var/templates/domains/<domain>/en/ followed by > /opt/mailman/core/var/templates/site/en/ > > and the first list:member:regular:footer or list:member:generic:footer > found is what will be used for regular deliveries and the first > list:member:digest:footer or list:member:generic:footer found is what > will be used for digest deliveries. I'd probably have to look at the code, but aren't they supposed to have either .txt or .html extensions? -- Abhilash Raj maxking(a)asynchronous.in

7 years, 5 months

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Mark Sapiro

On 6/29/20 1:38 AM, Florian Schulze wrote: > Hi! > > After upgrading to HyperKitty 1.3.x I get the following error for qcluster: > > File ".../lib/python3.7/site-packages/django_q/cluster.py", line 300, > in pusher > task = SignedPackage.loads(task[1]) > File ".../lib/python3.7/site-packages/django_q/signing.py", line 31, > in loads > serializer=PickleSerializer) > File ".../lib/python3.7/site-packages/django_q/core_signing.py", line > 38, in loads > return serializer().loads(data) > File ".../lib/python3.7/site-packages/django_q/signing.py", line 44, > in loads > return pickle.loads(data) > AttributeError: Can't get attribute 'process_task_result' on <module > 'hyperkitty.tasks' from > '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> > > How do I recover from that? It seems like there are still persisted > tasks in the qcluster queue using the old code from 1.2.x with the old > locking implementation. Have you stopped ans started qcluster since upgrading? Are you running the Django periodic jobs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

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

by Élodie BOSSIER

Le 18/02/2022 à 18:23, Mark Sapiro a écrit : > If you go to https://example.com/mailman3/domains/ (the Domains view > in Postorius) you will see at least two entries, one with Mail Host > ml.franceserv.fr and one with Mail Host ml.viticreation.fr. > > What are the Web Host entries for these? > You should have two separate site entries in the django_site table > (https://example.com/admin/sites/site/) for these domains. Ah alright, now I understand how to proceed and it's working perfectly. I need to add domains through https://ml.franceserv.fr/admin/sites/site/ and define a new site_id for each domain name. Thank you very much for your help. This is my result : https://images.franceserv.fr/images/2022/02/18/06d4eb84a0ded88d55c0296ff0c3… Now, I need to find how to set it automatic when I will add a new list. Perhaps I could do it with an an SQL command if there are no bash command ? I will check with "mailman create" and the --domain argument. Thank you again for your help.

3 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I made a change for test purpose on the mailman.cfg file and I got this: (env) [mailman@localhost etc]$ mailman restart Restarting the Mailman runners PID unreadable in: /var/lib/mailman/var/etc/var/master.pid [Errno 2] No such file or directory: '/var/lib/mailman/var/etc/var/master.pid' Is the master even running? How do I solve this? El mar., 1 ago. 2017 a las 13:02, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 10:15 AM, Rafael Mora wrote: > > Hello, > > > > I got postfix installed and I can use the command mail to send emails. > The > > thing is that mailman can't send the confimation mail yet, where should I > > look for the error?? > > > Look in Mailman's logs and Postfix's 'maillog'. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 4/8/19 4:44 AM, Henrik Rasmussen wrote: > I finally received the right mail from the user. I am sorry for the delay. > > The mail from the list does actually not contain any X-Mailman-Rule-Misses: nor X-Mailman-Rule-Hits: This is quite strange. There are no 'X-Mailman' headers which might be exchange removing all 'X-' headers other than its own, but while there are some 'List-' headers, there is no 'List-Id:' header which Mailman always adds. Can you try to get an example message from the list that was sent to a non-outlook/exchange user. Perhaps you could subscribe a gmail or other non-microsoft managed address to the list. I note the MX for your email domain is ku-dk.mail.protection.outlook.com, so that probably won't do. However, one thing to check is the list's Header filters settings. Is there a filter there that could match the owner's email with action accept? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/8/22 8:28 AM, kisner(a)live.com wrote: > > I tried to follow that guide ( https://docs.mailman3.org/en/latest/install/virtualenv.html ), but I couldn't get it to work. I'd have to try it again to see where it broke. One thing that I got past was I had to change: > > (venv)$ pip install wheel mailman psycopg2-binary<2.9 > > to > > (venv)$ pip install wheel mailman psycopg2-binary==2.8.6 > > and that got me past that part, I don't understand why that would make a difference since the latest psycopg2-binary<2.9 is 2.8.6 > but hyperkitty/mailman-web pip install has components that failed to install. I'm not sure why, someone smarter than me could probably have figured it out, but as written it wasn't working for me. If you do try again, post the specific issues/error messages and we will try to help. -- 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] Converting non-members to members

by Alan So

Postorius is not currently exposing non-members management. Our Mailman 2 users are currently using accept_these_nonmembers, hold_these_nonmembers and reject_these_nonmembers. We know that mailman import21 will change these to nonmembers entries in Mailman 3. Since list owners will still want to manage them, we tend to move all of them to members and turn off delivery status for them. However, we met some difficulties when we try to develop using mailman client. 1) If those non-members addresses already exist as members, we will encounter error when we subscribe for them: urllib.error.HTTPError: HTTP Error 409: b'Member already subscribed' 2) We cannot change the moderation_action: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: moderation_action' 3) We cannot change the preference: urllib.error.HTTPError: HTTP Error 400: b'Cannot convert parameters: delivery_status' Are there any better ways to enable the list owners to manage those previously configured nonmembers' addresses through the web? Otherwise, we probably need to have some manual effort to overcome the above three issues. We know that we can always do the above manually but we got a lot of lists to migrate to Mailman 3.

6 years, 8 months

[MM3-users] Re: Not able to start mailman server

by Mark Sapiro

On 8/4/21 2:24 PM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to start the mailman server on a mac according to the instructions given on the website as shown - What web site? A URL to the instructions you followed would help. > $(py3) git clone git@gitlab.com:mailman/mailman.git > $(py3) cd mailman > $(py3) python setup.py develop Rather than 'python setup.py develop', do 'pip install -e ./' > $(py3) mailman start > $(py3) cd .. > > But I run into the following problem - > > Starting Mailman's master runner > Generating MTA alias maps > /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > > Can anyone help me out with this? There should be a `master` in the same bin/ directory as `mailman` which is probably not '/usr/local/opt/python(a)3.9/bin/' What does `mailman info` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

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

by Abhilash Raj

On Fri, Mar 30, 2018, at 12:00 PM, Chris McMacken wrote: > Thanks for the prompt response. > > Why does the application store messages on the local disk? It is how our queuing system is built, every queue is stored on disk and messages in intermediate states like when being processed or decorated inside Mailman Core as stored on disk. *Most* of these isn't the problem, since the emails are sent out pretty fast, it's the held messages waiting for approval or broken messages in the shunt queue that would be lost and is what I mean by "State" mostly. AFAIK API being served by different instances will affect what and how many held messages are reported. > I'm guessing > it's for performance reasons but wanted to ask. Do you have any plans to > add database storage for these at some point in the future? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

7 years, 5 months

[MM3-users] Dmarc settings and

by paul＠arenson.org

In a long thread I asked this but have not gotten a clear enough explanation. Presumably, to insure fewer problems with users of Yahoo etc,, there seem to be two settings: 1) Alter messages 2) Dmarc mitigations I don’t understand how my choice in one affect the other, if they do even, Two experts have tried to help, but I think I need a little hand holding. I understand there is no consumer ready manual and all I have found us this: https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/dmarc-mi… My settings; REPLY GOES TO LIST (alter messages)--current settings REPLACE FROM: with list (DMARC mitigations) -> current settings DMARCH Mitigation YES OR NO (DMARC mitigations)--> currently NO I was told that Dmarc mitigations YES might prevent people from not getting mail How about Replace from with list? How about reply goes to list? In other words, what is the relationship between these two different menu items and the effect of the settings in one on the settings of the other? Can anyone help a confused would be happy user? Thanks? If so, what about the Alter Messages settings:

6 years

[MM3-users] mailman.log file owned by 'list' user

by Mike Wertheim

I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 that was done by someone else. Mailman is running as a non-privileged (non-root) user called 'xyz'. On the day that Mailman was installed, that non-privileged 'xyz' user was able to execute mailman commands successfully to create, view and modify lists. A couple of days later, when the 'xyz' user tried running those same mailman commands, they failed with this error: PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log When I did a 'ps' command, I saw that all of the mailman processes are running as user 'xyz'. No processes were running as the user 'list'. It seems that some process is rotating the mailman.log file at midnight, and the newly-created mailman.log is being owned by user 'list'. Can anyone explain why this is happening, and how to fix it?

2 years, 8 months

[MM3-users] Re: From address of subscription notifications

by worik

On 27/02/19 11:54 AM, Mark Sapiro wrote: > On 2/26/19 2:11 PM, worik wrote: >> When I subscribe some body to to a list I on I get a notification that >> says it comes from changeme(a)example.com >> >> As far as I can tell no subscribers are getting mail with that, so this >> is not a crises. But it is untidy and I cannot find where to change it. >> >> SERVE_FROM_DOMAIN is set in the mailman-web/environment section of >> docker-compose.yaml (I am using the docker distribution...) > You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > > There is no `mailman/config/schema.cfg` on my system. Should I raise a issue over at the docker-mailman github? I have: /opt/mailman/core/mailman-extra.cfg /opt/mailman/core/var/etc/mailman.cfg Should I change it in the second one? -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 6 months

[MM3-users] Re: Uncaught runner exception

by Stephen J. Turnbull

Wolfgang Bock via Mailman-users writes: > I tested port 25 with swaks ->mail to user on server: localhost > port 25 -> everything fine What is "swaks"? > Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server > localhost on port 25 Is it possible that Postfix is configured for TLS connections only? If so, it is probably listening on port 465 (the "submissions" port, AKA ssmtp and smtps) or (less likely) 587 (the "submission" port -- no trailing "s"). Mailman needs to be configured correctly for this. See https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht… It's barely possible that Postfix is listening on port 25 but insists on TLS. But that's very unusual, and I think that would produce a SMTP error such as "Need STARTTLS" or "Need SASL" (which happen *after* the TCP connection is established) instead of "Cannot connect" (which suggests a TCP error before a connection is completed). > I have no idea what to do for solving my problems. That's when we're most of service. At least, I hope so! :-) Steve

5 years, 5 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/27/20 11:08 PM, Shashikanth Komandoor wrote: > Thank you Mark for your response. > > All the mentioned versions of all the components are taken from my > currently running system only in which I am facing the issue. Did you run $ cd mailmanclient $ python setup.py develop as it says at <https://docs.mailman3.org/en/latest/devsetup.html> I do not understand exactly how the various components are installed in your installation, so I can't tell you what is wrong, but the version of mailmanclient that gives you the AttributeError: 'MailingList' object has no attribute 'get_requests_count' is not the one whose latest commit is ### Mailmanclient Version ### commit aaa529808e2d61899f90509da4ea802a70d2c8ff Merge: ff39dd8 8670751 Author: Abhilash Raj <maxking(a)asynchronous.in maxking(a)asynchronous.in> Date: Thu Oct 15 01:09:32 2020 +0000 Merge branch 'fix-ci' into 'master'* Use GHCR for the CI image* See merge request mailman/mailmanclient!130* because that one won't have this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Stephen J. Turnbull

Prasanth Nair writes: > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec can't > encode character '\ufffd' in position 252: ordinal not in range(128).* This is the Unicode REPLACEMENT CHARACTER, which means that something along the line, possibly Mailman, could not decode some bytes, and replaced them with that character. The message about "ASCII" codec usually means that this occurred in the header of the email, which is typical of spam. The message ID was generated by Mailman not by the originating system, which is also indicative of spam. If it is spam, you can identify the message and delete it from the archive. If it's not, you will need to find the text that is being replaced and delete it or replace it with ASCII yourself. > I ran the check_hk_import script before migrating and it was not > giving any error. In order to catch this kind of error, the check script would have to pretty much do the import but throw it away.

3 years, 11 months

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

by Matthew Alberti

I had a very similar experience. I don't mean to knock the dev team; Mailman3 is an awesome tool that really meets a need. It is really much much more than a 'tool.' A very comprehensive software suite. For me, I ended up using the docker option on Ubuntu 20.04. My advice is to give up on the idea of using OS package managers. They just aren't current enough (certainly for Ubuntu LTS), or updated frequently enough, for the current development of Mailman3. Nothing but problems for me on Ubuntu, and Debian is about the same. Pypi, or installation in a virtualized environment, was equally challenging. I strongly recommend the docker installation method. It is not quite turnkey, but the documentation is close enough where it might 'just work' in your environment. I used MariaDB, and that introduced some challenges. If you are using postgre, postfix, and nginx, you are pretty close to a very easy installation. This list is very supportive, with very frequent responses from the core dev team. And there are guys like me who really struggled to get to a production instance. Please let us all know what isn't working in the docker approach, and we will try to help I'm sure. - Matt Alberti ⁣Get BlueMail for Android On Dec 31, 2020, 8:15 PM, at 8:15 PM, ieso(a)johnwillson.com wrote: >So I've been trying for the last two weeks to get a new mailman3 server >running on a virtualized server (any server), and I'm turning to this >list after having failed many times and running out of holiday time. > >I started trying a non-docker installation on Ubuntu 18.04 >(https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) >, which got me the closest. Except I had a problem with inbound email >only being triggered when it came from certain accounts. But that >clearly wasn't good enough for production, so after many attempts to >figure out where it was failing, I decided to turn to docker as a >solution that should be cleaner. > >A few attempts at doing a docker installation on digitalocean.com >failed, which I realized might be due to it not routing private IP >addresses, so I moved to AWS after checking that their VPC policy would >fit mailman's docker requirements. I found a great but slightly >outdated guide on how to do this >(https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) >By this point I knew enough to correct a number of places where the >environment had changed since the procedure was written, but postorius >still failed at the curl test. > >The challenge for me has been the difficulty to know how to >troubleshoot the different different systems and network infrastructure >that are used to keep mailman3 humming. I've tried about 7 different >installation walkthroughs (there are no recent ones on Youtube by the >way, in case anyone wants to seize that opportunity!), and the good >guides provide ways to check each stage to try to help you a bit on >that front. > >Nonetheless, I feel stuck and thought I'd ask the simple question... >for a completely basic, barebones new installation, what's the easiest >way to get a mailman3 installation up-and running? (e.g. Which server >provider? Which operating system and version? Docker or otherwise?) > >Any pointers highly appreciated. Google Groups is clearly on its way >out, as it no longer allows for people to easily join groups by sending >an email or clicking a link, so that should be a big opportunity for >mailman3 to step up and help give those mailing list migrants a new >home... which is what we're looking for. We're just not quite as smart >as you guys. ;-) >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I put this config in mailman.cfg: To configure Core to use Postfix, add the following configuration to your mailman.cfg configuration, be sure to replace mail.example.com with your email domain: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 is this correct?? El lun., 24 jul. 2017 a las 17:47, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 03:31 PM, Rafael Mora wrote: > > I got this on maillog: > > > > > > > > [root@localhost log]# cat maillog > > > There's nothing in that log that shows any attempts by anything to > connect to Postfix. You have to look at logs from the processes you > think are trying to send mail and see what they're doing. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 1 month

[MM3-users] Re: Selective mailing

by Abhilash Raj

On Wed, Feb 27, 2019, at 8:43 PM, chucka(a)blackforest-co.com wrote: > I like the controls that MM uses. What I have and need: a member > database [name, address, email, date dues paid, etc]. So I can do this > 2 ways: 1) select name, email from members where xyz > file. Login to > MM empty member list - which is kind of painful then load file and send > the email. Then repeat for NOT xyz You could use the API to create mailing lists on-demand with the list of members, which you can get by executing SQL queries in whatever way you want. Then you can send the emails and re-create the mailing lists everytime your list of members change (monthly?). > or > 2) roll my own php script where I select from and if (xyz) Aemail else > Bemail > > Problem with #2 is I lose the discussion part. <sigh> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 6 months

[MM3-users] Re: howto reallow a banned email ?

by Nicolas Pettiaux

much thanks. I use mailman 2 interface (and will switch soon to 3) i'll look asap. --- Nicolas Pettiaux - PhD - nicolas(a){educode,pettiaux}.be - Président de Educode asbl Informer, former et susciter la réflexion des acteurs du monde de l'enseignement face aux évolutions d'un monde numérique - http://2019.educode.be & http://2018.educode.be Le 2019-06-19 6:33, Mark Sapiro a écrit : > On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: >> >> By mistake a user has been banned to post to mailman list. How can I >> allow him not only to post but also to become a member of a list ? >> >> I have not found any info on the web, or I have been unable to search >> correctly. > > > Do you have the Postorius web UI in your installation? If so go to the > list's Ban List and remove the unwanted entry. > > Or is this perhaps a Mailman 2 question? If so you'll find the ban_list > in the web admin UI at Privacy options... -> Subscription rules.

6 years, 2 months

[MM3-users] Re: How to remove a nonmember from a list

by Abhilash Raj

On Fri, Apr 10, 2020, at 3:45 AM, skenny(a)scss.tcd.ie wrote: > Out put from my python program is not dissimilar - I am seeing the > same WORKER TIMEOUT message: > > [10/Apr/2020:10:42:54 +0000] "GET > /3.0/lists/scss-sysadmins(a)lists.scss.tcd.ie HTTP/1.1" 200 421 "-" "GNU > Mailman REST client v3.3.0" > [10/Apr/2020:10:42:55 +0000] "GET > /3.0/lists/scss-sysadmins(a)lists.scss.tcd.ie/roster/member HTTP/1.1" 200 > 3766 "-" "GNU Mailman REST client v3.3.0" This seems like is timing out getting list of members. Without pagination, I do expect it to time out if the list is large. I think `.members` by default doesn't use pagination. > [2020-04-10 10:43:25 +0000] [30] [CRITICAL] WORKER TIMEOUT (pid:38) > [2020-04-10 10:43:25 +0000] [38] [INFO] Worker exiting (pid: 38) > [2020-04-10 10:43:26 +0000] [45] [INFO] Booting worker with pid: 45 > > Stephen > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 5 months

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

by Odhiambo Washington

On Sat, May 15, 2021 at 1:08 AM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > On 14/5/21 23:52, Odhiambo Washington wrote: > >> Which OS are you using? > > FreeBSD. > > > > > As Mark pointed, you probably have installed the textproc/sassc port (or > package). I'ts an equivalent for sass. Do the config as advised. > > I have mailman3 installed and running smoothly in a pair of 12.2 RELEASE > FBSD servers. > > There is a thread about this installations that can help: > https://forums.freebsd.org/threads/mailman-3.61050/post-488128 > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I will look into this. I know FreeBSD has a mailam3 port, but I have mailman2 in production and the port installs to /usr/local/mailman so I have to be careful - install mailman3 in /opt, then plan on hosing mailan2 and moving mailman3 to it's place after migration. It's not simple. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 4 months

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

by Odhiambo Washington

On Wed, Feb 1, 2023 at 2:03 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Odhiambo Washington writes: > > > All the above noted, and well-received. > > I only decided to experiment with this particular documentation because > it > > is the *OFFICIAL* one. > > Yup, and thank you for that! > > But not everyone has the time or the skills for it, so I wanted to say > in a public place that questions really are welcome (and please > don't be deterred if occasionally we seem exasperated by somebody's > questions, that happens but we get over it, it's not your fault :-). > > Steve > > Hello Steve, That is quite well understood. I am all too happy to be asking questions and yes, I know you and Mark do give us a lot of your time and we are grateful. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

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

by Odhiambo Washington

On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < as2020+github(a)fam.tuwien.ac.at> wrote: > > On Fri, 7 Apr 2023, at 12:43, Dave Hall via Mailman-users wrote: > > > On Fri, Apr 7, 2023 at 12:29 PM Odhiambo Washington <odhiambo(a)gmail.com> > > wrote: > >> On Fri, Apr 7, 2023 at 7:14 PM Dave Hall via Mailman-users < > >> mailman-users(a)mailman3.org> wrote: > > >> It's actually not that difficult to migrate from the Debian > >> packages to the virtualenv setup. > > It's not an option for me today. > > I feel you. > > I am running MM2 und 3 in parallel without problems, I do have a > special MTA setup though (Sendmail). Can't speak for Postfix etc.. > Your setup can handle list1(a)domain1.name via MM2 and MM3, simultaneously, right? :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 5 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Thank you very much for your response. I understood myself as quite ignorant even to find out the versions of each of the component. But my "mailman info" output looks like the below: *(venv3) [root@dlist-lsmgr mailman]# mailman info* *GNU Mailman 3.3.2rc2 (Tom Sawyer)* *Python 3.6.8 (default, Aug 10 2019, 06:54:07)* *[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]* *config file: /var/lib/mailman/mailman/var/etc/mailman.cfg* *db url: postgres://<username>:<password>@127.0.0.1/mailman* *devmode: DISABLED* *REST root url: http://localhost:8001/3.1/ <http://localhost:8001/3.1/>* *REST credentials: restadmin:restpass* *(venv3) [root@dlist-lsmgr mailman]# pwd* */var/lib/mailman/mailman* How to find out the versions of the each and every component of the mailman 3 like mailman core, mailmancilent, postorius, hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, after installation? If I am running an old mailmanclient or older version of any other mailman component, please suggest how to upgrade either one or multiple components based on the requirement. Is there any link that would help me to upgrade ? I have used the link https://docs.mailman3.org/en/latest/devsetup.html to install the mailman 3 components. I expected that the procedure followed in this link would install the latest versions of the mailman 3 components. Please correct me if I am wrong. Is there any latest version compatibility table ? Also please suggest me an URL that would install the latest versions of mailman 3 components and allow me to do customizations related to our domain. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Mon, Oct 26, 2020 at 4:16 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > I am currently running Mailman 3 with version 3.3.2rc2 and > in > > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > > with default values. As of now, we don't have any lists and just > installed > > software components only. > > > > After the installation and configuration, I have tried > > creating the domains and lists. I was successful in creating them but > when > > I tried to login and browse the lists using LDAP authentication, I am > > getting the "Mailman REST API not available. Restart Mailman core". > > > > I see the below trace in the mailmansuite.log. > > > > > *Traceback (most recent call last): File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 119, in __getattr__ return self._get(name) File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count > ... > > > > I don't see any error messages in the mailman.log. And I > > also executed a few curl commands in getting the details of the lists > > created and list info which I got their results successfully. > > > > Could you please guide where exactly I am missing or do I > > need to make any changes in my customizations ? > > > I think the issue is your mailmanclient is too old. The version of > Postorius you are running requires mailmanclient >3.3.1 which is only > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > What version of Postorius is this? It appears to be >1.3.3. If you > install Postorius from unreleased code on GitLab, you have to install > all of mailman, mailmanclient and django-mailman3 as well. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 10 months

[MM3-users] spam filtering (was: Re: list of subscribers)

by Peter Münster

On Sun, Feb 04 2018, Mark Sapiro wrote: > This would seem to be specific to your use case. I think in general what > we would want to display is the display_name from the list's member record. Ok, I see. Now I know, how to generate such list (email + full name) as site administrator, so it's ok for me. > We tried to send your copy of your post to you, but your MTA called it spam. > > Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: > to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, > delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host > mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of > DATA command)) IMO, spam filtering should be done at user level, every user should be free to filter what he likes, not the MTA. Perhaps I should do it like you, and manage my own email relay host? I've tried to subscribe with an address at orange.fr but it does not seem to work, probably the same problem as with free.fr... -- Peter

7 years, 7 months

[MM3-users] Is there a "global" max_message_size?

by skenny＠scss.tcd.ie

I'm running Mailman under Docker (maxking). I've a test list with a max_message_size set to 0 (unlimited). I know it's not what anyone should be doing in production, but I still want to test this. I've sent a series of messages with increasingly larger attachments to the list. Going up in 5MB increments, I find that while a message with a 15MB attachement gets through to the list members, a 20MB one doesn't. The interesting thing is the message in the mail logs: Jun 19 11:44:50 venus postfix/lmtp[17630]: C0C7928564: to=<mj(a)lists.scss.tcd.ie>, relay=172.19.199.2[172.19.199.2]:8024, delay=109, delays=2.2/0.04/0.01/107, dsn=5.0.0, status=bounced (host 172.19.199.2[172.19.199.2] said: 552 Error: Too much mail data (in reply to end of DATA command)) So 172.19.199.2 is complaining about "Too much mail data". That's the IP address of the mailman-core container. I'm wondering why this is happening, and where the decision is being made, as it seems at odds with the fact that the mailing list has no limit on message size. Would be grateful for any insights, many thanks. Stephen Kenny

5 years, 2 months

[MM3-users] Re: Set Postorius interface locale

by Mark Sapiro

On 3/2/21 7:55 AM, Duane Raymond wrote: > > The problems I've encountered so far are: > 1) Where do I set the local of the Postorius interface? > 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Multiple things are required. In order to be able to set the list's preferred_language via Postorius, the language must be included in the LANGUAGES definition in postorius/utils.py. However, you can set the list's preferred_language in Mailman core via `REST` or `mailman shell` or direct update of the database. Then there must be message catalogs for the language in postorius/locale, django_mailman3/locale and hyperkitty/locale and these must be compiled by the Django management command `compilemessages`. -- 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: How to delete user completely?

by William Oliver

On Fri, 2022-01-21 at 16:50 -0800, Mark Sapiro wrote: > On 1/21/22 4:32 PM, William Oliver wrote: > > I have installed mailman3 and it's up and running great. However, > > I > > noticed that, during a mass subscribe, I mis-typed an address, e.g. > > name(a)domain.ned rather than name(a)domain.net. I found how to > > unsubscribe > > the bad address, but I haven't found a "delete" option under Users > > or > > anywhere else. How to I purge a user from the users list? > > You need to do it via REST or `mailman shell`. In mailman shell, > ``` > >>> um = getUtility(IUserManager) > >>> usr = um.get_user('user(a)example.com') > >>> um.delete_user(usr) > >>> commit() > ``` > > > As a related question, in docs.mailman.org, I can find a list > > member's > > manual, but I can't seem to find an admin manual. Is there one? > > > No, not per se. > Thanks! billo

3 years, 7 months

[MM3-users] Re: Docker or virtualenv?

by Johannes Rohr

Am 31.12.22 um 12:29 schrieb Andrew Hodgson: > I actually moved from Docker to Virtualenv on my machine as I wanted to use the same larger VM to run a Cloudron instance which takes over Docker. Overall I have been more happier with the virtualenv approach as it allows me to customise the install more easier. I did look at running Mailman using Azure Container instances. The main thing here is we need to get the MTA integrated, and the MTA needs to send out emails from a static IP address with reverse DNS etc setup. This isn't easy to do on anything other than a VM. Sorry, can you elaborate? Are you talking about an MTA that runs inside a VM? Docker actually isn't a VM, so I am a bit confused. Johannes > > Thanks. > Andrew. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to johannes(a)rohr.org

2 years, 8 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Mark Sapiro

I have now seen a similar instance on one of my servers. I was able to get the raw garbled response from the user. I have asked to get the raw message that was sent, but unfortunately, I haven't gotten it and I suspect I won't. I think it was an attempted post sent by mistake to the LIST-confirm address. I have tried, so far without success, to duplicate this, but I will keep at it. The raw message is attached. This one is worse than the one in the OP in that the Content-Transfer-Encoding is base64, but the content is unreadable in the raw message. It is clearly not a valid base64 encoding. I'm guessing that the original message looked similar to the one in the OP, but Microsoft Exchange garbled it by doing some attempt at base64 decoding the unencoded plain text and placing that result in the message body -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: "From address" for list moderation notification

by Mark Sapiro

On 12/29/23 10:58 AM, ronn.ramirez(a)pge.com wrote: > Hi Mailman Group, > > I noticed that the from address for list moderation notifications are coming from a certain user address. > May you please help me figure out where to change this? > > In this example, I would like to change the From address "listadmin(a)domain.com" > > ================================================================ > -----Original Message----- > From: Admin <listadmin(a)domain.com> > Sent: Thursday, December 28, 2023 12:00 AM > To: dummy-list <dummy-list(a)domainx.com> > Subject: The dummy-list(a)domainx.com list has 2 moderation requests waiting. > > The dummy-list(a)domainx.com list has 2 moderation requests waiting. > ... I do not understand "certain user address". I also don't undersatnd the above example. These notices are sent both From: and To: the list owner address. In the above example it would be From: dummy-list-owner(a)domainx.com To: dummy-list-owner(a)domainx.com Is this not what you see? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Bounce processing

by Mark Ziranski

Thank you. when can we expect the release of Mailman 3.2? Gesendet: Freitag, 11. August 2017 um 17:06 Uhr Von: "Barry Warsaw" <barry(a)list.org> An: "Mailman 3 users (mailman-users(a)mailman3.org)" <mailman-users(a)mailman3.org> Betreff: [MM3-users] Re: Bounce processing On Aug 11, 2017, at 06:02, Mark Ziranski <Wal3(a)gmx.net> wrote: > I read that mailman3 supports 'bounce processing' but I do not know how > to configure it. I want to delete members automatically from a mailing > list if the delivery has failed after a certain time of attempts > because his mailbox has been removed or his mail server has been > shutdown etc. There is also the case that an users mailbox is full > (mailbox limit exceeded). Is possible to deal with this case too? Bounce processing is currently incomplete in Mailman 3.1. We will fix that in Mailman 3.2. (I was going to include a link to the issue, but GL is giving me a 500 error right now.) -Barry _______________________________________________ Mailman-users mailing list mailman-users(a)mailman3.org [1]https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org / References 1. https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

8 years

[MM3-users] Re: Clean-up of non-members

by Odhiambo Washington

On Mon, Dec 23, 2024 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 02:16, Odhiambo Washington via Mailman-users wrote: > > On Mon, Dec 23, 2024 at 1:37 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Isn't this just `mailman members --role nonmember LISTSPEC`? > >> > > > > I didn't know that the option was right in front of me, but it seems > there > > is a problem: > > GNU Mailman 3.3.10 (Tom Sawyer), Mailman Core API Version 3.1 > ... ^^^^^^^^^^^^^^^^^^^^^^^^ > > AttributeError: 'NoneType' object has no attribute 'display_name' > > > I saw that too. Reported > https://gitlab.com/mailman/mailman/-/issues/1187 and fixed > https://gitlab.com/mailman/mailman/-/merge_requests/1297 It isn't clear to me what I should do to mitigate the error. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

8 months, 3 weeks

[MM3-users] migration plan and auto responder

by Mohsen Masoudfar

Hi, I am writing this in the hope to get some good advises for migration lists from Mailman2 to Mailman3. Thanks a lot in advance. Here is the requirements: * During the migration the old system shouldn't process the emails for the list under migration in the normal way. It should send an email, and only one to the member who sent the original email to the list saying the list is under migration. I know I could do this by auto responder, but the original email would be processed and sent to all members, which I want to block . * After migration the old system should send, per auto responder again, an email to the member who sent to the list, mentioning the new address (the domain is a new one, the list name the same), but again not sending the original email to the list members. * No hackers, robots, spammers should get the new list address. The lists are all hidden. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

5 years, 2 months

[MM3-users] Re: Shunt Error Mail?

by Pete Ashdown

On 3/2/21 4:09 PM, Mark Sapiro wrote: > On 3/2/21 2:52 PM, Pete Ashdown wrote: >> I have a number of list managers with subscribers who are confused as to >> why their messages are silently disappearing. I've read the archives on >> how to decipher why a message was shunted, but this is not workable at >> scale. Is sending an error email back to the sender a consideration? > Why are messages being shunted? Each shunted message has thrown some > kind of uncaught exception which is logged with a traceback in Mailman's > mailman.log. > > These should be due to bugs that should get fixed or possibly malformed > messages which are almost always spam. > > In short, under normal circumstances messages should not be shunted at > all and when they are it is something the site admins need to address. > It is normally not something the sender of the message can do anything > about. This is good to know. I was concerned that shunting could happen due to HTML or message content (ie: not size).

4 years, 6 months

[MM3-users] Delayed password requests & migrating users from mm2

by Duane Raymond

Hi again, With my new mm3 instance, password reset email to members are being received many hours late or not at all. They seem to be sent fine and when I trigger one to one of my addresses, it works instantly. But many users report getting it many hours later or not at all (despite looking in spam and bulk folders). Anyone else experience this password reset mail delay/vanishing and/or have any suggestions for diagnosing it and resolving it? The main reason this is problematic is that in migrating lists from mm2, I've set a 'fake' password for them in the mm3 db and instructed members to reset their password to set a new one so they can access the list and update their subscription and/or subscribe to other lists (which they can also do without an account of course - but then lose the ability to use the web interface and access archives). So if, as an alternative, there is another way to get list members to access their account then I'm open to it. Cheers, Duane

4 years, 6 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Torsten R.

Mark Sapiro wrote: > The issue is not related to message content. > One possibility is that there is an incompatibility between > mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause > this. What are your versions? Understood, just wanted to mention that as I read it in another thread about the 401. Hyperkitty is 1.3.4 and mailman-hyperkitty is 1.2.0 > What is your setting in mailman-hyperkitty.cfg for base_url: base_url is set to https://www.fqdn.tld/mailman/hyperkitty > if you append api/ to that and do something like > curl base_url/api/ > it should return a page of documentation of the API. If that is the > case, the issue is almost certainly communicating the api key between > mailman-hyperkitty and HyperKitty I get some information back when appending /api/ to that URL mentioned above about REST API and some formats and endpoints. So, from your words it looks like there is some issue in the communication between mailman-hyperkitty and HyperKitty. Is there some place I could/should start looking or some log I should be examining (maybe some loglevel to be increased as well)?

3 years, 5 months

Search results for query "dO"