Search results for "2021" - Mailman-users

Re: New release candidates for Postorius and Hyperkitty

by Abhilash Raj

+cc: mailman-usersmailman3.org for more visibility. On Sat, Jan 16, 2021, at 2:20 PM, Ruth Ivimey-Cook wrote: > Hi, > > Is there a recommended method for upgrading an existing, running, server > from Python 3.6 to 3.8, especially in such a way as to enable downgrade > if something breaks? It depends on how did you install Mailman. If you installed using virtualenv, you can create another virtualenv and install new versions, that use the same configuration and switch between new and old versions, > > [When I upgraded a server distribution without enough preparation, it > broke mailman3 because I lost python3.6, and getting it working again > needed a lot of work to reinstall it without zapping needed state.] > > Regards > > Ruth > > > On 16/01/2021 20:38, Abhilash Raj wrote: > > Hey Everyone, > > > > Happy new year to everyone! > > > > I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! > > > > These include both new features and bug fixes. Complete change log for each components: > > > > Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > > > These releases require Mailman Core 3.3.2 and Python 3.6+. > > > > Since these are pre-releases, you can install them using: > > > > $ pip install --pre --upgrade postorius hyperkitty > > > > Or you can also specify the exact versions: > > > > $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' > > > > Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. > > > > If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. > > > > [1]: https://docs.mailman3.org/en/latest/translation.html > > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ > > -- thanks, Abhilash Raj (maxking)

4 years, 5 months

Re: Can login at /admin, but cannot login at the account/login page.

by Abhilash Raj

> On Aug 15, 2021, at 11:33 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 8/14/21 9:34 PM, Stephen J. Turnbull 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. > > > Not quite, but very soon. > > >> pabsta(a)gmail.com writes: >> > 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. > > > I'm sure that's right. > > >> > 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 > > > I see in the above `upstream: "http://127.0.0.1:8006/accounts/login/",` but in your settings > > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" > > > I suspect you may be getting a redirect from http to https which is losing POST data and you need to change > > proxy_pass http://127.0.0.1:8006; > > in your nginx configuration to > > proxy_pass https://127.0.0.1:8006; > > or set > > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" > This configuration actually doesn’t really dictate connection related configs, but mostly, the protocol to use in the emails generated by django-allauth to verify email and such. It shouldn’t have affect on the problem IMO. > -- > 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, Abhilash Raj (maxking)

3 years, 10 months

Re: error when starting the mailman executable from the venv

by Christian Stalberg

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/

4 years, 4 months

Internal Server Error: /mailman/accounts/fedora/login/

by Kilian Kilger

Hi mailing list, I own a mailman box. I regularily (many times a day) get mail with an internal server error. I am using Debian and the included mailman3-full package. I guess someone tries to hack my instance. But I don't understand why this leads to the internal server error. I am also wondering why the request URL is /mailman/accounts/fedora/login, as I am using Debian (understandable if the request happens via an outside trigger). I have no clue about the internal workings of mailman though. I use Debian 11 bullseye and thus version 3.3.3. I can trigger the internal server error by myself by visiting the request URL. Despite these emails the instance seems to work fine. Best regards, Kilian. Internal Server Error: /mailman/accounts/fedora/login/ TypeError at /accounts/fedora/login/ _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request Method: GET Request URL: <URL>/mailman/accounts/fedora/login/?process=login&next=/mailman/accounts/password/reset/ Django Version: 2.2.24 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: Fr, 17 Sep 2021 06:12:57 +0000 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', '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') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view 71. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 97. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in get 56. return self.post(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in post 67. client = _openid_consumer(request) Exception Type: TypeError at /accounts/fedora/login/ Exception Value: _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request information: USER: AnonymousUser

3 years, 9 months

Re: content filtering in version 3.1

by Simon Handfield

Thanks for your quick reply, Mark. I see, I've retried without the -l switch and the shell returns without error. The --help switch returns: # mailman shell --help usage: mailman shell [-h] [-i] [-r RUN] [--details] [LISTNAME] positional arguments: LISTNAME The 'fully qualified list name', i.e. the posting address of the mailing list to inject the message into. This can be a Python regular expression, in which case all mailing lists whose posting address matches will be processed. To use a regular expression, LISTNAME must start with a ^ (and the matching is done with re.match(). LISTNAME cannot be a regular expression unless --run is given. Thanks once again, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 12 May 2021 14:22 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: content filtering in version 3.1 On 5/11/21 8:45 PM, Simon Handfield via Mailman-users wrote: > Hi everyone, > > I'm sorry to resurrect this thread from so long ago but it appeared to provide exactly the answer I was looking for, trying to manage pass_types in 3.1.1 on Ubuntu 18.04. > > GNU Mailman 3.1.1 (Between The Wheels) > > Unfortunately when I run: > > ./bin/mailman shell -l [list address] > > I receive: > > usage: mailman [-h] [-v] [-C CONFIG] > {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} > ... > mailman: error: unrecognized arguments: -l > > Can anyone advise how I can use the -l switch to manage this setting for a list? Older versions of Mailman core did not support the -l/--listspec option for mailman shell. They expected the listname as an argument as in ``` mailman shell list(a)example.com ``` What does ``` mailman shell --help ``` show in your case? -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

4 years, 1 month

Imported Digest Settings

by Brian Carpenter

I am still seeing digest formatting issues with the import of Mailman 2 lists into Mailman 3. I am running the latest stable version of Mailman 3 core which is 3.3.3. This is what my client reported: > For the last three REDACTED digests I have been getting unusual and > unreadable characters? See example below. > >> Begin forwarded message: >> >> *From: *REDACTED >> *Subject: *REDACTED*Digest, Vol 2453, Issue 2* >> *Date: *February 13, 2021 at 12:30:24 AM PST >> *To: *REDACTED@REDACTED >> *Reply-To: *REDACTED@REDACTED >> >> �P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ >> [��X��ܚX�H �XH [XZ[ �[� H Y\��Y�H �] �X�X� ܂�� H� [ � ‚] [�\�\]Y\� >> [�ܙ‚�[�H �[� �XX� H \��ۈ X[�Y�[�� H \� ] �] [�[#<^_NSEDR_^#<ۙ\� >> [�ܙ‚�� [� �\ Z[�� X\�H Y ] [�\� �X�X� [�H �� ] \� [ܙH � X�Y�X [� �N� >> �۝ [� � و S� Y�\� �� ^I�� X�΂� K� �N� [� \� � [\ � >> �� ] >> \�B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKB�Y\��Y�N�B� >> ] N� �K L� �X��HL ��N�� L ��N� �� ] \� �� ] >> \�]\�X˘��O��X�X� � � S�H �N� [� \� � [\ • Έ �� [�Y[ �� [�Y[ >> ]ܙ[��K�Y O��Έ � S� H �[\ ] ^Y\�� [� \�] [ۘ[ �] �ܚˈ� [� >> [�ܙς�Y\��Y�KRQ � Q� >> � >> KM�� M� N Q �P��PL �P �] \�]\�X˘��O��۝ [� U \ N� ][ \ \� �[ \�] >> ]�N‚X��[� \�OP\ KSXZ[ M ь P�KL�L�KM ��KP�KM��̌#<^_NSEDR_^#<͌ >> L �Y\� H [�� YX�� H \� Y �[[^H [� � X� \� [�� Y] [�� Y�ܙH H Y� >> \� [� ] �Y[\� �\� Y [� �� \�H ��\ ] H ] [ � H �\� ۙH و \� � Y [� ˈ [ >> [�� ]�\�] [�� H �]�H YK �\� [� ]�Y X[ \ \�� [� �\�[ [�� X� [ۜˈ H >> �\�[ [�� X� [ۋ �H �\� �\� H [�� [\ ܝ [� [� �[ XX� H \� � H ۸�&] [�� >> H �]�H [ و \� � Y [� � H �[YH X] \�X[ ˈ ] �\� H ]X� [ܙH >> \�#<^_NSEDR_^#<ۘ[ ^�Y \ ��X� �܈ XX� � Y [� � H ��Y� \� �� ] H [� >> ܚ] [� � Y� H �]�H YH H \�� Y [� ]�[� ] � �� Y\� >> [�H ]�H � �H � � ۛ�� Y� ] \�JK ��\� �܈ �^[ۙ ] � [�� ] \��[� >> ��H ^H T ۙB� ۈ �X�L So the questions I have are: 1. Why does the formatting of digests change for some members when coming from MM2 to MM3? 2. What proble does the above example reveal? 3. What is the best approach to mitigate these issues? What I did: I had the client change the list member's digest setting from plain-text to mime. Was that the right instruction to do? -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 4 months

Re: A new issue with installation

by Abhilash Raj

On Sat, Feb 20, 2021, at 9:28 AM, Abhilash Raj wrote: > > > On Sat, Feb 20, 2021, at 8:51 AM, Brian Carpenter wrote: > > As usual, a new issue has arisen with installing Mailman 3. It seems > > Postorius and Hyperkitty want to install a module called cryptography. > > Which I am unable to install because of this: > > > > error: Can not find Rust compiler > > You need to install a Rust compiler. Depending on which distro you are > using, you can run `sudo apt install rustc` or same command with `yum`. Also, it is possible depending on your distro that packaged Rust compiler is too old. cryptography requires a more recent version of Compiler, 1.45 is the min supported version I think. FAQ: https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-wi… You can skip the Rust components by setting `CRYPTOGRAPHY_DONT_BUILD_RUST` but that would work just for this release and you won't be able to skip from the next release of cryptography. > > > > > Question 1: Is cryptography a new addition to Hyperkitty/Postorius? Or > > was cryptography always included and something else is different about > > my installation process? > > It was always included. The recent change has been in the underlying > security library to use Rust language in some parts of it. That has resulting > in 100s and 1000s of applications/CI and other stuff failing. The fix is quite > simple in most cases, just install rust compiler. > > > > > "Building wheels for collected packages: hyperkitty, django-haystack, > > django-mailman3, mailmanclient, robot-detection, rcssmin, > > django-allauth, cryptography" > > > > Question 2: Will Hyperkitty/Postorius work without cryptography? I > > haven't proceed with this installation once I received the above error. > > It is a transitive dependency for P/HK and is required by django-allauth. > I don't think you can skip it. > > > > > Question 3: Are there any Mailman 3/Postorius/HK documentation that > > addresses with the installation of cryptography? > > Since this issue arose about 2 weeks ago, there isn't anything there yet. > > > > > > > > > -- > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

4 years, 4 months

Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

Don’t use the code I posted, use the new patches from Mark if you want to apply them. The patches are https://gitlab.com/mailman/mailman/-/merge_requests/932 https://gitlab.com/mailman/mailman/-/merge_requests/933 I’ve applied both of them to my prod box now and they are working well. The only catch is 932 will include an update to NEWS.rst that won’t apply because the contents are different. Thats fine it doesn’t impact the patch. All I did was download both patches using the plain diff option when you click on the download icon at the end of the line “Request to merge msapiro:clean into master”. Then on my mailman server (I did it in my test environment first) applied the patch in order (your paths, locations, install may differ from mine, this works for me): $ cd /opt/mailman/venv/lib/python3.6/site-packages/mailman $ patch -p3 < /tmp/932.diff $ patch -p3 < /tmp/933.diff And then restart mailman. This also assumes you are running -Simon --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 10 Nov 2021, at 10:16 am, Joel Lord <jpl(a)ilk.org<mailto:jpl@ilk.org>> wrote: I got one of these yesterday as well. On 11/9/2021 7:06 PM, dancab(a)caltech.edu<mailto:dancab@caltech.edu> wrote: > We're also getting bit by this due to messages being replaced with the notice below. > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list". > > I'm looking to apply the patch above. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> > To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> > -- Joel Lord _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>

3 years, 7 months

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

by matthew＠alberti.us

Steve, Thanks for the response. I put " HYPERKITTY_ALLOW_WEB_POSTING = False " in and that has worked as intended. Sorry I wasn't more clear in my previous e-mail. I was trying to say that Django-recaptcha might be a good way to gate the signups, but it looked like mailman code would have to be changed to work with djangi-recaptcha. But it seems not effective enough to be worth pursuing. For now, maybe disabling posting via hyperkitty will be enough. Any SPAM sent in from other sources will be subject to scanning. - Matt Alberti -----Original Message----- From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Thursday, August 26, 2021 1:36 PM To: matthew(a)alberti.us Cc: mailman-users(a)mailman3.org Subject: [MM3-users] Unwanted E-mail to Maillists Submitted via Postorius Interface matthew(a)alberti.us writes: > I’ve seen a recent uptick in SPAM messages making it into > mailing lists. Looking at the raw, it seems that the e-mails are > being submitted thru the Postorius/Hyperkitty “Start a New Thread” > interface. Is there a way to turn that off? I think this is HyperKitty only. Postorius doesn't know anything about posting or distributing posts. You can disable web posting by setting HYPERKITTY_ALLOW_WEB_POSTING = False (as above, no quotation marks etc) in settings.py. I don't know much about HyperKitty, so I'm not sure where that file lives in your installation. > Part of the problem is that our anti-spam system RSPAMD trusts the > mailman-web IP… so it doesn’t scan things originating from > there.. %G 笘ケ%@ You know your organizational constraints, but it's a bad idea to trust any web-facing application that can send email to be responsible about it. :-( > Another uestion: Is there a way to implement captcha, or is > there a recommended gate that can be put in the signup process? Here's the most recent technical discussion I can find. Archived-At: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message /RSZLMKPASCTKFY63RKGPGNCVVPAB5C4M/> 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. > Apparently bots are finding a way thru the signup process, and then > sending messages to the list via the Postorius web interface. There > seems to be a Django plugin for it; but it appears the Mailman code > would have to be adjusted to implement it. I don't think so, because Mailman (that is, HyperKitty and Postorius) delegate authentication to Django. Why do you think Mailman code needs to be adjusted? Steve

3 years, 10 months

Mailman container images 0.3.12 is now out

by Abhilash Raj

Hey Everyone, I have just tagged release 0.3.12 on Github for container images for Mailman 3[1]. This release includes the fix for CVE-2021-40347 that was announced earlier today. For the folks using 0.3 or 0.3.11 release tags, it is highly recommended that you upgrade to this release. This release also bumps the version of Mailman Core to 3.3.4, Mailmanclient to 3.3.3 and Django-mailman3 to 1.3.7. Note that is since the main and v0.3.12 branches are different in many ways, the default documentation[2] and the docker-compose.yaml files in the main branch aren't accurate if you are using the stable release. Please refer to the README[3] at v0.3.12 tag in the Github repo for more accurate docker-compose.yaml and documentation. The project has grown large enough that we need to start versioning the documentation, if someone has experience with versioning docs using Github pages and mkdocs, then I very much need some help here! For those of you who are using the rolling release, it is recommended that you **don't** upgrade to this stable release. The fixes have been pulled into the rolling tags too, so just make sure that you upgrade to the latest published version of rolling release, which as of this writing should be based off on fda837f8d15540e190992c30f7971f50fca54dac commit[4]. This might not be the latest by the time you upgrade if I add a new commit, so look for versions published after 4:00 PM PST 9/5/2021. I am also working on cutting a new release, 0.4.0, which is backwards incompatible with the setup required to talk to web server and MTA (hence the minor version bump!). That should bring the rolling releases and stable releases closer to each other and add improvements around not needing static IPs in the docker network anymore, plus several bug fixes. If someone wants to test the upgrade to 0.4.0 from 0.3 release and is willing to try out the instructions at [5], it would give me some confidence in cutting out the release sooner. The only thing stopping the release of 0.4.0 images is that I haven't verified if the upgrade from 0.3 is documented enough or not. For all the registries listed in README[6], I am still trying to push to Quay (maybe I need to just skip pushing to Quay :-). So, just use the other two to pull the images, Github (ghcr.io) has more generous pull download policy for un-authenticated users though. [1]: https://github.com/maxking/docker-mailman/releases/tag/v0.3.12 [2]: https://asynchronous.in/docker-mailman/ [3]: https://github.com/maxking/docker-mailman/tree/v0.3.12 [4]: https://github.com/maxking/docker-mailman/commit/fda837f8d15540e190992c30f7… [5]: https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release [6]: https://github.com/maxking/docker-mailman#container-registries -- thanks, Abhilash Raj (maxking)

3 years, 10 months

Mailman-users search results for query "2021"