Search results for "2021" - Mailman-users

Re: Unwanted E-mail to Maillists Submitted via Postorius Interface

by Stephen J. Turnbull

Brett Delmage writes: > On Thu, 26 Aug 2021, Stephen J. Turnbull wrote: > > > However, it turns out that bots are almost as good at solving captchas > > as humans, and they can retry a lot faster. Captchas are also really > > horrible from an accessibility perspective. > > I have to disagree. > > I previously put a captcha on a Joomla website which stopped 100% of all > bogus account signup attempts. > > What was it ? "How many letters are in the word 'jazz'"? > This captcha is fully accessible, too. Of course, point taken. I've done similar things, and know quite a few such anecdotes. It's a good method, as long as *only a few of us use it*. But if enough people use it, patterns will show up, and we'll get into a "proof of waste" race with the spammers as we try to come up with logic puzzles people can solve but spammers' ML can't. I don't think it really addresses the issue that attackers can solve it easily if they want to, and will eventually automate that solution, although it does address the issue of accessibility (mostly -- I am not an expert but I wouldn't be surprised if long-time screen reader users are relatively poor spellers!) And it's not a satisfactory solution for a lot of our users. We can't safely add enabling functions to Mailman, because I'm sure there are a dozen Spamming as a Service (SpAAS) groups out there with Mailman 3 clone repos. So you need a skilled admin to implement custom CAPTCHAs. > If there's a captcha problem out there, it's because too many people just > use the same old, same old - Of course they do. After all, that's what software is for -- very cheaply using others' solutions for common problems. In this case, though, the "problem" is smart -- it's human attackers and their tools. > which is worth the bots cracking because it is used everywhere. That evaluation is close, but not exact in the age of SpAAS. If they want you, they'll get you, it's trivial for an open-subscription site. And if they need a human to crack your trivial CAPTCHA, a smart spammer (or even somebody who hates you for banning them from your comments) will add it to their box of tricks. I bet you'll get tired sooner than they do. Eventually it will make it into kiddie-scripts. The other thing is that if such simple captchas become popular, you know that the pros will start scanning sites for them just to make a database of patterns, and add hacks for any popular ones (or if they're smart, for every pattern they find -- I bet on a regular basis they'll get as lucky as I did when I stopped Klez, and then Fretham too, with just "iframe.*height=1"). Steve

3 years, 10 months

Re: Mailman 3 centos7 installation issues

by Abhilash Raj

On Wed, Mar 24, 2021, at 10:01 AM, bader(a)cchmc.org wrote: > So I am working with our Linux admin to install mailman3 in centos7 > following this instructions > https://docs.mailman3.org/en/latest/install/virtualenv.html# (and > adjusting for centos versus Debian) > The install went fine with the command “pip install wheel mailman > psycopg2-binary”until the config file. /etc/mailman3/mailman.cfg > > > The /etc/mailman3 directory did not get created? Should it have? It should not, `pip` cannot create these directories. You have to create them manually. > > We created it and the config file > > But “mailman info” throws errors > > venv) [mailman@bmimailmandr2 var]$ mailman info > Traceback (most recent call last): > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2336, in _wrap_pool_connect > return fn() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 364, in connect > return _ConnectionFairy._checkout(self) > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 778, in _checkout > fairy = _ConnectionRecord.checkout(pool) > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 495, in checkout > rec = pool._do_get() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/impl.py", line 140, in _do_get > self._dec_overflow() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ > with_traceback=exc_tb, > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ > raise exception > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/impl.py", line 137, in _do_get > return self._create_connection() > File > "/opt/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/pool/base.py", line 309, in _create_connection > return _ConnectionRecor This seems to be trying to connecting to database. Have you setup the database as described in https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-database and then added the right values in mailman.cfg you created? You will see a [database] section with a placeholder MYPASSWORD to put your database password. > > I suspect it is not using the config file at /etc/mailman3/mailman.cfg It should do that by default, unless you have a `mailman.cfg` in the current working directory. > But we do not even see a mailman service in > /etc/systemd/system/mailman3.service. `pip install` cannot creates these files. You have to manually create both `/etc/mailman3/mailman.cfg` and the above systemd service file. I’ll update the docs to be more explicit about this. > > Also, we are using python 3.6, will that be a major issue? or should > spend the time to install 3.7 from source? 3.6 should be okay for now, we do run CI for 3.6 so we will know if there is any breakage and can let the users know about it. We do run atleast one server on 3.6 ourselves. It doesn’t EOL until end of this calendar year. > _______________________________________________ > 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, 3 months

error changed after restart (was: KeyError: 'get_requests_count' after an upgrade)

by Guillermo Hernandez (Oldno7)

I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 5 months

Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 20:52 +0100, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > On 13/2/21 20:00, Mark Sapiro wrote: > > On 2/13/21 2:33 AM, Guillermo Hernandez (Oldno7) via Mailman-users > > wrote: > > > But... here is a thing that I can not understand: If the source (the > > > .po > > > file) is from november 7th, it doesn't matter how many times you > > > recompile it: the result will be the same. > > Correct, but the point is if you download the latest > > gnu-mailman-mailman-es.po from weblate, and compare it to the Nov 7 > > file > > in the distribution, you will find they are identical, so it it appears > > that the weblate translation hasn't changed since that time. > > > > If there are issues in this mailman.po, they exist in weblate too and > > need to be fixed there. > > That clarifies all. Thanks. As I said in my previous message, I'll wait > for the next upgrade and hopingly the translations done after 7h of > november (by others and me) will be there. I've visited Weblate, all Spanish strings are translated. Spanish is 100% translated, but, none of them have been "approved", whatever that is. It seems that a reviewer needs to approve the translation in order for them to be incorporated or released or whatever. I was sure I had reviewed everything between November 7th and the day Abhilash announced the release candidate and asked for translation review, but nothing has made it to the released version. Maybe there's something in the translation flow that we are doing wrong. I'm starting to miss the good old days when Mailman 2 translators just downloaded the .po files and returned them :-) > > Also note that the translations on weblate only affect strings in the > > core code. The Mailman core templates are not currently translated in > > weblate and there are currently no Spanish language templates. One > > would > > need to create Spanish translations of all the templates in > > < > > https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en > > > > > and submit a merge request to add them to a mailman/templates/es/ > > directory. > > > I will make the template translations locally, test them, and then, if > they are yet lacking in the main repo, follow your suggestion. I'm a bit short on time, but I'll help Guillermo with that, at least reviewing or doing a second pass. I'm not proficient enough to speak about Mailman core templates, but for Django templates, there is a nice tag for marking text with translations in the .mo files ... -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 4 months

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

Re: Strange messages after upgrading Mailman3

by Allan Hansen

I asked the poster of one message what he had done. Apparently, he had put the list address (just one list, according to him) in the Bcc: field. The message was then held for moderator approval and, when approved, sent out without a body. Another message was stopped because it did not have a subject field. Again, it was approved and then sent out without a body. From what I can see (the hold messages are sent to me as well), the messages were stripped after approval, as the approval messages have the message bodies. I will try to ask my moderators not to approve messages that are held by the server and instead reply to the senders and discard the messages. Yours, Allan P.S.: I had hoped that the upgrade would now allow the moderators to see the list of members, as that is enabled for each of my lists. It's now our top issue, with the change-of-address issue made easier. If moderators should not see the members list then maybe a third option on the menu should be 'Only list owners.' But it would be good for the moderators to see the list, as well as being able to subscribe and unsubscribe members. On 12/5/22, 9:39 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 12/5/22 08:56, Allan Hansen wrote: > Thank you, Mark, as always. > > We upgraded to the latest versions: > > Mailman Core Version GNU Mailman 3.3.7 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.9.2 (default, Feb 28, 2021, 17:03:44) [GCC 10.2.1 20210110] > > Also, I don't have any umbrella lists. I need more information about this. As far as I know, this can only happen with messages that are cross posted to multiple lists and held for moderator approval on more than one list. This should have been fixed in Mailman 3.3.6 by <https://gitlab.com/mailman/mailman/-/merge_requests/932>. This should never happen with a post that is delivered to members without being held. Also, I think when this happens to a delivered post, the post in the archive will also have the content lost message. I would like to get as much information as possible about the circumstances when this happens. In particular, was the post held for moderation, was it posted to multiple lists, for how many lists was the content lost. Also, it may help to see the full raw message with the content lost notice. (If there are privacy concerns you can send these to me off 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/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/33OOQ4DNXTJUNT65CD2KHMOSCAIMRSLL/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/jpeg Name: members.jpg

2 years, 7 months

Re: Hyperkitty 403 Forbidden Error

by Josef Dietl

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, '*'. (Asterisk makes a difference, see at the bottom) - 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. - 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. Mailman info says GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] . REST root url: http://localhost:8001/3.1/ Hyperkitty is 1.3.4, Postorious is 1.3.4, too. 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" [.] - - [19/Jan/2022:22:43:27 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB478573911C2A81B8898527E6C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:43:28 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . repeated many times, there seems to be quite a few testmessages in the queue . [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&key=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=6xpENHLEHQ0kD53vXt5RpKzPDOsKbcN9 HTTP/1.1 " 403 175 "-" "python-requests/2.25.1" [.] - - [19/Jan/2022:22:46:50 +0000] "POST /hyperkitty/api/mailman/archive?key=[.] HTTP/1.1" 403 166 "-" "python-requests/2.25.1" . again repeated many times . [.] - - [19/Jan/2022:22:46:51 +0000] "GET /hyperkitty/api/mailman/urls?mlist=demo%40lists.pro-digi-par.de&msgid=AM0PR0 4MB4785430188B9C0E8DF248231C2599%40AM0PR04MB4785.eurprd04.prod.outlook.com&k ey=[.] HTTP/1.1" 403 175 "-" "python-requests/2.25.1" I'd appreciate a new idea where I could look for clues. Thanks a lot, Josef

3 years, 5 months

Re: Problem with languages

by Abhilash Raj

> On Mar 20, 2021, at 10:19 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Andreas Barth writes: > >> Well, I personally wouldn't be so afraid, but that might come from the >> fact that I know the debian ecosystem way too well :) > > FWIW I've run a testing + a very few pinned to sid[1] for 15 years now, > and never had unexpected problems with testing packages themselves, > and only very rarely with distro issues (mucked up dependencies where > I couldn't install the current version of some package as specified in > testing). > > J. Guenther writes: > >>>> Also, translations had been the reason for some discussions lately, so >>>> this is still some work-in-progress. (Also on the git version I'm >>>> using, there are more texts in English than I'd wish for.) >>> >>> What I hear is that this is a common issue and I probably should get >>> along with it for now!? > > As Andi says, there was a glitch in the Weblate (IIRC) to Mailman > sources pipeline which should be fixed now, but for specific languages > you kind of have to track the completion rate with that translation > community. Probably there's a way to check on Weblate itself. Yeah, you can go the project page on Weblate and check completion rate for a specific language. For example this is the page for Postorius. https://hosted.weblate.org/projects/gnu-mailman/postorius/ > If > Weblate seems to be much farther along than Mailman git, ping us, it's > still a pretty manual process. For web interface (Postorius, django-mailman3 and Hyperkitty) it is only manual to the point that someone has to click “Merge” ;-) The process is fairly automated and new translations are sent as Merge Request[1] against our Git repos nightly. Since each commit adds a Merge Commit, I sometimes wait a little for 4-5 commits to pile up before merging them. But if there are large number of people installing from Git for up-to-date translations, I wouldn’t mind merging them asap. We definitely merge everything before a release is made and translations in a released version will definitely lag behind the Weblate for any changes made after the release. Core has a bit of manual work needed to copy translations from .po files to actual template files (.txt), but hopefully I or someone else will be able to fix that soon. It just needs a script to read from all the language specific .po files and write the translated templates to individual .txt files (where Core expects them to be). [1]: Like this one, for example, https://gitlab.com/mailman/postorius/-/merge_requests/618 > > Regards, > Steve > > Footnotes: > [1] These are all applications that I had extensive experience with > install from source, and still want quite recent versions. > > > _______________________________________________ > 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, 3 months

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

Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Kimmo L

> What does mailman conf -k anonymous_list_keep_headers > show, and what is the content of mailman/handlers/cleanse.py? Command output: [mailman] anonymous_list_keep_headers: And content of mailman/handlers/cleanse.py: # Copyright (C) 1998-2021 by the Free Software Foundation, Inc. # # This file is part of GNU Mailman. # # GNU Mailman 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. # # GNU Mailman 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 # GNU Mailman. If not, see <https://www.gnu.org/licenses/>. """Cleanse certain headers from all messages.""" import re import logging from email.utils import formataddr, make_msgid from mailman.config import config from mailman.core.i18n import _ from mailman.handlers.cook_headers import uheader from mailman.interfaces.handler import IHandler from public import public from zope.interface import implementer log = logging.getLogger('mailman.smtp') elog = logging.getLogger('mailman.error') @public @implementer(IHandler) class Cleanse: """Cleanse certain headers from all messages.""" name = 'cleanse' description = _('Cleanse certain headers from all messages.') def remove_nonkeepers(self, msg): cres = [] for regexp in config.mailman.anonymous_list_keep_headers.split(): try: if regexp.endswith(':'): regexp = regexp[:-1] + '$' cres.append(re.compile(regexp, re.IGNORECASE)) except re.error as e: elog.error( 'Ignored bad anonymous_list_keep_headers regexp %s: %s', regexp, e) for hdr in msg.keys(): keep = False for cre in cres: if cre.search(hdr): keep = True break if not keep: del msg[hdr] def process(self, mlist, msg, msgdata): """See `IHandler`.""" # Remove headers that could contain passwords. del msg['approved'] del msg['approve'] del msg['x-approved'] del msg['x-approve'] del msg['urgent'] # We remove other headers from anonymous lists. if mlist.anonymous_list: log.info('post to %s from %s anonymized', mlist.fqdn_listname, msg.get('from')) del msg['from'] del msg['reply-to'] del msg['sender'] del msg['organization'] del msg['return-path'] # Hotmail sets this one del msg['x-originating-email'] # And these can reveal the sender too del msg['received'] # And so can the message-id so replace it. del msg['message-id'] msg['Message-ID'] = make_msgid() # And something sets these del msg['x-mailfrom'] del msg['x-envelope-from'] # And now remove all but the keepers. self.remove_nonkeepers(msg) i18ndesc = str(uheader(mlist, mlist.description, 'From')) msg['From'] = formataddr((i18ndesc, mlist.posting_address)) msg['Reply-To'] = mlist.posting_address # Some headers can be used to fish for membership. del msg['return-receipt-to'] del msg['disposition-notification-to'] del msg['x-confirm-reading-to'] # Pegasus mail uses this one... sigh. del msg['x-pmrqc'] # Don't let this header be spoofed. See RFC 5064. del msg['archived-at']

2 years, 9 months

Mailman-users search results for query "2021"