Search results for "Postorius" - Mailman-users

Re: HTML email sent to lists migrated from Mailman 2.1

by Mark Sapiro

On 4/15/19 8:21 AM, Nate Coraor wrote: > > I have some lists migrated from 2.1 that are stripping the HTML parts > (perhaps all attachments?) from messages despite the options to do so not > being enabled and lynx not even being installed. I'm trying to get a new > list to behave the same way so I can figure out what's going on without > spamming a production list, but have been unsuccessful: despite setting > nearly all the list options the same as the old lists, new lists pass HTML > portions and attachments just fine. > > I've verified the settings using mailing list objects directly with > `mailman withlist` on the command line and the only differences are things > that I can't imagine would be related like admin_notify_mchanges, > advertised, and archive_policy. Are there are really old options that can't > be accessed via mailing list objects obtained with `withlist` on the > command line? No, there aren't "hidden settings" The relevant settings are filter_content filter_extensions filter_types pass_extensions pass_types collapse_alternatives convert_html_to_plaintext These are exactly analogous to the MM 2.1 settings filter_content filter_filename_extensions filter_mime_types pass_mime_types pass_filename_extensions pass_mime_types collapse_alternatives convert_html_to_plaintext and should behave the same way. Note that filter_extensions, filter_types, pass_extensions and pass_types are not exposed in Postorius, but can be seen and set via withlist. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

Re: Question about whitlisting a domain for specific mailing list

by Odhiambo Washington

On Thu, Mar 30, 2023 at 6:55 PM Zaheer Abbas <zaheer.psg(a)gmail.com> wrote: > Hi All, > > I need to whitelist a domain for a specific mailing list on your platform. > Only *(a)example.com email addresses should be allowed to post messages to > this list. > > Could you please provide me with documentation or instructions on how to > achieve this? I have already searched the knowledge base and user manuals > without success. > > I believe it was previously available in mailman2 > via Accept_these_nonmembers attribute. > > But I cannot find this attribute anywhere on postorius. > > I am using mailman 3.2.2 > > Any help would be really appreciated. > > Best regards, > I would do this at the MTA level with either a router or a filter (milter in Postfix lingo): IF $sender_address_domain IS NOT "example.com" AND $recipient is "listname@domain" THEN send-to-dev-null. Exim (MTA) has a filter plugin to do this. I don't know about Postfix and Sendmail (as I am not willing to read on your behalf). It is easier that way. I don't remember is Mailman3 has the logic to deal with that, but maybe it does. If you did not manage to find it, then my solution is plausible, no? Filter at the MTA level. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 5 months

Add old email address

by Stephen J. Turnbull

Quanah Gibson-Mount writes: > We've recently migrated our project's email lists from mailman2 to > mailman3. Given the project has been around for a few decades, many people > have used different email addresesses over the years, some of which they no > longer have access to. However, it would be useful to still be able to > associate those emails with a given account. Is there a way that I can do > this as an administrator of the mailman3 system? You can certainly add extra addresses to a Mailman 3 user (I don't know offhand whether/how an admin can do it through Postorius, but the core database certainly has that facility and the REST API allows it). However, this doesn't have the same semantics as in Mailman 2 because Mailman 2 doesn't have users at all. So as an admin how do you know which addresses correspond to particular users? More generally, what do you mean by "associate with an account", and why do you want to do it? Normally I would not ask the latter question, it's your business why you want to do it. But here I'm trying to get at what semantics you want. If I were going to do this for the kind of purposes I can imagine, it would be a matter of informing the users that this feature is available, and I'd ask the users to do it if they care. It seems you have some project goal in mind though. Steve

5 years, 6 months

Exception when rendering certain emails ([Django] ERROR (EXTERNAL IP): Internal Server Error...)

by Matt Blissett

Hi, I get exceptions logged when certain pages in the email archives (imported from Mailman 2) are opened. For example, this thread: https://lists.tdwg.org/archives/list/tdwg-tag@lists.tdwg.org/thread/HZCJQBJ… Could this be a bug in parsing the message? It's deployed using the maxking Docker packages, v0.5.3b1. Thanks, Matt Log follows: Internal Server Error: /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies No exception message supplied Request Method: GET Request URL: https://lists.tdwg.org/archives/list/tdwg-tag@lists.tdwg.org/thread/HZCJQBJ… Django Version: 4.2.20 Python Executable: /usr/bin/uwsgi Python Version: 3.12.10 Python Path: ['.', '', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/usr/lib/python3.12/site-packages'] Server time: Wed, 30 Apr 2025 15:04:09 +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', 'django.contrib.humanize', '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'] 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', 'allauth.account.middleware.AccountMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback (most recent call last): File "/usr/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/views/thread.py", line 269, in replies replies_html = replies_tpl.render(context, request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 175, in render return self._render(context) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/defaulttags.py", line 238, in render nodelist.append(node.render_annotated(context)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/loader_tags.py", line 208, in render return template.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 177, in render return self._render(context) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 1064, in render output = self.filter_expression.resolve(context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/django/template/base.py", line 742, in resolve new_obj = func(obj, *arg_vals) ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/hyperkitty/templatetags/decorate.py", line 42, in render return mark_safe(text_renderer(content)) ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 120, in __call__ return self.parse(s)[0] ^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/markdown.py", line 93, in parse self.block.parse(state) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 457, in parse end_pos2 = self.parse_method(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 216, in parse_method return func(m, state) ^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 368, in parse_block_quote text, end_pos = self.extract_block_quote(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 345, in extract_block_quote end_pos = self.parse_method(m4, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 216, in parse_method return func(m, state) ^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 387, in parse_list return parse_list(self, m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/list_parser.py", line 64, in parse_list groups = _parse_list_item(block, bullet, groups, token, state, rules) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/list_parser.py", line 174, in _parse_list_item block.parse(child, rules) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/block_parser.py", line 457, in parse end_pos2 = self.parse_method(m, state) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mistune/core.py", line 214, in parse_method assert lastgroup ^^^^^^^^^ Exception Type: AssertionError at /archives/list/tdwg-tag(a)lists.tdwg.org/thread/HZCJQBJPACPZZN7UDNKJIPIFNTM7CA63/replies Raised during: hyperkitty.views.thread.replies Request information: USER: mailman-admin GET: sort = 'thread' last_view = '' POST: No POST data FILES: No FILES data COOKIES: csrftoken = '********************' sessionid = '********************'

4 months, 2 weeks

Re: Message Sent to A Re-Created List Results In Error

by Morris Jones

Matt, I think you're describing exactly the problem that's handled by /virtual alias domains/ that were added to support this case. https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… I did an integration between Mailman3 and Zimbra which uses Postfix, and came across the same issue with domains managed by Postfix and Mailman simultaneously. I documented the case in my Zimbra - Mailman3 integration document here: https://gitlab.com/MojoLA/mailman3.3-zimbra-8.8-integration/-/blob/master/m… See if that helps ... Best regards, Mojo On 12/14/20 9:38 PM, matthew(a)alberti.us wrote: > I checked all over the mailman core logs and couldn't find a > problem. But then I noticed that the 550 error was coming from dovecot-lmtp. > I should rename this thread because the actual problem seems to be unrelated > to re-created lists. > > It seems like the actual problem seems to occur in the following > situation: > > * Using Postfix > * Using Dovecot > * /etc/postfix/virtual includes addresses with same domain as mailman > lists. > * An e-mail address subscribed to a mailman list is in the > /etc/postfix/virtual file as an alias (possibly also if destination address > for an alias). > * (Possibly related) E-mail address is also one of the list owners. > > In that environment, Postfix seems to check only 'virtual_transport' > list, which in my case is dovecot-lmtp, and when it doesn't find the mailman > listname@domain entry in there, it sends a 550 user unknown. It seems to be > that it isn't getting passed to 'transport_maps', which is mailman-lmtp. > > When I remove that one address (that is in /etc/postfix/virtual) > from the list of subscribers, I'm able to post again. Interestingly enough, > when I put it back in as a subscriber. I'm still able to post. So it seems > unsubscribing and re-subscribing that address fixed it, or adding an > additional list owner and deleting it fixed it, or some combination of > those. > > I know this might be shaping up to be a very unlikely scenario. But > basically the account is mine, an admin, doing testing before/after a > deployment.. I'll try to create a few test procedures to document the method > to reproduce the problem, and also hopefully fix it. If I can do that, I'll > open another thread. This could also be a postfix config error of some kind, > which is definitely possible if not likely. > > Thanks for reading. > > - Matt Alberti > > > > -----Original Message----- > From: Abhilash Raj <maxking(a)asynchronous.in> > Sent: Monday, December 14, 2020 11:42 PM > To: matthew(a)alberti.us; Mailman users <mailman-users(a)mailman3.org> > Subject: [MM3-users] Re: Message Sent to A Re-Created List Results In Error > > > > On Tue, Dec 15, 2020, at 10:00 AM, matthew(a)alberti.us > <mailto:matthew@alberti.us> wrote: >> I created a list in the Postorius interface, used it, and then deleted >> it. A week or so later, I re-created the list, and things were fine >> thru the creation and subscription process. But when I sent a message >> to the list, a >> "550 user unknown" error was sent back. > > Can you share more error details from the Mailman logs? If 550 error > response was sent, there must be some internal error traceback in the logs. > >> >> >> I tried to determine if this is a known issue by searching the issues >> in Gitlab; but didn't find anything. But wanted to ask if this was a >> known issue or not? > > I personally don't remember seeing such an issue, but Mark or others might > know. > >> >> >> >> Thanks. >> >> >> >> - Matt Alberti >> >> _______________________________________________ >> 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/ >> > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 9 months

Re: Hyperkitty on Debian 12

by Odhiambo Washington

On Mon, Mar 25, 2024 at 5:58 PM Markus Grandpre < markus.grandpre(a)uni-konstanz.de> wrote: > Dear list members, > > when following the instructions to migrate list archives from Mailman21 to > Mailman3 (see [1]), I face the following problem: > > # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 > /var/mailman21/testlist.mbox > python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such > file or directory > > and have no clue, where to find the right <manage.py> file. The command > dpkg returns: > Since we also don't know where it is, why don't you just find it? find / -type f -name "manage.py" Then you can run your command from within the directory where it lives. > > # dpkg -l | grep hyperkitty > ii python3-django-hyperkitty 1.3.7-1 all > Web user interface to access GNU > Mailman3 archives > > In </etc/mailman3/mailman-web.py> I find: > > INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > ... > > Can you please help me? Thank you in advance? > If you need us to help you easily, please consider NOT using the OS packages and use the virtualenv[0] method of installation. [0] 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, 5 months

Re: Welcome message template errors

by Mark

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

1 year, 4 months

problem configuring mailman3 on debian bullseye

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

Hello all, I'm a blind server administrator living in Italy. I use mailman since 2010 and I was very happy for this list manager. When was released the version 3 I started to have many problems to configure it. In this days I installed a new server for my association and I have this problem that I don't know to solve. The server is a debian bullseye. I installed mailman3-full from the standard packege. I'm using nginx as web server. I configured mailman3 and mailman3-web wit https support. All is working fine, but if I attempt to subscribe someone it does not work. I send a subscription e-mail to the address list and I receive correctly the request to confirm subscription. When I reply to the request mailman log gives this error: requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url: /postorius/api/templates/list/listname.domain/list:user:notice:welcome (Caused by SSLError(SSLCertVerificationError("hostname 'localhost' doesn't match either of 'example.com', 'www.example.com'"))) The strange thing is that I configured a domain list.example.com and in the configuration files I put this domain. Mailman3-web works fine I can create lists and make settings. Have you an idea about this issue? Thanks -- 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

2 years, 6 months

Re: Your Dashboard

by Mark Dadgar

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

5 years, 7 months

Re: Ann: Mailman Core 3.3.5 is out

by Odhiambo Washington

@Eggert, I believe you used apt to install and so you have to wait for the package maintainer to avail the upgrades via apt. On Wed, Sep 29, 2021 at 7:48 PM Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org> wrote: > Should I upgrade my Mailman 3.3.3 installed from Debian Bullseye? I would > have > to bypass the Debian installer. Or will there be Debian packages > available? > Same question for Postorius 1.3.6 > > > Am Mittwoch, 29. September 2021, 05:26:47 CEST schrieb Abhilash Raj: > > Hey Everyone, > > > > I just tagged and uploaded Mailman Core 3.3.5 release. > > > > This release includes both bug fixes and some new features. A full list > of > > changes is available here: > > > > > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS > . > > html#news-3-3-5 > > > > You can install this version using pip: > > > > $ pip install mailman==3.3.5 > > > > The release tarball is available on PyPI as well: > > > > https://pypi.org/project/mailman/3.3.5/#files > > > > Thanks to everyone who made this release possible! > > > > Abhilash > > > > > On Sep 19, 2021, at 11:02 AM, Abhilash Raj <maxking(a)asynchronous.in> > > > wrote: > > > > > > Hey Everyone, > > > > > > I just tagged and released Mailman Core 3.3.5rc1 release. > > > > > > This is identical to 3.3.5b1 in code, the only changes that have been > made > > > are in utility scripts and testing configuration.> > > > You can install this version using: > > > $ pip install --pre mailman==3.3.5rc1 > > > > > > If you want to download a release tarball, you can do so from here: > > > https://pypi.org/project/mailman/3.3.5rc1/#files > > > > > > This is the first (and only) planned release candidate for 3.3.5 > release. > > > The stable release is planned for next week. > > > > > > thanks, > > > Abhilash > > > > > > On 9/7/21 12:39 AM, Abhilash Raj wrote: > > >> Hello Everyone, > > >> I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a > > >> pre-release for 3.3.5, which is slated to come out in 3 weeks from > now. > > >> I am planning for a 2 week beta period, after which I'll release the > > >> first RC and then stable a week after. Right now I am not planning to > > >> release a second beta version, but if there are several changes in > Core > > >> in the next week or so, then I might. This release includes a lot of > bug > > >> fixes and some new features. It also includes a security enhancement > > >> that improves the authentication of REST API by adding resistance to > > >> some timing channel attacks. A full list of changes in this version > can > > >> be found here[1]. > > >> [1]: > > >> > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NE > > >> WS.html#news-3-3-5 We have also made improvements in the i18n workflow > > >> and now the email templates are updated from the translated messages > in > > >> the .po files that we get from Weblate. Documentation for translators > is > > >> available here[2] if you want to help translate Mailman into your > native > > >> language. [2]: https://docs.mailman3.org/en/latest/translation.html > > >> > > >> This is a pre-release version, if you want to test it with your > setup, > you can install it using: > > >> $ pip install --pre mailman==3.3.5b1 > > >> > > >> If you want to download a release tarball, you can do so from here: > > >> https://pypi.org/project/mailman/3.3.5b1/#files > > >> > > >> This release received a lot of contributions from community, which I > am > > >> really happy about! I'd like to thank everyone who made this release > > >> possible!> > > > -- > > > thanks, > > > Abhilash Raj (maxking) > > > > -- > > 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/ > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 11 months

Mailman-users search results for query "Postorius"