Search results for "Postorius" - Mailman-users

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, 7 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, 9 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

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

Re: Extracting mailing list users

by Mark Sapiro

On 1/1/23 10:37, Eggert Ehmke via Mailman-users wrote: > Hello Steve, > I really would appreciate to get some help on the withlist command. I really like to program python, but this interface is not at all intuitive. I also find it strange to do administrative tasks in a programming language. In this special case, I believe it should be possible to work on the display names in Postorius in the member settings. You can update user display names in Postorius via the Users tab at the top of the page, but it would be a tedious, one at a time process, and I don't think you can modify address display names in Postorius and those are the ones `mailman members` displays. I just posted a mailman shell (aka withlist) interaction at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Try that. > I also find it strange to do administrative tasks in a programming language. Understood, but there are a couple of things at work here. One is that this particular task is a one-off the correct the result of a bug, but perhaps more significantly, mailman developers (at least me) are comfortable with `withlist` (it's been around since MM 2.1) and if I can do it that way, it reduces the motivation to make something more friendly for the normal admin. Unfortunately doing things easily that way requires a lot of specialized knowledge of Mailman internals, so most admins need help with it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-02-16 11:06:40 -0800 (-0800), Mark Sapiro wrote: [...] > Yes, that doc really isn't appropriate for your purpose, but it's > the only one I could find on Django sites. Most of what it talks > about is for more complex situations than ours and whatever bits > are relevant are already done in Postorius/HyperKitty. Sorry for > leading you astray. [...] Please don't apologize, you've gone well out of your way to be helpful and it's very much appreciated. I've been on the other side of this conversation for plenty of projects and understand the challenges. > I don't think Django's docs address the simple task of adding a > site. While part of me wants to find that hilarious, I can't honestly claim the projects I work on are any better in that regard. Your latest recommendations have me un-stuck and left with a far better sense of how this fits together now. -- Jeremy Stanley

2 years, 5 months

Re: hidden list is hidden even to the owner

by Abhilash Raj

On Wed, Jul 1, 2020, at 1:31 PM, Mohsen Masoudfar wrote: > Hi, > > I am not sure, if it is designed this way, or I am doing something wrong. > > I created a list in MM3 as a hidden list, meaning: > Show list on index page: NO > and assigned the owner. When I login as Postorius web admin, I see the > list on the list page which is listed as: (unadvertised*). This is fine. > But when the owner or moderator login to Postorius they don't see the > list at all. Of course if they add the list name at the end of the URL, > they get to the list and as the owner can manage it too. > My question is: I am just not sure, if I am missing something or this > is how it is supposed to work? Which version of Postorius are you running? Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. > You could expect, that the owner or the moderator should see the list > as (unadvertised*) too. > > Best regards > Mohsen Masoudfar > Lead System Analyst, IT Operation > American Association for the Advancement of Science > 1200 New York Ave, NW, Washington, DC 20005 > 202-326-7087 > > > _______________________________________________ > 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

Re: hyperkitty web site

by Mark Sapiro

On 4/28/20 9:40 AM, Gelpi Andrea wrote: > > If in django administration I rename that site it works. > > But having more than one domain this is not a solution. > > what i need is to separate different domains > > https:/website1/mailman3/hyperkitty shows some lists > https:/website2/mailman3/hyperkitty shows other lists There are issues with FILTER_VHOST. See <https://gitlab.com/mailman/postorius/-/issues/394> for the Postorius issue. This will be fixed for Postorius in the next release. For HyperKitty, the issue is <https://gitlab.com/mailman/hyperkitty/-/issues/254>. This is not yet fixed. Currently, if FILTER_VHOST is True, HyperKitty only shows lists in the index for which the list's domain matches the domain in the accessing url with a leading 'www.' stripped. E.g. list(a)example.com will only show on the index if the accessing URL's host is example.com or www.example.com, but not if it is say lists.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

Mailman-users search results for query "Postorius"