Search results for "Postorius" - Mailman-users

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

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

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, 3 months

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, 6 months

Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Simon Handfield

Hi, I have been working through other threads that indicate the same symptom (500 error when loading held_messages for a list). These include potential truncation of values in pendedkeyvalue table (don't this is our problem) and error when trying to access a message in /var/lib/mailman3/messages (ran the suggested code to loop through the stored files but no error was thrown.) Environment: Ubuntu 18.04 mailman3/bionic,now 3.1.1-9 all [installed,automatic] mailman3-full/bionic,now 3.1.1-9 all [installed] mailman3-web/bionic,now 0+20170523-14 all [installed,automatic] python-django-mailman3/bionic,now 1.1.0-4 all [installed,automatic] python-mailmanclient/bionic,now 3.1.1-5 all [installed,automatic] python3-mailman-hyperkitty/bionic,now 1.1.0-4 all [installed,automatic] Error reported in log with debug enabled: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get resource = self._make_collection(request) File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> for resource in collection] File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource resource['msg'] = msg.as_string() File "/usr/lib/python3.6/email/message.py", line 158, in as_string g.flatten(self, unixfrom=unixfrom) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 272, in _handle_multipart g.flatten(part, unixfrom=False, linesep=self._NL) File "/usr/lib/python3.6/email/generator.py", line 116, in flatten self._write(msg) File "/usr/lib/python3.6/email/generator.py", line 181, in _write self._dispatch(msg) File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch meth(msg) File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text msg.set_payload(payload, charset) File "/usr/lib/python3.6/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-9: ordinal not in range(128) I'm sorry if this is a query that's answered already but I have not been able to find matching thread that seems to relate to my error. Thanks for any advice on where to look next. Cheers, Simon. _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

6 years

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, 5 months

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

Re: Digest Formatting

by mailman＠manygoodideas.com

I have 2 more digest questions, which I'm hoping to get insight on: 1) Is there a way to trigger a digest for a user (for testing purposes)? Specifically, is there a function that can be revealed via the REST api to an interface like Postorius and Affinity? 2) I have customized list:member:digest:header, but am not seeing the custom text where I thought it should be. The documentation seems to imply that both list:member:digest:header and list:member:digest:footer surround each message in the digest, with the digest starting with list:member:digest:masthead. What I'm seeing is list:member:digest:masthead, which is followed by list:member:digest:header, then the TOC, then all the digest entries. Thanks. Jay

5 years, 10 months

Re: Postorius: Show only own lists

by Thor Atle Rustad

2018-01-23 16:59 GMT+01:00 Terri Oda <terri(a)toybox.ca>: > > > On January 23, 2018 6:26:51 AM PST, Thor Atle Rustad < > thor.rustad(a)gmail.com> wrote: > >2018-01-23 14:37 GMT+01:00 Simon Hanna <simon(a)hannaweb.eu>: > > > >> On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > >> > >>> Imagine an installation with 500+ mailing lists and almost as many > >local > >>> admins that are supposed to maintain their own local lists with a > >few > >>> local > >>> members. As site admin, I see all 500+ lists, but I was expecting > >*local* > >>> admins to see only the lists they maintain. I have set all lists to > >>> "advertised = False", so they are hidden from ordinary view. Is > >there a > >>> way > >>> to show only relevant lists to local admins? > >I believe I wrote Postorius in the subject line, but it may not be so > >obvious. So yes, in Posterius I would like to hide the lists from email > >harvesters, while relatively "untrusted" admins should have access to > >basic > >operations on the one list he/she "owns" (and without having to browse > >through 50 pages of mailing lists). Somehow I don't think 500 > >superusers in > >our system is a good idea! > > What do you mean by local admins? > > Is this > 1. Giantsite.example.com hosts lists for a bunch of domains, and you want > the logged in admins of mydomain.com to see their list admin pages but > not otherdomain.org's lists > > 2. You want each logged in admin to have their own personal dashboard of > list admin pages for lists they administrate, even though they're all under > one big domain. > > (Neither of those scenarios talks about archives, since you say you're > only talking about postorious) > > I think #2 is something we should be doing, and the old "todo" section of > the interface kind of was made with that in mind. Probably worth mocking > up some screenshots and opening a feature request to keep the idea in mind, > but it should be more a matter of prioritizing how things are displayed > than any huge change. > > I'm not sure if we have a "local admin" concept in the system that lines > up with #1, though. > > Ok, this would more like number 2. It's National.dogclub.com with its various mailing lists like poodle.dogclub.com, which expands to poodle-regionA.dogclub.com, poodle-regionB.dogclub.com, poodle-regiionC.dogclub.com and so on. So with dozens of different dog breeds and geographic chapters, the number of mailing lists are between 500 and 1000, but all are under the same dogclub.com domain. The members of each list should be maintained by a person with some elevated rights, but not enough to mess up the system. What I called "local admin" should have rights to add and remove members of, say, the poodle-regionA mailing list.

8 years, 7 months

Mailman-users search results for query "Postorius"