Search results for "Postorius" - Mailman-users

Language Support In Templates

by Brian Carpenter

Hello MM3 Users, I have a question regarding the use of templates in different languages. I created a template for the unsubscribe notification in Postorius in Greek. The template shows up fine in Greek via Postorius. However the email that is sent out has a bunch of question marks where the Greek should be: ??????????? ?????????? ???????? ?????????? email ???? ???, ????? ????? ? ??????????? GNU Mailman ???? ????? $. ?????? ??? ?????? ????????? ??? ?? ????????? email $user_email ?????? ?? GNU Mailman ?????? ?? ?????????? ??? ??????? ???, ?????? ????? ?? ????????????? ?? ?????? ???. ???????? ?? ?? ?????? ????? ?????????? ?? ???? ?? ??????. ? ?? ?????? ?? ????????????? ??? ???????? ?????? - ??? ???? ?? ???????? line - ?? ??? ?????? ???? ?? $ request_email: confirm $token ????????? ??? ? ???? ???????? "?????????" ?? ???? ?? ?????? ?????? ?? ?????????? ?? ???????????? ?????????? ?????????????. ??? ??? ?????? ?? ??????????? ??? ????? ?? ????????? ???????????? ????????????, ????? ???????? ??? ??????. ??? ????????? ??? ??????????? ????????? ??? ?? ?????, ? ????? ????? ?????????, ???????? ?? ?????????????? $owner_email What does it take to get templates to send out messages in a different language then the interface itself. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 9 months

Re: Hyperkitty Text/Markdown/HTML

by Sam Darwin

> If you want to accept HTML in posts, you should ensure that only trusted users can post. This is good practice anyway to avoid spam on the lists. Then you don't have to be too concerned about malicious HTML. Right, that is already the case. However equally important is formatting via the sanitizer, not just removing malicious HTML. > I don't see a demand for a feature like that. Currently there is no demand for that, but also currently Hyperkitty only supports plaintext or markdown, so if you add HTML into the mix, it may change requirements. > Yahoo... that is not what I see. We both see the actual link is missing. The difference is, that you also are getting some garbage characters (multiple "|=20"), and I did not see that, although maybe I was not pasting the right thing. > Then the message will contain only the HTML. But if you do that, malicious HTML and missing plain text will be the least of the things to be concerned about. All sorts of malicious malware can be attached to email in other than HTML parts. You are saying "All sorts of malicious malware can be attached to email in other than HTML parts." What is the solution to this currently? We have "Collapse alternatives" and "Convert html to plaintext" enabled. If one of those is relevant (is it?) the description in postorius should not be limited to "Should Mailman collapse multipart?" but also say "This is strongly recommended, to remove all sorts of malicious malware", since that seems critical. Or, which postorius setting applies? Thanks.

1 year, 2 months

Re: Database running VERY hot

by Darren Smith

Well, we haven't tackled the issue if importing old archives yet - we're trying to stabilize things first, trying to get the 504 gateway timeouts to stop happening. Once that happens, we have over 40 million old emails to import. (some of the emails date back to 1987 I think.) We'll see how it goes. :) -Darren On Fri, Mar 9, 2018 at 10:20 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Fri, Mar 9, 2018, at 9:11 AM, Darren Smith wrote: > > Abhilash, > > Thanks for the response. I'm going over to lists.fedoraproject.org to see > if they have done any fine tuning. > > Our installation is at https://lists.rootsweb.ancestry.com, if you're > interested in seeing an installation with over 32,000 mailing lists. As I > mentioned, it was big enough that we have disabled the browse experience in > Postorius and are hosting our own pages for browsing to a new list. > > > Please keep us posted if you have other unique challenges for operating > this high number of lists, other than this particular one. We'd love to be > able to support high number of lists efficiently :) > > If we get time to work on this we will certainly create a pull request. :) > > > On Thu, Mar 8, 2018 at 11:49 AM, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > Hi Darren, > > > On 3/8/18 9:43 AM, Darren Smith wrote: > > Hello all, > > We had an old installation of Mailman 2.1 across three servers with over > 32,000 mailing lists on them. Due to circumstances beyond my control, we > had to shut them down and quickly set up Mailman 3 on a new server. > > We have Mailman3 set up on a single server this time, as we were having > problems with a 3-server setup and Hyperkitty and archives. Long story > short, it is up and running, and our users are starting to come back. > > However, we do not have very many users hitting Postorius and Hyperkitty > yet, and we are seeing a distressing number of 504 gateway timeouts. > > We noticed that there is a significant number of queries to the API > whenever hitting Postorius's front page to load the mailing lists, and then > on every load. It looks as if it makes a single call to the API to get > information about a single list, and does this 10 times - once for each > list - to render the page. This gets much worse when users set the view to > 200 per page, as they are inclined to do with 32,000 mailing lists... > > What we've done, actually, is to override the front page and point the > users to a different set of static pages where we have all of our lists > categorized and searchable, and when they find the list they are looking > for, we have a link back to postorius. It has taken a lot of the stress off > of the server. > > However, I still see where the database at times can run VERY hot. > > We have set up this server to run with PostgreSQL. When I do a ps aux | > grep postgres, I find a lot of processes that have been spawned to take > care of mailman - a dozen or so. However, one of the threads is taking up > about 85% of the load, another thread about 14%, and little dribbles here > and there from the rest of the threads. > > Here are the questions: > > 1) Has anyone run into problems like these? I would think that maybe this > is an issue having so many mailing lists, but honestly there aren't that > many people using the system yet. It is going to ramp up as the users > realize that we are live again, but we aren't getting that much traffic. > > > I can say that in general, Postorius doesn't really optimize REST API > queries and so loading a single page can sometimes make things bad. > > Currently, the largest installation of Mailman 3 that we know of runs at > lists.fedoraproejct.org and the administrators of the list would know how > well does our Web UI scale. > > However, I don't think we have anyone actively working on trying to fix > this particular issue. Pull Requests and fixes are welcome :) > > > 2) Is there any configuration that I can set, especially with regards to > the database, so that it can be used more efficiently and not throttle > through one or two threads? > > > There isn't any configuration that would change how databases are used in > Mailman Core. Django *may* have some, but I don't know about any of them of > the top of my head. > > thanks, > Abhilash > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > >

8 years, 8 months

Re: Default templates

by Mark Sapiro

On 11/8/23 16:01, Steve Brown wrote: > I'm new to this list and newly a Mailman list administrator. I know I can customize message templates and have done so for my list's Welcome message. My problem is knowing what I'm replacing when I create a "new" template. How/where can I see he default content? The fact that Postorius doesn't show it to you is https://gitlab.com/mailman/postorius/-/issues/366 The defaults are in your installation at mailman/templates/en/ or in GitLab at https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en or in the directory https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/ for other languages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: django fake users

by Andrew Hodgson

Stephen J. Turnbull wrote: >Andrew Hodgson writes: > > >Require moderator approval for subscribing. > > I don't think this would help the issue. What I am seeing here is > users signing up through Postorius using the sign up option which > then creates an account in Django (but not Mailman). >Ah, so "fake" == "account in Django but no user in Mailman"? Yes. >I don't have time to look at it, so take this with a grain of salt, but I don't think they are passing the email confirmation. If they were, they would show up in Mailman. Actually I did confirm the same to this list later on, the accounts are indeed not passing email confirmation. >I think this would be simple enough to deal with (not trivial, so I'm not making any promises except to try adding it to the GSoC ideas page >-- that should be enough to clarify whether there are any "annoyance to 'real' users" issues, and we move forward from there if there aren't). Basically, Postorius should notify Mailman that there is a >*pending* user in Django, and if there's no confirmation by a deadline, remove that user. This requires a bunch of infrastructure like a table of "pending" users, callbacks for the deletion, etc, but I don't see why it would be conceptually difficult. (This combination is why I think it would be a good GSoC task) Sure. I would rather go this route rather than use captchas at this stage, though right now my Cron job running once a week is sufficient. Thanks. Andrew.

5 years, 9 months

Can "Pre Verified" set to yes by default?

by Stephen J. Turnbull

Alan So writes: > However, some of our departmental staff sometimes forget to check > the box "Pre Verified" when they refresh (actually delete all and > subscribe all) list of members during term's start. [...] > Is this possible to add default setting of Pre Verified during > mass-subscription (for example settings.py) such that we can help > them a bit? I don't know if there's a way to do this in settings.py, but I suspect not. Maybe Mark knows a way. However, you can find .../site-packages/postorius/forms/list_forms.py (not sure exactly where that is in your instance but I guess you probably do), and find this code (AFAICT this is the unique instance of 'Pre Verified' in the whole Postorius code base) in that file: pre_verified = forms.BooleanField( label=_('Pre Verified'), initial=False, required=False, help_text=_( 'If checked, users will not have to verify that their ' 'email address is valid.'), widget=forms.CheckboxInput() ) Then just edit the line initial=False, to initial=True, Note that this will get overwritten if you upgrade (or reinstall) Postorius, and you'll have to do it again. But it will save you a ton of grief until that happens. Also note that if there *is* a way to do this in settings.py, it is *safe* to do that later without reverting the change to list_forms.py, and the settings.py setting will continue to work after any upgrade or reinstall. So you can patch list_forms.py now without worrying it will get you into trouble later. Steve

3 years, 10 months

Re: only show mail domains from web host on web-host-url

by Jens Günther

Just checked again and saw: - in the setup it works perfectly in Hyperkitty, that's nice - for the first web host I have 2 mail domains registered, so it also matches (unfortunately) with what you said :-( Anyway, I dceleted one of it, still both lists are shown on either web host, so it's generally not working. If I can do something on this issue, please advise me. Thanks. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > FILTER_VHOST is problematic. It works fairly well for HyperKitty, but > not so well for Postorius. In particular with Postorius it doesn't work > if there is more than one mail host domain with the current web host.

5 years, 7 months

Re: Postorius no connection to REST API

by Abhilash Raj

> On Aug 20, 2021, at 2:53 AM, Richard Rosner <rrosner5(a)gmail.com> wrote: > > WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,941 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 > WARNING 2021-08-20 11:49:22,954 3975 django.request Not Found: /mailman3 > [pid: 3975|app: 0|req: 17/16] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:10 2021] GET /mailman3 => generated 5651 bytes in 13321 msecs \ > (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) > [pid: 3975|app: 0|req: 17/17] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:07 2021] GET /mailman3 => generated 5651 bytes in 16373 msecs \ > (HTTP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) > WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts > WARNING 2021-08-20 11:49:32,820 3975 django.request Not Found: /accounts > [pid: 3975|app: 0|req: 18/18] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:32 2021] GET /accounts => generated 5651 bytes in 251 msecs (H\ > TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) > WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives > WARNING 2021-08-20 11:49:43,517 3975 django.request Not Found: /archives > [pid: 3975|app: 0|req: 19/19] 127.0.0.1 () {56 vars in 1208 bytes} [Fri Aug 20 11:49:43 2021] GET /archives => generated 5651 bytes in 99 msecs (HT\ > TP/1.1 404) 5 headers in 170 bytes (1 switches on core 1) > > The proxy pass config is > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > Proxypass "/mailman3" "http://127.0.0.1:8000/mailman3" > 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 "/archives" "http://127.0.0.1:8000/archives" > </IfModule> There seem to be extra entries in this, depending on where you installed from, there are only some URLs that you need. You need one of the /postorius and /mailman3, one between `/archives` or `/hyperkitty`. `/django` is probably not useful I think, `/accounts` looks fine. Top level URL patterns are basically listed here[1], but it depends on where did you install from and what the url patterns are. [1]: https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py#L25 > _______________________________________________ > 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

Error: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class

by Torge Riedel

Dears, I just upgraded my Server from Ubuntu 22.04 to 24.04 and I get the following error when accessing the web page. Django is 5.0.10 Postorius is 1.3.13 Any help is welcome. Thank you and kind regards Torge Internal Server Error:/mailman3/lists/ ImportError at/mailman3/lists/ Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Request Method: GET Request URL:https://lists.lsv-pinneberg.de/mailman3/lists/ Django Version: 5.0.10 Python Executable: /usr/bin/uwsgi-core Python Version: 3.12.3 Python Path: ['.', '', '/usr/lib/python312.zip', '/usr/lib/python3.12', '/usr/lib/python3.12/lib-dynload', '/opt/mailman/web/venv/lib/python3.12/site-packages'] Server time: Sun, 22 Dec 2024 11:05:00 +0100 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') 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', 'allauth.account.middleware.AccountMiddleware') Traceback (most recent call last): File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 30, in import_string return cached_import(module_path, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 16, in cached_import return getattr(module, class_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ The above exception (module 'django.contrib.sessions.serializers' has no attribute 'PickleSerializer') was the direct cause of the following exception: File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/deprecation.py", line 133, in __call__ response = self.process_request(request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/middleware.py", line 20, in process_request request.session = self.SessionStore(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/db.py", line 16, in __init__ super().__init__(session_key) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/contrib/sessions/backends/base.py", line 47, in __init__ self.serializer = import_string(settings.SESSION_SERIALIZER) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/web/venv/lib/python3.12/site-packages/django/utils/module_loading.py", line 32, in import_string raise ImportError( ^^^^^^^^^^ Exception Type: ImportError at/mailman3/lists/ Exception Value: Module "django.contrib.sessions.serializers" does not define a "PickleSerializer" attribute/class Raised during: postorius.views.list.list_index

1 year, 10 months

Re: Help request, almost got it going, but ....

by Claus-Justus Heine

I think I found the bug; I have posted a comment to the issue mentioned by Mark https://gitlab.com/mailman/postorius/issues/58 Regards Claus Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: > Oh well. > > Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>> >>> Seemingly, at some point in the deep dungeons of the source code the >>> "Acceptable aliases" Text-Box is not interpreted correctly. >>> >>> Specifically, at the start it contains the string >>> >>> [] >> >> >> See <https://gitlab.com/mailman/postorius/issues/58>. > > there they talk about fancy "uni-code thinks" (email addresses?) where > the task is to convert a new-line separated text-field into an array. Oops. > > Kind thanks anyway. > >> >> In order to set things on this page, you need to clear the Acceptable >> aliases box before submitting changes. You can't actually set Acceptable >> aliases via Postorius until this is fixed. > > The issue seems not to be overly active. I thought -- coming from > Mailman v2 -- that the configuration of acceptable submitters to an > email list (e.g. keep everyone moderated?) would be a central and > prominent and important configuration issue. Seems not to be a central > point. Mmmh. > > Thanks > > Claus > > -- 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

9 years, 2 months

Mailman-users search results for query "Postorius"