Search results for "Postorius" - Mailman-users

Docker files for mailman

by Simon Hanna

Hi, I started working on docker files for Mailman. I created three repositories: - https://github.com/simonsmiley/postorius-docker Holds the files needed to create a postorius container - https://github.com/simonsmiley/mailman-docker Holds the files needed to create a core container - https://github.com/simonsmiley/mailman-compose Holds docker-compose files that greatly simply the process of running the containers * The mailman repo currently lacks documentation * Currently no emails can be sent. I still have to figure out what the best way is... * Hyperkitty will be added next (together with a complete "bundler" install) I pushed two images to the docker hub. Their names are thelinuxguy/postorius and thelinuxguy/mailman I created two organizations mailman on docker hub and gnu-mailman on github https://github.com/gnu-mailman https://hub.docker.com/u/mailman/ I know we shouldn't use github, but there is no way around github/bitbucket for automated builds on docker hub. I post here to inform you about the docker images and I also to ask if I'm allowed to keep these two organizations and move my images/repos there. I'll happily give push/owner access to additional people if requested. The repositories could be mirrored to the gitlab mailman group, sadly the process doesn't work the other way round just yet. In case this request gets denied, I'll just remove the organizations and let the images be "unofficial". cheers, Simon

8 years, 4 months

Re: Starting from scratch

by Mark Sapiro

On 04/09/2018 10:01 AM, Benjamin Ragheb wrote: > > The two alternatives I am weighing right now are: > > 1. Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration. > > 2. Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.) > > Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python. > > Which is the least crazy option? If you are comfortable with 2), I think that's the better option. After PyCon in May when we release 3.2 and the rest of the suite, you should be able to install everything with pip and have it work. I'm not sure what the issues are now with a pip install. There is a 3rd option. See <https://packages.debian.org/stretch-backports/mailman3-full> -- 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: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Odhiambo Washington

On Sun, May 7, 2023 at 8:52 PM Volkmar Grote <volkmar(a)grote-family.com> wrote: > Hi Mark, > > On 07.05.23 01:31, Mark Sapiro wrote: > > 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. > > > thanks for the quick reply. > I am one step closer to a solution, > "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. > I get the functionality, but it looks ugly w/o any graphics, for which I > get yet another, slightly similar, error message: > > > > > > Page not found (404) > You can run: '/opt/mailman/mm/bin/django-admin clear_cache' as the mailman user. After that you can also restart Nginx, then test again and see if everything works. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 6 months

Avoiding non-members to be saved.

by Stephen J. Turnbull

Guillermo Hernandez (Oldno7) via Mailman-users writes: > Yesterday I had a problem with a private list. A spammer sent a mail > forging one address that was a non-member (in fact was an "accept this > no subscriber mails" from mailman 2.1 import) with very bad intentions > and it was distributed. If you upgrade from Mailman 2 to Mailman 3, the accept_these_nonmembers list for each list is grandfathered into the Mailman 3 list (from rules/moderation.py): # Check the '*_these_nonmembers' properties first. XXX These are # legacy attributes from MM2.1; their database type is 'pickle' and # they should eventually get replaced. for action_name in ('accept', 'hold', 'reject', 'discard'): legacy_attribute_name = '{}_these_nonmembers'.format( action_name) > There were no list of "accept this non members" in the Postorius > config If there is no such list in Postorius, I would guess that some developer thought "OK, this is a legacy feature and I'll get back to it when we move it to the proper database" (unfortunate, but most of us have open-subscription member-posts-only lists, and the current workflow seems to work well, so this feature may not be so salient). > I think it is solved now (deleting all and putting to hold just the > non-members addresses that I would want to pass messages on) This should not be necessary, unless there were pre-approved addresses that are no longer appropriate. But Mailman can't know that! > The fact is that any sender address of mails sent to the list is saved > as a "non member", and it make me nervous as it will grow despite it is > a legitimate message or not. As far as I can see there is no other rule except that legacy rule (and the rule that accepts all posts, which is rarely used) that will accept a post from nonmembers. > Anybody knows if there is a per list config to avoid saving all that > addresses as non members? o a overall config? No, there isn't, and there never will be. This is a basic design decision about the representation of "people who participate in any way in mailing lists". The only way to prevent creation of an Address object for the sender of an email is to reject or discard the post (in which case the "create an Address" path isn't entered), and don't set a moderation action on the sender. Obviously if you set a moderation action, that will create an Address in the database. The problem you encountered is not preventable by any means whatsoever: a malicious actor discovered an address that is allowed to post. The specific case you're worried about, that nonmembers will automatically be allowed to post, is not possible. The only way to get on the list of "accept_these_nonmembers" is to be inherited from accept_these_nonmembers on the parent Mailman 2 list, or an explicit decision by a moderator. The fact that this list is not exposed in Postorius is a bug, but I can't say when it might be fixed. It appears that the current process (the moderator can set the sender's persistent moderation action separately from approving or rejecting a particular post) works fine, since this is the first time I've heard of this issue, and as you present it, Mailman is doing the best it can since Somebody Authorized put that sender on the approved list in Mailman 2. If a particular nonmember becomes a problem, you can access that User or Address in Postorius and set them to Hold, Reject, or Discard. The process of deleting all nonmembers has been more difficult than it should be, but this is being fixed, IIRC in the next release. Steve

3 years, 3 months

Re: Default values for lists in Mailman 3

by Markus Grandpré

Dear Mark, dear list, in Menu "Mass Operations / Mass Subscription" I have set the default value for checkbox "Invitation" in file </usr/lib/python3/dist-packages/postorius/forms/list_forms.py> (on Debian 12) as you had suggested: invitation = forms.BooleanField( label=_('Invitation'), initial=True, required=False, help_text=_( 'If checked, the other checkboxes are ignored and the users will ' 'be sent an invitation to join the list and will be subscribed ' 'upon acceptance thereof.' ), widget=forms.CheckboxInput(), ) However, administrators of mailing lists on our Mailman3 demo system report that the invitation is still sent, even if they have deactivated the sending of the invitation via the “Invitation” checkbox. What have I done wrong? Best regards, Markus Am 20.09.24 um 09:05 schrieb Markus Grandpré: > Thank you very much for your answer. > > Best regards, > Markus > > Am 19.09.24 um 22:03 schrieb Mark Sapiro: >> On 9/19/24 05:46, Markus Grandpré wrote: >>> Dear list, >>> >>> I would like to activate the invitation setting for all lists as >>> default. In Mailman 2.1 I have done this in the file </etc/mailman/ >>> mm_cfg.py>: >>> >>> >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> >>> >>> How can I do this in Mailman 3? >> >> There is a draft merge request at https://gitlab.com/mailman/ >> postorius/-/merge_requests/930 which implements a framework for >> setting Postorius defaults and creates a setting to set the default >> for pre- verified on the mass subscription page. Once merged, this can >> easily be extended to provide a default for Invitation. >> >> In the mean time, you can only do this by patching src/postorius/ >> forms/ list_forms.py like >> ``` >> --- a/src/postorius/forms/list_forms.py >> +++ b/src/postorius/forms/list_forms.py >> @@ -1283,7 +1283,7 @@ class ListMassSubscription(forms.Form): >> >> invitation = forms.BooleanField( >> label=_('Invitation'), >> - initial=False, >> + initial=True, >> required=False, >> help_text=_( >> 'If checked, the other checkboxes are ignored and the >> users will ' >> ``` >>> Can I also transfer other default values like: >>> >>> ... >>> DEFAULT_SERVER_LANGUAGE = 'en' >>> DEFAULT_SEND_REMINDERS = 1 >>> DEFAULT_SUBSCRIBE_OR_INVITE = Yes >>> DEFAULT_PRIVATE_ROSTER = 2 >>> DEFAULT_ARCHIVE = Off >>> DEFAULT_ARCHIVE_PRIVATE = 1 >>> ... >>> >>> from the very same configuration file to Mailman 3? Is there a >>> documentation of the default values for lists in Mailman 3? >> >> This is done by creating a list style with the desired defaults. See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/ >> styles/ docs/styles.html for documentation of styles and see https:// >> gitlab.com/ mailman/example-mailman-plugin for an example of creating >> a plugin in Mailman core to make a persistent style. >> >> There is no specific doc for the list settings. You need to look at >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/ >> base.py for the various settings and https://gitlab.com/mailman/ >> mailman/-/blob/master/src/mailman/styles/default.py to see which >> default classes are applied for various styles. >> > > > _______________________________________________ > 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 markus.grandpre(a)uni-konstanz.de -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 month, 4 weeks

Re: [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by Mark Sapiro

On 2/28/21 10:17 AM, blackout69 wrote: > Hello everybody,I received this error message and from that moment the > maiilan3 has stopped working.I restarted the following services mailman3 > and mailman3-web and everything started working fine.Can you tell me > what is the problem my django server has encountered? It looks to me like a race condition of some kind or possibly an incompletely deleted thread. Have you deleted any threads? I'm curious as to how you happen to be going to <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> as opposed to <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. I know that ULS and similar ones are in HyperKitty's urls.py, but I don't see them exposed on any pages. Anyway, when you say "from that moment the maiilan3 has stopped working." (sic) exactly what stopped working. Did core stop delivering messages? Did Postorius stop working. If so, this all may be related to some underlying database issue or something like that that was fixed by the restarts. I don't see how this HyperKitty error could affect Postorius or 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, 8 months

Re: Fwd: Re: Removing a mail addresses and users

by Abhilash Raj

On Wed, Jun 10, 2020, at 3:33 PM, Allan Hansen wrote: > All, > > This disconnect between Mailman Core and Django and Postorius is, by > far, the weakest and, for subscribers, most confusing aspect of MM3 > (once it has been installed, which is extremely hard and confusing). The disconnect was intentional to make sure that we are fully able to leverage the power of Django's ability to run multiple dis-connected applications in a single Site and Account system. And Mailman Core was intentionally designed to not be an account management system so it can be kept simple. The disconnect however has caused more confusion than has helped, which we acknowledge. But this disconnect doesn't exist all that much right now, barring any bugs. We synchronize most of the state from Postorius down to Mailman Core including, any additional addresses that you add, primary address etc. Display Names don't trigger an update in Core, but it isn't that hard to do if you open a ticket. > > In a true account-centric system, you set up a web account and from > there manage your emails and, for each email, your subscriptions. > Subscription options would be hierarchical: account/email/list, with > lower levels inheriting/overriding settings from/the level above. You are able to sign in via web and manage your email and subscriptions. The preferences also work exactly how you described above where the lower level override the default and/or upper level settings. > > That’s really what I had expected when I pushed for us to move our 50 > email lists to MM3 and I was very excited about the prospect, > as it would solve a lot of system/subscriber management issues I had > managing MM2. > > Alas, I was very surprised that that’s not how MM3 works. Some things > got harder, even, such as the inability to change subscription > addresses, which should have been a showstopper from the start! > I still hope that MMxx OOTB will get there, but I guess it’ll be along > haul. Would we be talking about MM4 to be released 20 years from now? As a Subscriber, you are able to do switch emails in subscriptions from your options page. The URL to which is displayed in the List's Summary page when you are logged in. Yes, it requires an approval if the list's settings are set to moderate but that is going to be fixed, see this issue[1]. It is quite simple IMO to fix this one, if someone wants to take this up. [1]: https://gitlab.com/mailman/postorius/-/issues/425 Are you asking about switching emails as an administrator for your subscribers? > Some dedicated and skilled developers are currently investing heavily > in a replacement for Postorius, but I really believe that any work is > better spent transforming Mailman Core etc. into a true account-based > system. Then, and only then, will it make sense to build new and better > interfaces on top, as, without a healthy core, such interface will > currently may have to inherit the confusion and disconnect that > currently is so aggravating. I don't know if we want to add account management to Core, but User management is missing from Postorius, that is true. We punted on it and delegated that part to Django's admin interface. Long long time ago, I remember seeing that there was a User's tab for managing users, but that has since changed I think. If you and some others on this list would like to propose an RFC here[2], it would be a great help for me. What I am basically looking for is what kind of "User management" are administrators looking for. It doesn't have to be too detailed but a single line example would be: - As a Admin, I would like to delete a User completely from my system, including all their addresses and subscription - Also, it would be good to delete their account but retain their subscriptions - As a Admin, I would like to update User's attributes in the system like: - Manually verify their email address - Manually update their Name - As a User, I would like to delete my own account and all the subscriptions. Maybe this could be a starting point, but something like this can be added to Postorius. [2]: https://gitlab.com/mailman/postorius/-/issues/new As for the question in this thread, you are able to delete the User from Django's admin page and that would delete all the related EmailAddress for them. Deleting an Email address doesn't delete the User, since the relationship exists that User owns Emails. There is currently no way to delete all the subscriptions for a User though. > The above is not meant to aggravate the MM3 development team, for which > I have utmost respect and gratitude, and which I admire for their > tireless support given over decades to the community of admins. > Software development is devilishly hard and time consuming. And thank you for posting what you think is an important enhancement to Postorius. We don't have a very strict process to choose what new features to work on, so email like this do help us prioritize. Other users could also help by upvoting or just adding "+1" to the bugs/feature enhancements that affects them the most so we can fix them sooner rather than later. I would be more than happy if more people participated in just being able to prioritize features, all the work really happens in the open on Gitlab. As administrators of some 'open source' lists, the needs of us as admins are somewhat different from what would be in a closed organization and ability to kick someone completely out of the system is something never I had to do since folks are supposed to manage their own subscriptions. We do ban people from sending emails if they've been spamming, but that is a different thing, they are still able to login into Postorius AFAIK. > Yours, > > Allan Hansen > hansen(a)rc.org > > > > > > Begin forwarded message: > > > > From: Mark Sapiro <mark(a)msapiro.net> > > Subject: [MM3-users] Re: Removing a mail addresses and users > > Date: June 10, 2020 at 12:46:01 PDT > > To: mailman-users(a)mailman3.org > > > > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: > >> Hello. > >> > >> I tried to remove random email address signing ups (which I signed up > >> while testing) via admin panel. After removing I tried to sign up again, > >> but I am getting, > >> > >> 'A user is already registered with this e-mail address' > > > > You removed the user's subscription from the list, but you didn't remove > > the user from the system. > > > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > > User's have addresses and a user or one of the user's addresses can > > belong to a list with one or more roles (non-member, member, moderator > > or owner) > > > > > >> Combing through the database, I found auth_user table in mailman3web db > >> still contain those mail address. How to wipe email address entirely > >> from the db so I can signup again without the 'forget password' method > > > > There are a couple of things. If you log in to the web UI as a django > > superuser, you can go to the django admin UI -> Users section and delete > > the User, but I think that will only delete the web user and not delete > > the user from Mailman core. > > > > You can also log in to the web UI as the user and go to > > <https://lists.mailman3.org/user-profile/delete>, but that again only > > deletes the web user, and if you could do that, you could just subscribe > > once you're logged in, so I assume that's what you want to avoid. > > > > I don't think there is a way for a user as opposed to a site admin to > > delete her user record from Mailman core and even for a site admin, > > there's no way in Postorius to delete a user from core. It has to be > > done via REST > > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > > or `mailman shell`. > > > > -- > > 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/ > > _______________________________________________ > 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, 5 months

Re: Bounce counter visibility for List Admins

by Mark Sapiro

On 5/19/21 4:10 AM, smorytko(a)gmail.com wrote: > As you may know, we use MM3 but the Affinity/Empathy flavor and we only have List Administrator using the Postorious/Affinity. Unlike many here, we have no access to any server-based files. > > Can someone tell me if Postorious gives list administrators visibility into the bounce counters? User's bounce scores are not available in REST so neither Affinity nor Postorius has access to them. > While List Admins get to set various bounce counters we have no visibility of those counters until, all of a sudden, an entire source of subscribers hits the bounce threshold and gets bounced off the list. It would be really nice to be able to see the bounce counters and possibly head off trouble before users/subscriber mail hosts. It can serve as an effective early warning system that something is wrong. > > Assuming Postorious cannot, is there another way List Admins can inspect bounce counters? Email command? In the next release of Mailman core (3.3.5), lists will have a `bounce_notify_owner_on_bounce_increment` setting which if True, will send to the list admins a notice including the triggering DSN when a user's bounce score is incremented. This setting will also be exposed in Postorius 1.3.5. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Re: seems solved (was: Re: error changed after restart)

by Guillermo Hernandez (Oldno7)

On 8/2/21 11:26, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 7/2/21 19:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 7/2/21 19:04, Abhilash Raj wrote: > > Well... I did reinstall all mailman relationed apps with a > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient > > Restarted thee apache24 server... > > Aaaaaand closed de admin session and reopened it... (just for a "what > if" sensation). > > I can not tell what have been the solution here, but now I can access > the administrative pages and attend de pending subscriptions and > discard retained messages. > > Thanks Abhilash and Mark for your support. Some things did not work well enough after that (the subscriptions pending approval, between others), and then I did an pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django (adding postorius and django to my previous reinstall) And a su -m mailman3 -c "python3 manage.py collectstatic" in the mailman dir (mailman3 is the user who exectues all mailman related things) and again a su -m mailman3 -c "python3 manage.py migrate" And it seems there were things pendig to update... Restarted the server and now it seems all is OK. Thanks all and sorry for the noise.

3 years, 9 months

Re: Mailman3 on virtual domains

by Mark Sapiro

On 10/7/23 09:25, Lars Bjørndal wrote: > [Mark] > > [...] > >> See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > > Ok, so I have to create an alias_domain in Mailman. Is it possible to do that from the web interace? It has been in postorius since 1.2.0. > I find an Edit button for each domain, and then I may change name and description. But I can't find an option to add an alias_domain. As I'm blind, and using a text only browser, some information may have been missing. Or can I do it from the command line? If your Postorius is >=1.2.0, there should be 3 fields on the Edit domain page - Description, Alias Domain and Web Host. The whole page looks something like: Edit domain example.com Description Alias Domain Normally empty. Used only for unusual Postfix configs. Web Host The domain from which you want the web UI to be served from. This can be same or different from the Mail Host. You can edit the list of available web hosts here. You can also set an alias_domain in `mailman shell`. E.g., ``` >>> domain = getUtility(IDomainManager).get('example.com') >>> domain.alias_domain = 'x.example.com' >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

Mailman-users search results for query "Postorius"