Search results for "Postorius" - Mailman-users

New subscribed (by invitation) user: no password received in invitation/welcome e-mail. Postorius sign up / password reset broken

by ^m'e

Hi there, I migrated form MM2.1 to MM3.3.10 on Debian Trixie (mariadb backend) -- I know that's a bit unorthodox to ask here for help on a non venv-based installation, but hopefully I'll first gain a bit of insight of MM3 in order to formulate a more precise request to Debian maintainers. ## Issue #1. A newly invited (from Postorius mass subscription page) and confirmed user doesn't get any password in their invitation/welcome e-mail. I guess that's because MM3 allows a user to subscribe without having an account, right? Else, there's a problem. ## Issue #2 Anyway, if that new user asks for a password reset on Postorius they get "Server error An error occurred while processing your request." Log shows: ``` ERROR 2025-08-29 17:59:17,227 173488 django.request Internal Server Error: /accounts/password/reset/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 105, in view return self.dispatch(request, *args, **kwargs) ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/utils/decorators.py", line 46, in _wrapper return bound_method(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 144, in dispatch return handler( form.save(self.request) ~~~~~~~~~^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/forms.py", line 633, in save adapter.send_password_reset_mail(user, email, context) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 577, in send_password_reset_mail return self.send_mail("account/email/password_reset_key", email, context) ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/allauth/account/adapter.py", line 201, in send_mail msg.send() ~~~~~~~~^^ File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 299, in send return self.get_connection(fail_silently).send_messages([self]) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 134, in send_messages sent = self._send(message) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 152, in _send self.connection.sendmail( ~~~~~~~~~~~~~~~~~~~~~~~~^ from_email, recipients, message.as_bytes(linesep="\r\n") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3.13/smtplib.py", line 861, in sendmail self.ehlo_or_helo_if_needed() ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/smtplib.py", line 611, in ehlo_or_helo_if_needed if not (200 <= self.ehlo()[0] <= 299): ~~~~~~~~~^^ File "/usr/lib/python3.13/smtplib.py", line 451, in ehlo self.putcmd(self.ehlo_msg, name or self.local_hostname) ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/smtplib.py", line 378, in putcmd self.send(f'{s}{CRLF}') ~~~~~~~~~^^^^^^^^^^^^^^ File "/usr/lib/python3.13/smtplib.py", line 365, in send raise SMTPServerDisconnected('please run connect() first') smtplib.SMTPServerDisconnected: please run connect() first ``` The same happens if the new users tries to sign up. Any idea? Cheers -- Marco

2 weeks, 2 days

footer template priority

by Sam Darwin

It seems templates can be configured in the filesystem or via postorius. When I place a footer template in the filesystem it worked fine. Then without adjusting any configuration, without removing that, I tried to use the postorius control panel to add a footer template, which ends up in the database, both the core and web databases. But emails stop getting sent out. Emails were posted into Hyperkitty, but not mailed out via postfix. Whatever system logs I have access to, I have checked. There are no apparent errors anyplace. Perhaps I didn't look in the right places. The problematic email arrives, is posted to Hyperkitty, but isn't emailed out to subscribers. As if the template broke something. I remove the template from the postorius UI. Those queued emails are instantly sent! The template said "test content". No variables. I checked on the server for "queued emails" and did not find those either, in postfix or mailman. Mysterious. The phenomenon is repeatable on this server. Add a footer template, emails stop.

2 months, 3 weeks

Re: Time Zone Issue in Postorius

by Mark Sapiro

On 2/7/22 21:18, David Newman wrote: > On 2/4/22 10:29 AM, Mark Sapiro wrote: >> >> The appropriate setting for Django is always `TIME_ZONE = >> 'UTC'`because the time passed from Mailman core is a naive >> datetime.datetime object and is actually UTC. > > Could use clarification on this. Are you referring to the settings.py > file, or something else? Settings.py > Asking because my settings.py currently has: > > # Django time zones > USE_TZ = True > TIME_ZONE = 'America/Los_Angeles' It should be TIME_ZONE = 'UTC' Times passed from Mailman core are naive times, I.e. they don't have time zone info, but they are in UTC. Thus for Django to get the correct time with time zone you need USE_TZ = True (without that, Django will throw an exception about naive times) and the TIME_ZONE to apply is UTC. With those settings, Django has the correct time zone aware times. > and list timestamps appear to work OK both in Hyperkitty and as received > by members' mail clients. Mail sent to list members is not at all affected by this. That involves Mailman core only. Also, time stamps on posts in HyperKitty come from Date: headers or Django internal times. Where you see this manifested is for example when looking at a held message in Postorius and seeing the hold time. which is a time stamp generated by Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

Re: Where is postorius.wsgi?

by Simon Hanna

On 01/26/2018 11:18 AM, Peter Münster wrote: > On Fri, Jan 26 2018, Peter Münster wrote: > >> ImportError: No module named settings > Ok, I've found the solution: > > In wsgi.py: > > import sys > sys.path.append('/srv/www/htdocs/ckc3r/postorius/example_project') > > > But now, I get another error: > > File "/usr/lib/python2.7/site-packages/postorius-1.1.2-py2.7.egg/postorius/views/rest.py", line 33, in <module> > from django_mailman3.lib.scrub import Scrubber > File "/usr/lib/python2.7/site-packages/django_mailman3-1.2.0a1-py2.7.egg/django_mailman3/lib/scrub.py", line 26, in <module> > from email.message import EmailMessage > ImportError: cannot import name EmailMessage > > What should I do please? You appear to be using a prerelease version of django-mailman3 which is not compatible with the other parts. Install an earlier version and it should work. You also appeared to have used Python3 for the frontend in earlier posts. Currently Python3 is not yet supported. The next stable releases will most likely support Python3 and drop support for Python2

7 years, 7 months

Re: list footer web customization procedure

by Mark Sapiro

On 12/8/21 6:05 PM, Philippe B wrote: > Update: After disabling the footer on a few lists (as described here a week ago), we started seeing "Cache content lost" in most (but not all) messages from those lists. > > In some cases, that phrase is an attachment to the "real" body of the message. In others, it's the opposite (which is more problematic for responding). That seems to depend on whether the poster sent in plain text. The difference between inline and attachment has to do with how footers are added. They are only added inline if the message after content filtering is a simple text/plain message. > One puzzling aspect is that it doesn't happen consistently. One hourly automated message will have it; but exactly the same message one hour later won't have it; but will have it again 3 hours later for example. > > Is that a known problem, or would it be possible to troubleshoot? Thanks. The issue may be a bug or a race condition. What is going on is the 'empty' footer you created in Postorius is retrieved from Postorius by a URL. In order to reduce the number of http transfers to retrieve such templates, they are cached in the local file system. Now, when we want a template that is accessed via a non-mailman: URI, we call the cache managers get() method at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/cache.py… to get it. This should return either None if there's no cached file or the contents of the file, but if there is an entry but no corresponding file, it returns 'Cache content lost'. This could occur if some asynchronous process expunged the entry between getting the entry and getting the file. A process that could do that is the task runner that evicts expired cache entries. Look in your mailman.log. There will be `ACCEPT: <message_id>` entries for each accepted message and there will be hourly `Task runner evicted expired cache entries` entries. Do the ACCEPTs for the affected messages occur at the same time as the evictions? One way to avoid this is to not use Postorius to set the template but rather, create an empty `templates/lists/<list_id>/en/list:member:regular:footer.txt` in mailman's var/ directory for each such list and delete the Postorius templates. Of course, this is just a work around and not a solution to the issue. A proper fix is probably to implement a lock on the get(), evict(), evict_expired() and clear() methods so they can't execute concurrently. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Eggert Ehmke

Hello Stefan, I had the same problem. While I did not find the reason for this strange behavior, I found a workaround. I changed the lines in the apache vhost file like this: <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> Note I only changed the single ProxyPass line from mailman3 to mailman. The url to access the web gui also changes like this: https://my.mailinglistserver.local/mailman/postorius/lists/ This works for me, tell us your success. Would be nice when the problem could be solved finally, this happened to a few people. Cheers, Eggert Am Montag, 25. Oktober 2021, 10:45:50 CEST schrieb Stefan Bauer: > Dear Users, > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > web-interface via > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > I receive > > Not Found: /mailman//postorius/lists/ > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core > 1) > > Where does the wrong path come from (mailman vs. mailman3) > > After enabling Debug, i see in the browser the following: > > > Page not found (404) > Request Method: GET > Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ > > Using the URLconf defined in urls, Django tried these URL patterns, in this > order: > > ^$ > ^postorius/ > ^hyperkitty/ > ^user-profile/delete$ [name='mm_user_account_delete'] > ^user-profile/$ [name='mm_user_profile'] > ^accounts/ > ^admin/ > > The current path, /postorius/lists/, didn't match any of these. > > You're seeing this error because you have DEBUG = True in your Django > settings file. Change that to False, and Django will display a standard 404 > page. > > My apache configuration is very simply: > > # more /etc/apache2/conf-enabled/mailman3.conf > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > I dont see where the path gets traversed in the wrong way. Any help is > greatly appreciated. > > thank you. > > Stefan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 10 months

Re: MM3.1 templates

by Abhilash Raj

Hi Matt, On Tue, Jul 18, 2017, at 07:25 AM, Matt Richards wrote: > I've managed, to setup MM3.1 using the docker images from > http://github.com/maxking/docker-mailman. I would like to start > customizing > the templates MM3.1 uses for the footer and confirmation emails. Is there > any mailman site admin or list admin documentation on how to customize > email templates in MM3.1? Not yet, we are still working on perfecting the Installation Guide and other configuration related documentation for Mailman 3. For now, you might have to use command line to do these changes. Templates should exist inside the `$var/templates/<language_code>/` where $var is the var directory for Mailman Core. If you are using the container images, it should be at `/opt/mailman/core/var/`. The templates are named as the naming scheme mentioned in the documentation[1] and ending with a `.txt`. If you place those files there, it should be able to override the default templates that exist in the mailman. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht… > I've found this template doc at > https://gitlab.com/mailman/mailman/tree/master/src/mailman/rest/docs, but > I'm not clear how this works.. and it appears postorius doesn't have > template support yet? I am new to python and django.. That is correct, you can set the URI in the Postorius interface, but there is no way to actually write the templates in Postorius right now. > -- > --Matt > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Hope that helps! -- thanks, Abhilash Raj

8 years, 1 month

Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-02 17:32, Mark Sapiro a écrit : > On 5/2/22 06:39, Michael Hazan wrote: >> Hello, >> >> When creating a list via postorius, i can see 3 style appear >> (announce, discussion, private). Is it possible to either create a new >> style and add it to that list or modify one of those style ? > > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > Thanks i will look into setting up that plugin, hopefully an easier way to do that can make it's way to the default install. >> Also, coming from mailman2, you could directly set the members post >> moderation action when subscribing, now you can only do it via the >> user menu, is there a way to automate this in mm3 ? > > > I don't understand what you mean here. In MM 2.1 a member had only one > setting - moderated yes or no and if moderated there was a list > setting for the moderation action. There was also a list setting for > whether new members were moderated by default. How were you setting > the new member's moderation when subscribing? > > You are correct that when subscribing a new member, the member gets > the default action for members and different action has to be set in a > separate operation. I don't think this is significantly different from > MM 2.1. Also, can you describe what you mean by "automate this". in MM2.1, if you set the list to moderated and default action to hold posting, you can set a some member to be un-moderated (mod bit off) to automatically allow their posting. In the web interface of MM2.1 there is a checkbox with moderated bit on/off on the member list itself, in the postorius interface for MM3 you have to open each members settings page to access that. For automation, as list owner, upon registering a member (via mass subscription) the possibility to change that ? also the me too/dupe setting for example. Thanks

3 years, 4 months

Re: Member Issue Discovered

by Stephen J. Turnbull

Victoriano Giralt writes: > El vie, 23-10-2020 a las 08:19 -0700, Mark Sapiro escribió: > > > > This would be more difficult for Postorius/Hyperkitty because those > > users are Django users, but that isn't an issue for Affinity. > > > > All of a sudden, an idea has dawned on me ... Wouldn't it be possible for > Postorius/Hyperkitty, both Django applications, to use Mailman core user > model as their User model? It is just a setting for Django > (AUTH_USER_MODEL). I find the "just a setting" claim a bit implausible. I suspect a certain amount of replumbing of Postorius and HyperKitty will be necessary to get it to work. Most important, the "AUTH_" is pretty scary. Mailman core has *no* authentication built in. It is assumed to be firewalled off from the rest of the world with only access from Postorius and HyperKitty permitted. Can you expand on how hard it would be to do this? Remember that some Mailman instances are either big targets (eg, Apple) or require good security for content reasons (lists for doctors' patient support groups, domestic violence support groups). This is not a great authn/authz model in the modern Internet, but as far as I can see changing it is going to be quite a lot of work, and none of us are authentication specialists (although Abhilash did study security, I don't think he specialized in authentication tech) -- providing reasonably reliable and secure authentication services, especially "social auth" (OpenAuth, OpenID etc) is an important reason we went with Django in the first place. Steve

4 years, 10 months

Re: missing graphics in Postorius

by David Newman

On 12/7/21 11:17 AM, Mark Sapiro wrote: > On 12/6/21 10:15 PM, David Newman wrote: >> After installing MM3 on Debian 10 using the venv docs, no graphics >> appear in the admin or list pages, just broken links. >> >> The mailmanweb log has lines like this: >> >> ERROR 2021-12-07 06:04:10,002 18262 django.security.DisallowedHost >> Invalid HTTP_HOST header: '127.0.0.1'. You may need to add '127.0.0.1' >> to ALLOWED_HOSTS. >> >> which is odd because there is the line for "localhost" in settings.py, >> and /etc/hosts correctly ties this to 127.0.0.1. > > > Add '127.0.0.1' to ALLOWED_HOSTS anyway. Done, thanks. Given that DNS works fine on this host, with localhost and 127.0.0.1 resolving backward and forward, this seems like a bug. Shouldn't the resolver be able to recognize localhost without hard-coding an address? Particularly this address, since the IETF is considering what is IMO a crazy idea to unreserve 127/8? https://www.ietf.org/id/draft-schoen-intarea-unicast-127-00.html > > >> There are entries like this in /var/log/nginx/error.log saying the >> files just aren't there: >> >> 2021/12/06 22:00:30 [error] 18123#18123: *65 open() >> "/opt/mailman/web/static/postorius/img/mailman_logo_small_trans.png" >> failed (2: No such file or directory), client: x.x.x.x, server: >> somehost.example.com, request: "GET >> /static/postorius/img/mailman_logo_small_trans.png HTTP/2.0", host: >> "somehost.example.com", referrer: >> "https://somehost.example.com/mailman/lists/" >> >> (I've obfuscated names and addresses here, but "somehost.example.com" >> refers to a valid FQDN in the log.) >> >> I thought I'd followed all the venv docs, but the >> /opt/mailman/web/static/postorius directory doesn't exist. Did I miss >> something? > > Assuming you have > ``` > STATIC_ROOT = '/opt/mailman/web/static' > ``` > in your /etc/mailman3/settings.py file, you may need to create that > directory if it doesn't exist. You shouldn't need to manually create the > /opt/mailman/web/static/postorius directory if the > /opt/mailman/web/static directory exists and is writable/searchable by > the Mailman user. Yes, that was it. Thanks. Previously you'd pointed out what you considered an error in the venv docs, with the workaround to manually create the /opt/mailman/web directory [1]. I think the same issue applies here, and also that /opt/mailman/web and subdirectories need to be owned by the mailman user. Thanks again. dn > > That should enable > ``` > (venv)$ mailman-web collectstatic > ``` > to populate that directory. Be sure you've run all four commands at > https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… > et seq. >

3 years, 9 months

Mailman-users search results for query "Postorius"