Search results for "Postorius" - Mailman-users

Re: Assistance with mailman3

by Abhilash Raj

On Wed, Mar 13, 2019, at 8:47 AM, ayen(a)afilias.info wrote: > Hi all > > I'm pretty new to mailman but been trying to install mailman 3 and been > running into issues, following the documentation at > http://docs.mailman3.org/en/latest/prodsetup.html > installed Python 3.6, nginx, ruby-sass > then with pip installed whoosh mailman-hyperkitty postorius hyperkitty > mailman > > tried to start mailman core, symlinked master and runner -> /usr/bin/ > (otherwise it wouldn't run) > mailman core starts but when I hit the api url I get this in the logs > > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", line 218, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 248, in __call__ > responder, params, resource, req.uri_template = > self._get_responder(req) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 664, in _get_responder > route = self._router_search(path, req=req) > TypeError: find() got an unexpected keyword argument 'req' > Mar 13 10:54:44 2019 (17273) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 > > and on frontend "A server error occurred. Please contact the administrator." Inside your virtualenv, please run: $ pip install -U falcon==1.4.1 This should fix the above error. > > that leads to my gnu not working and throwing keyerrors for postorius. > > I'm using a clean install of ubuntu 18.04 but have also tried to > install on centos 7 with no success. > > Are there any missing dependencies or steps that I've missed any > assistance would be appreciated. > > Andy > _______________________________________________ > 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)

7 years, 4 months

An archive/read-only list on a full setup?

by Andreas Schamanek

I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly. After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc. What's the proper way to set up a hyperkitty-only list? -- -- Andreas :-)

3 years, 3 months

Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 10:25 AM, Mark Sapiro wrote: > I just upgraded from Django 3.2.11 to 3.2.14 on mail.python.org and > lists.mailman3.org. How to upgrade mailman-web to align with Django? I upgraded from Django 3.0.14 to 3.1.14 and then 3.2.14 using these docs: https://docs.djangoproject.com/en/4.0/howto/upgrade-version/ But then this upgrade command returned a complaint that mailman-web 0.0.5 requires Django<3.1: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi and it downgraded Django back to 3.0.14. I did not see anything about this in the Django for Mailman Admins doc, but I may have missed something. https://docs.mailman3.org/en/latest/django-primer.html Thanks. dn

4 years, 1 month

Mailman 3 Core user assistance

by Tony Deshields

I currently have a docker mailman stack that utilizes Django LDAP backend for authentication. I have my users attributes mapped as you see below in my settings.py file. Whenever a user logs into postorius with their 'uid', mailman-core uses their 'uid' as their email address instead of the 'email' attribute. Is there anyway to change this functionality? I would like my users to be able to login with their enterprise uid but be mapped to their email but I feel like there is a disconnect between Django and MM3 core. Any assistance is much appreciated. AUTH_LDAP_USER_ATTR_MAP = { "uid" : "userPrincipalName", "first_name": "givenName", "last_name": "sn", "email" : "mail", }

2 years, 6 months

Re: Unknown attribute: max_message_size

by Mark Sapiro

On 06/21/2018 03:29 AM, Alexander Klotz wrote: > Hi, > > unfortunately we still have problems configuring a list so that it > allows a message size larger than 40 KB. Neither the workaround > described here: > https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24… > (required was already set to false) nor this docker setup by yova > https://gitlab.com/mailman/postorius/issues/246 worked. Are there any > other options we could try? Use 'mailman shell'. I.e. 'mailman shell -l listname@domain' and set m.max_message_size = N where N is the number of KB you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

Re: Where does sender postorius@ come from?

by Mark Sapiro

On 6/15/23 14:03, Jens Günther wrote: > > > Am 15.06.23 um 00:34 schrieb Mark Sapiro: >>> - Then I tried settings_local.py with: >>> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' Sorry, this is actually a different setting. There are actually two more that control this. These are DEFAULT_FROM_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> and SERVER_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note that the defaults mentioned in the Django docs are probably overridden in your settings.py, but you should set them in settings_local.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: >Hi Mark, > >Actually all this stuff happens inside the container after it's started >and >initialized without errors. I didn't amend the image anyhow. > >Also I have the configuration based on docker-compose.yaml provided in >the >repository which works just fine for mailman-web image. > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) >fails >with 500 error... > >Now answering your questions: > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > >> do you have django-q in INSTALLED_APPS in your Django settings and >what >> is set for Q_CLUSTER? >> > >I've checked settings.py inside the container and I haven't found any >of >the mentioned configurations there. > >Does the manage.py that's being run here point to the right >settings.py? >> > >No clue. > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK >configured image? > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Because I am a dum dum ;-) Will work on removing those crons and stuff. Would be nice if you opened an issue on Github so that I don't forget. >Danil > > > >> -- >> 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/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

7 years, 5 months

Re: Lessons learned and a couple little gotcha for newbies

by Mark Sapiro

On 4/13/22 05:23, Paul Ssekamatte via Mailman-users wrote: > hi William, > please clarify what you mean by this step > 8. You need to manually set the local virtual host for mailman3 > Thank you He means that if you are going to use the alias domain feature discussed at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… you need to actually set the value you choose for the alias_domain in the Postorius domains view or via REST 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

4 years, 3 months

Fwd: Re: Removing a mail addresses and users

by Allan Hansen

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). 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. 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? 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. 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. 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/

6 years, 1 month

Re: Docker Installation of Mailman -- The Hyperkitty Chronicles

by Mark Sapiro

On 12/22/18 6:08 AM, brian(a)emwd.com wrote: > Using Maxking's docker project to install mailman3, I have a fairly functional mailman3 installation. However Hyperkitty is not archiving or showing list participants like: ... Check your list's Settings -> Archiving in Postorius and make sure policy is public or private and HyperKitty is active. Also, make sure the cron jobs are running. I'm not sure how this is set up in the Docker container, but see <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Mailman-users search results for query "Postorius"