Search results for "Postorius" - Mailman-users

Re: Easiest way to install a new mailman3 deployment?

by Mark Sapiro

On 1/5/21 3:37 PM, Ruth Ivimey-Cook wrote: > > I have only split mailman in two: mailman-core with the email-related > parts, and postorius for the UI. As yet, although Hyperkitty "works", I > haven't addressed the fact that mails get archived in folders on the > email host and so (for me) hyperkitty can't see them. Ideally, they > would be on the postorius/hyperkitty host, or possibly network shared The emails that get archived in folders on the Mailman core host are archived by the 'prototype' archiver, not by HyperKitty. HyperKitty archived emails are in tables in Django's database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server

by Mark Sapiro

On 11/28/24 12:01 AM, peterrflores(a)hotmail.com wrote: > > Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius? This is how things work. See for example https://mail.python.org/mailman3/?all-lists - each of those lists has its own settings. There are also `unadvertised` lists on that server, e.g. https://mail.python.org/mailman3/lists/capi-sig.python.org/ > Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated. Mailman core provides a REST API for list management. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… - this interface is only protected by a user name and password, so it is normally only available via `localhost` as wider access is not very secure. Postorius uses this API via the python bindings described at https://docs.mailman3.org/projects/mailmanclient/en/latest/ > Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful. A list can be anonymous id desired which means the sender of a post is not identified in any headers of the distributed email. HyperKitty archives can be private, i.e. accessible only to list members. The membership list can be restricted to only list owners/moderators or available to list members as well via list settings. There is currently no support for encrypted email. Full access to a list's settings and other info via Postorius is limited to logged in users who are either a `superuser` or an owner of the list. moderators have more limited access, list members may be allowed to see the membership. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: Help needed to create filters that were working in Mailman 2.

by Mark London

Mark - I'm an idiot. I previously had modified some of the text in Postorius to be shorter, and somehow had deleted the Accept feature! I hope not to ever have to upgrade our email server ever again. It took much years off my life. In any event, here's one of the text that I modified to be briefer. Perhaps you can see why I shortened it. Besides which, who goes on vacation these days, and disables emails from any source? I have users that literally have tens of thousands of unread email. They don't bother to delete it. Grrr... - Mark help_text=_( 'Set this option to Enabled to receive messages posted to this ' 'mailing list. Set it to Disabled if you want to stay subscribed, ' "but don't want mail delivered to you for a while (e.g. you're " "going on vacation). If you disable mail delivery, don't forget " 'to re-enable it when you come back; it will not be automatically ' 're-enabled.' On 6/21/2023 4:21 PM, Mark Sapiro wrote: > On 6/21/23 11:36 AM, mrl(a)psfc.mit.edu wrote: >> I'm using version 1.3.8 Which I installed on Ubuntu 22 on April >> 18. I'm guessing this feature was installed in 1.3.9? > > The attached screenshot (which may not make it to the list but should > be in your direct copy) is from Postorius 1.3.8 installed via pip. If > you don't see this, possibly you have installed the Debian/Ubuntu > package and this is a Debian issue. >

2 years, 5 months

Re: Social signup?

by Duane Raymond

Wow - thanks for the redirection on where to patch it and the first-cut code. I'll look into this in 2 weeks when I am able to focus on it. Cheers, Duane On Wed, 15 Mar 2023 at 16:18, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/23 05:08, Duane Raymond wrote: > > > > I'll jump over to the developers list when I start this (I'm about to > > travel for a week to run an annual event in Oxford - so the far removed > > from programming)...but which chatGPT suggested so far was > > > > 1. Extending postorius/signups.html with a loop to get the configured > > social login providers PLUS adding a csrf_token field to the form > > 2. Modifying postorius/views.py (which doesn't seem to exist but > there > > is a postorius/views folder) - so perhaps this is views/urls.py > > > This is not what you want to do for this. The changes need to be in > django-mailman3, not postorius. I have attached a patch which might work > for you. I think it is good, but some of the wording is stuff that may > not be appropriate. See what you think. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to duane(a)fairsay.com >

2 years, 9 months

Re: Server 500 error for just one list, just one page

by Mark Sapiro

On 6/28/20 4:05 PM, kelly.close(a)lrewater.com wrote: > I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are). Neither do I, but you want to look in Mailman core's mailman.log and Django's log. mailman.log is in a directory with others including smtp.log and subscribe.log. If you don't know where to find that, look in the output from `mailman conf`. The first thing to look for is [mailman] layout: which will have a value like `fhs`, `dev`, `here` or `local`. then look at [paths.xxx] log_dir: where xxx is the layout value, and if that includes $var_dir, look at [paths.xxx] var_dir: For the Django log look in settings_local.py and settings.py or whatever they're called in your case for LOGGING['handlers']['file']['filename'] > So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org… That page should be the same as <https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org…>. Can you go there? Where are you finding that link? What postorius version is this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: Where does sender postorius@ come from?

by Jens Günther

Am 15.06.23 um 00:34 schrieb Mark Sapiro: >> - Then I tried settings_local.py with: >> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > That is the correct place. It should work. Did you restart the container > after making this change? > Mh, unfortunately it does not work. - I changed the file and rebuilt the container. - I also restarted all 3 containers again. - I checked in the container the settings_local.py to verify that the change "arrived" and found it. - It still sends the "reset-password"-email with postorius@$SERVE_FROM_DOMAIN as shown in the screenshot. Is there any other way to test or check it? Any more ideas? Thank you in advance. ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: image/png Name: Bildschirmfoto_2023-06-15_22-55-29.png

2 years, 6 months

Re: Database running VERY hot

by Abhilash Raj

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

7 years, 9 months

Re: Link to account

by Mark Sapiro

On 4/11/23 23:08, Lars Bjørndal wrote: > > I would like to have postorius at .../mailman3 and admin, accounts etc. under .../mailman3/admin .../mailman3/accounts etc. Try this. In urls.py ``` urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), path('mailman3/archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('mailman3/accounts/', include('allauth.urls')), path('mailman3/admin/', admin.site.urls), path('mailman3/', include('postorius.urls')), ] ``` In apache ``` <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3/archives" "http://127.0.0.1:8000/mailman3/archives" ProxyPass "/mailman3/accounts" "http://127.0.0.1:8000/mailman3/accounts" ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/mailman3/admin" ProxyPass "user-profile" "http://127.0.0.1:8000/user-profile" ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" </IfModule> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

requiring questionnaire from new users

by Stephen J. Turnbull

Ethan Furman writes: > Is there a way to require new users to answer a questionnaire when > they subscribe? You could have it in the Postorius signup page template itself (see discussion below), but there currently is no way in Mailman to communicate that information to the moderator. Without modifying Mailman, you could have a separate signup page that invokes a Python program that notifies the admins and collects arbitrary data, as well as passing the normal subscription information to Mailman core for the normal address validation and moderator approval process. I have not done this myself, but a number of organizations have reported successfully creating alternative signup mechanisms (I haven't heard of this one). Such a signup page is the approach I'd recommend if the questions you have in mind would get free-form responses. Unfortunately, I do not believe the questionnaire responses could be displayed in the normal list admin interface without patching both Postorius and Mailman core, so this communication would have to be outside the normal procedure (but you would still use Postorius/core for the email validation and moderator approval steps). Perhaps one of the other devs has an idea about integrating it with the normal interface without patching. > I suspect that one of the lists I manage is getting a lot of > subscribers who don't understand what that particular list is for, > and having to answer a question or two would allow me to direct > them to better resources. I'm not sure how you want this to work. I guess you're getting this suspicion because new posters are posting a lot of off-topic stuff? So you want to have a subscription process where the moderators approve all subscriptions, and they would see the questionnaire responses in the subscription approval request? Not sure how well a simple questionnaire would capture this problem (see below), but it could help a lot, too. An alternative that doesn't inform the moderators is to modify the signup page template to (1) require the user check off the description of the list point by point (like a TOS notice, this is obviously not an improvement from the well-informed subscriber's point of view, though) and (2) provide links to commonly suggested alternative resources in the page template (these might be useful even to well-informed subscribers). The page templates are standard Django, so I'm sure that there's some facility for this. For example, if you were talking about python-dev, you could have Do you want to participate in implementation-focused discussions about work in progress to improve the Python language and its standard library? ( ) yes ( ) no If you answered 'yes', welcome! Do note that the focus is narrowly on implementation, and Python provides <a>many other venues</a> for new <a>ideas</a> and special interests like <a>distribution</a> and <a>documentation</a>. If you answered 'no', consider others of our <a>many lists</a> and our <a>Discourse channels</a>. - Do you want to discuss the best way to write a program in Python? ( ) yes ( ) no If you answered 'yes', <a>python-list</a> is probably a better venue for that. - Do you have a bug to report? ( ) yes ( ) no If you answered 'yes', please report it on the <a>issue tracker</a>. Discussion will take place there in any case, and you can attach a patch there if you have one. - Do you want to discuss a new idea to include in the Python language or standard library? ( ) yes ( ) no If you answered 'yes' but don't have a complete patch yet, <a>python-ideas</a> is probably a better venue for you. If you do have a patch, you should post it as a merge request on <a>GitHub</a>, too. This approach could get REALLY tedious (core-mentorship, scads of SIGs, etc). I think you'd have to add your own Javascript if you wanted to hide each recommendation until the new subscriber checks 'yes', but that would alleviate the annoyance quite a bit, I think. The only hitch is that I'm not sure Postorius wouldn't glitch on the extra information from the page, but even if so, that can probably be dealt with (a form without a submit button?) Regards, Steve

4 years, 4 months

Deleting archives

by Henrik Rasmussen

Docker-mailman 0.1: I have deleted some lists that I used for testing, but Hyperkitty seems to preserve the archives in the Available lists. Clicking on a list archive gets me to the archive of that list (with no posts because I haven't posted anything to the list). The URL is https://[WEBSITE]/hyperkitty/list/[LISTNAME](a)[LISTDOMAIN]/<https://[WEBSITE]/hyperkitty/list/%5bLISTNAME%5d(a)%5bLISTDOMAIN%5d/> (with a (a)), but when I click Manage subscription, the URI changes to https://[WEBSITE]/postorius/lists/[LISTNAME].[LIST<https://[WEBSITE]/postorius/lists/%5bLISTNAME%5d.%5bLIST>DOMAIN/ (with a dot instead of (a) which seems normal behavior) and I get a "Not Found The requested URL /postorius/lists/[LISTNAME]DOT[LISTDOMAIN]/ was not found on this server. " error. Of course I can't manage the subscription for a list I have deleted, but shouldn't the archive for a list be deleted along deleting the list. Henrik Rasmussen

8 years, 4 months

Mailman-users search results for query "Postorius"