Search results for "Postorius" - Mailman-users

Re: Customizing Look and Feel?

by Mark Sapiro

On 12/27/18 7:42 PM, Joel Lord wrote: > Is it possible to customize the look at feel of the web interface at > all? I have some lists that really require that subscription requests > include full name, to make the workload on the moderators, well, > workable in keeping a closed list tight. I've found where the "Your > name (optional)" text is in list_forms.py, but modifying that strikes me > as a poor plan. > > Changing that text would be lovely. Actually making that field required > would be seriously awesome. > > Is this possible in the current code base (3.2.0) without doing > ill-advised things modifying source code? None of this is really possible in Postorius without modifying source code. However, Postorius is just an example of a web list management UI. While it is non-trivial, it is possible to build your own web UI that either communicates directly with Mailman core's REST API or communicates via MailmanClient. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

Re: Unsubscribe Notifications Clarification

by Abhilash Raj

On Wed, Sep 2, 2020, at 7:32 AM, Brian Carpenter wrote: > I am trying to understand how Mailman 3 handles unsubscribe > notifications. From my testing I see the following behavior: > > 1. If list member sends email to listname-leave@listname, an > unsubscribe notification is sent to both list owner and list member if > list settings have them enabled. > > 2. If list list member is a registered user of Postorius and he uses > Postorius to unsubscribe, then no notification is sent out to either > list owner or list member, even if list settings has unsubscribe > notifications enabled. > > Is this correct? This is a bug in Core, for which I have opened https://gitlab.com/mailman/mailman/-/issues/759 It seems like the Unsubscriptions via the API do not follow the right codepath and just unsubscribe the user. It also does not seem to take the unsubscription policy into account. > Brian > _______________________________________________ > 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)

4 years, 11 months

Mailman Core 3.3.1rc1 release

by Abhilash Raj

Hey Everyone, I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1rc1/ To install this release via pip, you can run: $ pip install --upgrade --pre mailman Note the `--pre` flag because this is a pre-release. If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. If there aren't any major breaking changes reported, the final release will be identical to this one. -- thanks, Abhilash Raj (maxking)

5 years, 3 months

Re: SUBSCRIBE_FORM_SECRET in MM3?

by Mark Sapiro

On 1/30/20 1:50 AM, Gila Halpern wrote: > I've been looking into ways to prevent spam on my company's list, and one thing I came across was the SUBSCRIBE_FORM_SECRET option in the Mailman configuration, which embeds a CSRF token into the form, and prevents it from being submitted until five seconds after it renders, to keep bots from subscribing. Unfortunately, the information I found pertained to Mailman 2. Does this option exist in MM3 as well, or is there a similar option? This feature in MM 2.1 is not very effective. On mail.python.org, this feature as well as reCAPTCHA is enabled (e.g. <https://mail.python.org/mailman/listinfo/mailman-users>) and we still get periodic attacks of robotic subscribes that get around these measures. To answer your question, no, this does not exist in Postorius which is an entirely different, Django based web UI. Django may have some protections built in; I'm not sure about that, but there's nothing in Postorius itself like this MM 2.1 feature. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: Finding a user to delete them

by Brian Carpenter

On 3/14/20 5:03 AM, Stephen J. Turnbull wrote: > The bundled administrative interface*is* Postorius. The Mailman > shell is basically a quick hack (sorry Abhilash; if you want to call > it a masterwork and say the speed of development is testimony to your > skills, I won't deny it;-) to give more convenient access to > internals to experienced Mailman hackers. More administrative > features is something we plan to work on, but the Mailman project will > focus on Postorius for the forseeable future. I do think List Admins would want an interface to help "manage" a user account on behalf of a user then what is currently available in Postorius. I see this come up with my Mailman 2 clients frequently. For instance, a mm2 list member asked their list admin to subscribe them to a list topic to limit the amount of messages they receive. The list admin was new and open up a ticket to find out how they do that in which I replied showing them how they as a list admin, can go in and change options on behalf of a list member. I don't see this functionality built into Mailman 3 nowhere near the extent that Mailman 2 has. Last night a Mailman 3 client wanted to know how they can add a real name to a list member. I said you can't, not as list admin. I directed them to instead of unsubscribe the member and mass subscribe them so they can include a real name along with the email address of the list member. > For alternatives to Postorius and the Mailman shell, Brian Carpenter > (follow Allan's subthread) is working on a new management UI (using > PHP), and I believe there's a working node.js API "out there > somewhere". Please be very considerate of Brian's time; he and EMWD > constitute a bulwark of the Mailman ecosystem and will be even busier > with the UI project. But do pass on your suggestions to him as well > as to us, he's indicated he's open to that. There were some very good suggestions that were brought out in this thread and I had already passed them on to my developer. My approach with Affinity is definite leaning very heavy on the needs of list admins atm. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 4 months

Re: spanish localization

by Mark Sapiro

On 2/11/21 3:47 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > I contributed in january to translate to spanish all the items left in > Mailman Core, Django-mailman, HyperKitty and Postorius via Weblate. I > thought they will be used in the next upgrade, but I cannot see any > improvement and there are many words untranslated. The Spanish translations for Mailman core and HyperKitty are currently completely up to date with weblate. django-mailman3 differs in one string that was translated on Feb 10 and hasn't yet been merged. Postorius also differs in a few places from the Feb 10 version that hasn't yet been merged. Other than that, the translations should be good. > Is there any way to upgrade the .po files in order to get the last > translation? For the web UI you need to run the django management `compilemessages` command. For Mailman core you need to run ``` cd mailman/messages/es/LC_MESSAGES msgfmt -o mailman.mo mailman.po ``` to compile the mailman.po file for gettext. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

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

by Jens Günther

Thanks, already had a look at the issues and thought with the merge requests that it was solved :-) Maybe I have to update my mailman to 3.3.3 so that it does!? Or is it that you are saying that this hasn't been fixed but tried to and it didn't work!? Actually I see the logic of what you are talking about in the issues, but don't see if what happens with the code can be correct, since I'm unfortunately not a coder. Any other ideas how I could go on / help? This qould be a quite central feature for using mailman3 for us. Thanks anyway. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > On 3/19/21 6:38 AM, Jens Günther wrote: >> Thank you for your answer. I should have seen that in the Docs, but >> somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html >> >> I set it in the corresponding file, but unfortunately it doesn't work >> :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS >> works, changed here from '*' to 'localhost' and my example-domains, this >> works). It seems to be the same as this user describes (a while ago): >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > 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. > See these issues and MRs for more detail. > > https://gitlab.com/mailman/hyperkitty/-/issues/254 > https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs > https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs > https://gitlab.com/mailman/postorius/-/issues/394 > https://gitlab.com/mailman/postorius/-/merge_requests/500/diffs >

4 years, 4 months

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

On 24/06/2020 00:20, Mark Sapiro wrote: > Go to your Django admin web UI and look at your Django Mailman 3 Mail > domains. This will be at a URL like > https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ > > Do you see this domain there? If so, delete it. I hadn't logged in as admin before, so having done so I can now confirm that having done so this screen shows "0 mail domains" Because I could, I then visited "VIEW SITE" and see a mailing lists page, which is I think the same one I have been trying to visit, except of course now I am logged in. I do now see the correct, and only, mailing list configured on the core server. Returning to the previous "maildomain" page, that now shows the expected mailing list as well. Other admin pages seem to be working fine as well. I think, possibly, that it is now installed and working. ... But I don't know why. Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 1 month

Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Mark Sapiro

On 5/6/23 16:02, volkmar(a)grote-family.com wrote: > > My urls.py: >> (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py >> from django.contrib import admin >> from django.urls import include, reverse_lazy, re_path >> from django.views.generic import RedirectView >> >> urlpatterns = [ >> re_path(r'^$', RedirectView.as_view( >> url=reverse_lazy('list_index'), >> permanent=True)), >> re_path(r'^postorius/', include('postorius.urls')), >> re_path(r'^hyperkitty/', include('hyperkitty.urls')), >> re_path(r'', include('django_mailman3.urls')), >> re_path(r'^accounts/', include('allauth.urls')), >> # Django admin >> re_path(r'^admin/', admin.site.urls), >> ] We and the various docs are inconsistent about 'postorius' vs 'mailman3' and 'hyperkitty' vs 'archives' in urls. Add these re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), to your urlpatterns list in urls.py to cover both variants. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 14/2/21 18:42, Mark Sapiro wrote: > On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I did some exploration this morning (Spain time) in the weblate >> statistics and archives and I found that the changes done from >> Victoriano and me were recorded. I did a screencopy of all that if >> someone has any doubt about it. I downloaded this files: >> >> -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po >> -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po >> -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po >> -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po >> >> The thing is that they differ from the .po installed via pip upgrade. >> Mostly, as said, postorius, hyperkitty and django_mailman3. > > The latest packages in PyPI (pip) were released on Feb 2 except for > django-mailman3 which was released on Jan 15. They don't include updates > after those dates. > And I say that I (and others ) have made translations in postorius, hyperkitty an Django_mailman3 in January. Yes, I've made some changes in february 10th, but It were a pair of messages. But that's all about this from me. If in the next upgrade I find that there is any translation missing, I know, thanks to you and Victoriano, how to handle it. And if some new admin installs mailman 3 and try to localize it to spanish and comes to this list to ask how to do a more complete translation... well, these messages can point him or her to the right direction. My postorius web access to the lists is now almost completely translated to spanish and now I can help the users without hesitating language problems. Thanks. Thanks a lot.

4 years, 5 months

Mailman-users search results for query "Postorius"