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

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Mark, RE: The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. I ran mailman aliases and the first try got can't read main.cf. I granted read-only access to other on the file, the next mailman aliases command ran without errors, but I don't know if it did anything or not, e.g. nothing in postfix_domains or the lmtp files. How can I verify that "mailman aliases" worked? Thanks, ---------- Keith On Wed, Jul 3, 2024 at 2:52 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > 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 keith1christian(a)gmail.com

1 year, 4 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman Core.

by Shashikanth Komandoor

Thank you Mark for your response. I understood that gunicorn is a front end that is used like web server like nginx. But I don't think I am using it instead I am using the httpd to redirect requests to postorius. And I am starting the mailman-suite with the command "python manage.py runserver 0.0.0.0:8000 --insecure &". Hope this does not use gunicorn (which of course I don't know what it is until now). Please correct me if any point I am mentioning is wrong. So, in this case, do you think configuring gunicorn as below would work: *calling gunicorn.cfg in mailman.cfg as below * *[webservice]* *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* *and content of gunicorn.cfg as below* *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.* *workers = 4graceful_timeout = 90* Also what is the difference between timeout and graceful_timeout ? Please help me if I can increase the management better. Any guide is also helpful for me. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jul 23, 2020 at 4:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:21 AM, Shashikanth Komandoor wrote: > > Hi Mark, > > > > Never mind please I am sending to you only instead of group as I am > > sending you the production content along with the mail. > > > See my other reply. > > > > I have configured the workers count as 4 and timeout as 900 in > > mailman.cfg under [webservice]. This is FYI. > > You can't configure Mailman's REST gunicorn workers directly in the > [webservice] section of mailman.cfg. The only thing you can configure > there is: > > configuration: /path/to/gunicorn.cfg > > That file, which is separate from your web server gunicorn.cfg, is where > you put things like > > [gunicorn] > timeout = 900 > > It also will not work to put a gunicorn section in mailman.cfg. It must > be in a separate file pointed to by webservice.configuration. > > Increasing the number of workers won't help this issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 3 months

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

by Thomas Ward

On 10/23/23 22:57, Abhilash Raj wrote: > On 10/23/23 20:37, Thomas Ward via Mailman-users wrote: >> I want to add a custom handler that implements customized thread IDs >> in the system. I already have the DB logic worked out, but the >> documentation for plugins is NOT clear on how to define a handler in >> a plugin, nor does the example plugin in the documentation on Gitlab >> have any custom handlers. >> >> I'm looking to add a custom handler so that the private pipeline for >> threaded-subject-list can use thread-subject (the custom handler) >> instead of subject-prefix (builtin). > > https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/plugins/testin… > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… > > > These are two places you can find docs for an example plugin that > ships with Mailman's code. Adding a new "component", like a Handler, > works very similar to the "rules" in the example shown above. Yeah these're helpful, but the problem I was running into was file naming schema - I was not aware it's always PLUGIN/COMPONENT/COMPONENT.py in the naming, which it was not entirely clear about. It makes sense now that I look back, but it never hurts to get clarification. > > You will probably need a directory tree like: > ``` > example/ > __init__.py > hooks.py > handlers/ > __init__.py > handlers.py > ``` > > Installing the handler is same as per shown in docs using below (do > note that the above example is the name of the package that is > importable): > > > <snip> > > Finally, you can verify that your handler was loaded properly using > something along the lines of: > > ``` > $ mailman shell > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > > >>> for each in config.handlers: > ... print(each) > ... > <snip> The only other thing that was missing is how to set up the proper code for a Handler implementation/class, which I used an existing mailman3 core plugin as an example to just run with for testing purposes. There are notes in the example plugin on Gitlab and the documentation that "other components will be added as examples eventually" but that was well over a year ago, so we'll see how that ages. Thanks for the assist! Thomas

2 years

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

by Jana Berger

On 24.09.2023 16:52, Mark Sapiro wrote: > On 9/24/23 07:20, Stephen J. Turnbull wrote: >> >> The only thing I can think of at the moment that might move the >> discussion forward is if Mark knows how to run his test in your Docker >> environment to see if it also produces >> Content-Type: text/plain; charset="US-ASCII" >> Content-Transfer-Encoding: 7bit > > Assuming there is not something like > ``` > [language.en] > charset: utf-8 > ``` > in your mailman.cfg overriding the default us-ascii charset for > English, if you send a message From: yourself to > list-confirm-xxxxxxx(a)example.com with Subject: Re: Your confirmation > is needed to join the list(a)example.com mailing list (replacing list > and example.com with the actual list and domain), you should receive a > response like (some headers removed) > ``` > Subject: The results of your email commands > From: list-bounces(a)example.com > To: mark(a)example.com > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Message-ID: <169556563227.2592.7908020161516725770(a)example.com> > Date: Sun, 24 Sep 2023 07:27:12 -0700 > Precedence: bulk > X-Mailman-Version: 3.3.9b1 > List-Id: A test list <list.example.com> > List-Help: <mailto:list-request@example.com?subject=help> > List-Owner: <mailto:list-owner@example.com> > List-Subscribe: <mailto:list-join@example.com> > List-Unsubscribe: <mailto:list-leave@example.com> > > The results of your email command are provided below. > > - Original message details: > From: Mark Sapiro <mark(a)example.com> > Subject: Re: Your confirmation is needed to join the > list.example.com mailing list. > Date: Sun, 24 Sep 2023 07:27:10 -0700 > Message-ID: <20230924142710.GA23819(a)example.com> > > - Results: > Confirmation token did not match > > - Done. > > ``` > What do you get? > Well, that confirms it. I send the mail from an account at GMX and received the Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 with a properly (!) base64-encoded message body. I then send the mail both from my own mail system (which is also the one being used by Mailman) and got Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" with no encoding on the message. Lastly, I send the same mail from a GoogleMail account, which also received Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" with no encoding. ... which means this is almost surely a bug in the MTA of GMX, which will be much, much more difficult and unlikely to be fixed - that is why I had hoped for this to be an issue in/with Mailman ;) Thank you for the pointers and help!

2 years, 1 month

[MM3-users] MM3 Postfix FROM header issue

by Stephen J. Turnbull

eboltz(a)lhtservices.com writes: > When I check the /var/log/mail.log without the > sender_canonical_maps setting enabled, The meaning of "canonical" here is that this is the original and universally acceptable accept-no-substitutes-or-aliases version of the sender's address. If you don't want to see it *literally everywhere* in the header of a message coming out of Postfix, you shouldn't put it in a canonical_map. > then the initial email sender is either rejected because 'Recipient > address rejected: User unknown in virtual alias table' Postfix is configured to relay only local senders to anywhere, or remote senders to local recipients and to relay_domains. This means that the list address doesn't look like a local address (I think it's a bad idea to set myhostname=localhost!) and it isn't in relay_domains (not sure why that might be if the postfix_domains file is present as a compiled .db), so the last try is virtual address (Postfix's way of delivering a possibly remote recipient address to a local recipient). You should use postconf to check that all of the my* variables are set sanely. > or '550-From header sender domain not verified (example.com) > 550-On your sending Verified senders page > 550 verify the sender domain or email to be allowed to send' Not sure where the "example.com" is coming from. If that is being set by the remote smtpd (smtp2go?), and isn't a hard-coded string, something's wrong either with your Postfix configuration or your test email -- that should be the envelope sender domain, which should be your host. The example.com domain actually exists, and I'm sure it doesn't allow you to send email! As others mention, you probably need to have a valid SPF record in your DNS for your host as well. > Here is my main.cf setup Check that both the .txt (produced by Mailman) and .db (produced by /usr/sbin/postmap) files exist for the postfix_lmtp and postfix_domains maps. The function that produces the .txt source is supposed to call postmap to generate the compiled .db database, you shouldn't need to do it by hand. But that's the only Mailman-specific reason for the "not in virtual address table" message. Postfix itself only looks at the .db file, it will not compile or even read the .txt. > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains Make sure there are no Mailman mailing lists in the aliases file. > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases As mentioned, this is not a good idea: > myhostname = localhost Steve

1 year, 10 months

[MM3-users] Re: Clearing webserver cache - Nginx

by Odhiambo Washington

On Wed, Aug 7, 2024 at 2:08 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/6/24 14:27, Mark Sapiro wrote: > > > > Is this with only one browser? It's a long shot, but clearing browser > > cache might work. > > > Actually, I see the same issues from my browsers, so it's not a browser > caching issue. The only thing left is nginx caching, but, while I know > very little about nginx, I think it doesn't cache by default and I don't > see where in your posted config it's enabled. Perhaps there's more in > your config that you didn't post. > There is nothing I didn't post :) I finally found a way to purge the files cached by Cloudflare. It's in their Dashboard. But not before I had migrated everything to apache2! So now I have all my sites configured in both webservers and I can use whichever I like. Right now I am using apache2, but I am seeing something odd: https://mm3-lists.kictanet.or.ke/archives/ is empty. Is this normal? I am expecting my most active list to appear there or am I overthinking? Like this: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… > If there is a proxy_cache_path directive in your config try > > find /the/proxy/cache/path -type f -delete > > to clear the cache. > There isn't. All the caching mess was coming from Cloudflare proxy servers. If you host your DNS with CF, you will realize they proxy/cache your traffic by default unless you turn that off when creating an A record. As a last resort, your /opt/mailman/mm/static/CACHE/ directory should > contain a css/ directory with 3 files and a js directory containing one > file and a manifest.json file with a template for the `link` directives > referencing those files. > I have seen those files. The js/ directory is easy as its only one file, so your server is > looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create > a symlink in the js/ directory from output.3aaa7705d68a.js to the actual > file. For the css directory, your server is looking for > output.158acc288604.css and output.6dab123e4897.css, and I don't see the > third file in the logs you posted, but if I go to pages in your archive > that I see as unstyled and look at the stylesheet references, they are > to output.44ea6c55e917.css, output.e68c4908b3de.css and > output.9efeb5f3d52b.css so you could just symlink those to the actual > files, it doesn't matter which as all three are loaded on each page I did the symlinks and they helped with nginx, but because I have never had to do that before, I did not like it. That's why I switched to apache2 to see what the effects are and apache2 had/has no problem. Because I have purged the CF cache, I reverted back to nginx and to see from the logs what they are looking for: ``` root@eu:/opt/mailman/mm/static/CACHE/js# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:19:55 [error] 2403078#2403078: *62 open() "/usr/share/nginx/html/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.111, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/" ^C root@eu:/opt/mailman/mm/static/CACHE/js# cd ../css/ root@eu:/opt/mailman/mm/static/CACHE/css# ls -al total 196 drwxr-xr-x 2 mailman mailman 4096 Aug 16 16:55 . drwxr-xr-x 4 mailman mailman 4096 Mar 21 15:55 .. -rw-r--r-- 1 mailman mailman 1209 Mar 21 15:55 output.d29798365ddb.css -rw-r--r-- 1 mailman mailman 569 Mar 21 15:55 output.e68c4908b3de.css -rw-r--r-- 1 mailman mailman 180904 Mar 21 15:55 output.e69dbb26da3b.css root@eu:/opt/mailman/mm/static/CACHE/css# ``` So I am left wondering why nginx is prefixing "usr/share/nginx/html" to /static. I then decided to specify a root directive in the vhost pointing to /opt/mailman/mm/static, and I saw nginx prefixing that path to the /static/ again: ``` root@eu:/opt/mailman/mm/static/CACHE/css# cp /dev/null /var/log/nginx/mm3-lists_error.log root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:28:11 [error] 2404382#2404382: *239 open() "/opt/mailman/mm/static/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.112, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` Finally, I changed the root directory to /opt/mailman/mm and this time, I see nginx getting the path correctly, but still looking for the same nonexistent file from above and another file: ``` root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:32:25 [error] 2405076#2405076: *38 open() "/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 172.70.111.112, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:36:17 [error] 2405080#2405080: *841 open() "/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No such file or directory), client: 108.162.238.56, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` From the above logs, that IP making requests is not my IP! It's the CF proxies. I then disabled the A record proxying for the site and accessed it from a browser that I havven't used in months, and there was still some errors: The IP showing is my IP. ``` root@eu:/opt/mailman/mm/static/CACHE/css# systemctl restart nginx root@eu:/opt/mailman/mm/static/CACHE/css# tail -f /var/log/nginx/mm3-lists_error.log 2024/08/16 17:41:11 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/css/output.44ea6c55e917.css" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.44ea6c55e917.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:41:11 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/css/output.9efeb5f3d52b.css" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/css/output.9efeb5f3d52b.css HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " 2024/08/16 17:41:12 [error] 2406218#2406218: *267 open() "/opt/mailman/mm/static/CACHE/js/output.3aaa7705d68a.js" failed (2: No such file or directory), client: 185.199.102.24, server: mm3-lists.kictanet.or.ke, request: "GET /static/CACHE/js/output.3aaa7705d68a.js HTTP/2.0", host: " mm3-lists.kictanet.or.ke", referrer: " https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… " ``` And the issue is something about accessing the archives. Not sure if there is something to do for nginx to behave. Apache does not display any single error. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: Mailman Core 3.2.2 is now out

by Abhilash Raj

On Sat, Mar 30, 2019, at 1:11 PM, Danil Smirnov wrote: > Hi Abhilash, > > Docker builds are failing for the last few days so we don't have this > update in the images: > https://circleci.com/gh/maxking/docker-mailman/tree/master > > Could you look at the issue please? Yes, thanks for letting me know. I am aware of the failing builds, but I am having some weird issues getting uwsgi to start off with recent releases and I don't want to pin versions, so I have been trying to dig into the reason why it doesn't boot up with new releases. And then my local docker has been misbehaving a whole lot too, but I am on it whenever I can :) > > Best regards, > Danil Smirnov > > вс, 24 мар. 2019 г. в 07:59, Abhilash Raj <maxking(a)asynchronous.in>: > > > Hello Everyone, > > > > Mailman Core 3.2.2 is released and available on PyPI[1]. > > > > This is a regular bugfix release and I had to do that to fix a version > > constraint > > which pulled in a pre-release of a dependency (falcon) when installed via > > pip > > and caused the default install to break. > > > > There are few other changes included in this release, including a big > > refactor > > of error reporting in Core's REST API. All the error responses are now > > correctly > > formatted as JSON with more information about the error. For example, > > invalid > > inputs for Enum data types return the valid options. Other error message > > are > > now generated from the input validtor and will be more informative. > > > > REST API also accepts input as JSON formatted body, alongside the > > x-www-form-urlencoded. > > > > A full list of changes are available here: > > > > > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 > > > > This release supports Python 3.5-3.7. > > > > Thanks very much to all the contributors involved in this release. > > > > > > [1]: https://pypi.org/project/mailman/ > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

Hi Mark, Thank you Mark and Phil for your help. It seems I got stuck! 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" 2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size 3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 18, 2020 4:00 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, > you can set max_message_size in your list configuration. It defaults > to 40; units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 1 month

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/8/25 11:27, dap1--- via Mailman-users wrote: > Yes, everything is from the virtual environment and there were no errors reported anywhere during the process. > > <venv> $ ls -l /opt/mailman/var/etc > total 4 > -rw-rw---- 1 mailman mailman 501 Oct 19 11:07 mailman.cfg > > The sqlite line bothered me from the beginning. Shouldn't it be mysql? I'm still concerned that `mailman info` reports the config at /opt/mailman/var/etc/mailman.cfg instead of /etc/mailman3/mailman.cfg. The database is sqlite because thats what's defined in /opt/mailman/var/etc/mailman.cfg. Did you create /etc/mailman3/mailman.cfg? what does diff /etc/mailman3/mailman.cfg /opt/mailman/var/etc/mailman.cfg give? You are not seeing the list in mysql because Mailman core is using the sqlite db at /opt/mailman/var/data/mailman.db > <venv> $ ls -l /opt/mailman/var/data > total 300 > -rw-rw---- 1 mailman mailman 274432 Nov 1 14:40 mailman.db > -rw-rw---- 1 mailman mailman 343 Nov 1 14:39 postfix_domains > -rw-r----- 1 mailman mailman 12288 Nov 1 14:39 postfix_domains.db > -rw-rw---- 1 mailman mailman 1003 Nov 1 14:39 postfix_lmtp > -rw-r----- 1 mailman mailman 12288 Nov 1 14:39 postfix_lmtp.db The postfix files are good, but the mailman.db is spurious because the mailman.cfg that the mailman command is using most likely doesn't define a [database] section and gets the default from https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… The [database] you have defined in mailman.cfg as [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman:pppppppp@localhost/mailman?charset=utf8mb4&use_unicode=1 is presumably defined in /etc/mailman3/mailman.cfg which isn't being used. What is the content of /opt/mailman/venv/bin/mailman? Do you have the environment variable MAILMAN_CONFIG_FILE set? > I did this import command: > > <venv> $ mailman import21 lllllllllllll(a)ddddddddd.net /tmp/config.pck Which works but imports to the list defined in the sqlite database at /opt/mailman/var/data/mailman.db. > This was the hyperkitty command: > > <venv> $ mailman-web hyperkitty_import -l lllllllllllll(a)ddddddddd.net /tmp/lllllllllllll.mbox > > <venv> $ mailman-web diffsettings|grep DATABASES > DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailmanweb', 'USER': 'mailma > n', 'PASSWORD': 'ppppppppp', 'HOST': 'localhost', 'PORT': '3306', 'OPTIONS': {'charset': 'utf8mb4'}, > 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'CONN_HEALTH_CHECKS': False, 'TIME_ > ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'MIGRATE': True, 'MIRROR': None, 'NAME': N > one}}} This looks correct. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 day, 6 hours

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

by Andrew Hodgson

Hi. Seems other people have had this on Office365 when I searched the specific error. I have enabled VERP now on probes and all list messages so lets see if that improves things. Thanks. Andrew. -----Original Message----- From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 12:22 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to andrew(a)hodgson.io

2 years, 1 month

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Andrew Hodder

Well, that can't be true, I'm running DEBUG = False and Django is certainly trying to provide static files (as you'll see below): I found the issue in the nginx logs (it's connecting to both postorius and hyperkitty via uwsgi), it appears when I'm only viewing Hyperkitty's pages, I'm getting these type of errors (some changes inserted to hide my server details): 2017/11/01 19:22:04 [error] 64082#0: *75 open() "/opt/mailman/postorius/ example_project/static/CACHE/js/4ce1260ef558.js" failed (2: No such file or directory), client: 10.10.44.29, server: blah.blah.blah, request: "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1", host: "blah.blah.blah", referrer: "https://blah.blah.blah/hyperkitty/hyperkitty/list/ mailinglist(a)domain.com/2017/10/" So it appears Hyperkitty is attempting to load static files from postorius's side instead of it's own (I have postorius running under https://domain.tld and hyperkitty running under https://domain.tld/hyperkitty/ via nginx). I checked and confirmed the variables in settings.py: STATIC_ROOT = os.path.join(BASE_DIR, 'static') STATIC_URL = '/hyperkitty/static/' STATICFILES_DIRS = ('/opt/mailman/hyperkitty/example_project/static/') And for good measure, here's the nginx config: ------------------------------ server { listen 80; server_name DOMAIN.TLD; #Redirect to SSL if ($scheme = http) { return 301 https://$server_name$request_uri; } } server { listen 443 ssl http2 default_server; listen [::]:443 ssl http2 default_server; server_name DOMAIN.TLD; ssl_certificate "/etc/pki/nginx/DOMAIN.TLD.crt"; ssl_certificate_key "/etc/pki/nginx/private/DOMAIN.TLD.key"; ssl_session_cache shared:SSL:1m; ssl_session_timeout 10m; ssl_ciphers HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on; location / { include uwsgi_params; uwsgi_pass unix:/opt/mailman/postorius.sock; } location ~ /hyperkitty(?<path_info>/.*|$) { include uwsgi_params; uwsgi_pass unix:/opt/mailman/hyperkitty.sock; uwsgi_param PATH_INFO $path_info; uwsgi_param SCRIPT_NAME /hyperkitty; } #Make nginx aware of postorius static location /static/ { alias /opt/mailman/postorius/example_project/static/; } #for hyperkitty static location /hyperkitty/static/ { alias /opt/mailman/hyperkitty/example_project/static/; } error_page 404 /404.html; location = /40x.html { } error_page 500 502 503 504 /50x.html; location = /50x.html { } } Any thoughts would be appreciated, I'm getting stumped on this one. Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Fri, Oct 27, 2017 at 11:01 AM, Simon Hanna <simon(a)hannaweb.eu> wrote: > > On 10/27/2017 04:58 PM, Andrew Hodder wrote: > >> Sure thing: >> >> https://imgur.com/a/EXv3B >> >> Looks like your stylesheets aren't loaded. > > if you are running in production (with DEBUG=False) django won't serve > static files > You need to configure your webserver to do that. > You need to make sure to load all the static files using > `python manage.py collectstatic` > to gather everything and put them in one directory that can then be served > by your webserver > > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years

[MM3-users] Re: Monthly job failure

by Abhilash Raj

On Wed, Jun 26, 2019, at 2:46 AM, andrew.bernard(a)gmail.com wrote: > Hi Mark. Indeed, I am confused. I am not yet familiar with Hyperkiity > internals and code, and I must say it is currently like fog to me. :-) > > Indeed, rebuild_mailinglist_cache_for_month made me think this was a > monthly job. > > I had made some lists and deleted them shortly thereafter. I managed to > add some lines likes raise Exception(locals()) in some of the code, > which revealed that a deleted list was being referred to. I have no > idea how to purge this. I looked everywhere in every table in the > database to find references to the deleted table, to no avail. I > deleted all the queued, jobs in Django, to no avail. I rebooted three > times to no avail (highly unscientific), And now, for no obvious > reason, the error has stopped appearing. it definitely did not stop > after deleting Django queued jobs - although perhaps something takes > time to propagate, or there is something stuck cached in RAM? > > It's nice that it stopped but I feel a bit uncomfortable that creating > a list and deleting it a couple of hours later can cause the log to > fill up every minute with these tracebacks. The exception raised in the > code simply says <MailingList matching query does not exist>. It would > be great if the error could name the list. I think that would be > helpful. It would make it clearer to people what is happening at least, > a lot faster. Python tracebacks don't show the values of local > variables, unfortunately. The delete functionality isn't completely implemented yet and part of the problem lies in the way MailingList, Thread and Email objects are created in Hyperkitty. What you need to know is that once a MailingList has been created, several (routine and event based) tasks are added up in a queue. If at the time those tasks are ready to be executed, the mailinglist has gone away, it prints those errors. IMO, it is mostly harmless, but I can see so much of errors in logs would be worrisome to users. Right now, errors are logged unconditionally, but it is possible to filter them to skip `MailingList does not exist errors` altogether. Ofcourse, that is not the ideal solution, but I think it should at least stop the exceptions from being logged when us or the user can't do anything about it. > > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 4 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Please help me understand what steps are missing and I will try to > >> provide the information. > > > > > > Okay. > > > > At the installation stage, you say the following: > > "I already had some things set up in /opt/mailman including a git > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > postorius projects. On the third server I have added mailman-suite > > because I use the settings.py from that project as the basis for mine." > > > > Please assume that the reader is a newbie to python3 virtualenv and give > the > > details of the commands they need to execute to (a) clone all the > projects > > needed > > and (b) create the virtualenv. > > > > The next steps are: > > mkdir /opt/mailman/mm > > > > Then you say "I then created a /opt/mailman/mm directory and within that > a > > Python 3.6 virtualenv" > > What happens here is something that needs clarification, because you are > > specific about "python3.6". > > I have googled and realized that one has to be specific about the python > > version they want to use in their virtualenv > > as shown here -> > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > exact command to execute to create the /opt/mailman/mm/venv > > exact command to execute to activate virtualenv > > > I have added a comment to the page which I hope gives you what you want. > > I also added a section on templates instead of referring to a prior > version of the page. > That makes it better. However, as a newbie, something is not yet clear: "When active in a particular shell, it can be deactivated with the command deactivate or by exiting that shell." HI am trying to understand the effect of detaching from a venv. I am assuming that a virtualenv is a container that is supposed to be always active for the services within to be accessible. Is that right? So, how do I ensure it's always running/up, or that does not matter as the scripts which run the services will always refer to the files? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 10 months

[MM3-users] Re: Deliverability and Spam Filtering

by Abhilash Raj

On Thu, Jan 30, 2020, at 8:44 AM, tom(a)gather.coop wrote: > Hi folks! First time poster, long time Mailman user. > > I am setting up a new Mailman 3 instance, and am super excited about > the REST API. I plan to use it to enable tight integration with a > separate web app that I maintain. > > As I am setting up the mail server, I am wondering about two related > things: deliverability (for outgoing mail) and spam filtering (for > incoming mail). > > What solutions have folks used for these? I know it is generally common > now to outsource this critical task to a cloud provider like Mailgun or > etc. Have folks needed this or is running ones own incoming and > outgoing mail not a big deal? So many horror stories out there... > > As far as Mailgun goes, I think it should be straightforward to > configure it for outgoing mail, but I'm not sure how I'd use it for > incoming. Mailgun can forward mail via HTTP or to another email > address. Neither I think would work out of the box. It would be great > if there were a REST API endpoint for incoming mail, but I don't think > such a thing exists, right? Perhaps I could add one? There does exist a way to insert messages into Mailman via REST API, if you want to do that. It is done via Queue API, which exposes the internal store where messages sit after they are received from LMTP before they are processed. You can just inject the message in "IN" queue and it should be processed like a regular incoming message. https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/queues.html Although, it seems to only accept string representation of Email, which may not be ideal for your use case. It might be some work to make it work for raw bytes. > > Another thought I had was that I could write a simple HTTP server that > receives mail from Mailgun and forwards it to Mailman via LMTP. But it > seems simpler to go right to Mailman's core API given that one exist > already. > > Or am I thinking about this all wrong? Are there other more suitable > services out there? I looked for cloud MTA providers but didn't turn up > much except for in the large enterprise space, which I'm sure I can't > afford. > > Thanks for any thoughts! > _______________________________________________ > 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, 9 months

[MM3-users] Re: Mailman backend maintenance task

by Abhilash Raj

> On Aug 24, 2021, at 11:22 AM, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > > Eugenio Jordan (external) writes: > >> The idea we were considering was more or less stopping all of the >> components, then starting up only PostGRESQL, and then performing each >> one of the mentioned tasks. > > In that case, your Mailman installation will basically be down (no web > presence, no deliveries) for the duration of the database maintenance. > >> You mention that regardless the connectivity that >> Mailman's core processes might have with the database, the emails will >> be received by and queued until the connection is back again and they >> can be delivered to the distribution lists' members. Could you please >> confirm whether this task would be actually delegated to Postfix (or >> any MTA integrated with Mailman)? > > If Mailman core is running, it will accept the mail and store it in > its own queue. If not, the MTA will store it in its deferred queue > until Mailman comes back up. > > The big problem with delegating this to the MTA is that after two days > the MTA probably won't retry for whole days, but if you do an MTA > queue flush, it will probably stop other mail delivery for quite a > while, since it will be occupied with processing the Mailman backlog. > > The way Mailman works is that there is a master process, which manages > a suite of runners. Each runner is responsible for a particular > stage. The LMTP runner does nothing except accept messages from the > MTA, and store each one in a file for the next runner in the chain. Although, looking at the code[1], it seems like LMTP runner will actually try to verify that the incoming email in destined to a valid email address before it will accept the email. [1]: https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… So, if the database isn’t reachable, I think LMTP runner will start rejecting emails from MTA. This is perhaps handling the situation where the transport maps are out-of-date and Mailman receives an email from MTA for a list that has been deleted. While I haven’t tested this situation, I don’t think it would work. So far I am seeing that holding emails off at MTA level and letting it retry after the database maintenance has been complete might be the only thing that works if the entire Postgresql instance has to be brought down. If MTA will retry continuously for 2 days, would that not be enough time to complete the migration and bring the database back up? -- thanks, Abhilash Raj (maxking)

4 years, 2 months

[MM3-users] Re: problem with postorius initial setup

by Abhilash Raj

-- thanks, Abhilash Raj (maxking) > On Mar 16, 2021, at 11:35 AM, John Covici <covici(a)ccs.covici.com> wrote: > > On Tue, 16 Mar 2021 12:14:36 -0400, > Stephen J. Turnbull wrote: >> >> John Covici writes: >> >>> Hi. I am trying to setup postorius, but I have run into a problem. I >>> am using the example project, except I am using postgresql instead of >>> sqlite3. I ran python manage.py migrate which was successful. >>> >>> On running the development server I get: >>> Exception in thread django-main-thread: >>> Traceback (most recent call last): >>> File >>> "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", >>> line 20, in import_string >>> return getattr(module, class_name) >>> AttributeError: module 'postorius.middleware' has no attribute >>> 'APICountingMiddleware' >> >> This appears to be another version mismatch. The >> APICountingMiddleware appears to be a debugging or development >> instrumentation tool. It was added on 2021-02-28, so it's very >> recent. Somehow your Postorius settings.py is newer than your >> Postorius middleware.py. I would guess you have checked out or pip'ed >> a very recent version of Postorius but the example_project is picking >> up an older version, possibly from the Gentoo package. Why that could >> happen depends on whether you've set up a venv for the up-to-date >> Postorius, whether it's active, and so on. > > I think I know what is happening, but not how to fix. The > example_project which the docs told me to get is from the postorius > git which is, of course, recent, whereas the postorius I have from the > gentoo package is 1.3.3, which is not that old, but maybe not up to > the git version. Should I be using the git version? You want to follow this guide[1] for installing from pip. It covers both Postorius and Hyperkitty. [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… I am assuming you saw it in this doc [2] to use the example_project. That is very specific to development installations. I will update the document to make it clearer and point to [1] for any production setup. [2]: https://docs.mailman3.org/projects/postorius/en/latest/setup.html#setup-you… > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici wb2una > covici(a)ccs.covici.com > _______________________________________________ > 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, 7 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 9:21 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Fri, Dec 23, 2022 at 4:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/22/22 16:03, Odhiambo Washington wrote: >> > >> > There is just one more thing - I have this in settings.py: >> > LOGGING['handlers']['file']['filename'] = >> > '/opt/mailman/mm/var/logs/mailmanweb.log' >> >> >> And what are LOGGING['handlers']['file']['level'], >> LOGGING['handlers']['file']['class'] and >> LOGGING['handlers']['file']['formatter'] >> > > Those are left as defaults in my setup.py. > > >> > However, the referenced file is ever empty. At what point is it >> supposed to >> > record anything? >> >> What is logged depends on `level` but even with `DEBUG` not much routine >> stuff is logged. See >> https://docs.djangoproject.com/en/3.2/topics/logging/ > > > I will read that and see if I get to pick up something. > > And now I am having a problem with mod_wsgi. > First, the URL displayed when I load the page looks bogus to me. > While I expect the URL to be > https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is an > extra /mailman3! > > So I have; > 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - working, > or appears to. > 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - working, > or appears to. > 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, or > appears to > 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, or > appears to > 5. > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… > - This throws an exception error when I click "Manage Subscription". > > -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ > > And while I do not quite understand the error itself, there is also one > particular line that I also saw that has left me baffled: > [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client > 197.232.81.246:13865] AH00128: File does not exist: > /usr/local/www/apache24/data/archives/list/ > kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, > refe > rer: > https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke > > I also need to add the fact that at the point where I am clicking "Manage Subscription", the URL has changed to https://mm3-lists.kictanet.or.ke/mailman3/archives/list/kictanet@lists.kict… (just a single /mailman3). -- 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: how to unhold a hold message from a nonmmeber in hold list.

by Odhiambo Washington

On Fri, Apr 21, 2023 at 12:04 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > > El 21/4/23 a las 10:37, Odhiambo Washington escribió: > > > > > > On Fri, Apr 21, 2023 at 11:20 AM Guillermo Hernandez (Oldno7) via > > Mailman-users <mailman-users(a)mailman3.org> wrote: > > > > I'm having troubles with Django and cannot access to web admin. > > > > I need to unhold a message while figures out what is happening. > > > > Searching the mailman cli help commands didn't help me. > > > > Anyone who knows how to unhold a message, please? > > > > > > TBH, I find it a lot easier to fix the web UI than mess with the > > python shell :-) > > > > While you wait for @Mark Sapiro <mailto:mark@msapiro.net> to save you, > > you can be reading the following: > > > > > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Thanks: it seems the place to do it (I didn't find it) > > I'm fighting the web UI problem. It seems that something in wsgi has > changed and is no more compatible with my version of things. Error log > from apache shows: > > mod_wsgi (pid=30632): Failed to exec Python script file > '/usr/local/mailman3/wsgi.py'. > mod_wsgi (pid=30632): Exception occurred processing WSGI script > '/usr/local/mailman3/wsgi.py'. > Traceback (most recent call last): > File "/usr/local/mailman3/wsgi.py", line 34, in <module> > from django.core.wsgi import get_wsgi_application > File "/usr/local/lib/python3.9/site-packages/django/core/wsgi.py", line > 2, in <module> > from django.core.handlers.wsgi import WSGIHandler > File > "/usr/local/lib/python3.9/site-packages/django/core/handlers/wsgi.py", > line 3, in <module> > from django.conf import settings > File "/usr/local/lib/python3.9/site-packages/django/conf/__init__.py", > line 19, in <module> > from django.utils.deprecation import RemovedInDjango50Warning, > RemovedInDjango51Warning > File > "/usr/local/lib/python3.9/site-packages/django/utils/deprecation.py", > line 4, in <module> > from asgiref.sync import iscoroutinefunction, markcoroutinefunction, > sync_to_async > ImportError: cannot import name 'iscoroutinefunction' from > 'asgiref.sync' (/usr/local/lib/python3.9/site-packages/asgiref/sync.py) > If you did some system updates then that is where you need to check. Obviously, something did update, leading to the breakage. -- 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, 6 months

[MM3-users] Re: Mailman 3 install questions: HAYSTACK_CONNECTIONS

by Odhiambo Washington

On Sun, Jul 7, 2024 at 6:24 AM <heller(a)deepsoft.com> wrote: > I am using the debian 12 repo versions of mailman3, django, posterious, > hyperkitty, and xapian: > > sharky5% dpkg-query -l > python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} > mailman3\* | grep '^ii' > ii mailman3 3.3.8-2~deb12u2 all Mailing list > management system > ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list > management system documentation > ii mailman3-web 0+20200530-2.1 all Django > project integrating Mailman3 Postorius and HyperKitty > ii python3-django 3:3.2.19-1+deb12u1 all High-level > Python web development framework > ii python3-django-hyperkitty 1.3.7-1 all Web user > interface to access GNU Mailman3 archives > ii python3-django-mailman3 1.3.9-1 all Django > library to help interaction with Mailman3 (Python 3 version) > ii python3-django-postorius 1.3.8-3 all Web user > interface to access GNU Mailman3 > ii python3-xapian 1.4.22-1 amd64 Xapian > search engine interface for Python3 > > Before adding the HAYSTACK_CONNECTIONS options, I have this: > > sharky5% sudo mailman-web haystack_info --no-color --skip-checks > Number of handled 1 index(es). > - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at > 0x7fd0de1b0470> > > When I add this to /etc/mailman3/maymail_web.py (adapted from the section > titled: > "Setting up Fulltext search (xapian)" on > https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian > > HAYSTACK_CONNECTIONS = { > > 'default': { > > 'PATH': "/var/lib/mailman3/web/fulltext_index", > > 'ENGINE': 'xapian_backend.XapianEngine' > > }, > > } > > I get: > > File "/usr/lib/python3.11/importlib/__init__.py", line 126, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "<frozen importlib._bootstrap>", line 1206, in _gcd_import > File "<frozen importlib._bootstrap>", line 1178, in _find_and_load > File "<frozen importlib._bootstrap>", line 1142, in > _find_and_load_unlocked > ModuleNotFoundError: No module named 'xapian_backend' > > So, do I use Xapian or not? Is something missing somewhere? Is this a > documentation bug or something else? > It cannot be a documentation bug since you are NOT using/following the documentation! The message is good enough. Where is your xapian_backend,py?? ``` wash@gw:~$ locate xapian_backend.py /opt/mailman/mm/venv/lib/python3.11/site-packages/xapian_backend.py wash@gw:~$ ``` I hope the above gives you a clue as to where it should be found. However, since you aren't following the documentation I am familiar with, and I am not a Python expert, my end-of-thinking capacity (/etc) is here :-) -- 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: Migrating to Mailman3

by Dennis Putnam

On 10/19/2025 2:42 AM, Stephen J. Turnbull wrote: > Dennis Putnam via Mailman-users writes: > > > Thanks for the info. I thought I had followed everything but I an > > unable to start mailman3 because all the expected directories in > > /var are missing. What steps did I miss? > > If you are setting up according to the virtual environment > instructions, Mailman shouldn't be looking for anything in /var that > you didn't explicitly configure to be there. > > With the venv active, try running just "mailman info". If that > succeeds and reports something other than /etc/mailman3/mailman.cfg, > then check the file it reports for "layout" and "var_dir" settings, > and remove the var_dir hierachy because it's just confusing. Then run > > mailman -C /etc/mailman3/mailman.cfg info > > If that succeeds, try starting Mailman with > > mailman -f -C /etc/mailman3/mailman.cfg start > > The "-f" is short for "--force" and it just cleans up any stale lock > files that might prevent Mailman from starting. (We now recommend > using it in the init script or systemd unit file ExecStart command.) > > If either of those fails, or Mailman starts but "doesn't work", look > in the logs (systemctl status, journalctl -eu, and > $var_dir/logs/mailman.log for error messages, and send those along > with /etc/mailman3/mailman.cfg to us. In the case of "doesn't work", > tell us what you mean by "doesn't work": Mailman doesn't accept mail, > Mailman crashes, Mailman doesn't send mail, etc. > Hi Steve, Thanks again. I think I found the problem. When I created the mailman.cfg file, for some reason everything was commented out. After saving I didn't bother to look at it. My bad. I then went though and uncommented as appropriate however I have one problem. I don't know what to do with this section for MySQL. [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgresql://mailman:MYPASSWORD@localhost/mailman Just as an FYI here is my full mailman.cfg: # /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here # # This address is the "site owner" address. Certain messages which must be # # delivered to a human, but which can't be delivered to a list owner (e.g. a # # bounce from a list owner), will be sent to this address. It should point to # # a human. site_owner: xxxxxx@ddddddddddd [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgresql://mailman:MYPASSWORD@localhost/mailman [archiver.prototype] enable: yes # # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1

3 weeks

[MM3-users] Daily Cronjob fails

by Stefan Tatschner

Hey hey, I applied a recent Update from Debian Buster, und this night a received an email about a failing cronjob. The traceback can be reproduced using: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) START TRACEBACK: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) psycopg2.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs job().execute() File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 35, in execute sync_with_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 131, in sync_with_mailman mlist.update_from_mailman() File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 192, in update_from_mailman self.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 808, in save force_update=force_update, update_fields=update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 838, in save_base updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 905, in _save_table forced_update) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 955, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 667, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1204, in execute_sql cursor = super(SQLUpdateCompiler, self).execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 899, in execute_sql raise original_exception File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 889, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/usr/lib/python3/dist-packages/django/utils/six.py", line 685, in reraise raise value.with_traceback(tb) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 64, in execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: null value in column "description" violates not-null constraint DETAIL: Failing row contains (2, hb-events(a)hackbrettl.de, hb-events, null, [hb-events] , 1, 2015-10-22 09:54:53.684306+00, hb-events.hackbrettl.de). END TRACEBACK Appearently there is something wrong with the database. Is there anything what I can do about this? Running the migrations doesn't help: # sudo -u www-data flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Thanks! Stefan

6 years, 8 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

The only way I've gotten it to work so far is by using the FQN. I can switch back to 127.0.0.1 but that wasn't working. Here's the configuration I have. incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: 127.0.0.1 smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 and the end result: https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 I tried setting the smtp_host to 127.0.0.1 and list.domain.org both result in the same issue. ie: Here's the combinations I've tried: smtp_host: 127.0.0.1 lmtp_host: 127.0.0.1 #fail smtp_host: lists.domain.org lmtp_host: 127.0.0.1 #fail Finally I even tried the exact copy from the documentation: incoming: mailman.mta.postfix.LMTPoutgoing: mailman.mta.deliver.deliverlmtp_host: 127.0.0.1lmtp_port: 8024smtp_host: localhostsmtp_port: 25configuration: python:mailman.config.postfix ## Fail. smtp_host: lists.domain.org lmtp_host: lists.domain.org # success. The error I get if I don't open port 8024 is below and in the gist i linked earlier. May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, dsn=4.4.1, status=deferred (connect to lists.domain.org[198.199.98.177]:8024: Connection refused) The only way I've gotten it to work so far is by binding both the smtp_host and lmtp_host to be lists.domain.org and opening up port 8024. I'd rather not have that port open but I'm open to suggestions on what else to try. Locally on the server: PING lists.domain.org (198.199.98.177) 56(84) bytes of data. 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=1 ttl=64 time=0.071 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=3 ttl=64 time=0.069 ms -- Samir Faci On Mon, May 4, 2020 at 9:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/3/20 10:04 PM, Samir Faci wrote: > > > > # Where the LMTP server listens for connections. Use 127.0.0.1 instead > of > > # localhost for Postfix integration, because Postfix only consults DNS > > # (e.g. not /etc/hosts). > > lmtp_host: lists.domain.org > > lmtp_port: 8024 > > Why, in spite of the comment, do you have > > lmtp_host: lists.domain.org > > and not > > lmtp_host: 127.0.0.1 > > Note that > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > are the defaults. > > > > So, now it's finally working but here's a question. Does 8024 need to be > > publically accessible from the outside? > > > No. Port 8024 is only for LMTP delivery from Postfix to Mailman. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 6 months

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

by Richard Rosner

Mark Sapiro wrote: > > But whatever is listening on port 8001 is apparently not Mailman's rest > server. What does > ps -fww 14080 > or whatever PID is currently listening on port 8001 show. UID PID PPID C STIME TTY STAT TIME CMD list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 > > OK. > Perhaps instead you should have > uid: list > gid: list > in your uwsgi configuration if you don't already. Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. What the logs say: *** Starting uWSGI 2.0.18-debian (64bit) on [Thu Aug 12 08:46:37 2021] *** compiled with version: 8.2.0 on 10 February 2019 02:42:46 os: Linux-4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) nodename: mail machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 2 current working directory: / detected binary path: /usr/bin/uwsgi-core chdir() to /usr/share/mailman3-web your processes number limit is 3831 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) error removing unix socket, unlink(): Permission denied [core/socket.c line 198] bind(): Address already in use [core/socket.c line 230] Not sure if that means the two directories need to be owned by list, currently they are owned by root > > I'm not familiar enough with this form of ProxyPass using sockets to > understand what the localhost:8001 does in this context, but uwsgi > should not be doing anything with port 8001. In a configuration using > TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API > server listens. uwsgi should receive connects in your case via the unix > socket and then pass them to Django via the application in wsgi.py > Also, you may want other paths proxied to uwsgi, namely at least some of > hyperkitty, postorius, archives, accounts, admin and user-profile. Ok, I removed that port again, now it's exctly like in the automatically generated config file. And you mean like <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> > > These should be 'list', not 'www-data'. That's your permissions issue on > settings.py

4 years, 2 months

[MM3-users] Re: MM 3 and cPanel - was: Message does not appear in archive

by Mark Sapiro

On 09/14/2018 03:07 AM, Paul Arenson wrote: > Recently I asked my server administrator (large educational organization with many accounts for various sub groups). > > I pointed out that it might be a while before MM3 is on CPanel. I showed him the documentation at http://docs.list.org/en/latest/migration.html to show how to go from Mailman 2 to 3 manually. He said he might be willing to give it a whirl. > > He said he might be willing to make our group (GALE) a test case (we have about 60 people in two not-so-active lists). He asked: > > "I'd need to look into this a bit more to see what's possible. One issue is whether CPanel updates would overwrite any changes made. If you have any more details about it, let me know. We could try it out on the GALE site if you wanted, but I couldn't guarantee that it would work." The initial step is to install a working Mailman 3 on the server. This can be done in a couple of ways. See <http://docs.list.org/en/latest/prodsetup.html> for more detail. It is not clear to me because I don't know much at all about cPanel whether MM 3 can be installed outside of cPanel on the same server or not, and if it has to be installed within cPanel, how that would be affected by cPanel updates if it can even be done at all. > I take it he can migrate from MM2 following the directions above in the URL. I guess what he means is, once it becomes available in Channel, would it mean more work to get it to work and to update than if we waited for the CPanel version to debut. Since I don't understand much of the install stuff, he would presumably be doing it. The info at <http://docs.list.org/en/latest/migration.html> covers migration of Mailman 2.1 lists to Mailman 3. The big hurdle is the installation of Mailman 3 which is not covered in that doc. As far as how to migrate from a 'custom' install to an eventual cPanel Mailman 3, that would depend at least in part on the database manager (SQLite, MySQL or PostgreSQL) used. I.e. if your custom install used SQLite and cPanel's used only MySQL, you would have a database migration issue. Some of these questions would be better directed to cPanel itself. Only they can tell you what their Mailman 3 timeline might be or if they even have one. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Hyperkitty CPU usage

by Alain Kohli

Well, I understand that it might take a while, but the process is running for over 200h now, I doubt it can really take _that_ long if everything is working properly. Especially because the rebuild_index command is only taking a few hours at most, doesn't that essentially do the same? We have ~700k messages in ~300 mailing lists in case that helps you estimate how long it could take. I can take a look at alternative backends, though. On 5/7/19 4:32 PM, Abhilash Raj wrote: > On Sat, Apr 27, 2019, at 6:22 PM, Alain Kohli wrote: >> I'm running a custom image which is based on an older version of the one >> here: https://github.com/maxking/docker-mailman. I attached it below. >> But I separated postorius and hyperkitty, so hyperkitty is running in >> its own container. I'm deploying the image with a plain 'docker run' >> behind nginx. I made fulltext_index persistent now, but it didn't get >> populated with anything yet. I don't really have an error traceback >> because there is never an error thrown. The only thing with some content >> is uwsgi-error.log, which you can find below. I'm also still getting the >> "A string literal cannot contain NUL (0x00) characters." messages. I >> also noticed that it takes incredibly long for the webinterface to load >> (several minutes) even though there doesn't seem to be any process >> consuming notable resources apart from the minutely job. >> >> Funnily enough, I have the exact same image deployed on a second server >> as well for testing. On that one everything works fine. The only >> difference is that on the problematic one I have a lot more mailing >> lists/archives and that I imported them from mailman2. Could something >> have gone wrong during the import? I used the regular hyperkitty_import >> command. > Yes, this is because `whoosh`, the library set by default to run fulltext > indexing is a pure python implementation and quite slow in busy lists. > > We do support more backends though, see [1] for a list of all the supported > search backends. Something like Xapian(C++) or Elasticsearch/Solr(Java) > should be much better in terms of performance. > > [1]: https://django-haystack.readthedocs.io/en/master/backend_support.html > >> uwsgi-error.log: >> >> *** Starting uWSGI 2.0.18 (64bit) on [Sat Apr 27 22:50:17 2019] *** >> compiled with version: 6.4.0 on 27 April 2019 22:48:42 >> os: Linux-4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) >> nodename: hyperkitty.docker >> machine: x86_64 >> clock source: unix >> detected number of CPU cores: 4 >> current working directory: /home/hyperkitty >> detected binary path: /usr/local/bin/uwsgi >> !!! no internal routing support, rebuild with pcre support !!! >> setgid() to 82 >> setuid() to 82 >> chdir() to /home/hyperkitty >> your memory page size is 4096 bytes >> detected max file descriptor number: 1048576 >> lock engine: pthread robust mutexes >> thunder lock: disabled (you can enable it with --thunder-lock) >> uwsgi socket 0 bound to TCP address 0.0.0.0:8081 fd 8 >> uwsgi socket 1 bound to TCP address 0.0.0.0:8080 fd 9 >> Python version: 3.6.8 (default, Jan 30 2019, 23:54:38) [GCC 6.4.0] >> Python main interpreter initialized at 0x55dfaa41c980 >> python threads support enabled >> your server socket listen backlog is limited to 100 connections >> your mercy for graceful operations on workers is 60 seconds >> [uwsgi-cron] command "./manage.py runjobs minutely" registered as >> cron task >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" registered >> as cron task >> [uwsgi-cron] command "./manage.py runjobs hourly" registered as cron >> task >> [uwsgi-cron] command "./manage.py runjobs daily" registered as cron task >> [uwsgi-cron] command "./manage.py runjobs monthly" registered as >> cron task >> [uwsgi-cron] command "./manage.py runjobs weekly" registered as cron >> task >> [uwsgi-cron] command "./manage.py runjobs yearly" registered as cron >> task >> mapped 208576 bytes (203 KB) for 4 cores >> *** Operational MODE: threaded *** >> WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter >> 0x55dfaa41c980 pid: 1 (default app) >> *** uWSGI is running in multiple interpreter mode *** >> spawned uWSGI master process (pid: 1) >> spawned uWSGI worker 1 (pid: 40, cores: 4) >> Sat Apr 27 22:50:18 2019 - [uwsgi-cron] running "./manage.py runjobs >> minutely" (pid 45) >> [uwsgi-daemons] spawning "./manage.py qcluster" (uid: 82 gid: 82) >> 22:50:21 [Q] INFO Q Cluster-47 starting. >> 22:50:21 [Q] INFO Process-1:1 ready for work at 59 >> 22:50:21 [Q] INFO Process-1:2 ready for work at 60 >> 22:50:21 [Q] INFO Process-1:3 ready for work at 61 >> 22:50:21 [Q] INFO Process-1:4 ready for work at 62 >> 22:50:21 [Q] INFO Process-1:5 monitoring at 63 >> 22:50:21 [Q] INFO Process-1 guarding cluster at 58 >> 22:50:21 [Q] INFO Process-1:6 pushing tasks at 64 >> 22:50:21 [Q] INFO Q Cluster-47 running. >> 22:59:31 [Q] INFO Enqueued 3403 >> 22:59:31 [Q] INFO Process-1:1 processing [update_from_mailman] >> 22:59:33 [Q] INFO Processed [update_from_mailman] >> Sat Apr 27 23:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 73) >> Sat Apr 27 23:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> hourly" (pid 74) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 73 exited after 64 second(s) >> 23:01:28 [Q] INFO Enqueued 3404 >> 23:01:29 [Q] INFO Process-1:2 processing >> [rebuild_mailinglist_cache_recent] >> [uwsgi-cron] command "./manage.py runjobs hourly" running with pid >> 74 exited after 91 second(s) >> Sat Apr 27 23:01:36 2019 - uwsgi_response_write_body_do(): Broken >> pipe [core/writer.c line 341] during GET / (212.203.58.154) >> OSError: write error >> 23:01:36 [Q] INFO Processed [rebuild_mailinglist_cache_recent] >> Sat Apr 27 23:15:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 88) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 88 exited after 4 second(s) >> 23:28:24 [Q] INFO Enqueued 3405 >> 23:28:24 [Q] INFO Process-1:3 processing [update_from_mailman] >> 23:28:25 [Q] INFO Processed [update_from_mailman] >> Sat Apr 27 23:30:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 96) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 96 exited after 4 second(s) >> 23:44:40 [Q] INFO Enqueued 3406 >> 23:44:40 [Q] INFO Process-1:4 processing [update_from_mailman] >> 23:44:41 [Q] INFO Processed [update_from_mailman] >> Sat Apr 27 23:45:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 104) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 104 exited after 4 second(s) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> quarter_hourly" (pid 113) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> hourly" (pid 114) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> daily" (pid 115) >> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py runjobs >> weekly" (pid 116) >> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >> with pid 113 exited after 55 second(s) >> [uwsgi-cron] command "./manage.py runjobs weekly" running with pid >> 116 exited after 55 second(s) >> 00:01:36 [Q] INFO Enqueued 3407 >> 00:01:36 [Q] INFO Process-1:1 processing >> [rebuild_mailinglist_cache_recent] >> [uwsgi-cron] command "./manage.py runjobs hourly" running with pid >> 114 exited after 99 second(s) >> 00:01:50 [Q] INFO Processed [rebuild_mailinglist_cache_recent] >> 00:04:52 [Q] INFO Enqueued 3408 >> 00:04:52 [Q] INFO Process-1:2 processing [update_from_mailman] >> 00:04:54 [Q] INFO Processed [update_from_mailman] >> >> Dockerfile: >> >> FROM python:3.6-alpine3.7 # Add startup script to container COPY >> assets/docker-entrypoint.sh /usr/local/bin/ # Install packages and >> dependencies for hyperkitty and add user for executing apps. # It's >> important that the user has the UID/GID 82 so nginx can access the >> files. RUN set -ex \&& apk add --no-cache --virtual .build-deps gcc >> libc-dev linux-headers git \postgresql-dev \&& apk add --no-cache >> --virtual .mailman-rundeps bash sassc mailcap \postgresql-client >> curl \&& pip install -U django==2.2 \&& pip install >> git+https://gitlab.com/eestec/mailmanclient >> >> \git+https://gitlab.com/mailman/hyperkitty@c9fa4d4bfc295438d3e01cd93090064d004cf44d >> \git+https://gitlab.com/eestec/django-mailman3 \whoosh \uwsgi >> \psycopg2 \dj-database-url \typing \&& apk del .build-deps \&& >> addgroup -S -g 82 hyperkitty \&& adduser -S -u 82 -G hyperkitty >> hyperkitty \&& chmod u+x /usr/local/bin/docker-entrypoint.sh# Add >> needed files for uwsgi server + settings for django COPY >> assets/__init__.py /home/hyperkittyCOPY assets/manage.py >> /home/hyperkittyCOPY assets/urls.py /home/hyperkittyCOPY >> assets/wsgi.py /home/hyperkittyCOPY assets/uwsgi.ini >> /home/hyperkittyCOPY assets/settings.py /home/hyperkitty# Change >> ownership for uwsgi+django files and set execution rights for >> management script RUN chown -R hyperkitty /home/hyperkitty && chmod >> u+x /home/hyperkitty/manage.py# Make sure we are in the correct >> working dir WORKDIR /home/hyperkittyEXPOSE 8080 8081# Use stop >> signal for uwsgi server STOPSIGNAL SIGINTENTRYPOINT >> ["docker-entrypoint.sh"]CMD ["uwsgi", "--ini", >> "/home/hyperkitty/uwsgi.ini"] >> >> On 4/27/19 7:58 PM, Abhilash Raj wrote: >>> On Sat, Apr 27, 2019, at 9:40 AM, Alain Kohli wrote: >>>> I have run "python manage.py rebuild_index" before, doesn't that do >>>> clear_index as well? Apart from that, I run hyperkitty in a docker >>>> container and didn't know fulltext_index should be persistent, so that >>>> got deleted after every version update for sure. >>> Which images are you using and how are you deploying them? >>> >>> You should persist fulltext_index, yes, and possibly logs if you need >>> them for debugging later. >>> >>> Can you paste the entire error traceback? >>> >>>> On 4/26/19 10:18 PM, Mark Sapiro wrote: >>>>> On 4/26/19 11:14 AM, Alain Kohli wrote: >>>>>> I see loads of "A string literal cannot contain NUL (0x00) characters." >>>>>> messages, but I haven't found missing messages in the archives yet. Not >>>>>> sure how that could be related, though. Apart from that I don't see >>>>>> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to >>>>>> run and finish normally. >>>>> Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 >>>>> version? The Haystack/Whoosh search engine databases are not compatible >>>>> between the two and "A string literal cannot contain NUL (0x00) >>>>> characters." is the symptom. >>>>> >>>>> You need to run 'python manage.py clear_index' or just remove all the >>>>> files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in >>>>> your settings file (normally 'fulltext_index' in the same directory that >>>>> contains your settings.py. >>>>> >>>> _______________________________________________ >>>> 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/ >>

6 years, 6 months

[MM3-users] Re: Mailman3 Docker question and importing lists from MM2

by Abhilash Raj

On Fri, Sep 1, 2017, at 09:35 AM, Andrew Hodgson wrote: > Hi, > > Thanks for this, I saw the Docker entrypoint script which assumes the > domain variable in the Docker environment expects a single domain. If I > alter the local settings file, do I need to add in the domains from the > default settings file, or will that get merged? It will just override anything in the default settings. So, any variable you add in the settings_local.py should include the default ones too, unless obviously if you don't want them. > > Thanks. > Andrew. > ________________________________________ > From: Abhilash Raj [raj.abhilash1(a)gmail.com] > Sent: 01 September 2017 17:29 > To: C. R. Oldham; mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Mailman3 Docker question and importing lists > from MM2 > > On Fri, Sep 1, 2017, at 08:51 AM, C. R. Oldham wrote: > > > > > > I had a question regarding the parameter: SERVE_FROM_DOMAIN. > > > > > > I want to use multiple domains, what is the best way to specify multiple > > > domains in this environment variable? > > > > > > > > This works OK for me: > > > > SERVE_FROM_DOMAIN=lists.domain1.org,lists.domain2.net,lists.domain3.com > > I never thought this would work, I would correspond to an invalid entry > in > ALLOWED_HOSTS in Django configuration. > > > The best way would be to put the domain you are going to serve from in > the > SERVE_FROM_DOMAIN variable as this would replace the `example.com` SITE > that Django creates by default. > > And then, you can list all your domains in > /opt/mailman/web/settings_local.py > in a Python list: > > ALLOWED_HOSTS = ["domain1", > "domain2", > "domain3"] > > Note that you need to also include the domain you set in > SERVE_FROM_DOMAIN here. > > > > > > I also had to login to the Django admin interface and create the domains > > there under Home->Sites > > > And yes, for Django to allow domains, you need to create a 'Site' in the > admin > console. The default one is created automatically using > SERVE_FROM_DOMAIN variable. > > > > > > --cro > > _______________________________________________ > > 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/ > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 2 months

[MM3-users] Re: disabled users

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

Hello, Thank you for your answers. The problem is: I have a lot of user disabled for too many bounces. These users have the same provider that, probably, has some limits of number of mail that can be delivered from the same server. This causes timeout connections and, mailman creates correctly a bounce. So I would like to discover a way to reset bounce limits so they can be re enabled to receive. I tried also to unsubscribe and resubscribe users but it does not change anything. Thank you 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 26/10/23 00:13, Mark Sapiro ha scritto: > On 10/25/23 10:44 AM, Stephen J. Turnbull wrote: >> Servizio Informatico U.I.C.I. Sezione territoriale di Brescia writes: >> >> > Wher I find the disabled user of a mailing list and wher I can >> > reactivate them? >> >> If you are the list owner or superuser, when you visit the list's >> information page there will be a horizontal menu across the top. One >> of the entries is Users. Click to open the dropdown menu and choose >> Members. There doesn't seem to be an explicit notation for disabled >> users, but if the entry in the far right column "bounce score" is >> None, the member may be disabled. > > I don't think this is correct. Members with delivery disabled by > bounce will normally show 0 rather than None for bounce score. > > If you have shell access to the server as the Mailman user, you can > run this shell interaction to find members with delivery disabled by > bounce. > ``` > $ mm/bin/mailman shell -l test(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 test(a)example.com mailing list > >>> for member in m.members.members: > ... if member.delivery_status == DeliveryStatus.by_bounces: > ... print(member.address.email) > ... > >>> > ``` > But the question is, why do you want to re-enable their delivery. > Granted, there are situations such as a misconfigured MTA or not > applying needed DMARC mitigations that could result in 'spurious' > bounced deliveries, but normally bounce processing disables delivery, > sends warnings to the bouncing address and ultimately unsubscribes > them because the address it truly not deliverable. > >

2 years

[MM3-users] Cannot connect to SMTP server

by mkummini＠cmi.ac.in

Hello. I am setting up a new mailman3 server (debian 11). `mailman3-full` is installed on the same server as postfix (our MTA). There is just one test mailing list now. When I send a message to it (I am a subscriber), mailman3 accepts the message through LMTP. Both the postfix log and mailman.log confirm this. Postfix log: Aug 14 03:21:25 mail postfix/lmtp[4097036]: 44E49272437D: to=<testlist(a)cmi.ac.in>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.15, delays=0.02/0.03/0.01/0.09, dsn=2.0.0, status=sent (250 Ok) mailman.log: Aug 14 03:21:26 2022 (4096856) ACCEPT: <Yvgc3WsoFlpZbypw(a)cmi.ac.in> (The digest.mmdf file shows the test message I sent. Hence mailman3 has received the message from postfix.) However, after this, the postfix log does not show any attempt by mailman3 to send the message to the list members. The following runners have started (after the most recent mailman3 restart) Aug 14 03:19:53 2022 (4096853) archive runner started. Aug 14 03:19:53 2022 (4096863) retry runner started. Aug 14 03:19:53 2022 (4096862) rest runner started. Aug 14 03:19:54 2022 (4096855) command runner started. Aug 14 03:19:54 2022 (4096854) bounces runner started. Aug 14 03:19:55 2022 (4096860) pipeline runner started. Aug 14 03:19:55 2022 (4096866) digest runner started. Aug 14 03:19:55 2022 (4096858) nntp runner started. Aug 14 03:19:55 2022 (4096857) lmtp runner started. Aug 14 03:19:55 2022 (4096865) virgin runner started. Aug 14 03:19:56 2022 (4096856) in runner started. Aug 14 03:19:57 2022 (4096859) out runner started. However, I get the following line each time I do a restart Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. Following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do…>, I tried to create an outgoing test runner, but that resulted in the following errors. >>> from mailman.runners.outgoing import OutgoingRunner >>> from mailman.testing.helpers import make_testable_runner >>> outgoing = make_testable_runner(OutgoingRunner, 'out') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 92, in make_testable_runner return EmptyingRunner(name) File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 79, in __init__ super().__init__(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 53, in __init__ super().__init__(slice, numslices) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 63, in __init__ section = getattr(config, 'runner.' + name) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 123, in __getattr__ return getattr(self._config, name) AttributeError: 'NoneType' object has no attribute 'runner.out' Here are the lines in mailman.cfg referring to smtp smtp_secure_mode : starttls smtp_host: localhost smtp_port: 587 If you could suggest how I could fix this issue, it would be great. Thank you. Manoj.

3 years, 2 months

[MM3-users] Re: Is it possible to add non-members in regex format in Mailman 3 ?

by Shashikanth Komandoor

Thank you Abhilash for your response. I am currently running Postorius 1.0.2 and mailman core 3.3.1. I have deployed in a production environment and have done some customizations by adding the SMS notifications and removed some options which are not required to my organization like social logins and so. Now, if I upgrade only the Postorius from 1.0.2 release to 1.3.3 can I get all the customizations I had done or will I have to reconfigure the same customized code in the newer version? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 16, 2020 at 11:09 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Tue, Jun 16, 2020, at 7:09 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > In mailman 2, I was able to add the non-members in the > > respective privileged box even using the regex also which will be used to > > add the domains instead of a single mail id. > > > > But in mailman 3, I am not allowed to add the non members in > > the regex format. Of course it is allowing me to add individual mail ids > > and give permissions. But I want to add a non-member which may be > something > > like the entire cisco.com domain on which I want to set the rule. > > > > You can do that with Postorius 1.3.3 (which was released recently) and > Mailman Core 3.3.1. > > > > Please help me out by suggesting over this or if mailman 3 is > > not providing then please hint me out with a work around at least. > > > > -- > > Thanks & Regards, > > Shashi Kanth.K > > 9052671936 > > > > > > > > > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > > Virus-free. > > www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > > 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) > _______________________________________________ > 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

5 years, 4 months

[MM3-users] Re: Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?

by Pierre Malard

Ok, don’t throw any more away! If you really don't recommend the Debian packaged solution, I just have one question: Why have you included it in the Debian "main" repositories for so long? Just a quick thought: In a production setting it is essential to have consistent alert reporting of security updates for all installed packages. As we cannot spend our time scrutinizing the lists of these tools tool by tool (snap, virtualenv, docker, appimage, etc.) it is much more efficient to rely on the system managed and deployed by the OS if it this is serious; and this is the case of Debian. Either, I will contact the packaging manager and discuss with him but I must admit that your reactions of disintegration do not bode well for the future. Sincerely > Le 19 déc. 2023 à 17:24, Jörg Schulz <info(a)joergschulz.de> a écrit : > > Additionally, in my feeling, the docker way is the easiest one - see https://github.com/maxking/docker-mailman > > Am 19.12.23 um 17:01 schrieb Odhiambo Washington: >> (...) >> We (I am not including the MM3 Developers) are very happy to poke our noses >> into MM3 issues if they followed this documentation: >> https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install >> If not that, then it means you used your OS packages system and that is - >> well - not easy to help with as it's got several ways to break. >> >> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to plm(a)teledetection.fr -- Pierre Malard « - Il n'y a que trois éléments indispensables à la vie. Et il n'y a que les scientifiques pour penser que c'est l'oxygène, l'hydrogène et le carbone... - Quoi alors ? L'eau, l'air et le feu ? - Non ! Le désir, le désordre et le danger... » Manon Briand ; La turbulence des fluides (film québécois de 2001) |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

1 year, 10 months

[MM3-users] Re: Hyperkitty Text/Markdown/HTML

by Sam Darwin

> Thus, all you are asking here is that there be an option for HyperKitty to render the HTML (perhaps sanitized) inline as opposed to leaving it as an attachment. I understand that request. Yes. Or, the more the topic is discussed, I see there are two parts. Hyperkitty rendering is one of them. The other being to find a way to sanitize HTML of outgoing emails. > I was asking if you envisioned that a text/html part outside of a multipart/alternative part would cause mailman to create a text/plain alternative and package it with the text/html part in a multipart/alternative part. But if that was not your intent, OK. I hadn't thought about that situation. Maybe it is relevant after all. And then, you said that you are not interested in doing that. It might need to be investigated along with these other features. Not sure. > The issue is not in the plain text converted from the HTML by Mailman's Convert html to plaintext feature. The issue is in the text/plain alternative created by Yahoo when a message is composed as "rich text" and created by Yahoo as multipart/alternative. Were you looking at that text/plain alternative part from Yahoo., i.e. what you see in the outgoing mail if Collapse alternatives is Yes. The list's settings are Collapse alternatives=Yes and Convert html to plaintext=YES. Standard "plain" URLs are ok, but I was just now able to replicate some sort of problem. Using the yahoo toolbar, a fully HTML hyperlink with an href and name failed to render in plain text. It resulted in just plain text without appearing as a "link". If that's happening even now, maybe it won't get worse in the future. only better. if switching to html. > and most MUAs will render the converted html alternative. interesting... The future plan would be to set all filtering to NO. All MIME parts delivered. But then, what if a plain-text version is missing somehow. > If you want email clients to display the HTML, either don't filter content or filter content and pass both multipart and text main types and set both Collapse alternatives and Convert html to plaintext to No. This will accomplish what you want minus the possible sanitizing of the HTML for Mailman core and delivered messages. In HyperKitty, the HTML part(s) will still be rendered as attachments. Understood. Problems remain though: "minus sanitizing". Sanitizing should be added. "HTML part(s) will still be rendered as attachments." The bulk of this discussion is about avoiding Hyperkitty attachments, and instead showing html inline. > If we receive a merge request to implement inline rendering of HTML, it will be considered but no guarantees. Exploring the issue.

2 months

[MM3-users] Re: Custom Templates and reject_message() error

by Abhilash Raj

On Sat, Aug 1, 2020, at 9:38 AM, Marcel Pietschmann wrote: > Hi everyone, > > I'm running Mailman 3 in maxking's Docker container (tag 0.3). Mailman3 > runs really well, thanks for that good job! But I noticed two errors. > > 1) When a new list is created, Mailman will not notify the list owners > of their new mailing list. I tested it with the default template > "domain:admin:notice:new-list.txt" and my own template (which i copied > in $var_dir/templates/domains/DOMAIN/de/ > > Any customs templates in $var_dir/templates... aren't sent out, always > the default templates from > /usr/lib/python3/site-packages/mailman/templates/de. I can't find > anything in the logs for that issue. Do you mean to say the notification isn't sent out at all or that the custom templates aren't used? > > 2) When a post requires an approval and I reject it with a notification > a server error occurs: "An error occurred while processing your request." > > The Traceback in mailmanweb.log is: > > ERROR 2020-08-01 16:19:19,926 17 django.request Internal Server Error: > /postorius/lists/list.domain.de/held_messages/moderate > Traceback (most recent call last): > File > "/usr/lib/python3.6/site-packages/django/core/handlers/exception.py", > line 34, in inner > response = get_response(request) > File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", > line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", > line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File > "/usr/lib/python3.6/site-packages/django/views/decorators/http.py", line > 40, in inner > return func(request, *args, **kwargs) > File > "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", > line 21, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py", > line 60, in wrapper > return fn(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line > 549, in moderate_held_message > mailing_list.reject_message(msg.request_id, reason=reason) > TypeError: reject_message() got an unexpected keyword argument 'reason' This seems to be a bug, I forgot to bump Mailmanclient when I bumped Postorius. I have a PR that I am working on[1], will tag and push as soon as I can get it to build, there seems to be some build failures. [1]: https://github.com/maxking/docker-mailman/pull/389 > Thanks a lot for any suggestion. > > Greets > Marcel > > Mailman Core Version: 3.3.1 > Mailman Core API Version: 3.1 > Postorius Version 1.3.3 > HyperKitty Version 1.3.3 > _______________________________________________ > 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, 3 months

[MM3-users] ModuleNotFoundError: No module named 'settings'

by Michela

Hello! I've just set up Mailman 3 with Hyperkitty and Postorius in venv via pip by using the guide at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… on Oracle Linux 8.3 with Python 3.6.8. The process seemed to go smoothly and without errors. The log file, /opt/mailman/web/logs/uwsgi-error.log, contains the following stack trace, however. Note the bit toward the bottom: "ModuleNotFoundError: No module named 'settings'" Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 224, in fetch_command app_name = commands[subcommand] KeyError: 'qcluster' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_web/manage.py", line 30, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 231, in fetch_command settings.INSTALLED_APPS File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 76, in __getattr__ self._setup(name) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 63, in _setup self._wrapped = Settings(settings_module) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 142, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked ModuleNotFoundError: No module named 'settings' [uwsgi-daemons] throttling "/opt/mailman/venv/bin/mailman-web qcluster" for 245 seconds [uwsgi-daemons] respawning "/opt/mailman/venv/bin/mailman-web qcluster" (uid: 1002 gid: 1002) Mailman and mailman-web do start without errors when I run them via their systemd unit files and Postorius serves up pages (without styles and such, which I'll fix later). SELinux is disabled, at least while I work through this issue. I've gone over the configuration files, and everything appears to be in order as written in the installation instructions, but that's likely not the case. :) My configuration files outside of the Mailman virtual environment are in /etc/mailman/: (venv) [mailman@host ~]$ ls /etc/mailman3/ mailman.cfg __pycache__ settings.py uwsgi.ini When searching the web about this, I only found one result, on this very list, but it didn't have quite enough information for me to solve my issue. It might also not quite be the same problem: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Might you be able to point me in the right direction on solving this issue? Please tell me if there is any more information I can provide to that end. Best, Michela

4 years, 5 months

[MM3-users] Re: HyperKitty misreporting statistics

by Abhilash Raj

On Thu, Aug 24, 2017, at 09:42 AM, Cameron Smith wrote: > Abhilash, > > I think the location of the message, in the error log, is correct: in the > uwsci-cron.log, the entries show that the “minutely” jobs run for 32-33 > seconds, whereas the entries in the error log show the jobs as running > for only 2 seconds, suggesting an error. (As an aside, what is “minutely” > doing that takes 32-33 seconds?) Yeah, if there are no entries going to uwsgi-cron at all, it looks like there is some configuration problem in log routing. T this[1] is the uwsgi configuration that is supposed to route the cron related logs to uwsgi-cron.log. Also, I am not exactly sure of what jobs run "minutely", [2] is the place where all of them are defined if you want to dive in yourself. Jobs (class) have a method "when" which defines when they run like "hourly", "daily" etc. [1]: https://github.com/maxking/docker-mailman/blob/master/web/mailman-web/uwsgi… [2]: https://gitlab.com/mailman/hyperkitty/tree/master/hyperkitty/jobs > How best can I diagnose the problem? If need be, I can simply tear down > the whole system, including deleting /opt/mailman on the host, start > again and see if the problem persists. I think it would, however, be more > helpful if we could figure out what has gone wrong. I am not sure what exactly is the problem, opening an issue with Hyperkitty[3] might be worth it to see if the devs have ideas about it. If this is a problem with Hyperkitty, I'd assume it would also be visible on the archives on this list, which runs on Mailman 3 (and not using containers AFAIK). [3]: https://gitlab.com/mailman/hyperkitty/issues > > > On 2017.08.20, at 14:34 , Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Sun, 20 Aug 2017 08:38:53 -0700 > > Cameron Smith <ccsmith(a)cetsi.com> wrote: > > > >> Hmm… something is definitely not right. > >> > >> /opt/mailman/web/logs/uwsgi-cron.log has not been updated since Aug 11, which is when I installed the container images 0.1.1. However, /opt/mailman/web/logs/uwsg-error.log is being updated every minute with entries similar to this: > >> > >> Sun Aug 20 13:40:00 2017 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 123) > >> [uwsgi-cron] command “./manage.py runjobs minutely" running with pid 123 exited after 2 second(s) > > > > > > This seems like a bug in the uwsgi configuration, it should actually go to > > uwsgi-cron.log. I have opened a new bug[1] to track this problem. > > > > [1]: https://github.com/maxking/docker-mailman/issues/119 > > > > > Cameron Smith -- Abhilash Raj maxking(a)asynchronous.in

8 years, 2 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Gerald Vogt

Hi, are you sure you are both talking about the same setting? You wrote initially: "The list settings have automatically (and appropriately) been set to hold mails when I go to Settings -> Message Acceptance -> "Default action to take when a *non-member* posts to the list" -- it says Hold for moderation" That's for non-members, not for members. That does not apply to users which you have mass subscribed. For those there is the "Default action to take when a member posts to the list". That's the one Mark Sapiro mentioned. Regards, Gerald On 18.11.24 10:59, mark(a)suburbia.org.au wrote: > Hi Mark, > > Thanks for taking the time to reply. > > Mark Sapiro wrote: >> On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > >>> However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through. >>> Am I missing something with the expected functionality? >>> A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation? >> Actually, it is good practice to set that to Hold for moderation for >> all lists or at least all those that don't require moderator approval >> for subscription to prevent a spammer from subscribing and spamming the >> list. Then, upon approving a member's post you can also set the member's >> moderation action to default processing and upon discarding a spammers >> post, you can also set the spammer's moderation action to Discard. > > I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held. > > I'm happy to do more testing, provide other information/logs as desired if that would help? > > cheers, > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to vogt(a)spamcop.net

11 months, 3 weeks

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

by Stephen J. Turnbull

Duane Raymond writes: > I have a Debian-postfix-postgres-nginx-Hyperkitty-Postorius setup > with a primary domain (e.g. primarydomain.com) and several > 'secondary' domains used for email lists (e.g. emaillistA.com and > emaillistB.com) When sending emails to a list using the > primarydomain.com address, the email is received, sent to > subscribers and archived properly. But when it is sent to one of > the secondary domains like tes(a)emaillistA.com - the email doesn't > seem to be sent and isn't archived - despite it being set to be. What do you mean by "set"? That the list has archiving enabled? What is in the Postfix logs? Where does Postfix try to deliver the second class of email (list-specific domains)? Is there a "bounce" (more precisely, a Delivery Status Notice telling you that the mail was not delivered, and with luck, why Postfix had a problem)? What is in the Mailman logs? I assume from your description (one server, multiple domains) that these list-specific domains are "virtual" domains that are handled by the single server. It seems likely that something is going wrong with the routing in Postfix. > What I've tried so far (after searching these archives and looking > at the documentation) is to: > 1) Adding emaillistA.com and emaillistB.com to the > MAILMAN_ARCHIVER_FROM setting in the settings_local.py file (and > then restart mailman) > 2) Adding emaillistA.com and emaillistB.com to the mydestination > setting in the postfix main.cf file (and the restarting > postfix). (2) above will allow receiving mail for those domains, but is unlikely to be sufficient for routing to lists. You also need to inform Mailman about the virtual domains, because the internal name of the mailing list includes the domain. Postfix has extensive support for virtual domains. This is somewhat tricky. Are you familiar with this support, as documented in http://www.postfix.org/VIRTUAL_README.html, and the general docs? For Mailman's needs from Postfix, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. If the above aren't sufficient hints, we need more information about both the Postfix configuration and the Mailman configuration. In a later message https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, you report at the end of the traceback (line folded for readability): > AttributeError: 'NoneType' object has no attribute 'preferences' > Mar 04 14:08:24 2021 (5044) SHUNTING: > 1614866904.2741017+f1f320a5d0006e885586be5b33543e364e3829b4 This seems to indicate that either your list has a member that doesn't exist in Mailman's subscriber database or (maybe) that there are no subscribers, because it's trying to get profile information about a nonexistent list member (represented by the Python 'None' object). Did this occur only once? How many messages are in the "shunt" queue?

4 years, 8 months

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

by Kyriakos Terzopoulos

Hi Stephen, all, Firstly, thank you for your kind support. It seems that there is some misunderstanding there from my side, since I did not use the github repo to install mailman - I did it through pip install. I will try to set it up with github and come back with any issues. Thank you. Regards *Kyriakos Terzopoulos* Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d> On Mon, 2 Oct 2023 at 18:59, Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Kyriakos Terzopoulos writes: > > > ImportError: cannot import name 'path' from 'importlib_resources' > > Try putting the error message into Google with "" around it. (This is > generic advice for the future, obviously I already know what it is and > will tell you. :-) > > This is a known issue where Python changed some APIs that Mailman uses. > Discussion is here: https://gitlab.com/mailman/mailman/-/issues/1093 > There's a simple patch to requirements.txt at the end of the comments. > Edit it, and delete and reinstall the mailman package, it will take 10 > minures. If you're familiar with Python and pip you can also force > remove that package, then reinstall with the additional version > constraint. > > > In general would it be better or/and easier to set this up on a new > > machine in my Hetzner cloud e.g. on Debian which seems to have > > packages of mailman available? > > That depends. Do you want to get your Mailman help from Debian (the > answer is "NO!!"[1] unless you mostly expect to need no help -- that > probably works for 70% of Debian + Mailman users) or from us? Unless > your use case is exactly what the distro maintainer envisions, you > will occasionally run into issues that are impossible for them to > figure out, and rather expensive for us to help you with since they > depend on old and modified versions. We strongly prefer you use a > venv install, and if Mailman is at all important to your site's > mission, you probably will too. > > Footnotes: > [1] At least for servers, I prefer Debian myself. Distros are the > best thing since sliced bread. But Mailman is still a relatively > fast-moving target[2] and none of the distros keeps up. > > [2] In part because Gmail, Yahoo!, and O365 hate mailing lists, > almost as much as the spammers hate us, and we keep tweaking things to > deal with both kinds of Internet mischief. > >

2 years, 1 month

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

by Brian Carpenter

On 10/21/20 9:39 PM, Abhilash Raj wrote: > > On Wed, Oct 21, 2020, at 3:35 PM, Brian Carpenter wrote: >> 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? > I added the option in my drive to expose every possible Mailinglist settings via Postorius and missed the fact that we weren't actually able to moderate those requests. > > Yes, this option can be hidden if it doesn't work until the next stable release. I hid one of the list settings in Postorius exactly because it didn't work, but this one slipped. Thank you. I will go ahead and remove the option within Affinity. >> 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? > Unfortunately no, there is a bug report open for it though and I have some done some analysis on root cause[1]. The bug turned out to be a more than a trivial one and I haven't been able to get to it yet. > > [1]: https://gitlab.com/mailman/mailman/-/issues/768 > > This is good information to have at least so I appreciate letting me know. I probably need to spend more time looking through the outstanding issues for Mailman core and Postorius before launching a nuclear strike of epic and catastrophic proportions upon Mark. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

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

by mrl＠psfc.mit.edu

Roland - Thanks, but I don't think that will help. Because systemctl doesn't actually check to see if a service properly started. I.e., see below. Maradbd (mysql) did start before mailman3. However, it had to do a crash recovery after a non-clean reboot. So it was not ready to accept connections right away. Mailman3 then tried to start but failed. mailmanweb.service then tried to start, even though mailman3 wasn't running And tthen every attempt over the web to access the mailman3 web page, would generate an email message that was sent to me. So I had hundreds of emails when I woke up. Mailman3 core needs to keep trying to access mysql, rather than stopping. I could create a cron script that runs every 5 minutes, that checks if mailman3 is not running, and tries to start it. But that's a hack. :) Jul 26 04:52:11 psfcmail2 mariadbd[938]: 2023-07-26 4:52:11 0 [Note] InnoDB: Completed initialization of buffer pool Jul 26 04:52:12 psfcmail2 mariadbd[938]: 2023-07-26 4:52:12 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=9811536157,9811536157 Jul 26 04:52:13 psfcmail2 systemd[1]: Starting GNU Mailing List Manager... ... ul 26 04:52:25 psfcmail2 mailman[1313]: File "/opt/mailman/venv/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 901, in __connect Jul 26 04:52:25 psfcmail2 mailman[1313]: self.dbapi_connection = connection = pool._invoke_creator(self) Jul 26 04:52:25 psfcmail2 mailman[1313]: File "/opt/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/create.py", line 636, in connect Jul 26 04:52:25 psfcmail2 mailman[1313]: return dialect.connect(*cargs, **cparams) Jul 26 04:52:25 psfcmail2 mailman[1313]: File "/opt/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 580, in connect Jul 26 04:52:25 psfcmail2 mailman[1313]: return self.loaded_dbapi.connect(*cargs, **cparams) Jul 26 04:52:25 psfcmail2 mailman[1313]: File "/opt/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 352, in __init__ Jul 26 04:52:25 psfcmail2 mailman[1313]: self.connect() Jul 26 04:52:25 psfcmail2 mailman[1313]: File "/opt/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 668, in connect Jul 26 04:52:25 psfcmail2 mailman[1313]: raise exc Jul 26 04:52:25 psfcmail2 mailman[1313]: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] Connection refused)") Jul 26 04:52:25 psfcmail2 systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Jul 26 04:52:25 psfcmail2 systemd[1]: mailman3.service: Failed with result 'exit-code'.'. Jul 26 04:52:25 psfcmail2 systemd[1]: Failed to start GNU Mailing List Manager. Jul 26 04:52:25 psfcmail2 systemd[1]: Started GNU Mailman Web UI. Jul 26 04:52:25 psfcmail2 uwsgi[1600]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Jul 26 04:52:26 psfcmail2 mariadbd[938]: 2023-07-26 4:52:26 0 [Note] InnoDB: Read redo log up to LSN=9844697088 Jul 26 04:52:28 psfcmail2 mariadbd[938]: 2023-07-26 4:52:28 0 [Note] InnoDB: Starting final batch to recover 697 pages from redo log. etc...

2 years, 3 months

[MM3-users] Re: error changed after restart

by Abhilash Raj

On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > On 6/2/21 18:08, Abhilash Raj wrote: >> >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >>> I restarted de server and the error changed. Now the log shows >>> "KeyError: 'subscription_mode'": >> Did you also restart Mailman Core after the upgrade? > > Yes, indeed: > > I stopped mailman core and all the processes related. Did the > upgrades. > Started all again. Find the errors in the web user interface. Stopped > all again. Looked for errors in the log. Restarted the complete > server. > > Found the second error that this second mail is about to. It happens > when, in the main page that shows all the lists you click to see one > of > them. It seems to me that it has been database structure changes in > django that the upgrade is not aware... but it's a very long shot from > my side. `subscription_mode` was added in Mailman Core 3.3.2 and it is actually a derived atrribute and not stored in Database. Mailman's API should be returning this attribute for each Member, but for some reason it seems to me like it isn't doing that even though do have Mailman 3.3.3 running like you said. If you have Curl installed, can you send me the output of: $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 It should ideally return an output that looks something like shown here[1]. You can put the username/password of Core's API server in the above command. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… Abhilash > > I'm using sqlite as django database and mysql for mailman. > >> >>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server >>> Error: /mailman3/mailman3/lists/name_and_domain.of.the.list >>> Traceback (most recent call last): >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 119, in __getattr__ >>> return self._get(name) >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 86, in _get >>> raise KeyError(key) >>> KeyError: 'subscription_mode' >>> >>> During handling of the above exception, another exception occurred: >>> >>> Traceback (most recent call last): >>> File >>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >>> line 34, in inner >>> response = get_response(request) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>> line 115, in _get_response >>> response = self.process_exception_by_middleware(e, request) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>> line 113, in _get_response >>> response = wrapped_callback(request, *callback_args, >>> **callback_kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>> line 71, in view >>> return self.dispatch(request, *args, **kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >>> line 74, in dispatch >>> return super(MailingListView, self).dispatch(request, *args, >>> **kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>> line 97, in dispatch >>> return handler(request, *args, **kwargs) >>> File >>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >>> line >>> 295, in get >>> member.subscription_mode == >>> File >>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>> line 124, in __getattr__ >>> self.__class__.__name__, name)) >>> AttributeError: 'Member' object has no attribute 'subscription_mode' >>> *********************** >>> some info about the installed versions via pip list: >>> pip list | grep django >>> django-allauth 0.44.0 >>> django-appconf 1.0.4 >>> django-compressor 2.4 >>> django-extensions 3.1.0 >>> django-gravatar2 1.4.4 >>> django-haystack 3.0 >>> django-mailman3 1.3.5 >>> django-picklefield 3.0.1 >>> django-q 1.3.4 >>> djangorestframework 3.12.2 >>> >>> pip list | grep mailman >>> django-mailman3 1.3.5 >>> mailman 3.3.3 >>> mailman-hyperkitty 1.1.0 >>> mailmanclient 3.3.2 >>> >>> pip list | grep postorius >>> postorius 1.3.4 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users >>> wrote: >>>> I've just upgrade mailman 3 installation following Mr. Sapiro >>>> advice: >>>> did a >>>> >>>> pip install --upgrade django-mailman3 hyperkitty mailman >>>> mailmanclient >>>> mailman-hyperkitty postorius >>>> >>>> I did a "python3 manage.py migrate" after, too. >>>> >>>> And all seemed to run well. >>>> >>>> All the lists showed in postorius via web, but when I try to >>>> accesss >>>> into one of them the browser shows an error. >>>> >>>> In the log you can see: >>>> >>>> *-*-*-*-*-*-* >>>> >>>> Traceback (most recent call last): >>>> File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 119, in __getattr__ >>>> return self._get(name) >>>> File >>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>> line 86, in _get >>>> raise KeyError(key) >>>> KeyError: 'get_requests_count' >>>> >>>> ... (And after all the traceback lines) >>>> >>>> AttributeError: 'MailingList' object has no attribute >>>> 'get_requests_count' >>>> >>>> *-*-*-*-*-*-*-* >>>> >>>> The lists seem to be distributing messeages well.. but I cannot >>>> acces >>>> via web administration (django/postorius) >>>> >>>> Can anyone point me in the right direction to solve this, please? >>>> >>>> _______________________________________________ >>>> 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/> >>>> >>> _______________________________________________ >>> 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/> >>> > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > <mailto:mailman-users-leave@mailman3.org> > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

4 years, 9 months

[MM3-users] Re: Cannot Create New List

by Stephen J. Turnbull

dap1--- via Mailman-users writes: > Stephen: I get it. It just seems there is no place where all these > *nix dependent variations are easily found. Mailman docs seems like > to logical place. *You* don't need to find *all* the variations -- just what you have installed. *We* have to find them and keep them up to date. > Anyway, I still need help. I migrated my mailman2 to mailman3 per > the documentation and all seemed to go well. However, now that I > have the web UI working, no lists show up. Indeed, using mysql, > all the relevant tables in mailman db are empty. How do I figure > out if the import really worked when there are no error messages? I really don't have any idea how you figure these things out, because the behaviors you report make no sense. There is clearly a lot that you haven't told us, but I don't know what that might be. Mark suggests you may have used postgresql with Mailman core. Is postgresql installed on your system? There may be multiple versions and multiple database clusters per version. Find them and check for databases named 'mailman'. (And now you're at the end of my relevant knowledge of PostgreSQL.) I know almost nothing about MySQL, but I suppose the situation may be similar to PostgreSQL (multiple versions or flavors installed simultaneously, with multiple database clusters). Check that for 'mailman' databases, too. Check for running database servers. Something like "ps aux | grep sql" might catch them all, or maybe you need to scan the whole ps list. Mark suggests that you may have multiple configurations active depending on how you try to access Mailman. Try find / -name mailman.cfg This should return exactly two instances: /etc/mailman3/mailman.cfg /opt/mailman/venv/lib/python3.12/site-packages/mailman/config/mailman.cfg (I'm guessing the version of Python and I'm only 99% sure it's /opt/mailman.) If others exist, there's a good chance they were automagically created when you started mailman the first time, and some chance they're being used when you invoke 'mailman' explicitly (eg, "mailman shell" or the migration command). Similarly find / -name settings.py This should return /etc/mailman3/settings.py and a truckload of them under /opt/mailman/venv/lib/python3.12/site-packages. If there are others, copy the list for possible future reference. (Can't rule valid other instances out because it's such a common name.) Search /etc/mailman3/mailman.cfg and /etc/mailman3/settings.py for spurious database configurations. (Pretty sure we checked for mailman.cfg already and it was OK, but I don't recall mentioning settings.py.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 days, 13 hours

[MM3-users] Question about "envelope-from" header

by Stephen J. Turnbull

Stephen Daniel writes: > I think I could fix this by having postfix edit the "envelope-from" > header as it relays the mail, so that the "envelope-from" header > contains something like "admin(a)mydomain.com". Not sure, but I > think so. You can try it, but I'd bet money that it won't work. "Envelope-From" is a diagnostic convenience that often allows a mail admin to analyze problems like this one without coordinating user reports with MTA logs. If you are correct that smtp.google.com restricts the sending domains, the data smtp is looking at is *not* the Envelope-From header, it is the SMTP protocol "MAIL FROM" argument. This is data that does not appear in the mail message header unless some SMTP server arbitrarily decides to copy it into the header. To avoid such a restriction, you need to configure Postfix to change the envelope sender in MAIL FROM to "mydomain.com". I'm pretty sure Postfix can do that conditional on the content of the message's metadata (MAIL FROM, RCPT TO) or header, but I don't know how offhand. In your example, it would be only when the SMTP RCPT TO value is "alias1(a)mydomain.com". Search the postconf manpage for "sender". Note that if you set up the aliases file correctly you can probably use it in the condition for this operation. Most likely just a separate alias file for your random aliases will be enough, add it to all the relevant places. > My question is this: If I edit the envelope-from header in my > outbound emails to say "admin(a)mydomain.com" am I going to break my > email lists? No. This is effectively what happens with anonymized lists. Both the From header field and the MAIL FROM protocol argument are set to the list-post address. > Will bounce processing still work? I think so. Pretty sure bounce processing on the bouncing side doesn't care who the envelope sender is, it is based on the RFC 822 sender, which is the Sender header field if set and the From field if Sender is not present. Maybe Errors-To enters the mix, but this is also a field in the message header. I doubt you need to make changes, and anyway if you condition the sender editing on being a random alias it won't affect Mailman at all. > Will replies to the list still work? Yes. All autopopulation of the addressees in replies is based on the "From", "To", "Reply-To", "Cc:", and "List-Post" fileds in the RFC 822 message header (you only get the last if you're lucky, though). As mentioned above, mail clients normally have no way to know what the SMTP MAIL FROM value is.

2 years, 1 month

[MM3-users] Re: Remove old bounces in bouncedir

by Mark Sapiro

On 3/10/22 00:31, Stephan Krinetzki wrote: > Mark Sapiro wrote: > >> If you are referring to messages in Mailman's bounces queue, if these >> are not processed and removed within 15 minutes of arrival, Mailman's >> bounce runner is not running. > > Well, it is the queue.Our var directory is under /opt/mailman/var and the /opt/mailman/var/queue/bounces is over 8GB big. There are *.pck messages and some of them are very old (>3 Years). The bounce seems to be running: > > ``` > Mar 10 09:24:53 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:00 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:06 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:12 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:18 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:24 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:30 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:36 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:43 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > Mar 10 09:25:49 2022 (376) Member xxx@xxx already scored a bounce on list list.lists.example.com today. > ``` > > The process it self is there > > ``` > mailman 376 99.4 19.1 6578312 6279000 ? R 09:17 10:52 venv/bin/python3 venv/bin/runner -C mailman.cfg --runner=bounces:0:1 > ``` I don't understand what's happening. If the bounces runner is processing it's queue, those .pck files should be processed and deleted. Are there errors in /opt/mailman/var/logs/mailman? If you examine (some of) those files with `mailman qfile` do you see anything strange? Is there an ownership/permissions issue? Sometimes people run Mailman or some Mailman command as `root` and things get owned by root and then when Mailman is later run as `mailman` it can't delete or maybe even read them. >> If you are referring to bounce messages in the message store >> (var/messages/), there have been issues with those not being removed, >> but Mailman core >= 3.3.5 should clean those up. > > SInce the messages are hashed or otherwise stored, i can't verify or deny this. Is the size of the /opt/mailman/var/messages directory very big? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Hyperkitty on Debian 12

by Markus Grandpre

Dear Michael, thank you very much for your clarification. Best regards, Markus Am 3/26/24 um 17:38 schrieb Michael Oberrauch: > On Tue, 2024-03-26 at 08:06 +0100, Markus Grandpré wrote: >> Dear Mr Sapiro, >> >> thank you very much for your help. The required command is: >> >> # mailman-web hyperkitty_import \ >> -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ >> /var/mailman21/testlist.mbox >> >> Due to the following warnings, I still have to customize Hyperkitty: >> >> django_mailman3.MailDomain: (models.W042) Auto-created primary key >> used >> when not defining a primary key type, by default >> 'django.db.models.AutoField'. >> HINT: Configure the DEFAULT_AUTO_FIELD setting or the >> DjangoMailman3Config.default_auto_field attribute to point to a >> subclass >> of AutoField, e.g. 'django.db.models.BigAutoField'. >> ... >> >> Can you give me another hint? As Linux admin I installed the packages >> mailman and mailman-web that were offered to me under Debian 12. >> Although during the installation of the packages user "list" was >> created, I cannot use it: >> >> # su - list >> This account is currently not available >> >> As with Mailman 2.1, I will probably have to continue working with >> Mailman3 as root. Too bad that there is no documentation for Debian >> admins like me, who don't want to dive too deep into the python >> framework. Or have I overlooked something? >> >> Best regards, >> Markus >> >> > > Hi Markus, > > we are also running MM3 on Debian 12 from Package Repositories. > > First of all, you should not try to directly switch user (su) to the > lists user, it's generally intended to executes commands as that user, > if necessary; either using `runuser`, `sudo`, or `su -c`. > > However, the prepackaged scripts `mailman-wrapper` and `mailman-web` > already do this and therefore you ca run those as root without > permission problems. > > On Debian there are two relevant users for MM3: the list user runs > mailman core, whereas the www-data user runs Postorius and Hyperkitty. > So you have to make shure, that the www-data user can access the .mbox > files while importing. > > Hope that helps. > > Cheers, > Michael > > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 7 months

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

by Mark Sapiro

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

7 years, 6 months

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Odhiambo Washington

On Sat, Aug 24, 2024 at 6:32 AM Ken Alker <mailman3.org(a)alker.net> wrote: > We have been experiencing a strange anomaly. We are running a small-ish > list. When a particular subscriber to the list sends an email to the list, > a couple of dozen (or more) of the recipient's of the message end up with > their bounce scores incrementing. This particular subscriber uses about > three different email addresses when he sends his messages and every one of > them causes this behavior. There is another subscriber who also causes > this behavior when he sends an email to the list, but only one of the two > email addresses he sends from causes this behavior. There is a third > person who causes this behavior every time. There are dozens of other > subscribes who don't generate this behavior when they send to the list. > > I can't figure out why this is occurring. I *assume* that Mailman > re-writes the headers to add DKIM, etc., before sending them to the list > recipients but it sure seems like something in the header from the original > sender is ending up in the final header (or something is LACKING) which is > not liked by the recipient's MTA's. It doesn't seem like a subscriber > sending an email to the list should be able to cause this behavior - but > I'm no expert. > > The recipients appear to be using many different mail platforms (ie. their > addresses are not all, or even mostly, @google.com or some other domain; > the recipients appear to be a pretty good cross section of platforms). > > This has been going on all year (maybe longer). Any help or > troubleshooting suggestions would be greatly appreciated. > When you say "I *assume* that Mailman re-writes the headers to add DKIM, etc., before sending them to the list recipients", I think there lies the issue. It's either you have configured MM3 to do the DKIM bit or it's done by your MTA. Only one is enough. But even DKIM is not the issue, but DMARC. So my lists are configured this: https://imgur.com/a/Wk82b7Z And I think with proper DKIM+SPF for your MM3s mail host, there should be no such phenomenon you're observing. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

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

by tlhackque

On 03-Aug-17 17:14, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > You've said you're working with labbrands.com <http://labbrands.com>. > > labbrands.com <http://labbrands.com> has address 192.185.51.89 > mail.labbrands.com <http://mail.labbrands.com> has address > 192.185.51.89 > www.labbrands.com <http://www.labbrands.com> is an alias for > labbrands.com <http://labbrands.com>. > > telnet proves that Exim is running on that IP address. Either you're > running it, or hostgator is redirecting the SMTP ports. > > You added: > lists.labbrands.com <http://lists.labbrands.com> has address > 190.145.27.66 > > Presumably that's a different machine. > > So that now needs an MX record, and a firewall routing. > > > I added the MX record on our hostgator hosting like this: > image.png > > Is it correct??? > No. And sending images to the mailing list doesn't get you help. You set up lists.labbrands.com as a secondary server, not an independent mail domain. This will cause you serious grief. You need to get some help from a more suitable list. Setting this up is not mailman-specific, and getting it right is more than a quick note. Try the Postfix documentation & mailing lists. > > > And the SPF > records ... and spam and virus filters, and all the other stuff > you need > to setup an independent, public-facing smtp server. > > But at least you won't have to relay. > > Good luck. > > On 03-Aug-17 16:55, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > > >> I think you're confused. > >> > >> You already have mail.labbrands.com <http://mail.labbrands.com> > set up as the MX record for > >> labbrands.com <http://labbrands.com>. And it has an A record > with the same address as your > >> webserver. > >> > > I'm working with the hostgator mailserver, we are not running a > local > > mailserver. > > > > As suggested I added an A record like this: > > [image: image.png] > > > > Is it correct? is it redirecting to my Ip so I can redirect it to my > > postfix/mm3 server? > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > >> server running on that IP address. You can't have 2 servers > on port > >> 25. In that case, as has been noted before, you'll need to setup a > >> relay in that server, not a firewall redirect. Depending on > your MTA, > >> you would need to relay to your internal server. And make sure > your > >> firewall setup allows your MTA to do this. > >> > >> We can see it's EXIM: > >> > >> telnet mail.labbrands.com <http://mail.labbrands.com> 25 > >> Trying 192.185.51.89... > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > (192.185.51.89). > >> Escape character is '^]'. > >> help > >> 220-gator4137.hostgator.com > <http://220-gator4137.hostgator.com> ESMTP Exim 4.87 #1 Thu, 03 > Aug 2017 15:47:48 > >> -0500 > >> 220-We do not authorize the use of this system to transport > unsolicited, > >> 220 and/or bulk e-mail. > >> 214-Commands supported: > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > >> quit > >> 221 gator4137.hostgator.com <http://gator4137.hostgator.com> > closing connection > >> Connection closed by foreign host. > >> > >> Or, consolidate all your e-mail to one server - which is a lot > easier to > >> manage unless you have a really big operation. Postfix is > probably the > >> right choice, but requires more setup. > >> > >> Although Mailman3 configuration is not well documented (as you've > >> discovered), you may want to get help from someone with more > general > >> network and mail experience. You're now into territory that is, as > >> Simon indicated, not Mailman-specific. > >> > >> On 03-Aug-17 16:28, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >> escribió: > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >>>> escribió: > >>>>>> You need to forward port 25 for SMTP mail delivery and if > you want the > >>>>>> web UI (Postorius and HyperKitty) accessible from the > outside, port 80 > >>>>>> for http and/or port 443 for https > >>>>>> < > >>>>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>>>> . > >>>>> I mean for incoming mail redirected from my hostgator > hosting, because > >>>> when > >>>>> I suscribe an email address MM3 sends a confirmation email, > so I have > >> to > >>>>> reply to be suscribed to the list. > >>>> As I said, for mail delivery you need to forward port 25 to > the Mailman > >>>> server. > >>>> > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local > >> centos7 > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > >>> > >>> > >>>> -- > >>>> 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> > >>>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >>>> > >> -- > >> This communication may not represent my employer's views, > >> if any, on the matters discussed. > >> > >> _______________________________________________ > >> Mailman-users mailing list > >> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- This communication may not represent my employer's views, if any, on the matters discussed.

8 years, 3 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 06/08/2019 09:48, Phil Thompson wrote: > On 06/08/2019 03:38, Abhilash Raj wrote: >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >>> I'm in the process of setting up mailman3. The only problem I seem to >>> be >>> having is getting Hyperkitty to archive messages. Rather than the >>> authorisation problems people have previously asked about on the >>> list, I >>> am getting a 403 error... >>> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >>> <html><title>Forbidden</title><body> >>> <h1>Access is forbidden</h1></body></html> (403) >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >>> <html><title>Forbidden</title><body> >>> <h1>Access is forbidden</h1></body></html> (403) >>> >>> Any suggestions would be appreciated. >> >> How did you install Hyperkitty? > > On Ubuntu... > > apt-get install mailman3-full > >> You probably need to the set the API key correctly in both Core and >> Hyperkitty. >> >> Have you looked at documentation here[1]? >> >> [1]: >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in >> quotes, single or double, doesn't matter) in your settings.py for Web >> (Django) should be same as the `api_key : value` (without quotes here >> in hyperkitty.cfg config file). > > That's all correct. I'm familiar with the authorisation issues that > other people have had. > > The only thing I'm doing differently (as far as I am aware) is that > I'm using a URL prefixed with /mailman3 which is stripped off in my > nginx configuration... > > # mailman3. > location /mailman3/ { > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > include uwsgi_params; > uwsgi_param SERVER_ADDR $server_addr; > uwsgi_modifier1 30; > uwsgi_param SCRIPT_NAME /mailman3; > } > > location /mailman3/static { > alias /var/lib/mailman3/web/static; > } > > location /mailman3/static/favicon.ico { > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > } > > ...but I don't see this affecting the mailman to Hyperkitty > communication. Posting to lists and the Postorius and Hyperkitty > frontends seem to work fine. I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my public IP address). However I now get a 400 Bad Request error. I have traced this to the archive() function in hyperkitty/views/mailman.py which is expect a POST but is actually getting a GET, specifically... GET '/mailman3/hyperkitty/api/mailman/archive?key=...' ...which seems to be a fairly fundamental problem. Again, any suggestions would be welcome. Phil

6 years, 3 months

[MM3-users] Re: Status of hosting options after a year for non techies

by Brian Carpenter

Hi Paul, I believe we are the only shared Mailman 3 service at the moment. Other companies that offer Mailman 3 hosting seem to only offer it on a dedicated environment which can be expensive for a single list owner. However we also offer that option but mainly has a cost savings alternative to those who need to host more than 10 lists. We have found Mailman 3 to require more maintenance than Mailman 2 and it seems to require more server resources. I believe we are also the only company that provides an installation service on those who want it on their own dedicated environment however we only do this for CentOS 7 and we utilize the Docker version of Mailman 3. The positive side is we setup the whole shebang including Nginx, Exim, and Let's Encrypt. I doubt cPanel (or any other Hosting control panel) will ever offer Mailman 3 in their package. Have a great day! Brian Carpenter EMWD.com brian(a)emwd.com -----Original Message----- From: paul(a)arenson.org <paul(a)arenson.org> Sent: Monday, August 26, 2019 12:41 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Status of hosting options after a year for non techies Hi all This is Paul Arenson in Japan. I temporarily dropped off the list year ago when it was clear there was no Cpanel Solution forthcoming. I thought I would check in again. I used to be on CPanel and I was advised it might be a wait. 1) I am now on Plesk. I heard Plesk might allow Docker and installation may be possible. Am I misinformed or a possibility? --->Assuming no, I guess jump to question 4. 2) Assuming yes, I see a list of people who can possibly help install. https://wiki.list.org/COM/Mailman%20consulting%20services Only a few people on it. Has anyone used any or can recommend someone. 3) There is also a Python list, but before I submit a request, is this something that works on general. For example, when a new version or bug release comes up, will I need to call on the person or persons again? Is it still better to wait? 4) Hosting services: Only a few listed at https://wiki.list.org/COM/Mailman%20hosting%20services are or Mailman 3. Has anyone used this: https://mailman3.com The site seems incomplete. Or this: https://maadix.net/en/servers Looks good. Might be a bit expensive for my use. Or this: https://www.mailmanhost.com/mailman-3-hosting/ Also looks good. A long time ago we corresponded. They seem reasonable. My list is about 700 people. These seem to be the same people: https://www.emwd.com/mailman-3-shared-list-hosting/ Any others I should know about? Thanks in advance. paul arenson japan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 2 months

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

by Mark Sapiro

On 9/18/19 11:13 PM, Paul Arenson wrote: > Thank you Mark. I appreciate the response. Let me respond in two messages. The first is to confirm the rules for signing off for both types of used: > > The second is to clarify my problems with the signup procedure and how I might deal with it. (Mostly a very small change on your part and an explanation on my website for my users) > > 1) So, for both subscribers vi postorius only and hyperkitty users: > email to discuss-leave(a)list.tokyoprogressive.org (or > discuss-unsubscribe(a)list.tokyoprogressive.org) Yes, but you seem to have some confusion about how things work. Mailman 3 consists of several pieces. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/introduction.html…>. As it says there, Postorius and HyperKitty are separate, web based applications for list management and archiving respectively. Both of these are Django projects - Django is a Python web framework. What you refer to as hyperkitty users are actually Django Users. When you create and account and/or log in at Postorius or HyperKitty, you are creating/logging in to a Django account. When you are logged in, Django, and thus Postorius and HyperKitty know who you are. If you aren't logged in, they don't. > 2) Only for hyperkitty users, you can login, go to > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > and click the big red unsubscribe button. You need to be logged in for this so Postorius knows who to unsubscribe. > 3) Also only for hyperkitty users, log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/ and click the Delete > Account tab or go directly to > https://list.tokyoprogressive.org/user-profile/delete This deletes your Django account, but does not affect your list memberships. > (Guessing that #3 will not unsubscribe the person and--if they have already done 1 or 2, failing to do number 3 is not going to be a big problem. Am I right?) That's right. The important thing is Postorius itself knows nothing about lists or list settings or list members. It gets and/or sets this information by communicating with Mailman core. You saw an example of this when you changed an archive from public to private. Postorius told Core to make it private and Postorius would then tell you it was private because it would get that information from Core. But, it required a daily cron job to propagate that setting to HyperKitty, so HyperKitty didn't get the memo until later. I hope this helps rather than adding confusion. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] GNU Mailman in Google Summer of Code 2022!

by Stephen J. Turnbull

Hi all, We are participating in Google Summer of Code 2022 (GSoC) under the Python Software Foundation (PSF). We did apply as a separate organization, but didn't get in. Many thanks to the PSF's GSoC organization for picking us up at the last minute! You can find our ideas page at https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202022, and item on the PSF ideas page under https://python-gsoc.org/ideas.html (which isn't so interesting about Mailman, but you can check out who else is under the PSF banner there). Discussion and development of project ideas will take place on mailman-developers(a)python.org. If you have a developed idea not already listed that you're willing to discuss and advocate, and you're willing to grab the template (last item on our ideas page on list.org) and fill it out, please post it to mailman-developers(a)python.org. (This a deliberate hoop-jumping exercise to filter in "serious" ideas.) You can put more weight on it by expressing interest in mentoring the project, and even more by actually volunteering! ;-) If you have a half-baked idea, and/or you want to get input from other Mailman users, of course you should feel free to discuss it on mailman-users(a)mailman3.org. We *might* pick it up from there, even if it's just a drive-by post with little support from the list members. But no promises about that, most of our attention will go to mailman-developers. If you feel some idea should get more love, polish it a little and post that to mailman-developers (don't cross-post, please). Again, we'd love to have more mentors, including backup mentors. We currently only have two mentors. Although we're both core developers, and I'm on an academic schedule and can devote plenty of time to the student during the summer, not so for Abhilash. Volunteering at this stage is not a promise to do more than look at student proposals. You would only be asked to look at the proposals, and volunteer as mentor for that project if you have interest and some level of knowledge to contribute to it. Even if you're a site admin with little Python programming experience, vetting interns' brainstorms about list admin-visible features and holding their hands until the "pros from Dover" arrive is quite helpful in making the student feel at home in our community. Many students are shy about blogging and communicating about their projects to the community -- just talking to them about their project and suggesting that they blog what they told you is helpful. Coding skills and knowledge of some part of the Mailman 3 code base are most welcome, of course, but you can make your mentor role what you want it to be. Regards, Steve

3 years, 7 months

[MM3-users] Re: 120 gmail users removed from lists !

by Odhiambo Washington

If Yunohost installed Mailman3 for you, then it's better to ask them to update it for you. On Tue, Oct 24, 2023 at 7:51 AM Yvan ♞ <elemac(a)free.fr> wrote: > Hello, > Thanks for this answer, my problem is I'm on yunohost server and the > update 3.3.9 is not available now. > Any "handmaid" solution should be great. > Sincerely > > Le 22/10/2023 à 10:45, Stephen J. Turnbull a écrit : > > elemac(a)free.fr writes: > > > > > Hello, on 15th October, 120 users with gmail address where suddenly > > > removed from lists in mailman3, something changed in google ? > > > > Google is evil, who knew? > > > > Google decided to publish a DMARC policy of "p=none". This announces > > to the world that you have to decide for yourself whether to accept > > mail from Gmail with a broken DKIM signature from gmail.com. Gmail > > has decided that they will not accept such email from themselves, even > > though they know more about the sender than anyone else, and even have > > access to the original sender copy. > > > > Mark has a patch that applies your preferred DMARC mitigation to Gmail > > authors unconditionally. I think it's in the new version just > > released 3.3.9, so you can upgrade. The name of the variable is > > dmarc_addresses, and in Postorius it will be in the same settings > > group as other DMARC settings, with a similar tag. > > > > If for some reason you strongly prefer not to upgrade immediately but > > want this feature, it's commit #8532f751b6b8bfee3210c1327d755756f99d99ac > > (you can shorten that to 8532f). I do not recommend this. It probably > > is independent of other changes in 3.3.9 from other releases. But if > > not you could have issues. > > > > I think you also need the patches in Postorius, but I don't think > > they've been released yet. "Coming soon" as they say. The relevant > > commit is #770add1ebf27fd335c675607f26bb8f7cf313ddd, > > > > If you search back in the archives, I think Mark posted a link to his > > original patches. > > > > Steve > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com > -- 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

[MM3-users] moving from sqlite3 to postgresql

by Stephen J. Turnbull

Michael Richardson writes: > My upgrade was in part a response to the HTTP based attacks that used the signup > form on mailman2 to attack people via SMTP with DOS. I know the IETF > mailman2 install {now gone} had some kind of delay implemented in the web > form before you could submit. I didn't understand why. Partly it was a successor to TMDA (a challenge-response system to make senders verify they could receive mail at the source address, which weeds out a lot of spam), and partly a hack where a mailing list (which cannot be posted to) is used as a database of "community members", ie, anybody who has passed the challenge for any list is allowed to post to all the "public" lists (and vice versa: getting banned from that list is "IETF death"). > I installed via debian packages, and I'd really prefer to stay with that. > (Not what many maintainers would say, I know. Essential that it work if > mailman3 is going to take over) That's really Debian's problem, and it's a hard one since the whole point of using Debian packages for mission-critical applications is that they're stable. Unfortunately, the email and web environments are not, and dealing with changes in them is often quite impractical given the Debian release cycle. > I installed with sqlite3, since it seemed if all work was going to > go through the mailman3 daemon, that it would handle all the > concurrency issues. The problem is that sqlite3 is intended to be a single-threaded system, but Mailman 3 by default spawns around 15 daemons that may try to access the database. I would expect you would have warnings that the database is locked frequently. Not sure what you mean by "Sometimes this goes way on it's own, but sometimes it does not". Note that our primary purpose for the sqlite3 configuration is so unit tests don't have to spin up a full-scale PostgreSQL or MySQL database. > So I tried to switch last week from sqlite3 to postgresql. > I used pgloader with a configuration file attached below. Can't help you with that offhand, never used pgloader. Whatever method you use to load up the pg database, I would recommend doing some psql cave-diving into the PostgreSQL database to confirm it's sane before trying to configure Mailman to use that database. > ps: I'd pay some $$ money for email support consulting. See https://wiki.list.org/COM/Mailman%20consulting%20services Per my .sig, I'm on the list above but please go through channels linked there rather than talking to me personally about business. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 3 weeks

[MM3-users] deployment recommendation(?)

by noc＠iem.at

(sorry, if this comes in double; i sent the same mail yesterday, but it seems it didn't make it (i did check the archives); so i'm re-sending via the webinterface) hi, it's summer here in europe, and students have left the campus. so - like every summer - I ponder on the idea of migrating our old mailman2 instance that has served us for the last twenty years to a new and shiny mailman3. and - like always - i'm a bit unsure about the best way to proceed to find the optimum deployment strategy for a long-running (decades) medium-sized (our largest list has ~1800 members) installation. one of our primary objectives is receiving *security updates*. we also would like to stay on top of development (that is: use the latest and greatest *stable* mailman3 release). in my heart i am a Debian person, so my mailman2 installation just used the Debian packages. the new deployment machine, will be Debian based as well. now https://docs.mailman3.org/en/latest/install/install.html lists three options: # Debian packages this is what I would normally pick, but: my past experience with mailman3 in Debian was... rather suboptimal. (my current Debian box running mailman3 is frozen at Debian/buster ("old-old-stable") because of mailman3). i see that the packages in current Debian/stable ("bookworm"), are lagging slightly (3.3.8, rather than 3.3.9), though that's to be expected from a distro with stable releases. otoh, Debian/unstable still ships 3.3.8, which is a bit disappointing. in any case, the really nice thing about (Debian-official) Debian packages is that they are typically - stable - guarantee an upgrade path between releases # Docker packages this is of course the simplest from a deployment perspective, but then i'm a bit worried about the security perspective. in my perception, docker deployments tend to get installed and then forgotten, and while the host OS keeps getting updates, the docker images are just left as is. so they tend to get stale. i would like to know how this is handled # virtualenv this is the deployment method recommended in the docs. however, it doesn't say why this method is any better than the others. also, the website says that it was last updated in 2019, so: is this recommendation still relevant? personally i do not have much experience with deployment of long-running software in virtualenv, and i'm esp worried a bit when it comes to switching python releases (which will happen multiple times in the next few years) i use virtualenv all the time for my pet projects, but there it doesn't matter much, if the venv breaks: i just delete it and start from scratch. but those are not long-running services. so: what are the drawbacks, limitations, advantages and benefits of the various deployment methods? i'd really like to make the switch this year! gmfasdr IOhannes

1 year, 3 months

[MM3-users] Re: Found error in docker-container

by Abhilash Raj

Hi Alex, On Mon, Jul 17, 2017, at 06:32 AM, Alexander Klotz wrote: > Hi, > > unfortunately I have to get back to this topic, since there's still a > problem. We already removed the comments as you suggested, but we still > have to make manual corrections when creating a new list, because the > alias information is safed incorrectly in the tables of the postfix > host. There is a port indication with a "]" in the comments, but it is > incomplete. The proper address has to be inserted here. Let me do some testing before I answer this, so I will get back to you with some better answers than "it should not be happening". > Regards, > Alex > > > > > On Wed, Jul 5, 2017, at 03:21 AM, Alexander Klotz wrote: > >> Hi, > >> > >> one of our developers wanted to point out an error he found in mailman > >> 3.1, docker container maxking/mailman-core-0.1 > >> > >> The entries in /opt/mailman/core/var/data/postfix_lmtp are not set > >> correctly, example: > >> > >> /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2# IP > >> Address of mailman-core container]:8024 > >> > >> this actually should look like this: > >> > >> /^testlist(a)mailman\.example\.com$/ lmtp:[172.19.199.2]:8024 > > > > > > Can you send a copy of your Mailman configuration that you added at > > `/opt/mailman/core/mailman-extra.cfg`? > > > > I think this is mostly because the configuration parser doesn't > > understand the in-line comments. So, if you are using the configuration > > exactly as it is mentioned in the documentation, it could be the cause > > of this problem. > > > > Solution to that would be to just remove all the in-line comments. > > > > [mta] > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > lmtp_host: 172.19.199.2 # IP Address of mailman-core > > container > > lmtp_port: 8024 > > smtp_host: 172.19.199.1 # IP Address of host where > > postfix is. > > smtp_port: 25 > > configuration: /etc/postfix-mailman.cfg > > > > > > > > Like the two comments seen in the configuration above. > > > > I will update the documentation too so that others don't get caught in > > something like this. > > > > Thanks! > > > > > -- > Mit freundlichen Grüßen, > Alexander Klotz > > (redaktion kulturserver) > > mailto:alexk@kulturserver.de > > Stiftung kulturserver.de gGmbH > > Lothringerstraße 23 > D-52062 Aachen > http://ggmbh.kulturserver.de > > Geschäftsführer: Wolfgang Knauff > > Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 > Umsatzsteuer-Identifikations-Nr.:DE DE 230868040 -- thanks, Abhilash Raj

8 years, 3 months

[MM3-users] Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Internal Server Error: /archives/api/mailman/archive OperationalError at /archives/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0A\\x0A...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1")

by Mark Sapiro

2 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by matthew＠alberti.us

I should clarify a bit. That connection string I mentioned in the previous post is in the docker-compose.yaml file for the docker-mailman containers. For web, it seems the settings.py file for the mailman-web container is configured to parse connection string, but there isn't (I don't think) any provision to set additional options, such as the encoding. So there doesn't appear to be a straightforward way, using the container yaml approach, to pass the 'OPTIONS' for the encoding. It does however look like it is possible to override the whole database connection settings using settings_local.py, but unsure. That would I think be the way to do it, setting the whole database configuration settings per https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_project /settings.py#L156 in the settings_local.py file. For core, the connection string seems to accept a tailing "?charset=utf8&use_unicode=1" per https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So for core, maybe just updating the connection string to include "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the recommend encoding... maybe that should be updated? I realize this may be drifting more towards concerning the docker container setup vs. non-containerized core and web. But either way, these seem to be mysql specific caveats that I've certainly missed. Hopefully this helps someone else. Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is recommended, and it needs to be explicitly identified in the database settings for BOTH core and web, and probably somehow at database creation time? Now to see what the best procedure is to put these configuration changes in place, and also update the database? - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, December 9, 2020 9:35 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing On 12/9/20 6:06 PM, matthew(a)alberti.us wrote: > Thanks Mark. Also, just to confirm, should the database connection > string also be updated? In both the core and web configuration, I have > something > like: > > DATABASE_URL=mysql+pymysql://mailman:password@database/mailmandb > > Note the trailing UTF-8 encoding stuff isn't there. Should we be > specifying > utf8mb4 there as well? In the mailman.cfg database section, you probably want url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8mb4&us mysql+e_unicode=1 I don't know why you would have a DATABASE_URL setting in the web configuration. Exactly where is this? I don't think it would be meaningful in any Django settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 11 months

[MM3-users] Re: Twitter OAuth2

by Odhiambo Washington

On Thu, Dec 29, 2022 at 3:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/28/22 11:37, Odhiambo Washington wrote: > > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 12/27/22 21:46, Odhiambo Washington wrote: > >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >>>> > >>>> I see from another post that you've decided against using Twitter, but > >>>> to answer the question, Twitter does not require adding anything to > >>>> SOCIALACCOUNT_PROVIDERS. > >>>> > >>> > >>> I tried it and ended up with: > >>> > >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server > Error: > >>> /accounts/twitter/login/ > >>> Traceback (most recent call last): > >> ... > >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching > >>> query does not exist. > >> > >> > >> Do you have > >> > >> 'allauth.socialaccount.providers.twitter', > >> > >> in INSTALLED_APPS? > >> > > > > Here is what I have in settings_local.py: > > > > INSTALLED_APPS = ( > > 'hyperkitty', > > 'postorius', > > 'django_mailman3', > > # Uncomment the next line to enable the admin: > > 'django.contrib.admin', > > # Uncomment the next line to enable admin documentation: > > 'django.contrib.admindocs', > > 'django.contrib.auth', > > 'django.contrib.contenttypes', > > 'django.contrib.sessions', > > 'django.contrib.sites', > > 'django.contrib.messages', > > 'django.contrib.staticfiles', > > 'rest_framework', > > 'django_gravatar', > > 'compressor', > > 'haystack', > > 'django_extensions', > > 'django_q', > > 'allauth', > > 'allauth.account', > > 'allauth.socialaccount', > > #'django_mailman3.lib.auth.fedora', > > #'allauth.socialaccount.providers.openid', > > 'allauth.socialaccount.providers.github', > > #'allauth.socialaccount.providers.gitlab', > > 'allauth.socialaccount.providers.google', > > 'allauth.socialaccount.providers.facebook', > > 'allauth.socialaccount.providers.twitter', > > #'allauth.socialaccount.providers.stackexchange', > > ) > > > Did you add an app at https://site.name/admin/socialaccount/socialapp/ > with twitter as a provider? See > > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… Exactly, and I have entered all the credentials from the "OAuth 2.0 Client ID and Client Secret" of the twitter developer portal. https://webmail.kictanet.or.ke/~wash/twitter-oauth.png I have checked my settings_local.py several times trying to find out why the entry is ignored. -- 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] [Suspected Spam]Exim, Mailman3 and missing Message-ID:

by Stephen J. Turnbull

Robert: Thank you very much for the analysis and the configuration. Robert Lister writes: > As (bad) luck would have it, the very first real message bounced: :-( This is *very* bad luck. I don't think I've seen messages without Message-ID in decades! > Mail client: X-Mailer: Microsoft Outlook 16.0 > > So it seems in certain circumstances, Outlook doesn't put a Message-ID: > header in its messages. Outlook is not my favorite MUA (and I don't mean that I don't like using it). Nevertheless, RFC 5321 suggests that the responsibility for dealing with this or rejecting the message is with the submission host: The following changes to a message being processed MAY be applied when necessary by an originating SMTP server, or one used as the target of SMTP as an initial posting (message submission) protocol: o Addition of a message-id field when none appears o Addition of a date, time, or time zone when none appears o Correction of addresses to proper FQDN format The less information the server has about the client, the less likely these changes are to be correct and the more caution and conservatism should be applied when considering whether or not to perform fixes and how. These changes MUST NOT be applied by an SMTP server that provides an intermediate relay function. The context strongly suggests that a similar caution applies to final delivery servers, and I would assume Mediators such as Mailman. I conclude that the post is broken and very good reason would be needed to patch it up. > Therefore, Mailman3 using LMTP means exim will NOT "fix up" this problem > before mailman3 receives the message. As I read the passage you quoted, Exim won't fix up the problem regardless of whether it delivers to Mailman via LMTP or by pipe, etc. The problem is that Mailman's LMTP server rejects malformed mail. I seem to recall that in Mailman 2, Mailman itself would add a Message-ID field if one was not present. I don't know how easy it would be to provide this feature, since we would have to patch the LMTP server code so the message could make it to Mailman proper (Mailman 3 imports the LMTP server from the stdlib). > My solution for now (apart from telling people not to use old > broken Outlook!) is to modify the exim mailman3_transport so that > any message with a missing Message-ID: will have one generated by > exim before it's passed to LMTP. This reproduces the same behaviour > exim uses for locally submitted messages. I'm not sure it's a good idea to do this (and certainly not by default). The only times I've seen messages without a Message-ID are spam messages. I suppose we can add this to the documentation. Steve

6 years, 3 months

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

by Allan Hansen

Mark, Will this be part of an upcoming update or micro update to Mailman? Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630 > On Mar 31, 2023, at 15:49, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/31/23 14:17, Andrew Hodgson wrote: >> Hi. >> Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. > > > First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in > ``` > --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 > +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 > @@ -2,13 +2,13 @@ > import os > import sys > > -sys.path.insert(0, '/opt/mailman/mm') > +sys.path.insert(0, '/etc/mailman3') > # The above line is required. The next line doesn't hurt, but it doesn't work > # because the PYTHONPATH environment setting is processed by Python's setup > # and must be in the environment when Python starts to be effective. > -os.environ['PYTHONPATH'] = '/opt/mailman/mm' > +os.environ['PYTHONPATH'] = '/etc/mailman3' > os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' > -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' > +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' > > import django > django.setup() > ``` > Also, look at this > ``` > # If we delete the Django user and there is a Mailman user with no memberships > # shall we delete the Mailman user too. > DELETE_MAILMAN_USER = False > # Shall we delete the Django user if there is a Mailman user with no > # memberships or only if there is no Mailman user. > DELETE_DJANGO_IF_MAILMAN = True > ``` > and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to hansen(a)rc.org

2 years, 7 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Odhiambo Washington

On Wed, Aug 7, 2024 at 11:52 AM IEM Network Operation Center (IOhannes m zmölnig) <noc(a)iem.at> wrote: > thanks both Mark and Odhiambo (who replied off-list) for your answers. > > On 8/6/24 18:40, Mark Sapiro wrote: > > On 8/6/24 01:43, noc(a)iem.at wrote: > >> > >> but how can i export an entire MM3 list (including 20 years of > >> archives) to some serialization format, and import it again in another > >> instance? > > > > > > With the dump and other utilities from your database manager. Almost > > everything is in the database. There are some things in Mailman's var/ > > directory, but those can simply be moved. > > > > urgh. > while this will (hopefully) work with a fresh installation, i'm somewhat > afraid whether this will also work for: > - migrating a single list from one instance to another (at least, if you > (like me) do not have have an intimate knowledge about the db layout) > Hmm.. I think I did something like this in the recent past. I need to remember how I went about it though, but it could be something like: (Assuming a virtualenv install) I believe you could: 1. Make a full backup of the old MM2 install - I mean the DB and the MM3 files. 2. update the install to the latest version corresponding to the one on the new server. 3. Delete all lists with their archives EXCEPT that one list you want to migrate. 4. Export the DB(s) 6. !! Backup the DBs on the new server (just in case something bad happens!! 7. Import the DB dumps from the old server into the new one. Hopefully, there are no conflicts with the sites - importing lists into an instance that is already populated with other > lists (things like changed db schemas come to my mind) > Here again, you should have both sites running at the same software level. right now my task is to move both some MM3 lists (from an old MM3 > instance) and some MM2 lists onto a single server with a fresh > installation, so i guess i will be fine. > Okay. > my worries are mostly about future migrations. > Sit down and write down your plans. Always come back here for 'sanity checks' on those plans. > is a feature-request warranted, or am i worrying too much? > A feature to automate your migrations? Have you consulted ChatGPT yet? :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 3 months

[MM3-users] Creating users via RestAPI / User-Management - a bunch of questions

by Christian Schneider

Dear Mark and companions, somehow I can not cope with the user management... (I am running a venv-installation, latest stable versions) I read this manual: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… and played with the RestAPI calls... I know about the fine grained differences between user and member, admin/owner, superuser... and about the two user databases in PostgreSQL and Django-Framework. What I stumble upon is the RestAPI calls to create a "working" user (with the ability to login via WebUI). When I follow the manual (from the url above) I create a user (including password) that appears in the PostgreSQL database. (And this user is visible on the User-URL (https://example.com/mailman3/users)) Even when I (via WebUI) set the user as "approved" this user is not able to log in... I assume this restriction is in accordance to the fact that there is not equivalent Django user. (There was a mail in the archive of the MM3 user group...stating that one has to use the Django RestAPI to create the appropriate user) When I create the user using the WebUI (https://example.com/accounts/signup/?next=/mailman3/lists/) the new user is created in the right (complete) way...appearing in the PostgreSQL database and as a user in Django. How is this sync between the two databases realized? (The Django user also has the correct status (no staff status / no superuser status / just active status) how is this realized?) As I am not very familiar with python programming (I know Perl/Java/C++ and have an (maybe outdated) concept of OOP), is there a quick way to implement this kind of sync by copying the register logic from mailman's python action script for registering? Other questions: Will there be a create_admin_user-script that is callable via CLI (like createsuperuser or create_list)? (This script ought create a user in PostgreSQL and as Django user) How will a social account provider (like oidc) linkage (in Django) fit in this concept? Will oidc-accounts be copied to the Django's user database (or PostgreSQL db) or is it an on-the-fly check against the oidc-provider? (I assume second option) What are the status-flags (staff status/superuser status/active status) of the linked oidc-accounts? (Can I specify the status flags?) A conceptual thought: When "user1" (with email user1(a)example.com) is known to django via oidc linkage and I create "user1" (also with email user1(a)example.com) via RestAPI calls (following the url https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) do I have a "complete" user then? I mean a user who is able to login and who can be assigned to a list as admin (e.g.) (In this case I would not have to care about the Django user database... ;-)) Thank you for some clarifying hints... :-) Chris

4 months, 2 weeks

[MM3-users] Re: So, why are css & js files only served with "DEBUG = yes" ?

by Simon HANNA

js and css files are static and should be served by your web server of choice. In a development environment you usually don't have a web server running, so django serves the files itself. Your webserver can serve these static files much faster than django can, so django doesn't serve them in production by default. You can find instructions on how to do so online (Google is your friend) but since that's not incouraged there is no point in including these in the repos. Simon Am 7. Mai 2017 16:06:17 MESZ schrieb Simon Liebold via Mailman-users <mailman-users(a)mailman3.org>: >Hello List, > >I did see this discussed in #180 ><https://gitlab.com/mailman/postorius/issues/180>, but I didn't quite >understand if this is an issue or not. > >Why is it that I can run the development server just fine. > > [07/May/2017 13:23:47] "GET > /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/postorius/css/style.css > HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/django-mailman3/js/main.js > HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/django-mailman3/css/main.css > HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/postorius/js/script.js HTTP/1.1" > 304 0 > [07/May/2017 13:23:47] "GET > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 304 0 > >And as soon as I comment out > > # SECURITY WARNING: don't run with debug turned on in production! > # DEBUG = True > >in mailman-suite/mailman-suite_project/settings.py and restart it 404s >on me. > > [07/May/2017 13:41:36] "GET >/static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 >127 > [07/May/2017 13:41:36] "GET /static/django-mailman3/css/main.css > HTTP/1.1" 404 109 > [07/May/2017 13:41:36] "GET /static/postorius/css/style.css > HTTP/1.1" 404 104 > [07/May/2017 13:41:36] "GET /static/django-mailman3/js/main.js > HTTP/1.1" 404 107 > [07/May/2017 13:41:36] "GET > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 404 125 > [07/May/2017 13:41:36] "GET > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 404 123 > [07/May/2017 13:41:36] "GET /static/postorius/js/script.js HTTP/1.1" > 404 103 > [07/May/2017 13:41:36] "GET > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 404 123 > > >So the choice is insecure vs. ugly? Neither of those sounds very >tempting. > >I guess, I am missing something, or no? > >Simon > >_______________________________________________ >Mailman-users mailing list >mailman-users(a)mailman3.org >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 6 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by mark＠suburbia.org.au

Mark Sapiro wrote: > To diagnose this further, can you create a test list, set Default action > to take when a member posts to the list to Hold, mass subscribe an > address and send a post from that address and see if it's held. It > should be, and if it is, I think things are working as they should be > and a test post to the original list from one of these mass subscribed > members will be held. I've done some testing as follows: - Created a test list - Migrated the existing list in question from its mm21 config.pck to the test list - Changed the display name to avoid confusion :-) - Checked moderator settings for the list: - Default action to take when a member posts to the list: Hold for moderation - Default action to take when a non-member posts to the list: Discard (no notification) - Emergency moderation: No - Accept/Hold/Reject/Discard non-members: all blank - CSV exported the 247 existing list members - Pasted all exported member addresses from the CSV into the mass removal web page, *except* for the list-owner. After doing so hoped that they didn't all get an unsubscribe mail. Given that "Send goodbye message" was set to yes, I suspect I did. :-\ - Confirmed List members only had the list owner - Added a first new test user (me) via mass subscribe, ticked Pre confirm, Pre approved, Pre verified. Received welcome email - Confirmed List members; list owner "Hold for moderation", test user "None" - Added a second new test user (me with a second email address) via mass subscribe with same settings as above. Received welcome email - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" - Sent an email from test user 1 to the list - Sent an email from test user 2 to the list - Sent an email from a third email address that isn't on the list - Looked at Held messages: - test user 1 email was held for moderation in Web UI. User 1 received an email indicating as such. - test user 2 email was held for moderation in Web UI. User 2 received an email indicating as such. - non-member email was neither held for moderation, nor sent to the list. > If that is true, I can only think that at the time of that post, > settings weren't as they are now. I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Cheers, Mark

11 months, 3 weeks

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

by Jan Eden

On 2023-01-04 12:40, Mark Sapiro wrote: > On 1/4/23 11:39, Jan Eden via Mailman-users wrote: > > Hi, > > > > my question is not related to Mailman directly, apologies for using this > > list. I configured the DNS records for my base domain and my lists > > subdomain identically (the DMARC policy records are also identical, but > > not listed here): > > > > MX @ mail.eden.one > > TXT @ "v=spf1 mx ~all" > > MX lists mail.eden.one > > TXT lists "v=spf1 mx ~all" > > > > A mail 123.123.123.123 > > > > But both Yahoo and Google report different SPF results for the two domains: > > What could possibly cause this difference? The SPF test also fails for a > > [...] > > different base domain with the same MX and SPF records. > > Your spf for lists.mail.eden.one specifies its MX which is also > lists.mail.eden.one, however mail from that domain arrives from IP > 123.123.123.123 and presumably an rDNS lookup returns mail.eden.one which is > not lists.mail.eden.one, thus the failure. > > Add the IP 123.123.123.123 to the spf and drop the MX since it doesn't work > > TXT lists "v=spf1 123.123.123.123 ~all" This would explain a lot, but it also invalidates everything I thought to have understood about DNS records. Maybe the abbreviated records above (quoted from my provider's web interface) were misleading, so here's the output of dig: eden.one. 60 IN MX 10 mail.eden.one. eden.one. 60 IN TXT "v=spf1 mx ~all" lists.eden.one. 60 IN MX 10 mail.eden.one. lists.eden.one. 60 IN TXT "v=spf1 mx ~all" mail.eden.one. 60 IN A 123.123.123.123 So an MX lookup for both eden.one and lists.eden.one returns the hostname mail.eden.one, which points to the address 123.123.123.123. The SPF records for eden.one and lists.eden.one refer to the respective MX records (with the same target hostname). According to RFC 7208[1], the mx mechanism "matches if <ip> is one of the MX hosts for a domain. [...] check_host() first performs an MX lookup on the <target-name>. Then it performs an address lookup on each MX name returned. The <ip> is compared to each returned IP address. [...] If any address matches, the mechanism matches." So in both cases, the MX mechanism should first retrieve mail.eden.one, and then 123.123.123.123 via DNS queries, and should match accordingly when the message was sent from mail.eden.one/123.123.123.123. Although I could specify the IP address in my SPF records directly (as you suggested), I do hope that my understanding of DNS records laid out above is not entirely misguided. My current setup does work as expected for eden.one, after all. - Jan [1] https://www.rfc-editor.org/rfc/rfc7208#section-5.4

2 years, 10 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Odhiambo Washington

On Wed, Aug 7, 2024 at 1:05 PM IEM Network Operation Center (IOhannes m zmölnig) <noc(a)iem.at> wrote: > On 8/7/24 10:52, IEM Network Operation Center (IOhannes m zmölnig) wrote: > >> > >> With the dump and other utilities from your database manager. Almost > >> everything is in the database. There are some things in Mailman's var/ > >> directory, but those can simply be moved. > >> > > sorry for keeping you all busy, but: which "things in Mailman's var/" > need to be copied over to the new host? > > in my old instance (from Debian packages) i find in /var/lib/mailman3/: > > - ./archives: dirtree without files > - ./cache: (afaict) currently active templates for mailinglist mails > (hashed filenames) - i assume that these can safely be ignored and will > be restored from the db? > - ./data: empty > With a Postfic MTA situation, that would have had some files. So you don't use Postfix. > - ./lists: empty directories named after each list (i think these are > used by the MTA to determine whether it should hand over a mail to the > mm3-ltmp) > True, at least according to Exim MTA. > - ./locks: plenty of lock-files, most of them rather stale (as in: 3 > years old) > So MM3 on that host hasn't been running or? - ./messages: a couple of old messages (i think all of them have been > held for approval) > - ./queue: dirtree without files > - ./templates: more templates for the existing mailinglists, though they > don't seem to be used (are these the fallbacks when I remove a template > via the webinterface?) > Yes. > - ./web/static/*: seem to be copied over from various Debian packages > (dependencies of mm3), with minor differences in icons and jquery (I > assume these files get copied over when the mm3 instance is created, and > do not get updated when the corresponding Debian packages get updated) > - ./web/static/CACHE - can these be ignored? > - ./web/fulltext_index: are these files regenerated when running > "update_index"? > Yes, the files can be regenerated. > so i think the only stuff that needs to get recreated from mailman's var > is the ./lists directory. > is this correct? > For your MTA to know that your lists exist. So out here we focus so much on the following as the Bible for installing and running MM3: https://docs.mailman3.org/en/latest/install/virtualenv.html -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 3 months

[MM3-users] Ann: Postorius 1.3.6 is now out

by Abhilash Raj

Hey Everyone, I just tagged and released Postorius 1.3.6. This release includes both bug fixes and new features. Some of the notable features include - Ability to list and handle un-subscription requests to the list - Option to choose delivery mode and delivery_status directly when subscribing to a list - Addition of a user management interface, which allows updating a users password, manually verifying their email addresses, update user’s Display Name etc. - Expose a number of Bounce processing related options in List’s settings A full list of changes is available here https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 You can install this release using pip $ pip install postorius django-mailman3 mailmanclient —upgrade Do note that this release requires Mailman Core 3.3.5, so you need to upgrade Core before upgrading Postorius. The release tarball is available on PyPI as usual: https://pypi.org/project/postorius/1.3.6/#files Please also ensure to run the post-install commands as per the upgrade documentation: https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade Thanks to all the folks who helped with this release! Abhilash > Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). > On Sep 19, 2021, at 8:48 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hey Everyone, > > I am pleased to announce that Postorius 1.3.6b1 is now out. This is the first pre-release for 1.3.6, which is slated to release next week soon after Mailman Core 3.3.5 release. > > This release requires Mailman Core 3.3.5 release, so if you are trying out this release, please also upgrade Mailman Core to 3.3.5rc1 (which was just released today). > > This release includes several new features and bug fixes. A full list of changes is available here[1]. > > With this release, we have also improved on the localization of the interface, if you want to help out before the release of the stable 1.3.6, please see the instructions for translators here[2]. We use Weblate for translations, so if you are familiar with that, you can directly head over there[3]. > > Since this is a pre-release version, you can install this using pip via: > > $ pip install --upgrade --pre postorius django-mailman3 mailmanclient > > Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). > > A release tarball is available on PyPI: > > https://pypi.org/project/postorius/1.3.6b1/#files > > Finally, thanks to all the folks who helped with this release in any capacity and made it possible. > > [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 > [2]: https://docs.mailman3.org/en/latest/translation.html > [3]: https://hosted.weblate.org/projects/gnu-mailman/postorius/ > [4]: https://docs.mailman3.org/en/latest/upgrade-3.2.html#virtualenv-install > > > thanks, > Abhilash -- thanks, Abhilash Raj (maxking)

4 years, 1 month

[MM3-users] Slow and out-of-sequence delivery

by Gregg Roberts

Dear Mailman Supporters, I participate in a professional forum run on Mailman. It serves a small nonprofit mutual benefit organization with possibly fewer than 50 members. Messages that I post to the forum have been taking as long as 48 hours to come back to me. The issue is not new and AFAIK no one has been messing with the settings. But the issue seems to have been becoming more and more severe in recent weeks. Perhaps because of such delays, I also sometimes see responses to other posts before I see the original post. It takes extra time to understand the context when that happens. People's time gets wasted answering questions that have already been answered without their knowledge. It's just frustrating all around. The email address from which messages are sent is not in the list of email addresses maintained in the hosting account cPanel. There seems to be one by the name "relay" that is being used by Mailman. I actually don't know which version of Mailman is installed. I'm hoping it's the more recent of the two options so I optimistically joined this particular list. The hosting service tech support can't help because they can't see the forum email address or its logs. At least that's what they say. Tech-support also tells me that they routinely do load-balancing and the server should not be excessively busy. It should certainly not take 48 hours to send an email message to 50 recipients. It shouldn't even take more than an hour, because the system is set to send messages at least once per hour -- maybe even every 10 minutes -- and the whole queue should be able to be handled in one sending cycle ... right? A contract tech support guy has suggested that it might solve a problem if we started spending $100-$150 per month on a dedicated server. I think that is a wrongheaded suggestion. If the organization had thousands of members, it would make more sense. But throwing money at the problem if something is simply not set up right, or some critical file is corrupted, is not the right solution. Set the broken bone correctly first, THEN inject stimulants and send the player back out onto the field. :-) Thanks in advance for any help! Gregg Roberts http://legalsupport-sc.com Legal Support Services of Southern California 43430 E. Florida Ave #F-293 Hemet CA 92544 951-330-4450 The information contained in this e-mail message is privileged and confidential information, intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution of copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone at 951-330-4450 or reply by e-mail and delete or discard this message.

2 years, 10 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

I'll dig at that; thanks. I've just managed to get one of my Google accounts into this "broken" state, although I'm not entirely sure how I did it (or where the broken state is stored). This happened after I tried using the "Sign In" button on a list info page rather than the one in the upper right corner, but that may just be a red herring. I'll report back if I find anything. --Jered ----- On Dec 6, 2023, at 3:21 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 11:00, Jered Floyd wrote: >> > These errors are generated to me as the admin, and in the elided > environment section SITE_ID is indeed 0, but I'm at a loss to imagine > why this happens only sometimes! > > For me, on a test installation with SITE_ID = 0, this only occurs at > https://example.com/accounts/social/connections/ > > Other URLs such as https://example.com/accounts/password/change/ and > https://example.com/accounts/email/ do not throw this exception. > > Here's the code: > ``` > def get_current(self, request=None): > """ > Return the current Site based on the SITE_ID in the project's > settings. > If SITE_ID isn't defined, return the site with domain matching > request.get_host(). The ``Site`` object is cached the first > time it's > retrieved from the database. > """ > from django.conf import settings > > if getattr(settings, "SITE_ID", ""): > site_id = settings.SITE_ID > return self._get_site_by_id(site_id) > elif request: > return self._get_site_by_request(request) > > raise ImproperlyConfigured( > 'You\'re using the Django "sites framework" without having ' > "set the SITE_ID setting. Create a site in your database and " > "set the SITE_ID setting or pass a request to " > "Site.objects.get_current() to fix this error." > ) > ``` > > I tried patching it from > ``` > if getattr(settings, "SITE_ID", ""): > ``` > to > ``` > if getattr(settings, "SITE_ID", None) is not None: > ``` > but that's even worse. It throws a bunch of > "django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist." errors. > > Somehow, get_current is being called without a request object in the > cases where it fails. > > -- > 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 jered(a)convivian.com

1 year, 11 months

[MM3-users] Re: E-mail every minute: "Cron <www-data@sharky5> ..."

by Robert Heller

At Sun, 7 Jul 2024 19:48:02 +0300 Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > On Sun, Jul 7, 2024 at 7:16â¯PM Robert Heller <heller(a)deepsoft.com> wrote: > > > At Sun, 7 Jul 2024 18:52:05 +0300 Odhiambo Washington <odhiambo(a)gmail.com> > > wrote: > > > > > > > > On Sun, Jul 7, 2024 at 4:12ÃÂ¢Ãâ¬ÃÂ¯PM Robert Heller <heller(a)deepsoft.com> > > wrote: > > > > > > > What am I missing? I *think* I have mailman3 *mostly* setup, but there > > > > are > > > > still some configuration things that are missing, but I am not sure > > how to > > > > fix > > > > them (the docs are NOT clear). > > > > > > > > > > Which docs are you relying on? > > > > https://docs.mailman3.org/en/latest/config-web.html > > > > I presume these are the official docs for mailman3 -- maybe they aren't? > > > > > > > > How about this - > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > ?? > > > > I'm not using a virtual environment. I'm using all native Debian 12 > > packages, > > installed via apt. The virtual environment docs are actually even worse > > (even > > more confusing). > > > Worse? :-) Even more confusing. Both sets of docs make various assumptions and don't really explain things properly. Like everywhere where "settings.py" is mentioned, it really means "/etc/mailman3/mailman-web.py" In any case, the virtual environment docs are hard to relate to a "native" install and are generally hard to follow, since they seem to jump all over the place. (Spaghetti docs?) And it is hard to replace the various (and not always consistent) virtual environment paths and settings files to the "native" paths. The "official" docs are just not useful to me, since I am not using a virtual environment. If a virtual environment is recomended, what is the point of the Debian 12 packages? Are they just not meant to be used? Really? Do you mean that I should use a separate package management system for Mailman3? That really sucks. > > > > Maybe I'm too smart and experienced? > > > > You're clearly overestimating your smartness :-) Maybe. I am NOT an experienced Python programmer -- it is one of my *least* favorite programming languages. At this point I am considering scrapping Mailman and either giving up on have mailling lists on my new server or using some other mailing list software, > -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

1 year, 4 months

[MM3-users] Re: old usernames appearing in mailman.log

by Ken Alker

--On Sunday, June 25, 2023 3:26 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 2:27 PM, Ken Alker wrote: >> --On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> >> wrote: >> I see this in the logs from just after midnight: >> >> Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list >> found >> Jun 25 00:13:04 2023 (386086) ACCEPT: >> <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> >> Jun 25 00:13:04 2023 (386090) HyperKitty failure on >> https://lists.netlojix.com/hyperkitty/api/mailman/urls: >> >> Followed by a huge amount of HTML (strange). > > This is all from one post. > > The first is normal it just says that Mailman's > var/public_suffix_list.dat doesn't exist, but it should be retrieved from > https://publicsuffix.org/list/public_suffix_list.dat and then saved at > var/public_suffix_list.dat so it doesn't need to be retrieved from the > web again until the saved copy is older that the configured > dmarc.cache_lifetime (default = 7 days, so that message) after which time > the message will be 'Cached copy of public suffix list is out of date' > > The second is acceptance of the post. > > The third is a failure in archiving the message. Th HTML should contain > an error message with a traceback which should help determine the problem. > > >> Is there a way to kick it into re-running whatever it does at midnight >> so I can test this again after putting the public suffix list back? I >> assume I can just execute "mailman-web runjobs daily", but will this >> mess things up, or is it OK to run it mid-day without stopping anything >> first? > > > Midnight is a coincidence in this case. the above are all due to the post > with Message-ID: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > > The cached var/public_suffix_list.dat should now be there with a > timestamp of Jul 02 00:13:04 (7 days from Jun 25 00:13:04) Yes, thanks. >> Is the last (third) log line excerpt simply a result of the first, or do >> I have something else messed up? > > The third is not because of the first. It is because of some issue with > archiving that post. I have studied the output, looked at the code lines referenced in the Traceback, and I can't figure out the problem (I feel like the sad guy on the side of the street with his hood up staring into the engine bay with stream pouring out and not knowing what to do next). I did some analyses on the log file and determined that there are 71 messages it is having problems processing and there are 71 messages "stuck" in /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to process each message about 20 times). Since upgrading to V3.3.8 I've not seen new messages get stuck like this (although it's only been running smoothly for 24 hours now and there hasn't been much activity). But I'm suspecting there was something awry between the conversion from V2 to V3 in February and me installing V3.3.8 that caused this (based on message time stamps). It is HIGHLY likely these messages are in the archiving spool as a result of me unshunting the shunt queue and that they are copies of the messages that got delivered to the subscribers when I did that... but are now hung up in the archiving process. Following is an excerpt from mailman.log. Note that the "first section" (from DOCTYPE at top to 404 at bottom) is repeated four times (maybe not identical; but similar) (so I did not include it to save room) before the Traceback appears. Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list found Jun 25 00:13:04 2023 (386086) ACCEPT: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> Jun 25 00:13:04 2023 (386090) HyperKitty failure on https://lists.netlojix.com/hyperkitty/api/mailman/urls: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>lists.netlojix.com</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> <link rel="stylesheet" href="/static/postorius/libs/fonts/font-awesome/css/font-awesome.min.css" type="text/css" media="all" />    </head> <body> <nav class="navbar navbar-expand-md navbar-light bg-light navbar-default"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggler collapsed" data-toggle="collapse" data-target="#header-nav" aria-expanded="false"> <span class="sr-only">Toggle navigation</span> <span class="fa fa-bars"></span> </button> <a class="navbar-brand" href="/mailman3/lists/"><span><img src="/static/postorius/img/mailman_logo_small_trans.png" alt="Mailman logo"/> Postorius</span></a> </div> <div class="collapse navbar-collapse" id="header-nav"> <ul class="nav navbar-nav mr-auto"> <li class="nav-item"><a href="/mailman3/lists/" class="nav-link"> <span class="fa fa-envelope"></span> Lists </a></li> <li class="nav-item"><a href="/archives/" class="nav-link"> <span class="fa fa-comment"></span> Archives </a></li> </ul> <ul class="nav navbar-nav navbar-right"> <li class="nav-item"><a class="nav-link" href="/accounts/login/?next=/hyperkitty/api/mailman/urls"> <span class="fa fa-sign-in"></span> Login </a></li> <li class="nav-item"><a class="nav-link" href="/accounts/signup/?next=/hyperkitty/api/mailman/urls"> <span class="fa fa-user-plus"></span> Sign Up </a></li> </ul> </div> </div> </nav> <div class="container" role="main"> <h1>Page not found</h1> <div class="alert alert-danger">This page either doesn't exist, or it moved somewhere else.</div> </div> <footer class="footer"> <div class="container"> <p class="text-center"> <a href="https://postorius.readthedocs.org">Postorius Documentation</a> • <a href="http://list.org">GNU Mailman</a> • Postorius Version 1.3.8 </p> </div> </footer> <script src="/static/postorius/libs/jquery/jquery-3.6.0.min.js"></script> <script src="/static/postorius/libs/popperjs/popper-v1.11.0.min.js"></script> <script src="/static/postorius/libs/bootstrap/js/bootstrap.min.js"></script> <script src="/static/django-mailman3/js/main.js"></script> <script src="/static/postorius/js/script.js"></script> <script> // Add the .js-enabled class to the body so we can style the elements // depending on whether Javascript is enabled. $(document).ready(function(){ $("body").addClass("js-enabled"); }); </script> </body> </html> (404) ... above portion of log (or similar) repeats three more times ... Jun 25 00:13:05 2023 (386083) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError:

2 years, 4 months

[MM3-users] Hyperkitty issue(s)

by Bryan Loniewski

Hello -- I'm stuck trying to integrate Hyperkitty. I see the following errors in mailman.log and mailmansuite.log respectively: <snipped> [2020-05-27 16:42:11 -0400] [5140] [ERROR] Error handling request /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 406, in on_get for archiver in archiver_set.archivers File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 407, in <dictcomp> if archiver.system_archiver.is_enabled} File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/model/mailinglist.py", line 587, in system_archiver raise AssertionError('Archiver not found: {}'.format(self.name)) AssertionError: Archiver not found: hyperkitty and <snipped> Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/postorius/middleware.py", line 42, in __call__ return self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 36, in inner response = response_for_exception(request, exc) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 90, in response_for_exception response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info()) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/core/handlers/exception.py", line 125, in handle_uncaught_exception return debug.technical_500_response(request, *exc_info) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/views/debug.py", line 89, in technical_500_response reporter = ExceptionReporter(request, exc_type, exc_value, tb) File "/opt/mailman/mm/venv/lib/python3.6/site-packages/django/views/debug.py", line 254, in __init__ self.template_info = getattr(self.exc_value, 'template_debug', None) File "/opt/mailman/mm/venv/lib/python3.6/tempfile.py", line 479, in __getattr__ file = self.__dict__['file'] KeyError: 'file' Note that I've kinda followed the Virtualenv route along with using Mark's helpful webpage re: his experiences. Some relevant? config files... mailman.cfg: <snip> [archiver.prototype] enable: yes [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg <snip> mailman-hyperkitty.cfg: [general] base_url: https://a_real_domain/mm3/hyperkitty api_key: <movealong> I can provide additional conf file setups if warranted? I am curious (and perhaps this is in fact the issue) why when I run mailman conf I don't see the archiver.hyperkittty section even though its in the mailman.cfg file? While at the same time I do see archiver.{mail_archive,mhonarc}? I know it's reading my mailman.cfg based on other sections I've already setup/manipulated. Another data point: $ grep -i hyperkitty requirements.txt HyperKitty==1.3.2 mailman-hyperkitty==1.1.0 Any suggestions? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator

5 years, 5 months

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

by Stephan Krinetzki

Mark Sapiro wrote: > On 1/24/22 15:06, Mark Sapiro wrote: > > On 1/18/22 06:24, Stephan Krinetzki wrote: > > Hello, > > We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is > > installed in a venv and deployed using Apache and uwsgi. This works > > quite well so far, only withheld messages cause us a problem: If we > > try to approve them via Postorius, the message is delivered to the > > list immediately, but the success message in Postorius takes a long > > time - on average the process hangs for three minutes until the > > message is no longer displayed. We have already adjusted the timeout > > in gunicorn.cfg, but this does not improve the situation. Are there > > any tips on how we can speed up the REST API? Or is it even a > > configuration error? > > There are two steps in handling the POST for a held message. The first > > step is accepting, rejecting or discarding the message. This is > > happening immediately. > > The second step is handling the poster's moderation action based on the > > choice from the Set member moderation dropdown in the view of the held > > message. This is processed by the code at > > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…. > > If no selection has been made, the default value POSTed for > > moderation_choice is no-action and that code is skipped. If it is one > > of the choices Hold for moderation, Reject (with notification), > > Discard (no notification), Accept immediately (bypass other rules) > > or Default processing that is processed. So presumably a selection has > > been made and processing is stuck on getting the member or setting the > > member's moderation action. > > Possibly the logs of your database manager will have information. > > Some additional info. > By gunicorn.cfg, do you mean the file at mailman/config/gunicorn.cfg? If > you are using gunicorn as a wsgi server, that is separate from the > gunicorn serving the REST API and its config doesn't affect the REST > API. The relevant config is mailman/config/gunicorn.cfg?. > Also, I doubt the issue is with the REST API per se, but rather it is in > Mailman core's processing of the particular endpoint and if that is > slow, it is most likely some kind of database issue. Hi Mark, yes, we are using a local copy of the gunicorn.cfg. It is in the home directory of our mailman3 instance (like the mailman.cfg, same directory). We will now look into the postgresql database - maybe there is an index missing or something like that. Thank you for help.

3 years, 9 months

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

by Stephen J. Turnbull

Jonas Meurer writes: > But still, adding so-called "social" authenticators to the mailman3 > django application will expose users to the risk of clicking on > those ID provider buttons. I can see this point for Debian users. I suspect Ubuntu users are somewhat less paranoid. :-) Since that risk holds even for sites that enable explicitly (assuming we adopt the same policy) I will take a look at making that risk hard to realize (more distance from anything else clickable, smaller buttons with visible and accurate boundaries. > Personally, I consider it a major privacy issue if one central > instance (e.g. Facebook) is able to track on which platforms and > services you authenticate. Sure, but that ship has pretty well sailed AFAICT. Most users use unconfigured versions of IE (or Edge) and Safari, which means they're subject to all manner of webbugs. My employer just asked me to stop using Firefox because it's too pedantic for their website development vendors. :-( GDPR enforcement seems to primarily be an arm of the EU trade offensive against large American services (that's the Economist's recent opinion, not mine), while Europe-based globals are undoubtedly doing the same crap. > And to be honstes, I'm a bit irritated that those tracking features > from big corporates like Facebook and Google, whose main business > model is to aggregate as as much private data points as possible > about as much users as possible are enabled by default in Mailman3 > upstream. Your irritation is not our problem, though, since you can use Debian's version, and as I mentioned earlier, as far as I know most of our sites are happy to have social auth. I will be paying attention to the list to see what others think. > Besides the privacy concerns raised above, on problem with central > authentication services is that they also create new single points > of entry/failure. If your Facebook account gets hacked, you now > loose control over all other services/platforms, that you used the > Facebook authenticator service for. Same thing if you use a weak password. Effective and secure authentication is not something we're good at, and we can't really afford the effort to be good at it. These things are tradeoffs, and the default should be something that most of our users (ie, site and list admins, NOT subscribers) want. Hopefully their preferences in this respect reflect those of *their* users (== subscribers). > I agree with Torge that those social auth providers should be > disabled per default. IMHO, A sane default would be to list them in > the settings.py but have them commented out. "Those" social auth providers? Are there social auth providers who provide what you consider acceptable privacy guarantees (a la Duck-Duck-Go in search engines)? If so, we could make those higher in the list/easier to use.

6 years, 8 months

[MM3-users] Re: Domain Issue with MM3

by Mark Sapiro

On 10/23/19 12:53 PM, Liebeskind Uri (luri) wrote: > > I have setup this mailing list test(a)digital.lists.zhaw.ch but subscribing failed. How did you create the list and the digital.lists.zhaw.ch domain in Mailman? > * Subscribing via the Mass Import Form failed with a Server Error message in the browser. Log messages may help here. I can't tell you where to find them in your installation, but your Django settings or local settings will define LOGGING['handlers']['file']['filename'] which is where your Django logs are. and your various Mailman logs are generally in Mailman's var/logs/ directory. You may find a traceback from this error in the Django log or in Mailman's error.log or access.log. > * Subscribing via e-mail test-join(a)digital.lists.zhaw.ch<mailto:test-join@digital.lists.zhaw.ch> because no response came from MM3. This is Postfix. See below. > The mail to join has been delivered properly to MM3 but MM3 has swallowed the mail w/o response or error message. There also has not been any pending subscription. MM3 did respond. See below. > 2019-10-23T19:51:33.678705+02:00 svma-s-01321 postfix/smtpd[98348]: connect from srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.692258+02:00 svma-s-01321 postfix/smtpd[98348]: A8EFC3FA6A: client=srv-mail-013.zhaw.ch[160.85.104.123] > > 2019-10-23T19:51:33.693192+02:00 svma-s-01321 postfix/cleanup[98351]: A8EFC3FA6A: message-id=<eb90deb6-58af-a873-3382-c27ce6d05031(a)anydomain.org> > > 2019-10-23T19:51:33.704102+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: from=<name(a)anydomain.org>, size=5329, nrcpt=1 (queue active) > > 2019-10-23T19:51:33.704864+02:00 svma-s-01321 postfix/smtpd[98348]: disconnect from srv-mail-013.zhaw.ch[160.85.104.123] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > > 2019-10-23T19:51:33.763670+02:00 svma-s-01321 postfix/lmtp[98352]: A8EFC3FA6A: to=<test-join(a)digital.lists.zhaw.ch>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.08, delays=0.02/0.01/0/0.05, dsn=2.0.0, status=sent (250 Ok) Per the above the message was delivered to Mailman. > 2019-10-23T19:51:33.764485+02:00 svma-s-01321 postfix/qmgr[90603]: A8EFC3FA6A: removed > > 2019-10-23T19:52:29.278529+02:00 svma-s-01321 postfix/smtpd[98348]: table hash:/var/lib/mailman3/data/postfix_lmtp(0,lock|fold_fix|utf8_request) has changed -- restarting Why all these table changes/restarts? > 2019-10-23T19:52:29.286154+02:00 svma-s-01321 postfix/smtpd[98558]: connect from localhost[127.0.0.1] Mailman has connected to Postfix. > 2019-10-23T19:52:29.288612+02:00 svma-s-01321 postfix/cleanup[98351]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.292655+02:00 svma-s-01321 postfix/smtpd[98558]: 476AD3FA6A: client=localhost[127.0.0.1] > > 2019-10-23T19:52:29.293671+02:00 svma-s-01321 postfix/cleanup[98559]: 476AD3FA6A: message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> And delivered its response, message-id=<157185314763.94537.10517326910475727036(a)svma-s-01321.zhaw.ch> to Postfix. > 2019-10-23T19:52:29.296393+02:00 svma-s-01321 postfix/qmgr[90603]: table hash:/var/lib/mailman3/data/postfix_domains(0,lock|utf8_request) has changed -- restarting > > 2019-10-23T19:52:29.298231+02:00 svma-s-01321 postfix/smtpd[98558]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4 So the message was delivered to Postfix with the four commands ehlo, mail, rcpt and data. This is normal. What did Postfix do with the message? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

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

by Mark Sapiro

On 11/9/24 06:52, Odhiambo Washington via Mailman-users wrote: > > I looked at Django Admin and Postorius and I see all my MLs in both. What you see in Django admin is in the HYPERKITTY section and corresponds to hyperkitty_* tables in the mailmanweb database. > What I am sure about is that I did NOT create my MLs using Django admin UI. > I either created them using the CLI or Postorius. > Having said that, I did run two tests: > 1. Create a ML in Postorius and check whether it appears in Django admin - > The list was visible in Django Admin Because the list you created had the hyperkitty archiver enabled. > 2. Create a ML in Django admin and check whether it appears in Postorius - > The list was NOT visible in Postrorius Because it's only in HyperKitty. > 3. Create a ML in CLI and check if it appears in both Django admin and > Postorius - List is visible in Postorius, but not in Django admin Becayse this list did not have the hyperkitty archiver enabled. > ``` > MariaDB [mailmansuite]> select list_name, list_id from mailinglist where > list_name like 'ulf%'; > +-----------+-------------------------------+ > | list_name | list_id | > +-----------+-------------------------------+ > | ulftest2 | ulftest2.lists.kictanet.or.ke | > | ulftest3 | ulftest3.lists.kictanet.or.ke | > +-----------+-------------------------------+ > ``` These are only Mailman lists. > The list that I created using Django admin is NOT listed here! Because it's only in HyperKitty. > ``` > MariaDB [mailmansuite]> select list_id, name from hyperkitty_mailinglist > where list_id like 'ulf%'; > +-------------------------------+-------------------------------+ > | list_id | name | > +-------------------------------+-------------------------------+ > | ulftest1(a)lists.kictanet.or.ke | ulftest1(a)lists.kictanet.or.ke | > | ulftest2.lists.kictanet.or.ke | ulftest2(a)lists.kictanet.or.ke | > +-------------------------------+-------------------------------+ > ``` > The list I created using Django admin and the one I created using > Postorius are both listed, but the one I created from CLI is not listed. Because for some reason, the CLI created list does not create the HyperKitty archive until there is a post or until the `new_lists_from_mailman` job runs even though hyperkitty is enabled. > So there must be some logic behind this. However, I don't know what it is. The bottom line is you can have lists in HyperKitty that are not in Mailman and vice versa. The only thing you can't do is create a list in HyperKitty via the HyperKitty web UI, but you can use hyperkitty_import to import a mbox for a list which is not in Mailman and will be only in HyperKitty. Also, while you can create a list in Mailman that isn't in HyperKitty, if the list has hyperkitty enabled it will be created in HyperKitty when the `new_lists_from_mailman` job runs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 4 weeks

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

by Andreas Barth

* Stephen J. Turnbull (turnbull.stephen.fw(a)u.tsukuba.ac.jp) [210213 17:35]: > Andreas Barth writes: > > > I'd even say: these are different flags. > > They already effectively are, as Abhilash explained earlier (more > precisely, four values for one variable). Well, currently these are exclusive-states, I'd rather see them as or-able-states. > > So basically I'd consider it rather (as seperate boolean ones): > > I don't think separate booleans is a good idea, since they're > basically mutually exclusive states, and in most scenarios you want > the user to be able to reenable from any of the disabled states, so > having both "member disabled" and "admin disabled" would have no > special semantics. That's where I disagree :) > > - "disabled by member" (could be set by an admin as well of course) > > Currently this is determined by whether the logged in user is the > subscriber or not. It's an interesting idea to allow it to be set by > an admin. Then we could have the semantics that the only transition > allowed from this state would be to enabled, so that admins would know > the user had intentionally disabled and know not to enable without > permission. Exactly. Or while importing from another server, and there are people who have receiving mails disabled, this is the state that could be used for it. I expect that state to be the most-often used when setting a state manually. For "who set that", I would consider having some kind of history as useful (and displaying "last set by user / $person" to the admin but not the user). > > - "disabled for administrative reasons" (only by admin but user > > should be able to see it) > > I don't see why a user would need to see the difference. Unless > you're suggesting that the user would not be able to reenable without > asking the admin? What is the use case for this? I'm suggesting exactly that, yes. Why? Well, worked with user for too long. ;) E.g. consider that seeing archives works only for subscribers. And the subscriber in question complains about too many mails but still re-enables getting mails. This is basically "an admin has blocked you from more mails but not unsubscribed you". Might be an corner case, but still. Might also be too unimportant. > > - "bounced" (user and admin could reset it but not set it) > > Reenable but not set "bounced" is the current situation. Except if someone sets the state to "disabled" and then undo this, the state is automatically cleared. Which might be the right thing to do, but perhaps not. Anyways, that's just what I'd prefer. Doesn't mean that everyone needs to agree to it. :) Andi

4 years, 8 months

[MM3-users] Set member.moderation_action via REST API as part of message approval?

by Andy Matthews

We're using Mailman 3.3.9. My team and I have written a simple UI for displaying and approving/rejecting held messages from non list members. When an email receives an "always accept" flag from the UI we call the API to pass in the requested information: ``` Form form = new Form(); form.param("action", "accept"); Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); String safePath = UriBuilder.fromPath("lists/{listId}/held/{messageId}").build(listId, messageId).toString(); response = getTarget().path(safePath).request().post(data); ``` If that request is successful we update the `accept_these_nonmembers` property of the mailing list with the user's email. ``` Form form = new Form(); if (fieldValue.getClass().isArray()) { for (String val : (String[])fieldValue) { form.param(property, String.valueOf(val)); } } else { form.param(property, String.valueOf(fieldValue)); } Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); response = getTarget().path("lists/" + listId + "/config").request().method("PATCH", data); ``` The result of these two API calls is that both the subscribers and nonmembers properties of the mailing list are updated to include the new email (let's call it abc(a)123.com) The user can immediately send another email which is not held for moderation. The issue comes when a different nonmember sends an email and is approved (let's call it xyz(a)789.com) For some reason this blows out the "always accept" status of user abc(a)123.com and requires their email to be approved again. After some research I believe this is because the `accept_these_nonmembers` property has been deprecated (which seems valid because that property remains an empty array). Additional reading seems to indicate that we can now set `moderation_action` on each individual user which supercedes the mailing list's `default_nonmember_action` property (in our case it is `Action.hold`). The docs indicate that I should be able to submit a patch request to update the moderation action for any user: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… But it requires the user ID. And when trying to get the user_id for a nonmember it appears that it is not returned by the API. The following call: `/3.0/addresses/abc(a)123.com` returns ``` { "email": "abc(a)123.com", "original_email": "abc(a)123.com", "registered_on": "2025-03-03T19:18:35.169703", "self_link": "https://0.0.0.0:8001/3.0/addresses/abc@123.com", "http_etag": "\"92c44d0b3b323450f3576e6352acb59b4cc5d6f0a\"" } ``` So I'm not sure how I would be able to update this particular record without a member or user id. So, all that said, I'm looking for information on how to do one of the following. 1. When submitting a user's email to the `accept_these_nonmembers`, is there a way to indicate that the `member.moderation_action` should be a specific value? 2. Retrieve a nonmember record and have it include a member or user id that I can use to explicitly update the `member.moderation_action` value? There may of course be additional approaches that I'm not considering, but that's about the gist of it. Thoughts?

8 months

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

by Onyeibo Oku

Help! Regards Onyeibo On Thu Oct 13, 2022 at 6:03 AM WAT, Onyeibo Oku wrote: > On Wed, 12 Oct 2022 17:52:47 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks Eggert and Sapiro. > > > > > As Eggert suggests, see > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > > follow that. > > I already started out on the above route. Its an adaptation because I > am running Fedora. I had no problem with system-wide installations via > dnf package management. However, some parts of the documentation does > not add up. > > > You don't need to download the source from GitLab. > > Following that doc will get the latest releases from PyPI via pip. > > Those are still somewhat out of date - we really should make new > > releases - so if you want the latest from GitLab, there are a couple > > of ways to do it. Perhaps the easiest is to just run the various `pip > > install` commands as documented and then upgrade Mailman core in your > > venv with ``` > > pip install --upgrade git+https://gitlab.com/mailman/mailman@master > > ``` > > and update the various mailman web packages with > > ``` > > pip install --upgrade git+https://gitlab.com/mailman/xxx@master > > ``` > > where xxx is mailman-web, mailman-hyperkitty, django-mailman3, > > postorius, hyperkitty. I.e., run it 5 times, once for each value of > > xxx. > > > > I will come to this eventually (assuming that does not break things > later). I aim to get it all working with regular pip packages first. I > have installed mailman core already. > > Fedora expects mailman files to reside at /usr/lib/mailman. It appears > to ship with a mailman unix user. I adapted to those system defaults. > > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? > > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" > > I am lost > > "pip list" within the venv environment confirms that I have "mailman > 3.3.5". What am I missing? > > Regards > Onyeibo > > > _______________________________________________ > 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

[MM3-users] Re: Trouble Installing Mailman3

by Henry Hartley

This isn't doing a lot for my self-esteem. I'm now trying to install mailman-web and mailman-hyperkitty. Running the 'pip install' (as documented here https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-web-…) is giving me a similar setuptools error to the one I got before, although with a different version number: [SNIPPED successfully downloaded packages] Collecting django-haystack>=2.8.0 (from hyperkitty->mailman-web) Using cached django_haystack-3.3.0.tar.gz (467 kB) Installing build dependencies ... error error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> [2 lines of output] ERROR: Could not find a version that satisfies the requirement setuptools>=61.2 (from versions: none) ERROR: No matching distribution found for setuptools>=61.2 [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × pip subprocess to install build dependencies did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. Running 'pip install setuptools' replies that it's already installed (which is what I expected, because I installed it earlier) Requirement already satisfied: setuptools in ./venv/lib/python3.12/site-packages (80.9.0) I tried clearing pip's cache, but that made no difference. I am running as the mailman user in venv. It seems to be somehow related to the django-haystack package. In fact, running 'pip install django-haystack' results in the same error message. Perhaps I need to take it up with the maintainers of that. -- Henry Hartley Westat RB 2151 -----Original Message----- From: Henry Hartley via Mailman-users <mailman-users(a)mailman3.org> Sent: Friday, June 6, 2025 09:31 To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Trouble Installing Mailman3 CAUTION: External Email * [ This message appears to be from westat.com but the originating sender is external.] >> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> >> >> >> The next step in the instructions has me create >> >> /etc/mailman3/mailman.cfg. The first thing in that file is shown as: >> >> >> >> [paths.here] >> >> var_dir: /opt/mailman/mm/var >> >> >> >> Looking in /opt/mailman, there is no mm directory. Should that >> >> have been created, or is that something I need to create myself? >> > >> > You need to create it. I'll update the doc for that too. >> >> Actually, that's wrong. You don't need to create it. The first time you start Mailman core, it will be created. Excellent. Thanks. -- Henry _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://secure-web.cisco.com/1zFhvAPq5v7Gs3kANDBULVLuS95U56cpRwhnFwcvKwwPbI… Archived at: https://secure-web.cisco.com/1FyVIRlyXW9zpUP_wm98qkGB_DRuoOre5YHVvNpUo9unXQ… This message sent to henryhartley(a)westat.com * Please use caution when responding and/or clicking on links as this email originated from outside of Westat.

4 months, 4 weeks

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

When you set DEBUG=False, Django doesn't serve static files because of which you see only text and no styles. http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… If you do set DEBUG=False, you need to serve the static pages somehow. Alternatively in you case, you can remove the part of the `settings.py` which changes the Emailbackend when `DEBUG=False` so that you don't have to worry about serving static files and still send out emails. On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > For testing purpose I turned back to false the DEBUG var and everything > started working fine with HyperKitty > > I don't understand... this is the trace when I click Login from Postorius > to HyperKitty > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > HTTP/1.1" 200 10950 > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > HTTP/1.1" 200 156657 > > > What should I check? > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > > find them: > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > You need to ensure you have a working sass compiler. As I said at > > < > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > >, > > See the third bullet under > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > Then you need to run commands like > > > > django-admin collectstatic --clear > > django-admin compress > > > > > > -- > > 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

8 years, 3 months

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

by Joel Lord

Like Odhiambo, I see "v=spf1 -all" and nothing else. I see you're using Linode for public DNS, and going through all 5 of their servers directly they're all replying with the record Stephen saw. If I had to guess we're seeing a transient from Linode when you were updating the record at some point that has now gotten cached somewhere unfortunate (like Google...) and has a TTL you now wish were shorter. As for the record itself, I fully agree with Stephen with his recommendation. Get the extra stuff out and that '=' is currently breaking the IP clause, and the IP clause is what you need most. -Joel On 5/20/2023 10:36 AM, Stephen Turnbull wrote: > Christian writes: > > > 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record > > This says it's parsing your mail session and using the MAIL FROM. > > > 550-5.7.26 with a hard fail policy (-all) but it fails to pass SPF checks with > > 550-5.7.26 the ip: [192.46.218.224]. > > At least Google is seeing the mail arrive from the expected IP address. > >> To best protect our users from spam and > > 550-5.7.26 phishing, the message has been blocked. > > > Could the hard fail policy be implicated in the gmail rejection? > > It certainly could. However I would expect the DSN to say "because of the hard > fail specification we are rejecting your email" in that case. This looks like a Gmail > policy to me. > > > Other than readdressing my server, is there anything else I can do? > > I don't think readdressing is going to help unless you're referring to the PTR issue > mentioned below. > > I see the same SPF record you have described before: > lists.ccalternatives.org descriptive text "v=spf1 a mx ip4=192.46.218.224 -all" > so I'm not sure what is going on with Odhiambo's lookup. However, there is an > error (the '=' after ipv4 should be ':'), and it has some other problems: > 1. the 'mx' mechanism is a no-op because lists.ccalternatives.org has no MX record. > 2. the PTR for 192.46.218.224 points to mail.ccalternatives.org, not to lists.ccalternatives.org. > Neither should cause an SPF check to fail but they make the check more expensive. > > I would simplify your TXT record to > "v=spf1 ip4:192.46.218.224 -all" > because the 'a' mechanism isn't working and the 'mx' mechanism is a no-op. That's > really all you need. > > Steve > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jpl(a)ilk.org -- Joel Lord

2 years, 5 months

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

by Philip Colmer

We've set up several Mailman 3 servers on Ubuntu 20.04 successfully. We've always followed the virtualenv instructions: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… I realise those aren't the instructions you've been going through but I hope that at least confirmation that the virtualenv docs work is of some use to you. Philip On Sun, 2 Jan 2022 at 10:07, Michael Heseltine <heseltine.michael(a)gmail.com> wrote: > Hi all, > after many more attempts, I've still failed to find any set of > instructions that can install mailman3 on an Ubuntu 20.04 LTS server of > mine. I've recently switched to a new server without any previous > installation (apart from an apache web server) so that I can follow the > instructions provided in > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > to the letter, if possible. But still, I run into an error I do not > understand. > > I have followed the instructions until this point: > > > # pip install importlib_resources==1.1.0 > > Once the above packages are installed run “mailman info” in your virtual > environment. That will install Mailman core into your /opt/mailman/mm/var > directory. > > (I had to add "apt install libmemcached-dev" to the instruction for "pip > install psycopg2-binary" to succeed.) > > Then, I run "mailman info", but get an error message: > > > File > "/opt/mailman/mm/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", > line 508, in connect > > return self.dbapi.connect(*cargs, **cparams) > > File > "/opt/mailman/mm/venv/lib/python3.8/site-packages/psycopg2/__init__.py", > line 122, in connect > > conn = _connect(dsn, connection_factory=connection_factory, > **kwasync) > > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) connection > to server at "localhost" (::1), port 5432 failed: FATAL: password > authentication failed > for user "mailman" > > connection to server at "localhost" (::1), port 5432 failed: FATAL: > password authentication failed for user "mailman" > > This suggests that the connection to postgresql fails, but if I test this > using > > # psql --user mailman > > and type in the password listed in settings_local.py, I can login fine. > I've also changed the port number in that configuration from '' to '2222', > but the connection is still made to port 5432, which suggests to me that my > call to > > mailman info > > uses another set of connection parameters provided elsewhere. > > Where can this be found? How will I be able to run "mailman info" w/o > error and continue the installation as detailed in > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ? > > Any help is appreciated. > > Happy new year, Michael. > _______________________________________________ > 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, 10 months

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

by hansen

Thank you, Mark. Yes, the problem is with the mail clients which harvest addresses inappropriately (I never asked them to). I just found the header filter option, which I has been looking for under ’Settings'. Sorry for taking your time. It works great! Yours, Allan > On Jun 1, 2024, at 09:49, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/31/24 22:23, hansen via Mailman-users wrote: >> Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. > > > DMARC mitigation action ‘Replace From: with list address’ will also place the poster's address in Reply-To: (or Cc: depending on list configuration), so a simple `reply` from a reasonable MUA should go just to the poster. > > >> For example, say the mail client captures my address as >> “Allan Hansen via <listname>” <listaddress> >> then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: >> “Allan Hansen via <listname>” >> and, to make it worse, the actual email address, <listaddress>, is often hidden. > > > If this is the result of a `reply` and not `reply-all` the client is not behaving reasonably. > > >> The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. > > > That is a problem with the client, but I suppose such clients are not uncommon. > >> Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., >> "Allan Hansen via <listname>" > > You could add a header filter on the To header with a regexp like `^.*via <listname>` and the desired action. > >> Should I get onto the other list to request this as an enhancement? > > I don't think that's necessary in this case, as Header filters should do it. > > In general, the best way to request an enhancement is to file an issue with the appropriate GitLab project at `https://gitlab.com/mailman` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to hansen(a)rc.org

1 year, 5 months

[MM3-users] Re: Hyperkitty 403 Forbidden Error

by Mark Sapiro

On 1/20/22 11:40 PM, Josef Dietl wrote: > Dear all, > > > > Sorry for coming back to a topic that seems to be done for 18 months now. > > I'm staring at this issue for a few days now (on and off). But I still get > these messages: > > > > Jan 19 22:43:27 2022 (149439) HyperKitty failure on > https://lists.[...]/hyperkitty/api/mailman/urls: > <html><title>Forbidden</title><body> > > <h1>Access is forbidden</h1><p>Please check the IP addresses > > assigned to MAILMAN_ARCHIVER_FROM in the settings file. > > </p></body></html> (403) > > > > . and consequently, nothing ends up in the archive. > > > > I have checked (among others): > - MAILMAN_ARCHIVER_FROM - doesn't make a difference. 127.0.0.1, external IP > address, different orders, '*'. OK. > (Asterisk makes a difference, see at the bottom) ??? I didn't see what. > - MAILMAN_ARCHIVER_KEY in mailman-web.py matches api_key in > mailman-hyperkitty.cfg (except for the quotes). According to the editor's > color coding, the quotes are "right", too. I have removed special characters > to circumvent diverging treatment in different environments > > - I guess it doesn't matter, but wget --user restadmin --password [.] > http://localhost:8001/3.1/lists works, too. That is Mailman core's REST API which is not the issue here. > - ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" (probably also doesn't matter > > > > I'm running a fresh package installation from Debian Bullseye with > certificates from Certbot with nginx, so Certbot may have messed with my > nginx config, but even that seems to be OK: Yes, Certbot has inserted > http->https redirection, but I'd expect that a https base_url and > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" circumvents that. It should. Note that your primary resource for help with issue with Debian packages should be Debian. > Mailman info says ... > To provide all possible information, I'm also adding the nginx log that > seems to correspond to that request (no other requests at that time, give or > take five minutes): Yes, everything yields 403 response codes. > > > > [.] - - [19/Jan/2022:22:43:27 +0000] "GET > /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] > HTTP/1.1" 403 175 "-" "python-requests/2.25.1" The issue here is accessing the hyperkitty API. The base URL for these accesses is configured in mailman-hyperkitty.cfg. From what I see here, that is something like `http(s)://host.example.com/hyperkitty/` If you append `api/` to that base URL and go there in a web browser do you get a page of documentation of the HyperKitty API? If so, then figure out why it works from a web browser and not when Mailman core does it. If you get the 403, figure out why. This is probably an nginx issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Please help: Mailaman3 -

by Abhilash Raj

On Wed, Sep 2, 2020, at 10:28 AM, Jane Anara via Mailman-users wrote: > Hello Abhilash, > > Thank you for your reply. > > I did use the mailman-suit url.py before and got similar errors. At > your suggestion, I again included the following in the import session: > > from django.urls import reverse_lazy > from django.views.generic import RedirectView > > and the following line in the urlpatterns: > > url(r'^$', RedirectView.as_view(url=reverse_lazy ('list_index'), > permanent=True)), > > > The 'list_index' undefined error does not come up, however the HTTP > Error 404 I posted in my last message still shows up. I abstracted the > following from the error log as a potential cause: > > Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > File > "/opt/mailman/venv/lib/python3.6/site-packages/postorius/views/list.py", line 779, in list_index > paginator_class=MailmanPaginator) > File > "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 71, in paginate > objects = paginator.page(page_num) > File > "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 46, in page > number = self.validate_number(number) > File > "/opt/mailman/venv/lib/python3.6/site-packages/django/core/paginator.py", line 48, in validate_number > if number > self.num_pages: > File > "/opt/mailman/venv/lib/python3.6/site-packages/django/utils/functional.py", line 48, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File > "/opt/mailman/venv/lib/python3.6/site-packages/django/core/paginator.py", line 97, in num_pages > if self.count == 0 and not self.allow_empty_first_page: > File > "/opt/mailman/venv/lib/python3.6/site-packages/django/utils/functional.py", line 48, in __get__ > res = instance.__dict__[self.name] = self.func(instance) > File > "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 56, in count > return self.function(count=0, page=1).total_size > File > "/opt/mailman/venv/lib/python3.6/site-packages/postorius/views/list.py", line 775, in _get_list_page > advertised=advertised, mail_host=mail_host, count=count, page=page) > File > "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/client.py", line 181, in get_list_page > return Page(self._connection, url, MailingList, count, page) > File > "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ > self._create_page() > File > "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page > response, content = self._connection.call(self._build_url()) > File > "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 404: > > > I would appreciate any insight. This is trying to reach Mailman core and getting a 404 response from Mailman Core. Do you have Core running? Which version of Core are you running? > > Thank you. > > Regards, > Jane > _______________________________________________ > 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: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 6:35 PM, Mark Sapiro wrote: > On 1/14/22 6:11 PM, David Newman wrote: >> On 1/14/22 4:54 PM, Mark Sapiro wrote: >>> >>> It should work. I suspect you need to go to the list's Settings -> >>> Automatic Responses and set `Admin immed notify` to Yes. >> >> >> It's enabled. I think this triggers notifications only for new >> subscription requests, not pending ones. > > > Yes. That will send a single notification at the time of the request > using the `list:admin:action:subscribe.txt` template. Notices of pending > requests are sent by the `mailman notify` command using the > `list:admin:notice:pending.txt` template. > > ... >>> You can test `mailman notify` at any time by running it by hand. >> >> >> Thanks. This still isn't working as intended. I took these steps: >> >> 1. Created the file >> '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' > > > The template name is `list:admin:notice:pending.txt`, not > `list:admin:action:pending.txt`. Thats why it didn't work. Bingo. Thanks -- the template works as intended now. > > ... >> 2. Restarted the mailman3 and mailmanweb services > > > You only needed to restart Mailman core. OK > > > ... >> What I'm trying to do here is replicate a feature from MM2.1, where >> pending notifications had URLs embedded in the message. That's not >> available out of the box in MM3, and if there's a place for feature >> requests I'd be glad to ask that this be made the default. > > > The place for feature requests for Mailman core (which this is) is > https://gitlab.com/mailman/mailman/-/issues, however, this is not > straightforward as Mailman core doesn't know if you even have Postorius > or some other web management UI installed or what the URL to access it > might be. Thus it's not just a simple matter of editing templates. It > would also require a configuration setting for the base URL for the web > admin UI and changes in logic to provide an appropriate replacement > depending on whether or not the base URL was configured. Understood, thanks. Although this distinction is very important for server admins, it's likely not meaningful for many list owners and moderators. For them, MM2.1 sent an email saying "go here" and MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. There is some pending template in use by default, just not one with a URL included. Is this something better handled in the venv and/or Web installation docs? Or should I file a feature request for core, or Postorious or someplace else? Thanks very much! dn > >

3 years, 9 months

[MM3-users] Re: Flushing/syncing hyperkitty with mailman

by Eric Abrahamsen

On 06/16/18 19:46 PM, Mark Sapiro wrote: > On 06/16/2018 06:38 PM, Eric Abrahamsen wrote: >> >> >> A bump for this, I've been getting this series of errors once a minute >> for weeks now. There must be some way to clear out dangling thread >> references? And I take it that for the meantime we shouldn't be using >> the "delete thread" feature of hyperkitty... >> >>> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >>> [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] >>> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >>> [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] >>> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >>> [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] >>> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >>> [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] >>> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >>> >>> Is there something more I should be doing to sync hyperkitty's database >>> with mailman? I've got the crontab file in place, and that appears to be >>> running without error. Anything else? > > > Except that 'django-admin runjobs minutely' is probably what's producing > the errors. Yes, I guess that was poorly phrased... > You might try 'django-admin runjob empty_threads' (normally a monthly > job) or 'django-admin runjob thread_order_depth' (normally a yearly > job). I don't know if they will clear this up or not, but I don't think > it would hurt to try. > > See 'django-admin runjob --list' to see the various jobs and note that > 'django-admin runjob update_index' which runs minutely and does an > incremental update is not the same as 'django-admin update_index' which > only runs manually and does a full search index update. I've tried all the above with no luck, and am getting ready to dive a bit deeper. It's been a bit confusing tracking all the code flows. The rebuild_thread_cache_votes error occurs once a minute, at second 21. The rebuild_email_cache_votes error is also once a minute, but at second 56. Am I right that the only job that runs once a minute is the "runjob update_index" command, and that the error must be (eventually) arising from there? Does it seem meaningful that the two errors are offset by around 30 seconds? Lastly, searching the source for the rebuild_(email|thread)_cache_votes functions, they only seem to be called within the "on_vote_added" method of Email and Thread objects, but I don't see how that can be the source of the errors (as the objects in question obviously exist). So it must be update_index, which means I should be looking in haystack (ha) for whatever eventually calls these functions. Does that all sound correct? Thanks for your pointers, Eric

7 years, 4 months

[MM3-users] Re: Disable archives per list

by Stephen J. Turnbull

Bernd Wurst writes: > Am 25.02.21 um 22:01 schrieb Mark Sapiro: > > Normally a list admin can select which of the enabled archivers is > > active for that list via Postorius. To prevent this, you would have to > > modify Postorius. It would be easy enough to just remove settings from > > the relevant templates. > > This will take effect for all lists at once, I suppose. :( I'm not familiar with the content of Postorius's templates, but they support all of the Django features, so you can filter out the settings for specific lists. It would require code and database schema changes to make that configurable from Postorius, I think. > Hyperkitty has a rather cool frontend but stores all messages from all > lists together in one database table. Additionally, neither Mailman nor > Hyperkitty seems to know or tell anything about archive sizes of a list. > This is horribly for accounting. Mailman core doesn't know anything about archives except where you've told it to send them. Historical note: I'm not saying it was a good idea, but the folks who designed HyperKitty were aiming at the Fedora use-case. There's a fair amount of cross-posting between Fedora lists, so I think this makes sense for them both from the indexing and from the storage point of view. I doubt they were thinking about the hosting perspective. > So I thought if I can have a separate hyperkitty installation per user > without having to duplicate the whole mailman. You could do that, but it requires a separate port or domain for each. If you're already aliasing a server (or a server farm) for virtual domains, then that's no problem. > Alternatively, I'd like to enable archiving only for some customers > that buy a suitable plan. > I did not really get into mailman plugins. I don't think anybody has gotten into them. > Is is possible for plugins to hook into such settings? Since archiving involves getting the message from Mailman core, yes. Plugins can only deal with that end though. Everything else is controlled by the archiver itself. Without a plugin, you could disable archiving somewhat easily by giving each list a different posting pipeline that doesn't have the 'to-archive' handler in it. This wouldn't stop the list admin from configuring, but ... there wouldn't be any archives there. I don't know if that deserves a smiley. :-/ Unfortunately this would be annoying because you'd have to go in and modify for each list. With a plugin, Mailman core could refuse to configure a archive. However, stock Postorius wouldn't know anything about that. It would just see a "refused" response in the REST protocol, but without modifying Postorius, I suspect it would just log and display an error to the user. And without code changes Postorius can't provide a good UI for that. Steve

4 years, 8 months

[MM3-users] Re: Reply w/Email Clients - From: vs. Reply-To:

by Jay Hamilton-Roth

On Nov 17, 2020, at 5:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/20 2:34 PM, j(a)manygoodideas.com wrote: >> I'm setting up a new list, and a number of new list members are reporting a problem with replying to the thread. Their email clients seem to ignore the Reply-To: field and instead use from From: field. > > > Are you saying that a 'reply' , not 'reply-all' will reply to the From: > only and ignore Reply-To:? If so, the email clients that are doing that > are badly behaved. I can't say they are non-compliant as RFC 5322 > <https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.2> only says: > > The originator fields also provide the information required when > replying to a message. When the "Reply-To:" field is present, it > indicates the address(es) to which the author of the message suggests > that replies be sent. > > > I.e., Reply-To: is only a 'suggestion', but well behaved clients will > follow it. That's exactly what I'm saying. And there's more than a few of these badly behaved clients. >> When they use Reply All, the email is addressed to both the From: and Reply-To:. > > Reply All should reply to the Reply-To:, To: and Cc: addresses and to > From: if there is no Reply-To:. Whether Reply All should include From: > if there is a Reply-To is not well defined. > > >> Reading through previous threads here, I've tried a number of things: >> >> 1) DMARC mitigation action is "Replace From: with list address" >> 2) For Alter Messages - Set "Reply goes to list" >> >> The goal is that we want a reply to go to the list, not the person posting. Since Reply-To seems to be ignored by some clients, I'm hoping there's a way to force the "From" field to become the list address. Thanks in advance for your suggestions! > > If Alter Messages -> Reply goes to list is set to Reply goes to list, > Reply-To: will include the list posting address. What are the clients > that ignore this? Complaints should go to the providers of those. Complaints sent. > > Tf DMARC mitigation action is "Replace From: with list address", that > will happen to messages to which DMARC mitigation action applies. If you > want it to apply to all messages, set DMARC Mitigate unconditionally to > Yes. That fixed it. Thanks again, Mark! > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 11 months

[MM3-users] Re: Mailman3 on FreeBSD

by John Poltorak

Regarding location of mailman.cfg...FreeBSD adopt a strict directory hierachy https://www.freebsd.org/cgi/man.cgi?hier(7) Anything installed outside the base OS belongs in /usr/local I guess that issue is something for the FreeBSD porters of Mailman3... I'll use /etc/mailman.cfg for the time being but I don't know what should go in it. Can I see an example? The other problem regarding sqlite was solved by pkg install databases/py36-sqlite3 I'll get back to the install docs now. Thanks showing interest. On Sun, Aug 13, 2017 at 2:25 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Sat, 12 Aug 2017 18:10:49 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 08/12/2017 04:51 PM, Barry Warsaw wrote: > > > On Aug 10, 2017, at 16:32, John Poltorak <karotlopj(a)gmail.com> > > > wrote: > > >> > > >> On FreeBSD they ought to be in /usr/local/etc/mailman.cfg however > > >> I don't see any indication as to what I should put in this file > > >> and if it was in /usr/local/etc/mailman.cfg then how would mailman > > >> find it? > > > > > > It wouldn’t by default. Right now Mailman does not search > > > for /usr/local/etc/mailman.cfg, but that wouldn’t be a difficult > > > change to add. I’m not sure whether that would makes sense as a > > > general default or not. I’m not up on the FreeBSD conventions and > > > standards here; can you explain why /usr/local/etc is preferred > > > over /etc on that distro? > > > > > > I was hoping Abhilash would chime in here, because I think John is > > using the docker image and there's probably a specific path for > > mailman.cfg. > > As per his first message, I think John is using the prod setup from the > documentaion[1]. > > I don't have anything much to add on top of what Barry mentioned, it > looks like something is wrong with the Python install and missing > Sqlite3 module. > > The documentation does mention the paths where Core looks for > configuration file and anything else can be specified using -C or > MAILMAN_CONFIG_FILE environment variable. > > [1]: http://docs.mailman3.org/en/latest/prodsetup.html > > > As far as what goes in it, it could even be empty if you want to > > accept all the defaults, but you probably want at least > > > > [mailman] > > site_owner: real_person(a)example.com > > > > I expect if you do > > > > find -name mailman.cfg > > > > in your installation, you'll find at least examples. > > > > thanks, > Abhilash > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

8 years, 2 months

[MM3-users] Users, members, accounts and subscribers

by Stephen J. Turnbull

Cameron Smith writes: > In an attempt to introduce a friend to MailMan3, I had her > subscribe to a couple of lists that I set up and we exchanged a few > messages via the email interface. > > Then I introduced her to the web interface and we were both > confused when she could not log-in/sign-in and was told that her > email address was not recognized. In theory we could recognize addresses, and tell the user that the address is not associated with an account. This might not be a bad idea, but in theory it could be used by spammers to confirm that accounts are good ones. What we can do right away is to add a generic statement to the sign in screen that "addresses that are not linked to accounts and presented along with a valid password will be not be recognized". > It was only later that I realized that while she was a subscriber, > she hadn’t yet signed up for an account. Yes, that will happen in some cases, depending on how the subscription was created. The solution is simple: create an account via the web interface, and link the address (and therefore subscriptions using that address) to the account. > What is the point of “accounts"? A "user" or "account" manages the entire relationship that a person has with a Mailman installation, including subscriptions, personal profile, administrative roles, and credentials (currently just passwords). An account may have several addresses associated with it and several subscriptions. Sometimes several addresses may be subscribed to the same list, because subscription is often required by the posting priviliege. In Mailman 2, where a person is identified by an address, a person with several addresses would have to manage the credentials and preferences for each address separately. Mailman 3's concept of "user" allows a person have one account with a single password, set typical preferences, and still have exceptional configurations for particular subscriptions. It's more complex, but experience shows users are happy to accept this much extra complexity for the power and convenience. A "subscription" links a particular address and the associated user, if there is one, to a mailing list. An address is its own credential: if you can reply to a mail sent to an address, it is assumed you own that address and are allowed to subscribe it to lists, post from it, etc. (Not just by Mailman: this is an extremely common setup on the Internet.) However, this model becomes inconvenient rather quickly if you need to manage relationships among several addresses. > Why can someone become a subscriber, but not have an account? There are subscriptions, such as other lists or archiving services, that don't serve a single human person. It also is a reasonable approach to situations where it's a bad idea, or even impossible, to access personal data and credentials, such as a subscription by an admin on behalf of a person.

8 years, 2 months

[MM3-users] Re: how should I implement multiple domains for receiving emails to a list

by Mark Sapiro

On 4/15/25 16:51, Philip Bondi wrote: > > I have two domains: systemdatabase.ca, systemdatabase.homelinux.com > > All my lists should be on both domains. So h(a)systemdatabase.ca is the same list as h(a)systemdatabase.homelinux.com. I found this was the mailman2 behaviour on my old CentOS 7 installation and I am accustomed to it. While Mailman 2.1 had some support for multiple domains, list names had to be globally unique because a given list name referred to that one list regardless of domain. Mailman 3 is different in that the domain is part of the list name so h(a)systemdatabase.ca and h(a)systemdatabase.homelinux.com are different lists. > I edited /opt/mailman/venv_mm/var/data/postfix_lmtp directly. Duplicated and edited all the lines. And compiled with postmap /opt/mailman/venv_mm/var/data/postfix_lmtp > > I sent a test email. This appears to work. > > Is this the best method to achieve this goal? What would you recommend? If all you want is for mail to h(a)systemdatabase.ca or h(a)systemdatabase.homelinux.com to wind up at the same list, what you've done is OK, but whatever fqdn name your list is created as, it needs the other fqdn name added to it's Acceptable aliases setting, at least if Require Explicit Destination is Yes. The other issue is every time you start Mailman core it will implicitly run `mailman aliases` and overwrite your changes. I have a similar situation on one of the servers I support. The lists are all in a domain I'll call example.com, but we also want to allow mail to <list>@otherexample.com to reach the <list>@example.com list. We use this patch to add all those names. ``` --- a/src/mailman/mta/postfix.py +++ b/src/mailman/mta/postfix.py @@ -261,5 +261,10 @@ class LMTP: '{}@{}'.format(alias, mlist.true_mail_host)) line = VMAPTMPL.format(true_addr, width, addr) print(line, file=fp) + if mlist.true_mail_host == 'example.com': + true_addr = self._decorate( + '{}@{}'.format(alias, 'otherexample.com')) + line = VMAPTMPL.format(true_addr, width, addr) + print(line, file=fp) print(file=fp) return True ``` However, this only works because example.com has an alias domain. If that weren't the case, we would need something like this instead. ``` --- a/src/mailman/mta/aliases.py +++ b/src/mailman/mta/aliases.py @@ -43,9 +43,14 @@ class MailTransportAgentAliases: """See `IMailTransportAgentAliases`.""" # Always return yield mlist.posting_address + if mlist.mail_host == 'example.com': + yield '{}(a)otherexample.com'.format(mlist.list_name) for destination in sorted(SUBDESTINATIONS): yield '{}-{}@{}'.format( mlist.list_name, destination, mlist.mail_host) + if mlist.mail_host == 'example.com': + yield '{}-{}@{}'.format( + mlist.list_name, destination, 'otherexample.com') def destinations(self, mlist): """See `IMailTransportAgentAliases`.""" ``` Do not use both those patches. If your list domain has an alias domain, use only the first one and if not, only the second. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

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

by Abhilash Raj

On Fri, Jul 30, 2021, at 1:04 PM, bob B wrote: > is this the info you need for the container version > > [root@..... docker-mailman]# docker ps > CONTAINER ID IMAGE COMMAND > CREATED STATUS PORTS > NAMES > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 > hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, > 127.0.0.1:8080->8080/tcp mailman-web > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 > hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, > 127.0.0.1:8024->8024/tcp mailman-core > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 > hours ago Up 2 hours 5432/tcp > dockermailman_database_1 > > > for smtp host > ------------ > cat /opt/mailman/web/settings_local.py > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org'] > ALLOWED_HOSTS = ['*'] > DEBUG = True > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'smtp.example.com' > EMAIL_PORT = 25 > --------------------------- > cat /opt/mailman/core/mailman-extra.cfg > # mailman-extra.cfg > > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > # mailman-core hostname or IP from the Postfix server > lmtp_host: localhost > lmtp_port: 8024 > # Postfix server's hostname or IP from mailman-core > smtp_host: smtp.example.com > smtp_port: 25 > configuration: /etc/postfix-mailman.cfg > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: my_real_email_is_in_the_file.com > __________________________________ > > My docker most machine /etc/postfix/main.cf has > > transport_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > local_recipient_maps = > regexp:/opt/mailman/core/var/data/postfix_lmtp > relay_domains = > regexp:/opt/mailman/core/var/data/postfix_domains > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > ------------------------------ > > > > is that correct? I leave them set to smtp.example.com because the will > send out via the docker host machine, and so i ONLY have my actual > outbound server listed in /etc/postfix/main.cf on the docker host > machine, or do i need to replace smtp.example.com with our outbound > server? You should replace smtp.example.com in both mailman-extra.cfg and settings_local.py with whatever the IP address of the MTA (which I assume is running on the host, so it'd be the "gateway" address from the container's network) so Mailman components can talk to Postfix to deliver email. There is some gaps in the documentation because of the latest changes that have been made in the repo and the documentation and docker-compose files aren't versioned properly :( I've opened a bug report to update the compose and versions https://github.com/maxking/docker-mailman/issues/481 -- thanks, Abhilash Raj (maxking)

4 years, 3 months

[MM3-users] Re: [External] Re: Re: Problem getting Mailman3 to work with Ubuntu 24.04.1 LTS

by Sebenste, Gilbert

Hi Greg, We are using the venv method. Did you get it working on that? Did you require a special configuration for mailmanweb? Gilbert Gilbert Sebenste Meteorology Support Analyst [cid:image001.png@01DB05EB.83853440] From: Greg Newby <gbnewby(a)petascale.org> Sent: Friday, September 13, 2024 2:17 PM To: Sebenste, Gilbert <sebensteg(a)cod.edu> Cc: mailman-users(a)mailman3.org Subject: [External] Re: [MM3-users] Re: Problem getting Mailman3 to work with Ubuntu 24.04.1 LTS CAUTION: This email originated from outside of COD’s system. Do not click links, open attachments, or respond with sensitive information unless you recognize the sender and know the content is safe. Hi Gilbert. I don't know the solution. However, FWIW, I found the Ubuntu 24.04 LTS packages to be unusable and not fit for purpose. I tried to get them running on a fresh installation of 24.04 and ran into huge problems. The packages include outdated versions of the Mailman software and dependencies, and components of Mailman are stored in places that are non-standard and undocumented. Among other things, there were problems with file ownership since the Ubuntu/Debian approach is different from the Mailman3 official documentation. After getting some guidance from this list (which you can see in the archives), I abandoned the effort and installed it in a virtual environment per the instructions. That worked fine. It's a non-trivial installation, even so - many configuration files need to be created or edited. I will be curious to learn whether you get Mailman3 working correctly from the Ubuntu packages. Like you, I needed to port existing lists (from Mailman 2.1) and I eventually gave up. With the packages, it was a situation where I would think I had solved "the" problem, and then other problems kept appearing. ~ Greg On Fri, Sep 13, 2024 at 11:59 AM <sebensteg(a)cod.edu<mailto:sebensteg@cod.edu>> wrote: This got mailman3 working, but mailmanweb is still borked. Does anyone know what might cause this: > systemctl status mailmanweb mailmanweb.service - GNU Mailman Web UI Loaded: loaded (/etc/systemd/system/mailmanweb.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Fri 2024-09-13 18:55:37 UTC; 12s ago Duration: 1ms Process: 562668 ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini (code=exited, status=203/EXEC) Main PID: 562668 (code=exited, status=203/EXEC) CPU: 700us Sep 13 18:55:37 server1 systemd[1]: Started mailmanweb.service - GNU Mailman Web UI. Sep 13 18:55:37 server1 systemd[1]: mailmanweb.service: Main process exited, code=exited, status=203/EXEC Sep 13 18:55:37 server1 systemd[1]: mailmanweb.service: Failed with result 'exit-code'. _______________________________________________ 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to gbnewby(a)petascale.org<mailto:gbnewby@petascale.org> ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

1 year, 1 month

[MM3-users] Re: Send MySQL data to mailman list for distribution

by Ruth Ivimey-Cook

Hi, Your request is not particularly clear -- telling us what the end goal is would help -- but I think the answer is neither the mailman menu nor the phpmyadmin can do what you want. That is assuming that you want to send some tabular information to people via email, where the recipients are managed via mailman. Consider the parts of your process: 1) some data source, which you have not mentioned. 2) something that stores data from the source into MySQL tables. 3) something that creates html page text from the MySQL tables, that can be delivered by an http server. 4) something that creates an email message from the data in the MySQL tables. 5) something that sends the email message to an MTA (such as exim, postfix, etc). 6) something that stores and manages the email recipients to whom the data is sent (= Mailman + postorius etc). I think you must have something that manages (1), (2), and (3), as you mention that you have a web page that works. This solution likely uses php and nginx. [ Note that a web page never sends an email. It is possible for (eg) PHP programs to send an email, and it can be the case that a php program that is generating html for a web page can also generate an email message and send it, but that is to conflate two quite different processes unnecessarily. ] You still need (4) and (5), which mailman cannot help with but for which libraries like PHPMailer, and programs like exim, can help. The message to your recipients will be sent in (5) to mailman using an email address to mailman core which is set up as a posting non-member of the list, so it doesn't also get copies of mails sent. Hope this helps, Ruth On 01/06/2021 21:46, Zden Pos via Mailman-users wrote: > I'm trying to connect existing MySQL data to the Mailman distribution list. > Actually, a message is sent from the web page. It remains on this page and is also stored in the MySQL table on the provider server. This is working fine. > I have also existing Mailman distribution list generated from the cPanel on the provider server as well. This list is working fine when used for a direct mailing. > > I need to link the MySQL table to the Mailman distribution list. When the message is posted on the web page and stored in the MySQL table, it is also to be sent to members as per the Mailman distribution list. I don't know where to configure it. In the phpMyAdmn page of the MySQL or in the Malman menu ? > > Thank you for your help > _______________________________________________ > 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/ -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 5 months

[MM3-users] Re: Trouble Installing Mailman3

by Stephen J. Turnbull

Henry Hartley via Mailman-users writes: > This isn't doing a lot for my self-esteem. I don't think you need to worry about you. :-) There are dozens of moving parts involved, each of which sets its own requirements and is continuously being updated. And you're working in a virtual environment, which is a fragile hack. Works well if you treat it right, but does need care. > I'm now trying to install mailman-web and > mailman-hyperkitty. Running the 'pip install' (as documented here > https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-web-…) > is giving me a similar setuptools error to the one I got before, > although with a different version number: [...] > ERROR: Could not find a version that satisfies the requirement setuptools>=61.2 (from versions: none) [...] > Requirement already satisfied: setuptools in ./venv/lib/python3.12/site-packages (80.9.0) There are two ways those two messages can be consistent: that pip's version number parsing is buggy, or those aren't the same pip. The former explanation, while possible, is highly unlikely. One common explanation for this kind of conflict is that you did part of the installation with the venv active, and part without. I know you wrote that you are "running as the mailman user in venv", but just to double check, does "in" mean "current working directory is venv" or does it mean "venv is activated with '. bin/activate'" as well? You need to activate the venv to get all of the paths (especially to the "pip" and "python" commands) right. I took a look at a fairly recent install of django-haystack, and in the .dist-info it says the installer is 'pip' rather than 'pip3'. IMO this is bad practice, even today. One possible explanation is that somehow at an intermediate stage the install script is picking up a Python 2 pip, and IIRC Python 2 setuptools goes only to 58.x or 59.x. Or if you're in a Debian environment, I seem to recall the Debian Python 3 environment does not provide setuptools at all (and deliberately makes it hard to install outside of a venv). Check if your venv bin directory has a pip executable (or symlink to the executable). If not, adding a symlink pip -> pip3 may help. > It seems to be somehow related to the django-haystack package. In > fact, running 'pip install django-haystack' results in the same > error message. Perhaps I need to take it up with the maintainers of > that. No, the problem is pip is unable to understand that setuptools 80.9.0 >= setuptools 61.2 (probably because it's looking for setuptools somewhere other than your venv, and isn't seeing 80.9.0 at all). I very much doubt that the Haystack developers can help with this more than other experienced Python developers. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 4 weeks

[MM3-users] Re: I'm seeing a lot of database locked errors

by Mark Sapiro

On 9/18/23 8:36 AM, bryan.kartzman(a)yu.edu wrote: > > I'd like to say it worked flawlessly (and it did allow the archives to be displayed, which wasn't happening before, but I'm getting the following two errors (or maybe KeyError 1365 and 1366 are the same error?) every minute: > > 11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1365 : Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker > res = f(*task["args"], **task["kwargs"]) > File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.nodes[msgid]["obj"] > File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ > return self._nodes[n] > KeyError: 1365 > > 11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1366 : Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker > res = f(*task["args"], **task["kwargs"]) > File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions > compute_thread_order_and_depth(thread) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth > walk_successors(thread.starting_email.id) > File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors > obj = graph.nodes[msgid]["obj"] > File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ > return self._nodes[n] > KeyError: 1366 > > Is this an error only in the archives or might I also have a problem with other timestamp fields in the database? If its just the archives, is there a simple way to fix it? If no simple way to fix the archives, is there an easy way to erase all list archives? If no easy way to erase all list archives, would deleting all the lists and recreating them remove the archives? The above errors have nothing to do with timestamps. There are entries in the hyperkitty_thread table with starting_email_id = 1365 and 1366, i.e., `SELECT * FROM hyperkitty_thread WHERE starting_email_id in (1365, 1366);`, but there are no entries in the hyperkitty_email table with id = 1365 or 1366. You could look at the thread_id for those entries in the hyperkitty_thread table and see if there are entries in the hyperkitty_email table with message_id_hash = those thread_id values. if those entries exist, you can fix this by altering the starting_email_id of those entries to the respective id values for those messages from the hyperkitty_email table. If those messages don't exist in the hyperkitty_email table, you could just delete the offending entries from the hyperkitty_thread table. As far as deleting archives is concerned, a Django superuser should have a `Delete Archive` button on the top level Hyperkitty view for the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] List Digest - Subject line

by smorytko＠gmail.com

Is there a way to optionally cause the Subject line to display with the text body and as a summary at the top of the digest? I ask because on our mailing list (and probably many others too) subscribers include important content in the subject line and do NOT repeat it in the body of the text. So when the digest formatting places the Subject lines at the top to create "Today's Topics" as it does for all digest subscribers, the subject line and text body are widely separated making comprehension of the message much more difficult and separating important content unless it's repeated. This also happens on our list which uses Affinity/Empathy rather than Hyperkitty. In general, while a Today's Topics summary is useful, I think it would be preferable to always include the subject line with the body (one add'l line per digest message). Again I'm wondering if this is a web front-end function, a MM3 core function, or perhaps both? I ask because if it's not a MM3 core function I'll need to ask our developer for an Empathy modification. Below is an example from an Empathy-base list that shows how difficult it is to fully comprehend messages when the subject line is separated from the text body. The same issue would seem to be present in a Hyperkitty based list: Today's Topics: 1. Wilson’s Warbler (Albert Laguna) 2. RB Nuthatch, Kent (John Johnson) 3. Happy Mothers Day Summer Tanager (Visit Today Only) (Aidan Kiley) 4. Wimisink Sora, Marsh Wren (Angela Dimmitt) 5. Stn 43 South Windsor (Paul Desjardins) 6. White-crowned Sparrows at Hammonasset (Paul Smith) 7. Re: White-crowned Sparrows at Hammonasset (Paul Smith) 730am Beaver Pond Park in New Haven. Wilson’s Warbler sporting its distinctive black cap. Very birdy with yellow warbler, blue headed vireo, ruby crowned kinglet warbling vireo joining the fun, among others. Sent from my iPhone Red-breasted Nuthatch at our feeder this morning. First time ever in our yard in 35 years! John Johnson Kent FOR TODAY ONLY: Our special friend is still here today! I would like to open it up allow more people to see him because I really hate how “clique like” the birding community is here. Anyone interested can come stop by but would need to email me letting me know they’re interested in coming first. I will check my email and then I will send my address with instructions and where they are allowed to go. Thanks! Jill (jmahar(a)udel.edu) Jill Mahar Easton 5/9 - Sora back, calling; marsh wren, near end of boardwalk - Sherman/Wimisink marsh, Rte.39 at 55. Angela Dimmitt New Milford Paul Desjardins paul.desjardins2(a)gmail.com Phone: (860) 623-3696 This morning at the end of the Vibert Road section White Crowned Sparrow and north of Vibert Road f o y 2 Indigo Buntings. Paul Desjardins Windsor Locks 2 White-crowned Sparrows at Middle Beach. At the circular road by the picnic tables. Sent from my iPhone Oops, sent too soon Paul Smith New Haven Sent from my iPhone

4 years, 5 months

[MM3-users] Re: Gmail problems?

by Stephen Daniel

Thanks. My email kinda does originate from their servers, in that my SMTP relay is smtp-relay.gmail.com. For now, explicit whitelisting appears to help, I just have to do a lot of hand holding with each user to get it set up. And, most of the users seem to think this is my problem / my fault / my responsibility to fix. Sigh. On Sat, Apr 22, 2023 at 1:19 PM Dave McGuire <mcguire(a)neurotica.com> wrote: > On 4/22/23 11:02, Stephen Daniel wrote: > > I run a number of small lists for my neighborhood association. The > largest > > of these is ~120 users. Typical volumes are about 2 messages/day. > > > > In the past week or so a number of users who use gmail as their email > > client have complained that list emails have been going to spam or > > "promotions" folders. I've always had 1 or 2 users who had trouble > > receiving mails, but this seems to be a significant percentage of all > gmail > > users. > > > > I have DMARC mitigation set to unconditional, and the DMARC action set to > > "Replace From: with list address". > > > > My emails are sent using google workspace as my SMTP relay. > > > > I'm trying to teach my users to whitelist the list domain, but they are > > not, in general, a tech-savvy bunch, so it is slow going. > > > > Anyone else suddenly having trouble with gmail? > > Any suggestions? > > This started a couple of years ago, and it has become much worse over > time. It's not just lists, it's any email that originates from a server > that isn't Google's. Even servers with sterling reputations, and ones > which have gone through the BS of "registering" with Google. It does > nothing. > > It's a not-so-subtle hint that Google wants to handle YOUR mail too, > so they can data-mine it and make even more money. > > By and large, gmail users are blissfully ignorant of this and for the > most part don't seem to care. All they know is they don't see much > spam. You get blank stares when you tell them about this and explain to > them that if they receive a service for free, THEY are the product. > "But it's eeeeaaaaasier!" > > It's disgusting, Google ignores any attempt at communication, and > there doesn't appear that anything can be done. > > -Dave > > -- > Dave McGuire, AK4HZ > New Kensington, PA > > _______________________________________________ > 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 swd(a)pobox.com >

2 years, 6 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

Thank you so much Mark. I appreciate your help! I dropped the list and recreated it, the default value worked for the new list. Using Mailman shell is very helpful. I checked the mailman.log and found the issue. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, September 21, 2020 9:42 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/21/20 9:23 AM, Mohsen Masoudfar wrote: > > 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. > After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" This is <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…> fixed by <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…> in Mailman core 3.2.0. Either upgrade Mailman core or set it via `mailman shell` > 2- I checked the python files and found this file, where, it seems, the default value is defined: > /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 > > I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: > The message is being held because: The message is larger than the 40 KB maximum size Changing that file only affects the default setting for new lists. It doesn't affect any existing list. To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like $ /opt/mailman/mm/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 >>> m.max_message_size 40 >>> m.max_message_size = 0 >>> commit() > 3- I totally agree that the most important issue is the fact that the message vanished with the production list. > I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. > > 4- I checked the folders, under /var/lib/mailman3/queue/, all folders > are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ > out/ pipeline/ retry/ shunt/ virgin/ OK, but what if anything is in Mailman's mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 1 month

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

by Bill Oliver

My Ubuntu 24.04 installation is working great, and I have a list running perfectly. I'm now trying to install mailman3 on an older server, this time runing ubuntu 22.04. I'm following the venv installation instructions again, but suddenly came up with a new error. I've made it to the "Run database migrations" section I run mailmanweb-migrate and get: (venv) mailman@mail:~$ mailman-web migrate Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 128, in get_package_libraries module = import_module(entry[1]) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/opt/mailman/venv/lib/python3.10/site- packages/postorius/templatetags/markdown.py", line 21, in <module> from readme_renderer import markdown as md_render File "/opt/mailman/venv/lib/python3.10/site- packages/readme_renderer/markdown.py", line 16, in <module> from CommonMark import commonmark ModuleNotFoundError: No module named 'CommonMark' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib/python3.10/site- packages/mailman_web/manage.py", line 87, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/__init__.py", line 436, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 412, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 458, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 106, in wrapper res = handle_func(*args, **kwargs) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/commands/migrate.py", line 100, in handle self.check(databases=[database]) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 485, in check all_issues = checks.run_checks( File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/checks/registry.py", line 88, in run_checks new_errors = check(app_configs=app_configs, databases=databases) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/checks/templates.py", line 60, in check_for_template_tags_with_the_same_name for module_name, module_path in get_template_tag_modules(): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 105, in get_template_tag_modules for name in get_package_libraries(pkg): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 130, in get_package_libraries raise InvalidTemplateLibrary( django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'postorius.templatetags.markdown': No mod ule named 'CommonMark' I know nothing about CommonMark. Since I've suffered the error cascade problem of trying to fix things and just making it worse, I stopped here. Can I ignore this error, or what can I do to fix it? Thanks! billo

1 year

[MM3-users] Re: Apache Conf

by Thomas G

Yes, of course. Nginx and Apache works on the same server. (Nginx is stopped) I would like switch to Apache to add in front of hyperkitty a ldap connection. I need to re-compile nginx for this feature. It's directly available in apache with a module. In fact, a tried directly to integrade LDAP with django ( https://gitlab.com/mailman/postorius/issues/132) without results. Le ven. 19 oct. 2018 à 20:18, Abhilash Raj <maxking(a)asynchronous.in> a écrit : > > > On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > And, you have verified that the files exist at `/opt/mailman/static` on > your host? > > > > > > > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > > > Hi, > > > > Currently, I use a nginx configuration for mailman. It's work > perfectly. > > > > > > > > I tried to do the same with Apache, but the statics files are not > > > > delivered (404). > > > ... > > > > <VirtualHost *:80> > > > > ServerName mailing.ddd.fr > > > > > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > > > > > <Location /static/> > > > > Alias "/opt/mailman/static/" > > > > </Location> > > > > > > > > <Location /> > > > > ProxyPass http://localhost:8000/ > > > > ProxyPassReverse http://localhost:8000/ > > > > ProxyPreserveHost On > > > > </Location> > > > > </VirtualHost>/ > > > > > > > > > In Apache, location > > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > > > appropriate for resources in the file system. > > > > > > Try > > > > > > Alias /static/ /opt/mailman/static/ > > > > > > not within a location block. > > > > > > -- > > > 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/ > > > -- > thanks, > Abhilash Raj (maxking) >

7 years

[MM3-users] Re: converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Mark Sapiro

On 2/8/22 09:01, Lucio Chiappetti wrote: Snipping to what I thing are the issues. > What I found now (after the migration done by the administrators of the > central seat) is that in mailman3: > > - accept_these_nonmembers is empty > - there are 189 entries listed in Non-members (which look those > formerly in accept_these_nonmembers) And those non-members all have there moderation action set to Defer which means their posts will be accepted but the additional checks such as too big, etc. will still be applied. > - hold_these_nonmembers was copied identical with the same regexp's > as in mailman2 This is all expected. MM 3, unlike MM 2.1 has a concept of nonmembers with moderation action, and this is intended to replace *_these_nonmembers. The legacy *_these nonmembers attributes still exist to support regexps. This is why the addresses were made nonmembers with the appropriate moderation action, but the regexps were retained. > - I have inspected a few of them and found that they have > Administration options Moderation set to List default I'm not sure what you are looking at here. Imported nonmembers should all have moderation action set according to which *_these_nonmembers they came from. Imported members should have their moderation action set to Defer if they were unmoderated and if they were moderated, it should be set based on the 2.1 list's member_moderation_action. > - the effect of this apparently was that a post from some.guy(a)inaf.it > (whose subscription address is guy(a)somewhere.inaf.it) was hold for > moderation > > is this due to a loop with the regexp in hold_these_nonmembers ? It is because all the legacy *_these_nonmember actions are applied before nonmember moderation checks, so if an address matches a regex in hold_these_nonmembers, the post will be held regardless of the nonmember's moderation action. This may actually be a bug. I'll have to think about that. I've filed https://gitlab.com/mailman/mailman/-/issues/978 on this. > the default action would be to let it pass > > Or should we set Administration options Moderation to Accept > immediately ? No. You can avoid this issue by adding the 189 nonmember addresses to accept_these_nonmembers (as addresses, not regexps). Addresses still work, and accept_these_nonmembers takes precedence over hold_these_nonmembers just as in MM 2.1. > - if so, how can we do it automatically for all 189 entries ? > - or move back the 189 addresses to accept_these_nonmembers ? Yes, move them back. > - or for the future have persons posting with alternate addrresses > accepted for the future WITH ONE CLICk ? If they are nonmembers, you can accept the post and set moderation action in one operation in Postorius, but the regexps in hold_these_nonmembers will still take precedence. > - AND LAST BUT NOT LEAST would the syntax @list1 in > accept_these_nonmembers work in mailman3 ? This is https://gitlab.com/mailman/mailman/-/issues/794 (still open) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: ARC

by David Krantz

On Tue, Aug 13, 2019 at 5:54 PM Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > You need to enable ARC by adding the ARC section to mailman.cfg and > setting "enabled = yes" in it. Aha! That was the missing config. Thank you! > What do you mean by "effect"? Is the "effect" that you're not seeing > the presence of ARC header fields in outgoing mail? If so, you > probably haven't set the enabled flag. No, I hadn't as it was not present in the documentation. Tested that and received a stacktrace where authres (of which I know nothing) throws an exception complaining on a syntax error when parsing the AuthenticationResultsHeader. It seems as if it requires an authserv-id field but the few examples of the AuthenticationResultsHeader I've looked at just starts with the server name followed by a semicolon, with no preceeding tag for that server name value. Aug 14 13:43:25 2019 (28958) ACCEPT: <msgid_removed> Aug 14 13:43:26 2019 (28962) Uncaught runner exception: Syntax error: Expected authserv-id at: ; dkim=pass header.d=domain.tld; arc=none... Aug 14 13:43:26 2019 (28962) Traceback (most recent call last): File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/handlers/arc_sign.py", line 71, in process sign(msg, msgdata) File "...VENV/lib/python3.7/site-packages/mailman-3.2.3-py3.7.egg/mailman/handlers/arc_sign.py", line 50, in sign standardize=('ARC-Standardize' in msgdata)) File "...VENV/lib/python3.7/site-packages/authheaders-0.11.0-py3.7.egg/authheaders/__init__.py", line 256, in sign_message return ARC(msg, logger=logger).sign(selector, domain, privkey, srv_id, include_headers=sig_headers, timestamp=timestamp, standardize=standardize) File "...VENV/lib/python3.7/site-packages/dkimpy-0.9.3-py3.7.egg/dkim/__init__.py", line 953, in sign for res in ar_headers] File "...VENV/lib/python3.7/site-packages/dkimpy-0.9.3-py3.7.egg/dkim/__init__.py", line 953, in <listcomp> for res in ar_headers] File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/__init__.py", line 206, in parse return authres.core.AuthenticationResultsHeader.parse(core_features(), string) File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/core.py", line 442, in parse return self.parse_value(feature_context, string) File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/core.py", line 454, in parse_value header._parse() File "...VENV/lib/python3.7/site-packages/authres-1.2.0-py3.7.egg/authres/core.py", line 504, in _parse raise SyntaxError('Expected authserv-id', self._parse_text) authres.core.SyntaxError: Syntax error: Expected authserv-id at: ; dkim=pass header.d=domain.tld; arc=none... Aug 14 13:43:26 2019 (28962) SHUNTING: 1565790206.708188+e4196a80c2afc177ddc001ce8bbd8789f8d08912 > Of what kind? It's a simple protocol: if there is authentication > information (DKIM or ARC) in the incoming message, validate it. Then > package up the validation in the ARC-AR, ARC-Signature, and ARC-Seal > fields. Those are the operations the module performs. Limitations in Mailman3. I really should have written "other requirements or known incompatibilities". Thanks // David

6 years, 2 months

[MM3-users] slow restart time for mailmanweb

by David Newman

Debian 11.2, Mailman 3.3.5, Python 3.9.2, MariaDB 10.5.12-0+deb11u1 On a Debian system running MariaDB, mailman3 restarts quickly but mailmanweb takes about 90 seconds: root@myhost # time systemctl restart mailmanweb real 1m30.156s user 0m0.013s sys 0m0.000s The daemon.log has a timeout error: Dec 28 12:16:01 myhost systemd[1]: Stopping GNU Mailman Web UI... Dec 28 12:16:03 myhost uwsgi[409333]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: State 'stop-sigterm' timed out. Killing. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 409333 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418249 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418250 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418252 (sh) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418254 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418258 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418260 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418261 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418262 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418263 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418264 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418265 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418253 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Main process exited, code=killed, status=9/KILL Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Failed with result 'timeout'. Dec 28 12:17:31 myhost systemd[1]: Stopped GNU Mailman Web UI. Here is /etc/systemd/system/mailmanweb.service file. [Unit] Description=GNU Mailman Web UI After=syslog.target network.target mariadb.service mailman3.service [Service] Environment="PYTHONPATH=/etc/mailman3/" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini [Install] WantedBy=multi-user.target Starting with Debian 11, the MariaDB service is called mariadb and not mysqld or mysql. I tried substituting mysqld and mysql here and rerunning 'systemctl daemon-reload' each time, but restart times were similar, and also produced the same timeout error. And here is /etc/mailman3/uwsgi.ini: ##### [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log ##### What's causing the timeout, and what can I do to speed up restarts? Thanks. dn

3 years, 10 months

[MM3-users] Re: [Mailman-Developers] Container Images for Mailman 3.2 release

by Abhilash Raj

On Fri, Jul 27, 2018, at 1:16 PM, Kamran Soomro wrote: > Hi Abhilash, > > This is great. Thank you very much. Might I make a small suggestion? I > think it might be less confusing to use tags for your images that > conform to the mailman release. E.g. 3.2 should contain mailman 3.2, 3.3 > should contain mailman 3.3 etc. At the moment it’s hard to tell which > image contains which release. Sounds like a good idea! I will push 3.2 tags as soon as I can! > > Just my two cents. > > –Kamran > > > On 27 Jul 2018, at 21:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > Hi All, > > > > I have updated and pushed releases for Container Images with 3.2 release of the suite. > > > > They are available at: > > > > docker.io/maxking/mailman-web:0.2 > > docker.io/maxking/mailman-core:0.2 > > > > A similar copy of both is also available at quay: > > > > quay.io/maxking/mailman-web:0.2 > > quay.io/maxking/mailman-core:0.2 > > > > The releases contain the following versions of components: > > > > mailman-core: > > - Mailman Core 3.2.0 > > - Mailman-hyperkitty 1.1.0 > > > > mailman-web: > > - Postorius 1.2.1 > > - Hyperkitty 1.2.0 > > - Django-mailman3 1.2.0 > > - MailmanClient 3.2.0 > > > > The upgrade process from 0.1 release should be relative painless, except for the full-text index, which needs to be rebuilt due to the migration from Python 2 to 3 of the full-text indexing library whoosh. You can run the following commands to do so, after the upgrade: > > > > $ docker exec -it mailman-web bash > > bash # python manage.py rebuild_index > > > > If you are not using the default docker-compose.yaml file provided in the repo, you need to add an extra environment variable for mailman-web container, POSTORIUS_TEMPLATE_BASE_URL, which defaults to `http://mailman-web:8000`. It should be the URL where your mailman-web container is listening on with HTTP (port 8000 by default). > > > > The rolling releases are not being rolled out right everyday now, because of broken build scripts. I'd recommend everyone use the new stable releases that I mentioned above. Going forward, I'll try to release stable versions more often, so that there isn't any need for rolling version, but fixing the rolling releases is on my TODO. > > > > Documentation for these images is available at: > > > > https://github.com/maxking/docker-mailman > > > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > Mailman-Developers mailing list -- mailman-developers(a)python.org > > To unsubscribe send an email to mailman-developers-leave(a)python.org > > https://mail.python.org/mm3/mailman3/lists/mailman-developers.python.org/ > > Mailman FAQ: https://wiki.list.org/x/AgA3 > > > > Security Policy: https://wiki.list.org/x/QIA9 -- thanks, Abhilash Raj (maxking)

7 years, 3 months

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

by Mark Sapiro

On 7/29/20 4:15 PM, Massimo Zappalà wrote: > Hi Mark, > > /usr/lib/python3/dist-packages/mailman/templates/it$ ls -la > > -rw-r--r-- 1 root root 484 Jul 25 17:21 domain:admin:notice:new-list.txt > -rw-r--r-- 1 root root 825 Jul 25 17:06 help.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 __init__.py > -rw-r--r-- 1 root root 701 Jul 25 17:19 invite.txt > -rw-r--r-- 1 root root 337 Jul 26 16:36 list:admin:action:post.txt > -rw-r--r-- 1 root root 145 Jul 26 16:36 list:admin:action:subscribe.txt > -rw-r--r-- 1 root root 157 Jul 26 16:36 list:admin:action:unsubscribe.txt > -rw-r--r-- 1 root root 56 Jul 26 16:23 list:admin:notice:subscribe.txt > -rw-r--r-- 1 root root 334 Jul 26 16:49 list:admin:notice:unrecognized.txt > -rw-r--r-- 1 root root 43 Jul 26 16:49 list:admin:notice:unsubscribe.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:member:digest:header.txt > -rw-r--r-- 1 root root 423 Jul 26 17:07 list:member:digest:masthead.txt > -rw-r--r-- 1 root root 160 Jul 26 17:08 list:member:generic:footer.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:member:regular:header.txt > -rw-r--r-- 1 root root 658 Jul 26 17:18 list:user:action:subscribe.txt > -rw-r--r-- 1 root root 675 Jul 26 17:18 list:user:action:unsubscribe.txt > -rw-r--r-- 1 root root 0 Jan 4 2019 list:user:notice:goodbye.txt > -rw-r--r-- 1 root root 328 Jul 26 17:23 list:user:notice:hold.txt > -rw-r--r-- 1 root root 464 Jul 26 17:31 list:user:notice:no-more-today.txt > -rw-r--r-- 1 root root 108 Jul 26 17:32 list:user:notice:post.txt > -rw-r--r-- 1 root root 634 Jul 26 17:38 list:user:notice:probe.txt > -rw-r--r-- 1 root root 318 Jul 26 17:40 list:user:notice:refuse.txt > -rw-r--r-- 1 root root 155 Jul 26 17:42 list:user:notice:rejected.txt > -rw-r--r-- 1 root root 554 Jul 26 17:47 list:user:notice:welcome.txt > drwxr-xr-x 2 root root 4096 Jul 29 22:14 __pycache__ What is the ownership of the other directories in /usr/lib/python3/dist-packages/mailman/? They are probably also owned by root and that should be OK as long as they are world readable. >> I may need more information about messages that are and aren't >> delivered. I.e. what's different between them and the way they are >> submitted, or is this one message only delivered to some users? > > After copying the template files in the path indicated by you, the translated emails arrive only to the administrator user while the members of the list arrive in English. Please tell me what messages. Do you mean if I subscribe to the list, I get a welcome message in English, but the list owner gets the notification of a new member in Italian? I think you need to set the system default_language. In mailman.cfg, set [mailman] default_language: it -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

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

by Eggert Ehmke

So at what point did it "block" ? I can't help you when you don't give me exact information and error messages. cheers, Eggert Am Samstag, 12. März 2022, 17:38:02 CET schrieb Yvan ♞: > 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 > Yvan > > Le 12/03/2022 à 15:28, Eggert Ehmke a écrit : > > > Hello Yvan, > > > > > > > > I would suggest to install mailman3 following this guide: > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > > > > > but at first check, which operating system is on your yunohost? Is it > > Debian/ Ubuntu? In this case the guide is fine, else there will be some > > adaptions.> > > > > > > Tell me some details of your system, and if you have root access and can > > install software packages. > > > > > > > > Regards > > Eggert > > > > > > > > Am Samstag, 12. März 2022, 15:16:11 CET schrieb Yvan ♞: > > > >> Hello, just made a try to install mailman 3 on yunohost unsuccessfully > >> Sad... > >> If some body can help me... > >> Thanks > >> https://paste.yunohost.org/raw/hujesebita > >> > >> > >> > >> Le 07/02/2022 à 15:57, Stephen J. Turnbull a écrit : > >> > >> > >> > >>> Yvan ♞ writes: > >>> > >>> > >>> > >>> > >>> > >>> > Just to know if I have a chance, do I have to unistall mailman > >>> > before > >>> > installing mailman 3 ? > >>> > >>> > >>> > >>> > >>> > >>> No. In fact, you can run both at the same time. Not for the same > >>> list, obviously. And it requires a fair amount of planning and careful > >>> attention to your web and MTA configurations. As far as I know there > >>> are no naming conflicts in the default installations, Mailman 2 > >>> installs into directory trees under directories named "mailman", while > >>> Mailman 3 installs under "mailman3". > >> > >> _______________________________________________ > >> Mailman-users mailing list --mailman-users(a)mailman3.org > >> To unsubscribe send an email tomailman-users-leave(a)mailman3.org > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > > > > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 7 months

[MM3-users] Re: How to set up mailman 3

by David Krantz

On Sat, Mar 25, 2017 at 10:35 PM, Barry Warsaw <barry(a)list.org> wrote: > Yes, I'm sorry you went down a dead end with mailman-bundler. I'm trying to > purge the world of it so others won't get led astray. I've clobbered the > README in the GitLab repo and we may at some point just archive and delete the > whole project, but I'm not quite ready to do that yet. I did get things working with the bundler at last. Quite tricky and I have deactivated archival. But I suspect that I should retrace a bit of that work and upgrade to the latest versions. I miss a few functions from mailman2, especially setting a limit for message size to discourage sending larger files to the list. I also notice that there are no modbits per user that I can reach from the web as admin. > Where did you find out about the bundler? I'd like to make sure we steer > people to the current best recommendations: The documentation can be found on several places. The one that is best formatted is this one. I used a worse formatted version of the same text but right now I cannot find the link. https://mailman-bundler.readthedocs.io/en/latest/ I notice that you changed the text on the githlab project. Better. Now I have no idea of how upgrading the different components. I might start from scratch although it probably should be possible to upgrade the parts. The best option is probably to switch to mailman2, but that has disadvantages when handling lists for multiple domains if I am correctly informed and I already have a few domains... I also found that sending mails manually (telnet to port 25) with no headers other than "Subject:" causes the "Held messages" tab to crash with a 500-error. Log below my signature. cheers // David ERROR 2017-03-25 22:54:41,762 base 17632 140529157728000 Internal Server Error: /mailman3/lists/MYLIST.COM.COM/held_messages Traceback (most recent call last): File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/generic.py", line 67, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/views/generic/base.py", line 89, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/auth/decorators.py", line 81, in wrapper return fn(*args, **kwargs) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/views/list.py", line 387, in get held_messages = utils.paginate(request, self.mailing_list.held, 20) File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanclient/_client.py", line 443, in held moderation_reasons=entry['moderation_reasons'], KeyError: u'moderation_reasons'

8 years, 7 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I´m getting this: (env) [mailman@localhost etc]$ mailman stop Shutting down Mailman's master runner (env) [mailman@localhost etc]$ mailman start Starting Mailman's master runner (env) [mailman@localhost etc]$ Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in create_s erver sock.bind(sa) OSError: [Errno 98] Address already in use During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 198, in main runner.run() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/lmtp.py ", line 242, in run self.lmtp.start() File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py" , line 55, in start raise self._thread_exception File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py" , line 35, in _run ssl=self.ssl_context)) File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in run_until _complete return future.result() File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1047, in create_s erver % (sa, err.strerror.lower())) OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 8024 ): address already in use Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 194, in main runner = make_runner(*args.runner, once=args.once) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 94, in make_runner return runner_class(name, slice) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/rest.py ", line 53, in __init__ self._server = make_server() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/rest/wsgiapp.py ", line 234, in make_server handler_class=AdminWebServiceWSGIRequestHandler) File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 153, in make_se rver server = server_class((host, port), handler_class) File "/usr/local/lib/python3.6/socketserver.py", line 453, in __init__ self.server_bind() File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 50, in server_b ind HTTPServer.server_bind(self) File "/usr/local/lib/python3.6/http/server.py", line 136, in server_bind socketserver.TCPServer.server_bind(self) File "/usr/local/lib/python3.6/socketserver.py", line 467, in server_bind self.socket.bind(self.server_address) OSError: [Errno 98] Address already in use Why does it say Address already in use? El mar., 1 ago. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 12:52 PM, Rafael Mora wrote: > > I made a change for test purpose on the mailman.cfg file and I got this: > > > > > > (env) [mailman@localhost etc]$ mailman restart > > Restarting the Mailman runners > > PID unreadable in: /var/lib/mailman/var/etc/var/master.pid > > [Errno 2] No such file or directory: > > '/var/lib/mailman/var/etc/var/master.pid' > > Is the master even running? > > > > How do I solve this? > > > Try > > mailman stop > 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

8 years, 3 months

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

by Mark Sapiro

On 5/3/21 1:45 PM, summersan(a)nclack.k12.or.us wrote: > Hello, > > I've been setting up a new Mailman 3 installation earlier this year, and I think things have been going okay so far. > > I've noticed, however, that after a long amount of time passes (for example, a weekend), when I try to visit the local Mailman 3 web application (e.g., example.mailman.site/mailman3/lists/, where it says "Postorius" at the top left corner of the page and shows a list of mailing lists in the body of the page), I sometimes get a 502 Bad Gateway type of error (referenced from my notes). As far as I can tell, this looks like a normal web server (nginx?) error. If I try visiting the Mailman 3 server location again in a web browser shortly thereafter, I still might get a 502 Bad Gateway error. If I wait a while longer (maybe a minute or more?), the Mailman 3 web application appears to load as expected. What is your configuration for accessing Mailman. I gather you are proxying from nginx to something. Is that something gunicorn or uwsgi? You mention gunicorn but this can be confusing as mailman core's REST API uses gunicorn, but that is separate from the web server's wsgi interface to Django. In any case, this issue is probably with whatever nginx is proxying to (gunicorn or uwsgi) and not with Django or Mailman core. > I've tried looking at the gunicorn documentation (https://docs.gunicorn.org/en/stable/index.html) and searching online (including in this Mailman3 mailing list) to see if there's something that can be done to fix this issue. The closest thing I can find for now is advice for something that, while possibly being technologically unrelated, includes the idea of "warmup requests", which makes me think of simply setting up some sort of script to periodically load a page on the Mailman 3 web application in order to keep it more available for visitors (https://stackoverflow.com/a/57056170) That's certainly a possibility and may be a solution. It would be simple enough to set up an hourly cron to do a curl or wget to retrieve example.mailman.site/mailman3/lists/ and see if that helps. > Is there a setting or something in any of the Mailman 3 related programs that could help with keeping the Mailman 3 web application up and running more often without having to resort to making an ongoing, automated request to the Mailman 3 web application? Nothing that I'm aware of, but if so, it would most likely be a gunicorn or uwsgi setting rather than something in Mailman or Django, although it could be that gunicorn or uwsgi is timing out in trying to connect to Django in which case it could be a Django issue, but not one I've heard of. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Moderation -- implicit destination behavior

by Stephen J. Turnbull

Steve Bachinsky writes: > The lists are configured for “require_explicit_destination”. > However, the email address of the list is clearly in the CC: header > of the email (no alias or subdomain). Is there some other reason > why Mailman would hold an email for moderation with the reason of > “implicit destination”? Since as Mark explained there's no such reason, and there's no obvious "common error" that would explain it, I'm going to list a couple of "wild guesses". It would help if you would show us exactly what you are seeing. - I would guess you're looking at the "raw" or "source" version of the message. But if you're looking at it in a "modern" "helpful" MUA (or it was sent by such), it's possible that according to the header parser the "address" you're looking at is actually the display name (often but not always enclosed in double quotes ""), not the address (usually but not always enclosed in angle brackets <>). - Perhaps there is a missing comma, so that one of the addresses looks like "problem-list(a)your-host.com <some-address(a)somewhere.on.earth>" and there should be a comma after "com". How it's getting to the list that way I don't know; perhaps the list is subscribed to another list (see next point). - Are you sure that the moderating list is the same list that is in the CC? In the common configuration where a high-traffic discussion list is subscribed to a low-traffic announcement list, announcements will be held by the discussion list unless the announcement list is configured as an alias, or the discussion list allows implicit destination. - I can think of a couple of possibilities involving internationalized email addresses (eg, a-labels vs. u-labels which Mailman knows nothing about yet, but should be treated as equivalents). But this seems *really* unlikely, even the IETF has not figured out how to do EAI with mailing lists yet, and almost nobody uses it at all yet. > This moderation is not consistent for same list and poster. The > emails come from a large domain with multiple load-balancing email > servers. I suspect that it may be something with one or more of the > servers being misconfigured, but unable to see anything obvious > from the headers and confused why Mailman states the reason to be > implicit destination when that does not seem to be the cause. I haven't thought carefully about it, but the only such possibility I can think of is that the upstream server is deleting the comma or ignoring the fact that there should be a comma. Otherwise, whatever is happening is local to your MTA + Mailman system, I'm pretty sure. I hope one of the wild guesses helps you figure out what's going on, or helps you find a more useful anomoly. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

5 months, 2 weeks

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

by Jeremy Stanley

In the OpenDev Collaboratory we've got a bunch of separate Mailman 2.1 vhosts we've started migrating into a single Mailman 3.3.7 server, desiring to take full advantage of its improved multi-domain support. For the most part everything is working great (kudos to everyone who maintains the software and documentation, it's excellent). One of the things our users noticed fairly quickly was Hyperkitty on the second vhost was incorrectly showing the FQDN of the first vhost near the top of its pages. This is covered in the FAQ of course, and seems to imply that what we want is to switch the SITE_ID from 1 to 0 in our settings.py in order to take advantage of magic domain-guessing behavior. So far so good. Unfortunately, SITE_ID = 0 seems to explicitly require the addition of "mail hosts" (or "mail domains" from Django's perspective), and all the web routing returns error pages for any list sites besides the first one since, by default, our server did not have these predefined. What's odd is that, if I log into Postorius as admin and visit the "manage domains" page, suddenly the database gets populated with mail hosts for all of the FQDNs associated with our imported mailing lists. I would not have expected merely visiting that page as an admin to have a side effect of adding entries for the "missing" mail hosts, is that an intentional behavior or merely a bug? Once these entries are automatically added by visiting that page, they're all associated with the one "web host" ("site" in Django) we have for the server, and now the list filtering functionality in Postorius breaks and any of the vhosts all display the full set of mailing lists on the server rather than only those associated with a particular vhost (note that this seems to only be confusing Postorius, Hyperkitty has them correctly filtered still). Okay, so it looks like this is because the mail hosts are all tied to the one web host. We can create additional "sites" in the Django admin UI and then switch the association of the mail hosts to those distinct web hosts. But after doing so, the first vhost still seems to show an unfiltered list of all lists in Postorius (Hyperkitty continues to be fine), while Postorius on the other vhosts correctly shows their filtered sets of lists instead. I also noticed when mailman-web is starting up, its log claims the first site is being set as the "default domain," so have to wonder if that's related to this behavior. Should we create an extra web host to serve as the "default" so that all our typical vhosts get the expected list filtering behavior, or am I completely off-base and there's a much better approach I've missed? Sorry this is so long, I feel like I have at most a tenuous grasp of the details and variables involved, but hopefully it makes sense to someone. Thanks in advance for any recommendations or guidance. -- Jeremy Stanley

2 years, 10 months

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Wed, Feb 15, 2023 at 7:26 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 08:09, Odhiambo Washington wrote: > > > > [18:47 ~ ]$ ls -al /opt/mailman/mm/var/templates/lists/ > kictanet.lists.kictanet.or.ke/en/ > > total 48 > > drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . > > drwxr-xr-x 3 mailman mailman 512 Feb 14 08:54 .. > > -rw------- 1 mailman mailman 615 Jan 17 13:57 > domain:admin:notice:new-list.txt > > This template is used in a domain context. It will never be accessed > here. It needs to be in /opt/mailman/mm/var/templates/site/en/ or > /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ The last time I referred to the link, I deliberately duplicated the <LC> folder in two locations: [09:51 ~ ]$ ls -al /opt/mailman/mm/var/templates/site/en/ total 48 drwxr-xr-x 2 mailman mailman 512 Feb 14 08:53 . drwxr-xr-x 3 mailman mailman 512 Feb 14 08:53 .. -rw------- 1 mailman mailman 615 Jan 17 13:57 domain:admin:notice:new-list.txt -rw------- 1 mailman mailman 341 Jan 17 13:54 list:admin:action:post.txt -rw------- 1 mailman mailman 158 Dec 17 13:32 list:member:digest:footer.txt -rw------- 1 mailman mailman 452 Jan 17 13:54 list:member:digest:masthead.txt -rw------- 1 mailman mailman 137 Jan 17 13:55 list:member:generic:footer.txt -rw------- 1 mailman mailman 1219 Dec 8 15:12 list:member:regular:footer.txt -rw------- 1 mailman mailman 944 Jan 17 15:50 list:user:action:subscribe.txt -rw------- 1 mailman mailman 247 Jan 17 13:56 list:user:notice:post.txt -rw------- 1 mailman mailman 802 Jan 17 13:56 list:user:notice:probe.txt -rw------- 1 mailman mailman 639 Jan 17 13:57 list:user:notice:welcome.txt Yet, it is NOT being picked. So definitely something is wrong somewhere. > > -rw------- 1 mailman mailman 341 Jan 17 13:54 > list:admin:action:post.txt > > -rw------- 1 mailman mailman 158 Dec 17 13:32 > list:member:digest:footer.txt > > -rw------- 1 mailman mailman 452 Jan 17 13:54 > list:member:digest:masthead.txt > > -rw------- 1 mailman mailman 137 Jan 17 13:55 > list:member:generic:footer.txt > > The generic footer is used for both regular messages and digests if > there isn't a specific regular or digest footer. In this case, you have > both so the generic footer won't ever be used. > Thank you for clarifying that. I actually will delete the generic footer in this case because I don't need it. > > -rw------- 1 mailman mailman 1219 Dec 8 15:12 > list:member:regular:footer.txt > > -rw------- 1 mailman mailman 944 Jan 17 15:50 > list:user:action:subscribe.txt > > -rw------- 1 mailman mailman 247 Jan 17 13:56 > list:user:notice:post.txt > > -rw------- 1 mailman mailman 802 Jan 17 13:56 > list:user:notice:probe.txt > > -rw------- 1 mailman mailman 639 Jan 17 13:57 > list:user:notice:welcome.txt > > Are the other templates such as list:member:regular:footer.txt used? > I do see that in posts to the list, but I believe that is perhaps only working because the list had that footer when it was imported from MM2. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

[MM3-users] List Digest - Subject line

by Stephen J. Turnbull

smorytko(a)gmail.com writes: > Is there a way to optionally cause the Subject line to display with > the text body and as a summary at the top of the digest? It will always appear in the summary, I believe. Unless someone at your site has changed the configuration for mime_digest_keep_headers and/or plain_digest_keep_headers, it is already included, and should be displayed in the individual messages. I suspect this is a user agent (mail client) problem. > Again I'm wondering if this is a web front-end function, a MM3 core > function, or perhaps both? I ask because if it's not a MM3 core > function I'll need to ask our developer for an Empathy > modification. The digest message is a core function. When a message arrives for a digest-able list, Mailman core will add that to a separate mailbox, signalling the digest runner. The digest runner then decides if it's time and if so, reads the mailbox and assembles and sends the digest message. Digest creation and distribution is therefore entirely done by Mailman core. Display is another matter. As with all received mail, the Harvard Law applies: Under the most rigorously controlled conditions of pressure, temperature, volume, humidity, and other variables the [mail client] will do as it damn well pleases. Digest display is notoriously awful in common consumer mail clients. Many frustrated admins simply turn off the feature to quiet their subscribers. > Below is an example from an Empathy-base list The web interface doesn't matter. As far as I know it is impossible for the archive interfaces (Empathy, HyperKitty, etc) to view digests, because they receive each post individually and have no way to know the digesting schedule, so they can't calculate one either. That's certainly true of HyperKitty. So I assume you are viewing the digest in your own mail client? There are two possibilities. 1. Your mail client is refusing to display the headers in the digested messages even though they are present. I think this is more likely; the digest header configuration is rarely if ever changed. 2. The list is configured not to keep any headers. If you have access to the Mailman configuration files, the defaults are in the [digests] section of schema.cfg, and local changes, if any, are in the [digests] section of mailman.cfg. (Local changes completely override the configuration in schema.py.) If you don't, you'll have to ask the admin to check. Here are the schema.cfg defaults from a fairly fresh update of the Mailman sources (I doubt these lines have changed since being written): [digests] # Headers which should be kept in both RFC 1153 (plain) and MIME digests. RFC # 1153 also specifies these headers in this exact order, so order matters. # These are space separated and case insensitive. mime_digest_keep_headers: Date From To Cc Subject Message-ID Keywords In-Reply-To References Content-Type MIME-Version Content-Transfer-Encoding Precedence Reply-To Message List-Post plain_digest_keep_headers: Message Date From Subject To Cc Message-ID Keywords Content-Type ("Space separated" includes newlines and tabs.) As you can see, Subject is in both. Steve

4 years, 5 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, my first post was to optimistic - the user tested some other combinations and when he tries to send a signed HTML mail, the server again refuses to accept it with "Diagnostic-Code: smtp; 501 Message has defects". The user suggested that the problem is caused by a line containing only "-- " somewhere in the text, but I can not confirm this. Please find enclosed the refused mail (anonymized). Regards Rainer On Mi, 20 Apr 2022 10:51:38 +0200 Rainer Herbst <rainer.herbst(a)aip.de> wrote: > Dear all, > > as the original poster, I have asked the user to send a test mail >through our mailman3 system (docker image > maxking/mailman-core:0.4.2) and the mail passed. > > The user is now on Apple Mail 16, maybe that does the trick. Please >find enclosed the anonymizied mail source. > > Best regards and thanks for caring even if the problems seems to >affect only a small number of users! > Rainer > > On Fr, 15 Apr 2022 09:03:41 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: >> On 4/14/22 21:33, Stephen J. Turnbull wrote: >>> >>> Whether we *want* to do that depends on how much trouble that causes >>> for our main constituency (list and site admins), and whether we can >>> provide discoverable documentation of the problem. My take is that >>> this seems to be an extremely rare problem, and at least some MUAs >>>are >>> able to read the message, so we should let it through. >> >>First, we are not silently dropping this message. We are rejecting it >>at LMTP time so the sender should be notified. >> >> 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. >> >> 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. >> >> >> -- >> 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/ >> > > Viele Grüße > > Rainer Herbst > Leiter IT-Service > Phone: +49 331 7499-257 > e-mail: rainer.herbst(a)aip.de > https://www.aip.de > > ----------------------------------------------------------------------------------------------- > Leibniz-Institut für Astrophysik Potsdam (AIP) > An der Sternwarte 16, 14482 Potsdam > > Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach > Stiftung bürgerlichen Rechts > Stiftungsverzeichnis Brandenburg: 26 742-00/7026 > ----------------------------------------------------------------------------------------------- Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 -----------------------------------------------------------------------------------------------

3 years, 6 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Abhilash Raj

> On Mar 19, 2021, at 6:38 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html You seem to have landed on a very old version of the docs that I didn’t unfortunately knew was even available. I have disabled that page now. The settings are documented in https://docs.mailman3.org/en/latest/config-web.html > > I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > How could I check, that the setting is used!? > > But maybe some additional information: > - I use the Debian installation on a stable buster, so mailman is version 3.2.1 > - I use apache2 as my web-server and use the given alias-conf-file > - Python is version 3.7.3 > - Postorius is Version 1.2.4 > - HyperKitty is version 1.2.2 > > -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de > -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above > -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de > -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de > -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains > > What do I miss? Or where to investigate? > > Thank you in advance, best regards. > > By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html Mailman Suite consists of several individual projects including Mailman Core, Postorius (Web UI) and Hyperkitty (Archiver). The first URL is the landing page for the entire suite and should direct you to individual projects. The second one is the individual Mailman Core project. Historically, Core was the only project and hence claims the name “mailman” in most places. > > Am 18.03.21 um 21:52 schrieb Mark Sapiro: >> On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >>> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? >> Set FILTER_VHOST = True in your settings_local.py or where ever you put >> your site Django settings. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

4 years, 7 months

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

by Mark Sapiro

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

1 year, 10 months

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

by Andreas Barth

* Jens Günther (jens.guenther(a)posteo.de) [210621 17:05]: > Hey there, > > in Mailman2 there was a simple link in the moderation-emails, with > which I was able to open directly the "held-messages". I know how to > manually integrate such a link with the variables of mailman (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > But: > > How can I change the template for all the lists (respectively > maildomains/webdomains) so that I don't have to do this manually for > all lists? I searched a bit for the corresponding template, but > didn't find it. At the end it only says the following: I'm using this patch (however, german-only) Andi diff --git a/src/mailman/templates/de/list:admin:action:post.txt b/src/mailman/templates/de/list:admin:action:post.txt index bc76a54c4..85cdd9376 100644 --- a/src/mailman/templates/de/list:admin:action:post.txt +++ b/src/mailman/templates/de/list:admin:action:post.txt @@ -9,5 +9,6 @@ Die Nachricht wurde aus folgenden Gründen zurückgehalten: $reasons -Besuchen Sie die Administrations-Seiten, um die Nachricht +Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/held_messages diff --git a/src/mailman/templates/de/list:admin:action:subscribe.txt b/src/mailman/templates/de/list:admin:action:subscribe.txt index 88427c8d0..ba77aa3ce 100644 --- a/src/mailman/templates/de/list:admin:action:subscribe.txt +++ b/src/mailman/templates/de/list:admin:action:subscribe.txt @@ -3,3 +3,7 @@ die Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Anmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:admin:action:unsubscribe.txt b/src/mailman/templates/de/list:admin:action:unsubscribe.txt index c794355e8..0bace3950 100644 --- a/src/mailman/templates/de/list:admin:action:unsubscribe.txt +++ b/src/mailman/templates/de/list:admin:action:unsubscribe.txt @@ -3,3 +3,7 @@ der Mailingliste nötig: Für: $member Liste: $listname + +Besuchen Sie die Administrations-Seiten, um die Abmeldung +anzunehmen oder abzulehnen. +https://$domain/mailman3/postorius/lists/$list_id/subscription_requests diff --git a/src/mailman/templates/de/list:user:notice:welcome.txt b/src/mailman/templates/de/list:user:notice:welcome.txt index 3efc32bd1..974d8e465 100644 --- a/src/mailman/templates/de/list:user:notice:welcome.txt +++ b/src/mailman/templates/de/list:user:notice:welcome.txt @@ -1,16 +1,18 @@ Willkommen auf der Mailingliste "$display_name"! -Um an diese Liste zu schreiben, senden Sie eine E-Mail an: - +E-Mails an die Adresse $listname +werden an alle Teilnehmer verteilt. -Sie können Einstellungen vornehmen, indem Sie eine E-Mail an +Auf der Webseite https://$domain/ können Sie Ihre Einstellungen verwalten. +Wer dies möchte, kann sich dort registrieren - bitte mit der E-Mail-Adresse, +die auf der Mailingliste eingetragen ist. Nach dem Einloggen ist auch +möglich, die Empfangsadresse für die Mailinglisten zu ändern, oder +zusätzliche Sendeadressen einzurichten. +Sie können auch Einstellungen vornehmen, indem Sie eine E-Mail an $request_email - mit dem Wort 'help' (ohne Anführungszeichen) im Betreff oder im Inhalt -senden, Sie erhalten dann eine automatisierte Antwort mit weiteren -Instruktionen. Sie werden Ihr Passwort benötigen, um Änderungen an Ihren -Einstellungen vorzunehmen, aber aus Sicherheitsgründen wird dieses hier -nicht angegeben. Sollten Sie Ihr Passwort vergessen haben, nutzen Sie bitte -die 'Passwort vergessen'-Funktion auf der Login-Seite. +senden. Sie erhalten dann eine automatisierte Antwort mit weiteren +Instruktionen. Um Änderungen bei den Einstellungen vorzunehmen, wird das auf +https://$domain/ vereinbarte Passwort benötigt.

4 years, 4 months

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

by Victoriano Giralt

El viernes, 31 de diciembre de 2021 1:48:38 (CET) David Newman escribió: > I'd like for regular (non-admin) list subscribers to be able to manage > their subscription preferences and view list archives. That's a good way to go :-) My response is more of a (very) old sysadmin and Django user (since 2008) hunch that a proper one based on code and documentation review, but I've been trying to contribute several times and always (super) Mark Sapiro beats me :-) > If I'm reading the error correctly, this is related to an inability to > verify the cert chain. The /etc/mailman3/settings.py file points to the > same cert and key files used by Nginx, Postfix, and Dovecot. You are right in your diagnose but not in your interpretation (see my comment below inside the traceback). It is certificate related, but not for server TLS, but for CLIENT authentication. > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > EMAIL_HOST_USER = 'dnewman(a)networktest.com' > EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' > EMAIL_USE_TLS = 'True' > EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' > EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' All these settings above are used for SENDING messages and, if I'm not mistaken, the SSL key and cert are used for authenticating the user sending the email. Actually, using TLS and SMTP Auth for localhost is a bit too much. I've been configuring SMTP servers since 1990 and my mail servers just accept mail form localhost, if they are broken into, the user and password have already been exposed :-) > But this might only be for email, not Postorius/Django. You are right (if I also am) > What additional configuration is needed to allow regular users to create > and manage their own accounts? I'd say that is more what is not needed (the SMTP TLS authentication) I'll remove the "noise". These are the tell tale lines: > "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smt > p.py", line 67, in open > self.connection.starttls(keyfile=self.ssl_keyfile, > certfile=self.ssl_certfile) The SMTP Django backend is trying to connect to the mail server to send the Mailman account confirmation message and failing, probably because the user Django runs as cannot open the private key (which is a very sensible thing if that private key is the one used for the web facing TLS certificate, I can tell you how bad in private or search for my name, wasd, apache and VMS ;-)) That certificate is not needed for sending email from Django, and, as I said, not even SMTP Auth for sending via localhost. Actually, doing SMTP Auth on port 25 is not even recommended practice. Happy, healthy, safe and well ventilated New Year to all. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

3 years, 10 months

[MM3-users] Re: transport map (postfix_lmtp) does not update - new lists not working

by Odhiambo Washington

On Mon, Jan 29, 2024 at 2:32 PM Nils <mailman(a)bugblatterbeast.de> wrote: > End of last year, I've re-installed mailman3 using the virtualenv > installation method on ubuntu 20.04. > > Since then, the transport map (/opt/mailman/mm/var/data/postfix_lmtp) > has not been updated even though, new mailing lists were created. The > old mailing lists, that existed before the re-installation work > perfectly fine but those created after are not accessible. Because the > entries for those new lists are missing in the transport map, postfix > replies with a "mail for ... loops back to myself" error. > > I'm quite sure, that I did all the steps in the documentation (except > that I use a slightly different apache2 vhost configuration). I double > checked on the cronjobs. > > crontab -u mailman -e > > @daily /opt/mailman/venv/bin/mailman digests --periodic > @daily /opt/mailman/venv/bin/mailman notify > > * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely > 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly > @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly > @daily /opt/mailman/venv/bin/mailman-web runjobs daily > @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly > @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly > @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly > > Any idea, what I could have missed??? > > Kind regards, > Nils > I am not any good with Postfix, nor am I an expert with MM3, but my thinking is that those files are updated by Mailman whenever you create a list. Postfix only reads them. Now the question lingering in my head is: How does Mailman know that it needs to create those files? I think that unless you tell Mailman - via mailman.cf - that you aren't using Exim or Sendmail or other MTA, then it assumes that you are using Postfix and so creates/updates those files. I am saying that because in my mailman.cfg I have this: [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 verp_probes: yes incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost smtp_host: localhost lmtp_port: 8024 smtp_port: 25 configuration: python:mailman.config.exim4 <============ I think this is probably what stops Mailman from creating those files on my server. Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…, I do not see the line starting with "configuration", so I am taking it that Mailman core presumes Postfix by default. Now the other question is why would it NOT update those files whenever you create a new list? And I am thinking that maybe the permissions on that directory, or the initial files changed during your reinstall and so they could not be written to/updated. This is just my guess. I am sure the proper explanation is on the way :-) -- 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, 9 months

[MM3-users] Re: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/5/25 11:17, dap1--- via Mailman-users wrote: > Sorry Mark: > > These hundreds of emails are distracting and I have too many irons in the fire between you and Stephen. That is not a criticism as I greatly appreciate the help from both of you. Just that I'm having difficulty keeping up with you both. ``` > sudo grep -r '/usr/share/mailman3-web/manage.py' /etc/cron* /var/spool/cron > > /etc/cron.d/mailman3-web:* * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely > /etc/cron.d/mailman3-web:2,17,32,47 * * * * www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.quarter_hourly /usr/share/mailman3-web/manage.py runjobs quarter_hourly > /etc/cron.d/mailman3-web:@hourly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.hourly /usr/share/mailman3-web/manage.py runjobs hourly > /etc/cron.d/mailman3-web:@daily www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily > /etc/cron.d/mailman3-web:@weekly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.weekly /usr/share/mailman3-web/manage.py runjobs weekly > /etc/cron.d/mailman3-web:@monthly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.monthly /usr/share/mailman3-web/manage.py runjobs monthly > /etc/cron.d/mailman3-web:@yearly www-data [ -f /usr/bin/django-admin ] && flock -n /v > ar/run/mailman3-web/cron.yearly /usr/share/mailman3-web/manage.py runjobs yearly ``` This is not the crontab you reported at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… That one is probably /var/spool/cron/crontabs/mailman and wouldn't show here because it doesn't contain '/usr/share/mailman3-web/manage.py'. So the system crontab at /etc/cron.d/mailman3-web is your issue and should be removed. That will get rid of the cron failure emails. > This was a fresh install of Ubuntu server so the only packages installed so far are dump/restore, Ubuntu-desktop, MySQL, Postfix, fetchmail and mailman3. Apache2 comes preinstalled with Ubuntu but there may be others of which I am currently unaware. As far as I know the only other crontab is for root where I have the backup jobs scheduled. > > 0 3 * * 0 /usr/local/sbin/sysbackup Then the remaining question is how did that crontab get there in the system crontabs. The only way I know it could have gotten there if you didn't manually create it is via installation of Ubuntu Mailman packages. I think you probably also have a django-admin and perhaps other things in /usr/bin/ and also a /usr/share/mailman-web/ directory which you don't want or need. I suggest you do sudo apt list mailman3 mailman3-web mailman3-full mailman3-doc and see which of those unwanted packages are installed, and if any, `sudo apt remove` them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 days, 5 hours

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

by Marco van Tol

Op 25 jan 2024, om 14:16 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: > Op 24 jan 2024, om 13:46 heeft Marco van Tol <mvantol(a)ripe.net> het volgende geschreven: >> 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. > > Okay, so, I got a bit further, but something still gets stuck. > > Here’s what I did. > Keep in mind I’m using containers that are built from some CI/CD pipeline, so I updated the pipeline to apply the patch attached to this email to `/usr/lib/python3.11/site-packages/xapian_backend.py`. > > Before I had 2 list servers with the “Term too long” issue, 1 got resolved by this, and the other did not. > I opened a shell in the newly deployed container to confirm the patch was applied in it. > > The other attachment to this email is a copy/paste from the full error from `./manage.py rebuild_index`. > > Is there something else special in the email that makes it choke that evades the xapian patch? > > Thank you very much in advance! I tried to change to ‘hash’, but the code in that bit of the function has not been tested enough. For example `hole = sha224(hole.encode('utf8')).hexdigest()` comes back with that the bytes object hole does not have an encode() method. When I change it to `hole = sha224(hole).hexdigest()`, the following error is: text = text[:match.start()] + hole + text[match.end():] TypeError: can't concat str to bytes The ‘hash’ part of that function needs some debugging. Marco

1 year, 9 months

[MM3-users] Re: logrotate

by Odhiambo Washington

On Wed, May 3, 2023 at 2:38 AM Mark Sapiro <mark(a)msapiro.net> wrote: > Please don't hijack threads. Post a new topic as an original post, not > as a reply to an old thread. > > On 5/2/23 15:45, Christian via Mailman-users wrote: > > I noticed that my mailman logfiles are not being rotated. I followed the > > instructions in > > > https://mail.python.org/archives/list/mailman-developers@python.org/message/ > > FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ > > > Those instructions are for Mailman 2.1. > > > > Now when I try and run logrotate I get the following error > > > > root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf > > error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file or > > directory > > error: stat of /opt/mailman/mm/error.log failed: No such file or > directory > > error: stat of /opt/mailman/mm/mailman.log failed: No such file or > > directory > > error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file or > > directory > > error: stat of /opt/mailman/mm/smtp.log failed: No such file or > directory > > root@zarathustra: > > > > What am I doing wrong please? > > Here's a logrotate script I use: > ``` > /opt/mailman/mm/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > sudo -u mailman /opt/mailman/mm/bin/mailman reopen &>/dev/null > || true > if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mm/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } > ``` > A couple of caveats. The first line of the postrotate script may be > wrapped. `sudo ... true` is all one line. > > That line could also be > ``` > /opt/mailman/mm/bin/mailman --run-as-root reopen &>/dev/null || true > ``` > I.e., it either has to run as the mailman user or specify the > --run-as-root option. > > Also, if logs aren't in /opt/mailman/mm/var/logs/ or gunicorn.pid isn't > in /opt/mailman/mm/var/ those paths need adjusting. > > Finally, there may be an issue with `mailman reopen` in the postrotate > scrupt. See https://gitlab.com/mailman/mailman/-/issues/1078 > > In my case, I took a different approach with Django's logging configuration: [snip] 'handlers': { 'file': { 'level': 'INFO', 'class': 'logging.handlers.TimedRotatingFileHandler', 'filename': '/opt/mailman/mm/var/logs/mailmanweb.log', 'when': 'D', # specifies the interval 'interval': 1, # defaults to 1, only necessary for other values 'backupCount': 5, # how many backup file to keep, 5 days 'formatter': 'simpleRe', }, }, [snip] I have not been rotating the other log files as my list is not a high-volume one so logs aren't growing much. Plus I only rely on the logs for diagnostics, not for records ;( -- 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, 6 months

[MM3-users] Outgoing runner lockup? + "slice inspector" tool

by Stephen J. Turnbull

Hi, I'm advising a user on a system which experiences occasional lockups in an outgoing runner. The runner contacts a remote smarthost, and occasionally locks up with the smtp connection still open according to "lsof -i :25". This state seems to be permanent: the backlog for that slice starts to grow without bound, for at least an hour. When this was happening once a month, they would just restart Mailman core, and the backlog would clear in minutes. But recently it's been happening daily which is distracting their staff, and worries me. Another thing that is strange about this site is that it should be possible to hit that runner with a SIGUSR1 and restart it. This works for me, but on that system the stuck runner exits, but does not restart. Since normally it only happens to one runner of several, I wanted to identify the runner and process. I attach the tool I developed, for anyone who might have configured multiple runners and is interested to see the distribution across runners. Has anybody seen an outgoing runner lock up with an open smtp session? Any ideas on why? My analysis so far: - Because a restart works every time, I'm pretty sure it doesn't have anything to do with message content. - I believe both the Mailman host and the outgoing smarthost are Linodes, in the same datacenter. The problematic Mailman system is Mailman 3.3.6, Python 3.10 on Ubuntu 16.xx LTS. I believe the smarthost is a more recent Ubuntu LTS, probably running Postfix 3.7 as the MTA. (Yes, they have sufficiently paranoid security and QA teams. ;-) - We're using smtplib, which as far as I can tell basically has a 60s timeout for each command. Thus you'd think it would time out. I guess it could be inflooping on timeout, retry, timeout, retry, but I don't know how to check that. Maybe ss(8) will serve? - My system where SIGUSR1 works as documented is Python 3.11.2 on a Digital Ocean droplet with Debian 12.9, Linux 6.1.0. - I haven't tried to reproduce the Python 3.10 + Mailman 3.3.6 configuration and test SIGUSR1 in that configuration yet. Seems unlikely, waiting for the proverbial "round tuit". - It has occurred to us to use the local Postfix as the relay MTA. I'm waiting on a report whether that alleviates the problem. Even if so, I want to fix the underlying defect if possible. Any ideas would be welcome, including general debugging advice. Here's the promised slice_inspector tool. (Patches and suggestions welcome, though I don't promise to implement any time soon.) The tool imports some files from Mailman core, click, and psutil (not psutils!) I believe the latter modules are required by Mailman, so you should be able to run it as is under the 'mailman' user (or perhaps 'list' on Debian) in the environment Mailman itself uses. It defaults to assuming that mailman.cfg is /etc/mailman3/mailman.cfg. You'll probably need to fix the shebang if you want to chmod +x. The '--help' should be pretty self-explanatory. Steve

9 months, 1 week

[MM3-users] Re: More Mailman releases!

by Jered Floyd

Everything looks good to me in my multi-site install! I've updated my simple container install to pin the new versions: https://github.com/jeredfloyd/mailman-container --Jered ----- On Oct 22, 2023, at 2:10 AM, Abhilash Raj maxking(a)asynchronous.in wrote: > Hello, > > I missed one important merge request in django-mailman3, so here are a > couple more versions. > > I've released Django-mailman3 1.3.11 and Mailman-web 0.0.8 (which > requires django-mailman >= 1.3.11). > > Gitlab releases are available here: > > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.8 > Django-mailman3: > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.11 > > I have also yanked mailman-web 0.0.7 since that'll cause spurious errors > due to change in session serializer. > > Abhilash > > > On 10/22/23 00:05, Abhilash Raj wrote: >> Hello Everyone, >> >> I am pleased to announce several new releases for GNU Mailman project. >> Thanks to all the contributors for making these releases possible! >> >> 1. Postorius 1.3.10 [1] >> 2. Hyperkitty 1.3.8 [2] >> 3. Django-mailman3 1.3.10 [3] >> 4. Mailman-web 0.0.7 [4] >> >> All the releases are published to PyPI and you can find links to all the >> PyPI projects: >> >> https://docs.mailman3.org/en/latest/ >> >> A full list of change logs are available below: >> >> [1]: >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 >> [2]: >> https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 >> [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst >> [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst >> >> Do note that for Postorius, I released 1.3.9, but I forgot to update >> dependency metadata to require `django-mailman3>=1.3.10` (which is >> required for the new bootstrap 5 upgrade across packages) and so I also >> released Postorius 1.3.10 just after. >> >> Installation documentation is available at >> >> https://docs.mailman3.org/en/latest/install/install.html >> >> and if you are upgrading an existing virtualenv install you can refer >> >> https://docs.mailman3.org/en/latest/upgrade-3.2.html >> >> If you find any issues, you can report them at the respective bug >> tracker for the projects. The links to issue trackers are available >> at https://docs.mailman3.org/en/latest/. >> >> Finally, similar to Mailman Core, note that PyPI doesn't accept >> signatures anymore so each packages' release page now has the tarball >> uploaded to them along with the signature: >> >> Django-mailman3: >> https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 >> Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 >> Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 >> Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 >> > > -- > thanks, > Abhilash Raj (maxking) > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://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 jered(a)convivian.com

2 years

[MM3-users] Re: Default values for new lists

by Sten Aus

Thanks! Opened two new issues on Hyperkitty. This another problem in Mailman core styles - I hope to see it soon. As right now comparing to Mailman2 I have extra movements that needs to be done to achieve same outcome. Thank you and all the best! Sten On 09/01/2018 05:08, Abhilash Raj wrote: > On Thu, Jan 4, 2018, at 3:00 AM, Sten Aus wrote: >> Also, I would like to change archive (hyperkitty) default sort order >> (for Name), because I think it is weird where I cannot see lists I am >> participating in (even if I am logged in) in "most popular" view. Can it >> be achived somehow? >> >> >> And I think it's weird too that I see all lists in archive view (even if >> they are private) even when I am not subscribed to them. Only thing >> keeping me away from that list is that I cannot see archives and error >> message is displayed. >> >> >> Although I cannot imagine how many of list users log in to mailman panel >> and then try to access archives, mostly it is done by accessing direct >> link. But I don't need to display all archives (almost 3000) lists to >> every logged in user, if they are member of only one or two. > I am not 100% sure about it, but I don't think it can be configured right now. You can open an issue in Gitlab[1], I think it would be something useful to have. > > [1]: https://gitlab.com/mailman/hyperkitty/issues > >> On 04/01/2018 11:47, Sten Aus wrote: >>> Hi >>> >>> I haven't found out where I could choose or edit default list values >>> (when creating new list). >>> >>> For example I would like that all new lists would be with *private >>> archive* (and change this when it is needed). >>> This is great that I can choose not to advertise list in Index (which >>> I can choose from list creation interface) but I would like to choose >>> other options too. >>> Right now only solution is to create list and then choose Archiving >>> and then select "private archives". >>> >>> Another thing is that I would like to choose default subscription >>> policy to "Moderate". >>> >>> If anyone has encountered this problem, let me know! > Default settings are termed as "styles" in Mailman Core, and these can be used to create a default configuration for a list. However, these aren't easily configurable right now. There are few default styles that do exist today (annoucement, for example), but I am not sure if they are exposed in the UI. > > We had one of our GSoC student work on this and there is a merge request pending somewhere that improves the "Styles" in Mailman Core. However, it isn't a part of Core yet. > >

7 years, 10 months

[MM3-users] Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/25/23 10:57 PM, Ken Alker wrote: > > I have studied the output, looked at the code lines referenced in the > Traceback, and I can't figure out the problem (I feel like the sad guy > on the side of the street with his hood up staring into the engine bay > with stream pouring out and not knowing what to do next). I did some > analyses on the log file and determined that there are 71 messages it is > having problems processing and there are 71 messages "stuck" in > /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to > process each message about 20 times). Each time there is a new post, it retries all the messages in the spool/ directory. > Since upgrading to V3.3.8 I've > not seen new messages get stuck like this (although it's only been > running smoothly for 24 hours now and there hasn't been much activity). > But I'm suspecting there was something awry between the conversion from > V2 to V3 in February and me installing V3.3.8 that caused this (based on > message time stamps). It is HIGHLY likely these messages are in the > archiving spool as a result of me unshunting the shunt queue and that > they are copies of the messages that got delivered to the subscribers > when I did that... but are now hung up in the archiving process. Are new messages being archived OK. If so, that is a real mystery. It says mailman-hyperkitty can talk to hyperkitty and archive new messages, but it can't talk to hyperkitty when attempting to process a queued message. > Following is an excerpt from mailman.log. Note that the "first section" > (from DOCTYPE at top to 404 at bottom) is repeated four times (maybe not > identical; but similar) (so I did not include it to save room) before > the Traceback appears. > > Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list > found > Jun 25 00:13:04 2023 (386086) ACCEPT: > <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > Jun 25 00:13:04 2023 (386090) HyperKitty failure on > https://lists.netlojix.com/hyperkitty/api/mailman/urls: I just went to that URL and got a 404. This is a serious problem. https://lists.netlojix.com/hyperkitty/api/ also returns a 404. It should return some documentation of the API. https://lists.netlojix.com/archives/api/ does work and returns the expected information. Your urls.py file probably contains in its urlpatterns list ``` re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), ``` The simplest fix is to add ``` re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')), ``` to that list. Another way to fix this is in your mailman-hyperkitty.cfg, you have ``` base_url: https://lists.netlojix.com/hyperkitty ``` Change that to ``` base_url: https://lists.netlojix.com/archives ``` but it wouldn't hurt to add the `^postorius/` and `^hyperkitty/` patterns to urls.py anyway. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: [ERROR] Error handling request List archivers

by Shashikanth Komandoor

Thank you Mark for guiding me to the benefit of putting the list and so I have added the list. Along with the [archiver.hyperkitty], [mta] and [database], few lines of my mailman.cfg look like below: *[webservice]workers = 4timeout = 900* The above block of webservice is added yesterday for testing or trail as I am getting the above issue. And there is no line that is calling *gunicorn* in my mailman.cfg. Apart from that I tried to locate and see the content of the gunicorn.cfg file as below : *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.graceful_timeout = 30* Please confirm the time I have to change is *graceful_timeout *in *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I have never used or never known about this *gunicorn* but still running the service in production. Please help me and also suggest if I could provide you any more data from giving resolution. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#m_5710631741815235215_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jul 23, 2020 at 3:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:13 AM, Shashikanth Komandoor wrote: > > > Never mind please I am sending to you only instead of group as I am > sending you the production content along with the mail. > > I don't see anything there that can't be posted to the > mailman-users(a)mailman3.org list. If your concern is revealing the > support-tnvc.lsmgr.nic.in list id, just replace it with <list-id> or > list.example.com or similar. > > Messages sent to me personally rather than the list suffer many > problems. They are my absolute last priority, and I am only one person, > the collective knowledge of the list is greater. Also, at times I am off > line for several days or longer. > > Finally, there is no opportunity for other members of the community to > benefit from an off-list exchange. > > > When I am trying to browse one of my lists, I am getting "[ERROR] > > Error handling request /3.1/lists/support-tnvc.lsmgr.nic.in/archivers > > <http://support-tnvc.lsmgr.nic.in/archivers>" in the mailman.log and the > > full error message is in attachment. > > Try increasing your gunicorn worker timeout from the default 30 seconds. > I.e., add > > timeout = 90 > > to your gunicorn.cfg and restart gunicorn. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 years, 3 months

[MM3-users] I need professional help to get virtualenv Mailman3 installation running

by John Seifarth

Hello, I have been running Linux mailman2 servers for about 10 years, and sendmail/postfix servers for over 20 years. I have a client who wants to upgrade to Mailman 3 from their current Mailman2 system. I wanted to avoid the disruption of an upgrade, so I implemented a series of test servers with different names (leaving the mailman2 server in production at its historical address) running Ubuntu 18 and Ubuntu 20, using the mailman3 packages (3.1and 3.2 respectively). I sort of got it running with mailman 3.2 on Ubuntu 20, but couldn’t get Hyperkitty archiving to work. Plus the fact that mail bounce handling isn’t implemented prior to mailman 3.3.2, I decided to install the latest mailman version available in a venv environment, using the instructions at https://docs.mailman3.org/en/latest/install/virtualenv.html I followed the instructions carefully using the same paths, and tracked down and fixed errors as each step progressed. I finally set up a WSGI server according to the instructions, searched for and found (fragmentary) instructions for setting up the Apache configuration, started the mailman3 and mailman web services, and now have no errors in the /opt/mailman/web/logs files, the /var/log/apache files, and in syslog. But when I try to connect via the Web, I get the message "Server error An error occurred while processing your request.” in my browser. No other clues. I’m completely stuck, and I need help to conclude this rapidly, the client really needs the new service up and running ASAP. I’m at the limit of my competence. I’ve been learning Python on and off (insufficient available time), and I installed Django and ran the tutorials. I still am woefully unskilled in the subtleties of a complex Python project like Mailman/Posterious/Hyperkitty, and I really need the help of an expert who can log into the server and see for themselves where the problem(s) are, and fix them. What I need is an experienced Python programmer, who has installed, run, and upgraded venv mailman3 installations. Of course, I will pay for this expertise, and charge it to the end client. In other words, I will pay you directly, and then I will worry about getting paid myself later. I am ready to pay €60/h for your skills, paid directly to your bank account, after receipt of your invoice. It shouldn’t be all that much work, since everything has been installed according to instructions, I’m just not a good enough Python programmer to get all the parts to work together correctly. It’s important to note that the end client is an organisation of European political parties, the virtual machine running the Ubuntu 20 server is hosted at OVH in France. Thus the professional with whom I would work should preferably also be based in the EU, and subject to EU law. Practically speaking, if anyone is interested, please send me a direct email with your email address and phone number, and then we can discuss how to do this practically in terms of SSH access, passwords, etc. Thanks for taking the time to read this, and I hope some Python Mailman pro can come to my aid. John

4 years, 3 months

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Abhilash Raj

On Fri, Oct 27, 2017, at 02:39 AM, Simon Hanna wrote: > On 10/26/2017 11:51 PM, Abhilash Raj wrote: > > On Thu, Oct 26, 2017, at 11:23 AM, Andrew Hodder wrote: > >> I have an odd one, my Hyperkitty is functionally working fine (archived > >> several lists without issue, can login/out), however I must have done > >> something wrong during it's setup as it's layout is completely broken > >> (and > >> it keeps throwing Example.com up in the top-left corner). > > You need to change SITE_ID in your Django's configuration to point to > > your domain name you want to be show there. Default is set to > > `example.com` which corresponds to SITE_ID=1 in the Django's > > configuraiton. > > > > How to find the SITE_ID of your domain? > > > > This is rather no-so-nice right now, you will basically have to go to > > the admin console (/admin/) and login as admin. Then you visit > > `/admin/django_mailman3/maildomain/` and you should see your domain > > there. Clicking on it will how your it's id in URL bar, like > > /admin/django_mailman3/maildomain/2 or something. > > > > I understand this is rather difficult thing to do, there is an issue > > open to make this information visible in the UI. Ideally, SITE_ID is > > sequential, so if you have only one domain, it is most probably 2. > You shouldn't get it from maildomain but the real site instead which is > under the sites entry > /admin/sites/site/ Thank you for this correction, this is probably more accurate data. But since domains are tied to sites internally anyway, they both will probably have the same values. > > Also the default is actually 1 and not 2 Well, I didn't mean the default value. I meant that if example.com exists in the database, the next domain you create gets id sequentially, which would be 2 in this case. It is obviously not the best way to find out ID. > Django automatically creates a site with id 1 if the sites framework is > activated. > Only if you delete the existing entry and add another, you will get an > id of 2. Django automatically creates 'example.com' site with ID 1, that's true. There is no way to specify a default site at the startup time, to something other than 'example.com'. Anything you create after gets next sequential id. Either way, that is Django's internal semantics and I only mentioned as a stupid shortcut ;-) > Just editing will leave you with 1. > > as mentioned in the issue on gitlab, I think we should just drop the > SITE_ID or maybe only enable it for DEBUG==True Yeah, I agree it would make sense to not set a SITE_ID by default, that removes this extra step of finding and setting SITE_ID. > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years

[MM3-users] Re: Configuration variables in Docker

by Abhilash Raj

> On Apr 8, 2021, at 6:49 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > Hey there, we installed the latest Docker version of Mailman3 and it seems to work for now. But I have 2 problems with configuration: > > ## DJANGO_ALLOWED_HOSTS > > Here it says, that allowed hosts can be added: https://asynchronous.in/docker-mailman/web/ > > How de we add multiple hosts? Did I miss something? When we set 1 URL, everything works (with 2(!) Domains, since SERVE_FROM_DOMAIN is the first one). Is there a way I miss to input multiple hosts, that the variable is an array? We tried: > - DJANGO_ALLOWED_HOSTS=example1.com,example2.com > - DJANGO_ALLOWED_HOSTS='example1.com, example2.com' > - DJANGO_ALLOWED_HOSTS=example1.com example2.com > - DJANGO_ALLOWED_HOSTS=example1.com,\nexample2.com Multiple hosts aren’t allowed in the env var as you can already see from the config file that you added below. Although, comma separated multiple values are something we can add as an extension if you are willing to implement and create a Pull Request on the Github Repo. You have already found the place to make the change. If you want to add multiple hosts, you can override ALLOWED_HOSTS in your /opt/mailman/web/settings_local.py. > > And I think some more, but never works. The corresponding config file says: > > ALLOWED_HOSTS = [ > "localhost", # Archiving API from Mailman, keep it. > # "lists.your-domain.org", > # Add here all production URLs you may have. > "mailman-web", > "172.19.199.3", > os.environ.get('SERVE_FROM_DOMAIN'), > os.environ.get('DJANGO_ALLOWED_HOSTS'), > ] > > -> how is it possible to add an array for multiple Domains? > -> if not possible, shall we provide a fix that it is? > > ## FILTER_VHOST > > I want this variable to be true in my container. When I set it as a starting variable like the other configuration options, then the variable in the container seems to be set: > > <code> > # export | grep FILTER_VHOST= > declare -x FILTER_VHOST="True" > </code> > > But surely it still is set to false in mm-web-container: > > <code> > # cat settings.py | grep FILTER_VHOST > FILTER_VHOST = False > </code> > > -> is it ok to put the variable like that!? Not all variables are accepted as environment variables. Except the ones documented, all the Mailman settings would need to go in the configuration file mentioned above. > -> if not, how can it be done, that it is preserved on restarting the container? You do want to restart the container regardless of how you set it. Applications that are already running won’t pick up any dynamic changes you made in the environment of your shell after logging in. > -> if I see it right, it could be then something like: > <code> > FILTER_VHOST = os.environ.get('FILTER_VHOST_DOCKER'), This would work, except you need to provide a default value in the .get() call and the environment variable should be pre-pended with `MAILMAN_` instead of `_DOCKER` suffix. ``` FILTER_VHOST = os.environ.get(‘MAILMAN_FILTER_VHOST’, False) ``` You can open a Pull Request, this can also go into the images from next release. -- thanks, Abhilash Raj (maxking)

4 years, 7 months

[MM3-users] Re: Email verification

by Allan Hansen

They go out but are not received or found. The addresses are valid. I’m just looking for a way to help them over this hump. The error message indicates that ‘we’ can help. Yours, Allan Hansen hansen(a)rc.org > On Feb 9, 2020, at 9:54 , Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Sun, Feb 9, 2020, at 9:38 AM, Allan Hansen wrote: >> Thank you, Abhilash. >> Yes. People are getting these messages. I just got a message from one who had the issue. I asked her to try to sign in again and then she got the verification message. >> >> It’s just that some have issues, and I’d like to be able to help. > > Can you check your MTA logs to see if those confirmation emails were indeed sent out? > > It would help figure out of the email was never sent out or whether they didn't receive it. > >> Yours, >> >> Allan Hansen >> hansen(a)rc.org <mailto:hansen@rc.org> >> >> >> >>> On Feb 9, 2020, at 9:12 , Abhilash Raj <maxking(a)asynchronous.in <mailto:maxking@asynchronous.in>> wrote: >>> >>> >>> >>> On Sun, Feb 9, 2020, at 8:05 AM, Allan Hansen wrote: >>>> Some members cannot get past the email verification when they create >>>> their accounts. >>>> They insist that they have looked in their spam folders. Their email >>>> addresses they entered are correct - the are able to log into their >>>> accounts with the right email address. But they get the message saying >>>> that a confirmation message was sent and if they don’s see it to >>>> contact us. >>> >>> Is your Django configured to send out emails? >>> >>> https://docs.mailman3.org/en/latest/config-web.html#setting-up-email-requir… <https://docs.mailman3.org/en/latest/config-web.html#setting-up-email-requir…> >>> >>> >>>> >>>> 1. Who is ‘us’? My members are asking... >>>> 2. How do I help them? >>>> >>>> I tried subscribing them to a bogus list with pre-verified email, but >>>> that did not work, so both they and I are stuck. >>>> Tried finding help in archive, but did not see anything. >>>> >>>> Yours, >>>> >>>> Allan Hansen >>>> hansen(a)rc.org >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> _______________________________________________ >>> 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, 9 months

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

by Oliver Gräber

Hi, I also would like to have an answer to this. I was successful using the mailmanclient and the REST-API as described here: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… With this you have the same usecases as pistorius can handle in your python scripts Oli Am 23.07.24 um 22:17 schrieb Greg Newby: > Hi again folks. I have hundreds of lists to convert from MM2.1 to MM3, and > intend to write a Python program do this this rather than running commands > in mailman shell (and rather than running 'command()' functions in mailman > shell, if possible). > > However, when I write a simple Python program to run the types of commands > found in the Mailman docs, such as these > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>, > I get errors. This is a venv installation, following these instructions > <https://docs.mailman3.org/en/latest/install/virtualenv.html>. The Mailman3 > installation is working fine and I have a handful of lists in production > that I set up manually. > > Here's a very simple program, import-try1.py, just to create a list: > #!/opt/mailman/venv/bin/python3 > > from mailman.app.lifecycle import create_list > l = create_list('testlist2(a)lists.aaabbb.org') > > Here's the output I get (yes, the domain exists and already has lists - I'm > putting aaabbb instead of the actual domain name): > > ./import-try1.py > Traceback (most recent call last): > File "/opt/mailman/./import-try1.py", line 4, in <module> > l = create_list('testlist2(a)lists.aaabbb.org') > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/app/lifecycle.py", > line 74, in create_list > getUtility(IEmailValidator).validate(fqdn_listname) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", > line 180, in getUtility > raise ComponentLookupError(interface, name) > zope.interface.interfaces.ComponentLookupError: (<InterfaceClass > mailman.interfaces.address.IEmailValidator>, '') > > I get different errors with other sets of commands. The same commands work > fine from `mailman shell`, i.e., > > (venv) mailman@mail:~$ mailman shell > Welcome to the GNU Mailman3 shell on aaabbb.org > >>>> from mailman.app.lifecycle import create_list >>>> l = create_list('testlist2(a)lists.aaabbb.org') >>>> > Output from mailman info, with the passwords omitted: > > GNU Mailman 3.3.9 (Tom Sawyer) > Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] > config file: /etc/mailman3/mailman.cfg > db url: postgresql://mailman:secretaaabbb@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:reallysecretaaabbb > > I suspect I just need to either change the interpreter (1st line of my > program), or find the correct 'import' lines (I've tried numerous > variations; the above is the simplest example). Help will be appreciated! > Greg > _______________________________________________ > 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 o.graeber(a)jpberlin.de

1 year, 3 months

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

by Guillermo Hernandez (Oldno7)

On 9/8/21 17:56, Richard Rosner wrote: >> 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 have the apache24 and uwsgi working together. I did this way: For the apache24 part I decided to use the mod-wsgi (and uswgi binary). did a pip install mod-wsgi (with "mod_wsgi-express module-config" it shows the conf needed.) after that a pip install uwsgi In my systems the mailman3 files are located at /usr/local/mailman3, and the apache24 config path is /usr/local/etc/apache24 (I'm running FreeBSD) - Included these lines in the "loadmodule" part of /usr/local/etc/apache24/httpd.conf Watch out the correct path of your python ##### begin of added lines LoadModule wsgi_module "/usr/local/lib/python3.7/site-packages/mod_wsgi/server/mod_wsgi-py37.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty ##### end of added lines - Added this line in the correct places of my /usr/local/etc/apache24/extra/httpd-vhosts.conf (in the listen 80 and 443 servers) Include "/usr/local/mailman3/apache24.uwsgi.conf" ( my apache24.uwsgi.conf is copied below) Then all you have to do is a - service apache24 restart and initiate the uwsgi with a /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & (beware the "&" backgrounding it) ####### start of /usr/local/mailman3/uwsgi.ini # uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # Move to the directory wher the django files are. chdir = /usr/local/mailman3/ # Use the wsgi file provided with the django project. wsgi-file = wsgi.py # Setup default number of processes and threads per process. master = true process = 2 threads = 2 # Drop privielges and don't run as root. uid = www gid = www # Setup the django_q related worker processes. attach-daemon = ./manage.py qcluster # Setup the request log. req-logger = file://usr/local/mailman3/logs/uwsgi.log # Log cron seperately. logger = cron file://usr/local/mailman3/logs/uwsgi-cron.log log-route = cron uwsgi-cron # Log qcluster commands seperately. logger = qcluster file://usr/local/mailman3/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file://usr/local/mailman3/logs/uwsgi-error.log ####### end of /usr/local/mailman3/uwsgi.ini ####### start of /usr/local/mailman3/apache24.uwsgi.conf Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman3/static ######### # for hyperkitty Alias /static/admin /usr/local/mailman3/static/admin Alias /static/CACHE /usr/local/mailman3/static/CACHE Alias /static/django_extensions /usr/local/mailman3/static/django_extensions Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 Alias /static/rest_framework /usr/local/mailman3/static/rest_framework # for postorius Alias /static/postorius /usr/local/mailman3/static/postorius Alias /static/archives /usr/local/mailman3/static/postorius ##### ###ErrorLog /var/log/httpd/hyperkitty_error.log ###CustomLog /var/log/httpd/hyperkitty_access.log combined <Directory "/usr/local/mailman3/static"> Require all granted </Directory> ######## end of /usr/local/mailman3/apache24.uwsgi.conf

4 years, 3 months

[MM3-users] Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 11:45, Joel Lord wrote: > So I seem to have problems with both periodic AND size-triggered > digests. Size first, this is simpler. Just got one sent out, clearly > triggered by a new email getting added to the queued up messages, but > the setting for the list is the default 30KB and the digest came out at > 23.2 KB. Is it measuring the accumulated queue as size on disk > including metadata and filesystem block sizes or something, rather than > the size of what the emailed digest will be? The threshold is determined by the size in bytes of the MMDF format mailbox file in which the the messages for the digest are saved. This does not include metadata and is not affected by block sizes. It contains the raw messages with all headers and 8 bytes of message separators per message and a 'From ' line per message. Once the digest is triggered, the messages are configured into a digest message with boilerplate, a TOC and possibly a header and/or footer added. The messages themselves may be added as separate MIME message/rfc822 parts to a mime format digest or added as text to a plain format digest. Many headers are removed as the messages are added. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for what is kept. In addition any non text/plain parts in the message are not included in the plain format digest, but are replaced by notes that they have been removed. All this says that a MIME format may be larger or smaller than the threshold depending on the size of the removed headers vs. the added parts, and a plain text digest will probably be smaller if the messages have non text/plain parts, e.g. if content filtering doesn't collapse alternatives and leaves the text/html alternative part, this part will not be in a plain format digest. > Periodic is much more complicated, even to explain. I have the cron job > running nightly at 11:00 PM and it certainly seems to be working, except > for one really odd thing. The list also definitely has periodic digests > enabled in the web UI. This is a very bursty list, so it will go mad > with traffic for a few weeks and then will go mostly idle for a month or > so. The first digest of a burst is definitely size-triggered, but > pretty reliably it has the last few messages from the previous burst in > there. So the one I got today had three messages from today and one > message from May 4th. But that May 4th message should have gone out at > 11:00 PM on May 4th with the daily digest and then gotten flushed from > the pending digest queue, right? That's correct. Do you ever get periodic digests sent at 11:00 PM? If not, there is some issue either with configuration or something. If you get them sometimes, I don't know what could be wrong. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Mailserver Log entries following through mailman?

by Stephen J. Turnbull

Andreas Barth writes: > However, mailman doesn't have an internal id I can use to follow > the message (or at least, it doesn't transfer one to exim upon > delivery). Mailman does have an internal ID for each LTMP transaction, which is the queue file name. That is generated by hashing the message, the current time and something else so that should be unique enough for your purpose. I guess we could log that, but I'm not sure how that would benefit you. Returning it in the LMTP status may be possible, but it's not currently exposed to the LMTP runner which manages that transaction. > I can indeed use the user set message id for following mail. Then I don't see the problem. Identifying a particular message is what that is for. Unless you're getting a spew of repeats of a single message (which is certainly possible, but then I doubt that the problem you're solving is tracing a single instance of the spew!), that plus the timestamp should be enough to disambiguate most possible repeats. > However, I would prefer some internal id, and also to have > logged the IDs exim (or probably any other MTA) transmits upon I don't understand. MTAs don't explicitly transmit their internal IDs to the next hop; there's no provision for this in the SMTP (LMTP) protocol AFAICR. They can add it to their Received field, and they can log it themselves. In theory they can return it in the status message they pass back to the previous MTA upon acceptance, but I rarely recall seeing it done (Exchange does it, I think). And in any case this only works on your site, you're still going to have to fall back on some combination of message-id, author, and timestamp as goes from host to host. Please be more specific about how IDs are transmitted at your site, and be careful that different mechanisms have to be used on receipt and forwarding. > delivering the mails when handing the mails over to the MTA > again. (Probably in some format as "mailman-ID recepient MTA-id" so > that it's easy for me to grep for message if a user complains.) I guess we could do that for the outgoing MTA if it's present in the status message, but that's likely to be a lot of output unless all your subscribers are in the same domain. But there's no way to get it for the incoming MTA as far as I know, except maybe parsing it out of the Received chain. Besides the dubious existence of the relevant data, the lack of support in the SMTP and LMTP protocol means that every MTA, and some exceptional instances of each MTA (I'm pretty sure both Postfix and Exim4 support customizable status messages) would have to be supported individually by parsing it out of the status return or the Received chain, neither of which is standardized. This sounds like a lot of work for us for each MTA in use on the Internet. Steve

1 year, 11 months

[MM3-users] disable sign-ups

by Peter Münster

Hi, I would like to add new accounts only manually, the mailman3 site should not be open for sign-ups. So I've added this code to settings.py: --8<---------------cut here---------------start------------->8--- from allauth.account.adapter import DefaultAccountAdapter class MyAccountAdapter(DefaultAccountAdapter): def is_open_for_signup(self, request): return False ACCOUNT_ADAPTER = 'MyAccountAdapter' --8<---------------cut here---------------end--------------->8--- It seems to work, but the user experience is not optimal: the user can click on "Sign Up", and then gets to "Server Error (500)". This is the log: --8<---------------cut here---------------start------------->8--- ERROR 2018-01-31 21:53:47,116 6769 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 210, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 79, in dispatch **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 182, in dispatch if not self.is_open(): File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 191, in is_open return get_adapter(self.request).is_open_for_signup(self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 501, in get_adapter return import_attribute(app_settings.ADAPTER)(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/utils.py", line 150, in import_attribute pkg, attr = path.rsplit('.', 1) ValueError: need more than 1 value to unpack ERROR 2018-01-31 21:53:47,116 6769 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 34, in _wrapper return bound_func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 30, in bound_func return func.__get__(self, type(self))(*args2, **kwargs2) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 210, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 79, in dispatch **kwargs) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 182, in dispatch if not self.is_open(): File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/views.py", line 191, in is_open return get_adapter(self.request).is_open_for_signup(self.request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/account/adapter.py", line 501, in get_adapter return import_attribute(app_settings.ADAPTER)(request) File "/usr/lib/python2.7/site-packages/django_allauth-0.34.0-py2.7.egg/allauth/utils.py", line 150, in import_attribute pkg, attr = path.rsplit('.', 1) ValueError: need more than 1 value to unpack --8<---------------cut here---------------end--------------->8--- Do you have any hints, how to avoid such errors please? TIA for any help, -- Peter

7 years, 9 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, Unfortunately the provided options didn't work out either: Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the ************* mailing list >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.py", line 578, in confirm workflow.restore() File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 142, in restore raise LookupError(self.token) LookupError: 4d6b4b11266c7332684c5a492eb3f92c531f761b I noticed that the mail address was also listed as a non-member. After deleting it there, I could not accept the subscription either. Next, I have rejected the subscription and added it using the mass subscription option in the WebUI. I'll monitor if such cases will happen again. Thanks,Eric On Saturday, January 16, 2021, 06:05:19 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/16/21 7:49 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > I can't find any log entry which indicate a problem with this subscription request. > The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. It is unclear and confusing, but the requests are not in the _request table. See <https://gitlab.com/mailman/mailman/-/issues/768#note_415536043>. So this is normal. > The token is found in the pended table: > > +-----+------------------------------------------+---------------------+ > | id | token | expiration_date | > +-----+------------------------------------------+---------------------+ > | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | > +-----+------------------------------------------+---------------------+ > > These are the relevant entries in the pendedkeyvalue table: > +------+--------------+-------------------------------------+-----------+ > | id | key | value | pended_id | > +------+--------------+-------------------------------------+-----------+ > | 1130 | type | subscription | 115 | > | 1131 | list_id | "********************" | 115 | > | 1132 | email | "***********************@*********" | 115 | > | 1133 | display_name | "" | 115 | > | 1134 | when | "2021-01-06T16:17:38" | 115 | > | 1135 | token_owner | "moderator" | 115 | > +------+--------------+-------------------------------------+-----------+ > > Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Adding to the _request table won't help. Try confirming by emailing listname-confirm+4d6b4b11266c7332684c5a492eb3f92c531f761b(a)list.domain You could also try confirming via mailman shell 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 >>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') Traceback (most recent call last): File "<console>", line 1, in <module> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.3b1-py3.7.egg/mailman/app/subscriptions.py", line 570, in confirm raise LookupError LookupError In my case, I get the LookupError because the token doesn't exist, but I think it should work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 21:38, Mark Sapiro escribió: > On 4/1/23 12:22, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> El 1/4/23 a las 21:14, Mark Sapiro escribió: >>> >>> If you had completely stopped Mailman core and then started it, lmtp >>> runner should have started. What are the complete log messages from >>> mailman.log following the start? >>> >> I sent them before > > > And there is no `lmtp runner started` message in the log, so it isn't > being started at all. > > >>> What does `mailman conf -s runner.lmtp` show? >>> >> Here it is: >> >> root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c >> "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg >> conf -s runner.lmtp" >> [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner >> [runner.lmtp] instances: 1 >> [runner.lmtp] max_restarts: 10 >> [runner.lmtp] path: >> [runner.lmtp] sleep_time: 1s >> [runner.lmtp] start: yes > > > This says the runner should be started. That is the command that > starts Mailman? is it Yes, indeed. > > /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C > /usr/local/mailman3/var/etc/mailman.cfg start" > > or is it something that perhaps uses a different config. > > What happens if you do > > /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C > /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" > I get the same error as before: root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/runner -C /usr/local/mailman3/var/etc/mailman.cfg -v -r lmtp" Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Apr 01 21:40:36 2023 (12396) Using selector: KqueueSelector Traceback (most recent call last): File "/usr/local/bin/runner", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.8', 'console_scripts', 'runner')()) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1053, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.9/site-packages/click/core.py", line 754, in invoke return __callback(*args, **kwargs) File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/local/lib/python3.9/site-packages/mailman/bin/runner.py", line 70, in make_runner return runner_class(name, slice) File "/usr/local/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 295, in __init__ self.lmtp = LMTPController(LMTPHandler(), hostname=hostname, port=port) File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 417, in __init__ self._localhost = get_localhost() File "/usr/local/lib/python3.9/site-packages/aiosmtpd/controller.py", line 66, in get_localhost with makesock(AF_INET6, SOCK_STREAM) as sock: File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 7 months

[MM3-users] Re: Mailman 3 Status Update Please?

by tlhackque

On 21-Jul-17 22:58, Barry Warsaw wrote: > > One big project that I’d love to see gain more traction is Lemme, our authenticating REST proxy. We just haven’t had much collective resources to spend working on it. > > https://gitlab.com/mailman/lemme > > Cheers, > -Barry > It's not obvious why this is a 'big project', or why it needs to be a separate proxy. Modularity can go too far. The architectural problem with a separate proxy that provides separation of privilege is that the proxy has to be kept in sync with the core - add an object or property to the core, and the proxy has to be updated. You'll end up mirroring the decoding and structure of the core in the proxy in order to figure out what the access rights are. Or the proxy does just authentication and passes on a token used for authorization - in which case the proxy isn't adding much value. You already have a database of users & passwords - adding another database for the proxy is not going to simplify the admin's life. In addition, as the recent issues indicate, the REST API already has scaling problems - adding a proxy in the path will exacerbate those. The REST API supports Basic authentication - which is adequate for identifying users and delivering passwords, if over an encrypted link (e.g. TLS, which is easy to set up with standard libraries). Personally, I prefer client certificates as an identifier - which again, your TLS library will validate. They can be mapped to a username easily - just add the certificate's issuer and subject to the user data. TLS will handle verification & revocation (CRL and/or OCSP with your "trusted authorities" bundle or path). Webservers handle this, and can be used as a model. (E.g. apache's mod_ssl). What's missing is a STARTTLS-like mechanism in the REST API, a privileges field in the user and/or list databases, and suitable checks in the API actions. Even that can be simplified by requiring TLS for all connections, even local ones. I prefer that approach, as it reduces bugs and corner cases. For backward compatibility, a global configuration setting for TLS on or off can be added. Alternatively, you can use a webserver as a reverse proxy & let it handle the authentication. You already do this with DJango. The drawback is that the path from the proxy to the mailman REST server needs to be protected or trusted - a local socket on the same machine as the webserver is one approach. But that limits configurations. Or you can use TLS from the webserver to the API - but setting that up (and documenting it for users) is more work - and at that point, you've done 95% of the work for a direct TLS connection. (The advantage is where the webserver provides single signon authentication.) So I'd avoid this path & implement TLS in the REST server. Either way, the major work is (or should be) authorization tests in the core, with a touch of mapping an authenticated user to her(his) capabilities (for a list) in the database. Not a s"big" separate project. Why have you come to a different conclusion?

8 years, 3 months

[MM3-users] Re: An issue with the postfix_domains directory creation and the mailman start command.

by Keith Christian

Ron, I ultimately have these layout files, due to what I've seen in the documentation. Not sure if these conflict with each other or if I need to create directories, these are in the /etc/mailman3/mailman.cfg listing below. layout: here layout: fhs layout: local "Mailman info" to verify the mailman.cfg file in use: (venv) [mailman3@someserver ~]$ mailman info|cat -n 1 GNU Mailman 3.3.9 (Tom Sawyer) 2 Python 3.9.19 (main, May 16 2024, 08:45:40) 3 [GCC 8.5.0 20210514 (Red Hat 8.5.0-22)] 4 config file: /etc/mailman3/mailman.cfg 5 db url: postgresql://mailman3:not_the_password@localhost:5432/mailman3 6 devmode: DISABLED 7 REST root url: http://localhost:8001/3.1/ 8 REST credentials: restadmin:restpass Here is the /etc/mailman3/mailman.cfg file: (venv) [mailman3@someserver ~]$ cat -n /etc/mailman3/mailman.cfg 1 # /etc/mailman3/mailman.cfg 2 [paths.here] 3 var_dir: /opt/mailman3/mm/var 4 5 [mailman] 6 layout: here 7 layout: fhs 8 layout: local 9 # This address is the "site owner" address. Certain messages which must be 10 # delivered to a human, but which can't be delivered to a list owner (e.g. a 11 # bounce from a list owner), will be sent to this address. It should point to 12 # a human. 13 site_owner: user(a)example.com 14 15 [database] 16 class: mailman.database.postgresql.PostgreSQLDatabase 17 #url: postgresql://mailman:MYPASSWORD@localhost/mailman 18 url: postgresql://mailman3:not_the_password@localhost:5432/mailman3 19 20 [archiver.prototype] 21 enable: yes 22 23 # For the HyperKitty archiver. 24 [archiver.hyperkitty] 25 class: mailman_hyperkitty.Archiver 26 enable: yes 27 configuration: /etc/mailman3/mailman-hyperkitty.cfg 28 29 [shell] 30 history_file: $var_dir/history.py 31 32 [mta] 33 verp_confirmations: yes 34 verp_personalized_deliveries: yes 35 verp_delivery_interval: 1 36 On Wed, Jul 10, 2024 at 1:40 PM Ron <admin(a)bclug.ca> wrote: > > On 2024-07-10 08:48, Keith Christian via Mailman-users wrote: > > > 4 [mailman3@somehost ~]$ sudo ls -l > > /opt/mailman3/mm/var/data/postfix_domains > > 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': > > No such file or directory > > 6 [mailman3@somehost ~]$ ls -dl/opt/mailman3/mm/var/data/ > > 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 > > /opt/mailman3/mm/var/data/ > > > > What should I do about lines 4-7? Thought it might be a permissions > > issue but it's owned by the correct user. > > My guess would be that mailman is using a different location for storing > these files (aliases, domains, etc.) > > > One could search the system for where (if) the files were created with > something like: > > find / -name "postfix_domains" > > > > Another (better?) thought would be to compare the [paths] pointed to by > the "layout: ..." in /etc/mailman3/mailman.cfg to ensure it's pointing > where you expect (in this case, /opt/mailman3/mm/var/data for data_dir). > > > As user mailman, running: > > mailman conf > > to double check the "layout: ..." that's in use. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to keith1christian(a)gmail.com

1 year, 3 months

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

by paul＠arenson.org

Results of my redoing my tests following Mark’s comments. A) Thoughts before the tests B) The tests C) Summary A) Thoughts before summarizing tests. 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. B) THE TESTS I was testing too many variables so, to simplify things, I made my settings as follows 1) Subscription—> Confirm 2) Message Acceptance—> Default processing (so only members may post) 3) Testing Procesure I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… <https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres…> Comment: This is fastest. User can immediately send and receive. 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. Comment This worked fine. C) Summary 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. What comes back is the below. a) Isn’t there a better way to unsubscribe by email? b) And how about a way to remove their account itself? The results of your email command are provided below. - Original message details: From: Paul Subscribe <tokyosubscribe(a)icloud.com <mailto:tokyosubscribe@icloud.com>> Subject: help Date: Wed, 18 Sep 2019 01:33:43 -0000 Message-ID: <e46a43ec-e7dd-4846-94b1-d899ea626f53(a)me.com <mailto:e46a43ec-e7dd-4846-94b1-d899ea626f53@me.com>> - Results: Ignoring non-text/plain MIME parts confirm - Confirm a subscription request. echo - Echo back your arguments. end - Stop processing commands. help - Get help about available email commands. join - Join this mailing list. leave - Leave this mailing list. stop - An alias for 'end’. Thanks!!!!

6 years, 1 month

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

by Stephen J. Turnbull

Guillermo Hernandez (Oldno7) via Mailman-users writes: > But� I'm talking about a moderator can put a member mails in hold when > it is marked to accept. To prevent putting more gas in the fire. Not sure what you want here. I don't see how this is supposed to work -- if a subscriber is set to accept, the moderator will never see the posts until they're distributed to the subscribers. But that inspires a short rant ;-) a little about the implied feature request. First let me point out that there are a lot of lists out there where the owner is relatively laissez faire, and some moderators are a lot more activist. In the modern environment, it turns out to be important for many lists to vet new subscribers' first posts, and moderators basically function to give prompt response to non-spam first posts. So I don't want to just give moderators the same privileges as owners here, because they'll impose restrictions that the owner doesn't want, and the current low-privilege moderators seem to work just fine for a lot of lists. I don't object in principle to allowing *owners* to give moderators more privileges. On the one hand, it's often case that owners trust their colleagues with owner-level privileges. So that's an option we already have -- no moderators, all owners. So maybe you *don't* like the all-owners strategy (and it's obvious why many owners won't, no need to bend my ear on that). The design problem is that there are a lot of capabilities, and it's not obvious to me that there's a specific collection of them that owners want to grant to their moderators. Maybe we can get rough consensus on that list, and then it's not hard to get to working code. I'm not going to start the conversation here (I don't personally have such a list), but I'm happy to listen, and provide advice to anyone who wants to submit a merge request. If there isn't consensus, then we're going to need a framework for moderator capability management so that owners can pick and choose. That's something I'd be interested in working on myself if there's user demand for it. (There's a long list of things I'm interested in, and not a lot of work actually done recently, so no promises. But it could happen! ;-) It could also end up on the GSoC idea list for next year. :-) Another capability I have an interest in is closing replies to specific posts and to whole threads. Again, that's going to require some thinking about the administration interface. It's easy enough to do the basics if there's an archive (allow the moderator to click on a post, and either disable replies to that post or replies to all thread descendents), but I can imagine lots of related capabilities (reenable replies for "sane" subthreads, automatic expiration of the restriction, ...). And of course all of the above (except unconditionally granting moderators the capability to apply a HOLD to users) requires REST updates, I suspect. As always: code contributions welcome. Steve

4 years, 1 month

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

by Mark Sapiro

On 10/12/19 8:55 PM, Paul Arenson wrote: > I have found that my users in the discussion list are creating their own topics rather than using the existing ones, so decided to make it a read-only list and use WordPress moderated comments. Since I do not have the original settings for READ ONLY (this is a hosted version), I want to make sure that these are correct. Can someone comment. I'm guessing what you want and what you are saying First, I think you are saying your issue is that your users are using HyperKitty as a web forum and when replying to a message in an existing thread instead of using the 'reply' action on that message, they use the Start a new thread button. Is that really what you are saying? > MOST IMPORTANT—> What setting makes it a discussion list as opposed to read only? If by "read only" you mean the "Announce only mailing list style" as opposed to the "Ordinary discussion mailing list style" the only difference is that for the Announce only style the list attribute allow_list_posts is False and for the Discussion style, it's True. This is the setting in Postorius -> Settings -> Alter Messages -> Include the list post header an all it does is include or not include the List-Post: header in mail from the list. > ALTER MESSAGES > ----------------------- > Filter content Now YES > > Collapse Alternatives Now yes > > Convert html to plain text Now NO Above are not relevant. > Anonymous NOW YES Are you sure you want this. What it does is replace the From: address with the list posting address and removes all other headers that could aid in identifying the poster. It is intended for lists discussing things such as domestic abuse where people may want to be able to post anonymously. > Include RFC2369 headers Now Yes OK, but not relevant > Include the list post header Now Yes This is what the announce style will set to No. > Reply Goes to List Now No munging > > Pipeline Default > > > > DMARC MITIFGATIONS > ----------------------- > > Replace From with list address > > DMARC mitigate unconditionally Now NO > > > MESSAGE ACCEPTANCE > ----------------------- > > Require Explicit Destination Yes > > Administrivia YES The above are OK, but again not relevan to what I think you're asking. > > Default action to take when a member posts to the list Hold for moderation > > > Default action to take when a member posts to the list Hold for moderation Basically these two settings will hold all posts for moderator action, however if the user has a moderation setting other thgan list default, they won't apply. > OTHER? See the FAQ at <https://wiki.list.org/x/4030685>. This is written for Mailman 2.1 and older and some of the settings aren't relevant or exactly the same in Mailman 3, but it may help. On the other hand, if I'm not understanding what you want, please clarify. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

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

by Greg Newby

Thanks for this, Odhiambo. Unfortunately it doesn't address my situation. See below: On Tue, Oct 15, 2024 at 3:21 AM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Mon, Oct 14, 2024 at 10:43 PM Greg Newby via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Hi friends. >> >> I'm now getting a 500 server error upon signing up a new username on the >> web-based front end. The username is created in the back end, but the >> verification email does not get sent. >> >> This is GNU Mailman 3.3.9 (Tom Sawyer), venv, Ubuntu 24.04LTS, PostgreSQL, >> Postfix >> >> 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> >> > ^^^^ Note the problem isn't the "From:" address. That is being correctly configured from mailman-web.py and settings.py via the variables below. The problem is it's going "To:" root@localhost. I don't know why this is happening - shouldn't it be going to redacted(a)gmail.com? Also, based on settings below shouldn't this be From: postorius(a)lists.domain.tld not From: root(a)lists.domain.tld? More: > >> lists.domain.tld is the domain for Mailman3. I don't know why it's trying >> to send email from root@. >> >> I've seen places where 'localhost' appears in the Mailman settings >> (settings.py, mailman.cfg, mailman-web.py), and tried changing them to the >> host's FQDN and restarting mailman3 and mailman3-web, but the problem >> persists. >> > > Find and fix these values to what they should be as explained. > > # The sender of emails from Django such as address confirmation requests. > # Set this to a valid email address. > DEFAULT_FROM_EMAIL = 'johndoe(a)domain.name' > > # The sender of error messages from Django. Set this to a valid email > # address. > SERVER_EMAIL = 'johndoe(a)domain.name' > > I use listmaster(a)lists.domain.name in my servers. > In the default files via the venv installation, these were already set properly: EMAILNAME='lists.domain.tld' <-- I set this myself These were default in settings.py and mailman-web.py: DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) SERVER_EMAIL = 'root@{}'.format(EMAILNAME) I set them explicitly to postorius(a)lists.domain.tld and root(a)lists.domain.tld and restarted mailman and mailman web, and this did not change the problem with the server error and mail log entries above. > I am not sure what files on your server contains them in your server. > > And while at it, also fix the site_owner: email in mailman.cfg. > That was already set to my email address, and I do correctly get site emails, such as cron output. Further guidance would be appreciated. ~ Greg

1 year

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

by Stephen J. Turnbull

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

7 years

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello, I'm newbie in centos 7 and I might need a little bit of help understanding (filesystem hierarchy standard) layout, I don't know about it. How do I check if I have mailman v2 installed??? How do I change the layout to "dev"?? Thank you El mar., 11 jul. 2017 a las 15:13, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > Looks like you are using the fhs (filesystem hierarchy standard) layout; > is that what you intend? I would suggest changing the layout to "dev" for > testing purposes. This will use your mailman.cfg/../.. as the var directory. > > Is it possible you also have mailman v2 installed via rpms? > > -Kyle > > On Tue, Jul 11, 2017 at 3:41 PM, Rafael Mora <rafael.mora.guti(a)gmail.com> > wrote: > >> Hello, >> >> Here it's mailman info: >> [root@localhost bin]# ./mailman info >> GNU Mailman 3.2.0a1 (La Villa Strangiato) >> Python 3.6.0 (default, Jul 7 2017, 11:59:56) >> [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] >> config file: /etc/mailman.cfg >> db url: sqlite:////var/lib/mailman/data/mailman.db >> devmode: DISABLED >> REST root url: http://localhost:8001/3.1/ >> REST credentials: restadmin:restpass >> >> >> Here it's mailman conf: >> [root@localhost bin]# ./mailman conf >> [antispam] header_checks: >> [antispam] jump_chain: hold >> [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive >> [archiver.mail_archive] clobber_date: maybe >> [archiver.mail_archive] clobber_skew: 1d >> [archiver.mail_archive] configuration: python:mailman.config.mail_archive >> [archiver.mail_archive] enable: no >> [archiver.master] class: >> [archiver.master] clobber_date: maybe >> [archiver.master] clobber_skew: 1d >> [archiver.master] configuration: changeme >> [archiver.master] enable: no >> [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc >> [archiver.mhonarc] clobber_date: maybe >> [archiver.mhonarc] clobber_skew: 1d >> [archiver.mhonarc] configuration: python:mailman.config.mhonarc >> [archiver.mhonarc] enable: no >> [archiver.prototype] class: mailman.archiving.prototype.Prototype >> [archiver.prototype] clobber_date: maybe >> [archiver.prototype] clobber_skew: 1d >> [archiver.prototype] configuration: changeme >> [archiver.prototype] enable: no >> [bounces] register_bounces_every: 15m >> [database] class: mailman.database.sqlite.SQLiteDatabase >> [database] debug: no >> [database] url: sqlite:///$DATA_DIR/mailman.db >> [devmode] enabled: no >> [devmode] recipient: >> [devmode] testing: no >> [devmode] wait: 60s >> [digests] mime_digest_keep_headers: >> Date From To Cc Subject Message-ID Keywords >> In-Reply-To References Content-Type MIME-Version >> Content-Transfer-Encoding Precedence Reply-To >> Message List-Post >> [digests] plain_digest_keep_headers: >> Message Date From >> Subject To Cc >> Message-ID Keywords >> Content-Type >> [dmarc] cache_lifetime: 7d >> [dmarc] org_domain_data_url: >> https://publicsuffix.org/list/public_suffix_list.dat >> [dmarc] resolver_lifetime: 5s >> [dmarc] resolver_timeout: 3s >> [language.ar] charset: utf-8 >> [language.ar] description: Arabic >> [language.ar] enabled: yes >> [language.ast] charset: iso-8859-1 >> [language.ast] description: Asturian >> [language.ast] enabled: yes >> [language.ca] charset: utf-8 >> [language.ca] description: Catalan >> [language.ca] enabled: yes >> [language.cs] charset: iso-8859-2 >> [language.cs] description: Czech >> [language.cs] enabled: yes >> [language.da] charset: iso-8859-1 >> [language.da] description: Danish >> [language.da] enabled: yes >> [language.de] charset: iso-8859-1 >> [language.de] description: German >> [language.de] enabled: yes >> [language.el] charset: iso-8859-7 >> [language.el] description: Greek >> [language.el] enabled: yes >> [language.es] charset: iso-8859-1 >> [language.es] description: Spanish >> [language.es] enabled: yes >> [language.et] charset: iso-8859-15 >> [language.et] description: Estonian >> [language.et] enabled: yes >> [language.eu] charset: iso-8859-15 >> [language.eu] description: Euskara >> [language.eu] enabled: yes >> [language.fi] charset: iso-8859-1 >> [language.fi] description: Finnish >> [language.fi] enabled: yes >> [language.fr] charset: iso-8859-1 >> [language.fr] description: French >> [language.fr] enabled: yes >> [language.gl] charset: utf-8 >> [language.gl] description: Galician >> [language.gl] enabled: yes >> [language.he] charset: utf-8 >> [language.he] description: Hebrew >> [language.he] enabled: yes >> [language.hr] charset: iso-8859-2 >> [language.hr] description: Croatian >> [language.hr] enabled: yes >> [language.hu] charset: iso-8859-2 >> [language.hu] description: Hungarian >> [language.hu] enabled: yes >> [language.ia] charset: iso-8859-15 >> [language.ia] description: Interlingua >> [language.ia] enabled: yes >> [language.it] charset: iso-8859-1 >> [language.it] description: Italian >> [language.it] enabled: yes >> [language.ja] charset: euc-jp >> [language.ja] description: Japanese >> [language.ja] enabled: yes >> [language.ko] charset: euc-kr >> [language.ko] description: Korean >> [language.ko] enabled: yes >> [language.lt] charset: iso-8859-13 >> [language.lt] description: Lithuanian >> [language.lt] enabled: yes >> [language.nl] charset: iso-8859-1 >> [language.nl] description: Dutch >> [language.nl] enabled: yes >> [language.no] charset: iso-8859-1 >> [language.no] description: Norwegian >> [language.no] enabled: yes >> [language.pl] charset: iso-8859-2 >> [language.pl] description: Polish >> [language.pl] enabled: yes >> [language.pt] charset: iso-8859-1 >> [language.pt] description: Protuguese >> [language.pt] enabled: yes >> [language.pt_BR] charset: iso-8859-1 >> [language.pt_BR] description: Protuguese (Brazil) >> [language.pt_BR] enabled: yes >> [language.ro] charset: iso-8859-2 >> [language.ro] description: Romanian >> [language.ro] enabled: yes >> [language.ru] charset: koi8-r >> [language.ru] description: Russian >> [language.ru] enabled: yes >> [language.sk] charset: utf-8 >> [language.sk] description: Slovak >> [language.sk] enabled: yes >> [language.sl] charset: iso-8859-2 >> [language.sl] description: Slovenian >> [language.sl] enabled: yes >> [language.sr] charset: utf-8 >> [language.sr] description: Serbian >> [language.sr] enabled: yes >> [language.sv] charset: iso-8859-1 >> [language.sv] description: Swedish >> [language.sv] enabled: yes >> [language.tr] charset: iso-8859-9 >> [language.tr] description: Turkish >> [language.tr] enabled: yes >> [language.uk] charset: utf-8 >> [language.uk] description: Ukrainian >> [language.uk] enabled: yes >> [language.vi] charset: utf-8 >> [language.vi] description: Vietnamese >> [language.vi] enabled: yes >> [language.zh_CN] charset: utf-8 >> [language.zh_CN] description: Chinese >> [language.zh_CN] enabled: yes >> [language.zh_TW] charset: utf-8 >> [language.zh_TW] description: Chinese (Taiwan) >> [language.zh_TW] enabled: yes >> [logging.archiver] datefmt: %b %d %H:%M:%S %Y >> [logging.archiver] format: %(asctime)s (%(process)d) %(message)s >> [logging.archiver] level: info >> [logging.archiver] path: mailman.log >> [logging.archiver] propagate: no >> [logging.bounce] datefmt: %b %d %H:%M:%S %Y >> [logging.bounce] format: %(asctime)s (%(process)d) %(message)s >> [logging.bounce] level: info >> [logging.bounce] path: bounce.log >> [logging.bounce] propagate: no >> [logging.config] datefmt: %b %d %H:%M:%S %Y >> [logging.config] format: %(asctime)s (%(process)d) %(message)s >> [logging.config] level: info >> [logging.config] path: mailman.log >> [logging.config] propagate: no >> [logging.database] datefmt: %b %d %H:%M:%S %Y >> [logging.database] format: %(asctime)s (%(process)d) %(message)s >> [logging.database] level: warn >> [logging.database] path: mailman.log >> [logging.database] propagate: no >> [logging.debug] datefmt: %b %d %H:%M:%S %Y >> [logging.debug] format: %(asctime)s (%(process)d) %(message)s >> [logging.debug] level: info >> [logging.debug] path: debug.log >> [logging.debug] propagate: no >> [logging.error] datefmt: %b %d %H:%M:%S %Y >> [logging.error] format: %(asctime)s (%(process)d) %(message)s >> [logging.error] level: info >> [logging.error] path: mailman.log >> [logging.error] propagate: no >> [logging.fromusenet] datefmt: %b %d %H:%M:%S %Y >> [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s >> [logging.fromusenet] level: info >> [logging.fromusenet] path: mailman.log >> [logging.fromusenet] propagate: no >> [logging.http] datefmt: %b %d %H:%M:%S %Y >> [logging.http] format: %(asctime)s (%(process)d) %(message)s >> [logging.http] level: info >> [logging.http] path: mailman.log >> [logging.http] propagate: no >> [logging.locks] datefmt: %b %d %H:%M:%S %Y >> [logging.locks] format: %(asctime)s (%(process)d) %(message)s >> [logging.locks] level: info >> [logging.locks] path: mailman.log >> [logging.locks] propagate: no >> [logging.mischief] datefmt: %b %d %H:%M:%S %Y >> [logging.mischief] format: %(asctime)s (%(process)d) %(message)s >> [logging.mischief] level: info >> [logging.mischief] path: mailman.log >> [logging.mischief] propagate: no >> [logging.root] datefmt: %b %d %H:%M:%S %Y >> [logging.root] format: %(asctime)s (%(process)d) %(message)s >> [logging.root] level: info >> [logging.root] path: mailman.log >> [logging.root] propagate: no >> [logging.runner] datefmt: %b %d %H:%M:%S %Y >> [logging.runner] format: %(asctime)s (%(process)d) %(message)s >> [logging.runner] level: info >> [logging.runner] path: mailman.log >> [logging.runner] propagate: no >> [logging.smtp] datefmt: %b %d %H:%M:%S %Y >> [logging.smtp] every: $msgid smtp to $listname for $recip recips, >> completed >> in $time seconds >> [logging.smtp] failure: $msgid delivery to $recip failed with code >> $smtpcode, $smtpmsg >> [logging.smtp] format: %(asctime)s (%(process)d) %(message)s >> [logging.smtp] level: info >> [logging.smtp] path: smtp.log >> [logging.smtp] propagate: no >> [logging.smtp] refused: $msgid post to $listname from $sender, $size >> bytes, >> $refused failures >> [logging.smtp] success: $msgid post to $listname from $sender, $size bytes >> [logging.subscribe] datefmt: %b %d %H:%M:%S %Y >> [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s >> [logging.subscribe] level: info >> [logging.subscribe] path: mailman.log >> [logging.subscribe] propagate: no >> [logging.vette] datefmt: %b %d %H:%M:%S %Y >> [logging.vette] format: %(asctime)s (%(process)d) %(message)s >> [logging.vette] level: info >> [logging.vette] path: mailman.log >> [logging.vette] propagate: no >> [mailman] cache_life: 7d >> [mailman] default_language: en >> [mailman] email_commands_max_lines: 10 >> [mailman] filtered_messages_are_preservable: no >> [mailman] html_to_plain_text_command: /usr/bin/lynx -dump $filename >> [mailman] layout: fhs >> [mailman] listname_chars: [-_.0-9a-z] >> [mailman] noreply_address: noreply >> [mailman] pending_request_life: 3d >> [mailman] post_hook: >> [mailman] pre_hook: >> [mailman] sender_headers: from from_ reply-to sender >> [mailman] site_owner: changeme(a)example.com >> [mta] configuration: python:mailman.config.postfix >> [mta] delivery_retry_period: 5d >> [mta] incoming: mailman.mta.postfix.LMTP >> [mta] lmtp_host: 127.0.0.1 # IP where Mailman should listen for >> emails from MTA >> [mta] lmtp_port: 8024 >> [mta] max_autoresponses_per_day: 10 >> [mta] max_delivery_threads: 0 >> [mta] max_recipients: 500 >> [mta] max_sessions_per_connection: 0 >> [mta] outgoing: mailman.mta.deliver.deliver >> [mta] remove_dkim_headers: no >> [mta] smtp_host: 127.0.0.1 # IP Where MTA is listening for >> emails >> [mta] smtp_pass: >> [mta] smtp_port: 25 >> [mta] smtp_user: >> [mta] verp_confirm_format: $address+$cookie >> [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$ >> [mta] verp_confirmations: no >> [mta] verp_delimiter: + >> [mta] verp_delivery_interval: 0 >> [mta] verp_format: ${bounces}+${local}=${domain} >> [mta] verp_personalized_deliveries: no >> [mta] verp_probe_format: $bounces+$token@$domain >> [mta] verp_probe_regexp: ^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$ >> [mta] verp_probes: no >> [mta] verp_regexp: >> ^(?P<bounces>[^+]+?)\+(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ >> [nntp] host: >> [nntp] password: >> [nntp] port: >> [nntp] remove_headers: >> nntp-posting-host nntp-posting-date x-trace >> x-complaints-to xref date-received posted >> posting-version relay-version received >> [nntp] rewrite_duplicate_headers: >> To X-Original-To >> CC X-Original-CC >> Content-Transfer-Encoding X-Original-Content-Transfer-Encoding >> MIME-Version X-MIME-Version >> [nntp] user: >> [passwords] configuration: python:mailman.config.passlib >> [passwords] password_length: 8 >> [shell] banner: Welcome to the GNU Mailman shell >> [shell] history_file: >> [shell] prompt: >>> >> [shell] use_ipython: no >> [styles] default: legacy-default >> [styles] paths: >> mailman.styles >> [webservice] admin_pass: restpass >> [webservice] admin_user: restadmin >> [webservice] api_version: 3.1 >> [webservice] hostname: localhost >> [webservice] port: 8001 >> [webservice] show_tracebacks: yes >> [webservice] use_https: no >> >> >> What do you suggest? Thank you >> >> El mar., 11 jul. 2017 a las 14:31, Simon Hanna (< >> simon.hanna(a)serve-me.info>) >> escribió: >> >> > Below is how I would recommend to run Mailman for production using a >> > virtualenv >> > >> > # useradd -r -m -d /var/lib/mailman mailman >> > >> > # su - mailman >> > >> > >> > $ python3 -m venv env >> > $ source env/bin/activate >> > $ pip install mailman >> > $ mailman info >> > >> > Now you should have a working configuration in /var/lib/mailman/var/ >> > >> > to run mailman you don't need to activate the virtualenv, just use the >> > executable /var/lib/mailman/env/bin/mailman >> > >> > cheers, >> > Simon >> > _______________________________________________ >> > 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/ >> > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 3 months

[MM3-users] Re: Users, members, accounts and subscribers

by Cameron Smith

Excellent = explanation. Thank you Stephen. On = 2017.08.20, at 19:41 , Stephen J. Turnbull = <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: Cameron Smith = writes: In an attempt to introduce a = friend to MailMan3, I had her subscribe to a couple of lists that I = set up and we exchanged a few messages via the email = interface. Then I introduced her to the web interface and we were = both confused when she could not log-in/sign-in and was told that = her email address was not recognized. In theory = we could recognize addresses, and tell the user that the address is = not associated with an account. This might not be a bad idea, = but in theory it could be used by spammers to confirm that accounts = are good ones. What we can do right away is to add a generic = statement to the sign in screen that "addresses that are not linked = to accounts and presented along with a valid password will be not be = recognized". It was only later that I = realized that while she was a subscriber, she hadn=E2=80=99t yet = signed up for an account. Yes, that will happen in = some cases, depending on how the subscription was created. The = solution is simple: create an account via the web interface, and link = the address (and therefore subscriptions using that address) to the = account. What is the point of = =E2=80=9Caccounts"? A "user" or "account" manages = the entire relationship that a person has with a Mailman = installation, including subscriptions, personal profile, = administrative roles, and credentials (currently just passwords). = An account may have several addresses associated with it and = several subscriptions. Sometimes several addresses may = be subscribed to the same list, because subscription is often = required by the posting priviliege. In Mailman 2, where a = person is identified by an address, a person with several addresses = would have to manage the credentials and preferences for each address = separately. Mailman 3's concept of "user" allows a person have = one account with a single password, set typical preferences, and = still have exceptional configurations for particular subscriptions. = It's more complex, but experience shows users are happy to = accept this much extra complexity for the power = and convenience. A "subscription" links a particular address = and the associated user, if there is one, to a mailing list. An = address is its own credential: if you can reply to a mail sent to an = address, it is assumed you own that address and are allowed to = subscribe it to lists, post from it, etc. (Not just by Mailman: = this is an extremely common setup on the Internet.) However, = this model becomes inconvenient rather quickly if you need to manage = relationships among several addresses. Why can someone become a subscriber, but not have an = account? There are subscriptions, such as other = lists or archiving services, that don't serve a single human person. = It also is a reasonable approach to situations where it's a bad = idea, or even impossible, to access personal data and credentials, = such as a subscription by an admin on behalf of a = person. _______________________________________________ Mailman-user= s mailing = list mailman-users(a)mailman3.org https://lists.mailman3.org/mailman3/= lists/mailman-users.mailman3.org/ Cameron = Smith =

8 years, 2 months

[MM3-users] Re: error when starting the mailman executable from the venv

by Brian Carpenter

Well the first thing to check I think is the /opt/mailman/mm/logs/mailman.log to see if that holds any clues to the failure. On 2/10/21 8:58 AM, Christian Stalberg via Mailman-users wrote: > Thanks for the quick response Brian. No I did not try what you suggest. I > rebooted the entire server and that fixed it. What can I do to prevent this > from happening again? > > > -----Original Message----- > From: Brian Carpenter <brian_carpenter(a)emwd.com> > Sent: Wednesday, February 10, 2021 5:52 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: error when starting the mailman executable from the > venv > > Have you tried using the following as root? > > #systemctl restart mailman > > On 2/10/21 8:39 AM, Christian Stalberg via Mailman-users wrote: >> I tried to access a 'held' message and got the 'Mailman REST API not >> available. Please start Mailman core.' error message. When I went to >> start the mailman executable from the venv I get this >> >> #~mailman/mm/venv/bin/mailman start >> Starting Mailman's master runner >> Generating MTA alias maps >> Traceback (most recent call last): >> File "/opt/mailman/mm/venv/bin/mailman", line 11, in <module> >> load_entry_point('mailman==3.3.2', 'console_scripts', 'mailman')() >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", > line 829, in __call__ >> return self.main(*args, **kwargs) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", > line 782, in main >> rv = self.invoke(ctx) >> File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/bin/mailman.py", > line 68, in invoke >> return super().invoke(ctx) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", > line 1259, in invoke >> return _process_result(sub_ctx.command.invoke(sub_ctx)) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", > line 1066, in invoke >> return ctx.invoke(self.callback, **ctx.params) >> File "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/core.py", > line 610, in invoke >> return callback(*args, **kwargs) >> File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/click/decorators.py", line > 21, in new_func >> return f(get_current_context(), *args, **kwargs) >> File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/commands/cli_contr > ol.py", line 131, in start >> os.execl(*execl_args) >> File "/usr/lib/python3.7/os.py", line 539, in execl >> execv(file, args) >> TypeError: expected str, bytes or os.PathLike object, not NoneType >> >> >> Please advise. Thank you. >> ~Christian >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org To >> unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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/ -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: Assistance Needed for Ubuntu 22.04 Mailman3 Installation and Configuration

by Odhiambo Washington

On Sat, Aug 31, 2024 at 9:12 AM smiithjohn90--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hello Everyone, > > I'm trying to install Mailman3 on an Ubuntu 22.04 server right now, and > I've run across a few obstacles that I'd like help with. I've followed the > installation instructions, but I'm having trouble in a couple places, so I > was hoping an experienced someone might help me out. > > This is what I have completed thus far: > > - I used the apt-get package manager to install Mailman3. > Installing Mailman3 using the steps outlined at https://docs.mailman3.org/en/latest/install/virtualenv.html is highly recommended. However.... - PostgreSQL was configured as the database backend. > - Postfix was installed and set up to function as the Mail Transfer Agent > (MTA). > - Assemble Postorius, Hyperkitty, and the Mailman3 core. > > Problems I'm Having: > > Postorius and Hyperkitty Connectivity: I'm having problems making sure > that the Mailman core is correctly connected to Postorius and Hyperkitty. I > get a 502 Bad Gateway error when I try to access the web interfaces. > Despite checking my specifications, I am unable to identify the problem. > Check to see that "mailman-web" is running and listening on the port you have specified in your webserver config. lsof -i -P -n | grep :NNNN > Problems with Email Delivery: I'm also having trouble with email delivery. > Although Mailman appears to be receiving emails, it is not appearing to be > sending any out. I think there might be a Postfix problem, but I'm not sure > how to solve it. > You can check Postfix logs for clues. Generally Suggested Practices: Are there any particular security best > practices I should be aware of when it comes to Mailman3 installations? I > want to confirm that my configuration is both performance- and > security-optimized. > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > https://www.igmguru.com/salesforce/salesforce-developer-training > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > I would be grateful for any advice or resources! It would be really > beneficial if someone with a similar setup could share their settings or > troubleshooting procedures. > Our settings are as documented in this HOWTO: https://docs.mailman3.org/en/latest/install/virtualenv.html We do NOT use Distro packages for Mailman3. Regarding "performance- and security-optimized", I can say that for Nginx/Apache/Postfix, the usual security/optimization rules apply, which I think might be somehow beyond the scope of the MM3 discussion. PS: There are others who use the distro packages to install MM3 and they have previously posted the details in this list. You could search the list archives for that. There is some old documentation that I believe can work for you too: https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… It's detailed enough. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

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

by Mark Sapiro

On 3/1/21 11:53 AM, David Partain via Mailman-users wrote: > Thanks for being patient with me. I'm still baffled but might have found the problem. > > > I've done the above, to no avail. > > > If I look at the queries being sent to mysql, I see stuff like this: > > > 174 Connect mailman3web@localhost<mailto:mailman3web@localhost> on mailman3web using TCP/IP > > 174 Query SET sql_mode='STRICT_TRANS_TABLES' > > 174 Query COMMIT > > 174 Query SET AUTOCOMMIT = 0 > > 174 Query SET AUTOCOMMIT = 1 > > 174 Query SET AUTOCOMMIT = 0 > > > I note that there is nothing about the charset, so something's clearly wonky. > > > As previously stated, /etc/mailman3/mailman-web.py has the right thing: > > > 'OPTIONS': { > > 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", > > 'charset': 'utf8mb4', > > }, > > > but that latter is having no effect. > > > I then found /var/lib/ucf/cache/:etc:mailman3:mailman-web.py which doesn't have charset > > (but does have init_command), but I _think_ that's only about the package management system. I think that's correct. I doubt that that's the problem, but if all else fails, you might just remove it. I don't think that would hurt as it's purpose is just todetect on upgrade of the package if you've changed the file from the distributed one and ask you what you want to do about it. > So... I found that /usr/share/mailman3-web/settings_local.py is just a link to /etc/mailman3/mailman-web.py > > (which obviously has the right thing), but what about the .pyc file? > > > # grep -i STRICT_TRANS_TABLES /usr/share/mailman3-web/settings_local.pyc > > Binary file /usr/share/mailman3-web/settings_local.pyc matches > > # grep -i charset /usr/share/mailman3-web/settings_local.pyc > > # > > > It ain't in the .pyc file. Am I overly optimistic that that might the be problem? > > > If so, I'd be grateful if someone'd tell the newbie how to recreate that file without > > trashing something. This is a bit strange: Here's how it works. .pyc files are byte-compiled versions of the corresponding .py file. When Python runs or imports from a .py file, it first looks for a corresponding .pyc file and if that is as new or newer than the .py, it uses the .pyc. If not, it uses the .py and byte-compiles it and if it has permission, writes an updated .pyc Except recent Python3 (at least I think 3.5 and newer doesn't use a .pyc in the same directory as the .py Its uses a __pycache__ directory in the same directory as the .py and within that directory a file like in this case settings_local.cpython-37.pyc (or whatever the python version is) In any case, I would remove the existing settings_local.pyc. That can't hurt, but I'm curious what ls -lR /usr/share/mailman3-web/ shows. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Mailman 3 Status Update Please?

by Abhilash Raj

Hi David, On Thu, Jul 20, 2017, at 12:47 PM, ddw David Wilson wrote: > Mailman 3 Status Update Please > > I have been following the progress and difficulties with great interest > as many struggle to implement the new version of the great Mailman 3 > list-server software. Last year about this time I posed some questions > regarding the current development status and recognize that many > additional problems seem to get in the way of actually working on long > term big picture issues. > > From my perspective of being an senior (ie overaged) person desirous of > implementing fully-featured, capable, scalable, reliable, secure > applications such as Mailman, I am convinced that I am thoroughly over > my head. > > From my limited perspective, it would seem to me that a 'nice to have' > system would incorporate the following. > > 1. An open container standard configurable system install, compatible > with different web & mail servers, DB utilities, etc; This already exists as of today, there are some open bugs and issues but nothing that would prevent you from using it right now. You can follow the documentation for the container images here[1] and look at the issues on the corresponding Github project. It should be compatible with major web & mail server and databases. [1]: https://asynchronous.in/docker-mailman/ > 2. Python 3 version Django utilities for archiving and mail list name > management; This is in the Roadmap and on high priority now that we have Mailman 3.1 out. > 3. A design/plan from an inside expert perspective stating costs, time > and resources to implement the plan, incorporating crowdfunding to > pay for project. > 4. As a backup incentive to the crowdfunding plan might be the offer of > an expert to set up a system for each significant amount donated, > say US$1,000, such as might be accomplished by an SSL session on the > target computer/server after the user has specified all necessary > detail as required in a template. AFAIK the Core developers aren't providing any services for Mailman 3 as of now. > > I am sure that the program author and other major contributors could > greatly enhance this list. > > In summary, I guess what I am requesting is an overview forecast by half > year period and out for the next two years? > > Please share the big picture? There are some TODO items that we have talked about but they aren't set as hard goals with deadlines. Most important of it is adding more features to Postorius (the Web Frontend) so as to accomplish everything one would want to interact with Mailman Core. One missing feature of the top of my head is the customizing the template. Fixing the upgrade path from Mailman 2 is another important issue. Other changes have more to do with the quality of code and probably more robust testing of the different components. Another important thing would be to have more user documentation for different management related tasks, like a List Administrator Manual. Apart from this, I can't think anything more as of now. Others might step in if they feel there is something missing in the list. -- thanks, Abhilash Raj

8 years, 3 months

[MM3-users] Re: Migrating to Mailman3

by Dennis Putnam

On 10/17/2025 3:09 AM, Stephen J. Turnbull wrote: > dap1--- via Mailman-users writes: > > > I am about to migrate from mailma2 on CentOS to mailman3 on > > Ubuntu. Are there any special gotchas of which I need to be aware? > > TIA. > > * The Ubuntu packages are old, and not well-supported by Ubuntu or the > Mailman project. Mailman 3 is not a hyperactive project, but we are > making steady progress and many new Mailman 3 users have issues or > requests for enhancement for 2-, 3-year-old packages that have been > fixed or implemented in the most recent releases. For these reasons, > we strongly recommend installing from source or from PyPI in a virtual > environment: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > (Installing from source is not hard, but it's more work than using > pre-built packages. Source is required for beta testers and > developers, but not recommended for most production environments.) > > * If your preferred RDBMS is in the MySQL family: > 1. Make sure the Mailman database(s) have the utf8mb4 charset option > set. Otherwise all emoji and some Asian characters will cause > your database to throw errors (I think this is mostly an issue for > HyperKitty and maybe a few users who put them in their display > names in Postorius and Mailman core). This is not needed for > PostgreSQL or SQLite3. > 2. You may want to increase the timeout for startup (I think this is > in the systemd units for mailman and mailmanweb). The issue is > that the mysqld doesn't exit until the journal has been flushed to > the main database (or something like that), and this may take many > seconds. This is not an issue for SQLite3 (it's a library) or > PostgreSQL (it uses dbus to notify systemd that it's ready). > > * The migration scripts for list database and web databases are quite > good, but not 100%. > > * The user model is completely different. Ordinary subscribers will > probably be happy or won't notice, but there are some traps for > administration roles. The most important is that some list owners > will give the owner password to moderators so they can do work like > use mass subscribe, but put them on the moderator list attribute so > they get the moderation notices. These moderators will lose the > "owner" capabilities like mass subscribe. > > * If you're looking at a multinode installation with Mailman core, > Postorius and HyperKitty distributed across several hosts or > containers, configuration can be finicky. I don't recommend it unless > you're familiar with such distributed operations. > > Steve > Hi Steve, Thanks for the info. I thought I had followed everything but I an unable to start mailman3 because all the expected directories in /var are missing. What steps did I miss? The instructions are a bit confusing because I had to keep switching between mailman and admin for setting up various files such as /etc/mailman3. There was no step to make mailman a sudoers. I hope I didn't mess up the installation by switching back and forth.

3 weeks, 1 day

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by Mark Sapiro

On 1/14/22 11:56 AM, David Newman wrote: > > I created a pending subscription request on a test list. Here is the > text I'm using in a file called 'list:admin:action:subscribe.txt' (minus > the rows of hypens): > > ---------- > > > As list administrator, your authorization is required for a mailing list > subscription request approval: > > For: $member > List: $listname > > At your convenience, visit: > > https://${domain}/mailman/admindb/lists/${short_listname}.${domain}/ This looks like a Mailman 2.1 URL. Are you sure you don't want something like https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > to approve or deny the request. > > ---------- > > Instead the message that goes out at midnight daily reads like this: That's a different message. It is sent from the `mailman notify` command run by cron. It's built from the list:admin:notice:pending template. > > On successive nights I have placed copies of the > 'list:admin:action:subscribe.txt' file above in these locations: > > mm/var/templates/lists/test.lists.domain.tld/en I hope you mean /opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en > /opt/mailman/mm/var/templates/site/en Either of those should work. The lists one will take priority over the site one for that list. > and then in Postorius, with the same contents as above. If you set a template in Postorius, it takes priority. If you later decide you want to use one in /opt/mailman/mm/var/templates/ you have to delete the postorius one. > The file > versions are owned by the mailman user, and have 0644 permissions. Not > sure this is necessary but I've restarted the mailman3 and mailmanweb > services each time after a change. > > There is no sign of trouble in the MM3 or web logs. The only thing I see > is in the Postfix log, where the shorter and less helpful message goes > out each night. I don't see anything in the template docs about this. > > Questions: > > 1. What to do to get the custom message working? It should work. I suspect you need to go to the list's Settings -> Automatic Responses and set `Admin immed notify` to Yes. > 2. Is there a way to trigger a subscribe reminder for one list only? If by subscribe reminder you mean the `list:admin:action:subscribe.txt` message, yes that's the above list setting. If you mean the one sent from the `mailman notify` command, see `mailman notify --help` for the options. You can specify one or more lists (default is all lists) via options and put them in your cron. > Asking because there are other lists on this server with other requests > pending, and I don't want to bother other moderators with multiple > reminders per day. Not a big deal, but it would be nice to test this > with one list rather than waiting up to 24 hours after each change. You can test `mailman notify` at any time by running it by hand. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

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

by Abhilash Raj

On Sat, Jun 8, 2019, at 2:12 AM, andrew.bernard(a)gmail.com wrote: > I'm new to Mailman. I have a Ubuntu 19 production server. I attempted > to get Mailman 3 and the web components going with the system packages, > but I encountered a few showstopper errors (such as indexing not > working at all) which I know have been fixed in the codebase. To that > end I erased my installation, and installed mailman from the gitlab > source. That all works much more nicely now and I feel I have a lot > more control of the layout of all the files (the various Ubuntu > packages smear the parts all over the place, confusingly). > > Now I want to get Postorius and Hyperkitty going again, independently > of Ubuntu packages. I would like to run Postorius and Hyperkitty under > one Django project. So I downloaded the git source for mailman_web. I > do not know if this is the right way to install. Mailman Web works okay, there are very few things actually in there. If you want to install things from source, consider using the mailman_suite project as a starting point. https://gitlab.com/mailman/mailman-suite Mark wrote down his experience installing Mailman 3 on two machines, which is currently running this very list. https://wiki.list.org/DOC/Mailman%203%20installation%20experience > I am partially familiar with Django, but to come to the point, I have > no idea once having obtained the source from git how to setup and > install the project, where it lives in the filesystem, and so on. Are > there any pointers to help in this area? The very nice readthedocs > format files for Postorius and Hyperkitty are very silent on basic > matters like this, which is not of much help! The git README files also > define a new level of brevity. > > I need some initial hand holding here. If any help is forthcoming, such > as links to more full documentation for newbies to Mailman, I would be > most grateful. I'll try to write the steps in short, let me know if you need me to expand on any of these. 1. Choose a directory to get all the sources. I usually prefer /opt. So, create /opt/mailman 2. Create a Python 3 virtual environment. $ cd /opt/mailman $ python3 -m venv vevn $ source venv/bin/activate 3. Get all the sources and install in this virtualenv, you neeed: 1. Mailman Core (mailman/mailman) 2. Mailman Client (mailman/mailmanclient 3. Mailman-Hyperkitty (mailman/mailman-hyperkitty 4. Django-Mailman3 (mailman/django-mailman3 5. Postorius (mailman/postorius) 6. Hyperkitty (mailman/hyperkitty) You can also just `pip` install those packages, instead of using git sources. I would actually recommend using the release versions if you are not ready to deal with the instability of the git heads. 4. Finally, you need to create config files in right places: - Mailman Core's config lives at `/etc/mailman.cfg - Django config lives in the django project, mailman-suite. I am not going to dive into actual runtime configuration here. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years, 5 months

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

by Stephen J. Turnbull

Kimmo L writes: > Our mailman + hyperkitty runs on RHEL 8 and yes, all the services are systemd format. > Host has 8GB swap at the moment > In addition to the above mentioned services, there is also NGINX and postfix services as well. OK. That's helpful to know. > > Have you modified any web pages associated with Mailman, including any > > of the Django templates? Are there any pages with unusually long load > > times? > No and usually all pages are very smooth. Only if i open archives, > then sometimes it will load like sec or three. That's what I would expect. > I also noticed that after midnight, if one of the mailman-web > cronjob was finished, the free memory jumped from 100mb to 1gb. Search indexes are quite large, and constructing them takes a lot of concurrently active data. I'm not at all surprised that some of the cronjobs take ~1GB. The thing about Linux is that it hates free memory. It thinks that memory should be used. If you open a data file, then close it, Linux will leave it in memory along with the metadata needed to find that memory without reading the file again. (Consider the case of a script where the first process writes a temporary file, closes it, and exits, then the second process opens the file and reads it. Big win, and this is not an uncommon case.) This is what is meant by "cache" in Linux kernel memory statistics. > And then it will start to decrease again. Because of caching, free memory is not the right statistic to look at to check for memory leaks when you're running Linux. It's free + cache. If that total consistently decreases, you have either a leak or a process that's building a large data structure. For example, when the cronjobs go on their midnight run, I'm sure you see not only free memory decrease, but cache as well. Then when they're done, boom! you see free memory jump by ~1GB. When a program builds a large structure in memory, it does so because it needs to write to it a lot. It's definitely volatile during the run, and normally it's variable from run to run. So there's no provision for caching it: when a program the creates a large data structure exits, that memory is returned to the free pool. In fact, how do programs cache such structures? They write them to files! So the first run doesn't use the kernel cache for that data, but the second run checks for the file, reads it, and after that it will be in the kernel's cache until some process demands the memory. > I will try to investigate little bit more and play little bit with > the services to be sure, that the issue is related with mailman or > gunicorn or with something else. Write a script that prints free + cache and the top ten processes from ps, sorted by VM size and also by RSS size. Run this every 15 minutes or so, it should help catch the culprit. Steve

3 years, 2 months

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

by Stephen J. Turnbull

Alexander Inzinger-Zrock writes: > It seems i set both *facepalm* while doing [1] and then adding > changes according to [2]: It's OK to set both. But you need to coordinate "layout: LAYOUT" and "[paths.LAYOUT]" if you are going to set any paths such as var_dir. > so i have empty logs at /opt/mailman/mm/var/logs > and populated log files under /var/tmp/mailman/logs "var_dir: /var/tmp/mailman" is a good setting for experimenting with Mailman 3 before you're ready for production. But you don't want /var/tmp for production. Your logs and any queued messages will get deleted when the system reboots (for most system configurations). > Now - before changing the /etc/postfix/main.cfg - there is the > question that brings us almost back to the start: For the production system you want main.cf as it is, but change mailman.cfg to [mailman] layout: local [paths.local] var_dir: /opt/mailman/mm/var For an experimental system where you don't care if stuff disappears on reboot, you can comment out the two lines for [paths.local], and change the prefix in the *_maps variables in main.cf from /opt/mailman/mm/var/ to /var/tmp/mailman/. > **what is the recommended place to put the files to?** Wherever is convenient for you! There are four predefined "selectable layouts", paths.local, paths.dev, paths.here, and paths.fhs based on paths.master. paths.master defines the configurable names, and some more or less convenient defaults. In particular, it chooses a non-destructive (because temporary) var_dir: /var/tmp/mailman, and puts all of Mailman's data in a flat structure underneath. paths.local is just an alias for paths.master (defined in schema.cfg). paths.dev and paths.here are aliases for paths.master with var_dir set relative to mailman.cfg and the current directory respectively (two configurations some developers find convenient). paths.fhs pretty much ignores paths.master (except that it must use the same directory names) to put the various components in places that conform to the Filesystem Hierarchy Standard (FHS), which makes Debian and Ubuntu packagers happy. You can select any of those by using the "[mailman] layout" setting (I'm not sure if you can use "layout: master", but you're not supposed to). You can further modify them by using the "[paths.LAYOUT] SOME_dir" settings. In production, you almost certainly want either paths.fhs (as is) or paths.local with a var_dir setting either in /opt or in /var. > and that the above specific /opt/mailman -part is just a leftover "/opt" is not a "leftover", it's a convention where the whole package, including programs and resources, is placed in its own hierarchy (like a macOS application). The "var_dir: /opt/mailman/mm/var" setup is a configuration that Mark Sapiro found convenient and continues to use. I prefer a different layout, but if I were you I'd stick with layout: local, var_dir: /opt/mailman/mm/var because everybody who answers questions is familiar with it. > If my assumption is correct i would create an issue + merge-request > for the docs. No, the docs are generally fine. I'll check some details later. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 1 week

[MM3-users] Apache+mod_wsgi issue

by Odhiambo Washington

Still on my MM3 learning path. I mostly have everything running without errors - even uwsgi is starting without errors after I followed the fix from the discussion at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I have standardized all the files in /opt/mailman/mm/ because this is FreeBSD and our configs for user-installed apps are usually supposed to go to /usr/local/etc/. My VHOST configuration is the exact replica of https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… with the only change being the Python version from 3.6 to 3.9. My challenge now is to get Apache+mod_uwsgi to serve my pages, but I am hitting the error below which has gotten me stuck. Thanking you in advance for your advice on how to overcome this. [Thu Dec 22 14:21:22.758277 2022] [wsgi:info] [pid 4288] [remote 197.232.81.246:15107] mod_wsgi (pid=4288, process='mailman-web', application='mm3-lists.kictanet.or.ke|/mailman3'): Loading Python script file '/opt/mailman/mm/wsgi.py'. [Thu Dec 22 14:21:23.039999 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] mod_wsgi (pid=4288): Failed to exec Python script file '/opt/mailman/mm/wsgi.py'. [Thu Dec 22 14:21:23.040054 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] mod_wsgi (pid=4288): Exception occurred processing WSGI script '/opt/mailman/mm/wsgi.py'. [Thu Dec 22 14:21:23.040841 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] Traceback (most recent call last): [Thu Dec 22 14:21:23.040914 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/wsgi.py", line 38, in <module> [Thu Dec 22 14:21:23.040921 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] application = get_wsgi_application() [Thu Dec 22 14:21:23.040929 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/wsgi.py", line 12, in get_wsgi_application [Thu Dec 22 14:21:23.040934 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] django.setup(set_prefix=False) [Thu Dec 22 14:21:23.040941 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/__init__.py", line 19, in setup [Thu Dec 22 14:21:23.040945 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) [Thu Dec 22 14:21:23.040952 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/__init__.py", line 92, in __getattr__ [Thu Dec 22 14:21:23.040957 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] self._setup(name) [Thu Dec 22 14:21:23.040964 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/__init__.py", line 79, in _setup [Thu Dec 22 14:21:23.040968 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] self._wrapped = Settings(settings_module) [Thu Dec 22 14:21:23.040975 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/__init__.py", line 190, in __init__ [Thu Dec 22 14:21:23.040979 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] mod = importlib.import_module(self.SETTINGS_MODULE) [Thu Dec 22 14:21:23.040986 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module [Thu Dec 22 14:21:23.040990 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] return _bootstrap._gcd_import(name[level:], package, level) [Thu Dec 22 14:21:23.040997 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "<frozen importlib._bootstrap>", line 1030, in _gcd_import [Thu Dec 22 14:21:23.041004 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "<frozen importlib._bootstrap>", line 1007, in _find_and_load [Thu Dec 22 14:21:23.041012 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked [Thu Dec 22 14:21:23.041064 2022] [wsgi:error] [pid 4288] [remote 197.232.81.246:15107] ModuleNotFoundError: No module named 'settings' -- 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: default processing

by Stephen J. Turnbull

Sam Darwin via Mailman-users writes: > His answer: "the user is set to 'list default'. Isn't that > right??" No. It should be 'default processing'. > > Notice the reasoning. he just thinks "default", and that's all, > which is a mistake. Sure, and it wouldn't have happened if he'd been instructed more precisely. The options are very nuanced. I doubt most untrained moderator candidates would be able to state the differences between "discard" and "reject", or "accept" and "default processing", and there are reasons why each of those options might be the preferred policy for the moderator's action on a given list. The list owner should explain these things to a new moderator. Perhaps some kind of documentation (popup help on mouseover, for example) could be added to the moderation page template. I think that's the most plausible improvement, and a merge request would likely be approved. > There isn't a mnemonic device where the settings have different > names. The problem isn't that the names aren't mnemonic. It's that the moderator doesn't understand the semantics, and has nothing for a mnemonic to refer to. Any names that reflect the semantics ("list fallback" for "list default", "standard processing" for "default processing") are going to have the same problem, although possibly not to the same degree. You're welcome to submit a merge request to change to alternative names, but I will be -1 if they don't reflect the semantics, Most likely I will be negatively biased because (a) I think properly educating moderators is important, which would likely eliminate the problem, and (b) I don't want to make work for the translators (who also are frequently not native speakers of English and might not understand why the change was made, and the proper translation!) > But it brings up another idea also. When accepting a held > moderated message, could there be an option, which is enabled by > default, so it just works, that is "and switch this user from > moderation-action1 to moderation-action2. That is, from 'list > default' to 'default processing', at the same moment as accepting a > message, and even without further mouse clicks. Then there would > need to be an option, which is clickable, when accepting a message, > "keep this member in moderation". This is a more plausiable suggestion, but it's clearly inadequate (or perhaps the last part is redundant). The "accept", "discard", and "reject" options are present for reasons, so they must be available as well as "do nothing" (which is not exactly the same thing as "keep in moderation"). I am concerned about whether "bad things" could happen if a moderator clicks "and switch this user from moderation-action1 to moderation-action2" when one of the other options should have been chosen. It seems you envision that "moderation-action1" and "moderation-action2" could be configurable, or that there might be several such options. I wonder how that would look. In your merge request, please document how you address those design considerations. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 weeks, 6 days

[MM3-users] Re: Mailman upgrade results in page not found error

by Guillermo Hernandez (Oldno7)

El 3/11/22 a las 14:00, Andrew Hodgson escribió: > Hi. > > Just doing the Mailman suite upgrade on my small installation I use for test purposes. > > Steps include: > Run backup script > Stop services > Mv venv venv-old > python3 -m venv --system-site-packages --symlinks venv > source venv/bin/activate > pip install -U pip > pip install mailman mailman-hyperkitty hyperkitty postorius whoosh > deactivate > ./bin/Django-admin collectstatic > ./bin/Django-admin migrate > > At this step I got an error regarding the import of URLs, a quick Google suggested this was because the new venv has upgraded to Django 4.0. I downloaded the urls.py from the mailman-web Git repo (I should migrate to this at some point I know) and replaced my version with this one. This allowed the migrate to run correctly. I found the same error, I modified urls.py in the way below: ### from django.conf import settings ### mod. 30/10/22 ###from django.conf.urls import include, url from django.conf.urls import include from django.urls import re_path as url ##### Leaving the rest of original urls.py lines unmodified. > > Once services were up everything worked as expected except for the web page. If you go tohttps://lists.hodgsonfamily.org you get a Postorius page not found error, however if you click on the Mailman logo you get to the correct place. I think this is a problem with the new urls.py I downloaded, what is the best way to restore the old behaviour of havinghttps://lists.hodgsonfamily.org going to the correct place? > > Urls.py: > # -*- coding: utf-8 -*- > # Copyright (C) 1998-2016 by the Free Software Foundation, Inc. > # > # This file is part of Postorius. > # > # Postorius is free software: you can redistribute it and/or modify it under > # the terms of the GNU General Public License as published by the Free > # Software Foundation, either version 3 of the License, or (at your option) > # any later version. > # > # Postorius is distributed in the hope that it will be useful, but WITHOUT > # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or > # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for > # more details. > # > # You should have received a copy of the GNU General Public License along with > # Postorius. If not, seehttp://www.gnu.org/licenses/. > > > from django.conf.urls import include > from django.contrib import admin > from django.urls import path, reverse_lazy > from django.views.generic import RedirectView > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), > ), > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('accounts/', include('allauth.urls')), > path('admin/', admin.site.urls), > ] > > Thanks. > Andrew. > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years

[MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature'

by Mohsen Masoudfar

________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, April 13, 2023 1:11 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature' Thank you Mark, please see below the responses to your questions. On 4/13/23 07:25, Mohsen Masoudfar wrote: > I am observing the following error message in the logs for one specific list: > > = = = > relay=email-smtp.us-east-1.amazonaws.com[35.168.84.210]:587, delay=0.27, delays=0.05/0.04/0.12/0.06, dsn=5.0.0, status=bounced (host email-smtp.us-east-1.amazonaws.com[35.168.84.210] said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) > = = = This is non-compliant. Various parts of RFC6376, e.g. sections 5.6 and 6.1 clearly anticipate that a message can contain multiple DKIM-Signature: headers. > As I mentioned, this happens for one single list only and this list has not been able to send any email for a week now. After checking mailman-users, I came across the following setting, which seems kind of related to my issue: Is email-smtp.us-east-1.amazonaws.com the outgoing MTA for Mailman. I.e the value reported by `mailman conf -k smtp_host` or perhaps smtp_host is a local MTA which is configured to relay via email-smtp.us-east-1.amazonaws.com? > > # mailman conf -k smtp_host > > [mta] smtp_host: localhost In what log is that message? > > in /var/log/mail.log Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. Postfix is running on the local host and in /etc/postfix/main.cf, this is defined: relayhost = [email-smtp.us-east-1.amazonaws.com]:587 > = = = > To distribute messages with valid DKIM signatures, I set > remove_dkim_headers: yes > in /etc/mailman3/mailman.cf > = = = > > Here are my questions: > 1 - I have around 100 lists and this happens for this one list only, so, I am not sure, if the issue might be solved with this change. This setting will remove all DKIM headers from the message as Mailman receives it. Then, it depends on how and how many DKIM signatures are added to the outgoing mail. > > could this have any side effects? Is there a reason that this is NOT set per default? > 2 - Because this happens for this one list only, I would rather change it for this one list only, is there any option available changing it for one list only and not for the whole server? No, there is no such option. The fact that this happens for only one list is very strange. I would need more information to understand why. Do these messages get queued in Mailman's retry queue? If so, if you examine one such message with `mailman qfile`, what are the complete headers from that message. > > /var/lib/mailman3/queue/retry is empty Thanks again. M -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 6 months

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

by Brian Carpenter

On 2/25/21 8:28 PM, Abhilash Raj wrote: > Thanks Brian, this looks quite comprehensive in the details. The only > thing I am a bit concerned about is granting sudo privileges to the > Mailman user. It really shouldn't have sudo given that Mailman and > Django are supposed to run as mailman user. Any compromise of > the Django application will provide the attacker root on the machine. Thanks for pointing that out. I have removed that step. It really wasn't needed. > Is there a specific reason that you chose to go with an entirely new doc Yes. Just from observing the communications on this list, there are multiple ways to install Mailman 3 which produces installation issues, database problems, outdated apps, etc. My document produces a VERY stable installation of Mailman 3 and one that is easy to maintain and update. It is also very comprehensive covering not just Mailman Suite, but the configuration of an entire server environment. Personally I think the choice of Debian, NGINX, Postfix, and PostgreSQL makes for a long and loving relationship with Mailman 3 but I do understand everyone has their own environment that they want to work with. My guide represents a very stable and easily maintained environment for me and hopefully others. > rather than helping to improve the existing one? Several parts of it (at > least the ones that official guide covers) seems similar to me and is > duplicate information that at least two people are going to spend time > writing and maintaining in future. Is there an official guide? See that is the problem. I did not know there was an official guide. Because every time I tried finding documentation in the past using Google searches, I got fed outdated information. So for me the guide that I came up with, works great for me and if no one else uses it, I certainly will. Your guide, by nature has to be minimalistic to accommodate all the various server environments out there. My is meant to be narrow but comprehensive. > Is it something about the contribution process to the official documentation > that makes it hard for people to contribute? Most of the pages at > docs.mailman3.org or come from this[1] repo and use Sphinx to build and > REsT formatting (.rst). > > [1]:https://gitlab.com/mailman/mailman-suite-doc Well I don't know much about any of the above approach to documentation. So I would say that is a hindrance. > I am just trying to understand how can we lower the barrier for community > members to help contribute to existing docs instead of them having to create > new ones. Specifically around installation, since that tends to get stale often > when depedent packages change or a new dependency is added that > breaks the installation. I had to update my guide twice due to recent changes made to the installation process such as the addition of the Dart Sass section and the problem with the cryptography module when installing Hyperkitty. While my guide covers these new hurdles to a new installation, I don't think yours says anything about them. The Dart Sass section came from Mark's comments on this list. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: Problem replying via Hyperkitty

by Jeff

I am finally getting around to revisiting the problems I have been having with replying or posting through the web of my Mailman 3 installation. Posts or replies simply disappear. Here is the Django log section from when I did a test post today: [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b/addresses HTTP/1.1" 200 824 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 1195 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org HTTP/1.1" 200 480 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname(a)lists.domain.org/config HTTP/1.1" 200 3878 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org/member/address%40domain.com HTTP/1.1" 200 544 "-" "GNU Mailman REST client v3.3.3" Nothing at all appeared in the Mailman log or the MTA log. Does anyone have any idea what is happening to the posts or what I can do to troubleshoot? Thanks much! > On Jun 30, 2022, at 6:44 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/30/22 10:07 AM, Jeff wrote: >> Hello Everyone, >> A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: >> [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) > > > This looks like the post of the reply to HyperKitty. What does the user see in response to that? > > There should be a brief alert popup indicating the message was sent. > > >> A couple of basic questions: >> 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? > > To the list. > > >> 2) what log files could I check to see what — if anything — happens to these emails? > > Mailman's var/logs/mailman.log, The MTA logs and the Django logs. > > >> 3) Are there any settings that need to be set to make this work? > > There shouldn't be as long as the list and archiving work. > > Note, a user can select 'Use email software' when replying which should open a composition dialog in their email client to post a reply yto the list. > > > -- > 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, 3 months

[MM3-users] Re: Mailman3 in dockers on EC2 - running out of memory and puking ev.ry.where.

by Danil Smirnov

Hi, I assume micro instance has been used for obvious reason to leverage AWS Free tier. Unfortunately it wouldn't work for Mailman 3 w. Hyperkitty because of large memory footprint of the applications. However, Postorius-only version works just fine on micro instance. I'm providing free AMIs for both cases with zero-configuration needed (but without SES integration) in AWS Marketplace, links could be found on page https://mailman3.com/aws/ Best regards, Danil Smirnov ср, 10 апр. 2019 г., 19:29 Abhilash Raj <maxking(a)asynchronous.in>: > On Tue, Apr 9, 2019, at 2:34 PM, roger.hislop(a)is.co.za wrote: > > Hi all -- really need some help. I'm tech literate, but definitely not > > a sysadmin or dev. > > > > I'm following the tutorial at "Olay's Farmland" at > > https://www.olay.xyz/2018/01/01/deploy-mailman-3-on-aws-using-docker/ > > which seems to be a clone of the same content here > > https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/ > > The right place to get help regarding these guides would be the author of > the posts, which AFAIK, have no affiliation with Mailman Core Team. > > On a (very) quick glance, it seems fine. > > > Easy enough to get most of the way ... set up EC2 instance, configure > > SES and add DNS settings with DKIM etc. Set up Postfix, test it. All > > working groovy. > > > > I run through the how to all the way through setting up the containers > > and firing it up. This is where things start to get funky. > > > > Once the docker-compose is run, I run "curl > > http://172.19.199.3:8000/postorius/lists/" to test. First time it said > > it couldn't connect to database. So I nuked and restarted from scratch. > > Second time it said the same thing... was reading around the place and > > tried again, and then reran that curl and it worked -- gave me html > > from a page. But the VM started running slowly --taking forever to > > follow keypresses. > > > > Eventually became unresponsive. So I rebooted the machine via AWS > > console, and docker ps showed only the postgres db running. > > docker-compose ps shows > > Name Command State > > Ports > > > ------------------------------------------------------------------------------------------ > > docker-mailman_database_1 docker-entrypoint.sh postgres Up > > 5432/tcp > > mailman-core docker-entrypoint.sh maste ... Exit 255 > > 8001/tcp, 8024/tcp > > mailman-web docker-entrypoint.sh uwsgi ... Exit 255 > > 8000/tcp, 8080/tcp > > > > So rebuilt the container -- same thing. It looks and feels like its > > running out of memory. > > > > I used the compose file from > > > https://gist.githubusercontent.com/Yexiaoxing/833bfcc5d3e4e0c06a8b7f0bac7c4… > (with appropriate edits). > > > How much memory do yo have in your VM? Have you tried using a bigger VM? > > thanks > Abhilash > _______________________________________________ > 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, 6 months

[MM3-users] Re: Problems after update to mailman 3.3.7

by Guillermo Hernandez (Oldno7)

El 6/12/22 a las 15:59, Danil Smirnov escribió: > Hi Guillermo, > > We've faced the same issue and already reported it: > https://gitlab.com/mailman/mailman/-/issues/1044 > I see. Thanks, Danil, for the confirmation that I'm not alone in this.. > I would not recommend anyone using MySQL/MariaDB database engine upgrade to > the latest version yet. Too late for that... Doy you know what components could I downgrade to avoid this? SQLAlchemy? Which versions of which packages could I downgrade to work prpoerly? Again, thanks a lot > With my best regards, > Danil Smirnov > Mailman3.com > > On Tue, Dec 6, 2022 at 4:32 PM Guillermo Hernandez (Oldno7) via > Mailman-users<mailman-users(a)mailman3.org> wrote: > >> I've getting the most strange behaviour after update to last releases. >> In one of my mailman3 servers, the messages doesnt reach for some lists >> (the five last ones) >> >> the update have not showed any error but in the var/data for the lmtp >> and vmap postfix files mailman does not create aliases for that last 5 >> lists. Any message addressed to them is returned with a "no such user" >> error. >> >> If I create a new list the system or restart mailman runners it shows >> this error: >> >> Generating MTA alias maps >> /usr/local/lib/python3.9/site-packages/pymysql/connections.py:799: >> UserWarning: Previous unbuffered result was left incomplete >> warnings.warn("Previous unbuffered result was left incomplete") >> >> I did a CHECK TABLE on mailinglists table but all seems ok. >> >> I tried reinstalling PyMySQL, but has no effect. (well, I tried >> reinstalling all) >> >> It seems to me that something is preventing creation of that aliases, an >> then the that last five lists are unreachable. >> >> I have no clue of what to do now and I'm driving crazy. >> >> Some direction to look for will be much apreciated. >> >> Thanks in advance. >> >> P.S.: I can access via postorius/hyperkitty to the archives of the lists >> that are unreacheable. >> >> >> -- >> >> ___________________________________________ >> Mailman's content filtering has removed the >> following MIME parts from this message. >> >> Content-Type: image/png >> Name: firma-GHP-emails.png >> >> Replaced multipart/alternative part with first alternative. >> _______________________________________________ >> Mailman-users mailing list --mailman-users(a)mailman3.org >> To unsubscribe send an email tomailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent todanil(a)smirnov.la >> > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess… > > This message sent toguillermo(a)querysoft.es > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 11 months

[MM3-users] configuring postfix local recipient table

by Stephen J. Turnbull

Alexander Inzinger-Zrock via Mailman-users writes: > B. /etc/postfix/main.cfg > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/path-to-mailman/var/data/postfix_lmtp This is the main issue for main.cfg. Others we can deal with later if they apply to your system. > C. aliasing, restarting services and test without , > > I then restarted postfix, rebuilt the postfix aliases (command > ''newaliases'') These are not relevant to Mailman 3, except maybe you have an alias for the Mailman site admin. > and rebuilt the mailman aliases (command ''mailman aliases''), I usually just restart Mailman instead (building the aliases is most of the time taken up by starting Mailman with Postfix). > D. empty /opt/mailman/mm/var/data/postfix_lmtp > > and then i just found out that my postfix_lmpt file was empty 1. What database are you using?[1] Is it running? If not, yes, that file is going to be empty. 2. Do you have any lists configured for your Mailman 3 instance? If not, that file will be empty. 3. Is Mailman running? (This probably isn't necessary, just checking.) 4. Is there a postfix_lmtp.db file in the same place? (Postfix will not read the plaintext version, it must be a .db file.) > 1. could somebody suggest a way, an entry should occur in > postfix_lmtp? Each entry in postfix_lmtp is added to the SQL database when you create a list, then the whole file is refreshed from the SQL database at that time. After that, the file is refreshed from the database every time you start Mailman or run "mailman aliases". > 2. What would be the appropriate order to manually generate aliases? > first: postfix-command ''newaliases'' and It doesn't matter. newaliases only handles local aliases. Mailman 3's aliases are necessarily *virtual* aliases, and the database is created from the postfix_lmtp file using "postmap", not "postalias". > 3. finding traces [7] of a file called postfix.cfg > 3.1 parameter for default lookup table type > 3.2 pointing to command ''postmap'' Both entries must be present or Mailman will error out before creating the postfix_lmtp file. There should be a template (actually, you can probably use it "as is") in site-packages/mailman/mta/postfix.cfg (or maybe in config/postfix.cfg). This file can be located anywhere, but I recommend putting it where mailman.cfg is (usually /etc/mailman3), and pointing to it in the [mta] section of mailman.cfg with the full path. > 4. to what user should the command ''postmap'' be available [8]? The user that the "mailman" command expects to run as. Normally it is installed with a+x in /usr/sbin, so as long as you put the full path in postfix.cfg you'll be fine. Footnotes: [1] We *strongly* recommend a full-scale SQL implementation like PostgreSQL (what the Mailman developers generally use) or one of the MySQL family (popular but not with us for no particular reason, we just happen to use PostgreSQL). sqlite3 is a great product, but it is not designed for heavy concurrent usage, and a typical Mailman system has about 15 daemons running all the time that are accessing the DB. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 2 weeks

[MM3-users] Re: Errors while importing mm2 list archives

by Odhiambo Washington

On Sat, Dec 10, 2022 at 9:45 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/10/22 01:13, Odhiambo Washington wrote: > > On Thu, Dec 8, 2022 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> In the DATABASES['default'] definition, you need to set `'OPTIONS': > >> {'charset': 'utf8mb4'}` > >> > > > > I added that: > > > > [database] > > class: mailman.database.mysql.MySQLDatabase > > url: mysql+pymysql://mailman_user:XXXXXXXXX@localhost > > /mailmansuite?charset=utf8mb4&use_unicode=1 > > > The above is for Mailman core. It doesn't affect HyperKitty. For that > you need to look at the DATABASES definition in > /etc/mailman3/settings.py > < > https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail…> > > and ensure that in addition to the other settings under `default {` you > have > ``` > 'OPTIONS': {'charset': 'utf8mb4'}, > ``` > > ... > >> You might also need to modify the tables, particularly hyperkitty_email > >> with something like > >> ``` > >> ALTER TABLE hyperkitty_email > >> DEFAULT CHARACTER SET utf8mb4, > >> MODIFY subject varchar(512) > >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, > >> MODIFY content > >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; > >> > > > > > > So I removed my list, dropped the database, and proceeded as follows: > > > > create database mailmansuite CHARACTER SET utf8mb4 COLLATE > > utf8mb4_0900_ai_ci; > > ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4; > > ALTER TABLE hyperkitty_email MODIFY subject varchar(512) CHARACTER SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY content longtext CHARACTER SET > utf8mb4 > > COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY sender_name varchar(255) CHARACTER > SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY in_reply_to varchar(255) CHARACTER > SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > > > I did all those (although looks overzealous) just to be on the safe > side. I > > have seen people putting emojis in their names. > > > None of that should be necessary. `mailman-web migrate` should create > the database and tables as needed. > > > > After that, I did the mailman-web migrate, created the list, imported the > > config from MM2 and then proceeded to import the archives. > > However, the errors still are there, and several messages were not > imported > > Do you have the OPTIONS setting in your DATABASES definition in > settings.py? > Here is what I have tested lately in settings.py: # MySQL Database setup DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailmansuite', 'USER': 'mm3', 'PASSWORD': 'XXXXXXXXX', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } } I have dropped the DB, recreated, run the 'migrate', created the list, imported config from MM2. However, nothing seems to be able to address the errors with importing the archives. -- 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: Hyperkitty CPU usage

by Alain Kohli

I have not seen any improvement over time, so I switched the backend to Xapian. That works like a charm now, I guess our lists were indeed just too busy for whoosh. On 5/7/19 5:15 PM, Alain Kohli wrote: > Well, I understand that it might take a while, but the process is > running for over 200h now, I doubt it can really take _that_ long if > everything is working properly. Especially because the rebuild_index > command is only taking a few hours at most, doesn't that essentially > do the same? > > We have ~700k messages in ~300 mailing lists in case that helps you > estimate how long it could take. I can take a look at alternative > backends, though. > > > On 5/7/19 4:32 PM, Abhilash Raj wrote: >> On Sat, Apr 27, 2019, at 6:22 PM, Alain Kohli wrote: >>> I'm running a custom image which is based on an older version of the >>> one >>> here: https://github.com/maxking/docker-mailman. I attached it below. >>> But I separated postorius and hyperkitty, so hyperkitty is running in >>> its own container. I'm deploying the image with a plain 'docker run' >>> behind nginx. I made fulltext_index persistent now, but it didn't get >>> populated with anything yet. I don't really have an error traceback >>> because there is never an error thrown. The only thing with some >>> content >>> is uwsgi-error.log, which you can find below. I'm also still getting >>> the >>> "A string literal cannot contain NUL (0x00) characters." messages. I >>> also noticed that it takes incredibly long for the webinterface to load >>> (several minutes) even though there doesn't seem to be any process >>> consuming notable resources apart from the minutely job. >>> >>> Funnily enough, I have the exact same image deployed on a second server >>> as well for testing. On that one everything works fine. The only >>> difference is that on the problematic one I have a lot more mailing >>> lists/archives and that I imported them from mailman2. Could something >>> have gone wrong during the import? I used the regular hyperkitty_import >>> command. >> Yes, this is because `whoosh`, the library set by default to run >> fulltext >> indexing is a pure python implementation and quite slow in busy lists. >> >> We do support more backends though, see [1] for a list of all the >> supported >> search backends. Something like Xapian(C++) or Elasticsearch/Solr(Java) >> should be much better in terms of performance. >> >> [1]: >> https://django-haystack.readthedocs.io/en/master/backend_support.html >> >>> uwsgi-error.log: >>> >>> *** Starting uWSGI 2.0.18 (64bit) on [Sat Apr 27 22:50:17 2019] >>> *** >>> compiled with version: 6.4.0 on 27 April 2019 22:48:42 >>> os: Linux-4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) >>> nodename: hyperkitty.docker >>> machine: x86_64 >>> clock source: unix >>> detected number of CPU cores: 4 >>> current working directory: /home/hyperkitty >>> detected binary path: /usr/local/bin/uwsgi >>> !!! no internal routing support, rebuild with pcre support !!! >>> setgid() to 82 >>> setuid() to 82 >>> chdir() to /home/hyperkitty >>> your memory page size is 4096 bytes >>> detected max file descriptor number: 1048576 >>> lock engine: pthread robust mutexes >>> thunder lock: disabled (you can enable it with --thunder-lock) >>> uwsgi socket 0 bound to TCP address 0.0.0.0:8081 fd 8 >>> uwsgi socket 1 bound to TCP address 0.0.0.0:8080 fd 9 >>> Python version: 3.6.8 (default, Jan 30 2019, 23:54:38) [GCC 6.4.0] >>> Python main interpreter initialized at 0x55dfaa41c980 >>> python threads support enabled >>> your server socket listen backlog is limited to 100 connections >>> your mercy for graceful operations on workers is 60 seconds >>> [uwsgi-cron] command "./manage.py runjobs minutely" registered as >>> cron task >>> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" >>> registered >>> as cron task >>> [uwsgi-cron] command "./manage.py runjobs hourly" registered as >>> cron >>> task >>> [uwsgi-cron] command "./manage.py runjobs daily" registered as >>> cron task >>> [uwsgi-cron] command "./manage.py runjobs monthly" registered as >>> cron task >>> [uwsgi-cron] command "./manage.py runjobs weekly" registered as >>> cron >>> task >>> [uwsgi-cron] command "./manage.py runjobs yearly" registered as >>> cron >>> task >>> mapped 208576 bytes (203 KB) for 4 cores >>> *** Operational MODE: threaded *** >>> WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter >>> 0x55dfaa41c980 pid: 1 (default app) >>> *** uWSGI is running in multiple interpreter mode *** >>> spawned uWSGI master process (pid: 1) >>> spawned uWSGI worker 1 (pid: 40, cores: 4) >>> Sat Apr 27 22:50:18 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> minutely" (pid 45) >>> [uwsgi-daemons] spawning "./manage.py qcluster" (uid: 82 gid: 82) >>> 22:50:21 [Q] INFO Q Cluster-47 starting. >>> 22:50:21 [Q] INFO Process-1:1 ready for work at 59 >>> 22:50:21 [Q] INFO Process-1:2 ready for work at 60 >>> 22:50:21 [Q] INFO Process-1:3 ready for work at 61 >>> 22:50:21 [Q] INFO Process-1:4 ready for work at 62 >>> 22:50:21 [Q] INFO Process-1:5 monitoring at 63 >>> 22:50:21 [Q] INFO Process-1 guarding cluster at 58 >>> 22:50:21 [Q] INFO Process-1:6 pushing tasks at 64 >>> 22:50:21 [Q] INFO Q Cluster-47 running. >>> 22:59:31 [Q] INFO Enqueued 3403 >>> 22:59:31 [Q] INFO Process-1:1 processing [update_from_mailman] >>> 22:59:33 [Q] INFO Processed [update_from_mailman] >>> Sat Apr 27 23:00:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> quarter_hourly" (pid 73) >>> Sat Apr 27 23:00:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> hourly" (pid 74) >>> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >>> with pid 73 exited after 64 second(s) >>> 23:01:28 [Q] INFO Enqueued 3404 >>> 23:01:29 [Q] INFO Process-1:2 processing >>> [rebuild_mailinglist_cache_recent] >>> [uwsgi-cron] command "./manage.py runjobs hourly" running with pid >>> 74 exited after 91 second(s) >>> Sat Apr 27 23:01:36 2019 - uwsgi_response_write_body_do(): Broken >>> pipe [core/writer.c line 341] during GET / (212.203.58.154) >>> OSError: write error >>> 23:01:36 [Q] INFO Processed [rebuild_mailinglist_cache_recent] >>> Sat Apr 27 23:15:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> quarter_hourly" (pid 88) >>> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >>> with pid 88 exited after 4 second(s) >>> 23:28:24 [Q] INFO Enqueued 3405 >>> 23:28:24 [Q] INFO Process-1:3 processing [update_from_mailman] >>> 23:28:25 [Q] INFO Processed [update_from_mailman] >>> Sat Apr 27 23:30:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> quarter_hourly" (pid 96) >>> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >>> with pid 96 exited after 4 second(s) >>> 23:44:40 [Q] INFO Enqueued 3406 >>> 23:44:40 [Q] INFO Process-1:4 processing [update_from_mailman] >>> 23:44:41 [Q] INFO Processed [update_from_mailman] >>> Sat Apr 27 23:45:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> quarter_hourly" (pid 104) >>> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >>> with pid 104 exited after 4 second(s) >>> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> quarter_hourly" (pid 113) >>> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> hourly" (pid 114) >>> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> daily" (pid 115) >>> Sun Apr 28 00:00:00 2019 - [uwsgi-cron] running "./manage.py >>> runjobs >>> weekly" (pid 116) >>> [uwsgi-cron] command "./manage.py runjobs quarter_hourly" running >>> with pid 113 exited after 55 second(s) >>> [uwsgi-cron] command "./manage.py runjobs weekly" running with pid >>> 116 exited after 55 second(s) >>> 00:01:36 [Q] INFO Enqueued 3407 >>> 00:01:36 [Q] INFO Process-1:1 processing >>> [rebuild_mailinglist_cache_recent] >>> [uwsgi-cron] command "./manage.py runjobs hourly" running with pid >>> 114 exited after 99 second(s) >>> 00:01:50 [Q] INFO Processed [rebuild_mailinglist_cache_recent] >>> 00:04:52 [Q] INFO Enqueued 3408 >>> 00:04:52 [Q] INFO Process-1:2 processing [update_from_mailman] >>> 00:04:54 [Q] INFO Processed [update_from_mailman] >>> >>> Dockerfile: >>> >>> FROM python:3.6-alpine3.7 # Add startup script to container COPY >>> assets/docker-entrypoint.sh /usr/local/bin/ # Install packages and >>> dependencies for hyperkitty and add user for executing apps. # >>> It's >>> important that the user has the UID/GID 82 so nginx can access the >>> files. RUN set -ex \&& apk add --no-cache --virtual .build-deps >>> gcc >>> libc-dev linux-headers git \postgresql-dev \&& apk add --no-cache >>> --virtual .mailman-rundeps bash sassc mailcap \postgresql-client >>> curl \&& pip install -U django==2.2 \&& pip install >>> git+https://gitlab.com/eestec/mailmanclient >>> \git+https://gitlab.com/mailman/hyperkitty@c9fa4d4bfc295438d3e01cd93090064d004cf44d >>> \git+https://gitlab.com/eestec/django-mailman3 \whoosh \uwsgi >>> \psycopg2 \dj-database-url \typing \&& apk del .build-deps \&& >>> addgroup -S -g 82 hyperkitty \&& adduser -S -u 82 -G hyperkitty >>> hyperkitty \&& chmod u+x /usr/local/bin/docker-entrypoint.sh# Add >>> needed files for uwsgi server + settings for django COPY >>> assets/__init__.py /home/hyperkittyCOPY assets/manage.py >>> /home/hyperkittyCOPY assets/urls.py /home/hyperkittyCOPY >>> assets/wsgi.py /home/hyperkittyCOPY assets/uwsgi.ini >>> /home/hyperkittyCOPY assets/settings.py /home/hyperkitty# Change >>> ownership for uwsgi+django files and set execution rights for >>> management script RUN chown -R hyperkitty /home/hyperkitty && >>> chmod >>> u+x /home/hyperkitty/manage.py# Make sure we are in the correct >>> working dir WORKDIR /home/hyperkittyEXPOSE 8080 8081# Use stop >>> signal for uwsgi server STOPSIGNAL SIGINTENTRYPOINT >>> ["docker-entrypoint.sh"]CMD ["uwsgi", "--ini", >>> "/home/hyperkitty/uwsgi.ini"] >>> >>> On 4/27/19 7:58 PM, Abhilash Raj wrote: >>>> On Sat, Apr 27, 2019, at 9:40 AM, Alain Kohli wrote: >>>>> I have run "python manage.py rebuild_index" before, doesn't that do >>>>> clear_index as well? Apart from that, I run hyperkitty in a docker >>>>> container and didn't know fulltext_index should be persistent, so >>>>> that >>>>> got deleted after every version update for sure. >>>> Which images are you using and how are you deploying them? >>>> >>>> You should persist fulltext_index, yes, and possibly logs if you need >>>> them for debugging later. >>>> >>>> Can you paste the entire error traceback? >>>> >>>>> On 4/26/19 10:18 PM, Mark Sapiro wrote: >>>>>> On 4/26/19 11:14 AM, Alain Kohli wrote: >>>>>>> I see loads of "A string literal cannot contain NUL (0x00) >>>>>>> characters." >>>>>>> messages, but I haven't found missing messages in the archives >>>>>>> yet. Not >>>>>>> sure how that could be related, though. Apart from that I don't see >>>>>>> anything unusual. The other jobs (quarter_hourly, hourly, etc.) >>>>>>> seem to >>>>>>> run and finish normally. >>>>>> Did you upgrade from a Python 2.7 version of HyperKitty to a >>>>>> Python 3 >>>>>> version? The Haystack/Whoosh search engine databases are not >>>>>> compatible >>>>>> between the two and "A string literal cannot contain NUL (0x00) >>>>>> characters." is the symptom. >>>>>> >>>>>> You need to run 'python manage.py clear_index' or just remove all >>>>>> the >>>>>> files from the directory defined as 'PATH' under >>>>>> HAYSTACK_CONNECTIONS in >>>>>> your settings file (normally 'fulltext_index' in the same >>>>>> directory that >>>>>> contains your settings.py. >>>>>> >>>>> _______________________________________________ >>>>> 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/ >>> >

6 years, 5 months

[MM3-users] Re: Can login at /admin, but cannot login at the account/login page.

by Abhilash Raj

> On Aug 14, 2021, at 9:34 PM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > I'm sorry, I'm in a "second vaccination" fog at the moment (mending > but concentration lasts only about 10 minutes), so I'll answer what I > know offhand since Abhilash is busy and Mark is probably offline for > vacation by now. Perhaps later somebody can give a fuller answer. > > pabsta(a)gmail.com writes: > >> In comparison to the walkthrough, I did two changes; First, I used >> different port numbers , as it would otherwise conflict with other >> services on the server. > > Thank you for the very precise description. It's very helpful. > >> Second, I disabled the social accounts authentification mechanisms. > > This should not be a problem since you disabled only the providers (I > think the socialauth base module is required even if you don't use it.) > >> I am still running on sqllite, as I am still testing things (one >> task at a time). > > This should be no problem. > >> Using my "superuser" credentials, I can log to the admin section in >> a fraction of a second. > > If you mean the django admin page https://localhost:800something/admin, > that doesn't involve any part of Mailman at all. > >> However, if logout and attempt to login from the postorius website, >> I get a « 502 bad gateway » error after roughly 30 seconds. The >> logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech >> free" error message > > I would guess this is also just a connection drop because it doesn't > receive the expected response within timeout. > >> and the nginx error logs just show a connection drop: >> >> 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: >> [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" > a > > >> 1- If I attempt to login with improper credentials, the services >> respond normally, and I get the expected red box with "invalid >> credentials" message on the postorius page. It is only when proper >> credentials are given that the connection fails. > > The only thing I can think of is that having sucessfully logged in, > Postorius can't find Mailman core to populate your user page. That > would explain why an invalid login (which is entirely within Postorius > and Django) proceeds as expected, but a valid login would fail so > spectacularly. This would be my guess too, although, it will show MailmanApiError in logs. Do note that that gunicorn logs don’t have all the logs from exceptions raised in Postorius, for that, you want to file the location of the ‘postorius’ or ‘root’ logger in your settings.py (I couldn’t find that, it seems like you skipped those). So, I’d expect some error or something in the logs if this isn’t the actual case. -- thanks, Abhilash Raj (maxking)

4 years, 2 months

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

by Michael Heseltine

Hi Mark, Stephen, in fact, there isn't anything running on port 8000, even though I added the service description files under "/lib/systemd/system" as detailed in the HowTo. Looking at "journalctl -xe", both the "gunicorn" and the "qcluster" service run into errors i don't understand: (qcluster) > Jan 08 21:22:23 lists.mydomain.com systemd[1]: qcluster.service: Start request repeated too quickly. > Jan 08 21:22:23 lists.mydomain.com systemd[1]: qcluster.service: Failed with result 'exit-code'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- The unit qcluster.service has entered the 'failed' state with result 'exit-code'. > Jan 08 21:22:23 lists.mydomain.com systemd[1]: Failed to start HyperKitty async tasks runner. > -- Subject: A start job for unit qcluster.service has failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- A start job for unit qcluster.service has finished with a failure. > -- > -- The job identifier is 734836 and the job result is failed. (gunicorn) > Jan 08 21:24:58 lists.mydomain.com systemd[1]: gunicorn.service: Failed with result 'exit-code'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- The unit gunicorn.service has entered the 'failed' state with result 'exit-code'. > ...skipping... > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/bin/gunicorn", line 14, in> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: sys.exit(gunicorn.app.wsgiapp.run()) > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: WSGIApplication("%(prog)s [OPTIONS] [APP_MODUL> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: super().run() > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: Arbiter(self).run() > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.halt(reason=inst.reason, exit_status=inst> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.stop() > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: time.sleep(0.1) > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.reap_workers() > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERRO> > Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker fa> > Jan 08 21:24:58 lists.mydomain.com systemd[1]: gunicorn.service: Main process exited, code=exited, statu> > -- Subject: Unit process exited > -- Defined-By: systemd > -- Support: http://www.ubuntu.com/support > -- > -- An ExecStart= process belonging to unit gunicorn.service has exited. > -- > -- The process' exit code is 'exited' and its exit status is 1. the qcluster.service and guncorn.service are 1:1 copies of the sample files provided in the base howto. Do you know what is the problem now? Cheers, Michael.

3 years, 10 months

[MM3-users] Re: old usernames appearing in mailman.log

by Ken Alker

--On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 11:04 AM, Ken Alker wrote: >> >> I've just taken on the project so I'm new to all of this, and one thing >> I noticed that caught my eye, and has left me curious, is that for the >> first a couple of seconds starting just after midnight every night (just >> after log rotation) mailman.log would have many (dozens, or hundreds) of >> lines entered in it just like this one: >> >> Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET >> /3.0/users/old-user(a)domain.tld HTTP/1.1" 404 58 >> >> where "old-user(a)domain.tld" is the email address of a user who either >> had unsubscribed or changed their email address (I don't know which, I >> just know they are no longer a member/subscriber to the list). Each >> successive entry in the log would have a different "old username" in it. >> I don't understand why these entries would be in the log and what they >> mean. Can someone shed some light on this for me? This is merely a >> question of curiosity, and not one of import. (Since migrating from >> 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.) > > > This is the Django hyperkitty sync_mailman job which is one of the django > admin jobs run daily. It goes through the HyperKitty 'sender' database > table and tries to find the Mailman core user id for each sender address > to add/update its mailman_id field with core's user_id. > > The 404s are addresses im HyperKitty's sender table for whih there is no > corresponding Mailman user. There are multiple possible reasons for this. And that is OK, right? > If the behavior has stopped it's probably because the periodic Django > jobs are not being run - this is bad. I see this in the logs from just after midnight: Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list found Jun 25 00:13:04 2023 (386086) ACCEPT: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> Jun 25 00:13:04 2023 (386090) HyperKitty failure on https://lists.netlojix.com/hyperkitty/api/mailman/urls: Followed by a huge amount of HTML (strange). I'm not sure if the first and last (third) lines in the log excerpt above are due to the same thing. I know why the public suffix list is not found; when I was migrating all my queues from the Debian layout to the "source install" layout, I could not figure out where it should go in the new world order. Can you tell me where it would normally be found on a fresh source install? I'll move it there. Is there a way to kick it into re-running whatever it does at midnight so I can test this again after putting the public suffix list back? I assume I can just execute "mailman-web runjobs daily", but will this mess things up, or is it OK to run it mid-day without stopping anything first? Is the last (third) log line excerpt simply a result of the first, or do I have something else messed up? Thank you! Ken

2 years, 4 months

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

by Mark Sapiro

On 12/11/19 12:43 AM, Marvin Gülker wrote: > > Thanks for this information. Ubuntu's mailman stores the messages below > /var/lib/mailman3/messages. The "mailman" command is in the $PATH. > >> This should print the file name and Message-ID-Hash (two lines the same) >> for each message in the messages directory until it prints only one line >> followed by the UnicodeEncodeError exception. That list line is the file >> name/Message-ID-Hash of the offending message. > > I've execucted that code, but it does not cause an exception at all. It > quietly runs through. I've attached the transcript of the shell session > to this mail. With a little crude use of grep(1), however I found my > held message in WQ/ZS/WQZSFFJLVMWQHMG4VYKGXJEKQVQXVK67. Here's a revised script: ``` $ mailman shell Welcome to the GNU Mailman shell >>> import os >>> import pickle >>> for root, dirs, files in os.walk('/var/lib/mailman3/messages'): ... for fn in files: ... print(fn) ... with open(os.path.join(root, fn), 'rb') as fp: ... msg = pickle.load(fp) ... print(msg['Message-ID']) ... x = msg.as_string() ... ``` I have adjusted the paths for your package, changed the second print to print the message-is and added the ` x = msg.as_string()` line. Now we expect to see the hash of each message-id followed by the message-id followed by the exception for the offending message. > Does the messages directory contain only held messages? I've looked at > some messages and all of these I looked at were spam. The directory > structure contains 40 messages in total, accumulating to 480 KiB disk > space. Yes, the directory and the corresponding database table contains only messages held for moderator approval. > >> DELETE FROM message WHERE message_id_hash = xxx; > > As the exception you expected did not occur, I didn't do this yet. I can > make a database and directory backup and then run it, though. Should I try? > > I assume after this I should also delete the respective files from the > messages/ directory? Actually, a better way to deal with this is in mailman shell ``` Welcome to the GNU Mailman shell >>> ms = getUtility(IMessageStore) >>> ms.delete_message('xxx') >>> ``` where xxx is the message-id value printed from the above script. >> As of Mailman core 3.3.0 there is a 'mailman notify' command designed to >> be run periodically by cron to notify owners/moderators of pending >> requests. > > I did receive an e-mail to the list owner address that told me that the > e-mail from my incorrect e-mail address "requires approval". That was > the first time I received such an e-mail. In parallel, on the incorrect > e-mail address, I received the notification for moderator approval. Yes, those are the only messages unless you are running `mailman notify`. It seems however that the latest Debian (hence Ubuntu) package doesn't have 3.3 yet. As to why you didn't receive owner notices about the held spam, perhaps they were spam filtered or somehow otherwise lost. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] sass error

by Alexander Klotz

Hi everybody, we tried to make a fresh installation out of the current version following the readme.md - we encounter the following error trying to do so. As mentioned elsewhere, 'sass' has been replaced by 'sassc', however, maybe somewhere there is still a reference to it that may have been overlooked? The answer to a similar error posted to this list in August 2017 unfortunately didn't help either. Any help would be appreciated! Thanks, Alex ERROR 2018-04-19 09:07:49,096 29 django.request Internal Server Error: /accounts/login/ Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 41, in inner response = get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 217, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 215, in _get_response response = response.render() File "/usr/local/lib/python2.7/site-packages/django/template/response.py", line 107, in render self.content = self.rendered_content File "/usr/local/lib/python2.7/site-packages/django/template/response.py", line 84, in rendered_content content = template.render(context, self._request) File "/usr/local/lib/python2.7/site-packages/django/template/backends/django.py", line 66, in render return self.template.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 207, in render return self._render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/loader_tags.py", line 177, in render return compiled_parent._render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 199, in _render return self.nodelist.render(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 990, in render bit = node.render_annotated(context) File "/usr/local/lib/python2.7/site-packages/django/template/base.py", line 957, in render_annotated return self.render(context) File "/usr/local/lib/python2.7/site-packages/compressor/templatetags/compress.py", line 131, in render return self.render_compressed(context, self.kind, self.mode, forced=forced) File "/usr/local/lib/python2.7/site-packages/compressor/templatetags/compress.py", line 107, in render_compressed rendered_output = compressor.output(mode, forced=forced) File "/usr/local/lib/python2.7/site-packages/compressor/css.py", line 49, in output ret.append(subnode.output(*args, **kwargs)) File "/usr/local/lib/python2.7/site-packages/compressor/css.py", line 51, in output return super(CssCompressor, self).output(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 295, in output output = '\n'.join(self.filter_input(forced)) File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 235, in filter_input for hunk in self.hunks(forced): File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 205, in hunks precompiled, value = self.precompile(value, **options) File "/usr/local/lib/python2.7/site-packages/compressor/base.py", line 268, in precompile return True, filter.input(**kwargs) File "/usr/local/lib/python2.7/site-packages/compressor/filters/base.py", line 229, in input return super(CachedCompilerFilter, self).input(**kwargs) File "/usr/local/lib/python2.7/site-packages/compressor/filters/base.py", line 196, in input raise FilterError(err) FilterError: /bin/sh: sass: not found

7 years, 6 months

[MM3-users] Re: Getting connection refused on postfix trying to connect to mailman-core:lmtp

by Dmitry Makovey

On 10/05/2017 07:20 PM, Abhilash Raj wrote: > On Thu, Oct 5, 2017, at 05:36 PM, Dmitry Makovey wrote: >> On 10/05/2017 03:20 PM, Abhilash Raj wrote: >>> On Thu, Oct 5, 2017, at 03:08 PM, Dmitry Makovey wrote: >>>> >>>> I've got a setup where postfix runs inside one VM(container) and mailman >>>> runs inside another one (maxking containers). I've wired everything >>>> according to docs yet I'm getting: >>>> >>>> postfix/lmtp[266]: 66A72800A87: to=<somelist(a)lists.here.stanford.edu>, >>>> relay=none, delay=0.5, delays=0.48/0.01/0/0, dsn=4.4.1, status=deferred >>>> (connect to mailman-01.stanford.edu[1.2.3.4]:8024: Connection refused) > > I found this in your settings: > > [mta] lmtp_host: mailman-01.stanford.edu > [mta] lmtp_port: 8024 > > > And the log message above. > > I believe that the LMTP runner died because it wasn't able to bind to > `mailman-01.stanford.edu`, which I am assuming is the hostname assigned > to the host running these containers. > > `MM_HOSTNAME` env variable in the docker containers should be something > that the process inside mailman-core container can bind to and can be > reached by postfix (which can run either on host or on another > container). (Now that I read it myself, I agree that the name of the > variable sounds not-so-intuitive.) thank you so much for the hints! I've changed docker-compose to include MM_HOSTNAME variable *and* made sure that for the mailman-core I've got: services: mailman-core: hostname: mailman-01 domainname: stanford.edu ... environment: ... MM_HOSTNAME: mailman-01.stanford.edu that solved the issue while keeping the mentioned mailman config. Is that what you've had in mind? I was looking for a quick hack, but still would like to find out proper solution if that isn't the one. > The default configuration (and docker-compose.yaml) sets this value to > the IP Address of the container (172.19.199.2), which is reachable from > the host. If you set this value to whatever IP the mailman-core is > assigned and re-create the containers (or just re-start and run `mailman > aliases` in mailman-core to re-generate transport_maps), it would work > out. if I understand above correctly that means semi-manual mangling of postfix aliases file which I'd rather not do. Using above technique mailman-core does generate proper aliases while binding to the appropriate IP. kind of icky but seems to work. > > Also, I see your docker-compose.yaml configuration (`MAILMAN_CORE_IP: > 172.19.199.2`) is not consistent with your output of `mailman > conf`([webservice] hostname: 172.19.199.5`). I am not sure how that > happened though, just wanted to point it out. This *might* cause the > rest runner to die to and thus Postorius/HK wouldn't work. right, some of the IPs keep on popping at me and I've got to look for them - I intentionally removed direct IP assignment in docker-compose.yaml yet I get the feeling that someplace there's another IP assignement I've missed. > Hope that was helpful! very much so! thanks for your quick responses - provided my existing deadlines I value them that much more :) -- Sr System and DevOps Engineer SoM IRT

8 years, 1 month

[MM3-users] Re: warning: database postfix_domains.db is older than source file postfix_domains

by Mark Sapiro

On 10/26/20 10:07 AM, Torge Riedel wrote: > Hi, > > I frequently get this warning mail.log. stat'ing the files give: > > # stat /opt/mailman/var/data/postfix_domains > File: /opt/mailman/var/data/postfix_domains > Size: 361 Blocks: 8 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1573095 Links: 1 > Access: (0660/-rw-rw----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-24 19:52:16.887258326 +0200 > Modify: 2020-10-20 07:09:48.792000000 +0200 > Change: 2020-10-20 07:09:48.792000000 +0200 > Birth: - > # stat /opt/mailman/var/data/postfix_domains.db > File: /opt/mailman/var/data/postfix_domains.db > Size: 12288 Blocks: 24 IO Block: 4096 regular file > Device: 801h/2049d Inode: 1583965 Links: 1 > Access: (0640/-rw-r-----) Uid: ( 1004/ mailman) Gid: ( 1002/ mailman) > Access: 2020-10-26 07:46:54.569935782 +0100 > Modify: 2020-10-20 07:09:47.575889000 +0200 > Change: 2020-10-20 07:09:47.575889000 +0200 > Birth: - I don't understand how this is happening. With defaults for mailman.cfg settings you should have in the [mta] section configuration: python:mailman.config.postfix which points to the file mailman/config.postfix.py in the installation which has in its [postfix] section postmap_command: /usr/sbin/postmap These settings say whenever mailman updates `/opt/mailman/var/data/postfix_domains`, it runs `/usr/sbin/postmap` /opt/mailman/var/data/postfix_domains` to update `/opt/mailman/var/data/postfix_domains.db`. These files, `postfix_domains` and `postfix_lmtp`should be written and closed before invoking the posymap command, so Y don't understand why the modify/change times on the .db files would be 1.22 seconds earlier than those on the source. > I do not have the feeling that this is really a problem, cause > everything works well. But it is confusing and misleading and might > makes me missing a problem in the future, when the database is really > outdated. > > Could this be easily fixed in mailman? I don't think it's a Mailman issue. For example on the server that supports this list I see $ stat /opt/mailman/mm/var/data/postfix_* File: ‘/opt/mailman/mm/var/data/postfix_domains’ Size: 391 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113910 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.787818101 +0000 Modify: 2020-10-24 19:30:44.731817318 +0000 Change: 2020-10-24 19:30:44.731817318 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_domains.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112421 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:39:45.452615116 +0000 Modify: 2020-10-24 19:30:44.787818101 +0000 Change: 2020-10-24 19:30:44.787818101 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp’ Size: 3465 Blocks: 8 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5113909 Links: 1 Access: (0660/-rw-rw----) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-24 19:30:44.775817934 +0000 Modify: 2020-10-24 19:30:44.719817150 +0000 Change: 2020-10-24 19:30:44.719817150 +0000 Birth: - File: ‘/opt/mailman/mm/var/data/postfix_lmtp.db’ Size: 12288 Blocks: 24 IO Block: 4096 regular file Device: ca11h/51729d Inode: 5112424 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 110/ mailman) Gid: ( 118/ mailman) Access: 2020-10-26 19:40:38.509356931 +0000 Modify: 2020-10-24 19:30:44.775817934 +0000 Change: 2020-10-24 19:30:44.775817934 +0000 Birth: - Which is what I expect. Note that the only times both the `postfix_domains` and `postfix_lmtp` are updated together is when one of the `mailman` subcommands `aliases` or `start` is run. Are you possibly running both these at the same time causing some kind of race condition? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Dear Mark, FYI, I observed this issue with the postfix that receives the mails from the previous MTA and hands it over to the mailman. But I fixed at postfix by upgrading it to the version postfix 3. But still Mailman is not able to understand Hindi (Indian local language) in which language the display names of the email ids are there. So, now what to do at Mailman so that it can also understand local languages or any work around or other alternate solutions for these sort of cases. On Fri, Jun 18, 2021 at 4:04 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Thank you Mark for your immediate response. > > The below are the tracebacks I could find in the mailman log. > > > > > > > > > > > > > > > > > *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: > expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback > (most recent call last): File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in > _one_iteration self._process_one_file(msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in > _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in > _dispose process(mlist, msg, msgdata, pipeline) File > "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in > process handler.process(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line > 59, in process addrs = getaddresses(msg.get_all(header, [])) File > "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = > COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str > instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: > 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* > > In the shunt file, I see something like this as below in CC while To is > good: > > > > > > > > > *Cc: > =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* > > Also, I came to know that two of the recipients in CC block have their > mail ID display name in their local language. While I am not sure, I doubt > if it could be the issue of getting shunted. > > Please confirm and suggest any solution. > > > > On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: >> > >> > Is there any chance to find out the reason for shunting of the >> > mails through any means ? >> > >> >> >> Look in Mailman's var/logs/mailman.log for the tracebacks associated >> with the shunted messages. >> >> -- >> 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 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 4 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Thank you for the clarification! Am 19.03.21 um 18:48 schrieb Abhilash Raj: > > >> On Mar 19, 2021, at 6:38 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: >> >> Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > You seem to have landed on a very old version of the docs that I didn’t unfortunately knew > was even available. I have disabled that page now. > > The settings are documented in https://docs.mailman3.org/en/latest/config-web.html > >> >> I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> How could I check, that the setting is used!? >> >> But maybe some additional information: >> - I use the Debian installation on a stable buster, so mailman is version 3.2.1 >> - I use apache2 as my web-server and use the given alias-conf-file >> - Python is version 3.7.3 >> - Postorius is Version 1.2.4 >> - HyperKitty is version 1.2.2 >> >> -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de >> -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above >> -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de >> -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de >> -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains >> >> What do I miss? Or where to investigate? >> >> Thank you in advance, best regards. >> >> By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html > > Mailman Suite consists of several individual projects including Mailman Core, Postorius (Web UI) and > Hyperkitty (Archiver). The first URL is the landing page for the entire suite and should direct you to > individual projects. The second one is the individual Mailman Core project. Historically, Core was the > only project and hence claims the name “mailman” in most places. > >> >> Am 18.03.21 um 21:52 schrieb Mark Sapiro: >>> On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >>>> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? >>> Set FILTER_VHOST = True in your settings_local.py or where ever you put >>> your site Django settings. >> _______________________________________________ >> 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, 7 months

[MM3-users] Re: Python is updated

by Odhiambo Washington

This is too complicated. On Thu, Apr 27, 2023, 23:00 Duane Raymond <duane(a)fairsay.com> wrote: > Hi Lars, > > I did the same thing this weekend (upgraded mailman to latest and python > from 3.7 to 3.11) as part of a process to do some work I've promised Mark > :-) > > Here are my notes (to I can repeat it next time). I'm on Debian 10. My > mailman install is based on Brian Carpenters install notes: > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > 0) IF UPGRADING: copy /static folder, /venv folder and base config files to > new backup folder (e.g. config_bak) > 1) Install desired python e.g 3.11 (from source if necessary) and be sure > to include: > apt install libreadline-gplv2-dev libncursesw5-dev libssl-dev > libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev > 2) IF UPGRADING: Stop the mailman related services: systemctl stop mailman > qcluster gunicorn > 3) Create local venv at: python3.11 -m venv /opt/mailman/mm/venv (backup > old one first to backup folder) > 4) Set ownership of venv folder and subfolders/files: chown -R > mailman.mailman venv > 5) Switch to owner: su mailman > 6) Activate venv: source /opt/mailman/mm/venv/bin/activate > 7) Check pip uses the intended python version: pip -V > 8) Upgrade PIP if necessary: pip install --upgrade pip > 9) Install mailman3 basics: pip install --upgrade mailman hyperkitty > postorius > 10) Install additional if missing: pip install --upgrade django-mailman3 > mailmanclient mailman-hyperkitty > 11) Install DB connector: pip install pylibmc psycopg2 python3-psycopg2 > python3-pil python3-psycopg2 whoosh python3-whoosh python3-httplib2 > 12) Update /opt/mailman/mm/urls.py with desired paths (django) > 13) IF UPGRADING RUN: bin/django-admin migrate > PLUS: bin/mailman-post-update (or individually below) > bin/django-admin collectstatic --clear --noinput --verbosity 0 > bin/django-admin compress > bin/django-admin compilemessages > 13) Exit venv environment: deactivate and Exit mailman user: exit > 14) Start mailman: systemctl start mailman (check status: systemctl > status mailman.service) > 15) Start qrunner: systemctl start qcluster (check status: systemctl > status qcluster.service) > 16) Start gunicorn: systemctl start gunicorn (check status: systemctl > status gunicorn.service) > > Note: > > 1. /django-admin is the same as /mailman-web in some installation notes. > 2. The bin/mailman-post-update script Brian used does everything except > the "migrate" step > 3. I don't know if all the pip psycopg2/whoosh modules are needed - I > didn't take the chance. > 4. My system now uses django 4.1.8 so I didn't need to worry about the > psycopg2-binary install (I don't think I did - it seems to all work) > 5. The 3.8 release notes contain a breaking change with the postgresql > connection command. I changed that before upgrading. (assuming you are > using postgresql!) > 6. What I haven't covered here is checking the autostart, service > settings and crons are working as that is in the documentation and may > already/still be running on your server. > > Hope that helps :-) > > Cheers, > > Duane > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 6 months

[MM3-users] Re: Upgrade Mailmam Core from

by Stephen J. Turnbull

Odhiambo Washington writes: > Can you possibly blow away everything and start afresh again - using the > following howto - > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ? I appreciate your efforts to help, and with a different set of facts your approach *would* be helpful. So don't stop! But please be more careful. Sascha already has successfully installed Mailman (in fact more times than they know :-), has experience with this particular approach to installation, and was already interacting with two core developers. Starting from scratch at this point doesn't make sense. > > After this, I deleted the venv again and startet anew, again. Unknown to Sascha, this venv was already a successful install. The error messages can be ignored. > > But this time, I explicitly did (as Stephen suggested above) > > > pip install wheel > > prior to > > > pip install wheel mailman psycopg2-binary\<2.9 > > > > This time, it ran through without errors, although "wheel" is also > > contained in the latter command. > > Can you explain that? Note: this second run is also successful. Explanation: "Failed to build wheel" is actually not an error. *wheels* are the preferred packaging format for Python for several years now, but others are available, and pip used one of those instead. I suspect the "Error" tag comes from a separate external command (bdist_wheel), but pip reads the error status and tries an alternative method to build a package. Sascha: I don't understand why pip doesn't install wheel before starting on mailman in "pip wheel mailman psycopg2-binary\<2.9. I think that's a bug, because this is an obvious way to use pip. Perhaps you have an older version of pip? Have you tried pip install --upgrade pip? > > Second question: > > There is still no directory "/etc/mailman3" created, where I can create > > mailman.cfg in. That's right. There are a number of different philosophies about handling files like mailman.cfg, and the Mailman install scripts can't be sure which one you want to follow. /etc/mailman3/mailman.cfg probably works for 90% or 95% of installations nowadays, but we don't know. If you're not going to put mailman.cfg there, we shouldn't create the directory. > > Does this maybe result from the fact that in first instance, I tried to > > install mailman3-full via "apt-get install" and removed it again via > > "apt-get remove"; with manually deleting /etc/mailman3 > > afterwards. That's what I consider correct behavior as implemented by apt. > > Shall I create /etc/mailman3 manually and adding "mailman" system user > > permissions? Mark wrote earlier, but let me confirm that yes, that's what you should do. Note that Debian and Ubuntu prefer to gather all possible mailing list users into a single user 'list'. I don't think this causes trouble for Mailman, but in many cases if you create a different user (as you will if you follow our instructions), you will have problems if the system-created directory with system-standard owner and permissions is left behind. This is one of several reasons why you should purge (not just delete) packages supplied by distros if you are going to switch to upstream's code. (Obviously keep copies!) Regards, Steve

3 years, 1 month

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

by Guillermo Hernandez (Oldno7)

El 3/4/23 a las 1:25, Mark Sapiro escribió: > On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I'm NOT blaming any of the parts involved... Sure, most probably is >> my fault. But the last upgrade shows that the process that fail is >> involved with mailman upgrade. The last server was working smoothly >> and it has higher traffic than the first I tried. It cannot be that I >> missed that something was not working for weeks (since the last >> upgrade of the OS) > > It depends on what you did. Mailman's lmtp runner would only encounter > this issue at startup, so unless you restarted Mailman or rebooted the > server, lmtp runner would have continued without issue even if there > was an underlying OS problem. I thought I said it: I reboot this server everyday at 06:40 CEST time. That's why I'm sure it's not an undetected problem for weeks. The lists in this last upgraded server are with daily traffic. I'm suscribed to all. > > Also, I don't think the problem is with Mailman per se. The underlying > issue is in the Python library socket module. Try the following in a > Python 3 shell > ``` > $ python3 > 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. > >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock > >>> sock = makesock(AF_INET6, SOCK_STREAM) > >>> sock.bind(("::1", 0)) > >>> sock.close() > ``` > This is essentially what aiosmtpd does and I expect that `sock = > makesock(AF_INET6, SOCK_STREAM)` will throw the `OSError: [Errno 43] > Protocol not supported` exception. > And you are right (ther is more down of this): Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported Buuuuuut, if I do the same in the "father" server: Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) >>> sock.bind(("::1", 0)) >>> sock.close() File "<stdin>", line 1 sock.close() IndentationError: unexpected indent >>> sock.close() >>> The server can open a socket without problem. As I though previously it has to be something with the jailed envviroment. Your test had probe me right (and wrong in my jail tests). It's very valuable. I know now where I can dig more. Thanks a lot -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 7 months

[MM3-users] Re: Urgent help needed...

by Darren Smith

So we have just found the culprit, or at least ONE of the culprits. The calls that are being made to populate the date browse in the left hand side of hyperkitty for a given mailing list was causing this query to be run. I still don't know what changed from yesterday to today that is causing postgres to freak out over this call - it used to work just fine. On a different note, there appear to be a lot of issues in the system that don't show up until the system is used at scale. As a question, is there any sort of system of load testing that mailman/hyperkitty/postorious/etc. can be put through so that we can find these issues before they bring down our system in production? And on a related note, we actually are in the process of setting up a testing server that we are going to populate with our live data. We should be able to run certain types of load testing against it. We won't really be able to test the flow of the 150,000 emails per day that go through our system, but testing the UI and what happens to it when it is under load, that we can test. -Darren On Thu, May 24, 2018 at 12:57 PM, Simon Hanna <simon(a)hannaweb.eu> wrote: > On 05/24/2018 06:21 PM, Darren Smith wrote: > > Hello, > > > > This morning our Mailman 3/Hyperkitty/Postorius installation has become > > unresponsive. When looking at the machine, postgres is pegging all 4 CPUs > > on the machine. > > > > We did some digging in postgres, and here is the query that is causing > > problems: > > > > "SELECT hyperkitty_email.date FROM hyperkitty_email WHERE > > hyperkitty_email.mailinglist_id = 'fooey(a)rootsweb.com' ORDER BY > > hyperkitty_email.date ASC LIMIT 1;" > > > > We have found that it doesn't matter what mailinglist_id is being used. > > > > We have also found that this might be an issue with the LIMIT 1 - our > > investigation is showing that using LIMIT 1 in postgres makes things > > execute very differently than if you use a limit 2 or more, and that this > > is probably what is going on. > > > > Basically, every time this gets called, it pegs an entire CPU for 20-30 > > seconds. It appears to be called a LOT. > > > > So our users are getting 504 gateway timeouts right now. > > > > What has changed: > > > > We have been in the process of importing our 40 million archived emails > > from our old mailman 2 archives. > > > > Questions: > > > > 1) We have tried doing a grep in the codebase - mailman3, hyperkitty, > > postorius, django - basically anything that might be calling this code, > but > > we can't find it. Does anyone know what generates this query? > It looks like the query is to get the date from the last email for a > mailinglist. > AFAIK Hyperkitty checks this when new emails get it (maybe even during > import) > > It could also relate to the "active" state of mailinglists... > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 5 months

[MM3-users] Re: Gmail problems?

by Stephen Daniel

Danil -- I've learned something today. I did not know you could check the authentication. When I check a message that I received from the list I am told: ARC-Authentication-Results: i=2; mx.google.com; dkim=neutral (body hash did not verify) header.i=(a)bellsouth.net header.s=s2048 header.b=nkq1aBRe; arc=pass (i=1); spf=pass (... I also see this: ARC-Authentication-Results: i=1; pb-mx22.pobox.com; arc=none (no signatures found); bimi=skipped (DMARC did not pass); dkim=fail (message has been altered, 2048-bit rsa key sha256) header.d=bellsouth.net header.i=(a)bellsouth.net header.b=nkq1aBRe header.a=rsa-sha256 header.s=s2048 x-bits=2048; dmarc=none policy.published-domain-policy=none How do I fix this DKIM error? Has the body changed because I add a footer to emails as they pass through? Note that bellsouth.net is the original sender's email domain. On Sun, Apr 23, 2023 at 3:41 AM Danil Smirnov <danil(a)smirnov.la> wrote: > Hi Steve, > > Have you checked "Show original" page in Gmail for the messages coming from > the list? > Does it have SPF, DKIM, and DMARC checks all "PASS"? > > Have you checked if your mailing list server IP hasn't been caught by some > anti-spam blacklist? > > I wouldn't consider the Promotions folder as the issue at all... > It is not a punishment, just an imprecise classification caused by the > message content most probably. > > With my best regards, > Danil Smirnov > Mailman3.com > > On Sat, Apr 22, 2023 at 6:03 PM Stephen Daniel <swd(a)pobox.com> wrote: > > > Mailman Gurus -- > > > > I run a number of small lists for my neighborhood association. The > largest > > of these is ~120 users. Typical volumes are about 2 messages/day. > > > > In the past week or so a number of users who use gmail as their email > > client have complained that list emails have been going to spam or > > "promotions" folders. I've always had 1 or 2 users who had trouble > > receiving mails, but this seems to be a significant percentage of all > gmail > > users. > > > > I have DMARC mitigation set to unconditional, and the DMARC action set to > > "Replace From: with list address". > > > > My emails are sent using google workspace as my SMTP relay. > > > > I'm trying to teach my users to whitelist the list domain, but they are > > not, in general, a tech-savvy bunch, so it is slow going. > > > > Anyone else suddenly having trouble with gmail? > > Any suggestions? > > > > Thanks!! > > > > -- Steve > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > Archived at: > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > This message sent to danil(a)smirnov.la > > > _______________________________________________ > 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 swd(a)pobox.com >

2 years, 6 months

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

by Guillermo Hernandez (Oldno7)

El 28/10/22 a las 9:18, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 27/10/22 a las 21:39, Mark Sapiro escribió: >>> After that the compress part showed errors... but the postorius web >>> maintenance was working well except for the CSRF error verification. >>> I will trace the compress errors and will try to find the problem >>> later. >> >> >> Do you have `COMPRESS_ENABLED = True` in your settings? If that's not >> the issue, it may be in the settings for COMPRESS_PRECOMPILERS > > While I'm tracing the problem out, this is the configuration I had > working and the error it shows after upgrade: > > <------- snip of settings.py> > > # > COMPRESS_PRECOMPILERS = ( > ('text/less', 'lessc {infile} {outfile}'), > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > # On a production setup, setting COMPRESS_OFFLINE to True will bring a > # significant performance improvement, as CSS files will not need to be > # recompiled on each requests. It means running an additional "compress" > # management command after each code upgrade. > # > http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression > #### activo compresion 18/12/20 > COMPRESS_OFFLINE = True > ###COMPRESS_OFFLINE = False > <---------- end snip> > > And below is the error it shows: > > /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" > Traceback (most recent call last): > File "/usr/local/mailman3/manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 279, in fetch_command > klass = load_command_class(app_name, subcommand) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 49, in load_command_class > return module.Command() > File > "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", > line 274, in __init__ > raise TypeError("requires_system_checks must be a list or tuple.") > TypeError: requires_system_checks must be a list or tuple. > > After searching around, I've got a hint of what can be happening. It seems a variable has changed in Django 4.1 its nature from boolean to a tuple https://github.com/painless-software/django-probes/issues/24 I've upgraded another server with mailman3 lists, with the same config listed above, and it shows the same error in the "compress" part. I'm not sure where to set the requires_system_checks variable as in one of the comments of the link, and as it doesn't seems to break anything more, I will wait for more info before trying to avoid it. I'm sure it will have some repercusion on the performance, but I'll have to live with it. Thanks again for your supporting advices. > > > > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years

[MM3-users] Re: Localization of auto-responses, question marks in welcome message

by Claus-Justus Heine

Am 25.04.22 um 08:41 schrieb Stephen J. Turnbull: > Claus-Justus Heine via Mailman-users writes: > > > Kind thanks for the response. I have to apologize: my "test user" had > > its preferred language set to en_US, so that was the reason for the > > question marks. So this was indeed a user-error (i.e. my fault). > > But we'd like to have that user get the English version of the > message. One of two things seems reasonable: > > 1. You have customized the German template, but not the English > template. In that case, I think it makes sense for Mailman to > assume the German template has important information that the > English does not, and send the German template with its > appropriate encoding (UTF-8, nowadays). The fact that en_US can > be encoded in ASCII should not affect the encoding of the de > template, ever.[1] I have installed custom templates using the REST API and pointing MM3 to some download URIs. So MM3 has custom templates for particular lists, but I did not yet install different templates for different languages. Still I would also prefer that MM3 would assume that all template text are UTF-8, independent from the language. > > 2. You have not customized the German template. In that case the > user should get the default English template. > > How do those sound to you, as goals for Mailman behavoir? > > So ISTM this is a Mailman issue, if Mailman is sending out the German > message with question marks substituted for non-ASCII characters, or > if Mailman is sending out the German message with US-ASCII as the > Content-Type charset parameter. The only way I can see this as a user > (admin) issue is if you overwrote the English template with German > (and even then, it's nuts for Mailman not to use UTF-8 for English > what with directed quotes, emoji, and all the other enhancements to > the character repertoire that US English speakers use). > > Can you tell me a little more about whether you configured any custom > templates, and if so, how? That is, did you use the Postorius text > field or overwrite files directly? I am installing download URLs pointing to a Nextcloud via the REST API described here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… However, I did not care to use URL placeholders for the language which probably I should have done. However, the RTD page only talks here about the list's preferred language, not the user's preferred language. What strikes me more that for the localization of the auto-response subjects the global setting default_language of the server seems to be relevant and not the particular list's preferred language. Claus > > Steve > > > Footnotes: > [1] Note to self: perhaps the admin UI can check the list of > supported languages and warn if some but not all are customized. > > _______________________________________________ > 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/ -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

3 years, 6 months

[MM3-users] mailman.cfg (use_https: yes) fails

by Wolfgang Bock

Hello, I configuered 3 domains in postorius https://[mydomain]/mailman3/postorius/domains/ ... also shown here: https://[mydomain]/mailman3/admin/sites/site/ (django) I installed mailman3 with debian command apt-get install mailman3-full. The package mailman3-full is described as follows: Paket: mailman3-full (3.2.1-1) (for debian-buster, W.B.) ... Betreuer: * Debian Mailman Team <mailto:pkg-mailman-hackers@lists.alioth.debian.org> (QS-Seite <https://qa.debian.org/developer.php?login=pkg-mailman-hackers%40lists.aliot…>, E-Mail-Archiv <https://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/>) * Pierre-Elliott Bécue <mailto:peb@debian.org> (QS-Seite <https://qa.debian.org/developer.php?login=peb%40debian.org>) * Jonas Meurer <mailto:jonas@freesources.org> (QS-Seite <https://qa.debian.org/developer.php?login=jonas%40freesources.org>) 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 ..... That's the output of # mailman info GNU Mailman 3.2.1 (La Villa Strangiato) Python 3.7.3 (default, Apr 3 2019, 05:39:12) [GCC 8.3.0] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://[-secret-][mydomain]/mailman3?charset=utf8&use_unicode=1 devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:[-secret-] I dont know what version of mailman client is included in the package. Should I wait until an update includes a higher Version of the mailman-client? In this context I faced a strange behavior: In the database mailman3web in table django_site are listed several domains, either in the django-domain-management site https://[mydomain]/mailman3/admin/sites/site/ id domain name 1 example.com Example.com 2 [mydomain-1] [mydomain_name_1] 3 [mydomain-2] [mydomain_name_2] 4 [mydomain-3] [mydomain_name_3] In case I delete line 1 with the id 1, in the database or in the django-web-site, postorius fails to work. After re-inserting this line, postorius works again. Regards Wolfgang Am 16.11.2019 um 01:02 schrieb Mark Sapiro: > On 11/15/19 3:45 AM, Wolfgang Bock via Mailman-users wrote: >> That doesn't solve the problem. I changed that in mailman-web.py >> (MAILMAN_REST_API_URL = https://localhost:8001) and after that in >> mailman.cfg (use_https: yes). But got the same errormessage on postorius >> website. > > You posted this log excerpt: > > Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET > /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 > Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET > /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 > Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" > 200 1438 > Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad > HTTP/0.9 request type > > > The first 3 GETs are a normal sequence of GETs from Postorius when you > go to the Mailing Lists view. That should be followed by a GET like "GET > /3.1/domains/domain.tld HTTP/1.1" where domain.tld is a configured > domain. Do you have any domains configured?/0.9'? > > I'm not sure what the issue is. You have an older version of > mailmanclient < 3.2.3a1 which uses httplib2 rather than requests. > https://pypi.org/project/httplib2/ says: > > HTTP and HTTPS > HTTPS support is only available if the socket module was compiled > with SSL support. > > but I don't think this can be the issue because the first 3 GETs work. > > You might try upgrading mailmanclient to 3.3.0. I don't know if that > will help, but it may. >

5 years, 11 months

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

by gordon＠dickens.com

David Newman wrote: > One general comment: Debian packages install files with a different > owner than the pip install. You want to be sure all your directories and > files are owned by the Mailman user ('mailman' on Debian). Yes, I have checked the ownerships. The debian package installed everything in mailman3 as user "list" whereas I have now setup everything to run as user "mailman". As I previously mentioned, mailman3 (core) is running fine. In fact mailman3 has properly posted numerous messages to several of my mailing lists since I finished setting it up with pip. However, mailman3-web (or mailman-web) is not working, I think because of a permissions issue. The installation instructions specify that mailman3-web (or mailman-web) run as user=mailman and group=mailman. However, the debian installation specifies the data files as user=www-data and group=www-data which is what apache runs as. For instance, I have my static files stored in the /var/lib/mailman3/web/static directory and the previous Debian mailman3 version set all the ownerships and groups to www-data for /var/lib/mailman3/web, /var/lib/mailman3/web/static along with all of the directories and files in the static subdirectory. So, when I run "mailman-web collectstatic" it bombs on the following permissions error: PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/web/static/hyperkitty/js/hyperkitty-common.js' So, my question is as follows. Should I continue to run mailman3-web as user mailman and change the ownership of the /var/lib/mailman3/web directory to mailman or should I leave the permissions of the /var/lib/mailman3/web directory alone and have mailman3-web run as user and group www-data? > Do you have anything further in any of the logs in /opt/mailman/web/logs ? Yes, everytime that I try to start mailman3-web it posts this to the log and which includes a permission error as the last line: *** Starting uWSGI 2.0.20 (64bit) on [Wed Jan 26 17:00:13 2022] *** compiled with version: 10.2.1 20210110 on 24 January 2022 19:51:51 os: Linux-5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) nodename: slc.mailhub4u.com machine: x86_64 clock source: unix pcre jit disabled detected number of CPU cores: 8 current working directory: / detected binary path: /opt/mailman/venv/bin/uwsgi chdir() to /usr/share/mailman3-web your processes number limit is 31530 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) bind(): Permission denied [core/socket.c line 230] > This one might be due to a bug I hit as well. There's a problem with > mistune, one of the components. If that's the issue here, this should > address it, run as the mailman user: > pip install mistune==2.0.0rc1 > mailman-web migrate > mailman-web compress > mailman-web collectstatic > mailman-web compilemessages Thanks for that tip David! Reverting mistune back to version 2.0.0rc1 allowed "mailman-web migrate" to work. I think that the balance of my problems are permissions related to running mailman3-web (or mailman-web) as user mailman versus www-data. So, please let me know, based on your installation, if I should change the permissions for /var/lib/mailman3/web/ to user/group mailman or should I run mailman3-web as user/group www-data. Also, any other advice from David or anyone else would be very much appreciated. Thanks! Gordon

3 years, 9 months

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

by Thor Atle Rustad

There is a way around it! I have had two issues with the the maxking docker image. One is that the regexp is not working properly. I reported that, and it has been fixed in newer code. My other problem is that the docker image creates a user, mailman, that receives uid 103. Well, uid 103 on my system is already taken by systemd-bus-proxy (grep 103 /etc/passwd returns "systemd-bus-proxy:x:103:105:systemd Bus Proxy,,,:/run/systemd:/bin/false"). My solution includes downloading the corrected postfix.py, and replacing the Dockerfile. I put the postfix.py in <docker-mailman>/core/assets/. My Dockerfile: FROM maxking/mailman-core RUN grep mailman /etc/passwd && grep mailman /etc/group \ && deluser mailman \ && addgroup -S -g900 mailman \ && adduser -S -u900 mailman mailman \ && grep mailman /etc/passwd && grep mailman /etc/group COPY assets/postfix.py /usr/local/lib/python3.6/site-packages/mailman/mta/postfix.py I then run docker build (with -t parameter, you must look up that yourself). I use a different name for my images, so I end up with (note, there are two tags per image): root@mailer:/home/mailman/docker/docker-mailman_mods/core# docker images REPOSITORY TAG IMAGE ID CREATED SIZE local/mailman_core_900 20171110_2 9649e84767e1 2 days ago 176MB local/mailman_core_900 latest 9649e84767e1 2 days ago 176MB local/mailman_web_900 20171110_2 07a9b3d7ddd6 2 days ago 247MB local/mailman_web_900 latest 07a9b3d7ddd6 2 days ago 247MB I do the same with the web image, as I need to change the user there, too. Then, in docker-compose.yaml, I change the line(s) referring to the image name(s): services: mailman-core: image: local/mailman_core_900 container_name: mailman-core hostname: mailman-core mailman-web: image: local/mailman_web_900 container_name: mailman-web hostname: mailman-web I don't know if this is a good solution, but at least it fixes some serious issues with the 3.1's postfix integration that wouldn't otherwise be fixed until the 3.2 release. The bottom line is that it works for me, but it adds an additional layer of complication. 2017-11-03 19:40 GMT+01:00 Abhilash Raj <maxking(a)asynchronous.in>: > On Fri, Nov 3, 2017, at 08:29 AM, Fabian A. Santiago wrote: > > October 26, 2017 11:07 PM, "Mark Sapiro" <mark(a)msapiro.net> wrote: > > > > > On October 26, 2017 7:30:35 PM PDT, "Fabian A. Santiago" < > fsantiago(a)garbage-juice.com> wrote: > > > > > >> That was it. Perfect. I manually modified my regexp map and it works > > >> now. Excellent and Thank you. You're the man. Does mm3 ever refresh > > >> those maps or only as I add new domains / lists? > > > > > > Only when you make changes to domains or lists. > > > > > > -- > > > Mark Sapiro <mark(a)msapiro.net> > > > Sent from my Not_an_iThing with standards compliant, open source > software. > > > > Mark, > > > > I've noticed that even simply restarting the mm3 components those alias > > maps get rewritten and the problem returns until I can manually edit it. > > Yeah, that is true. Transport maps are re-generated everytime the > container restarts. > > I don't think think there is any way around this right now :( > > > -- > Abhilash Raj > maxking(a)asynchronous.in > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 11 months

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

by Mark Sapiro

On 8/12/21 12:01 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> But whatever is listening on port 8001 is apparently not Mailman's rest >> server. What does >> ps -fww 14080 >> or whatever PID is currently listening on port 8001 show. > > UID PID PPID C STIME TTY STAT TIME CMD > list 15972 15963 0 Aug11 ? Sl 0:13 /usr/bin/python3 /usr/lib/mailman3/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 I had asked "What does ps -fwwa|grep rest show?" and it didn't find this. That was my error. I meant 'ps -fwwA|grep rest' >>> OK. >> Perhaps instead you should have >> uid: list >> gid: list >> in your uwsgi configuration if you don't already. > > Tried that while also switching mailman3-web.service to list:list, exactly the same error. Also, I have /run/mailman3-web/uwsgi.sock owned by list:list now instead of www-data:www-data. All the mailman processes should run as `list` and all mailman related things should be readable and writable by `list`. >>> I'm not familiar enough with this form of ProxyPass using sockets to >> understand what the localhost:8001 does in this context, but uwsgi >> should not be doing anything with port 8001. In a configuration using >> TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API >> server listens. uwsgi should receive connects in your case via the unix >> socket and then pass them to Django via the application in wsgi.py >> Also, you may want other paths proxied to uwsgi, namely at least some of >> hyperkitty, postorius, archives, accounts, admin and user-profile. > > Ok, I removed that port again, now it's exctly like in the automatically generated config file. > And you mean like > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /hyperkitty unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /postorius unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /admin unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /archives unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /accounts unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > ProxyPass /user-profile unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> Yes, I meant if you want those URLs to work, you have to pass them to uwsgi. You don't need all of them. `mailman2` and `postorius` are synonyms as are `archives` and `hyperkitty` However, you could try using TCP to communicate with uwsgi rather than a Unix socket. This means replacing uwsgi-socket = /run/mailman3-web/uwsgi.sock with uwsgi-socket = 0.0.0.0:8000 in your uwsgi.ini file and using directives like ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/django" "http://127.0.0.1:8000/django" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" in apache. I am not familiar enough with apache/uwsgi configuration to be of more help. Have you seen https://wiki.list.org/x/12812344 and have you asked Debian for help with their package. They are the ones who should be supporting it <https://www.debian.org/support>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

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

by Odhiambo Washington

On Sun, Jul 28, 2024 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/28/24 09:54, Roland Giesler via Mailman-users wrote: > > > > These settings from the Django docs look like the ones in mailman.cfg. > > Do I have to set them somewhere else too? > > > Yes. The settings in mailman.cfg only affect mail from Mailman. For mail > from Django, you have to set things like > > EMAIL_HOST = 'box2.gtahardware.co.za' > EMAIL_PORT = 465 > EMAIL_HOST_USER = 'roland(a)giesler.za.net' > EMAIL_HOST_PASSWORD = '...' > > and possibly others as desired, See the links to the Django docs for these. > > > > * |use_tls|:|EMAIL_USE_TLS| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T… > > > > * |use_ssl|:|EMAIL_USE_SSL| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S… > > > > * |timeout|:|EMAIL_TIMEOUT| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO… > > > > * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K… > > > > * |ssl_certfile|:|EMAIL_SSL_CERTFILE| > > > > < > https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C… > > > > This all goes in your Django settings which from other posts I gather is > /etc/mailman3/mailman3-web.py. I'm guessing you are using the Debian > packages and that's where the package puts the Django settings. > I am following this thread out of curiosity. So I added the same lines to my /opt/mailman3/settings.py - on a virtualenv install of the latest MM3 code.It's my test VM. After adding the lines and restarting mailmanweb, I then entered the virtualenv and did 'mailman-web createsuperuser' which completed successfully, but NO MAIL! As matter of fact, there isn't even anything in the logs of the MTA running at w.kictanet.or.ke. ``` root@ubuntu24:/home/wash# su mailman (venv) mailman@ubuntu24:~$ tail -n 5 /etc/mailman3/settings.py EMAIL_HOST = 'gw.kictanet.or.ke' EMAIL_PORT = 587 EMAIL_HOST_USER = 'mailman(a)gw.kictanet.or.ke' EMAIL_HOST_PASSWORD = 'XXXXXXYYYYYYYZZZZ' (venv) mailman@ubuntu24:~$ mailman-web createsuperuser Username (leave blank to use 'mailman'): mm3admin1 Email address: odhiambo(a)outlook.com Password: Password (again): Superuser created successfully. (venv) mailman@ubuntu24:~$ tail -n 5 /opt/mailman/web/logs/mailmanweb.log [Nothing in that file] (venv) mailman@ubuntu24:~$ tail -n 10 /opt/mailman/mm/var/logs/mailman.log [2024-07-29 13:41:22 +0300] [301491] [INFO] Starting gunicorn 22.0.0 [2024-07-29 13:41:22 +0300] [301491] [INFO] Listening at: http://127.0.0.1:8001 (301491) [2024-07-29 13:41:22 +0300] [301491] [INFO] Using worker: sync [2024-07-29 13:41:22 +0300] [301537] [INFO] Booting worker with pid: 301537 [2024-07-29 13:41:22 +0300] [301538] [INFO] Booting worker with pid: 301538 Jul 29 13:41:23 2024 (301485) bounces runner started. [29/Jul/2024:13:45:52 +0300] "GET /3.1/domains HTTP/1.1" 200 333 "-" "GNU Mailman REST client v3.3.5" [29/Jul/2024:13:45:52 +0300] "GET /3.1/domains/lists.wash.lan HTTP/1.1" 200 228 "-" "GNU Mailman REST client v3.3.5" [29/Jul/2024:13:45:52 +0300] "GET /3.1/users/odhiambo(a)gmail.com HTTP/1.1" 200 395 "-" "GNU Mailman REST client v3.3.5" [29/Jul/2024:13:45:52 +0300] "POST /3.1/lists/find HTTP/1.1" 200 503 "-" "GNU Mailman REST client v3.3.5" -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 3 months

[MM3-users] Re: Incoming command emails (i.e. listname-leave) routed to list itself

by Mark Sapiro

On 04/20/2017 05:37 PM, Mark Lindsay wrote: > > I'm new to Mailman 3 and Mailman in general, but I've got it up and > running, and my external app is communicating quite well with the > administrative REST API. Cool. > Here's the only problem I haven't been able to figure out: > > Say I have a list called "potato." List members can post to the list by > emailing potato(a)lists.mydomain.org. This works fine. However, incoming mail > for command addresses (e.g. potato-leave(a)lists.mydomain.org) is routed to > the list too. The command email gets sent out to all members, as if the > user who wanted to unsubscribe had just written to potato(a)lists.mydomain.org. > This is also the case with the potato-request(a)lists.mydomain.org address. > > I am using exim4 on Ubuntu. I followed the instructions here: > http://mailman.readthedocs.io/en/release-3.0/src/mailman/docs/MTA.html. The > only change I had to make to the exim4 config files in the readthedocs > instructions was in this line: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}@${domain} > > I had to change it to: > > MM3_LISTCHK=MM3_HOME/lists/${local_part}.${domain} > > That is how the subdirectories are named in my lists directory. e.g. > potato.lists.mydomain.org. If I use the exact MM3_LISTCHK value from > readthedocs, I get 550 Unrouteable bounces. OK. That document needs updating. Also, the '-admin' local_part_suffix should not be there, but that's not related to your issue. '-admin' is from MM 2.1 and isn't used in MM 3. > Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.org >> `? That's the key question. The transport is supposed to just relay the message to Mailman via LMTP to MM3_LMTP_PORT, but it appears to be rewriting the envelope recipient from potato-leave(a)lists.mydomain.org to potato(a)lists.mydomain.org. I suspect the router is somehow stripping local_part_suffix from the recipient address, but why, I don't know. > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through it. We want to make MM 3 work with Exim as an MTA. Unfortunately, I have not used Exim as an MTA in a long time and not with Mailman 3 at all, so I may not be much help. I think the person who set up Exim is on this list and may reply. If not, I'll try to research this further. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

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

by Nelson Strother

Here are the (four identical, but for timestamps and process numbers, at a glance) tracebacks, and some related info: --- from /var/log/syslog Jun 8 03:35:47 localhost mailman[13107]: Traceback (most recent call last): Jun 8 03:35:48 localhost mailman[13107]: File "/var/tmp/mailman/.local/bin/runner", line 8, in <module> Jun 8 03:35:48 localhost mailman[13107]: sys.exit(main()) Jun 8 03:35:48 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Jun 8 03:35:48 localhost mailman[13107]: return self.main(*args, **kwargs) Jun 8 03:35:48 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1055, in main Jun 8 03:35:48 localhost mailman[13107]: rv = self.invoke(ctx) Jun 8 03:35:48 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Jun 8 03:35:48 localhost mailman[13107]: return ctx.invoke(self.callback, **ctx.params) Jun 8 03:35:48 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 760, in invoke Jun 8 03:35:48 localhost mailman[13107]: return __callback(*args, **kwargs) Jun 8 03:35:48 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Jun 8 03:35:48 localhost mailman[13107]: return f(get_current_context(), *args, **kwargs) Jun 8 03:35:48 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/bin/runner.py", line 160, in main Jun 8 03:35:49 localhost mailman[13107]: initialize(config_file, verbose) Jun 8 03:35:49 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 231, in initialize Jun 8 03:35:49 localhost mailman[13107]: initialize_2(propagate_logs=propagate_logs) Jun 8 03:35:49 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 189, in initialize_2 Jun 8 03:35:49 localhost mailman[13107]: config.db = getUtility(IDatabaseFactory, utility_name).create() Jun 8 03:35:49 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py", line 60, in create Jun 8 03:35:49 localhost mailman[13107]: return database Jun 8 03:35:49 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ Jun 8 03:35:49 localhost mailman[13107]: self.unlock() Jun 8 03:35:49 localhost mailman[13107]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 420, in unlock Jun 8 03:35:49 localhost mailman[13107]: raise NotLockedError('Already unlocked') Jun 8 03:35:49 localhost mailman[13107]: flufl.lock._lockfile.NotLockedError: Already unlocked Jun 8 03:35:49 localhost dhclient[633]: RCV: Advertise message on ens192 from fe80::250:56ff:fe95:b457. Jun 8 03:36:46 localhost mailman[13100]: Traceback (most recent call last): Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/bin/runner", line 8, in <module> Jun 8 03:36:46 localhost mailman[13100]: sys.exit(main()) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Jun 8 03:36:46 localhost mailman[13100]: return self.main(*args, **kwargs) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1055, in main Jun 8 03:36:46 localhost mailman[13100]: rv = self.invoke(ctx) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Jun 8 03:36:46 localhost mailman[13100]: return ctx.invoke(self.callback, **ctx.params) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 760, in invoke Jun 8 03:36:46 localhost mailman[13100]: return __callback(*args, **kwargs) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Jun 8 03:36:46 localhost mailman[13100]: return f(get_current_context(), *args, **kwargs) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/bin/runner.py", line 160, in main Jun 8 03:36:46 localhost mailman[13100]: initialize(config_file, verbose) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 231, in initialize Jun 8 03:36:46 localhost mailman[13100]: initialize_2(propagate_logs=propagate_logs) Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 189, in initialize_2 Jun 8 03:36:46 localhost mailman[13100]: config.db = getUtility(IDatabaseFactory, utility_name).create() Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py", line 60, in create Jun 8 03:36:46 localhost mailman[13100]: return database Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ Jun 8 03:36:46 localhost mailman[13100]: self.unlock() Jun 8 03:36:46 localhost mailman[13100]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 420, in unlock Jun 8 03:36:46 localhost mailman[13100]: raise NotLockedError('Already unlocked') Jun 8 03:36:46 localhost mailman[13100]: flufl.lock._lockfile.NotLockedError: Already unlocked Jun 8 03:36:56 localhost mailman[13109]: Traceback (most recent call last): Jun 8 03:36:56 localhost mailman[13109]: File "/var/tmp/mailman/.local/bin/runner", line 8, in <module> Jun 8 03:36:56 localhost mailman[13109]: sys.exit(main()) Jun 8 03:36:56 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Jun 8 03:36:56 localhost mailman[13109]: return self.main(*args, **kwargs) Jun 8 03:36:56 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1055, in main Jun 8 03:36:56 localhost mailman[13109]: rv = self.invoke(ctx) Jun 8 03:36:56 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Jun 8 03:36:56 localhost mailman[13109]: return ctx.invoke(self.callback, **ctx.params) Jun 8 03:36:56 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 760, in invoke Jun 8 03:36:56 localhost mailman[13109]: return __callback(*args, **kwargs) Jun 8 03:36:56 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Jun 8 03:36:56 localhost mailman[13109]: return f(get_current_context(), *args, **kwargs) Jun 8 03:36:56 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/bin/runner.py", line 160, in main Jun 8 03:36:56 localhost postfix/anvil[13147]: statistics: max connection rate 1/60s for (smtp:163.123.143.10) at Jun 8 03:33:27 Jun 8 03:37:00 localhost postfix/anvil[13147]: statistics: max connection count 1 for (smtp:163.123.143.10) at Jun 8 03:33:27 Jun 8 03:37:00 localhost mailman[13109]: initialize(config_file, verbose) Jun 8 03:37:01 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 231, in initialize Jun 8 03:37:01 localhost mailman[13109]: initialize_2(propagate_logs=propagate_logs) Jun 8 03:37:01 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 189, in initialize_2 Jun 8 03:37:01 localhost mailman[13109]: config.db = getUtility(IDatabaseFactory, utility_name).create() Jun 8 03:37:01 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py", line 60, in create Jun 8 03:37:01 localhost mailman[13109]: return database Jun 8 03:37:01 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ Jun 8 03:37:01 localhost mailman[13109]: self.unlock() Jun 8 03:37:01 localhost mailman[13109]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 420, in unlock Jun 8 03:37:01 localhost mailman[13109]: raise NotLockedError('Already unlocked') Jun 8 03:37:01 localhost mailman[13109]: flufl.lock._lockfile.NotLockedError: Already unlocked Jun 8 03:37:01 localhost postfix/anvil[13147]: statistics: max cache size 1 at Jun 8 03:33:27 Jun 8 03:37:01 localhost mailman[13110]: Traceback (most recent call last): Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/bin/runner", line 8, in <module> Jun 8 03:37:01 localhost mailman[13110]: sys.exit(main()) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Jun 8 03:37:01 localhost mailman[13110]: return self.main(*args, **kwargs) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1055, in main Jun 8 03:37:01 localhost mailman[13110]: rv = self.invoke(ctx) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Jun 8 03:37:01 localhost mailman[13110]: return ctx.invoke(self.callback, **ctx.params) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/core.py", line 760, in invoke Jun 8 03:37:01 localhost mailman[13110]: return __callback(*args, **kwargs) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Jun 8 03:37:01 localhost mailman[13110]: return f(get_current_context(), *args, **kwargs) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/bin/runner.py", line 160, in main Jun 8 03:37:01 localhost mailman[13110]: initialize(config_file, verbose) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 231, in initialize Jun 8 03:37:01 localhost mailman[13110]: initialize_2(propagate_logs=propagate_logs) Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 189, in initialize_2 Jun 8 03:37:01 localhost mailman[13110]: config.db = getUtility(IDatabaseFactory, utility_name).create() Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py", line 60, in create Jun 8 03:37:01 localhost mailman[13110]: return database Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ Jun 8 03:37:01 localhost mailman[13110]: self.unlock() Jun 8 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 420, in unlock Jun 8 03:37:01 localhost mailman[13110]: raise NotLockedError('Already unlocked') Jun 8 03:37:01 localhost mailman[13110]: flufl.lock._lockfile.NotLockedError: Already unlocked --- note that processes 13100, 13107, 13109, and 13110 are the ones missing from the sequential process numbers shown by systemctl status mailman below, were presumably momentarily the missing command, digests, retry, and virgin runners ... -- all of the recent lines from /var/tmp/mailman/logs/mailman.log : Jun 08 03:24:17 2023 (4268) Master stopped Jun 08 03:30:18 2023 (13093) Master started Jun 08 03:43:31 2023 (13108) task runner started. Jun 08 03:43:52 2023 (13108) Task runner evicted 0 expired pendings Jun 08 03:43:52 2023 (13108) Task runner deleted 0 orphaned workflows Jun 08 03:43:53 2023 (13108) Task runner deleted 0 orphaned requests Jun 08 03:43:54 2023 (13108) Task runner deleted 0 orphaned messages Jun 08 03:43:54 2023 (13108) Task runner evicted expired cache entries Jun 08 03:44:17 2023 (13101) in runner started. Jun 08 03:44:23 2023 (13105) pipeline runner started. Jun 08 03:44:54 2023 (13103) nntp runner started. Jun 08 03:45:59 2023 (13098) archive runner started. Jun 08 03:46:06 2023 (13104) out runner started. Jun 08 03:46:23 2023 (13099) bounces runner started. Jun 08 03:46:43 2023 (13106) rest runner started. [2023-06-08 03:46:43 +0000] [13106] [INFO] Starting gunicorn 20.1.0 [2023-06-08 03:46:43 +0000] [13106] [INFO] Listening at: http://127.0.0.1:8001 (13106) [2023-06-08 03:46:43 +0000] [13106] [INFO] Using worker: sync [2023-06-08 03:46:44 +0000] [13345] [INFO] Booting worker with pid: 13345 [2023-06-08 03:46:44 +0000] [13346] [INFO] Booting worker with pid: 13346 Jun 08 03:46:46 2023 (13102) lmtp runner started. Jun 08 04:44:04 2023 (13108) Task runner evicted 0 expired pendings Jun 08 04:44:04 2023 (13108) Task runner deleted 0 orphaned workflows Jun 08 04:44:05 2023 (13108) Task runner deleted 0 orphaned requests Jun 08 04:44:05 2023 (13108) Task runner deleted 0 orphaned messages Jun 08 04:44:05 2023 (13108) Task runner evicted expired cache entries {with these last five lines being repeated hourly since ...} -- root@localhost:~# systemctl status mailman ● mailman.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-06-08 03:30:18 UTC; 13h ago Process: 13092 ExecStart=/var/tmp/mailman/.local/bin/mailman --config /var/tmp/mailman/var/etc/mailman.cfg start (code=exited, status=0/SUCCESS) Main PID: 13093 (python3) Tasks: 17 (limit: 465) Memory: 73.5M CPU: 15min 23.511s CGroup: /system.slice/mailman.service ├─13093 /usr/bin/python3 /var/tmp/mailman/.local/bin/master -C /var/tmp/mailman/var/etc/mailman.cfg ├─13098 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=archive:0:1 ├─13099 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=bounces:0:1 ├─13101 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=in:0:1 ├─13102 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=lmtp:0:1 ├─13103 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=nntp:0:1 ├─13104 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=out:0:1 ├─13105 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=pipeline:0:1 ├─13106 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=rest:0:1 ├─13108 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=task:0:1 ├─13345 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=rest:0:1 └─13346 /usr/bin/python3 /var/tmp/mailman/.local/bin/runner -C /var/tmp/mailman/var/etc/mailman.cfg --runner=rest:0:1 Jun 08 03:37:01 localhost mailman[13110]: initialize_2(propagate_logs=propagate_logs) Jun 08 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/core/initialize.py", line 189, in initialize_2 Jun 08 03:37:01 localhost mailman[13110]: config.db = getUtility(IDatabaseFactory, utility_name).create() Jun 08 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py", line 60, in create Jun 08 03:37:01 localhost mailman[13110]: return database Jun 08 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ Jun 08 03:37:01 localhost mailman[13110]: self.unlock() Jun 08 03:37:01 localhost mailman[13110]: File "/var/tmp/mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py", line 420, in unlock Jun 08 03:37:01 localhost mailman[13110]: raise NotLockedError('Already unlocked') Jun 08 03:37:01 localhost mailman[13110]: flufl.lock._lockfile.NotLockedError: Already unlocked root@localhost:~# On 6/8/23 13:02, Mark Sapiro wrote: > On 6/7/23 21:30, Nelson Strother wrote: >> >> Interestingly if I use `systemctl start mailman` thus far the results >> are: >> - the wall clock duration is shorter than when `mailman start` is >> issued from the command line, and >> -- either that all of the runners remain present once they are started, >> -- or I can see in syslog a traceback from each missing runner >> process starting from .../mailman/.local/bin/runner and ending with >> "flufl.lock._lockfile.NotLockedError: Already unlocked". >> >> I do not yet understand how to make use of these clues, but at least >> one can see an epitaph from each deceased process. > > > The NotLockedError is most likely because a lock has been set with a > lifetime and its lifetime has passed and some other process has broken > the lock before the original process tries to unlock it. This probably > has something to do with the long times to do start/restart. > > However, the only lock that should be involved is the master lock set > by the master watcher, so I don't really understand what might be > happening. > > What is the full traceback from these errors? >

2 years, 5 months

[MM3-users] Re: Deliverability and Spam Filtering

by Tom ＠ Gather

Interesting! Does the `in` queue also work for emails to subaddresses like foo-owner, etc? Or is it only for list posts? Relatedly, why is `list_id` a required parameter? Isn't that information contained in the email? Struggling to understand this fully... Thanks for the help. On Thu, Jan 30, 2020 at 4:06 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Thu, Jan 30, 2020, at 8:44 AM, tom(a)gather.coop wrote: > > Hi folks! First time poster, long time Mailman user. > > > > I am setting up a new Mailman 3 instance, and am super excited about > > the REST API. I plan to use it to enable tight integration with a > > separate web app that I maintain. > > > > As I am setting up the mail server, I am wondering about two related > > things: deliverability (for outgoing mail) and spam filtering (for > > incoming mail). > > > > What solutions have folks used for these? I know it is generally common > > now to outsource this critical task to a cloud provider like Mailgun or > > etc. Have folks needed this or is running ones own incoming and > > outgoing mail not a big deal? So many horror stories out there... > > > > As far as Mailgun goes, I think it should be straightforward to > > configure it for outgoing mail, but I'm not sure how I'd use it for > > incoming. Mailgun can forward mail via HTTP or to another email > > address. Neither I think would work out of the box. It would be great > > if there were a REST API endpoint for incoming mail, but I don't think > > such a thing exists, right? Perhaps I could add one? > > There does exist a way to insert messages into Mailman via REST API, if > you want to do that. It is done via Queue API, which exposes the internal > store where messages sit after they are received from LMTP before they are > processed. > > You can just inject the message in "IN" queue and it should be processed > like a regular incoming message. > > > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/queues.html > > Although, it seems to only accept string representation of Email, which > may not be ideal for your use case. It might be some work to make it work > for raw bytes. > > > > > Another thought I had was that I could write a simple HTTP server that > > receives mail from Mailgun and forwards it to Mailman via LMTP. But it > > seems simpler to go right to Mailman's core API given that one exist > > already. > > > > Or am I thinking about this all wrong? Are there other more suitable > > services out there? I looked for cloud MTA providers but didn't turn up > > much except for in the large enterprise space, which I'm sure I can't > > afford. > > > > Thanks for any thoughts! > > _______________________________________________ > > 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, 9 months

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

by Thomas Ward

On 10/23/23 23:03, Thomas Ward via Mailman-users wrote: > On 10/23/23 22:57, Abhilash Raj wrote: >> On 10/23/23 20:37, Thomas Ward via Mailman-users wrote: >>> I want to add a custom handler that implements customized thread IDs >>> in the system. I already have the DB logic worked out, but the >>> documentation for plugins is NOT clear on how to define a handler in >>> a plugin, nor does the example plugin in the documentation on Gitlab >>> have any custom handlers. >>> >>> I'm looking to add a custom handler so that the private pipeline for >>> threaded-subject-list can use thread-subject (the custom handler) >>> instead of subject-prefix (builtin). >> >> https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/plugins/testin… >> >> >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… >> >> >> These are two places you can find docs for an example plugin that >> ships with Mailman's code. Adding a new "component", like a Handler, >> works very similar to the "rules" in the example shown above. > Yeah these're helpful, but the problem I was running into was file > naming schema - I was not aware it's always > PLUGIN/COMPONENT/COMPONENT.py in the naming, which it was not entirely > clear about. It makes sense now that I look back, but it never hurts > to get clarification. >> >> You will probably need a directory tree like: >> ``` >> example/ >> __init__.py >> hooks.py >> handlers/ >> __init__.py >> handlers.py >> ``` >> >> Installing the handler is same as per shown in docs using below (do >> note that the above example is the name of the package that is >> importable): >> >> >> <snip> >> >> Finally, you can verify that your handler was loaded properly using >> something along the lines of: >> >> ``` >> $ mailman shell >> Welcome to the GNU Mailman shell >> Use commit() to commit changes. >> Use abort() to discard changes since the last commit. >> Exit with ctrl+D does an implicit commit() but exit() does not. >> >> >>> for each in config.handlers: >> ... print(each) >> ... >> <snip> > > The only other thing that was missing is how to set up the proper code > for a Handler implementation/class, which I used an existing mailman3 > core plugin as an example to just run with for testing purposes. > > There are notes in the example plugin on Gitlab and the documentation > that "other components will be added as examples eventually" but that > was well over a year ago, so we'll see how that ages. > > > Thanks for the assist! > > > Thomas > One last question: This is in the Plugins documentation: > Mailman defines a plugin as a Python package on sys.path that provides components matching the IPlugin interface. This means I can install the code to anywhere on `sys.path` that the system can detect and it does not need to be in the Mailman3 library/directory space in the venv? Thomas

2 years

[MM3-users] Re: Message-Footer after migrating to Mailman3

by Mark Sapiro

On 5/24/21 10:43 AM, christopher.claus(a)tgcamberg1848.de wrote: > > I found the file > [code] > /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt > [/code] > which includes the old footer: > [code] > _______________________________________________ > $display_name Mailingliste -- $listname > Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} > [/code] > > but no configuration item to disable this behaviour. That is the default footer template that's part of the Mailman distribution. That template is overridden by those in Mailman's var/templates/ directory. Mailmnan's import21 process created footers template in var/templates/lists/<LIST_ID>/list:member:regular:footer.txt and var/templates/lists/<LIST_ID>/list:member:digest:footer.txt > I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used where did you put it? > in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. > > In the logfiles I found an error and a warning: > [code] > ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. > WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer > [/code] It appears you created the new template with Postorius, but there is an issue for Postorius templates. Possibly your Django setting for POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. > Obviously I have a problem with the hostname. I set > [code] > POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 > [/code] > where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost > [code] > wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… > [/code] > will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? If that works, yes. > I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. > > Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. The issue you are seeing has only to do with the fact that the footer is non-empty. It is not related to footer content. It is because you are posting other than text/plain messages and the MUAs you are viewing the mail with are confused by the footer being a separate MIME part. See the FAQ article at https://wiki.list.org/x/4030707 for discussion of this issue in MM 2.1 which is also relevant to MM 3. To disable adding footers entirely, sitewide, create an empty file, readable by Mailman at Mailman's ``` var/templates/site/de/list:member:generic:footer.txt ``` More about templates and search rules is at templates/de/list:member:generic:footer.txt and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

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

by Thomas G

Hi, https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… I changed "sender" for this; # Sender try: from_str = header_to_unicode(message['From']) from_name, from_email = parseaddr(from_str) from_name = unidecode.unidecode(from_name).strip() except (UnicodeDecodeError, UnicodeEncodeError): raise (ValueError("Non-ascii sender address", message)) try: sender_address = from_email.encode('ascii').decode("ascii").strip() except (UnicodeDecodeError, UnicodeEncodeError): if from_name: sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) if not sender_address: sender_address = "unknown(a)unknown.com" else: sender_address = "unknown(a)unknown.com" print("Non-ascii sender addre -- Sender address replaced by ", sender_address) I got this output (example): |Non-ascii sender address -- Sender address replaced by stephaneblipblopstlablipblopgmailcom It's not really perfect, I'm working to do something better, but basically it's works. I think that there is a issue in the original code: Because : "" raise ValueError("Non-ascii sender address", message) "" The second part will be never call: if not sender_address: if from_name: sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) if not sender_address: sender_address = "unknown" sender_address = "{}(a)example.com".format(sender_address) else: sender_address = "unknown(a)example.com" If you bypass : "" raise ValueError("Non-ascii sender address", message) "", by a simple print(), you will get an error due to an unassigned variable (sender_address). Le mar. 30 oct. 2018 à 04:10, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/28/18 12:03 PM, Guiseppin Thomas wrote: > > Hi, > > > > I imported some mbox archives in Hyperkitty. > > > > I have lot issues like: > > > > /\Failed adding message <5b0900ab.1c69fb81.70ab.2f87(a)mx.google.com>: > > ('Non-ascii sender address', <email.message.EmailMessage object at > > 0x7f05f1606048>)// > > //Non-ascii sender address from "Stéphane blipblop <stlablipblop at > > gmail.com>" about [HATLAB][It] Re: A débarrasser ! / > > > > It's probably because "Stéphane". > > > The 'Non-ascii sender address' message comes from > > > try: > > from_str = header_to_unicode(message['From']) > > from_name, from_email = parseaddr(from_str) > > from_name = from_name.strip() > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > raise ValueError("Non-ascii sender address", message) > > Possibly the exception is thrown in parseaddr(), but much more likely, > the email address, not the display name contains non-ascii. > > > Some advise to fix it ? > > > All the other messages should have been imported. If you can find and > fix the 'bad' ones in the mbox, you can make a new mbox with just those > and import that. You could also import the entire mbox with fixed > messages. The already added ones won't be re-imported because of > duplicate Message-ID:, but it's extra processing. > > If the actual bad message From: header is > > From: Stéphane blipblop <stlablipblop(a)gmail.com> > > or > > From: Stéphane blipblop <stlablipblop at gmail.com> > > That shouldn't cause the error, so I'g guessing that 'blipblop' is not > the actual value and the actual value in <stlablipblop at gmail.com> has > non-ascii. > > -- > 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

[MM3-users] Moderated unsub requests are not provided by mailman3 service

by Joachim Schrod

Hello, I'm new to Mailman3; being in the process of moving some mailing lists from an ancient Mailman2 installation to a new host. (These lists are not big; they are used to organize a yearly holiday of roughly 50 persons.) As part of the migration; I'm testing out actions that were done on the previous Mailman2 instance. Currently, I stumble over confirmation of unsubscribe requests. Unsubscribe policy of the list is "Moderate". I subscribed an email address and used "Mass operations - Mass removal" in Postorius to unsubscribe it. (Actually, since it didn't work at first, I used that dialog twice.) Now I, as the mailing list owner, get a daily email vom Mailman3 that there are pending unsubscription requests that I shall approve. (Both unsubscription requests for the same email requests are listed in that email; doublettes are not handled properly.) The unsubscriptions requests are not shown in the web interface. I suppose they should appear in the UI section "Subscription requests", either as "Pending Approval" or "Pending Confirmation". (Frankly, I don't understand the difference between these two options at all.) Tracing the communication between Postorius and mailman3 service, I see that Postorius asks mailman3 about pending unsubscriptions with the following requests: 1) GET /3.1/lists/MBOX@DOMAIN This returns list information. 2) GET /3.1/lists/MBOX@DOMAIN/requests?token_owner=moderator This returns a JSON structure with properties "start" 0 and "total_size" 0. 3) GET /3.1/lists/MBOX@DOMAIN/requests/count?token_owner=moderator This returns a JSON structure with count 0. 4) GET /3.1/lists/MBOX@DOMAIN/held/count This also returns a JSON structure with count 0. When one wants to see the "Subscriptions pending user confirmation", there is also a GET to get the requests of token_owner=subscriber; returning the same result as the request for token_owner=moderator above. Looking at the mailman3 database, there are 2 records in table `workflowstate' that are in step `unsubscribe_from_restore' who describe the open unsubscribe requests. I could not identify any other database records that are obviously relevant to that issue. (Since this is a fresh test setup, the database is small enough that I can still look at any record in the database.) Why does Mailman3 have no info in its JSON responses about the unsubscription requests that I get informed about daily? Any hints where I could look further are dearly accepted. System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; both on Debian 11 (bullseye). I know that this is out of date; thus a definitive info "this is fixed by now" is quite OK for me. (Debian upgrade is planned as the next action after getting Mailman3 to work for that use case.) Hope that someone can guide me towards a solution, Joachim PS: The list configuration that I actually want is something completely different: mass unsubscription by the mailing list owner without moderation; but moderation for individual unsubscription requests. This is a mailing list where every year all subscribers are setup anew. Subscribers are email-illiterate users who may know WhatsApp at best, which brings its own problems. No person (un)subscribes herself or himself; all is done by the list owner. Unsubscription would mean cancelling the holiday participation -- the list owner must then ask if that's really wanted... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

11 months, 1 week

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Wed, Feb 27, 2019, at 12:04 PM, Danil Smirnov wrote: > Hi, > > After upgrading my PostgreSQL from 9.2 to 9.6, I was able to up postorius container. > But when I try to open UI, I'm getting 500 Internal Server Error all the time - either for /postorius/lists/ as well as for /admin/. > I've checked all the logs but haven't found anything there which can bring some light at the issue. Just error 500... > > I've checked: > - nginx logs: just error 500 > - mailman-web docker container logs: no errors > - mailman-web (postorius) logs: mailmanweb.log is empty, uwsgi*.log with some errors > - mailman-core logs: no errors > > I've also called curl localhost:8000 from inside the mailman-web container and got the same 500 Internal Server Error. > > Could you guys advise what else should I check? We would need to figure out if it is Core or Web causing the 500 errors. So, what errors are you looking at in uwsgi*.log? Do you see any successful requests in mailman core's mailman.log? > > With my best regards, > Danil > > > пт, 22 февр. 2019 г. в 09:12, Danil Smirnov <danil(a)smirnov.la>: >> Hi Abhilash, >> >> Thank you for the quick resolution, but I'm still unable t start the container: >> https://github.com/maxking/docker-mailman/issues/309 >> >> DB migrations are failing. >> >> Danil >> >> вс, 17 февр. 2019 г. в 12:21, Danil Smirnov <danil(a)smirnov.la>: >>> Hi Abhilash, >>> >>> Thank you for the explanation, I've created a report: >>> https://github.com/maxking/docker-mailman/issues/307 >>> >>> Danil >>> >>> >>> >>> сб, 16 февр. 2019 г. в 18:40, Abhilash Raj <maxking(a)asynchronous.in>: >>>> On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote: >>>> > Hi, >>>> > >>>> > I'm interesting in Mailman3 deployment with archiving feature completely >>>> > disabled. >>>> > >>>> > I've tried to deploy Core + Postorius using this docker-compose >>>> > template: >>>> > https://github.com/maxking/docker-mailman/blob/master/docker-compose-postor… >>>> > >>>> > Unfortunately Postorius version came with this template is quite outdated: >>>> > 1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image I >>>> > see version 1.2.3. >>>> > >>>> > I've also checked image maxking/postorius:rolling but it seems >>>> > irrelevant/broken (container exits with error). >>>> > >>>> > Are there newer Postorius docker image I can use? >>>> >>>> No, but if you could report the failure and error that you, maybe the Maintainer can help >>>> fix that issue you have? >>>> >>>> P.S. I maintain those images. The Postorius image is kind of neglected since there are >>>> fewer people using it, but I'd be happy to fix any error that you see. >>>> >>>> Package ugprades are merely a version number bump in Dockerfile :) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

6 years, 8 months

Search results for query "dO"