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

[MM3-users] Re: multiple sites on a mailman3 server question

by William Oliver

On Wed, 2021-12-29 at 09:21 -0800, Mark Sapiro wrote: > On 12/29/21 8:48 AM, William Oliver wrote: > > > > What I'm trying to figure out is where uwsgi yanks control from > > nginx > > and does the rewriting. Pulling that proxypass stuff out will stop > > mailman3 from coming up, and adding it allows mailman3 to show its > > interface, but the address gets referred regardless. > > > > Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow > > tell > > nginx not to push it to port 8000. But I don't see where nginx is > > getting told to go to 8000 in the www.domain.com section. > > > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you have > ``` > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > ``` > in your nginx config and everything goes to uwsgi. What you want is > to > put those proxy directives in only the mailman locations as at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > and then configure your document root so other locations are served > from > there. >

3 years, 11 months

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

by Franklin Weng

Hi Mark, Mark Sapiro 於 2023/7/21 12:01 寫道: > On 7/20/23 20:42, Franklin Weng wrote: >> >> Thank you. When I set it in my settings_local.py, I clicked register >> and got an error: >> >> ModuleNotFoundError at/accounts/signup/ >> No module named 'django_mailman3.views.user_adapter' >> >> (In the document the path is /etc/mailman3/settings.py but I >> installed it with Debian packages so I guess the path is somewhat >> different, and I thought setting in setting_local.py should work >> too. It seems work since it gave me the error above.) >> >> Do I have to install something else? Or disable some other options? > > > What is the version of django_mailman3 in your Debian package? As it > says in the FAQ article, "You would need django-mailman3 >= 1.3.6 for > these settings to work." > Debian Bullseye goes with 1.3.5, and Debian Bookworm goes with 1.3.9 but as I have said in another thread it has problems in django admin. So I downloaded the 1.3.9 source code, extracted it, and copied django-mailman3/views/user_adapter.py to /usr/lib/python3/dist-packages/django_mailman3/views. It worked! For a record here. Thanks for your help. Thanks, Franklin

2 years, 4 months

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

by Roland Giesler

On 2024/07/30 22:39, Mark Sapiro wrote: > It appears you have a situation where the MX for the Mailman domains > is not the Mailman server. You need to configure the MTA on > box2.gtahardware.co.za to relay Mailman's mail to the mailman server. > You can to this by configuring that MTA to use transport_maps, etc as > if it were the Mailman server. In order to get Mailman's generated > files on the other server, you need to create a process to do that. > When Mailman makes changes by adding or deleting lists or when it is > started, it updates the postfix_lmtp and postfix_domains files and > calls a command (normally postmap) to update the corresponding .db > files. The command can be set by setting `postmap_command` in the > `[postfix]` section in mailman.cfg. I'm not able to find any documentation about `postmap_command`, not even in the schema.cfg. If I have to provide method to update the postfix_lmtp and postfix_domains on another server, then it would have to something like sftp? mailman changes the files on the mailman server (in a location I set) and then postmap_command copies those files to the destination on the MTA server. Is that in principle what needs to be done? thanks again! Roland

1 year, 4 months

[MM3-users] Re: Problems with web interface after upgrade

by Victoriano Giralt

De: Mark Sapiro <mark(a)msapiro.net> > On 2/9/21 3:26 PM, Victoriano Giralt wrote: >> >> It's CentOS7, but sassc was already installed and has -t as short for --style. > > You wrote > >> ModuleNotFoundError: No module named 'sassc -t compressed {infile} {outfile}' > > It should be looking for just sassc, not 'sassc -t compressed {infile} > {outfile}'. Whats in your settings for COMPRESS_PRECOMPILERS. I'll check this anyhow. > That may not be the issue. You also wrote > >> compressor.exceptions.FilterError: Error: It's not clear which file to >> import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. >> Candidates: >> ../libs/bootstrap/stylesheets/_bootstrap.scss >> ../libs/bootstrap/stylesheets/bootstrap.scss >> Please delete or rename all but one of these files. >> on line 4 of static/hyperkitty/sass/hyperkitty.scss > > You need to remove the older of > > hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss > > and > > hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss > > That may be the whole issue. And it was! You clearly have telepathy, as I was testing this while you were writing, and your message arrived when I had just clicked send on my "SOLVED" message :-D :-D -- Victoriano Giralt Sent from mobile device

4 years, 10 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

Finally got a scenario where there was contents queued up for digest delivery and not enough traffic to kick off size based digest volumes. Running "/usr/local/bin/mailman digests --periodic --verbose" ran through all the lists and kicked out digests successfully. So something is making this work when I run it as the lists user by hand, but fail when I run it from cron as the lists user. Clearly this is on my end, I'll report back if I find anything useful or interesting. On 6/13/2023 2:14 PM, Mark Sapiro wrote: > On 6/13/23 10:58, Joel Lord wrote: >> I ran the "/usr/local/bin/mailman digests --periodic" again, sadly >> without the --verbose, and it kicked out the digests as it ought to >> have the first time. Now I have to wait for some list traffic to come >> in to "recharge" the digests so I have something to test with again. > > Even with the --verbose option, it wouldn't have helped much because it > worked. What we would really like to see is the output with the > --verbose option when it fails. > > It is a mystery to me why it would sometimes fail and sometimes not with > the same digest.mmdf file. > -- Joel Lord

2 years, 5 months

[MM3-users] Re: MM3 in virtualenv - FreeBSD-11

by Odhiambo Washington

I am keeping all of my steps in a text file. If I end up with a functional install, then I believe FreeBSD users will be able to install MM3 using virtualenv. I am banking on the help of the experts here to achieve that and document it. So far, I don't know anyone who is using FreeBSD who has managed to install and run MM3. This will be the first time anyone has ever done it. I therefore beg all of you to accommodate my stupidity. I'm 50 in April so it's not a mean feat 😂 😂 On Fri, Jan 11, 2019, 23:10 Mark Sapiro <mark(a)msapiro.net wrote: > On 1/11/19 6:51 AM, Odhiambo Washington wrote: > > > > Now that I look at it, I think you should clarify that if one is not > > interested in using PostgreSQL (which is what `pip install > psycopg2-binary` > > is for), > > then there should be some different binary they need to install, no? And > > which one is it? > > > I have added a note to the comment at > https://wiki.list.org/DOC/Mailman%203%20installation%20experience which > says: > > """Also, please note the first paragraph of the introduction. This is > documentation of my decisions and experiences. It is not a how-to and > does not replace the documentation at http://docs.list.org/""" > > In particular, documentation of the requirements for different databases > is at > <https://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html>. > > > > Under your "*Recommended Configuration*", I have followed each step, > > getting the files and editing them to suite my needs, until I got to > where > > you refer to: > > /opt/mailman/mm/settings.py (copy of the mailman-suite settings.py file > but > > with DEBUG = False) > > I tried to get this file using `git clone > > https://gitlab.com/mailman/mailman_suite.git` > <https://gitlab.com/mailman/mailman_suite.git> and realized that > > authentication is required in order to get it. > > > Because you should be getting > <https://gitlab.com/mailman/mailman-suite.git> (hyphen, not underscore) > which works without authentication. > > Or you could just go to > < > https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… > > > and copy it from there. > > > > What is the reason you did not include a copy like for the rest?? > > > Because it's available on GitLab. > > > > I have created the executables - all of them. > > I have created the templates and did `find . -type f -exec sed -i.BAK 's/ > > mailman3.org/mydomain.name/g' {} \;` > > Maybe you should state explicitly that once one gets these templates, > they > > need to change the url to match theirs. You said it, but it doesn't come > out > > forcefully :0 > > > I added "Of course, if you use these you need to edit the URLs for your > site." > > > > In your "MTA" section, I suppose you need to be a little more generic as > > well and accommodate Exim users. > > First I suggest you clearly state that one needs to edit /opt/mailman/mm/ > > mailman.cf to ensure that the values under [mta] match what is required. > > Maybe there is a different file to edit for MTA settings??? > > > Again, I'm documenting MY experience, not trying to replace the official > documentation. I refer to > < > https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#postfix > > > because I use Postfix. That same page also has Exim documentation. > > > > So far ..... > > > > Next, I will be looking into "Running Things".... which is where I > believe > > things will get thicker .... > > > Perhaps when you're done you will write u your experiences with FreeBSD > and Exim. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 11 months

[MM3-users] Re: Getting connection timed out

by peter＠chubb.wattle.id.au

>>>>> "Stephen" == Stephen J Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> writes: Stephen> blackout69 writes: >> Il 23/05/21 01:21, Mark Sapiro ha scritto: > Can you successfully >> telnet to port 25 on mail.simail.it from the > Mailman server? No >> > If you can connect (via telnet) to port 25 on mail.simail.it from >> the > Mailman server, then I'd suggest stopping and restarting >> Postfix. >> >> if i try from the mail server i get >> >> telnet mail.simail.it 25 Trying 217.27.113.30... telnet: Unable to >> connect to remote host: Connection timed out Stephen> mail.simail.it is ignoring your mail server. This is not a Stephen> Mailman problem. 1. Check to see if that server has a Stephen> stated policy for "abusive" mail and some way of getting back Stephen> in their good graces. 2. Check if your mail server is in Stephen> the RBLs. Some of them are very aggressive about adding IPs Stephen> and domains. 3. Try writing the postmaster at Stephen> mail.simail.it. 4. Ask your subscriber(s) at mail.simail.it Stephen> to write their postmaster. Also check your firewall rules. Outgoing port 25 is usually blocked by ISPs unless you explicitly ask for it not to be. Peter C

4 years, 6 months

[MM3-users] Re: import an mm3 hyperkitty archive

by Eggert Ehmke

Thank you Mark, this got me on the right track. But I still think this not at all clear when reading the docs. My system is in a venv. I had to run these commands: mailman-web hyperkitty_import --since=01.01.2022 -l mylist@mydomain my-mbox-file mailman-web update_index_one_list mylist@mydomain Where is it stated that in this situation I have to run mailman-web instead of django-admin? Thanks anyway, problem solved. Am Donnerstag, 8. Dezember 2022, 17:51:58 CET schrieb Mark Sapiro: > On 12/7/22 05:57, Eggert Ehmke wrote: > > I was able to export the archive of my old mm3 installation in hyperkitty. > > However, I seem to be blind when looking for hyperkitty_import in the > > documentation. Where to start? > > There is documentation at > <https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html#im > porting-the-current-archives> and also at > <https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy>. > You can also run `django-admin hyperkitty_import --help`. The docs refer > to importing messages from MM 2.1, but you can import messages from any > unix like mbox file. > > Note in the above, `django-admin` is the command you use to invoke > Django's management which may be `django-admin`, `manage.py`, > `mailman-web` or something else depending on how Mailman is installed.

3 years

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/29/20 11:26 AM, Mark Sapiro wrote: > 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>. Thanks Mark. To clarify more, we have this ability for List owners with our own custom admin interface (Affinity). I thought Postorius had that. When I checked out Postorius, I was indeed logged in as server owner. Sorry for the incorrect info. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/6/22 6:28 PM, Stephen J. Turnbull wrote: > > In my Debian configuration [mod_proxy_http.conf] is needed > > because it contains the necessary directives to enable proxying. > > Actually though, I think that's enabled as part of proxy. The Apache documentation strongly implies that this needs to be explicitly enabled by the admin: The forward proxy is activated using the ProxyRequests directive. Because forward proxies allow clients to access arbitrary sites through your server and to hide their true origin, it is essential that you secure your server so that only authorized clients can access the proxy before activating a forward proxy. By contrast for a reverse proxy: A reverse proxy is activated using the ProxyPass directive or the [P] flag to the RewriteRule directive. It is not necessary to turn ProxyRequests on in order to configure a reverse proxy. Both are from https://httpd.apache.org/docs/2.4/mod/mod_proxy.html. > However, see > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > I now suspect the real issue is there's no wsgi server listening on port > 8000. Could be. Apache docs notwithstanding, I'm happy to trust your intuition, and that would make things simple for the OP. :-) Steve

3 years, 11 months

[MM3-users] Re: Moderation not working?

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 11/24/20 12:30 PM, peter(a)chubb.wattle.id.au wrote: >> >> Hi Folks, Running a shiny new instance of mailman3, as per the >> Debian package (version 3.2.2) but the moderation doesn't seem to >> work. WE got hit by a heap of spammers overnight, even though the >> 'hold for moderation' bit is set for non-members (and now for >> members too). Mark> If the action for member posts was accept ot default processing Mark> at the time, perhaps the spam spoofed a member address in one of Mark> From:, Reply-To:, Sender: or the envelope sender, Nope ... >> Emails seem just to get straight through. Mark> Even now with both member and non-member actions set to hold? Haven't seen any emails since setting that bit, so can't tell yet. The only think I noticed after trawling through all the configs is there was no moderator address set up. In Mailman 2.1 that meant the list owner would be asked to moderate. I've added a couple of addresses to see what happens next For other lists on the same mailman instance I *am* seeing moderation requests for non-member postings --- but they had explicit moderator addresses configured. Peter C

5 years

[MM3-users] Re: is there a mailman command/setting to periodically clean archives?

by David Newman

On 12/29/21 4:11 PM, Mark Sapiro wrote: > On 12/29/21 3:58 PM, William Oliver wrote: >> >> I'd like to delete all my archives that are more than a certain age, >> e.g. more than a week old. I can easily do that with a cron job, >> deleting old files in >> >> >> /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* >> >> which is, as far as I can see the only place archive emails live. > > > Those are emails archived in the prototype archiver. That's all the > prototype archiver does - store the mail there. The HyperKitty archived > emails are stored in the mailmanweb database in the hyperkitty_email > table. Attachments are in the hyperkitty_attachment table and other > tables are also involved. As a followup: Is there any need or advantage to running both the prototype and hyperkitty archivers? I did an installation following the venv directions, and it looks as though the system now uses both archivers. If this is a duplication of effort and storage, is it safe to disable the prototype archiver like this: # /etc/mailman3/mailman.cfg .. [archiver.prototype] enable: no and then delete anything under here? /opt/mailman/mm/var/archives/prototype/ Thanks dn

3 years, 11 months

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

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:59 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Sat, Dec 17, 2022 at 9:33 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/16/22 22:21, Mark Sapiro wrote: >> > >> > I suggest you look at ownership and permissions. >> > >> > ``` >> > find /opt/mailman/mm/static/ -not -user mailman >> > find /opt/mailman/mm/static/ -not -perm -u+rw >> > find /opt/mailman/mm/static/ -type d -not -perm -u+x >> > ``` >> > and the same on >> > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ >> > >> > >> >> If the above doesn't reveal anything substantial, then let me know and >> I >> >> can bump up the verbosity. >> > >> > >> > I don't know if --verbosity 3 will reveal anything or not. You could >> try. >> >> >> Did you see the post at >> < >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>? >> >> Have you tried >> ``` >> django-admin clear_cache >> > > (venv) mailman@list:~$ /opt/mailman/mm/bin/django-admin clear_cache > Cache "default" has been cleared! > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ > total 16 > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 css > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 js > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ > total 8 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/js/ > total 8 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. > (venv) mailman@list:~$ > > So all the css files that were in /opt/mailman/mm/static/CACHE/css/ are > gone after running `django-admin clear_cache`. > > After that, I did run my mailman-post-update script again which created > dirfferent files under CACHE/css/ as the date shows > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ > total 20 > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 . > drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 css > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 js > -rw-r--r-- 1 mailman mailman 621 Dec 16 22:46 manifest.json > (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ > total 176 > drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 . > drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 .. > -rw-r--r-- 1 mailman mailman 162923 Dec 16 22:46 output.1d3a3c0dd51d.css > -rw-r--r-- 1 mailman mailman 1209 Dec 16 22:46 output.9a7b11621c5a.css > -rw-r--r-- 1 mailman mailman 569 Dec 16 22:46 output.e68c4908b3de.css > (venv) mailman@list:~$ > > I then rebooted the system just to be sure everything is restarted. > > And the PROBLEM IS SOLVED :-) > > Thank you very much for your time spent in following this up with me to > the conclusion. > So just for the record, I have added the clear_cache option to the script. Maybe this will benefit someone else one day. <CUT> #!/bin/bash set -e BINDIR="/opt/mailman/mm/bin" CONFDIR="/opt/mailman/mm" SETTINGS="settings" DJANGO_CONTROL_SCRIPT="$BINDIR/django-admin" STATIC_DIR="$CONFDIR/static" DEBUG="False" set -x if [ "$DEBUG" == "False" ]; then mkdir -p "$STATIC_DIR" || : "$DJANGO_CONTROL_SCRIPT" clear_cache "$DJANGO_CONTROL_SCRIPT" collectstatic --clear --noinput --verbosity 0 "$DJANGO_CONTROL_SCRIPT" compress "$DJANGO_CONTROL_SCRIPT" compilemessages fi syncdb_cmd="$DJANGO_CONTROL_SCRIPT migrate" if [[ ! -t 1 ]]; then # stdout is not a terminal syncdb_cmd="$syncdb_cmd --noinput" fi $syncdb_cmd echo 'Do you want to rebuild the search index? This takes a long time.' echo 'Type "Yes" to continue; anything else to quit.' read -p "> " response if [ "x$response" != "xYes" ] ; then exit; fi "$DJANGO_CONTROL_SCRIPT" update_index </CUT> The important thing here is that after an update, it helps to run the following 4 options with your "django-admin" script (whatever it is named) - clear_cache, collectstatic, compress, compilemessages. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Fwd: Re: Removing a mail addresses and users

by Allan Hansen

All, This disconnect between Mailman Core and Django and Postorius is, by far, the weakest and, for subscribers, most confusing aspect of MM3 (once it has been installed, which is extremely hard and confusing). In a true account-centric system, you set up a web account and from there manage your emails and, for each email, your subscriptions. Subscription options would be hierarchical: account/email/list, with lower levels inheriting/overriding settings from/the level above. That’s really what I had expected when I pushed for us to move our 50 email lists to MM3 and I was very excited about the prospect, as it would solve a lot of system/subscriber management issues I had managing MM2. Alas, I was very surprised that that’s not how MM3 works. Some things got harder, even, such as the inability to change subscription addresses, which should have been a showstopper from the start! I still hope that MMxx OOTB will get there, but I guess it’ll be along haul. Would we be talking about MM4 to be released 20 years from now? Some dedicated and skilled developers are currently investing heavily in a replacement for Postorius, but I really believe that any work is better spent transforming Mailman Core etc. into a true account-based system. Then, and only then, will it make sense to build new and better interfaces on top, as, without a healthy core, such interface will currently may have to inherit the confusion and disconnect that currently is so aggravating. The above is not meant to aggravate the MM3 development team, for which I have utmost respect and gratitude, and which I admire for their tireless support given over decades to the community of admins. Software development is devilishly hard and time consuming. Yours, Allan Hansen hansen(a)rc.org > Begin forwarded message: > > From: Mark Sapiro <mark(a)msapiro.net> > Subject: [MM3-users] Re: Removing a mail addresses and users > Date: June 10, 2020 at 12:46:01 PDT > To: mailman-users(a)mailman3.org > > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) > > >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 6 months

[MM3-users] Re: Problem with list creation

by Abhilash Raj

On Thu, Sep 17, 2020, at 4:17 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > > > We increased timeout in mailman.cfg > > This looks like the issue in Shashikanth's post, too: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > They are also creating more than 1000 lists. > > Do we know why these timeouts are happening? (Search for "list > creation times out" returns no results in either core or Postorius > issues.) This is the first time I am actually seeing this. I tried hammering a local server with default number of workers, 2, and created 5000 lists in a loop and went through pretty smooth. I am probably not replicating the exact situation, I am using the sqlite database (which I presumed would be slow and choke up faster but...it didn't). Creating list isn't one of the slow operations AFAIK, so I am actually surprised that it needs increasing timeout. It could be the interaction with database layer maybe, but I can't be sure without more debugging. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years, 2 months

[MM3-users] Re: New installation, new issue: mailman3 migrate -- no module CommonMark

by Bill Oliver

On Sun, 2024-10-27 at 10:01 -0700, Mark Sapiro wrote: > On 10/27/24 05:13, Bill Oliver wrote: > > > > (venv) mailman@mail:~$ pip freeze | grep readme > > readme-renderer==17.4 > > > Which is over 6 years old. Howat did that get installed? Current > version > is 44.0. There may or may not be an issue with the current version as > it > imports cmarkgfm which is in the venv of all the MM 3 installations I > support, but I don't know how it gets there as even though > readme_renderer imports it, it is not listed as required by > readme_renderer or anything else. > > In any case, in your venv, do > ``` > pip install --update readme_renderer cmarkgfm > ``` > That did the trick, though I had to use --upgrade instead of --update. Thanks... Now on to the next step. I don't know about the libraries. Here's my mailman info. It seems like the right version of python. (venv) mailman@mail:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:qazASD%401cko@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Thanks for your help! billo

1 year, 1 month

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by ulf.rapphahn＠offis.de

Mark Sapiro wrote: > Lists, not Mailman lists. When you create a list in Postorius or Mailman > core, this is a Mailman list. A corresponding HyperKitty list will also > be created if hyperkitty is one of the active archivers for the list so > you see it in Django. > When you create a list in Django, it is only a HyperKitty list and will > be visible in HyperKitty, but no Mailman list is created so the list is > not in Mailman/Postorius. Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

1 year, 1 month

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/lists/test2.***/settings/message_acceptance MultipleObjectsReturned .. get() returned more than one EmailAddress -- it returned 2!

by Marco Emilio Poleggi

Thanks, Mark. On 2025-09-01 19:40, Mark Sapiro wrote: > On 9/1/25 08:17, ^m'e via Mailman-users wrote: >> >> The same problem appeared today with my mariadb-based installation. @Mark, >> do you have a mysql version of your scripts? > > I'm not certain as I don't offhand have a way to test, but I think > > g/psycopg2/s//pymysql/ > > (i.e. just replace both occurrences of `psycopg2` with `pymysql`) will do it. > Yeah, it works! In my case, no uppercase addresses were found by the UC_fix script, whereas the Mult_primary did spot two accounts, both with 'staff status' in Django admin UI and with the same set of extra addresses. Most probably my fault, as I intended to use both accounts for administrative tasks and played to far with assigning the same sets of addresses, one of which was primary for one account. I guess that was causing the failure, right? -- ^m'e ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/pgp-keys Name: OpenPGP_0xC366FCF67CDBD9F9.asc

3 months, 1 week

[MM3-users] Re: Error: 451 Requested action aborted

by Hagen Bauer

On 16.11.18 00:41, Mark Sapiro wrote: > On 11/15/18 8:23 AM, Hagen Bauer wrote: >> Hi >> I am running mailman in docker and I start to receive this error when my >> postfix tries to deliver a mail >> >> said: 451 Requested action aborted: error in processing (in reply to end >> of DATA command)) >> >> Any idea what is going wrong and where to look for problems? > > > Is there more information in the Postfix mail.log? > > no, in postfix this is the only entry. But I believe I solved one problem and now have to work on the next one. First I saw this error in in a log file ERROR could not translate host name "database" to address: Name does not resolve Based on this hint https://github.com/moby/moby/issues/8425 adding external dns server made this message go away. Now I find this error in my logs. : ERROR: xlog flush request 0/1FA5640 is not satisfied --- flushed only to 0/1E9C7A0 CONTEXT: writing block 0 of relation base/16384/16525 I believe this is related to some sort of database corruption but since I have no idea about postgres I am not sure (I chose the docker images because I didnt want to care about the Internals) any suggestions are welcome

7 years

[MM3-users] Re: SUBSCRIBE_FORM_SECRET in MM3?

by Phil Stracchino

On 2020-01-30 12:01, Mark Sapiro wrote: > On 1/30/20 1:50 AM, Gila Halpern wrote: >> I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option? > > > This feature in MM 2.1 is not very effective. On mail.python.org, this > feature as well as reCAPTCHA is enabled (e.g. > <https://mail.python.org/mailman/listinfo/mailman-users>) and we still > get periodic attacks of robotic subscribes that get around these measures. Human verification vs. verification-defeating countermeasures is an ongoing arms race which, frankly, humans have been losing for a long time. I have more than once commented, not entirely joking, that we're reaching a point where *FAILURE* to complete the CAPTCHA is evidence that you're a human. We need to come up with a better verification paradigm than presenting increasingly difficult puzzles which AI agents are better overall at solving than humans are. -- Phil Stracchino Babylon Communications phils(a)caerllewys.net phil(a)co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958

5 years, 10 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Hello every body I have progress to try to reinstall mailman3 on yunohost server but I still have an error, if somebody can help me as I don't understand the log https://paste.yunohost.org/raw/ugijepuyuv Sincerely. Yvan Le 14/03/2022 à 16:31, Yvan ♞ a écrit : > Ok thanks, I'll try on debian forum as I already unsuccessfully tried > on yunohost since 6 months. > > Le 14/03/2022 à 16:23, Mark Sapiro a écrit : >> On 3/14/22 08:12, Yvan ♞ wrote: >>> Maybe an idea of my problem as I have pgadmin app installed, it >>> could be in conflict to create a postgresql db? >> >> Your original dbug logs seem to show no issue with postgresql. >> >> I don't think people on this list can be much help for installing the >> Debian package on YunoHost. As I said earlier, I would go first to >> YunoHost for help and then to Debian if necessary. >> >> If you want help from us, I recommend installing as documented at >> https://docs.mailman3.org/en/latest/install/virtualenv.html >> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 8 months

[MM3-users] Re: combine postorius and hyperkitty into one Apache vhost

by Eggert Ehmke

So you prefer Gunicorn over uWSGI? When I have a working installation that uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason for this, and while I am open for alternate solutions, ... ´ never change a running system Am Donnerstag, 29. Dezember 2022, 21:48:54 CET schrieb Mark Sapiro: > On 12/29/22 05:51, Wolfgang Rosenauer wrote: > > Hi, > > > > I'm in the process to set up a new mailman3 site. > > (Migrating from mailman2) > > > > There are RPMs for my distribution which integrate postorius and > > hyperkitty with uwsgi. > > I think you'll be much happier if you don't use the distro's RPMs which > are probably out of date and instead follow > <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those > instructions use uWSGI as a WSGI interface, but Gunicorn > <https://gunicorn.org/> is what is used on the site supporting this > list. The advantages of Gunicorn are it's already installed as a > dependency of Mailman core, and it's what the Mailman developers are > more familiar with. > > I'll work on updating > <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include > Gunicorn as an alternative.

2 years, 11 months

[MM3-users] Re: Upgrade to 3.3.2 fails

by Joel Lord

On 12/26/2020 3:07 PM, Mark Sapiro wrote: > As far as utf8mb4 vs. utf8 is concerned. There will be issues with the > hyperkitty_email table subject and content columns in particular and > maybe others if email messages contain 4-byte utf-8 unicodes. However, > as I read the MySQL docs, for columns like VARCHAR(255) and > VARCHAR(510), the difference affects only the number of characters that > can be stored in the column and not the actual column width. I.e., a > VARCHAR(255) column is actually up to 256 bytes wide (1 byte for length > and up to 255 butes of data) and can thus hold up to 85 3-byte utf-8 > encodings or up to 63 4-byte utf-8 encodings, but since any string > normally contains only a few if any (probably none in the case of the > mailinglist table) the actual limit is much closer to 85. > Earlier I had attempted changing the encoding and collation and manually adding the new column, and it failed with the same error. This fits with Mark's explanation of how the column size and encoding go together. I just ran an "optimize table mailinglist;" and then the update ran clean. Thanks for the eyeballs today, no idea why that would have worked but now we're up and running. -- Joel Lord

4 years, 11 months

[MM3-users] [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by William Oliver

On Fri, 2021-12-24 at 21:12 -0800, Mark Sapiro wrote: > On 12/24/21 8:22 PM, William Oliver wrote: > > > > I clicked on that, and it took me to a page where I could add > > servers. > > So, I added my real domain (libertyfp.org) It successfully added > > it, > > so I decided that I clearly didn't need "example.com" as a server, > > and > > deleted it using the same page. > > > > Immediately, I got an "internal server error" and have now lost all > > web > > interfaces. I tried restarting the daemons and rebooting the box, > > to > > no avail. > > > You have to set SITE_ID in your Django settings to the correct value > for > your site. See > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > > Joy! You are a lifesaver. I had to guess at the ID number, but "2" worked. Just out of curiosity, if I could not have guessed a valid ID number and did not have the admin interface, how could I have figured out what site IDs were available? Thanks. billo

3 years, 11 months

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

by Mark

On 2023-09-24 13:28, Mark Sapiro wrote: > On 9/23/23 19:19, Mark wrote: >> >> Yes, the query returns a result and the case in "name" matches that in >> the query ... >> >> select * from hyperkitty_mailinglist where name like >> 'listname(a)domain.com' >> >> id | 91 >> name | listname(a)domain.com >> display_name | Listname >> description | ... >> subject_prefix | [Listname] >> archive_policy | 1 >> created_at | 2023-09-21 08:55:36.385239+2 >> list_id | listname(a)domain.com > > Is that really what you get for list_id? It should have a dot, not at > as listname.domain.com. > > What if you do something like the following where django-admin is > whatever command you use for the Django admin command. > ``` > $ django-admin shell > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models.mailinglist import MailingList >>>> mlist_name = 'listname(a)domain.com' >>>> mlist = MailingList.objects.get(name=mlist_name) >>>> mlist > <MailingList listname(a)domain.com (listname.domain.com)> >>>> > ``` My bad. I was in too much of a hurry when redacting. The list_id is as you say: listname.domain.com

2 years, 2 months

[MM3-users] Re: Mysterious Bounces Being Logged

by Allan Hansen

All, Appreciation to Brian for bringing this up. After upgrading to MM3, a lot of legitimate users' subscriptions on my lists have been disabled even though they still get at least some messages (according to them), while some were correctly disabled. Yes, I need to be informed of bounces, because when the accounts get disabled, I don't want my reply to be 'Huh? I don't have a clue why.' I reported this before. Yours, Allan On 3/26/21, 14:08 , "Brian Carpenter" <brian_carpenter(a)emwd.com> wrote: On 3/26/21 2:59 PM, Mark Sapiro wrote: > They are being bounced by a downstream MTA. If you want to know why, you > have a few choices. You can mail the address yourself and hopefully get > a DSN back. You can install this patch: I would think any mail administrator for a mailman server would want to know why bounces are happening. I never saw this issue with Mailman 2. Did it exist? Is the patch going to make it to the next version of Mailman 3 core? Are there any plans to make bounce processing more transparent to server admins so we can troubleshoot delivery issues? -- Brian Carpenter Harmonylists.com Emwd.com _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 8 months

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

by Jeremy Stanley

On 2024-09-18 16:36:50 -0700 (-0700), Mark Sapiro wrote: > On 9/18/24 10:13, Jeremy Stanley wrote: [...] > > Since all the lists for the given domain will be moving to the same > > unused new domain on the existing server, and can move at the same > > time, I suppose this could be done through (offline if necessary) > > backend database update queries. [...] > ``` > UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = > 'old_domain'; > ``` [...] > ``` > UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE > mail_host = 'new_domain'; > ``` > For HyperKitty, similar changes need to be made to the > hyperkitty_mailinglist table. The `name` column entries need to be changed > from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column > entries need to be changed from `listname.old.domain` to > `listname.new.domain` Preparing to test this, I poked around the schema a bit and noticed that the domain names are also embedded as strings in the following fields: django_mailman3_maildomain.mail_domain django_site.domain django_site.name domain.mail_host Can anyone think of any additional tables/columns which would need updating for this? I'll see if scanning a dump of the full DB content turns up anything I might be missing too. Thanks again! -- Jeremy Stanley

1 year

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Abhilash Raj

> On Nov 1, 2021, at 9:07 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/31/21 10:42 PM, Simon Coggins wrote: >> Looking at the code in gitlab it looks like it wasn’t merged until 1.3.6: >> https://gitlab.com/mailman/postorius/-/blob/1.3.6/src/postorius/urls.py#L53 >> But it’s not in 1.3.5: >> https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49 > > > Yes, I was mistaken. That code was merged on 14 Feb 2021 and is not in Postorius 1.3.4 which was released on 2 Feb. It should have been in 1.3.5 and I don't know why it is not at https://gitlab.com/mailman/postorius/-/blob/1.3.5/src/postorius/urls.py#L49, but that is moot in any case. > 1.3.5 was a security release with no fixed included. It was branched off from 1.3.4 and only the security fix was applied. One Gitlab pro tip is when you are trying to determine which particular release a particular commit is included in, you can click on the the “…” three dots next to "parent 6096958a master” just under the title and it will show all the tags and branches that this commit is included in. https://gitlab.com/mailman/postorius/-/commit/0aba874cae15b1baae2839dca57d3… for example, is included in 1.3.6b1, 1.3.6 and jquery and master branch. -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

Oops sorry I hit send to soon. If I try to go to /lists/listname.example.com/unsubscription_requests<http://listname.example.com/unsubscription_requests> I get a 404, it looks like unsubscription_requests<http://listname.example.com/unsubscription_requests> isn’t in my urls.py list for Postorius? (venv) [mailman@mailman postorius]$ grep version __init__.py # Software Foundation, either version 3 of the License, or (at your option) # any later version. __version__ = '1.3.4' (venv) [mailman@mailman postorius]$ grep _requests urls.py url(r'^subscription_requests$', list_views.list_subscription_requests, name='list_subscription_requests'), I’m upgrading this week to: django-mailman3 1.3.7 mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 postorius 1.3.6 And I’ve just confirmed that 1.3.6 does have the url endpoint. So I’m guessing it came in in 1.3.5+? (venv) [mailman@mailman-dev postorius]$ grep version __init__.py # Software Foundation, either version 3 of the License, or (at your option) # any later version. __version__ = '1.3.6' (venv) [mailman@mailman-dev postorius]$ grep _requests urls.py re_path(r'^subscription_requests$', list_views.list_subscription_requests, name='list_subscription_requests'), re_path(r'^unsubscription_requests$', list_views.list_unsubscription_requests, name='list_unsubscription_requests'), -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:15 pm, Simon Coggins <s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au>> wrote: The version of postorius is 1.3.4 django-mailman3 1.3.5 mailman 3.3.4 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…> although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 1 month

[MM3-users] Re: Show diplay_name in a list

by Abhilash Raj

On Mon, Sep 30, 2019, at 6:33 AM, Joel Lord wrote: > On 9/29/19 5:59 PM, Mark Sapiro wrote: > >> Any idea what I was missing there? > > Often, member.display_name doesn't exist or is "None". > This seems to also be the problem that I submitted a while back (6 > months ago?) that the notification to the moderator of subscription > requests, which should include both display name and email address of > the requestor, only has the email address. We've been trying to track > the problem down in code but it keeps going deeper and deeper... This should be the UI trying to unconditionally convert a Python object to string. Name string transforms correctly, but since the absence of a name is denoted by a None object (as opposed to an empty string ''), the renderer mindlessly converts it to "None". It could be fixed with a simple {% if member.display_name is not None %}{{ member.display_name }}{% endif %} in the right place in the Django template. > > -- > Joel Lord > Web Administrator, Alpha Psi Omega Grand Cast > etc... etc... etc... > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 2 months

[MM3-users] Re: Whitelist non subscriber

by Stephan Krinetzki

Mark Sapiro wrote: > On 08/06/2018 06:43 AM, Stephan Krinetzki wrote: > > > The steps are as follows, right? > > - Add users to the list and give the role "nonmember" > > - Set moderation action ('defer' or 'accept') > > Right. Good. So i understand it :) > > > > The only thing missing in the documentation is a note on how to do > > this via the Admin API. Who can explain that to me? > > Can you be more specific about what you are looking for? If by "Admin > API" you mean the REST API, are you asking how to interact with it or > what specific POST/PUT/PATCH commands to send? > > Or are you asking about the 'mailman shell' command? > With Admin API I mean the REST API from the localhost. Whether it's the REST API, the Mailman shell or the Admin API, I personally don't care. The only important thing is that we can set and use this role. However, I think that's settled anyway, since you're writing > > Also, we want to expose the nonmember role in Postorius and enable > setting moderation action for nonmembers, but we didn't get that in MM > 3.2/Postorius 1.2. So the whitelistening is not working at the moment, right?

7 years, 3 months

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Joachim Schrod

Mark Sapiro writes: > > > I maintain a mailing list for a private holiday where people don't > > subscribe themselves; I subscribe them. I have vetted their email > > address beforehand. (The subscribers are mostly not able to handle a > > verification email, nor any email-based workflow at all.) Is there a > > configuration option for a mailing list that sets "Pre Verified" to > > true as a default? > > > This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed > by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was > later extended by > https://gitlab.com/mailman/postorius/-/merge_requests/945 however these > are not available until Postorius 1.3.14 which is not yet released. > > These add a setting, POSTORIUS_DEFAULTS, which can be used to set these > defaults. E.g., setting > > POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True} > > will set the default for Pre Verified to True. So far, the only defaults > that can be set in this manner are mass_subscription_pre_confirm, > mass_subscription_pre_approve, mass_subscription_pre_verify and > mass_subscription_invite and those not until Postorius 1.3.14, but more > may be added. Thanks a lot for this info -- I'm looking forward for an upcoming Postorius 1.3.14 release! ;-) :-) Happy holidays and a good new year to everyone, Joachim

11 months, 3 weeks

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

by Abhilash Raj

> On Mar 27, 2021, at 3:03 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > 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? I guess Brian was asking about Subscription Requests. Support for specifying reason when rejecting subscription requests has been added in master and will be a part of next release, 1.3.5 most probably. -- thanks, Abhilash Raj (maxking)

4 years, 8 months

[MM3-users] Re: mailman3 postorius cannot retrieve template

by Andreas Barth

* Quanah Gibson-Mount (quanah(a)symas.com) [211104 22:59]: > > > --On Thursday, November 4, 2021 8:25 AM -0700 Mark Sapiro > <mark(a)msapiro.net> wrote: > > >On 11/4/21 5:04 AM, Wolfgang Bock via Mailman-users wrote: > >> > >>My conclusion: > >>I ask you to consider these experiences in an update for the mailman3 > >>packages in debian bullseye. It would save time, questions and nerves. > > > > > >Issues with Debian packaging should be directed to Debian. > > Or as previously discussed, the debian packages should be avoided entirely. I strongly disagree with that statement. Distribution packages have their own up- and downsides. Of course, how they are done is to be discussed with the distribution, so: if something is wrong with a debian package, please follow the instructions on bugs.debian.org on reporting bugs. However, they have the advantage that they're integrated with the distribution. They have the disadvantage that they're stable for some time - that is why it's called a stable release. If they have all the features someone wants, they usually work fine (and my first mm3-installation was the default debian package). If one looks for bleeding edge, of course that's not what one can expect from a distribution package - but that's also a feature. Andi

4 years, 1 month

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

by Florian Schulze

On 29 Jun 2020, at 23:40, Mark Sapiro wrote: > 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? Yes > Are you running the Django periodic jobs? They were disabled because of the errors (someone else did the upgrade). I have enabled them again and will watch it and report back. Regards, Florian Schulze

5 years, 5 months

[MM3-users] Re: Emailing a list from the list server

by Mark Dadgar

On Jun 1, 2020, at 11:45 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/1/20 10:02 AM, Mark Dadgar wrote: >> >> I cannot email a list from an account on the list server itself (for example, programmatically by script, but also manually) using mail / mailx / mutt / etc from the command line. The emails just disappear into the ether. > > > What's in Postfix's mail.log? Jun 1 11:54:55 mail postfix/lmtp[238922]: 1F42613BEB5: to=<test3(a)pdc-racing.net>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.04, delays=0.02/0.01/0/0.02, dsn=2.0.0, status=sent (250 Ok) smtp.log: Jun 01 11:54:55 2020 (238852) Peer: ('127.0.0.1', 53402) Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) handling connection Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'LHLO mail.pdc-racing.net' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'MAIL FROM:<mark(a)pdc-racing.net>' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) sender: mark(a)pdc-racing.net Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'RCPT TO:<test3(a)pdc-racing.net>' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) recip: test3(a)pdc-racing.net Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'DATA' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) Data: b'QUIT' Jun 01 11:54:55 2020 (238852) ('127.0.0.1', 53402) connection lost Jun 01 11:54:55 2020 (238852) Connection lost during _handle_client() Test3 is a working mailman3 list. There are no posts held for moderation. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 6 months

[MM3-users] Re: {Spam?} Re: Monthly mailman-web job using a lot of memory

by Andy Smith

Hi, On Fri, Jul 01, 2022 at 12:57:41PM -0700, Mark Sapiro wrote: > I second Mark Dadgar's comment to replace whoosh with xapian. It > will help, although it requires rebuilding the entire search > index. Thanks both. Yes I am currently using whoosh which is the Debian packages' default. I decided to dramatically reduce the number of messages in our archives, as the vast majority of them are for lists that had never actually been looked at ever when under Mailman2, and external archives of them already exist. For ~6k messages it still took approx 16 hours to run that monthly job, and during that time spewed out thousands of these errors: Failed to remove document 'hyperkitty.email.29351' from Whoosh: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/haystack/backends/whoosh_backend.py", line 309, in remove self.index.delete_by_query(q=self.parser.parse('%s:"%s"' % (ID, whoosh_id))) File "/usr/lib/python3/dist-packages/whoosh/index.py", line 365, in delete_by_query w = self.writer() File "/usr/lib/python3/dist-packages/whoosh/index.py", line 464, in writer return SegmentWriter(self, **kwargs) File "/usr/lib/python3/dist-packages/whoosh/writing.py", line 515, in __init__ raise LockError whoosh.index.LockError …so I'm not even sure if it worked. I will definitely have to look in to switching to Xapian. Thanks, Andy

3 years, 5 months

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

by Eric Broens

Hi Mark, 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. This is weird because other mails have been distributed. The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings Best Regards,Eric On Sunday, December 13, 2020, 06:29:19 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 7:40 PM, Eric Broens via Mailman-users wrote: > There are no messages in var/archives/hyperkitty/spool/. At this time of the night (4:40 AM local time), there is no incoming mail. I'm not sure what is causing the repeated access of /archives/api/mailman/urls... This call comes from Mailman core in order to request the URL at which a message will be archived. It is called from mailman/src/mailman/handlers/rfc_2369.py when adding the Archived-At: header and from mailman/src/mailman/handlers/decorate.py in order to get the hyperkitty_url replacement value. I don't understand why it would be called repeatedly for the same message. Are there any clues in mailman.log. > I just noticed when clicking on "All Threads" or "Threads by month", the emails are displayed. The statistic however shows that there were no mails in the past month, while there actually are.When clicking "Recent", "Most Active", etc. the page shows "No discussions this month (yet)." What if you look at "threads by month" and select the current month? > Another observation. For one list, which is one of the more active ones, the bar diagram is not empty, while showing 0 participants and 0 discussions (see attached screenshot).This one however shows the mailthreads when opening the list. I think the basic issue is when you see no messages, HyperKitty, for whatever reason thinks there are no current messages. I'm not sure, but if there are recent posts, are they all in threads started more than 30 days ago? As far as all the participants/discussions counts being zero, I think one of the periodic jobs will fix that (possibly the daily recent_threads_cache job) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years

[MM3-users] Re: Enable delivery

by Hirayama, Pat

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

1 year

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

by Alexander Inzinger-Zrock

Am 29.04.25 um 18:27 schrieb Mark Sapiro: >> 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. + [X] deactivate services + mailman3.service + mailmanweb.service + postfix.service + postfix(a)-.service + [X] deleting files under /opt/mailman/mm/var/data + postfix_domains + postfix_domains.db + postfix_lmtp + postfix_lmtp.db + [X] restart services + mailman3.service + mailmanweb.service + postfix.service + postfix(a)-.service LEARNINGS: + no new files made (expected). + despite mailman3.service reports: + 'Apr 30 14:37:40 mlist01-prod mailman[533171]: Generating MTA alias maps' + postfix warns about the deleted files (expected): Apr 30 14:41:02 mlist01-prod postfix/error[533928]: warning: hash:/opt/mailman/mm/var/data/postfix_domains is unavailable. open database /opt/mailman/mm/var/data/postfix_domains.db: No such file or directory Apr 30 14:42:02 mlist01-prod postfix/error[533928]: warning: fast_flush_domains: hash:/opt/mailman/mm/var/data/postfix_domains: table lookup problem Apr 30 14:42:02 mlist01-prod postfix/error[533928]: warning: C5B821C00E5: flush service failure

7 months, 1 week

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Andrew Bernard

Hi Mark, Thanks for your great help. But despite decades of UNIX experience, my area is not Django (yet). The nub of my question is that I thought you have to have a manage.py file for Django to be able to set up the various affairs, such as making the database migrations and so on. It is that that is eluding me. Apologies for this hopelessly newbie question. I was impressed with your method of installation in the page referenced, and I have foolwed that closely. But I am puzzled about the build script. If I run as user mailman, not root, it wanted to install under /usr. which of course results in permission denied. I had to modify the script to say this: python setup.py install --prefix /opt/mailman/mm/venv I am concerned that I have also misunderstood something here. A On Sun, 9 Jun 2019 at 00:57, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/8/19 4:04 AM, Andrew Bernard wrote: > > > > Where is the Django config area for the > > pip installed modules? It is this that I find obscure. > > The short answer is wherever you put it. If you look at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > which Abhilash mentioned, you'll see what I do. > > >

6 years, 6 months

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

by Quanah Gibson-Mount

--On Thursday, March 17, 2022 12:06 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This says that there is no Address object with the email > xxxxxxxx(a)xxxxx.org > > What do you get in `mailman shell` for > ``` > >>> um = getUtility(IUserManager) > >>> um.get_address('xxxxxxxx(a)xxxxx.org') > >>> um.get_user('xxxxxxxx(a)xxxxx.org') > ``` > These should return an Address and a User respectively. If they don't, > did you perhaps run some process to delete the user? I've done nothing in regard to this user. Neither command returns anything. I see it return my user object if I test with my own email address. > If the user is gone, you should be able to replace > ``` > ... sub_mgr.confirm(token) > ``` > in the above with > ``` > ... wfm = getUtility(IWorkflowStateManager) > ... pendings.confirm(token, expunge=True) > ... wfm.discard(token) > ``` > to clear the pending subscription and workflow and then be able to mass > subscribe the user. I did this, and can confirm that they no longer show up in the list of pending subscriptions via the mailman shell interface for that list. However, if I go to mass subscribe them via the interface, I get: HTTP Error 409: b'Subscription request already pending' Regards, Quanah

3 years, 8 months

[MM3-users] Re: message awaits moderator approval

by Eggert Ehmke

Yes, the templates did have URL's of the old lists. I changed them to refer to the new lists. Am Mittwoch, 21. Dezember 2022, 21:33:26 CET schrieb Mark Sapiro: > On 12/21/22 08:53, Eggert Ehmke via Mailman-users wrote: > > Now it turned out that there were several relicts of the old list in the > > database, in particular in the template table. I removed them using direct > > SQL commands. > > > > Now my new mailing lists work as expected. > > > > Is this a bug in postorius? I think when I delete a mailing list, all > > relicts should be deleted from the database. > > Were there Postorius custom templates for that list?, I.e. did the > template table entries have Postorius URLs. If so, this is probably a > Postorius issue. I haven't actually looked, but when Postorius deletes a > list, it should delete any of it's templates from the > postorius_emailtemplate table and revert the template table entries. > > Beyond that, Postorius is just telling Mailman core to delete the list, > and when Mailman core does that it should probably also remove any > var/templates/lists/<list_id> directory and any entries from the > template table with context = the list_id. If it doesn't, this is a core > issue.

2 years, 11 months

[MM3-users] Re: mail loops back to myself

by Florian Sukup

On 6/12/25 19:48, Mark Sapiro wrote: > > That is not correct. Postfix should receive the initial connect and smtp > for the list and then transport_maps should tell it to relay the message > via lmtp to the configured lmtp_host and lmtp_port (127.0.0.1:8024 per > your previously posted mailman.cfg). You have also posted that Postfix > main.cf contains > > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > > What is the content of that file? In particular does it contain > > mylists(a)lists.yyy.com lmtp:[127.0.0.1]:8024 > Yes, that's exactly the case. > and is the timestamp of /var/lib/mailman3/data/postfix_lmtp.db >= that > of /var/lib/mailman3/data/postfix_lmtp, and have you restarted/reloaded > Postfix since updating main.cf? And, is Mailman core running and > listening on port 8024? > # ls -rtl total 296 -rw-rw---- 1 list list 270336 Jun 8 21:58 mailman.db -rw-rw---- 1 list list 1123 Jun 12 08:43 postfix_lmtp -rw-rw---- 1 list list 367 Jun 12 08:43 postfix_domains -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_lmtp.db -rw-r----- 1 list list 12288 Jun 12 08:43 postfix_domains.db # lsof -i :8024 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python3 1146914 list 23u IPv4 78503106 0t0 TCP localhost:8024 (LISTEN) I always restart mailman3 after changing main.cf if there is any interest, postfix_domains contains this line: lists.yyy.com lists.yyy.com Florian.

6 months

[MM3-users] Re: auto-away notices as bounces

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210830 04:30]: > On 8/24/21 11:17 AM, Andreas Barth wrote: > > > >Well, the mail adress got disabled, and the user got warning mails > >("Your subscription for list mailing list has been disabled"). As none > >of the list owners did that, I don't think there is any other > >explanation. Please note that individualsation was enabled, so all > >mails are sent out with per-subscriber mail envelope address, which > >then makes bounce detection quite straight-forward. > > > If by 'individualsation was enabled' you mean messages were VERPed, > there could be a bug here. Yes, that's what happens. > There are a couple of considerations. First the vacation responder > should not respond to list messages. See > <https://www.rfc-editor.org/rfc/rfc5230.html#section-4.6>. I fully agree with you, and already responded with the same remark to the user before sending my initial mail here. > That said, bounce processing should treat even a VERPed message as > unrecognized if it doesn't look like some kind of DSN. This may not > be the case in MM 3. Thanks, that's what I also think. Looking at the returned mail, they definitly don't look like DSNs / bounces to me. Anything I should be doing re this topic? Thanks, Andi

4 years, 3 months

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

by Allan Hansen

That worked, Mark. Thank you. Now I just have to figure out how to put it all in a script for the cron utility, so I can run it daily (or hourly, for that matter). But for now I have no more non-members. Yours, Allan As for non-members, the list settings for 'Message Acceptance' has a number of options to accept, hold, reject or discard messages for a list of addresses (entered using regexps, even) of non-members. Under 'Users' there is an option to add non-members. Given this, the notion that non-members are being automatically created in the database, has been a source of confusion to me, let alone my users/moderators. On 9/17/22, 11:18 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/17/22 11:01 AM, Allan Hansen wrote: > Sure: > >>>> lm = getUtility(IListManager) >>>> for l in lm: > ... print(l.posting_address) > ... >>>> > > Nothing here, either. So your `mailman shell` command is not pointing at your productiom mailman.cfg. Try `mailman -C /path/to/production/mailman.cfg shell` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 2 months

[MM3-users] Re: "to" Headers for Non-Anonymous lists

by Dan Caballero

> But I am confused as to your goal. Previously when the list was > anonymous, all replies went to the list. Maybe your goal is to have list > replies be addressed to <list-name(a)caltech.edu> rather than Last Name, > First Name via list-name <list-name(a)caltech.edu>. If that is the goal, > you could try setting Reply goes to list setting to Reply goes to list. > That will set a Reply-To: list's short description > <list-name(a)caltech.edu>. That may be what you want as long as the > responder's MUA honors Reply-To: over From: > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Thanks. I had forgot to mention that we did also configure the DMARC mitigation to show the sender's email. You're correct about us looking to set the "reply-to" to the list address instead of the sender. I've done some testing and this is close to what we need. However, I seem to be having an issue with the option for "Explicit Reply-to set; no Cc added". The messages are still including a Cc field with the sender's email. Is there another setting that affects the Cc field? Thanks again.

6 months

[MM3-users] Re: Fwd: Re: Removing a mail addresses and users

by Stephen J. Turnbull

Mark Sapiro writes: > Then the people who developed the web based management UI (Postorius) > and archive UI (HyperKitty) chose to develop those within a Django > framework and Django has its own concept of User separate from Mailman > Core and that is where the disconnect occurs. > > It's not that Mailman Core lacks what you want. It's that Django doesn't > use it. I think that's mostly right, in terms of the features that users miss. However, as far as I know, Mailman core does lack facilities for identification, authentication, and authorization of connections to the REST API. And that means that the front ends have to handle this. I would guess that's why the web interfaces are built around Django user authentication. I think it would be possible to have somewhat tighter integration between the Django "web users" and the Mailman core User objects, but it's not necessarily going to be trivial. I see that Abhilash is pretty optimistic, but I fear this this is going to be a long-tail situation where we're going to be seeing core user vs. web-gui user integration issues in 2030 (maybe by then only 1 every 450 days ;-). I have some ideas, maybe in a couple weeks I can sketch them out. Steve

5 years, 5 months

[MM3-users] Re: customized welcome message

by Nils

On 12/7/23 22:40, Mark Sapiro wrote: > How and to what did you set the URL for the template? What does the > database query > > SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; > > show? http://localhost/postorius/api/templates/list/testliste.lists.DOMAIN.TLD This value can't work. Now it makes sense that it gets redirected and the use of localhost also explains why it didn't show in any of the virtual hosts log files that I was checking until it was redirected. However, I didn't set that value. I edited the template at postorius/lists/testliste.lists.DOMAIN.TLD/templates and there I can just select a template type and then I get one textarea input field for the content. The value in the database is set automatically, when I create a template in postorius (and is also automatically removed when I delete a template there). I can't edit this value without manually changing it in the database. > This is very old. Current Postorius is 1.3.10. 1.2.4 is from February > 2019. The Debian/Ubuntu packages are out of date. We recommend > installing via the doc at > https://docs.mailman3.org/en/latest/install/virtualenv.html The server will be updated from Ubuntu 20.04 (focal) to 22.04 (jammy) very soon. The Debian/Ubuntu packages sure have their downsides but once they work, they update automatically and require very little maintenance.

2 years

[MM3-users] Re: Hyperkitty messages stuck in spool

by Andrew Hodgson

Stephen J. Turnbull wrote: >Mark Sapiro writes: > > On 11/18/21 6:38 AM, Andrew Hodgson wrote: > > > > > > Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? > > > > I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. > >If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack. Thanks. Andrew.

4 years

[MM3-users] Re: [Mailman-Users] Web interface for users (not admins)?

by Stephen J. Turnbull

Mark Sapiro writes: > No, Posting from HyperKitty without using the "Use email software" > button is plain text only. That surprised me. There is the possibility of enabling Markdown in the viewer, but that's not a real solution for atechnical users who are used to mousing around, and by itself doesn't enable attachments. > There is no plan to add any sort of rich text capability. That doesn't surprise me. A number of things are possible, but I think that providing the mailto link give the atechnical user the best of both worlds: a quick text-based response or the comfort (? :-þ) of their usual mail client. One constraint that we have is that many of our users value "no Javascript" quite highly, so just dropping in the Electron-based editor du jour is something we don't want to do. By the way, Skip, if you decide that richtext followups are an important feature, earlier I mentioned EMWD's commercial offerings Affinity (for admin) and Empathy (for archiving). I don't know if Empathy offers more features for posting than HyperKitty does, but I encourage you to check with Brian Carpenter <brian(a)emwd.com>. These are commercial, closed-source (at least for now) offerings, but I believe rates are reasonable and support has a very good reputation. Regards, Steve

4 years, 7 months

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

by Odhiambo Washington

On Wed, Dec 14, 2022 at 8:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/14/22 08:15, Odhiambo Washington wrote: > > After upgrading MM3 and running all the post-update tasks and even > > re-indexing all the posts, I have ended up with a somehow "broken" > > hyperkitty. > > The archives display on a browser six, to say the least. > > The site is public, so I can share the link: > https://list.rc.org/archives/ > > > > What should I do in order to fix this? > > > > > Are you asking about the lack of style or the "No archived list yet."? > The lack of style is the main issue. > The former indicates an issue in your web browser with accessing the > `static` directory or an issue with the django admin collectstatic or > compress commands. > So I have tested this with Brave, Google Chrome, Firefox - all on MS Windows and I do clear the browser cache. > I don't know about the latter - could it be because all the archives are > private and I'm, not logged in? > Even when logged in, the situation is the same, unfortunately. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: Social signup?

by Duane Raymond

HI Mark, On Sun, 12 Mar 2023 at 22:06, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/12/23 13:56, Duane Raymond wrote: > > Is there a way to enable social signup (vs just login for existing > users)? > > It isn't at all clear or documented, but a user without an account can > go to the login page and login via a social account button and this will > create an account connected to that social account and log the user in. > Thanks for clarifying. Once I implemented social login, the buttons for social login did appear fine on the login page, but not on the signup page. I noticed for this list as well, there are no social signup buttons. So if it works, how does this happen? 1. Is there something I am missing adding to my settings.py and settings_local.py files to make it appear on the Posterius/Hyperkitty signup (vs login) page? (I searched but couldn't find anything) 2. Do I manually add this code to the Posterius/Hyperkitty signup template? 3. If a user tries to login via the login page and isn't registered will it be counted as a signup? 4. something else :-) I'm trying to get my head around where this is working from / what I need to do to get social signup obvious on the signup page (or other route) Cheers, Duane

2 years, 9 months

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 3:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > We're really working on getting a consistent, workable installation > story and even getting some packaged solutions. I know we're not yet > there, but we're here to help when people run into problems. The site now works, but not the / url for the site. I get this error in the mailman-web.log (with a very long stacktrace before it) NoReverseMatch: Reverse for 'hyperkitty.views.index.index' not found. 'hyperkitty.views.index.index' is not a valid view function or pattern name. I think that would correspond to this line in urls.py url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), but this corresponds exactly to what the example config says and I know of no other name for hyperkitty. Probably it is dependent upon understanding the url dispatching in Django but that takes some time to read up on. The interesting thing is that /archives works so it is just this redirect that has problems. I can probably get apache to do the redirect instead but that is not the most elegant solution. Then I of course have things to do on getting social logins to work. I currently get "DoesNotExist: SocialApp matching query does not exist." if trying to connect an account to google (which I started with). Not a showstopper as passwords do work. cheers // David

8 years, 8 months

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

by Peter Münster

On Thu, Jan 25 2018, Mark Sapiro wrote: > It's got a different name. It's in the above directory, at > example_project/wsgi.py Thank you. Unfortunately, it does not work... First I tried with python-3 (installed package was "apache2-mod_wsgi-python3"), but I got this error: Invalid command 'WSGIScriptAlias', perhaps misspelled or defined by a module n...ration Then, I tried with python-2 (installed package is now "apache2-mod_wsgi"), and this is the error message of apache: mod_wsgi (pid=18880): Target WSGI script '/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py' cannot be loaded as Python module. mod_wsgi (pid=18880): Exception occurred processing WSGI script '/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py'. Traceback (most recent call last): File "/srv/www/htdocs/ckc3r/postorius/example_project/wsgi.py", line 16, in <module> application = get_wsgi_application() File "/usr/lib/python2.7/site-packages/django/core/wsgi.py", line 14, in get_wsgi_application django.setup() File "/usr/lib/python2.7/site-packages/django/__init__.py", line 17, in setup configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup(name) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 44, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 92, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import__(name) ImportError: No module named settings Could you help me please, to get Postorius working (and later also HyperKitty...)? TIA for your efforts, -- Peter

7 years, 10 months

[MM3-users] Re: MM3+Python3.11

by Odhiambo Washington

On Mon, Mar 6, 2023 at 7:52 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Mon, Mar 6, 2023 at 7:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 3/6/23 08:23, Odhiambo Washington wrote: >> > >> > I install Python3.11 manually on Debian12 (maybe this is the issue!) VM >> > using the script below: >> > #!/bin/bash >> > cd Python-3.11.2 >> > ./configure --enable-optimizations >> >> You also want --enable-shared >> > > I had done that, but somehow the build had failed with it. I will try it > again. > I managed to reinstall Python3.11 the correct way: <CUT> #!/bin/bash cd Python-3.11.2 ./configure --enable-optimizations --enable-shared make altinstall # Set Python 3.11 as the Default update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.11 1 # Install PIP using the following command if you do not have it. curl -sS https://bootstrap.pypa.io/get-pip.py | python3.11 </CUT> After this, I installed a fresh venv, activated and installed everything according to ``` https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… ``` MM3 is running fine with uwsgi as documented. I have not deviated even a single step from the documentation above. Now I will test with mod_wsgi and gunicorn and report back. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 9:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/25/22 01:14, Odhiambo Washington wrote: > > On Sat, Dec 24, 2022 at 9:40 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> How about https://mm3-lists.kictanet.or.ke/user_profile/ ? > >> > > > > I have uncommented the line "WSGIScriptAlias /user-profile > > /opt/mailman/mm/wsgi.py", > > I don't see any definition for it in urls.py as well. Perhaps that's the > > issue? > > > It is defined in django_mailman3/urls.py which is referenced by > > re_path(r'', include('django_mailman3.urls')), > I have seen that now. > > When I uncomment /user-profile, I end up with an ugly URL: > > https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ > > > > So instead of aliasing the /user-profile, I have decided to add another > > definition to urls.py: > > re_path(r'^user-profile/', include('allauth.urls')), > > Which I think gives me a cleaner URL: > > https://mm3-lists.kictanet.or.ke/user-profile/login/?next=/user-profile/ > > It shouldn't include `allauth.urls`. That URL is appropriate if you > aren't logged in, but what do you get when you are? > > Go to https://lists.mailman3.org/user-profile/ and log in if necessary > and you'll see what it should look like. > Here when I log in. I land on the /archives ( https://lists.mailman3.org/archives/?sort=popular) I then head to the dropdown and click "Account " and I am taken to https://lists.mailman3.org/user-profile/ (very clean URL!) and that's the same thing I am seeing on my server at the moment.. When I comment out the edit I had on /etc/mailman3/urls.py and uncomment to /user-profile alias in the VHOST, I end up with 1. https://mm3-lists.kictanet.or.ke/user-profile/mailman3/lists/ - once I am logged in 2. https://mm3-lists.kictanet.or.ke/user-profile/user-profile/ - when I click on "Account " # I hope you can see the duplication of /user-profile, which is ugly. However, your server isn't using mod_wsgi, I believe, so I shouldn't be comparing it to mine. I just don't like the extra URLs being added. > I also had to alias /accounts, which then brings me to: > > https://mm3-lists.kictanet.or.ke/accounts/mailman3/lists/ - which I > believe > > is fine because one gets the > > option to either login or signup. > > > > And I think that "/account" and "/user-profile" are synonymous. > > They are in your instance because of > > re_path(r'^user-profile/', include('allauth.urls')), > > but they should not be. > I have changed that, as already pointed out, but with consequences :) There must be a way to not have "/user-profile/user-profile" > >> It's a mod_wsgi thing. I haven't used mod_wsgi for Mailman for some time > >> (I now use gunicorn on all the sites I manage), but when I did I think I > >> had > > > > > >> WSGIScriptAlias /mm3 /opt/mailman/mm/wsgi.py > >> > >> and all the URLs were like https://example.com/mm3/mailman3/..., > >> https://example.com/mm3/archives/..., etc. > >> > > > > I already had gunicorn working too, but I just need to also figure out > this > > mod_wsgi. > > > Why? Intellectual curiosity or do you have an actual need. > It's out of intellectual curiosity actually. The bottom line is with mod_wsgi, whatever you have in your > WSGIScriptAlias is going to be prepended to the URL path. If you don't > want anything prepended, you need > ``` > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > ``` > but then in order for user-profile to work, you need to replace > ``` > re_path(r'', include('django_mailman3.urls')), > ``` > in urls.py with the urlpatterns from django_mailman3/urls.py > ``` > re_path(r'^user-profile/delete$', delete_account, > name='mm_user_account_delete'), > re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), > ``` > and also add > ``` > from django_mailman3.views.profile import delete_account, user_profile > ``` > to the imports in urls.py > And with that, I am now happy with what I am seeing. Again, thank you very much. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users]Re: Installation issues

by Andrew Hodgson

Mark Sapiro wrote: >On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > >> I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? >Sort of, but it's not (yet) public. The process I followed is very >convoluted and not what I would recommend anyone follow. Part of the >issue is I started with mailman-bundler not using a venv, but bundler >still installs a lot of stuff in Python 2 and Python 3 venvs. I then >proceeded to install the git master branches of mailman, >mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their >dependencies system wide and ripped out most of the venv stuff. I started off without using venvs and ran into several issues, though one of them I think was due to the bundler pulling down an outdated dependency. My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible. Thanks. Andrew.

9 years, 7 months

[MM3-users] Re: Announce Only List

by hansen＠rc.org

Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 8/13/20 9:49 AM, joseverde(a)gmail.com wrote: > > So if we want to make a list announce only (e.g. > > only specific > > folks) can post, I've found I can set the list settings to > > automatically discard messages from members and non-members. Then > > I go into the individual permissions on each user to be allowed > > to post without moderation. This works fine, however it seems > > cumbersome. > > Don't we have a list style for announce lists? If we don't, we > should.... > I don't see what's "cumbersome" about the individual permissions. You > need to do something per allowed user, if only sending email to > their individual addresses to tell them the password in the anternate > method: > > There is an alternative. Set a moderator_password for > > the list. Then > > anyone can successfully post with an Approved: <password> header or > > pseudo header if they know the password. > > Steve I have a few lists that I set up as announce-only lists by simply dumping all email but that from a couple of authorized members. It's a one-off deal and was trivial to set up. There are more urgent things to spend time on, IMHO. :-)

5 years, 3 months

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

by Odhiambo Washington

On Sat, Oct 28, 2023 at 7:19 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/28/23 01:59, Odhiambo Washington wrote: > > Running an install on Debian12 VM. Getting a new error message that I > > haven't seen previously: > > > > (venv) mailman@debian12:~$ mailman-web compress > > Compressing... Invalid template socialaccount/login_cancelled.html: > Invalid > > block tag on line 7: 'element', expected 'endblock'. Did you forget to > > register or load this tag? > > Invalid template account/verified_email_required.html: Invalid block tag > on > > line 7: 'element', expected 'endblock'. Did you forget to register or > load > > this tag? > > > These templates are part of django_allauth. What is your version of > that? There are backwards incompatible changes in version 0.58. See > > https://github.com/pennersr/django-allauth/blob/main/ChangeLog.rst#backward… (venv) mailman@debian12:~$ pip freeze | grep django-all django-allauth==0.58.0 If you have 0.58 try > ``` > pip install django_allauth\<0.58 ``` > After that, I end up with: (venv) mailman@debian12:~$ pip freeze | grep django-all django-allauth==0.57.0 And then `mailman-web compress` is happy. -- 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, 1 month

[MM3-users] Re: Upgrading packages

by Eggert Ehmke

Am Donnerstag, 13. Oktober 2022, 20:25:44 CEST schrieb Mark Sapiro: > On 10/13/22 10:55, Eggert Ehmke wrote: > >> 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? > > It should have nothing to do with migrations. The command > ``` > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > ``` > run as the mailman user with your venv active should have set the > content of venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py > to be the same as > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/renderer. > py, but it didn't. I wonder what else didn't get upgraded? Clearly it did do > something because mistune was upgraded. In the meantime I run pip install --upgrade --force-reinstall git+https://gitlab.com/mailman/hyperkitty@master and that installed the correct renderer.py. Should I do this with all packages? > If you run `pip freeze` in your active venv,, what versions do you see > for the things you upgraded? Do they look for example like > ``` > HyperKitty @ > git+https://gitlab.com/mailman/hyperkitty@cf585a6588a176e714ec32bbcfe52e8a28 > fd7803 ``` Yes that version is installed.

3 years, 2 months

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Thanks Mark! I changed the outgoing.py per cut&paste because I didnt know, whow th patch a python file ... But succeeded: /var/log/mailman3/mailman.log Apr 08 19:08:10 2020 (9234) Master started Apr 08 19:08:12 2020 (9241) bounces runner started. Apr 08 19:08:12 2020 (9263) virgin runner started. Apr 08 19:08:12 2020 (9259) out runner started. Apr 08 19:08:12 2020 (9255) lmtp runner started. Apr 08 19:08:12 2020 (9259) Cannot connect to SMTP server localhost on port 25 [Errno 13] Permission denied: '/var/lib/mailman3/cache/7d/c6/7dc6d1a99a5ecf2b2241d6d0958a2bc704e32238150e5cc273f6779b124bd04f' Apr 08 19:08:12 2020 (9237) archive runner started. .... Checked the ownership .... ls -la: /var/lib/mailman3/cache drwxrwx--- 3 root root 4096 Nov 9 22:27 61 drwxrwx--- 3 root root 4096 Feb 3 17:37 6c drwxrwx--- 3 root root 4096 Nov 12 11:59 71 drwxrwx--- 3 root root 4096 Nov 6 12:01 72 drwxrwx--- 3 root root 4096 Feb 5 21:52 7d drwxrwx--- 3 root root 4096 Feb 5 23:05 8b drwxrwx--- 3 root root 4096 Nov 12 23:41 94 drwxrwx--- 3 root root 4096 Nov 7 08:31 ae drwxrwx--- 3 root root 4096 Nov 12 23:40 fa /var/log/mailman3/mailman.log .... Apr 08 19:08:19 2020 (9259) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 93, in _dispose self._func(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/deliver.py", line 86, in deliver refused = agent.deliver(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/bulk.py", line 100, in deliver self.decorate(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/mta/decorating.py", line 32, in decorate decorator.process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 264, in process process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/decorate.py", line 73, in process for archiver in IListArchiverSet(mlist).archivers: File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 135, in __call__ adapter = self.__adapt__(obj) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 151, in __adapt__ adapter = hook(self, obj) File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 353, in queryAdapter return self.adapter_hook(provided, object, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 363, in adapter_hook result = factory(object) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 600, in __init__ for archiver in config.archivers: File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 260, in archivers archiver = call_name(class_path) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 70, in call_name return named_callable(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/archiving/mhonarc.py", line 46, in __init__ config.archiver.mhonarc.configuration) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 335, in external_configuration cfg_path = str(expand_path(resources, path)) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 80, in expand_path cfg_path = resources.enter_context(path(package, resource + '.cfg')) File "/usr/lib/python3.7/contextlib.py", line 426, in enter_context result = _cm_type.__enter__(cm) File "/usr/lib/python3.7/contextlib.py", line 112, in __enter__ return next(self.gen) File "/usr/lib/python3.7/importlib/resources.py", line 188, in path yield Path(reader.resource_path(resource)) File "<frozen importlib._bootstrap_external>", line 932, in resource_path File "<frozen importlib._bootstrap_external>", line 941, in is_resource File "<frozen importlib._bootstrap_external>", line 95, in _path_isfile File "<frozen importlib._bootstrap_external>", line 87, in _path_is_mode_type File "<frozen importlib._bootstrap_external>", line 81, in _path_stat File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 114, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Apr 08 19:08:19 2020 (9259) SHUNTING: 1586365699.6492867+798bd45a31fb2b8d5fd24a481a3cf95710994bf7 Apr 08 19:08:19 2020 (9259) out runner exiting. Apr 08 19:08:19 2020 (9234) Master watcher caught SIGTERM. Exiting. Apr 08 19:08:19 2020 (9234) Master stopped Changed the ownership for /var/lib/mailman3/cache to list:list and from that point my lists are responding. Same problem occurs before fort he list-directory, which I corrected some days ago. Is the ownship misconfiguration a coincidence or did I made a mistake somewhere?? Thanks for your assistance! Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Mittwoch, 8. April 2020 00:23 An: MM3 Users <mailman-users(a)mailman3.org> Betreff: [MM3-users] Re: Uncaught runner exception On 4/7/20 2:40 PM, Wolfgang Bock via Mailman-users wrote: > Yes, I assume that means telnet localhost 25 succeeds. Try the attached patch to mailman/runners/outgoing.py. It should log more about the actual exception. -- 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: Mailman3-Web lots of database queries

by Abhilash Raj

On Thu, Nov 22, 2018, at 2:14 AM, Stefan Tatschner wrote: > On Sun, 2018-11-18 at 14:38 -0800, Mark Sapiro wrote: > > No. This is not normal. This is apparently coming from Django qcluster. > > At least it is qcluster that uses the django_q_ormq table, but these > > repeated queries are not normal, at least I don't see them in the sites > > I administer. > > These calls are normal, since qcluster polls the database at a high > rate: > > https://django-q.readthedocs.io/en/latest/configure.html#poll > > Fortunately this setting can be reduced, but yeah, polling happens > though. So, if you are using Django's ORM to keep the task states in Django Q, this is bound to happen depending on how frequently do you run tasks. In Hyperkitty, we have some minutely tasks, which means the polling is going to be high. You can however, configure Django Q to store the tasks outside of database in a better high-speed in-memory database like Redis for example[1] for queuing the tasks. Other options like MongoDB, Amazon SQS is also available. [1]: https://django-q.readthedocs.io/en/latest/configure.html#redis > > Stefan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

7 years

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

by Marvin Gülker

Hi, Am 11. Dezember 2019 um 09:55 Uhr -0800 schrieb Mark Sapiro: >Here's a revised script: [...] >Now we expect to see the hash of each message-id followed by the >message-id followed by the exception for the offending message. Success! This time it crashes with the expected exception. I've attached the shell transcript. As expected, it's a spam message. I've uploaded the offending file here for you to look at: <https://ftp.secretchronicles.org/misc/Q5PQZI4QEE4C42XNZMXESSKDCSZBUT4T> This way I don't risk getting caught by spam filters. I'm going to put that down quickly again, though, I don't want to distribute spam messages. Now that the problem is identified, I'm going to purge it from both database and file system. Thank you for your help. If you need any further information for debugging the problem, please tell me. >As to why you didn't receive owner notices about the held spam, perhaps >they were spam filtered or somehow otherwise lost. Maybe. I'll ensure I update quickly when the new Ubuntu LTS comes out to get that functionality. Installing Mailman not via the repos is not really an option for me; this list is for a hobby project and should run with as low maintenance effort as possible (i.e. automatic updates). Thanks a lot. Marvin -- Blog: https://mg.guelker.eu

6 years

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Dadgar

On Feb 15, 2021, at 10:14 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. >> >> The resulted in a broken web interface. >> >> Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. >> >> Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. >> >> Anyone got a solution to this? > > > From the tracebacks it looks like Django is broken. I would suggest > starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ > aside and create a new venv > > virtualenv /opt/mailman/mm/venv/ > > and then activate it and pip install everything. Ok, that worked. THANK YOU. My lists are back up. The CPUs getting pounded by some failing process is back, though. I’ll post about that separately. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

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

by Peter Münster

On Wed, Jan 31 2018, Mark Sapiro wrote: >> I have verp_delivery_interval = 10 ... > > Which says only every 10th message will be VERPed. You want > verp_delivery_interval = 1 to VERP every message. Hi, Why? The smtp relay host would get much more outgoing messages. With verp_delivery_interval = 10, only 10% of the messages would be personalized. Shouldn't this be enough to detect sooner or later, that a recipient address is no more valid? Or is it important, to detect such failure immediately? > The message does appear in the mail log, but until the issues below are > fixed, even if Mailman receives it, you won't see it. Ok. For now, I could do a grep of the syslog messages of Postfix, for example once per month, to check for DSNs. > They should be processed by Mailman and scored as bounces for the > recipient if recognized and forwarded if not (depending on settings), > but they currently are only stored. Ok. >> The question for me is: does the remote MTA needs a fix (i.e. the >> Message-ID is required by some RFC), or mailman (i.e. a DSN without >> Message-ID should be acceptable)? > > I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. Thanks! That means, that I won't need to teach Postfix to add a Message-ID to the DSNs. :) Kind regards, -- Peter

7 years, 10 months

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

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210530 09:19]: > Mark Sapiro writes: > > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > > > Membership adapter is a Mailman 2 feature that allowed use of an > > > external membership database (such as a corporate LDAP system). I > > > thought it was ported to Mailman 3 but maybe not. > > > Actually, it's not quite that simple. Mailman 2.1 defines a > > MemberAdaptor class, [...]. > > The Mailman 3 analog of this is the IMember interface defined in > > mailman/interfaces/member.py and implemented in mailman/model/member.py > > OK, but for Andi it is "simple" in the sense that he doesn't have an > existing MemberAdapter, so the plan is "Implement the IMember interface". 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). Whoever subscribes by mail needs some admin action, or some cron job, or is unsupported - for my case the main interface is the web interface, not the email commands. That of course would imply that e.g. cleaning up mailing lists happens by a cron job with rest, but why not? Andi

4 years, 6 months

[MM3-users] Re: multiple sites on a mailman3 server question

by David Newman

On 12/28/21 6:15 PM, William Oliver wrote: > So, I have successfully installed mailman3 and it's working great. > However, the way it works now, if someone goes to the domain website, > he or she will get the mailman page. I'd prefer that it work something > like: > My > www.example.com goes to a home page > lists.example.com goes to the mailman3 page > mail.example.com goes to a roundcube page > > > I'm using nginx I'd asked about this a few weeks ago for a MM3 host running Ngnix with a few virtual domains, one of which runs Roundcubemail as its default. Mark Sapiro suggested the following, and it seems to be working OK. You'll need these lines in the Nginx config file for each virtual host you define. # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff dn

3 years, 11 months

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

by Marcus Bautze

Hi, Am 07.06.2024 um 06:22 schrieb Mark Sapiro: > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "Thank you, archiver is now starting. Now there's another > problem:". Does this mean messages are being archived in HyperKitty or > are they accumulating in (I think the Debian path is) > /var/lib/mailman/archives/hyperkitty/spool/? They are in /var/lib/mailman3/archives/hyperkitty/spool/, i doesn't find them in the HyperKitty-archives. > At > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > you say "The Keys are in mailman-hyperkitty.cfg and mailman-web.py > and this are the same Keys." To be clear, in mailman-web.py the key is > quoted and in mailman-hyperkitty.cfg it is not. E.g., in > mailman-hyperkitty.cfg > > api_key: Some_key here is the key unquoted: api_key: *** > > and in mailman-web.py > > MAILMAN_ARCHIVER_KEY = 'Some_key' here's the Key quoted: MAILMAN_ARCHIVER_KEY = '***' > > What are your versions for mailman-hyperkitty and HyperKitty? > HyperKitty >= 1.3.5 is incompatible with mailman-hyperkitty < 1.2.0 > and if I recall corectly, at least one Debian package was shipped with > this incompatibility > i found: python3-django-hyperkitty 1.3.7-1 python3-mailman-hyperkitty 1.2.1-1 mailman3-full 3.3.8-2~deb12u1 (no other hyperkitty-related packages) -- Marcus Bautze marcus(a)mbautze.de

1 year, 6 months

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

by Odhiambo Washington

On Wed, Mar 1, 2023 at 6:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/28/23 21:33, Odhiambo Washington wrote: > > > > Now that I have the error message - mail was generated at 0600hrs - what > > should I grep for in mailmanweb.log to ascertain when the cron job > started? > > > You could look in /etc/crontab to see what time the cron.monthly jobs > are run or you could look in syslog for 'cron\.monthly'. > In FreeBSD we have the /var/log/cron. Mar 1 00:00:00 gw /usr/sbin/cron[66206]: (mailman) CMD (/opt/mailman/mm/bin/django-admin runjobs monthly) So the job was started at 00:00, and the email was generated at 06:00: 2023-03-01 06:00:52 1pXCi4-000N2h-2D <= mailman(a)gw.kictanet.or.ke U=mailman P=local S=1466 T="Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly" from <mailman(a)gw.kictanet.or.ke> for mailman That is 6hrs and the lock was still there. Given that my search engine is whoosh and my archive is heading to 3GB, I should probably try setting the value to 10hrs for a start? PS: Is there any documentation (for laymen) on how to set up an alternative search engine for MM3? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Joel Lord

On 11/23/2020 10:48 PM, Mark Sapiro wrote: > On 11/23/20 7:22 PM, Mark Dadgar wrote: >> >> I also believe that it’s common for unsophisticated users to just start marking list emails as spam stop seeing them instead of figuring out how to unsubscribe. Which really sucks for everyone else. > > > Several servers I'm involved with managing are subscribed to Yahoo's > feedback loop (go to https://help.yahoo.com/kb/postmaster and select > "Complaint Feedback Loop"). Reporting list mail as spam is one way to > get quickly removed from a list. However, this is a bit complicated > because the "report spam" button in Yahoo's web mail UI is right next to > the "delete" button, so some reports are accidents. > I've done the same thing, but Yahoo is pretty good at sanitizing their report to make it difficult to impossible to tell who actually needs to get ejected. I added "Sent to %(user_name)s at %(user_address)s" to the footer and while they'd generally get the user_address wiped out, the user_name would generally survive. And because Yahoo's UI is flawed as Mark pointed out, with the delete and spam buttons adjacent, I'd usually give people a couple chances before I'd airlock them. -- Joel Lord

5 years

[MM3-users] Re: Problems with shunted Mails

by Stephan Krinetzki

Mark Sapiro wrote: > > One of the list's regular members has no associated address record. I > don't know how this can happen. That doesn't sound good. When something is unknown, that's never good. > You could find the member with mailman shell, e.g. > mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> for mbr in m.regular_members.members: > ... if mbr.address is None: > ... mbr.subscriber > ... mbr.user > ... mbr.user.addresses > ... mbr.user.preferred_address > ... Yupp, this returns two entries (or better: User Objects?) > You might be able to fix this with something like > >>> for mbr in m.regular_members.members: > ... if mbr.address is None: > ... mbr.address = mbr.user.preferred_address or > member.user.addresses[0] > ... > >>> commit() This fix didn't worked. It returned a "Index out of bounds" exception. Instead, we have deleted the corresponding entry in the database. It should be possible to find it this way: select * from member where list_id = 'list.lists.example.com' AND address_id IS NULL; After deleting the row, the list works again.

3 years, 7 months

[MM3-users] Re: REST API authorization failed

by Axel Rau

Hi Mark, thanks for your answer. > Am 08.01.2022 um 23:07 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Is the password unquoted in mailman.cfg as > > admin_pass: ??? yes. > > and quoted in settings.py as > > MAILMAN_REST_API_PASS = '???‘ yes. > > Does the `mailman info` command report what you think for REST credentials? yes. > > To you get an appropriate JSON response from > > > wget -O- --user restadmin --password ??? http://localhost:8001/3.1/lists <http://localhost:8001/3.1/lists> I used curl: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# curl -v -u restadmin:??? http://localhost:8001/3.1/lists * Trying 127.0.0.1:8001... * Connected to localhost (91.216.35.42) port 8001 (#0) * Server auth using Basic with user 'restadmin' > GET /3.1/lists HTTP/1.1 > Host: localhost:8001 > Authorization: Basic cmVzdGFkbWluOnc2cmtuQXpJZmVRc1o4WnlkMFpBcmNjcm55OA== > User-Agent: curl/7.80.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 401 Unauthorized < Server: gunicorn < Date: Sun, 09 Jan 2022 13:51:43 GMT < Connection: close * Authentication problem. Ignoring this. < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" < content-type: application/json < vary: Accept < content-length: 77 < * Closing connection 0 {"title": "401 Unauthorized", "description": "REST API authorization failed“} - - - I see "Server: gunicorn“, does this mean, I must install gunicorn? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 11 months

[MM3-users] Re: mailman2 import not working

by Abhijith PA

On 29/07/20 10:38 pm, Mark Sapiro wrote: > On 7/29/20 9:33 AM, Abhijith PA via Mailman-users wrote: >> >> ------------------------------------------- >> mailman create -o <foo(a)example.com> foo-bar(a)lists.example.com >> mailman import 21 foo-bar(a)lists.example.com path/to/config.pck >> ------------------------------------------- > > > You don't need to specify an owner for `mailman create`. The owners will > be imported. Ok, noted. >> After everything done tried a test mail, but didn't reach any of the >> inbox though mail is archived. mailman.log says message is accepted >> >> ACCEPT: <FEE2E515-C054-41E6-9853-744D3312A137(a)xxxxxx.org> >> Nothing after this. > > It is surprising that no exception/traceback/SHUNTING message(s) are > logged. That would seem to say that Mailman's `out` runner is not running. When I restarted mailman. I got, Jul 29 16:58:21 2020 (14473) SHUNTING: 1596041901.2833998+efbeb949a9c248bae23ea6bcc644450f497a4d8d > I think Mailman's var/ directory in the Debian package is > /var/lib/mailman3/, so what does `ls -aR /var/lib/mailman3/queue` show? > Is there a .pck file either in shunt/ or in out/? There is many .pck files in /var/lib/mailman3/queue/shunt and /var/lib/mailman3/queue/out. And a lot of .psv files in /var/lib/mailman3/queue/bad > what does `ps -fwwu list` show? There should be a lot of runner > processes. Is there one with argument --runner=out:0:1? > Yes. I can confirm. --a

5 years, 4 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

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

8 years, 4 months

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

by Brian Carpenter

On 4/19/20 4:38 PM, Mark Sapiro wrote: > On 4/19/20 1:21 PM, hansen(a)rc.org wrote: >> We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? > > We are not seeing an issue like this on either lists.mailman3.org (this > list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) > > What are you seeing in web server logs? > I concur with Mark. I am not seeing any such behavior on none of my MM3 servers. One server we were having similar problems and that was due to a bunch of bad behaving indexing bots (semrush, ahrefbot) hammering the server. So definitely check your web server log. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 7 months

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

by Andreas Schamanek

On Sat, 25 Mar 2023, at 17:32, Mark Sapiro wrote: > On 3/25/23 10:01, mike-mailman(a)earth.li wrote: >> >> This seems like maybe its a CSS issue? The class of the held-message-modal >> is "modal fade show" but I am not sure where that is or should be defined >> (or even if I'm looking at completely the wrong thing. >> >> Anyone able to suggest where to look? > > This is bootstrap. See > https://www.w3schools.com/bootstrap/bootstrap_modal.asp > > One possible issue is if you have older bootstrap cached in your browser it > could cause problems. It's unlikely considering you've tried different > browsers, but try clearing your browser cache. I had the exact same issue. As you guessed, Mark, it was related to bootstrap, though not from the browser cache but a mixup of versions served by the server. Also thanks to your research, Mike, I found that my Apache server has Alias /mailman3/static /var/lib/mailman3/web/static /var/lib/mailman3/web/static included a directory "postorius" which served bootstrap.min.css v3.3.5 whereas on my server v4.0.0 is included in python3-django-postorius 1.3.4-2+deb11u1 cd /var/lib/mailman3/web/static mv postorius postorius.bak ln -s /usr/share/python3-django-postorius/static/postorius fixed it for me. There's also a Debian bug report for it: https://bugs.debian.org/1010273 -- -- Andreas :-)

2 years, 8 months

[MM3-users] Re: Template for Password Reset Email

by Mark

On 2024-11-14 23:58, Mark Sapiro wrote: > On 11/14/24 13:57, Mark wrote: >> Most message emails (such as the Welcome email) all arrive in French, >> but not the Password Reset email (shown below) - it arrives in >> English. > This message comes from django-allauth. there is a French message > catalog for it. These are in > site-packages/allauth/locale/fr/LC_MESSAGES and should be good. You > can always run `django-admin compilemessages` to update all the .mo > files for all the projects. I can see the French text for the "Password Reset Email" in the django.po file. And running the compilemessages command reports the "django.po" for French is okay and up to date. Should I be recompiling the ".mo" file? cd /opt/mailman/venv/lib/python3.11/site-packages/allauth (venv) ... $ django-admin compilemessagespwd ... File “/opt/mailman/venv/lib/python3.11/site-packages/allauth/locale/fr/LC_MESSAGES/django.po” is already compiled and up to date. ... > However, the issue is probably that Django doesn't get the language > context from the list's preferred language. In fact, the password > reset is not in a list context at all. See > https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… > for how it determines the language to serve. I'm afraid I don't understand the Django documentation. It seems to be referring to site-wide settings for language, and not "per list".

1 year

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Now I do have a running instance, too. Seems my error was to do all of the installation via ansible from the start and I wouldn't seen many things failing: - missing wheel - missing gcc The link to the virtualenv user guide seems to be broken. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 9 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > First, we are not silently dropping this message. We are rejecting it at > LMTP time so the sender should be notified. Sure, but you know how users are about being told that their broken MUAs are spewing crap into the Internet. And most of them will get their mail back and will have no idea how to diagnose what the problem is, let alone repair it. > Then the broader question is should we accept all messages with > defects, almost all of which are spam, or only certain defects and > which ones. No (for the reason given), yes, and "it depends". This one I think we can pass through by default. Some lists might want to pass some of the defects that are characteristic of spam. For example, lists for projects developing MUAs in Japan. I regularly got mail with unencoded Japanese in Subject, display names, and occasionally Date at one point in time. > I note that Apple has now released Mail 16 so maybe they've fixed this. > My macs are still on Big Sur, so I can't test this. I have a Mac on Monterey but I haven't switched to it yet, and I'm not a regular user of signed mail and I've never ever used Apple Mail. I'll probably need a bit of handholding to set up a test. Steve

3 years, 7 months

[MM3-users] Re: URLs in moderation messages

by Odhiambo Washington

On Fri, Mar 3, 2023 at 8:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > 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. > Are these proposed VirtualHost configs independent of whether one is using gunicorn/mod_wsgi/uwsgi? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: MM2 -> MM3 Migration: listinfo page

by Odhiambo Washington

On Wed, Mar 8, 2023 at 6:16 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/8/23 02:21, Odhiambo Washington wrote: > > > > For those who have migrated from MM2 to MM3, does someone have an > elegantly > > modified listinfo page they are willing to share? > > I remove the MM 2.1 list, but leave the archives. Instead of having any > kind of listinfo page, I put a redirect in Apache for each migrated > list. E.g. > > RedirectMatch permanent /mailman/listinfo/mailman-users(/.*)?$ \ > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > > For archives, I add a note to archives/private/<listname>/index.html. > See https://mail.python.org/pipermail/mailman-users/ for an example. > This works for public archives, but not for private archives because > there is no longer a list to use for private archive authentication. I'd rather not touch the MM2.1 domain because references have been made to it in publications. What I am struggling with is the listinfo.html file: ``` https://lists.kictanet.or.ke/mailman/listinfo/kictanet ``` I am struggling to add reference to the MM3 subscription link user the " Subscribe to KICTANet by filling out the following form:" The HTML code to insert there beats me :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Hyperkitty error - not archiving

by Odhiambo Washington

On Sat, Jul 26, 2025 at 8:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/25 10:35 AM, Odhiambo Washington via Mailman-users wrote: > > > > I had examined the message using 'mailman qfile', but did not see > anything > > obvious. > > There were 3 files inside the spool/ directory. > > I have just checked again and they are no longer there. > > If the files `disappeared`, they were eventually successfully delivered > to HyperKitty. If you made no changes to mailman-hyperkitty.cfg, there > was probably some transient network issue that caused the initial error. > Most likely. Another thing I have seen, inside /etc/mailman3/ root@list:/etc/mailman3# ls -al total 40 drwxr-xr-x 3 mailman mailman 4096 Jul 26 10:52 . drwxr-xr-x 110 root root 12288 Jul 26 07:17 .. -rw-r--r-- 1 mailman mailman 948 Jul 25 02:48 mailman.cfg -rw-r--r-- 1 mailman mailman 352 Oct 25 2023 mailman-hyperkitty.cfg drwxr-xr-x 2 mailman mailman 4096 Jul 26 03:11 __pycache__ <===== Is the presence of this directory expected? -rw-r--r-- 1 mailman mailman 4971 Jul 26 03:10 settings.py -rw-r--r-- 1 mailman mailman 863 Jul 25 04:14 uwsgi.ini -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 2 weeks

[MM3-users] Re: Unknown templates being used

by Brian Carpenter

On 2/14/21 1:31 PM, Mark Sapiro wrote: > On 2/14/21 5:44 AM, Tom Stoddard wrote: >> 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. > So you should be getting your support from EMWD. > > >> 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.) >> >> Thexxxxxxxxxx(a)xxxxxxxxxx.org list has 1 moderation requests waiting. >> >> >> Held Subscriptions: >> User:xxxxxxxxxx@gmail.com >> >> Please attend to this at your earliest convenience. Yeah, the funny thing here Mark is he is not asking for support for the interface. He is wanting to know why isn't there a way for List Owners to modify moderation notices. It had nothing to do with Affinity. BTW - I told this client CLEARLY there was no template for that notification but he was welcome to join the list to ask for the source of it since I did not know. Geez. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: MM3 to MM3 migration

by David Newman

On 1/31/23 2:01 PM, Mark Sapiro wrote: > On 1/31/23 13:34, David Newman wrote: >> >> Is this really as simple as building the new server, creating the >> same lists on the new server, and rsync’ing the archives from the old >> server? If not, how to do the migration? > > > If you want to mirror the entire installation, you can dump the > databases off the old server and import them to the new server. > Depending on the installation, everything may be in one database or > there may be separate ones for mailman core and mailman web. This is a > little tricky because some of the tables have to do with Django stuff. > > To do only selected lists is much more difficult and there are no > scripts that I am aware of. > > HyperKitty can dump a list's archive as a mbox which could then be > used as input to hyperkitty_import on the new server to move archives, > but there are no similar scripts to dump list settings, users, > memberships, etc. in a format that can be imported. Thanks for this. Would I need to create the lists first on the new server before restoring databases and running hyperkitty_import? Also, I'm unclear about there not being scripts for settings, users, etc. –– isn't that stuff in the mailman database? Thanks! dn

2 years, 10 months

[MM3-users] Re: Memory footprint

by Richard Shetron

some systems also support the sar command (system activity report). If you have it read the manpages to see all the options as there are many. When looking for performance issues/problems that aren't real easy to find I like to just let 'vmstat 5' run in a window and take a look occasionally, particularly when things seem slow. I prefer the 5 second readings to see more about general trends. On 4/11/2017 8:33 PM, Mark Sapiro wrote: > On 04/10/2017 02:25 PM, David Krantz wrote: >> Hi. >> >> Now running mailman 3 I am a bit surprised that the memory footprint >> is so large. I count to 13 processes with each a virtual space of >> 160-250MB and a reserved space of about 50MB each. Not much, but quite >> much to run on smaller cloud instances which generally have limited >> memory. This is (a lot) more than the corresponding postgres >> installation uses, >> >> Is this normal? > > > Those numbers seem "normal" but you really have to look deeper to > understand if you just have a bunch of processes sitting in memory > because the memory is available and nothing else wants it, or if there's > real memory contention going on. > > The article at <https://wiki.list.org/x/4030711>, while written about > Mailman 2.1, has some general information which may be of interest. > >

8 years, 8 months

[MM3-users] Re: No DBA password when installing Mailman3 with remote database server

by Markus Ludwig Grandpré

> but apparently dpkg wants to > create databases for Mailman and Mailman Web. During the installation process dpkg creates not only a database and a database user with approriate permissions, but also many tables. Dpkg allows to skip database configuration. Is there routine or skript to create database, database user and all required tables after the installation process has finished? Best regards, Markus On 31.10.22 18:52, Mark Sapiro wrote: > On 10/31/22 07:04, Markus Ludwig Grandpré wrote: >> Dear Mailman3 list, >> >> I try to install the Mailman3 software 3.3.3-1 on a Debian 11 system >> with a remote Postgres database server. During the installation >> process dpkg is asking for the DBA password that our DBA team would >> not provide to me. So what can I do? > > > This is really a question for Debian, but apparently dpkg wants to > create databases for Mailman and Mailman Web. You will need to get your > DBA team to create these databases (probably named `mailman` and > `mailmanweb`) and a Mailman user (probably `list`) with all access to > these databases and probably manually configure the `[database]` section > of mailman.cfg and `DATABASES` on Django's settings > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, Tel: ++49 7531 88 4342

3 years, 1 month

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

by Darren Smith

As for the traceback - I'm assuming it's from postorius, as this happens when attempting to load the held messages in the Postorius UI. On Mon, Apr 23, 2018 at 3:29 PM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > "It's in Mailman's database in the 'message' table." > > I can see the message table - is there a way to see where it is marked as > "held"? All I'm seeing in that table is id, message_id, message_id_hash, > and path. > > I'm wanting to be able to query for held messages for a given mailing > list, as there are currently over 98,000 entries in the message table. > > -Darren > > > On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/23/2018 01:31 PM, Darren Smith wrote: >> > So it appears that there was a message sent to one of our mailing lists >> > that was put into the held message queue. However, when attempting to >> go to >> > the message to do the moderation, the web page returns and Error 500. >> > >> > Looking in the mailman log, I found this: >> > >> > Apr 23 14:21:02 2018 (17878) REST request handler error: >> > Traceback (most recent call last): >> > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line >> 137, >> > in run >> > self.result = application(self.environ, self.start_response) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> database/transac >> > tion.py", line 50, in wrapper >> > rtn = function(*args, **kws) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/wsgiapp.py" >> > , line 214, in __call__ >> > return super().__call__(environ, start_response) >> > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", >> > line 227 , in __call__ >> > responder(req, resp, **params) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 167, in on_get >> > resource = self._make_collection(request) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in _make_collection >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/helpers.py" >> > , line 159, in <listcomp> >> > for resource in collection] >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 157, in _resource_as_dict >> > resource = self._make_resource(request.id) >> > File >> > "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/ >> rest/post_modera >> > tion.py", line 100, in _make_resource >> > make_header(decode_header(resource['subject']))) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, >> in >> > make_he ader >> > h.append(s, charset) >> > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, >> in >> > append >> > s = s.decode(input_charset, errors) >> > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: >> > illegal multibyte sequence >> > >> > It LOOKS as if there might be a character in the email somewhere - >> possibly >> > in the subject or sender fields? - that is somehow unexpected. >> >> >> It appears that the Subject: header is RFC 2047 encoded and there is an >> encoded word with charset gb2312 that contains an invalid encoding. >> >> The message is apparently defective, but this kind of defect shouldn't >> cause a 500 error. >> >> I can't tell for sure from the traceback if this is Postorius or some >> other application accessing the REST api. Is it Postorius or something >> else? >> >> >> > I am attempting to find the held message - can someone point me where I >> can >> > go to see the message so that I can see what might be causing the >> problem? >> >> >> It's in Mailman's database in the 'message' table. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > >

7 years, 7 months

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

by Ugnius S

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

6 years, 3 months

[MM3-users] Re: Importing mbox file into MM3

by Mark

On 2023-06-23 12:19, Mark Sapiro wrote: > On 6/22/23 7:00 PM, Mark wrote: >> Hi All >> >> I'm trying to import a large mbox file from a MM2 list into a new list >> on MM3. >> >> The new MM3 list has 3 test emails in its archive. >> ... >> The import or rebuild has failed as it's just rebuilding the existing >> archive of the 3 test messages. >> >> What am I doing wrong? > > > Presumably, the 3 test emails are newer than the messages in the > archive .mbox. The default for hyperkitty_import is to not import > messages older than the newest message in the existing archive. > You need to specify something like `--since='1970-01-01'` on the > hyperkitty_import command to import these older messages. > Thanks Mark. That looks more promising. It's been chugging away now for 3 hours with only 4 errors reported so far. # cd /usr/share/mailman3-web/ # python3 manage.py hyperkitty_import --since='1970-01-01' -l LISTNAME@DOMAIN /home/mark/tmp/LISTNAME.mbox "Failed adding message ......(a)mail.yahoo.com>: A string literal cannot contain NUL (0x00) characters". The mbox file is about 3 GB. The errors look like they're for messages that aren't kosher (maybe misplaced "From"s in replies). I can live with a few missing messages. Back to watching the spinning pipe. Chug chug. Cheers Mark

2 years, 5 months

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

by Simon Liebold

Am 28.05.2017 um 22:24 schrieb Mark Sapiro: > 'Delete this message' is in the 'message' view. "Delete this thread" is > in the 'thread' view. Now found the message view. Thanks. > HyperKitty requires Django<1.11. The comment in the requirements in > setup.py implies this is only a django-haystack requirement > > "Django>=1.8", > # Don't upgrade to 1.11 until django-haystack supports it: > # https://github.com/django-haystack/django-haystack/pull/1499 > "Django<1.11", > > but since it works for me with Django 1.10, you might want to try that. OK, I was still running an RC version. Silly me. > In particular, this looks like Django 1.11 bug > <https://code.djangoproject.com/ticket/27975>. Which was closed in the release version that I initially upgraded to (1.11.1). Now, I get to see the confirmation view and upon confirming I see these (luckily different) errors like below (same with Django 1.10): Could not delete message P2GJLK4JPDU2K6ZKBSDUWASF2TVHCJTT: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist") Could not delete message 4I2TRZTFXMMH2XRQAS73IAEIYROFE5YM: (1146, "Table 'mailmansuite.django_q_ormq' doesn't exist") True, this table doesn't exist in the database. It isn't created by python manage.py migrate. The error is served with HTTP-200. No stack trace in mailmansuite.log. Headscratching: Simon

8 years, 6 months

[MM3-users] Re: multiple sites on a mailman3 server question

by William Oliver

On Tue, 2021-12-28 at 18:23 -0800, David Newman wrote: > > > > [snip] > > I'm using nginx > I'd asked about this a few weeks ago for a MM3 host running Ngnix > with a > few virtual domains, one of which runs Roundcubemail as its default. > > Mark Sapiro suggested the following, and it seems to be working OK. > You'll need these lines in the Nginx config file for each virtual > host > you define. > > # begin mailman3 stuff > > location /static/ { > alias /opt/mailman/web/static/; > } > [snip] No joy. This just makes it kind of work as the mailman interface when it gets rewritten. My problem is that the url is getting referred to domainname/mailman3/lists even when I don't want it to. Adding these changes just (partially) loads the mailman3 interface when it gets rewritten. What I'm trying to figure out is where uwsgi yanks control from nginx and does the rewriting. Pulling that proxypass stuff out will stop mailman3 from coming up, and adding it allows mailman3 to show its interface, but the address gets referred regardless. Somehow I need to tell uwsgi to ignore www.domain.com *or* somehow tell nginx not to push it to port 8000. But I don't see where nginx is getting told to go to 8000 in the www.domain.com section. billo

3 years, 11 months

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

by Nelson Strother

Well, this is using the default libsqlite 3.34.1 . One improvement is to use write-ahead logging: mailman@localhost:~$ sqlite3 /var/tmp/mailman/data/mailman.db SQLite version 3.34.1 2021-01-20 14:10:07 Enter ".help" for usage hints. sqlite> PRAGMA journal_mode = WAL; wal sqlite> This setting is persistent, and based on a small sample this seems to dramatically speed up the completion of root@localhost:~# systemctl stop mailman ## consumes <2 minutes with journal_mode = WAL; root@localhost:~# ## instead of up to 20 minutes with the default journal_mode = delete But this does not make a big change the completion time for: root@localhost:~# systemctl start mailman Since there is no point in busy waiting when running on a processor with only one core (as this virtual server), the next setting that I would like to try is change the sqlite busy_timeout from the default of none to 1 or 2 seconds, e.g.: sqlite> PRAGMA busy_timeout = 2000; 2000 sqlite> However, this setting is not persistent, and thus needs to be applied to each connection (i.e. tens of database connections are made during `systemctl start mailman`). I have not yet found where to insert this directive in mailman's database wrapper for SQLite. Might someone who has read more of the source be able to offer me a clue? On 6/8/23 15:47, Mark Sapiro wrote: > I would look to your database manager for the issue.

2 years, 6 months

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

by Helio Loureiro

Hi, And here we have it: (venv) mailman@new=server ~ (v3.3.9)> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK tl;dr: it was the database. So the django was spitting out absolutely horrible traceback errors to diagnose the issue. I modified the code to print the query and then raise exception (what is expected from an error, not only "I just failed, sorry do whatever"). Then I got the query and tried manually. And it failed. (venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email...Error running query: b'*ALTER** TABLE `account_emailaddress` DROP INDEX `email`'* Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) [...] (venv) mailman@new-server ~ (v3.3.9) [0|1]> mysql -umailman3web -p -h localhost mailman3web Enter password: Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 32 Server version: 10.6.12-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [mailman3web]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2013 (HY000): Lost connection to server during query MariaDB [mailman3web]> *ALTER TABLE `account_emailaddress` DROP INDEX `email`;* ERROR 2006 (HY000): Server has gone away No connection. Trying to reconnect... Connection id: 32 Current database: mailman3web ERROR 2013 (HY000): Lost connection to server during query So I looked to the mysql error logs and searched Internet for the issue. It recommended to run a "mysql_upgrade", which failed with another error: root@seliius26224 /e/mailman3# mysql_upgrade -u root --force Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.engine_cost Error : Table 'mysql.engine_cost' doesn't exist status : Operation failed mysql.event OK mysql.func OK [...] sys.x$wait_classes_global_by_avg_latency OK sys.x$wait_classes_global_by_latency OK sys.x$waits_by_host_by_latency OK sys.x$waits_by_user_by_latency OK sys.x$waits_global_by_latency OK Phase 4/7: Running 'mysql_fix_privilege_tables' ERROR 1932 (42S02) at line 477: Table 'mysql.innodb_index_stats' doesn't exist in engine FATAL ERROR: Upgrade failed I searched again the Internet and found a fix: https://stackoverflow.com/questions/37856155/mysql-upgrade-failed-innodb-ta… Now migration is progressing. Thanks for all the patience and support. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Tue, 19 Dec 2023 at 15:23, Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/19/23 3:11 AM, Helio Loureiro wrote: > > Hi, > > > > No luck :( > > > > (venv) mailman@new-server ~ (v3.3.9)> *pip install -U > > django-allauth==0.58.0* > > You need to install django-allauth<0.58.0 as in > ``` > pip install django-allauth\<0.58 > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to helio(a)loureiro.eng.br >

1 year, 11 months

[MM3-users] Re: How to delete large numbers of held messages

by lists＠g1fef.co.uk

Mark Sapiro wrote: > On 4/21/22 14:56, Chris via Mailman-users wrote: > > We had a mail loop on one of our lists and ended up with over 51k messages in pending (held due to post not form a list member) > > Trying to delete them from the web UI will take forever, as the largest pagination you can view is 200 at a time. > > Tried to delete them from the Python interactive shell, but it looks like the API times out after a while. > > Is there another way to delete all these unwanted held posts? > > I suggest the following in mailman shell > $ bin/mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> from mailman.app.moderator import handle_message > >>> requestdb = IListRequests(m) > >>> for id, type in requestdb.held_requests: > ... if type == RequestType.held_message: > ... handle_message(m, id, Action.discard) > ... > >>> commit() Thanks for the reply, unfortunately that gives an error: Traceback (most recent call last): File "<console>", line 1, in <module> TypeError: cannot unpack non-iterable _Request object

3 years, 7 months

[MM3-users] Re: Templates do not work

by Eggert Ehmke

It seems my apache vhost settings are messed up. To access the postorius page, I have to use URLs like this: https://lists.[1]tld_/mailman3/mailman3/lists/_ That does not look right, and maybe is the cause of my problem. There are very few guides to set up apache virtual hosts with mailman virtualenv installation. Any hint? Am Donnerstag, 28. April 2022, 19:02:42 CEST schrieb Mark Sapiro: > On 4/28/22 02:50, Eggert Ehmke wrote: > > I created some templates in Postorius to get > > personalized notifications when there are > > moderator requests. The notifications I get seem to > > be the standard texts. When I look into mailman/ > > mm/var/templates > > the directory is empty. Nevertheless, the templates I > > create in Postorius seem to be stored (where?), they > > just do not work. > > As Steve said the templates are stored in the database. > > I suspect the issue is and incorrect value for > `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to > construct the URI to retrieve the template. The URI is stored in the > `template` table in the database. It is normally just `http(s)://host.name/` > > If this is the issue, after correcting the setting and restarting the > web service, you will need to delete and re-enter the template in > Postorius to correct the `template` table entry. -------- [1] https://lists.ftv-spandau.de/mailman3/mailman3/lists/

3 years, 7 months

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

by Odhiambo Washington

On Sun, Feb 5, 2023 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/5/23 01:13, Odhiambo Washington wrote: > > > > So in my case, I should at least increase the value of > > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? > In the last episode, I did set: HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE = 3600 However, the same error has reared its head again. > It probably isn't even set in your case and defaults to 900 if it isn't > set. Yes, you can set it to a larger value. If your archive search > engine is woosh and your archive is even moderately large, 1800 probably > isn't nearly enough. There was no indication of timing in your OP, but > you should determine when that cron job started and when the error was > reported. Now that I have the error message - mail was generated at 0600hrs - what should I grep for in mailmanweb.log to ascertain when the cron job started? > The difference is the absolute minimum you should set for > HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE, but you should add some margin > to that. > ..so as to get this difference, that I need to set as the _ bsolute minimum_, with some margin? Thanks in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 9 months

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Thomas Ward

Is there a way to oerhaps custom-plugin my way through to set this up as an integration into Core? And specify the custom handler process or such to allow that integration? I see that there are ways to code plugins into existence so it may be a custom-processor plugin or such for this purpose. Replies to threads would still have the corresponding RFC headers and such for replies and would properly get Hyperkitty to index threads properly, but subject munging on this case might be something I would custom-code into the system if that's doable. Thomas On 10/18/23 18:03, Mark Sapiro wrote: > On 10/18/23 14:54, Thomas Ward via Mailman-users wrote: >> >> Is there any way to have Subject based thread tagging, etc.? I ask >> this only because we're trying to thread items for easy ID in a >> system right now that does thread ID tagging in the subject line >> (i.e. "[Test-0000004] Something" and "Re: [Test-0000004] Something" >> are identified as the same thread, but a brand new message >> "Something" would end up as "[Test-0000005] Something" in the chain >> if it was a new message.) > > > It is not possible with the current design. > > The issue is the tagging is done by Mailman core and Mailman core > knows nothing about threads. >

2 years, 1 month

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I thought I could not configure Mailman, but with Kyle and Mark help and support I could. So, I don't want to be demeaning as you also said but maybe we could try, maybe you can also help, if it turns too complicated I will use mailchimp, but let me try before givin' up, don't you think?? El sáb., 22 jul. 2017 a las 9:01, Simon Hanna (<simon.hanna(a)serve-me.info>) escribió: > On 07/22/2017 03:46 AM, Rafael Mora wrote: > > Can I use it for mailing lists? like MailChimp? > > > > El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > >> On 07/21/2017 06:07 PM, Rafael Mora wrote: > >>> I want to use Mailman to send emails to our customers. > I would highly recommend using a service like MailChimp. > MailChimp has a decent free tier and if you are above that, > I'm not sure if you can handle configuring Postfix the right way. > It's not my intention to be demeaning or anything, but it sounds like > that would be a little too complicated for you... > (I wouldn't want to manage a Mailserver in charge of tens of thousands > of emails per month) > > _______________________________________________ > 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, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

8 years, 4 months

[MM3-users] Re: unwanted chunked delivery

by mm3-omf＠sh.werbittewas.de

Am 07.01.22 um 21:33 schrieb Mark Sapiro: >> nevertheless, we've tried to set it to a high value, but even this >> doesn't change anything in behaviour. > > Right, because chunking isn't arbitrary. Chunking is done by recipient > domain. The addresses are placed in `buckets` by TLD. All `.com` goes in > one bucket; `.net` and `.org` in another; `.edu`, `.us` and `.ca` in a > third, and all the rest in a fourth. thanks for this info. > My question is why is this important to you? See the FAQ article at well, most of these 81 users are handled on our local system, but with different domains and TLDs (mainly 80% .de and 20% .org/.net). therefore we don't see any benefit in chunking here, especially in case 50% of the chunks are unused (.com,.edu/.us/.ca). to simplify our logging-analysis in case of problems it seems beeter for us to have one entry for delivery to list-server and one entry for delivery from there. > https://wiki.list.org/x/4030582 (which is for Mailman 2.1 so it talks > about SMTP_MAX_RCPTS which is what max_recipients used to be called) > which suggests a much smaller number. I understand, why chunking may have benefits perhaps in most situations, so it's set as default, but it would be great, to have the possibility to disable this without patching code, which might get overwritten with an update. omf.

3 years, 11 months

[MM3-users] Re: more about spanish translations

by Guillermo Hernandez (Oldno7)

On 19/2/21 18:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 19/2/21 18:26, Mark Sapiro wrote: >> On 2/19/21 5:09 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> I would like to translate it all, but as said, I cannot find where >>> to do >>> it. I wonder if it's comes from another package as allauth or something >>> like this. >> >> Yes, it does come from allauth, specifically >> allauth/templates/account/email/email_confirmation_message.txt. >> >> The Spanish allauth message catalog is at >> <https://github.com/pennersr/django-allauth/tree/master/allauth/locale/es/LC…>. >> >> I suppose you could submit a pull request to update it. >> >> Or you could just update your local file in your installation. >> > I will do both: first translate locally. Test it, and then see if I > can share it with the rest of the people (and then I will not have to > worry to maintain it when next upgrades come) I went first with the translation in github and the pull request. Let's see if it's approved and then how to upgrade locally. > > Thanks a lot, as always, Mark. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 9 months

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

by Odhiambo Washington

On Sat, May 15, 2021 at 12:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > > total 104 > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > > > I imagined I needed an executable. > > > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass > > > Those are headers for compiling some sass. Possibly you actually have a > `sassc` installed in which case you may need > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > > This change makes the error I was getting to go away. However, I cannot login to manage lists, even after restarting mailman. The error details are here: https://pastebin.ubuntu.com/p/vM2c5WYyJ4/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 6 months

[MM3-users] Re: REST API authorization failed

by tlhackque

On 10-Jan-22 13:30, Mark Sapiro wrote: > On 1/10/22 1:58 AM, Axel Rau wrote: >>> >>> Anyway, the above is saying that restadmin:??? doesn't match what's >>> configured in Mailman core and reported by `mailman info`. Please >>> check carefully that these are the same in both mailman.cfg >>> admin_pass and settings MAILMAN_REST_API_PASS. >> >> Yes, again with password disclosed: >> - - - > ... >> (mailman_33) [root@lists5 /usr/local/mailman3]# grep admin >> var/etc/mailman.cfg >> admin_user: restadmin >> admin_pass: restpass > > Does `mailman info` show the same password? A common issue that may (or may not) be in play here is leading/trailing whitespace and/or non-spacing control characters. It may be worth making the output (& input) use quotes & escaping, where the input should accept non-spacing controls, leading/trailing whitespace, and non-traditional interior whitespace (e.g. nbsp, numsp, NoBreak, tab) only in escaped form. By escaped form, I mean one or more formats like HTML's  , or Python's at https://python-reference.readthedocs.io/en/latest/docs/str/escapes.html When dealing with user quantities, if it looks like a space, it should be a space. And if you can't see it, it shouldn't be there (using escapes to make the invisible visible is fine). ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 11 months

[MM3-users] Re: "Unsubscribe all" button

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/20/22 17:32, Philippe B wrote: > > Would it be possible to add a confirmation screen after you click > > on it? Like: WARNING! Clicking "Confirm" will empty the list of > > all its existing members, regardless of what was entered on the > > previous screen. That operation cannot be reversed. Are you > > absolutely sure that you want no one to be on your list anymore? > > There is a confirmation screen although it is not as strongly worded as > you suggest. I'll go check the issue, but let me say I think a confirmation screen is bad UI here. People who know what they're doing shouldn't have to pay the price of a confirmation screen. I know of at least two universities where they "unsubscribe all" from thousands of class mailing lists every term. Of course they automate that pretty quickly when they get to thousands, but it seems plausible to me that such lists for groups that regularly turn over (nearly) 100% of subscribers are a reasonably common use case. Instead, there should be a check for selected users, either disabling the "unsubscribe all" button itself (if we decide to implement more Javascript in the UI) or presenting the confirmation screen if there are any selected users. Also, at least for native speakers, "Unsubscribe everyone" will probably be a better label for the button.

3 years, 1 month

[MM3-users] Re: SpamAssassin and clamav?

by Jeremy Stanley

On 2024-03-15 18:50:32 -0700 (-0700), Marisa Giancarla via Mailman-users wrote: > On 3/15/24 18:40, Mark Sapiro wrote: > > On 3/15/24 17:52, Marisa Giancarla via Mailman-users wrote: > > > Is there a way to have mm3 use SpamAssassin and/or clamav? > > > Marisa > > > > It would require custom code modification to invoke SpamAssassin > > and/or ClamAV from mailman. It is much better to integrate these > > in the MTA. > > Ok sounds good... A big reason this is the preferred approach is that your MTA, if appropriately configured, can scan incoming messages before deciding whether to accept or reject them into its delivery queue. For messages rejected at receipt, this means legitimate senders whose messages were incorrectly misclassified get useful error messages in the NDR generated by their own mail provider, while spoofed spam and malware doesn't generate backscatter to unwilling victims and put your own server at risk of getting listed as a spam source. If Mailman were in charge of checking for spam or malware, its only options would be to silently drop offending messages (providing no feedback to senders of misclassified messages) or reject them (causing your MTA to generate an NDR which often times ends up either part of a coordinated attack against some victim organization or sitting undeliverable in the queue because that address is at an unreachable domain). These are obviously undesirable, even actively harmful, results. -- Jeremy Stanley

1 year, 8 months

[MM3-users] Re: Google Summer of Docs

by Abhilash Raj

On Sun, Mar 24, 2019, at 11:58 PM, Terri Oda wrote: > > > On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" > <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >Ralph Seichter writes: > > > * Mark Sapiro: > > > > >> > If you post an issue at > ><https://gitlab.com/mailman/mailman/issues>, > > > > one of our GSOC aspirants may pick it up. > > > > > > Done, although I wonder if any GSOC participant would want to write > > > documentation instead of code... ;-) > > > >For their actual, Google-supported, project, Google explicitly > >excludes documentation. > > > > They do for Google Summer of **Code** but they've just announced Google > Summer of **Docs** which sounds really neat and we might want to > participate. They are calling it Season of Docs, happening in winter I think Sept-Dec AFAIK. Yep, we should participate in that, I sent out an email earlier about this too. > > (It's my personal opinion that our docs have really suffered since I > finished my PhD and stopped using them as a warmup exercise when I was > procrastinating on writing my thesis. *grin*) > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 8 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

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

8 years, 4 months

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

by Odhiambo Washington

On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 01:19, Odhiambo Washington wrote: > > Apart from all the defaults in settings.py (derived from gitlab), I also > > have this line: > > LOGGING['handlers']['file']['filename'] = > > '/opt/mailman/mm/var/logs/mailmanweb.log' > > > > Before the New Year releases of MM3, I used to get errors written to this > > file. > > Not anymore after I updated to the New Year releases. > > Another thing that I have realized is that prior to the New Year > releases, > > I would get an error logged to that file and also mailed to me. > > I don't think that I have changed anything in settings,py related to > > logging. > > > Nothing in those releases per se would affect this. This is Django and > django-allauth. Perhaps when you updated the Mailman packages, you also > updated these dependencies. > Which dependencies would those be? When I upgraded, the command I ran was: pip install --upgrade --force mailman mailmanclient postorius hyperkitty mailman-hyperkitty django-mailman3 And how do I find out what is suppressing the logging for the social accounts? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 5:39 PM, Mark Sapiro wrote: > On 10/21/20 12:14 PM, Brian Carpenter wrote: >> >> Well I can't dictate that to my list owners and there is no confirm >> token sent with the moderation notice. Why include this option in >> Postorius when it can't be properly handled? > > Postorius is still a work in progress. The unsubscription policies are > in core and are exposed in Postorius. Certainly the ability to moderate > an unsubscription should be in Postorius, but it isn't yet. We are an > all volunteer project and there aren't that many of us, and perhaps I'm > overreacting, but the tone of some of your recent posts seems a bit > demanding. I apologize. I didn't think I was coming across demanding but I am somewhat exasperated at some of these issues. I have a list owner who is now going to get a moderated request notice everyday that he can't do anything about it. But my question still remains: why is this option in Postorius when it can't be handled properly? Surely the option can be easily removed, right? Is the ability to list (via the pending moderation notices tab) and handle (as in the List owner can decide a moderation response) an unsubscribe moderation request there in Mailman core so that I can properly address it via Affinity? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

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

by Abhilash Raj

On 12/14/22 03:31, Mark Sapiro wrote: > On 12/13/22 10:38, Dan Caballero wrote: >> Hi Mark, >> >> I ran the commands and it took about 35 seconds for the loop to run. >> >> Here's the result. >> >>>>> count >> 4168 > > > So that's at least part of the issue. How does 35 seconds compare to the > length of time to process one moderated message through Postorius? > It seems it has to do with in-efficient lookup of the actual entry in the pendings table which needs to be purged after handling a held message. It scales linearly with how many entries are there in pendedkeyvalue and pendings tables. I was actually browsing through the perf metrics on mail.python.org and found the slowest API response from Core is handling held messages and spent some time last night trying to improve it [1]. The linked MR should significantly reduce the time, although there is more that can be done to make it even better. I haven't had a chance to benchmark my solution yet, but I am hoping it will reduce the latency quite significantly. I'll report on the linked issue [2] after deploying [1] on m.p.o. how much it helped. [1]: https://gitlab.com/mailman/mailman/-/merge_requests/1068 [2]: https://gitlab.com/mailman/mailman/-/issues/1045 -- thanks, Abhilash Raj (maxking)

2 years, 11 months

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

by Alain D D Williams

On Thu, Nov 28, 2024 at 01:04:13PM -0800, Mark Sapiro wrote: > > I did not see this y/day and created the entry in table django_site using SQL. > > This might be the cause of the other problems that we have been talking about. > > > It's not likely that this is the cause. It is fixed - the mail list works. I had forgotten to put the reverse proxy into the Apache config -- this is what led to the many, rapid retries. I had a problem for a while in the nothing to one particular list was sent to users. This had several users who's delivery status was 'disabled' (correctly, as on the old instance). If was only after a lot of fiddling (trying to delete from the list) that it started to work for the others. There are still rough edges, eg trying to delete a list member gives a server error. In /var/log/mailman3/mailman.log I see a 404: "DELETE /3.1/lists/chat.bray.phcomp.co.uk/member/a.chentouf(a)hotmail.com HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.5" I am not to worried about that today, will look at it in the future. Thanks for your help -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/29/21 9:50 AM, Odhiambo Washington wrote: > > 1. Confirmation emails to Users has wrong domain name (example.com!) > > <https://docs.mailman3.org/en/latest/faq.html#id1> > > < > https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… > > > > > > This happens when your reverse (SSL) proxy isn’t setting up the correct > > headers when proxying requests. Fix this by setting the right > > proxy_set_header directives: > ... > > How is this supposed to be mitigated in Apache when using WSGI? > > > > My config: > > > > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > > user=mailman group=mailman > > WSGIPythonHome "/usr/local" > > WSGIProcessGroup hyperkitty > > > You are using mod_wsgi and not proxying at all, so this is not relevant > in your case. > > Are you actually seeing this issue? If so, it might be related to > > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > My issue is related to this, but the documentation referred to is not for the faint-hearted! I can't make head or tails of it. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 2 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 24 jan 2024, om 12:24 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: > Op 23 jan 2024, om 19:09 heeft Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> het volgende geschreven: >> >> On 1/23/24 05:49, Marco van Tol wrote: >>> Small unfortunate twist, this leads to: >>> --- >>> [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... >>> --- >>> I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? >> >> This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. >> There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. >> >> I use the one from the PR, but it requires a substitution `s/force_text/str/`. > > Hi, thanks! Just to double check, do you mean `str` or `force_str` in the substitution? > > I found a comment on this topic regarding django-4 where they advice to use force_str. > https://stackoverflow.com/questions/70382084/import-error-force-text-from-d… Hm, never mind, sorry. I now see the current file already has str() rather than force_text() in it. Marco

1 year, 10 months

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

by Eric Broens

`mailman qfile` on the 5 pck files that were in the /out directory looked OK, although I am not sure if I should have looked at something specific. The bak file disappeared as soon as I stopped mailman. When I started mailman again the name of the bak file had changed, and it changed every time I listed the directory.After stopping and starting mailman once more it didn't appear anymore. There are also 6 files in the shunt directory. I don't know what this directory is used for. For now I have disabled the hourly jobs.I will rebuild the search index for each mailinglist separately since the update_index was apparently killed before it finished. Best Regards,Eric On Sunday, December 13, 2020, 06:18:21 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/13/20 7:11 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > 1.Regarding the repeated access of /archives/api/mailman/urls seems to be related to mailman not being able to open port 25. > This is weird because other mails have been distributed. > The mailman log shows:Dec 12 22:16:48 2020 (1471) ACCEPT: < message id > > Dec 12 22:16:52 2020 (1474) Cannot connect to SMTP server localhost on port 25 That message is in response to a socket.error exception in attempted delivery. It is logged only once until there is a successful delivery, but the message keeps being retried. > webserver logs:<host > - - [12/Dec/2020:22:16:50 +0100] "GET /archives/api/mailman/urls ?mlist=...&key=*** HTTP/1.1" 200 64 "-" "python-requests/2.25.0" > <host > - - [12/Dec/2020:22:16:52 +0100] "GET /archives/api/mailman/urls?mlist=...&msgid=< message id >&key=*** HTTP/1.1" 200 105 "-" "python-requests/2.25.0" > This last entry is repeated forever (until I stop the mailserver for a few minutes, but later on this happens again for other mails too). Those GETs are part of normal message processing. As I said, they result from core handlers asking HyperKitty for the URL at which the message will be archived so they can add that URL to the Archived-At: header and maybe to a message header or footer. Presumably the one that keeps repeating is the one message/message-id that is throwing the socket.error and being continuously retried. I would stop Mailman and move that one .pck or .bak file out of Mailman's var/queue/out/ directory and then start mailman. You can then examine the queue entry with `mailman qfile` and maybe see what the issue is. > 2..Regarding the mails on the archive page, for most of the lists it is solved now. So probably one of the periodic jobs fixed that.The mailinglist which showed 0 participants 0 subscribers, does show now 0 participants 66 discussions.I have checked the member tables, and the members for this mailinglist are included there. OK. > 3.What I notice now too is that the hourly runjobs tasks don't seem to finish.I would have to check what they exactly do. Can I somehow activate logging for these? > mailman 300042 300016 1 08:00 ? 00:09:18 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 302158 302149 2 09:00 ? 00:09:10 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 304513 304506 2 10:00 ? 00:09:38 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 308631 308620 3 11:00 ? 00:09:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 312847 312832 3 12:00 ? 00:09:15 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 317343 317332 4 13:00 ? 00:09:20 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 320079 320072 7 14:00 ? 00:09:08 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 322618 322610 13 15:00 ? 00:08:54 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settingsmailman 325205 325198 84 16:00 ? 00:06:56 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/django-admin runjobs hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project --settings settings /opt/mailman/venv/bin/django-admin runjobs --list will show you what the jobs are. The hourly jobs are new_lists_from_mailman, thread_starting_email and update_index. The one running long is almost certainly update_index. I would stop running the hourly jobs until you have successfully updated the search index for all lists. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years

[MM3-users] Re: Mailman shell tutorial

by Andrew Bernard

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

6 years, 6 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/24/21 9:40 AM, David Newman wrote: > > > > IMO post-installation docs for list admins would be a big help in > > Mailman3 adoption. I'm willing to help with this. > > > Thank you for being willing to contribute. +1 > I think the place for list admin docs would be in the > https://gitlab.com/mailman/mailman-suite-doc project which is the > source for https://docs.mailman3.org/en/latest/. +1 > Here are the steps to migrate a 2.1 list named `alist(a)example.com` and > its archives. This is documented at https://docs.list.org/en/latest/ (prominent link in sidebar). This appears to be completely different from https://docs.mailman3.org/ (and https://mailman.readthedocs.io/ which I guess is just a redirect). But it looks like the sources are in the some gitlab repo?! > > And I don't know where to add list members. I guess it would be a good idea to provide an image of the menu tree for Postorius. > Did you specify the list's fqdn as in > https://www.example.com/archives/list/list@example.com/ That's not an FQDN, though. "example.com" might be one, but that whole thing is the URL to the archive. Pedantry aside, I think we should probably have a Mailman-specific glossary for many terms, including the tests we use for validation. In this case, FQDN appears to be "sequence of characters not containing '@' or '/'." Steve

4 years

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

by kisner＠live.com

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

3 years, 5 months

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

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > > My point was after you remove the newly minted mailmandb database and > then create a new blank one, and import into that, you should then run > manage.py migrate to apply any new migrations to the imported database. Ah, right ... ok, I've done that now, and all's good. Actually, I've noticed something related. It looks like the mailman-web container runs manage.py as part of its startup procedure in any event. After the import completes, I start up the mailman-web container and, its logs say this: mailman-web | Operations to perform: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | Applying auth.0012_alter_user_first_name_max_length... OK mailman-web | Applying django_q.0014_schedule_cluster... OK mailman-web | Applying hyperkitty.0022_mailinglist_archive_rendering_mode... OK mailman-web | Applying postorius.0014_auto_20210329_2248... OK mailman-web | Applying postorius.0015_auto_20210619_0509... OK mailman-web | Applying postorius.0016_auto_20210810_2157... OK If the container is restarted again, it shows that there's nothing to do this time: mailman-web | Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount mailman-web | Running migrations: mailman-web | No migrations to apply. These latter diagnostics are also what I see if, at this point, I enter the mailman-web container and run "manage.py migrate" explicitly. I really appreciate the help, thanks so much.

3 years, 4 months

[MM3-users] Re: Add an extra option for "Delivery status" for users?

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/19/25 12:50 PM, Thomas Ward via Mailman-users wrote: > > We have a unique case where we have a user we want to disable for mail > > receiving, etc. for the reason "Disabled by IT Security Team" but I > > don't even know if it's possible to add a delivery status that is that > > custom. > At a minimum, you would need to add that choice to the > DeliveryStatus(Enum) in mailman/interfaces/member.py and the choice and > its description to the DELIVERY_STATUS_CHOICES tuples in > postorius/forms/fields.py. I don't know offhand if that would be > sufficient, or if more would be required. In postorius/views/user.py, you also need to add it to `UserPreferencesView,delivery_status_disabled_fields`. Otherwise users will be able to reenable from a security disable. In Mailman core, it's not absolutely necessary, but I think you should handle it the same as `by_moderator` in mailman/commands/cli_members.py, mailman/commands/cli_addmembers.py, and mailman/commands/cli_syncmembers.py. The mention of `by_moderator` in mailman/utilities/importer.py is irrelevant since the new `by_security` (or whatever you call it) doesn't exist in Mailman 2. In mailmanclient, you *may* want to update docstrings in mailmanclient/asynclient.py and mailmanclient/restobjects/mailinglist.py. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 weeks, 2 days

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-05-01 13:35, Mark Sapiro wrote: > On 4/30/24 17:54, Mark wrote: >> >> In the new installation, are the template.uri (in the mailman DB) >> records written as http://localhost:8000/... ? > No. In both the installation that worked and the one that didn't, they > were https://msapiro.net/..., but I don't think it would have > mattered. > > When I reinstalled, I kept the same database, I only rebuilt the venv. > > As I have said at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, > this is all strange. My logs from the failure show the web server > getting the request and serving the template with a 200 status and > then after 5 seconds which is the specified timeout a > requests.exceptions.ReadTimeout error is logged in mailman.log. > > The exact same code is executed whether by a rest runner gunicorn > worker or via some other Mailman core runner, but only the rest runner > fails. Further, a reinstalled venv on the failing server has no error, > and another server which has a venv identical to the failing one > except for Python micro version also has no error. > > I can't begin to understand what the underlying cause might be. Thank you Mark. I'll give rebuilding venv a crack. In the meantime I've cobbled together a script -- https://postmark.io/scripts/ -- and it's got things going for the moment. .

1 year, 7 months

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Gilles Filippini

Gilles Filippini a écrit le 15/06/2020 à 22:05 : > Mark Sapiro a écrit le 15/06/2020 à 21:58 : >> On 6/15/20 12:37 PM, Gilles Filippini wrote: >>> >>> There are 4 emails stored into this folder. 3 of them are spam, and the >>> last one is a legitimate email. This is annoying that such emails could >>> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >>> more and more hyperkitty errors. >>> >>> Any idea how to make their processing more error proof? >> >> >> Change the offending .encode() method to add errors='replace'. >> >> The traceback from the error should tell you where it is. >> >> You could also open an issue at >> <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If >> you do that, please include an error traceback if possible. If there is >> not a traceback in mailman.log associated with the error, there might be >> one in HyperKitty's log (configured in Django's settings). Also, >> including enough of a message to duplicate the issue is very helpful. > > I've now deleted the offending messages. Will open an issue with related > details the next time this error occurs. I've experienced this error again today. Filed issue #301. Thanks, _g.

5 years, 5 months

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

by Jim Popovitch

On Wed, 2021-03-24 at 10:57 -0700, Mark Sapiro wrote: > On 3/24/21 7:58 AM, Brian Carpenter wrote: > > On 3/24/21 9:54 AM, Ralph Weber wrote: > > > Comments received directly from one of the people who developed the > > > AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively > > > established that AWS Mailman is *not* intended to interact with AWS > > > SES when receiving email messages > > > > I don't think there is a Mailman 4 and the person who is marketing his > > services under that name is sending a confusing message to the public. > > Danil Smirnov owns both the mailman3.com and mailman4.com domains. > Mailman 4 is apparently his branding of "Mailman 3 in AWS Marketplace". > In response to our request, the following is included at the bottom of > <https://mailman3.com/>;: > > Mailman3.com (this site) is unaffiliated with Mailman3.org, the domain > used to coordinate development of the Mailman 3 free software suite. The > Mailman 3 core developers are not involved with Mailman3.com, and cannot > answer any questions or provide any support related to its operations. > If you are looking for resources for development of the Mailman 3 free > software suite, please see mailman3.org. > > Yes, this is all ripe for confusion ... Just to add, Danil also owns mailman2.com, and I own (and parked) mailman2.org. -Jim P.

4 years, 8 months

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

by tokyoprogressive＠mailbox.org

Thank you Mark. I will need to find time tomorrow to create two totally new email accounts that I can use in tests so I do not inadvertently sign up again with the same address. Also will double check my settings. Best regards Paul Sent from my iPhone > On Sep 17, 2019, at 14:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/16/19 9:22 PM, Paul Arenson wrote: >> In my test of the two forms of signup, I am getting these unexpected results. Is it my settings or is something weird within the program itself? >> >> 1) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… >> >> 2) Choose "You can also subscribe without creating an account. If you wish to do so, please use the form below" >> >> 3) Then I have to approve it. They get "Welcome to the "Discuss" mailing list! To post to this list, send your email to: discuss(a)list.tokyoprogressive.org > > > You have to approve it or the user has to confirm her email address? > Maybe you have to approve it because the lists Subscription Policy is > Moderate. > >> 4) But I have to approve it.I assume this is because they do not yet have a real account. And they should be listed as a NON MEMBER? > > > No. They will be a member, they just will not have a Django account that > they can log in to. > > >> 5) But even when they sign up here: https://list.tokyoprogressive.org/accounts/signup/?next=%2Fpostorius%2Flist… they get an email from my provider (NOT MY LIST????) as follows: >> >> "Hello from mailman3.emwd.com! You're receiving this e-mail because user iCloud has given yours as an e-mail address to connect their account. >> To confirm this is correct, go to https://list.tokyoprogressive.org/accounts/confirm-email/MTE3:1iA44k:E7w7xh… Thank you from mailman3.emwd.com! mailman3.emwd.com" > > > Because when you create a Django account, you have to confirm your email > address. > > >> 6) And this is where it gets weird. If they send from their email program and get the welcome (Welcome to the "Discuss" mailing list! >> To post to this list, send your email to: discuss(a)list.tokyoprogressive.org You can unsubscribe or make adjustments to your options via email by >> sending a message to....... I then get a notice: >> >> "Your mail to 'discuss(a)list.tokyoprogressive.org' with the subject test notice Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member" > > > What is Message Acceptance -> Default action to take when a member posts > to the list ? > > You get the notice or the user gets the notice? > > >> 7) While if they send FROM THE interface it goes through. >> >> 8) What I am confused about. >> >> Signing up for an account should make them a member, right? Subscribing should make them a non member, no? > > Signing up for an account is just signing up for a Django account. You > can sign up for an account and log in and then subscribe to the list. > > Subscribing makes one a member whether or not you subscribe from a > logged in account or subscribe without creating an account. > > >> But here it seems that both make them a non member. > > If an address which is not a member posts to the list, that address > becomes a non-member. This is the only way other than being explicitly > added by an admin that an address becomes a non-member. > > >> And worse, someone with an account sending from the Interface has their message get through while the same person sending from an email program has me get a notice that a non member is trying to post. > > > If by sending from the interface, you mean posting via hyperkitty, the > user must have an account and be logged in to do that. > > Your "same person" may have multiple entities within Mailman, possibly > subtly different email addresses, one of which is a member and one of > which isn't. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 2 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Sun, 6 Jan 2019 at 18:55, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/19 6:54 AM, Odhiambo Washington wrote: > > > > If I could run MM3 using the apt-get install method, perhaps that would > > have made my life a bit easier, hoping that MM3 can actually be run in > > parallel with MM2.1 on the same host. Is anyone doing that already?? > > > Yes. I am on two production and one development machines. See, e.g. > <https://mail.python.org/mailman/listinfo/> and > <https://mail.python.org/mailman3/> > > One caveat here is I install both Mailman 2.1 and Mailman 3 from source > on all these machines. I don't know for example if the Debian/Ubuntu > packages play well together. > On my Ubuntu machine, I decided to install MM21 from source so I am willing to install MM3 either from source, package or docker. The sparse documentation is my undoing. > > See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> > for more on how I install MM 3. > I have seen that link, but it's missing a ton of details within the process. As I mentioned before, these virtualenv stuff are new to me too, so I thought dockernization would simplify things. If you could include the missing steps that you left out then I could possibly be able to follow the steps :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 11 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > Actually, there's more involved in the pipeline between the > to_archive and to_outgoing handlers. The to-digest, to-usenet, > after-delivery, acknowledge and dmarc handlers are all invoked > between to_archive and to_outgoing IIRC all of the shunted messages that Stephen looked at with qfiles were those special digest messages (ie, message component empty, pointer to lists/$LIST/something.mmdf in the msg_data component). So something is going wrong in the to-digest handler. I don't understand why the original .pck would disappear without either leaving an error log or delivering. (Hmm, @Stephan, have you looked at your "vette" log? it is a separate log in your mailman.cfg I think.) The number of .tmp files lying around bothers me. AFA grep CS, the only place that can happen is in switchboard.py:136 in .enqueue: with open(tmpfile, 'wb') as fp: fp.write(msgsave) pickle.dump(data, fp, protocol) fp.flush() os.fsync(fp.fileno()) os.rename(tmpfile, filename) where `msgsave` is already a pickled object. So either pickle.dump is choking on something in data (the metadata, which I believe is all primitive Python data types), or something (OOM kill?) is happening at the OS level. A crash in pickle.dump should leave an exception log and backtrace in the logs. AFAIK, Mailman does not clean up .tmp files at startup, right? -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 1 week

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 2024-06-23 00:51, Mark Sapiro wrote: >> Nothing showed up in /opt/mailman/mm/var/lists/<LISTID> > > Probably because (in Postorius) Settings->Digest->Enable Digests is No Double checked that Enabled Digest s= Yes >> Then, as "mailman", I ran "mailman digests --periodic" manually and >> got the same error (as expected since there is nothing there) ... > This error should not occur if there is no digests.mmdf. It only does > occur because you have set Digest size threshold to 0 under the > assumption that 0 means unlimited which it doesn't. If you don't want > digests sent on size, you need to set Digest size threshold to a very > large number. > > I've created https://gitlab.com/mailman/mailman/-/issues/1158 to avoid > throwing the exception, but setting the threshold to 0 is still wrong Oh? I was indeed assuming that 0 meant unlimited. The threshold was set at 0. My thinking was that meant the file size was not a factor in determining when the digest was sent and that the sending would be triggered by the daily cron. When I set the threshold very low - 10kB - it sends a digest on every post. So my understanding of what you are saying is: if the threshold is set very large, say 100,000 kB - then a digest will be be sent by the daily cron even if it is smaller than 100,000 kB. Am I understanding correctly?

1 year, 5 months

[MM3-users] Re: MTA setup

by Arte Chambers

Looks like the from header is the email address I am using for testing: From: Arte Chambers <paul.m.robey(a)gmail.com> ``` $mailman qfile /opt/mailman/mm/var/archives/hyperkitty/spool/1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck [----- start pickle -----] <----- start object 1 -----> Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com [209.85.208.182]) by list.louisvillecommunitygrocery.com (Postfix) with ESMTPS id 3E36381ED2 for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec 2024 17:02:48 +0000 (UTC) Received: by mail-lj1-f182.google.com with SMTP id 38308e7fff4ca-3003e203acaso44323081fa.1 for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec 2024 09:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734973367; x=1735578167; darn= list.louisvillecommunitygrocery.com; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; b=SFr5MsvE4S5GUIy9pEuqDHdEW5nW16briFnXG6ARqjLiFgAX12TU5ozUgw5NCJobcx RQWkL64TyXv2C2CTKHjcBH26jiLo1p7h2edLXSBCmd374QbRYQPbv5yZb4jmwX5kfMzr fc/I3pSk6ruN/j+JPGLVxBJBreyLRDV+YL0rDJts83a8hcPHghGMkRTmi2Z1vLYgqThA 2fV/IYwrOe/q4c2+/AwlKQFUuClaxFN4AniNi++Hk7eql7q4ceDtURp1pHW/h4+8UXgJ 2DQ+zwPapOiU5POtfka1fAHTJgykuOoMCmO0YiwfP9p51lXmr4GmdFjFgDOiQwzhx8dH vAEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734973367; x=1735578167; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; b=IwucO1D8XfIbWVT6dQ/LdKNsesrSsiekzj0khFI38CLd6WryQGJOQftxOLR5AvneNs 9gUbVvFAe0VENzTbMrelFr4H5DTI9HrKbNVYEbleeMrbuPypsTdtqWTrjizGhMQROhvs vOxl3T+UfRjDywLj9OuYBiWKTDIIaTpeQ7rR4u1lT8iMGTUre0V8kikm1BsFXwRRzl+U e0ghdIaZYN5kfu/bfR5veCCQhU0l0IF+DvoZzdJCgLkYgImIPhB/X7Zv0wQiUnKoebJo h1UFAEQIrVx2iMFHzLsHiqBhKHvJqG72PAa1bMiG0K3EsYvSJHu5zjrkTjoHXazAci4c trXg== X-Gm-Message-State: AOJu0Yz8oZOnap/9jvXAOcFZnjYoReVHBQrfUnC9u6Mi6M2Ea7dkofrs 4mAlHtOuQYGEyFxJZIOdFybTI20qdBoQBJAPF7FHL6d4mAGrLbPMgTZy3/hWFtmXfOo93a74CSu YsRCZKH5ixK5jPHn4Vye0i/h0oilWXQ== X-Gm-Gg: ASbGncsYG3zr9300F+iwV6VLqHlMKoLuiS2mnT5tGiid8o6Ojd4JIrOBQI0BVNx1aeO FVisNFC7AKewms0adY+Ug4HLKEtg8GwSIz0i32IOtPNA+tNxEAac47wHBGkcv+H2EfTOMsD/p X-Google-Smtp-Source: AGHT+IFNyfqXALTZ0zcO0GJZfpIf/4WT9IZ2EG3oThjt5aoZP3sdPhxjN2UOMTqwI2axiu9io1WSiFszsjxPLHtLIs8= X-Received: by 2002:a05:6512:1190:b0:53e:37e4:1457 with SMTP id 2adb3069b0e04-54229550e25mr4737922e87.33.1734973365282; Mon, 23 Dec 2024 09:02:45 -0800 (PST) MIME-Version: 1.0 References: <77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> In-Reply-To: <77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com > From: Arte Chambers <paul.m.robey(a)gmail.com> Date: Mon, 23 Dec 2024 12:02:08 -0500 Message-ID: <CAM05vAepJnJQengX825dZ4E1PVVxeEgv4ogUcmifP9tqh1i= mg(a)mail.gmail.com> To: Arte Chambers <paul.m.robey(a)gmail.com> Content-Type: multipart/alternative; boundary="00000000000021f3da0629f2f7aa" Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG X-Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG X-MailFrom: paul.m.robey(a)gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: testing(a)list.louisvillecommunitygrocery.com X-Mailman-Version: 3.3.10 Precedence: list Subject: [Testing] Re: test 12.23.24 11.57 List-Id: For testing mailing list software < testing.list.louisvillecommunitygrocery.com> Archived-At: <> List-Archive: <> List-Help: <mailto:testing-request@list.louisvillecommunitygrocery.com ?subject=help> List-Owner: <mailto:testing-owner@list.louisvillecommunitygrocery.com> List-Post: <mailto:testing@list.louisvillecommunitygrocery.com> List-Subscribe: <mailto:testing-join@list.louisvillecommunitygrocery.com> List-Unsubscribe: <mailto:testing-leave@list.louisvillecommunitygrocery.com> --00000000000021f3da0629f2f7aa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Mon, Dec 23, 2024 at 2:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/23/24 09:01, Arte Chambers via Mailman-users wrote: > > Output from mailman log after sending a test message to the list: > > > > Dec 23 16:52:23 2024 (684048) Traceback (most recent call last): > > File > > > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > > line 158, in _archive_message > > url = self._send_message(mlist, msg) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > File > > > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > > line 228, in _send_message > > raise ValueError(result.text) > > ValueError: > > <!doctype html> > > <html lang="en"> > > <head> > > <title>Bad Request (400)</title> > > </head> > > <body> > > <h1>Bad Request (400)</h1><p></p> > > </body> > > </html> > > mailman_hyperkitty is sending the message to hyperkitty to be archived > and receiving the 400 response. Presumably it has previously requested > and received the list_url and the permalink to put in the message > headers. This can be confirmed by the presence of List-Archive: and > Archived-At: headers with values in the messages from the list. So the > configuration seems to be correct to allow mailman_hyperkitty to > communicate with hyperkitty. It is not clear why, but this code > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… > is getting the ValueError. That can come from one of three places in > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming…. > > The lack of a Message-ID: is not it because Mailman's lmtp runner will > add one. Most likely it is the non-ascii sender address from > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming… > > What do you get from > ``` > mailman qfile var/archives/hyperkitty/spool/xxx.pck > ``` > where xxx.pck is one of the (hopefully smaller) files. In particular, > what is the From: header in that? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to paul.m.robey(a)gmail.com >

11 months, 2 weeks

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

by Ken Alker

--On Monday, June 26, 2023 5:26 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/26/23 4:19 PM, Ken Alker wrote: >> >> What else is stored in /var/messages, if not archives? I see 4711 >> messages in that directory (which I presume would be as many messages >> are in the archive database). If there is a write-up on this, feel >> free to point me to it. I found >> <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/ >> model/docs/messagestore.html> but this isn't really answering my >> question. > > > These are probably artifacts from your old Debian package. There have > been issues in the past with handled messages not being removed from the > message store. See https://gitlab.com/mailman/mailman/-/issues/257 > > This was fixed in 3.3.5 and the task runner implemented in 3.3.5 removes > orphaned messages from the message store, but if they are still > referenced in pendings they won't be deleted. So is the only thing stored in var/messages/ the held messages, and nothing more? Is there an outline as to how to clean up the var/messages hierarchy? (I assume one has to be careful not to remove current held messages and maybe old ones that have not been processed; or maybe "old ones" can all be assumed orphaned, and thus, removed w/o concern?)

2 years, 5 months

[MM3-users] Re: Setting up on ubuntu server 22.04

by Odhiambo Washington

On Wed, Oct 4, 2023 at 3:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/3/23 06:00, Kyriakos Terzopoulos wrote: > > > > However, I cannot find the mailman/setup.py anywhere in order to patch > it, > > since the installation was done through pip from here: > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > > Maybe I can try upgrading python from 3.10 to 3.11 and re-install > > > Upgrading Python won't help. There is currently an incompatibility issue > when following > https://docs.mailman3.org/en/latest/install/virtualenv.html because that > doc is based on the head of the GitLab branch, but `pip install > mailman3` installs the 3.3.8 released version of core and the latest > 6.1.0 version of importlib_resources and these are incompatible. > > There are two ways to fix this. > > The easy way is to downgrade importlib_resources in your venv with > ``` > pip install importlib_resources\<6.0 > ``` > The slightly more complex way is to upgrade mailman core to 3.3.9b1 from > GitLab with > ``` > pip install -U git+https://gitlab.com/mailman/mailman.git And I think the 'slightly more complex way' is a better choice as it lets one not get stuck with old software versions :) -- 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, 2 months

[MM3-users] Re: Default moderation for new members

by Seth Seeger

On Thu, Nov 14, 2019, at 9:33 PM, Mark Sapiro wrote: > > > I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. > > > In Postorius set Settings -> Message Acceptance -> "Default action to > take when a member posts to the list" to Hold for moderation. > > This is the action which will be taken for a post from a member whose > individual Moderation is List Default as it is for all new members. > > Then when a post from that member is held, if you click the subject in > the held messages view, a dialog opens showing the message content with > Accept, Reject and Discard buttons and a dropdown list you can use to > set that member's Moderation to Default processing. > > Default processing is generally what you want as it bypasses the > moderation hold but still applies other tests such as header filters, > administrivia, implicit-dest, max-recipients, max-size, etc. So I've set my "Default action to take when a member posts to the list" to "hold". I'm just unclear on what I want to set each member's moderation action to... defer or accept? (I've been reading the docs, but I'm not clear on the difference.) Thanks, Seth

6 years

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

by Odhiambo Washington

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

5 years, 4 months

[MM3-users] Re: using SSH/TLS with external MTA

by Odhiambo Washington

On Sat, Jul 27, 2024 at 11:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/27/24 13:05, Odhiambo Washington via Mailman-users wrote: > > > > ASMTP works on the premise of "we can relay mail for you if we can > > authenticate you with certain credentials" > > Adding the IP to "hosts we can relay mail for" negates the need to > > authenticate, IMHO. > > So I am still waiting for how MM3 does ASMTP. Does it? > > > If by ASMTP, you mean SMTP AUTH, Mailman does it if smtp_user: and > smtp_pass: are provided in mailman.cfg. > > > I agree that an authenticated user should be able to submit mail to be > relayed. Just guessing here, but perhaps the issue is the OP is > submitting to the deprecated port 465 instead of 587. > Port 465 is not quite depreciated. It's the decision of the Admin to decide to listen on/and accept SMTP AUTH on which port. On the servers I run, and based on Exim as the MTA, I accept SMTP AUTH On ports 465, 587 and 2525 (this is meant to subvert some ISPs!). But let's await Roland's response. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

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

by Onyeibo Oku

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

5 years, 1 month

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

by Allan Hansen

Sure: >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... >>> Nothing here, either. Yours, Allan On 9/17/22, 10:30 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/17/22 10:03, Allan Hansen wrote: > Hi Mike, > > Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. > > I tried your script again, with nothing happening. So I tried this: > >>>> >>>> a = 1 >>>> b = 1 >>>> for l in lm: > ... print(a) > ... a = a+1 > ... for nm in l.nonmembers.members: > ... print(b) > ... b = b + 1 > ... nm.unsubscribe() > ... >>>> commit() >>>> print(a) > 1 >>>> print(b) > 1 > > > It appears that lm can't see the lists (I have 50+ of them). Did you start with lm = getUtility(IListManager) ? What if you do ``` >>> lm = getUtility(IListManager) >>> for l in lm: ... print(l.posting_address) ... ``` That should print the posting address for all the lists. What does `mailman info` show? In particular, for `config file:` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 2 months

[MM3-users] Re: Change digest frequency and default threshold

by Henrik Rasmussen

Mark Sapiro wrote: > On 9/21/18 6:21 AM, Henrik Rasmussen wrote: > > When Digest Size Threshold is not reached, mails seems to be sent > > according to digest_volume_frequency': which is set to 'monthly'. The web > > interface doesn't seem to have a setting for this. > > No. digest_volume_frequency only controls how often the digest volume > number increments (and issue number resets). > > In order to send periodic digests, you need to run 'mailman digests > --periodic' via cron. Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). As I understand, using --sent should send a digest immediately (except when used with --dry-run). As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? -- Henrik Rasmussen

7 years, 2 months

[MM3-users] Getting connection timed out

by blackout69

Il 22/05/21 23:52, Mark Sapiro ha scritto: > It's probably not blacklisting. It's not getting that far. Your `glugct` > is attempting to connect to port 25 at mail.simail.it and the connect is > not being answered. Normal blacklisting will not occur until after the > remote MTA answers the connect and determines the IP of the caller. And > in any case, if it is some kind of blacklisting it is your `glugct` > server that is blacklisted by mail.simail.it. > > I just did the following > ``` > $ telnet mail.simail.it 25 > Trying 217.27.113.30... > Connected to mail.simail.it. > Escape character is '^]'. > 220 mail.simail.it ESMTP ready. > quit > 221 mail.simail.it closing connection > Connection closed by foreign host. > ``` > so it did answer my connect. In any case, this is not a Mailman issue. > It is between Postfix on your server and the remote server at > mail.simail.it. Thanks Mark for the reply, I had already checked with the telnet command on port 25 and everything is fine. The suspicion of the blacklist came to me, but now, after checking https://mxtoolbox.com/blacklists.aspx I saw that the mail.simail.it server is in the SORBS SPAM blacklist. Because my lists work fine on any other mailing address. I also checked my email server reputation at https://www.mail-tester.com and I get 10/10 Apparently it doesn't depend on my postfix server. In this case, what strategy do you recommend? Thank you -- blackout69

4 years, 6 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Maybe an idea of my problem as I have pgadmin app installed, it could be in conflict to create a postgresql db? Le 13/03/2022 à 13:46, Yvan ♞ a écrit : > Yes, always this folder file problem, if I create the folder, when > trying install > answer is "mailman allready installed" > https://paste.yunohost.org/raw/avaweyiqom > Still searching... But I'm really not an expert... > Yvan > > Le 12/03/2022 à 21:32, Mark Sapiro a écrit : >> On 3/12/22 08:38, Yvan ♞ wrote: >>> Yes it's debian and I have root access but it's a more "user >>> friendly" server release. >>> I tryed this but it block >>> https://github.com/YunoHost-Apps/mailman3_ynh/blob/master/README.md >>> >>> https://yunohost.org/en/administrate/whatisyunohost >>> Sincerely >> >> I don't read French very well, but your original logs at >> https://paste.yunohost.org/raw/xiqoyajegi and >> https://paste.yunohost.org/raw/hujesebita show installation failing >> because it fails to create /etc/mailman3/mailman.cfg. >> >> This is either an issue with the Debian package or the YunoHost >> installer or an incompatibility between them. >> >> I would go first to YunoHost for help and then to Debian if necessary. >> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 8 months

[MM3-users] Re: applying patch 1130

by David Newman

On 8/21/23 7:57 PM, Mark Sapiro wrote: > On 8/21/23 12:45 PM, David Newman wrote: >> >> I'm looking to patch an existing production server running 3.3.8 so >> it will be able to start under Python 3.11 on Debian 12. Thanks in >> advance for additional clues on what seems like a fairly standard >> problem. > > Since !1130 is merged, just `pip install` from the gitlab head. > ``` > pip install git+https://gitlab.com/mailman/mailman@head Perhaps something else is needed first? This is on a Debian 12 system upgraded from 11, with MM3 3.3.8 installed in a venv. (venv) mailman@x12:~$ pip install git+https://gitlab.com/mailman/mailman@head Collecting git+https://gitlab.com/mailman/mailman@head Cloning https://gitlab.com/mailman/mailman (to revision head) to /tmp/pip-req-build-wjge_v67 Running command git clone --filter=blob:none --quiet https://gitlab.com/mailman/mailman /tmp/pip-req-build-wjge_v67 warning: redirecting to https://gitlab.com/mailman/mailman.git/ WARNING: Did not find branch or tag 'head', assuming revision or ref. Running command git checkout -q head error: pathspec 'head' did not match any file(s) known to git error: subprocess-exited-with-error × git checkout -q head did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × git checkout -q head did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. Thanks dn

2 years, 3 months

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

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 7., H, 19:23): > What is the exact email address that you are logging on to the web UI > with. Does it match exactly with the address of a list member or are > there mixed-case differences? You might try an interaction like this: > ``` > mailman-web shell > Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) > >>> from django_mailman3.lib.mailman import get_mailman_client > >>> client = get_mailman_client() > >>> list_id = 'test.example.com' # your actual list_id > >>> rest_list = client.get_list(list_id) > >>> email = 'user(a)example.com' # your actual email > >>> member = rest_list.get_member(email) > >>> member > This should print something like > <Member 'user(a)example.com' on 'test.example.com' with role 'member'> > ``` > This is exactly what HyperKitty is doing except in your case > rest_list.get_member(email) is throwing a ValueError exception instead > of returning the member. I get: <Member 'megabrutal(a)gmail.com' on 'the.correct.list.address' with role 'member'> So it's even weirder – however, I'm really not sure if this is the address HyperKitty is checking for, as I have 3 attached to my account! How may I know which one it's trying to use?

8 months

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: > > If the manage.py in the directory in which you ran this is the > correct one for your Mailman Django project, I don't know why it > didn't work. Me neither :-( That's why I asked, and probably Guillermo, as well. > Is your Mailman installed in a virtualenv? If so, was the virtualenv > activated? No virtualenv. Mine is deployed using system python on a CentOS 7 system, toghether with another in house developed low requirements Django project, both served by uWSGI vassals. And then, all of a sudden, while I was writting this, it dawned on me! Postorius, Hyperkitty and django-mailman are installed with pip, so, the end up in the site-packages directory (usually /usr/local/lib/python3.x/site-packages), but, normally, django projects are deployed somewhere in the web server hierarchy (/var/ww/django in my case, due to old personal tastes), and applications properly defined in the settings.py for the project. So, the message files are out of reach for manage.py. Changing to /usr/local/lib/python3.x/site-packages/X (with X being postorius, hyperkitty and django_mailman3) and using django-admin compilemessages all works! Thanks for pushing my thoughts in the right direction! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 10 months

[MM3-users] Re: Postorius no connection to REST API

by Richard Rosner

Mark Sapiro wrote: > > Because those aren't the settings that matter for this. > What if anything are your settings in the mailman.cfg [webservice] > section for > hostname: > port: > admin_user: > admin_pass: > use_https: > (defaults in our distribution are localhost, 8001, restadmin, restpass > and no respectively - I don't know if Debian changes these). > These need to match the Django settings > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = 'restpass' They do match. Even the port (still on 8001). > > The REST API is apparently not listening on the host/port this is trying > to connest to. Apparently. The question is why. > > What is executing the manage.py command to start Django. Is it user list? Probably. It depends on who is calling it. I understand too little of the new architecture. But mailman3.service is run as list, mailman3-web.service as root. > > I don't use uwsgi and know little about it so I don't know what the Unix > domain socket /run/mailman3-web/uwsgi.sock connection is for, but this > appears to be some miscunfiguration between apache and uwsgi. > Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via > tcp port 8000 and uwsgi is configured with > [uwsgi] > uwsgi-socket = 0.0.0.0:8000 I too have no experience in the combination ow apache and uwsgi. The only other uwsgi app I'm running is on another server and running under nginx.

4 years, 4 months

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

by Brian Carpenter

On 11/10/20 4:40 PM, Mark Sapiro wrote: > On 11/10/20 1:22 PM, Mark Dadgar wrote: >> Brian specified: >> >> verp_personalized_deliveries: no >> >> Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? > > That depends on the setting of verp_delivery_interval. If > verp_delivery_interval = 1, every message will be VERPed regardless of > verp_personalized_deliveries. If verp_delivery_interval = 0 and > verp_personalized_deliveries = no, deliveries won't be VERPed as you > note. If verp_delivery_interval = 0 and verp_personalized_deliveries = > yes, only personalized deliveries (i.e. individual messages, not > digests, from lists with Personalization enabled) will be VERPed. > > The theory is VERPing has a cost because it requires a separate message > sent to each recipient rather than a single message with multiple > recipients, but personalization also requires a separate message sent to > each recipient, so those can be VERPed at no extra cost. > > But to be clear, automated bounce processing does not require VERP. It > just works a tiny bit more reliably with VERP. We actually enable VERP by default on all new installations of Mailman 3 as we don't see a real performance hit and its benefits are generally very good. This new list however was a whole different beast. Also due to the nature of the list, the benefits of VERPing pales in comparison to the timeliness of the mail being sent. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: spanish localization

by Victoriano Giralt

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

4 years, 10 months

[MM3-users] Re: aborted connection

by Sandor Dibuz

On 2/20/22 01:56, Mark Sapiro wrote: > > First, If your Mailman core version is >= 3.3.5, you shouldn't be > running gatenews via cron. Mailman's nntp runner runs it. See > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > But, that probably isn't it because in Mailman >= 3.3.5, running > gatenews via cron should produce this error > > The gatenews command is run periodically by the nntp runner. > If you are running it via cron, you should remove it from the crontab. > If you want to run it manually, set _MAILMAN_GATENEWS_NNTP in the > environment. > > > However, since you have no lists using a news->mail gateway, you don't > need to run gatenews at all so just remove it from the crontab. I installed Mm3 from Debian stable distro packages as one of the suggested installations methods in Mm3 docs. It's a bit of dated though I know but it was the easiest and fastest. Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] So I disabled gatenews cron job. Maybe later I bite the bullet and upgrade to a recent version (either venv or docker haven't decided yet) but will have to learn how to avoid conflicts with already installed deb packages first. So far so good and everything works, have to check changelogs if an upgrade is worth it. Thank you all your help, Mark. Sanyi

3 years, 9 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-27 08:01, Mark Sapiro wrote: > On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > > > – but the existing directory /opt/mailman/fulltext_index (and its > > contents) are readable and writeable by mailman:mailman: > > > > > drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ > > > > > > -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc > > > -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg > > > -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg > > > -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg > > > -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg > > > -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg > > > -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > > > I fail to see where haystack tries (and fails) to create the directory. > > FWIW, deleting threads is not a problem. > > It is uwsgi trying to do this. What user is it running as? Maybe you need to > add that user to the `mailman` group. That's what baffles me – uwsgi is run as the mailman user: mailman 3904667 1.3 0.5 129516 62188 ? Ss 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904668 0.0 0.3 203248 48796 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini mailman 3904670 0.8 0.6 220436 74464 ? Sl 18:33 0:00 /opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini - Jan

3 years

[MM3-users] Re: Strange password problem

by Eggert Ehmke

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

2 years, 2 months

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

by Odhiambo Washington

On Thu, Jun 6, 2024 at 11:28 AM Marcus Bautze via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hallo, > > Am 27.05.2024 um 14:33 schrieb Mark Sapiro: > > Enabling archivers is done in mailman.cfg similarly to > > ``` > > [archiver.hyperkitty] > > class: mailman_hyperkitty.Archiver > > enable: yes > > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > > Thank you, archiver is now starting. Now there's another problem: > > In mailman.log i'm finding: > > "Jun 06 10:16:16 2024 (3556489) ACCEPT: > <d3072553-2f52-4bd7-b14a-2701863812c7@***> > Jun 06 10:16:17 2024 (3556492) HyperKitty failure on > https://[URL]/mailman3/hyperkitty/api/mailman/urls: <html> > <head><title>403 Forbidden</title></head> > <body> > <center><h1>403 Forbidden</h1></center> > <hr><center>nginx</center> > </body> > </html> > (403)" > > in mailman-hyperkitty.cfg there is: > > base_url: https://[URL]/mailman3/hyperkitty/api/mailman/urls > The documentation says that mailman-hyperkitty.cfg should contain: [general] base_url: https://[URL]/archives api_key: S0m3SecretArchiverAPIKey In settings.py, you should have: MAILMAN_ARCHIVER_KEY = 'S0m3SecretArchiverAPIKey' The KEY is quoted in settings.py,m but not in mailman-hyperkitty.cfg and it must be the same in both files. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 6 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 20:00, Mark Sapiro wrote: > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> But... here is a thing that I can not understand: If the source (the .po >> file) is from november 7th, it doesn't matter how many times you >> recompile it: the result will be the same. > Correct, but the point is if you download the latest > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 file > in the distribution, you will find they are identical, so it it appears > that the weblate translation hasn't changed since that time. > > If there are issues in this mailman.po, they exist in weblate too and > need to be fixed there. That clarifies all. Thanks. As I said in my previous message, I'll wait for the next upgrade and hopingly the translations done after 7h of november (by others and me) will be there. > > Also note that the translations on weblate only affect strings in the > core code. The Mailman core templates are not currently translated in > weblate and there are currently no Spanish language templates. One would > need to create Spanish translations of all the templates in > <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> > and submit a merge request to add them to a mailman/templates/es/ directory. > I will make the template translations locally, test them, and then, if they are yet lacking in the main repo, follow your suggestion. Thanks.

4 years, 10 months

[MM3-users] Re: Issues with importing archives from a particular list

by Philip Colmer

On Thu, 13 Jan 2022 at 18:01, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/13/22 4:33 AM, Prasanth Nair wrote: > > Hello, > > > > We are trying to import archives from Mailman2 to Mailman3. For a > > particular list, it is not importing all of the messages. We can see that > > Mailman2 has archives from 2015 to 2022. But, it only imports messages > from > > 2018 to 2022 to the Mailman3 server. It was not giving any errors while > > importing. > > > The problem list probably already had an archived message from 2018. If > you don't specify a --since= date for hyperkitty_import, it only imports > messages newer than the newest existing message in the archive. > > You can run it again with, e.g., --since=2000-01-01. It won't reimport > the messages already imported because of duplicate message ids. > Thank you, Mark, for your reply. It turned out that this wasn't an issue with any part of the Mailman 3 suite. Unbeknownst to Prasanth, the affected list had previously been migrated from a different server in 2018 but, for some reason, the mbox file was not copied over - just the pipermail archive directory was. That explains the split between the pipermail archives and the mbox file. Thankfully, the original server still had the older mbox file so we've now been able to import all of the messages into HyperKitty. Apologies for the noise. Regards Philip

3 years, 10 months

[MM3-users] Re: REST API authorization failed

by Axel Rau

Hi Mark, thanks for your patience. > Am 10.01.2022 um 04:56 schrieb Mark Sapiro <mark(a)msapiro.net>: > > Anyway, the above is saying that restadmin:??? doesn't match what's configured in Mailman core and reported by `mailman info`. Please check carefully that these are the same in both mailman.cfg admin_pass and settings MAILMAN_REST_API_PASS. Yes, again with password disclosed: - - - (mailman_33) [root@lists5 /usr/local/mailman3]# service mailman restart Restarting the Mailman runners (mailman_33) [root@lists5 /usr/local/mailman3]# su -m www -c "curl -v -u restadmin:restpass http://localhost:8001/3.1/lists" * Trying 127.0.0.1:8001... * Connected to localhost (91.216.35.42) port 8001 (#0) * Server auth using Basic with user 'restadmin' > GET /3.1/lists HTTP/1.1 > Host: localhost:8001 > Authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz > User-Agent: curl/7.80.0 > Accept: */* > * Mark bundle as not supporting multiuse < HTTP/1.1 401 Unauthorized < Server: gunicorn < Date: Mon, 10 Jan 2022 09:39:43 GMT < Connection: close * Authentication problem. Ignoring this. < www-authenticate: Basic realm="mailman3-rest",charset="utf-8" < content-type: application/json < vary: Accept < content-length: 77 < * Closing connection 0 {"title": "401 Unauthorized", "description": "REST API authorization failed“} (mailman_33) [root@lists5 /usr/local/mailman3]# (mailman_33) [root@lists5 /usr/local/mailman3]# grep REST settings.py MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' (mailman_33) [root@lists5 /usr/local/mailman3]# grep admin var/etc/mailman.cfg admin_user: restadmin admin_pass: restpass (mailman_33) [root@lists5 /usr/local/mailman3]# - - - What am I doing wrong? Is something wrong with my installed python packages? pip freeze attached. clueless, Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 years, 11 months

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

by Mark Dadgar

On Oct 5, 2019, at 12:22 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > You could just run, e.g., `sudo -u list bin/mailman import21 ...` which > will work even if 'list' can't log in. That’s what I get for being old school and just su’ing to the user. Thanks. > If you run hyperkitty_import --since=1990-01-01, that should do it. > Awesome - rerunning now. Thank you. > As far as "the archives for many months consist of just a single > identical thread", were there error messages when you ran the initial > import? Were there issues in the imported mbox that you have corrected? > Mailman 2.1's bin/cleanarch can help identify unescaped 'From ' lines > that cause problems. Yes, I ran the archive mbox through cleanarch before importing it. It’s a 24GB mbox file with 17 years of archives for a very active mailing list. > If unescaped 'From ' lines is the issue and you have fixed them, > rerunning the import should import the messages correctly, but it won't > delete the bogus threads. You can delete these threads manually in > HyperKitty if you are logged in as a Django superuser. Great - thank you. I see the occasional “table is locked” error (I am running against sqlite because I only run a couple of lists and I was having issues getting the postgres config working) so it skips the occasional message. We’ll see what happens this time. Your help is much appreciated. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 2 months

[MM3-users] Re: Monthly Password Reminders

by Stephen J. Turnbull

Odhiambo Washington writes: > On Thu, Feb 2, 2023 at 8:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/2/23 06:29, Odhiambo Washington wrote: > > > Does MM3 send these monthly subscription reminders the way MM2 used to > > do? > > > I am looking for the setting, but can't find that in the list settings. > > > > No, it does not. > > The rationale behind the decision to toss away that feature? Security?? For the passwords, yes. It was frequently reported as a bug, in fact. Mostly the reminders generate requests to know how to shut them off. You're the first in probably a decade who's asked how to turn them on! While in theory we could protect in transit with SMTP over TLS, we can't guarantee end-to-end encryption (eg, if there's a .forward at the subscribed address), and while TLS is widely implemented, it's still not universal. And there's no way to protect unencrypted email from admins at the receiving host. Receiving encrypted email is pretty much not implemented at all, except in some specialized communities. Also, now that passwords (if they're used) are attributes of Users who may have several Addresses and worse, they may have admin privileges. So Mailman 3 passwords are generally higher value than in Mailman 2. I can imagine a use for the list of subscriptions part that a few users might like, but most folks would prefer not to get another regular mailing. Steve

2 years, 10 months

[MM3-users] Re: autoresponse not sent

by Peter Sørensen

Thanks Mark, I found the mysql.py as you suggested and a few places more. /usr/lib/python3/dist-packages/mailman/database/mysql.py /usr/lib/python3/dist-packages/alembic/ddl/mysql.py /usr/lib/python3/dist-packages/passlib/handlers/mysql.py /usr/lib/python2.7/dist-packages/django_extensions/management/mysql.py Could this be the problem ? Best regards Peter Sørenen University of Southern Denmark Den 19/10/18 18:47 skrev "Mark Sapiro" <mark(a)msapiro.net>: >On 10/19/18 8:21 AM, shadiakiki1986(a)gmail.com wrote: >> Hello. Newbie to mailman here. >> I tried out mailman3 today. My setup is >> - mailman3 suite using the docker-compose file from asynchronous.io >> - exim4 on the local machine and configuring it as smarthost using >>mailgun smtp server >> >> The emails to the mailing list are received by the subscribers, >> but the autoresponse is not being received by the sender (who is not >>from the subscribers list). >> I'm not sure if the problem is from mailman-core, settings from >>mailman-web, or from exim. > > >This is most likely <https://gitlab.com/mailman/mailman/issues/504>. The >fix has been in the master branch for a couple of months but is not in >3.2.0. It may be in the asynchronous.io "rolling release". > >-- >Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >San Francisco Bay Area, California better use your sense - B. Dylan >_______________________________________________ >Mailman-users mailing list -- mailman-users(a)mailman3.org >To unsubscribe send an email to mailman-users-leave(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

7 years, 1 month

[MM3-users] Re: no access to Postorius web pages after upgrade

by David Newman

On 10/22/23 2:16 PM, Mark Sapiro wrote: > Here is the nginx error, with obfuscation of client and server info: >> >> 2023/10/22 10:43:24 [error] 2264140#2264140: *135 >> "/opt/www/roundcubemail/postorius/domains/index.php" is not found (2: >> No such file or directory), client: 1.2.3.4, server: >> lists.example.com, request: "GET /postorius/domains/ HTTP/2.0", host: >> "lists.example.com", referrer: >> "https://lists.example.com/mailman3/listinfo" > > > Here you are trying to get > https://lists.example.com/postorius/domains/, but (see below) > # begin mailman3 stuff >> >> location /static/ { >> alias /opt/mailman/web/static/; >> } >> >> location /mailman3/ { >> proxy_pass http://127.0.0.1:8000; >> proxy_set_header Host $host; >> proxy_set_header X-Forwarded-For $remote_addr; >> } > Above you have defined proxying for the paths beginning with > /mailman3/, /archives/, /mailman/ and others, but not /postorius/ or > /hyperkitty/. Bingo. Adding location statements for hyperkitty and postorius and restarting Nginx cleared the issue. Unclear why this ever worked before the upgrade. I don't remember monkeying with a urls.py file. Anyway, it works now. Thank you Mark! >> (venv) mailman@mail10:~$ mailman-web migrate >> System check identified some issues: >> >> WARNINGS: >> account.EmailAddress: (models.W036) MariaDB does not support unique >> constraints with conditions. > > This is an issue with MariaDB and MySQL. > Thanks again. No issues here, but glad to see you previously raised this as a known issue. dn

2 years, 1 month

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-24 10:38, Mark Sapiro wrote: > Try the following in `mailman shell` running as user mailman > ``` > (venv) $ mailman shell > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > >>>> import requests >>>> r = requests.get( > ... > 'https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD…', > ... timeout=5) >>>> t.text > ``` > Note the URL above is all on one line. > This is exactly what Mailman core is doing to get the template > assuming the `uri` in the template` table entry is the argument of the > requests.get(). > > If this times out, try increasing the timeout= value. ************************************************ I crossed emails with you on my last post. I reset the POSTORIUS_TEMPLATE_BASE_URL (in settings.py) back to the domain name, restarted everything, created a new Welcome template (using Postorius) and ... >>> import requests >>> r = >>> requests.get('https://MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/li…', >>> timeout=5) >>> r.text 'Another test Welcome message for new members.' >>> ... so all well there. And mailman is running mailman core ... # cd /opt/mailman/venv/bin/ # ls -la ... -rwxr-xr-x 1 mailman mailman 230 Jan 26 04:00 gunicorn -rwxr-xr-x 1 mailman mailman 231 Jan 26 04:00 mailman -rwxr-xr-x 1 mailman mailman 230 Mar 25 22:18 mailman-web ...

1 year, 7 months

[MM3-users] Re: Problems with New MM3 Installation

by Jeff

> On May 11, 2021, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > Set base_url: in /usr/local/mailman3/mailman-hyperkitty.cfg to a url > that will reliably access HyperKitty, probably the same base URL that a > user with a web browser would use. > Thanks Mark, I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: 1) some emails that arrived before I got the archive working are still sitting in: /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? 2) Some messages that arrived while I was having other problems with the setup have been stored in: /usr/local/mailman3/mm/var/queue/shunt What should I do to get these messages processed? 3) Similar to above, some messages are in: /usr/local/mailman3/mm/var/queue/bad How can I get these messages processed? 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? Thanks again for any help anyone can provide. Jeff

4 years, 7 months

[MM3-users] Re: High memory usage

by Stephen Daniel

I'm not an expert, and you might be better served by posting this question in one of the communities that serves sysadmins; however, my reading says that the oom-killer is invoked when the system cannot allocate more virtual memory, not more physical memory. The graph in your screenshot is physical memory usage. The first thing I would try is increasing the size of your swap partition. That adds to the amount of available virtual memory, without the need for actually buying more RAM. If you really need more RAM the result will be that the system stays up, oom-killer stays quiet, but performance is bad and the "si" and "so" columns in vmstat get into the triple digits or higher. On Wed, Feb 16, 2022 at 3:18 AM Philip Colmer <philip.colmer(a)linaro.org> wrote: > Thank you for the replies from Mark and Stephen. > > One of the reasons why Prasanth & I are concerned with this specific system > is because the first time memory usage crept up, it got to the point where > oomkiller stepped in and, as is usual for that particular mechanism, one of > the processes it killed was sshd, thus removing access to the system :(. I > know that oomkiller can be tuned to stop it killing processes like sshd but > it will, nevertheless, start killing *some* processes if it sees an out of > memory situation. > > So, as Prasanth said, we doubled the memory available and stuck an alarm on > it to trigger when usage exceeded 85% for 5 minutes. I've saved a > screenshot of the monitored memory usage over the last couple of weeks: > > https://1drv.ms/u/s!Aq7dn8GDGLdCodsU-pybJBdckxWU1A?e=BJY1UA > > (It is stored on OneDrive in case you don't recognise the URL format) > > We changed the server on 4th February to the larger memory size. On 11th > Feb, it triggered the alarm and we rebooted the server. Memory usage is > starting to climb again, albeit not at the pace that it was previously. > > What is particularly curious for us is that we have four Mailman 3 servers. > Two of them are single domain and two are hosting two domains. This server > is one of the servers hosting two domains, but it is also the ONLY one of > the four servers exhibiting this memory pattern. By comparison, the memory > usage for the other server hosting two domains looks like this: > > https://1drv.ms/u/s!Aq7dn8GDGLdCodsVyEufkeQqit_cGA?e=ifrJHs > > The biggest difference we are aware of with the "problematic" server is > that some of the list archives are quite large by comparison with our other > servers. The largest is 15K messages, then 2K then 1K. The other three > servers have lists with relatively small archives by comparison (double or > triple digits at worst). > > Finally, and just FYI, we're using PostgreSQL for the database and Xapian > for the indexing engine. > > Regards > > Philip > > On Tue, 15 Feb 2022 at 16:36, Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 2/15/22 08:11, Stephen Daniel wrote: > > > TL;DR: quite likely your system has plenty of memory and is operating > > > normally. > > ... > > > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair < > prasanth.nair(a)linaro.org> > > > wrote: > > > > > >> Hi, > > >> > > >> We are having an issue with high memory usage on our Mailman3 server. > > >> Initially, our server had 16GB RAM and the memory usage went up from > 5% > > to > > >> 92% within a week. So, we increased the memory capacity to 32GB RAM > and > > we > > >> can see that the memory usage is going up in the same pattern. > > >> > > >> Any idea why it is happening? or any suggestions? > > > > > > Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM 3 > > lists with 16 GB of ram and no swap. > > > > The server that supports this list and also the www.list.org web site > > has 4 GB of ram and no swap. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 9 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-28 01:32, Mark Sapiro wrote: >> 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. I created a text file as a custom welcome message and chowned it to mailman:mailman, then edited the database record (template.uri) from http://localhost:8000/mailman3/api/templates/list/mytestlist.mydomain.com/l… TO file:///home/mark/welcome.txt This delivered the custom welcome message to the user when subscribed via Mass Subscribe. I'm not sure what this tells me other than a call can be made to a file but not the database. > More strangeness. I've now done a test on one of the production > servers I manage, and there is no error. Both the production server > and the development server are running the identical Mailman code > installed in a venv, they both have the same version of urllib3 and > similar Python versions, 3.9.16 on the development server and 3.9.10 > on the production server. Both servers are running under Ubuntu > 20.04.6. The only other difference I see is on the production server > everything runs as user mailman and on the development server > everything runs as user mark. Mine is Debian 12 with Python 3.11.2. Could a newer Python version really cause this amount of grief?

1 year, 7 months

[MM3-users] Re: Setting base_url for the domain to use it in the templates.

by Odhiambo Washington

On Thu, Jul 11, 2024 at 6:58 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/10/24 7:17 PM, Timour Bakeev wrote: > > Hi all! > > > > I'm trying to use extended placeholders for the [templated texts]( > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > in the message footer that are sent to the members: > ... > > But my attempts to use REST API to set it fail: > > > This feature is in the not yet released Mailman 3.3.10, see > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… And talking of 3.3.10, I have a feature request, or I might just be making unnecessary noise if this is already documented somewhere: I find the unsubscribe_all button quite scary! I have never used it though, so I am not quite sure about its behavior. What scares me is the possibility of clicking it and then in one fell swoop you've removed ALL the members without a "confirmation". So I was wondering if that button can be modified to have a dropdown selection with No/Yes, so that one has to select the No (backoff) or Yes (blow away!). -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 5 months

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

by Bill Christensen

On 6/23/18 5:01 PM, Mark Sapiro wrote: > On 06/23/2018 02:48 PM, Bill Christensen wrote: >> Our Mailman2 setup uses Fetchmail to retrieve list mail from our >> accounts on Gmail. >> >> Is there a similar setup for Mailman3? > > Delivery to Mailman is different in Mailman 3. What are you currently > doing with Fetchmail? the general syntax we're using is: poll imap.gmail.com protocol IMAP username "<list address>" there with password "<password>" is "mailman" here nofetchall keep ssl sslcertck sslcertpath /path/to/share/ssl/certs mda "/path/to/mail/mailman post <listname>" set daemon 900 > > If you are doing something like getting the mail from google and > delivering it via SMTP to an MTA on the Mailman server, that should > still work for MM 3. I think that's what the above is doing. Right? > > If Fetchmail is piping it to a command like > > "| /path/to/mail/mailman post listname" > > that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP > server (which it calls a runner). Mail is normally delivered to an MTA > which is configured to relay the mail via LMTP to the localhost port > that Mailman is listening on. So Fetchmail can eithr deliver to the MTA > and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port. > -- Bill Christensen http://SustainableSources.com http://LinkedIn.com/in/billc108 Dance like nobody's watching. Encrypt like everyone is. --Adrián Lamo

7 years, 5 months

[MM3-users] Re: Your Dashboard

by Mark Dadgar

On Feb 11, 2020, at 12:26 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. > > > I explained above why this is the case, but you can fix it. You do so by > making a sitewide template for this message. In the case of this list, > we have a template in Mailman's var/templates/site/en/ directory (the > default directory for sitewide english templates. This template is named > list:admin:action:post.txt and its content on this site is: > >> As list administrator, your authorization is requested for the >> following mailing list posting: >> >> List: $listname >> From: $sender_email >> Subject: $subject >> >> The message is being held because: >> >> $reasons >> >> At your convenience, visit >> https://lists.mailman3.org/mailman3/lists/$list_id/held_messages > > > Of course, in your case the <https://lists.mailman3.org/mailman3/> part > of the URL will be different. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> > for the other templates I also install. > > You can also put domain specific templates in > var/templates/domains/$domain/$lc/ which override site templates for the > domain and list specific templates in var/templates/lists/$list_id/$lc/ > which override site and domain templates for the list, and you can also > set list templates via Postorius. Awesome - thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 10 months

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

by denis.bitouze＠univ-littoral.fr

Mark Sapiro wrote: > On 6/23/22 12:37, denis.bitouze(a)univ-littoral.fr wrote: > > > > What is the Postorius version and is it installed from source, pip or as > > package and if as package, what package? - Postorius 1.3.4 - Here are some details: ┌──── │ $ apt-cache show mailman3-full │ Package: mailman3-full │ Source: mailman3 │ Version: 3.3.3-1 │ Installed-Size: 48 │ Maintainer: Debian Mailman Team <pkg-mailman-hackers(a)lists.alioth.debian.org> │ Architecture: all │ Depends: mailman3, mailman3-web, python3-mailman-hyperkitty │ Description-en: Full Mailman3 mailing list management suite (metapackage) │ This is GNU Mailman, a mailing list management system. This metapackage │ depends on all components of the full Mailman3 suite: │ . │ * mailman3: The core Mailman3 delivery engine │ * mailman3-web: Django project integrating Mailman3 postorius and hyperkitty │ * python3-mailman-hyperkitty: Mailman3 server plugin for Hyperkitty archiver └──── > The choices should be Accept, Reject and Discard. There should be no > Ignore choice, but I'm guessing you see them in French where the > translation of Discard is Ignorer. See > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/L.... Indeed, sorry for the misleading translation from French to English. Maybe I'll suggest another word to the French translation team. > The difference between Reject and Discard is Reject notifies the > sender of the rejection whereas Discard just discards the message > without notification. IMHO, even in English, “Reject” and “Discard” are not self-explanatory. BTW, no clue about an automatic banishment of emails from discarded messages?

3 years, 5 months

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

by Eggert Ehmke

/ I saw output like:/ <User "Real Name1" (250400693957149667060114911620088407125) at 0x7f9435096640> deleted from Mailman <User "Real Name2" (52978839424924170731978420609240089133) at 0x7f9435096760> deleted from Mailman So your users had no real names configured? Cheers, Eggert Am Dienstag, 25. April 2023, 23:14:27 CEST schrieb Andrew Hodgson: > Mark Sapiro wrote: > >The script at https://www.msapiro.net/scripts/clean_users.py has been > >updated. As before, it has settings to control whether Django users are > >deleted if there is a corresponding Mailman user with no memberships or > >only if there is no corresponding Mailman user, and whether or not Mailman > >users with no >memberships are deleted. > Thanks, I ran this script and it did delete a load of Mailman users, I got > output similar to this: <User "" (47600399411039288509336192576257642185) > at 0x7fb17a6a35e0> deleted from Mailman > > Why aren't we seeing the actual address here? > > Thanks. > Andrew. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message > /BTJUT6FGNGK5ARADPD6VW37VMHQG2GWJ/ > > This message sent to eggert(a)eehmke.de ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 7 months

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

by Marvin Gülker

Hi, Am 11. Februar 2019 um 13:20 Uhr -0800 schrieb Mark Sapiro: > I downloaded the February mbox from > <https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/export/wlug@l…> > and imported it to a test list with 'django-admin hyperkitty_import and > see the same issue. Here's the Hyperkitty Mbox for my affected mailinglist: <https://lists.secretchronicles.org/hyperkitty/list/tsc-devel@lists.secretch…> Maildir from my local machine as received from Mailman via e-mail: <https://files.guelker.eu/misc/tsc-devel.tar.gz> > Examination of the mbox shows for the first message [...] > Note the folding of the header and the double angle brackets. I can confirm that I see this behaviour for my affected mailinglist as well. The Message-ID header is broken over two lines with double angle brackets in the Hyperkitty MBox linked above: Message-ID: < <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org>> However, the original message as it was delivered by Mailman to me does not have such a weird message-id header: Message-ID: <153582973006.27514.7508703206376217479(a)alexandria.secretchronicles.org> In this message, the header is broken exactly as shown above after the colon of "Message-ID:". Maybe some problem with parsing long Message-ID headers, or ones folded over multiple lines? With regard to bug reporting on gitlab.com: I already have accounts on a ton of sites, and at some point I'd actually like to stop creating new ones all the time... Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

6 years, 10 months

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > That combination at least produces multipart/signed messages with > multipart/* parts containing a Content-Transfer-Encoding: header. > > The Python 3 email library considers this to be a > InvalidMultipartContentTransferEncodingDefect() message defect. Merely containing C-T-E is not an error per RFC 2045, although it seems to consider it a stupid thing to do. If present, it may be "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening that restriction been published since? (I don't know why it would, though.) Even with a non-cleartext C-T-E, it seems reasonable for Mailman to treat it as application/octet-stream and pass it through, unless the list is configured to do something like strip application/octet-stream or that requires decoding like spam-filtering (Postel principle, although one could argue it shouldn't be sent on on the same principle -- ah, the joys of being an e-mail Mediator). That would be especially true it if were quoted-printable, since any relevant MIME headers would (presumably) be pure ASCII and therefore unencoded. > multipart/signed > multipart/mixed * > text/plain > message/rfc822 (the attached message) * > multipart/signed * > text/plain > application/pgp-signature > text/plain (an empty plain text part) > text/plain (a quote of my message to you) > application/pgp-signature It's true that Apple Mail is horked if it produces that structure with C-T-E in the indicated places (but we already knew that :-( ). Steve

3 years, 7 months

[MM3-users] Re: Process on migrating mailman

by Odhiambo Washington

On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > Any suggestion on how to migrate mailing list and archirve with diffirent > server and domain. For the mailing list from sample.domain1.example.com > to sample.domain2.example.com > > Old Mailing list > Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] > Domain Domain1.example.com > > New Mailing list > Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC > 8.5.0 20210514 (Red Hat 8.5.0-20)] > Domain domain2.example.com How many lists? How big are the archives? Looking at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, it seems like it's not a trivial exercise. However, I am wondering about the consequences of: 1. dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then re-importing 2. editing settings.py and webserver config to reflect the DOMAIN2 3. reconfiguring your MTA to handle list mails using the DOMAIN2 I am imagining a virtualenv type of installation. Is there somewhere in the data where the DOMAIN1 is hardcoded in a way that it cannot be replaced by a text editor? @Mark Sapiro <mark(a)msapiro.net> ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: Dealing with email bounces from web signups

by Hans-Martin Mosner

Am 17.03.22 um 03:40 schrieb Mark Sapiro: > > > The issue of more concern to me is when the subscription uses a deliverable address. The owner of that address > receives this unwanted confirmation email which is bad enough, but then sometimes reports it as spam to her ISP which > affects my server's reputation. But, so far, I don't do anything about that either. > As I'm a mail admin for a server whose users get lots of those misguided mails I'd say that the vast majority of them are not from mailing list signups but from web contact forms which automatically respond to entered contact requests with "Dear Polly liked your profile https://bit.ly/crap". I regularly report these as spam and expect website owners to disable automatic mails from such forms (I also advise our users who have their own websites to disable that, and strictly filter it on outgoing mail). I would probably also report these as spam when coming from mailing lists subscription requests, and I would likewise advise you to send subscription responses only after a moderator checks and releases the subscription request. It can still happen that you send out somethin to someone who didn't subscribe, but you should be able to reduce the numbers significantly. I know this causes extra moderator work because you don't get the automated pre-filtering for deliverable addresses, so this is something where you need to weigh pros and cons for your particular situation. Cheers, Hans-Martin

3 years, 8 months

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

by Nelson Strother

As you had suggested, the `in` runner/queue was missing in action. Given your insight about the limitations of `mailman restart`, I looked back at the log from the time of the preceding `mailman start`, and found that there was NOT a line such as: in runner started. in that instance! Watching the logs on each subsequent `mailman start`, the good news is that the `in` runner/queue has been started each time; the bad news is that slightly more than half of the time one or two runners are NOT shown as starting. The other runners/queues sometimes missing in action per the log file have been `retry`, `task`, `nntp`, `archive`, and `pipeline`. No errors are being recorded in the mailman log files. This is GNU Mailman 3.3.8 via `pip install mailman` on Debian 5.10.179-1 (2023-05-12) running on a shared system where VMware gives this server enough cycles that `mailman start` and `mailman stop` each consume from 20 minutes to an hour of wall clock time, so I do not issue those commands recreationally, attempting to keep the system available for users. What should I do to help understand the cause for these failures? Would not it be helpful for this limitation of restart to be included in: mailman restart --help with a suggestion to use `mailman stop` and `mailman start` instead? On 6/1/23 11:16, Mark Sapiro wrote: > When you issued a restart and the logs show runners restarting, did > all the runners restart or was one or more missing.

2 years, 6 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Tue, Dec 27, 2022 at 11:57 AM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mark Sapiro writes: > > > The last I looked into using Twitter as an OAuth2 provider, which was > > some time ago, it would not work because Twitter would not provide the > > user's email address via OAuth2. Possibly this could work if the user's > > name was her Twitter handle. > > Yeah, but then I (@yasegumi@twitter) could log in as > yasegumi(a)example.com and every other yasegumi in the world. There > probably aren't any of those that aren't me, but of the 30 kids in my > 6th grade class 5 were named something with the diminuative "Steve", > and we also had one Stephanie. So I could log in as > steve(a)turnbull.sk.tsukuba.ac.jp (that's me) or steve(a)xemacs.org > (that's not me, I'm stephen(a)xemacs.org) or steve(a)any.old.com. Not > good. > > Also, I wouldn't trust Musk's Twitter with no security staff left to > give out only confirmed email addresses. If they give out any address > you gave them, then anybody can spoof anybody. So I would advise not > using Twitter as an idP under any conditions, unless it's to prove you > own a Twitter handle. > Okay. Now I really don't want to add Twitter to my Social Account logins :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

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

by Mark

On Sat, 2023-09-23 at 18:56 -0700, Mark Sapiro wrote: On 9/23/23 17:51, Mark wrote: > > For example, on searching for the word "Derbyshire" (which is > mentioned > in one of the archived messages) the results page displays: > > "Sorry no email could be found for this query." > > The logs show: > > +++++++++++++++++++++++++++++++++++++ > /var/log/mailman3/web/mailman-web.log > +++++++++++++++++++++++++++++++++++++ > > [pid: 1156|app: 0|req: 55/55] > 2001:8004:5310:2405:ce66:5ff:41fc:60db () > {76 vars in 1537 bytes} [Sat Sep 23 23:57:43 2023] GET > /mailman3/hyperkitty/search?mlist=LISTNAME- > 1%40DOMAIN.COM&q=Derbyshire > => generated 13752 bytes in 3188 msecs (HTTP/1.1 200) 5 headers in > 164 > bytes (1 switches on core 0) ... > mlist = MailingList.objects.get(name=mlist_name) > File "/usr/lib/python3/dist- > packages/django/db/models/manager.py", > line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/usr/lib/python3/dist-packages/django/db/models/query.py", > line > 406, in get > raise self.model.DoesNotExist( > hyperkitty.models.mailinglist.MailingList.DoesNotExist: > MailingList2023-09-21 08:55:36.385239+10 > matching query does not exist. What does this database query return ``` select * from hyperkitty_mailinglist where name like 'LISTNAME-1(a)DOMAIN.COM'; ``` If it returns a row, does case match for the name in the row and the query? Yes, the query returns a result and the case in "name" matches that in the query ... select * from hyperkitty_mailinglist where name like 'listname(a)domain.com' id | 91 name | listname(a)domain.com display_name | Listname description | ... subject_prefix | [Listname] archive_policy | 1 created_at | 2023-09-21 08:55:36.385239+2 list_id | listname(a)domain.com

2 years, 2 months

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Odhiambo Washington

The links work for me. On Thu, Jan 9, 2025, 20:19 Alain D D Williams <addw(a)phcomp.co.uk> wrote: > On Thu, Jan 09, 2025 at 09:06:56AM -0800, Mark Sapiro wrote: > > On 1/9/25 06:07, Alain D D Williams wrote: > > > > > > For an example see: > > > > > > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > > > The above URL and also > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… > > and even https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/ all give > a 500 > > internal server error response. > > Sigh - try again. > > The 500 error happens several times a day. After 5 minutes it behaves as it > should ... until it happens again some time later. I have not found out > what is > happening; nothing obvious in the logs, not high system load. I can live > with > it for now as I am busy elsewhere. > > -- > Alain Williams > Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT > Lecturer. > +44 (0) 787 668 0256 https://www.phcomp.co.uk/ > Parliament Hill Computers. Registration Information: > https://www.phcomp.co.uk/Contact.html > #include <std_disclaimer.h> > _______________________________________________ > 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 >

11 months

[MM3-users] Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Eggert Ehmke

This makes it even stranger. Removing the trailing / did not help in my case, but replacing the mailman3 for mailman in the ProxyPass line did. Would be really nice to solve this problem at the root. Am Montag, 25. Oktober 2021, 18:09:21 CEST schrieb Mark Sapiro: > On 10/25/21 1:45 AM, Stefan Bauer wrote: > > Dear Users, > > > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > > web-interface via > > > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > > > I receive > > > > Not Found: /mailman//postorius/lists/ > > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated > > 2821 > > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on > > core > > 1) > > > > Where does the wrong path come from (mailman vs. mailman3) > > See the thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U > SXUYZYB5KIXT37APMCOAUZLKBRPARTL/ > > ... > > > <IfModule mod_proxy_uwsgi.c> > > ProxyPass /mailman3/favicon.ico ! > > ProxyPass /mailman3/static ! > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > </IfModule> > > Others have found that removing the trailing slash from > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > to make it > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > > fixes the issue.

4 years, 1 month

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 4:37 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 00:32, Odhiambo Washington wrote: > > > > Apparently so, because: > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists > > No matching mailing lists found > > mailman@lists:~$ > > > > Which is surprising, given this: https://imgur.com/a/LPrh42K > > > Postfix is talking to a different Mailman core. > There isn't any other. This server has only been running Mailam21. > > root@lists:/home/wash# su - mailman > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create > > skunkworks(a)lists.my.co.ke > > sh: 1: /usr/sbin/postmap: not found > > sh: 1: /usr/sbin/postmap: not found > > Traceback (most recent call last): > ... > > RuntimeError: command failure: /usr/sbin/postmap > > /opt/mailman/var/data/postfix_lmtp, 127, Key has expired > > command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, > > 127, Key has expired > > > > Now that wants Postfix, while I don't use Postfix, but Exim as the MTA. > > > In the [mta] section of mailman.cfg, put > ``` > incoming: mailman.mta.exim4.LMTP > configuration: python:mailman.config.exim4 > ``` > See > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… That is exactly what I have in my mailman.cfg Installing Postfix suppresses that message though. I installed Postfix and then disabled it. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Stephen J. Turnbull

Mark Sapiro writes: > Of course it is logical. You, the person, are a member of the list > so you post to the list should be treated as from a member > regardless of which of your addresses it comes from. > > Why is that a problem? People are not particularly logical about this kind of thing. They want what they want at the moment (compare the discussion with Odhiambo where he wanted the same address to correspond to different users). People with multiple addresses frequently want to separate their outgoing messages as well as incoming messages into separate streams. (Eg, one of the addresses is for specific use on an anonymous list.) But in many cases what they want is as you say, "I" am subscribed so any of my addresses should do. While your explanation that a (human) person who wants that behavior should link separate addresses to separate Users is a perfectly good technical answer, I would not expect typical folks to figure that out for themselves. I don't have a suggestion for a user-friendly UI for this; I think it's just a hard concept to grasp with the amount of effort we generally want to put into a mailing list subscription. It might be a good idea to add this issue to the documentation on anonymous lists. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months, 2 weeks

[MM3-users] Re: Hiding the "subscribe without creating an account"

by Matthew Blissett

On 13/07/2024 07:17, Mark Sapiro wrote: > On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: >> >> Is there a configuration option that does this, or was it a custom >> change made in >> the templates? Was the change made to reduce fake registrations? Did >> it work? > > > It was added in Postorius 1.3.9. See the UI section at > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 > > Yes, the change was made in an attempt to reduce fake registrations. > > We haven't really studied it's effectiveness. It seems to help > somewhat, but it also seems that bots may already have a template to > POST so removing it from the UI is not a complete solution. They would be missing the CSRF token (a hidden field on the anonymous signup form) so this ought to fail. > There is also a lot of email to innocent third parties and > non-existent addresses from attempts to register them for an account. There are patches to integrate a Captcha system here: https://gitlab.com/mailman/django-mailman3/-/issues/33 I think it's needed, as less than 24 hours after migrating to Mailman 3 I already see bots retrieving the signup form to get the CSRF token (GET /accounts/signup/?next=/postorius/lists/) then POSTing the request for a new user account (POST /accounts/signup/). There's also the setting ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False, which prevents spam from the "forgot password" address, see https://gitlab.com/mailman/postorius/-/issues/591 -- Matt

1 year, 5 months

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

by Odhiambo Washington

On Wed, Dec 25, 2024 at 8:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/24/24 23:35, Odhiambo Washington via Mailman-users wrote: > > > > Now only if you can help me reconcile the fact that Postorius tells me > that > > I have > > ``` > > List Nonmembers (872) > > > > ``` > > > > ..while the CLI command gives me only 13 addresses. > > > How are you invoking the `mailman nonmembers` command? I suspect it is > not using the proper mailman.cfg. Does `mailman info` show the correct > mailman.cfg. > ``` (venv) mailman@eu:~$ whoami mailman (venv) mailman@eu:~$ mailman info GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman:XXXXXXXXX@localhost /mailmansuite?charset=utf8mb4&use_unicode=1 devmode: DISABLED REST root url: https://localhost:8001/3.1/ REST credentials: restadmin:restpass (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC Agnes <agnesa(a)REDACTED.com> Angela M <angelam(a)REDACTED.org> <beatiemaina!!(a)REDACTED.com> <psgimode(a)REDACTED.ke> <jwothaxxx(a)\REDACTED.ke> <lgichdhdh(a)REDACTED.ke> <mrussher(a)REDACTED.org> <mutwiXXj3(a)REDACTED.com> <news@REDACTED> Nesema <xxxxxx(a)kictanet.or.ke> Robert M <xxxxxxo(a)yahoo.com> <telasalma17@ REDACTED > <wambdddddd(a)REDACTED.ke> (venv) mailman@eu:~$ mailman members --role nonmember LISTSPEC | wc -l 13 (venv) mailman@eu:~$ ``` It uses the correct config file. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months, 2 weeks

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

by Odhiambo Washington

On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < Willie.Castillo(a)caemilusa.com> wrote: > The issue started right after the site's CERT expired. The CERT expired on > 7/8/25. This is what's in the log... > > Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: > HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with > url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by > SSLError(SSLCertVerificatio > nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: > certificate has expired (_ssl.c:1000)'))) > > The CERT has been updated but the 7/25 message is not archived still. While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what is documented so that the issue doesn't recur: ``` [general] base_url: http://127.0.0.1:8000/archives/ api_key: Secret_Hyperkitty_API_Key ``` PS: I haven't seen your responses to @Mark Sapiro <mark(a)msapiro.net>'s questions quoted below: ``` Did the new post get archived? If so, why is last post at still July 25, 2025? If no, why not. The post must go to the archiver to cause the queue to be processed. If the post was archived and the July 25 messages are still queued, what's in Mailman's mailman.log. There should be error messages and tracebacks indicating the issue. ``` -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 2 weeks

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

by Abhilash Raj

On Wed, Feb 27, 2019, at 5:46 PM, worik wrote: > 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? /opt/mailman/core/mailman-extra.cfg Change it in this 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) > _______________________________________________ > 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, 9 months

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

by Thomas Stein

Am 2024-04-25 19:05, schrieb Mark Sapiro: > On 4/25/24 04:35, Thomas Stein wrote: >> >> Traceback (most recent call last): >> File "/usr/bin/django-admin", line 33, in <module> >> sys.exit(load_entry_point('Django==4.2.11', 'console_scripts', >> 'django-admin')()) >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> File >> "/usr/lib/python3/dist-packages/django/core/management/__init__.py", >> line 442, in execute_from_command_line >> utility.execute() >> File >> "/usr/lib/python3/dist-packages/django/core/management/__init__.py", >> line 416, in execute >> django.setup() >> File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, >> in setup >> apps.populate(settings.INSTALLED_APPS) >> File "/usr/lib/python3/dist-packages/django/apps/registry.py", line >> 124, in populate >> app_config.ready() >> File "/usr/lib/python3/dist-packages/allauth/account/apps.py", line >> 15, in ready >> raise ImproperlyConfigured( >> django.core.exceptions.ImproperlyConfigured: >> allauth.account.middleware.AccountMiddleware must be added to >> settings.MIDDLEWARE Thanks for you answer. > This is a packaging issue in the Debian/Ubuntu package and should be > reported to Debian. I already did. https://bugs.launchpad.net/ubuntu/+source/mailman-suite/+bug/2062960 > See the BREAKING CHANGE item in the 1.3.10 section at > <https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst>. > > You need to add `allauth.account.middleware.AccountMiddleware` to the > MIDDLEWARE setting in your Django settings. I'm not sure how to add that to my django settings. Adding: x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x did not help. Any hints? thanks again, t.

1 year, 7 months

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

by Abhilash Raj

On Fri, May 14, 2021, at 2:16 PM, Odhiambo Washington wrote: > On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > > > /usr/local/include/sass > > > > > > That is the only thing found that is in the base system. > > > > And that's the one you want. What is it's mode? > > > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. This sounds like a result of you running `pip3 install sass`, probably with sudo which failed mid-way due to the exception you posted above. Which OS are you using? On debian/ubuntu, you can install: sudo apt install sassc I am not exactly sure how it got removed during your upgrade to the new version of Mailman since it shouldn't affect your system packages. Did you install Mailman initially using system packages or instructions provided at [1]? [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… -- thanks, Abhilash Raj (maxking)

4 years, 6 months

[MM3-users] Re: problem configuring mailman3 on debian bullseye

by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia

Hi, Thank you. I discovered tha I removed all templates but in the db table the template was not removed. It was pointing to localhost and this was the problem. Thanks to all for help! Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it Il 16/03/23 04:20, Mark Sapiro ha scritto: > 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. >

2 years, 8 months

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

by MegaBrutal

Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2025. ápr. 9., Sze, 4:49): > ``` > $ mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > > >>> um = getUtility(IUserManager) > >>> usr = um.get_user('user(a)example.com') # any of the three addresses > >>> usr.addresses > prints a list of the 3 addresses. These are indexed as 0, 1, 2 > >>> usr.preferred_address > prints the preferred address. If this is the one you want to delete, do > >>> usr.preferred_address = usr.addresses[n] # n is the index of one > you want > >>> del usr.addresses[n] # n is the index of the address you don't want > >>> usr.addresses.remove(n) # n is the index of the address you don't > want > >>> commit() > ``` Thanks, I successfully removed my unwanted address, so it now doesn't appear anywhere. (Looks like .remove(n) wasn't needed, it only gave an exception, and the settings were saved even without commit() – which is concerning because I would have assumed that I can cancel transactions by omitting it.) However, the problem still persists: I can't post to the list from HyperKitty. In this regard, nothing has changed since my original report. I'm subscribed to the list with my primary, preferred address, which is the GMail address right now.

8 months

[MM3-users] Re: mail loops back to myself

by Florian Sukup

On 6/9/25 20:54, Mark Sapiro wrote: > On 6/9/25 05:06, Florian Sukup wrote: >> >> The setup has historic reasons. However I can eliminate >> reverse.rrr.com completely and replace it by host.xxx.com. Right now >> reverse.rrr.com has an A-record pointing to the host's ip address. > > Eliminating reverse.rrr.com completely and replacing it by host.xxx.com > would be good. This will help. > First step is done: I replaced reverse.rrr.com by host.xxx.com the DNS zones of all domain I use. Tomorrow I will have the rDNS record be rewritten by my ISP. > Also if I look up the A record for reverse.rrr.com either locally or at > aaron.ns.cloudflare.com there isn't one. This will be moot if you > replace reverse.rrr.com with host.xxx.com. > reverse.rrr.com is not the real name ... > > >>> What is the output from `postconf -n`? >>> >> >> alias_database = hash:/etc/aliases >> alias_maps = hash:/etc/aliases >> append_dot_mydomain = no >> biff = no >> compatibility_level = 2 >> inet_interfaces = all >> inet_protocols = all >> local_recipient_maps = proxy:unix:passwd.byname $alias_maps >> hash:/var/lib/mailman3/data/postfix_lmtp >> mailbox_size_limit = 0 >> message_size_limit = 0 >> mydestination = localhost, localhost.localdomain, arvak > > This needs to include $myhostname > I don't want to receive any emails like ...(a)host.xxx.com . So I thought removing host.xxx.com from $mydestination is a good idea. Is there any other solution for that? Florian.

6 months

[MM3-users] Re: High memory usage

by Philip Colmer

On Thu, 17 Feb 2022 at 01:02, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/16/22 00:18, Philip Colmer wrote: > > Thank you for the replies from Mark and Stephen. > > > > One of the reasons why Prasanth & I are concerned with this specific > system > > is because the first time memory usage crept up, it got to the point > where > > oomkiller stepped in and, as is usual for that particular mechanism, one > of > > the processes it killed was sshd, thus removing access to the system :(. > I > > know that oomkiller can be tuned to stop it killing processes like sshd > but > > it will, nevertheless, start killing *some* processes if it sees an out > of > > memory situation. > > > It sounds like there is a memory leak somewhere. This is an issue with > some versions of Python. I know both Python 3.10.2 and 3.9.10 were > released ahead of schedule to fix this. See > https://bugs.python.org/issue46347 Thanks, Mark. We're using Python 3.8; I've looked at the open issues and don't immediately see any that might be memory-leak related in a way that would affect Mailman 3. That said, there are quite a few libraries and other "moving parts" involved in this project so we're going to try and track memory usage over time by process or similar to see if we can see whether or not this is a leak and, if it is, what the likeliest culprit might be. Philip

3 years, 9 months

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

by kisner＠live.com

Mark Sapiro wrote: > On 7/9/22 8:48 AM, kisner(a)live.com wrote: > > Thanks! > > OK, ran through again on a vanilla Debian 11.3 install, got this error (I'll try to create the directory and see if I can get past it): > > (venv) mailman@lists:~$ mailman-web migrate > > Traceback (most recent call last): > > File "/usr/lib/python3.9/logging/config.py", line 564, in configure > > handler = self.configure_handler(handlers[name]) > > File "/usr/lib/python3.9/logging/config.py", line 745, in configure_handler > > result = factory(**kwargs) > > File "/usr/lib/python3.9/logging/handlers.py", line 445, in __init__ > > logging.FileHandler.__init__(self, filename, mode=mode, > > File "/usr/lib/python3.9/logging/__init__.py", line 1142, in __init__ > > StreamHandler.__init__(self, self._open()) > > File "/usr/lib/python3.9/logging/__init__.py", line 1171, in _open > > return open(self.baseFilename, self.mode, encoding=self.encoding, > > FileNotFoundError: [Errno 2] No such file or directory: '/opt/mailman/web/logs/mailmanweb.log' > > Creation of the directory is documented. From > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configur... > # Make sure that this directory is created or Django will fail on start. > LOGGING['handlers']['file']['filename'] = > '/opt/mailman/web/logs/mailmanweb.log' My bad, I missed that. Maybe pull that line out of the config comments and put it in the instructions below? That wasn't the show stopper, though, that I could figure out, it was the other bug. I'm glad someone already reported it and fixed it.

3 years, 5 months

[MM3-users] Re: Digests not working correctly

by Joel Lord

I ran the "/usr/local/bin/mailman digests --periodic" again, sadly without the --verbose, and it kicked out the digests as it ought to have the first time. Now I have to wait for some list traffic to come in to "recharge" the digests so I have something to test with again. -Joel On 6/13/2023 1:46 PM, Mark Sapiro wrote: > On 6/13/23 09:42, Joel Lord wrote: >> Now I'm on one of the lists in digest mode and I can see that it's a >> mess. Periodic digests are definitely NOT working, so I'll lay that >> out here. >> ... >> root@host2:/# grep digests /var/log/cron.log >> Jun 11 23:00:01 host2 CRON[1632765]: (lists) CMD >> (/usr/local/bin/mailman digests --periodic) >> Jun 12 23:00:01 host2 CRON[2177286]: (lists) CMD >> (/usr/local/bin/mailman digests --periodic) > > > OK. > >> root@host2:/home/members/directory# su - lists >> lists@host2:~$ /usr/local/bin/mailman digests --periodic >> lists@host2:~$ ls var/lists/<list>/ >> digest.mmdf > > > If there is nothing in Mailman's mailman.log, I don't know what the > issue is unless the list's digest_send_periodic flag is False. > > >> How can I try and track this down? > > > Try manually running > ``` > /usr/local/bin/mailman digests --periodic --verbose > ``` > to get more info. Also try > ``` > /usr/local/bin/mailman digests --send --verbose > ``` > to see what it reports and whether it sends the digest. > -- Joel Lord

2 years, 6 months

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

by Stephen J. Turnbull

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

10 months, 1 week

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 5, 2020, at 9:21 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/5/20 8:55 AM, Mark Dadgar wrote: >> I moved my mail server to a Digital Ocean droplet. I basically installed all the appropriate packages and then rsync’d everything that matters from my metal server up to the cloud instance. Everything more or less works fine. >> >> However, I am now getting this hourly error - see below. > ... >> [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 36301): Term too long (> 245): XSUBJECT95251413 >> Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update >> backend.update(index, current_qs, commit=commit) >> File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 488, in update >> database.replace_document(document_id, document) >> xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413 > > > This error comes from Xapian. It is due to a (new) message in your > archive that contains a 'word' longer than 245 characters. > > There is a PR at > <https://github.com/notanumber/xapian-haystack/pull/181> that addresses > this plus another suggested fix in that PR's comment thread. Thanks. I guess I wait for them to roll the fix in and the ubuntu maintainers to pick it up. > Note: I got there by googling "xapian term too long" which gave > <https://github.com/notanumber/xapian-haystack/issues/153> as the first > hit and that led me to the above. Yeah, that would have been smarter. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 7 months

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

by Odhiambo Washington

On Wed, Feb 1, 2023 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/31/23 23:33, Odhiambo Washington wrote: > > Is this a race condition? > > > > <CUT> > > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > > Traceback (most recent call last): > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/django_extensions/management/commands/runjobs.py", > > line 40, in runjobs > > job().execute() > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/jobs/update_and_clean_index.py", > > line 37, in execute > > run_with_lock(update_index, remove=True) > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/lib/utils.py", > > line 181, in run_with_lock > > log.exception("Failed to update the fulltext index: %s", e) > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > > line 470, in __exit__ > > self.unlock() > > File > > > "/opt/mailman/mm/venv/lib/python3.9/site-packages/flufl/lock/_lockfile.py", > > line 420, in unlock > > raise NotLockedError('Already unlocked') > > flufl.lock._lockfile.NotLockedError: Already unlocked > > <CUT> > > > Yes, it is a race between the monthly hyperkitty update_and_clean_index > job and the hourly hyperkitty update_index job > Okay. This is a bit off from my understanding. What is the cause and how do I mitigate it? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Verification emails 'helo' rejected

by Greg Newby

Success! Below: On Wed, Oct 16, 2024 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/24 12:42, Greg Newby via Mailman-users wrote: > > > > Here are the corresponding logfile entries from mailmanweb.log: > > smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 > <mail>: > > Helo command rejected: need fully-qualified hostname')} > > > > and from mail.log: > > Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from > > localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need > > fully-qualified hostname; from=<root(a)lists.domain.tld> > to=<root@localhost> > > proto=ESMTP helo=<mail> > > > > lists.domain.tld is the domain for Mailman3. I don't know why it's trying > > to send email from root@. > > > I think the mail.log entry is for the DSN for the failure. The issue is > the HELO/EHLO command. Try the following in your venv > ``` > (venv) ...:~$ python > Python 3... > Type "help", "copyright", "credits" or "license" for more information. > >>> import socket > >>> socket.getfqdn() > ``` > If that returns `localhost`, that's the issue. I think you can fix it by > putting a fully qualified domain name in /etc/hostname. > > That was the answer. I had the short hostname, not the fully qualified domain name. Thank you! The logfile messages were pretty confusing since they did not mention the hostname at all. Postfix was not the problem, as you wrote separately. ~ Greg

1 year, 1 month

[MM3-users] Re: Hyperkitty search on Message-ID?

by Bryan Fields

On 12/5/24 2:02 PM, Mark Sapiro wrote: > Message-ID is not one of the fields indexed. These are defined at > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index… Looks like it would trivial to add there. Think anyone would be opposed to adding support for this? > A bit obscure for laypersons, but one can compute the message_id_hash > from the Message-ID > ``` > from base64 import b32encode > from hashlib import sha1 > > def get_message_id_hash(msg_id): > return b32encode(sha1(msg_id).digest()).decode() > ``` This is great to know. I assume the thread ID is generated the same way? > I can't help but wonder though how one has the Message-ID without having > the message. I'm wondering in general how often if ever the layperson > would be searching the archive for a Message-ID. Well I've been working with an import of 34 years of mail archives (200k messages or so), and we have several people spot checking what we have and fixing threading based on their archive. Since they have the message already, it would be easy to search for the message ID for them. The older archives predate RFC2822 by a decade or so and in-reply-to is missing or just wrong on quite a few of them. From what I can see it was migrated from LISTSERV to majordomo in 1993, then to mailman2 in 2008, and what I have for an archive was from the mail to NNTP spool, at least for the pre-1993 list. Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year

[MM3-users] Re: Sudden increase in "***UNCHECKED***" in email subjects

by Dave Clements

Hi Peter and Mark, Thanks for the insight and fixes. We (we being Nate who is also on this list) think it was a lack of virtual memory on the server. This crashed ClamAV and it could not restart. Thus our mail really was unchecked. Restarting processes and cleaning up some things has fixed this. Cheers, Dave C On Sun, Jul 19, 2020 at 4:07 PM Peter Adebahr via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 7/18/20 7:46 PM, Mark Sapiro wrote: > > On 7/18/20 9:30 AM, Dave Clements wrote: > >> Hi all, > >> > >> I have just noticed a big jump in the number of emails going out with > >> "***UNCHECKED***" added to the subject line. > > > > > > This does not come from Mailman. Some milter or other process in your > > MTA or elsewhere in the delivery chain is adding this to the Subject: > > > > Hi Dave, > > I had experienced the same symptom a while ago. For me, it was amavis > doing this. This behaviour could be corrected by adding this line to > amavisd.conf: > > > # $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it > $undecipherable_subject_tag = undef; > # > > Hope it helps :) > > Best regards, > Peter > > _______________________________________________ > 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/ > -- https://bcc2020.github.io/ https://galaxyproject.org/

5 years, 4 months

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

by Shashikanth Komandoor

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

3 years, 8 months

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

by Jeremy Stanley

On 2023-03-23 09:07:02 -0700 (-0700), Mark Sapiro wrote: [...] > 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. And those will also become out of date over time, because Debian is a stable server distribution so intentionally freezes the versions of software it supplies and backports only critical/security fixes to those increasingly outdated versions when warranted. Basically it's a question of whether users value stability with a bit of security support over newest versions of software and new features. The upstream Mailman packages on PyPI (and container images) cater to users who want the latest versions of the software, packages in stable server distros like Debian cater to users who want to safely go years between behavior changes in software. Both are valid choices, it just comes down to the user's specific situation. That said, when you have trouble with the packaged versions of software in Debian, the expectation is that you ask on Debian mailing lists and possibly report bugs in the Debian bug tracker, rather than burdening upstream software maintainers with details that might be specific to choices or mistakes in Debian's packages. The package maintainers in Debian generally forward bug reports upstream if they determine the issue you've encountered isn't related to how it's been packaged, isn't already fixed upstream (in which case they might backport the fix), et cetera. -- Jeremy Stanley

2 years, 8 months

[MM3-users] Re: Member Issue Discovered

by Stephen J. Turnbull

Victoriano Giralt writes: > El vie, 23-10-2020 a las 08:19 -0700, Mark Sapiro escribió: > > > > This would be more difficult for Postorius/Hyperkitty because those > > users are Django users, but that isn't an issue for Affinity. > > > > All of a sudden, an idea has dawned on me ... Wouldn't it be possible for > Postorius/Hyperkitty, both Django applications, to use Mailman core user > model as their User model? It is just a setting for Django > (AUTH_USER_MODEL). I find the "just a setting" claim a bit implausible. I suspect a certain amount of replumbing of Postorius and HyperKitty will be necessary to get it to work. Most important, the "AUTH_" is pretty scary. Mailman core has *no* authentication built in. It is assumed to be firewalled off from the rest of the world with only access from Postorius and HyperKitty permitted. Can you expand on how hard it would be to do this? Remember that some Mailman instances are either big targets (eg, Apple) or require good security for content reasons (lists for doctors' patient support groups, domestic violence support groups). This is not a great authn/authz model in the modern Internet, but as far as I can see changing it is going to be quite a lot of work, and none of us are authentication specialists (although Abhilash did study security, I don't think he specialized in authentication tech) -- providing reasonably reliable and secure authentication services, especially "social auth" (OpenAuth, OpenID etc) is an important reason we went with Django in the first place. Steve

5 years, 1 month

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

by Bryan Fields

On 7/25/24 7:04 PM, Mark Sapiro wrote: > On 7/25/24 11:20, Bryan Fields wrote: >> When this happens, I get an email error below. > > > This is really wierd. See below. > >> line 88, in reverse >> return resolver._reverse_with_prefix(view, prefix, *args, **kwargs) >> File >> "/opt/mailman/venv/lib/python3.10/site-packages/django/urls/resolvers.py", line 828, in _reverse_with_prefix >> raise NoReverseMatch(msg) >> >> Exception Type: NoReverseMatch at >> /archives/list/nanog(a)nanog-mm3.keekles.org/ >> Exception Value: Reverse for 'hk_archives_with_month' with keyword >> arguments '{'year': 999, 'mlist_fqdn': 'nanog(a)nanog-mm3.keekles.org', >> 'month': 12}' not found. 2 pattern(s) tried: >> ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$', 'hyperkitty/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$'] >> Raised during: hyperkitty.views.mlist.overview > > > It appears to be trying to get the threads for December, 999. > > What do these queries show? > > SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; > > SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; mailman=> \c mailmanweb You are now connected to database "mailmanweb" as user "mailman". mailmanweb=> SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; id | thread_id | date_active | category_id | mailinglist_id | starting_email_id -------+----------------------------------+------------------------+-------------+----------------+------------------- 35670 | GHLCKUC7TDEBAI27SKRQN5PWX3TGB26Q | 0102-04-15 20:06:12+00 | | 3 | 150555 (1 row) mailmanweb=> SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; id -------- 136872 150555 (2 rows) Does this mean it imported archives with an invalid date somehow? Thanks, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year, 4 months

[MM3-users] Re: redirecting -bounces replies

by Hirayama, Pat

HI Mark, On 6/26/25 13:16, Mark Sapiro wrote: >On 6/26/25 11:37, Hirayama, Pat wrote: >> >> When I look at the domains in mailman-core, I see: >> >>>>> show_domains() >> <Domain fhcrc.org> >> <Domain fredhutch.org> >> <Domain lists.fhcrc.org, , alias: lists.fredhutch.org> >> <Domain lists.hanc.info, , alias: > >> - owner: cit-sys-engineering(a)fredhutch.org > > >This is part of the problem. The alias domain for a list should not be a >real domain. Apparently, someone set this up so that mail to lists in >the lists.fhcrc.org domain would go to the corresponding list in the >lists.fredhutch.org domain. I think that may actually work, but you need >more. In order to add recipients to the patest-bounces addresses, the >recipient domains need to have an alias domain. In the cases below the >domains lists.fredhutch.org and lists.hanc.info. E.g set an alias domain >for lists.fredhutch.org to x.lists.fredhutch.org and for >lists.hanc.info to x.lists.hanc.info. Ah, I think that makes sense. So, add the alias domains here or through the CLI: [cid:3f6bbb96-1ec3-4bdd-9a59-991fc9d1e31b] Oh, does the alias domain x.lists.hanc.info (etc) need to be resolvable in DNS, or will it be internal just to Mailman? Thanks, -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Replaced multipart/alternative part with first alternative.

5 months, 2 weeks

[MM3-users] Re: Disable Sign-up per domain

by Mark

On 2025-08-01 19:40, Mark Sapiro wrote: > Please confirm that the issue only occurs with the modified > /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py > and does not occur with the original .../user_adapter.py. > Hi Mark, In working through this I reverted the test server (which had the working "Disable") back to original, then re-applied the changes, and now I'm getting the same errors as on the Production server. I think it might be me screwing up somewhere. It's doing my head in today so I'll sleep on it and have another crack at it tomorrow. STEPS TAKEN =========== 1. Reset the "Test" server back to original. (a) I put the original "user_adapter.py" back in place. It contains: ... def is_open_for_signup(self, req): return False ... (b) Ensured that "settings.py" had the following completely removed: ... ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ... (c) systemctl restart mailman3 systemctl restart mailmanweb (d) Reloaded browser with "lists" page for each domain and clicked "SignUp" on each. Result: As expected, both domains correctly displayed their SignUp pages. ----------- 2. Made the following changes to the "Test" server. (a) Edited /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py It now contains: ... # def is_open_for_signup(self, req): # return False def is_open_for_signup(self, req): if req.META['HTTP_HOST'] == 'lists.MYDOMAIN.COM': return False else: return True ... (b) Appended to - /etc/mailman3/settings.py - the following: ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' (c) systemctl restart mailman3 systemctl restart mailmanweb Result: 502 Bad Gateway page and log shows ... raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. ===========

4 months, 1 week

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 15/2/21 16:57, Mark Sapiro wrote: > Finally, although I said previously that the translated templates should > be submitted as a merge request, that can still be done, but is not > necessary. They can be translated in weblate. See > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > and<https://gitlab.com/mailman/mailman/-/issues/825>. I had the templates translated now in UTF-8 coding map. I copied all of them en a new directory (es) under mailman package templates (as I can see are other languages): /usr/local/lib/python3.7/site-packages/mailman # ls templates __init__.py de es it __pycache__ en fr sk /usr/local/lib/python3.7/site-packages/mailman # ls templates/es domain:admin:notice:new-list.txt list:member:regular:header.txt help.txt list:user:action:invite.txt list:admin:action:post.txt list:user:action:subscribe.txt list:admin:action:subscribe.txt list:user:action:unsubscribe.txt list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt list:admin:notice:disable.txt list:user:notice:hold.txt list:admin:notice:removal.txt list:user:notice:no-more-today.txt list:admin:notice:subscribe.txt list:user:notice:post.txt list:admin:notice:unrecognized.txt list:user:notice:probe.txt list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt list:member:digest:header.txt list:user:notice:rejected.txt list:member:digest:masthead.txt list:user:notice:warning.txt list:member:generic:footer.txt list:user:notice:welcome.txt But mailman isn't aware of them (I restarted the server). May I have to execute some process as "compilemessages" to mailman be capable to use them? Now mailman is using the "en" templates for sure. After testing them I'll do both of the suggestionsyou made: a merge request AND the revision and translation via Weblate.

4 years, 9 months

Search results for query "sapiro"