Search results for "Postorius" - Mailman-users

Re: adding imprint / private policy link to postorius

by Abhilash Raj

On Tue, Sep 1, 2020, at 11:17 PM, Thomas Stein wrote: > > Hello one and all. > > Is it possible to add an imprint link to the postorius start page? I > guess it is, but it would be > nice if someone could me point to the right direction / documentation. > Something like they have: > > https://lists.openrailwaymap.org/mailman3/postorius/lists/ > There isn't an official way to do that, but you can patch your installation to update the footer. This[1] is the location and file you want to update and you can insert simple HTML there. If you are using system packages it should be somewhere in the `/usr/lib/python3/dist-packages` directory and in `lib/site-packages` if you are using a virtualenv based installation. https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/… > cheers, t. > _______________________________________________ > 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, 9 months

[MM3-users]Re: Moderation Emails & Page

by Simon Hanna

> I’m running the current MM3 from the bundler on RHEL7, and most things seem to be working properly. > ERROR 2016-04-20 14:58:05,959 base 3256 140375419246336 Internal Server Error: /mailman3/lists/listname/held_messages > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 22, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python2.7/site-packages/postorius/auth/decorators.py", line 77, in wrapper > return fn(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/postorius/views/list.py", line 413, in list_moderation > paginator_class=utils.MailmanPaginator) > File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 89, in paginate > results = paginator.page(1) > File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 62, in page > number = self.validate_number(number) > File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 39, in validate_number > if number > self.num_pages: > File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 86, in _get_num_pages > if self.count == 0 and not self.allow_empty_first_page: > File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 75, in _get_count > result = self.function(count=1, page=1) > File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 681, in get_held_page > return Page(self._connection, url, HeldMessage, count, page) > File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 333, in __init__ > self._create_page() > File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 363, in _create_page > self._connection, entry['self_link'], entry) > KeyError: u’self_link' This one seems to be a new one. To my knowledge held messages should not work because of this issue: https://gitlab.com/mailman/mailmanclient/issues/10 Your issue seems to be with postorius' paginator. Could you open an issue in postorius? https://gitlab.com/mailman/postorius/issues Please include this trace, and some additional info. * What version of django are you using? * What version of postorius are you using? * What version of mailmanclient are you using? To actually confirm the issue is with postorius and not mailmanclient, you could try to access the held messages through mailmanclient directly The easiest way to do this, is start a django shell. You need to activate the python2 virtualenv for this Replace manage.py with whatever command you use to start the webserver python manage.py shell from postorius.utils import get_client lists = get_client().lists lists[0].held # pick a list that has held messages lists[0].get_held_page() # and you could try getting one specific message lists[0].get_held_message(<held id>) if you can do all this, then the issue is probably in postorius

9 years, 1 month

Re: Customise Postorius templates?

by Duane Raymond

On Mon, 7 Feb 2022 at 00:56, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Feb 1, 2022, at 11:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 2/1/22 09:47, Duane Raymond wrote: > >> Hi, > >> I'm looking to do some radical customisation of the Postorius (and > Hyperkitty) templates over the next 6 ish months and was wondering if there > is a 'best practice' way to do this that will survive updates to MM3. I've > searched around and not found much and also tested copying > >> > venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html > >> to > >> var/templates/lists/summary.html > >> As suggested in some posts - but it didn't seem to pick up the > customisation - only customisations in the venv path worked - and they get > overwritten on update. > The best way to do this would be utilize Django’s template loader. See > here[1] for the documentation on how you can do this. You want to put the > path where you are putting the templates under `DIRS` option of the > `TEMPLATES` section. > > Do make sure that you are keeping the directory structure correct so that > Django can discover them. Like, Hyperkitty’s base.html should be in > `/custom/path/hyperkitty/base.html`, where `/custom/path` is what you’ve > setup in DIRS setting above. > This looks promising! I've not got it working yet, but this is what I've tried: 1. Created folder 'custom' in the mm root (in my case: /opt/mailman/mm/) 2. Copied the files and folders from postorius/templates/postorius/* and hyperkitty/templates/hyperkitty/* to the custom/ folder (not the full postorius/templates/postorius/ match, just evening in the second postorius/ dirrectory) 3. Recursive update of permissions of the custom/ folder and files to be mailman 4. Updated /opt/mailman/mm/settings.py by changing "'DIRS': []" to "'DIRS': [BASE_DIR, '/custom/']" in the "TEMPLATES =" section 5. Edited the original AND copied postorius/lists/summary.html to have a small change in the footer of each so I know what version it is serving 6. Restarted: gunicorn qcluster mailman nginx and cleared browser cache 7. Reloaded the 'info' page of a few lists to see which version ti was serving Variants: I've also changed the DIRS value to the hard-coded path: /opt/mailman/mm/custom Result: it is still serving the default/original Postorius template vs the custom one. Any suggestions for things I should do to make it use the /custom/ folder instead? Any recompiling or other actions beyond just restarting? (I probably don't need to restart qcluster and maybe not even mailman core for this to take effect but I do it just in case!) Cheers, Duane

3 years, 3 months

Re: postorius only show 50 owner lists

by Abhilash Raj

On Sat, Mar 2, 2019, at 3:41 AM, elalelopez(a)gmail.com wrote: > Hello, thanks for answering. > > The DB is postgresql. > > And it's not a paging problem. > > The paging buttons are disabled because I am trying to see all the > owner's lists. > > I understand that postorius executes the list_index_authenticated > function in postorius / views / list.py > > The description of the function shows: > > "" "Index page for authenticated users. > > Index page for authenticated users is slightly different than > un-authenticated ones. Authenticated users will see all their memberships > in the index page. > > This view is not paginated and will show all the lists. > > "" " That sounds like a bug in Postorius. Can you please report it on Gitlab (https://gitlab.com/mailman/postorius/issues)? > Regards. > _______________________________________________ > 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)

6 years, 3 months

postorius not displaying mailman logo

by sekamug＠yahoo.com

I successfully installed mailman3 but Postorius doesn't display images on the web interface. I have checked and the files exist at at the location /opt/mailman/web/static/postorius i have checked the logs and they appear as follows: [pid: 366783|app: 0|req: 43/104] () {34 vars in 687 bytes} [Tue Mar 22 09:36:30 2022] GET /static/postorius/js/script.js => generated 5280 bytes in 43 msecs (HTTP/1.1 404) 6 headers in 197 bytes (1 switches on core 0) [pid: 366783|app: 0|req: 44/105] () {34 vars in 715 bytes} [Tue Mar 22 09:36:30 2022] GET /static/postorius/img/favicon.ico => generated 5280 bytes in 43 msecs (HTTP/1.1 404) 6 headers in 197 bytes (1 switches on core 1) it seems the browser fails to access the directory where the pictures are stored. I have checked and mailman is the owner of that directory. Please advise.

3 years, 2 months

Ann: Postorius 1.3.6b1 is now out

by Abhilash Raj

Hey Everyone, I am pleased to announce that Postorius 1.3.6b1 is now out. This is the first pre-release for 1.3.6, which is slated to release next week soon after Mailman Core 3.3.5 release. This release requires Mailman Core 3.3.5 release, so if you are trying out this release, please also upgrade Mailman Core to 3.3.5rc1 (which was just released today). This release includes several new features and bug fixes. A full list of changes is available here[1]. With this release, we have also improved on the localization of the interface, if you want to help out before the release of the stable 1.3.6, please see the instructions for translators here[2]. We use Weblate for translations, so if you are familiar with that, you can directly head over there[3]. Since this is a pre-release version, you can install this using pip via: $ pip install --upgrade --pre postorius django-mailman3 mailmanclient Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). A release tarball is available on PyPI: https://pypi.org/project/postorius/1.3.6b1/#files Finally, thanks to all the folks who helped with this release in any capacity and made it possible. [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 [2]: https://docs.mailman3.org/en/latest/translation.html [3]: https://hosted.weblate.org/projects/gnu-mailman/postorius/ [4]: https://docs.mailman3.org/en/latest/upgrade-3.2.html#virtualenv-install thanks, Abhilash

3 years, 8 months

Re: nextcloud as auth provider for postorius

by Jered Floyd

Hi Falk, Social logins are mediated by django-allauth. Have you configured this properly in your settings.py? (See https://docs.allauth.org/en/latest/socialaccount/providers/nextcloud.html) Are there any errors in your mailman logs? Regards, --Jered ----- On Dec 1, 2023, at 7:08 AM, mailman3--- via Mailman-users mailman-users(a)mailman3.org wrote: > Hello, > > have anybody successful setup nextcloud auth provider for postorius? > I have done configured the OAuth 2.0-Client in > nextcloud/index.php/settings/admin/security. > I have add the nexcloud as social application in > mailman3/admin/socialaccount/socialapp/. > If i try to login via nexcloud, postorius redirect me to the nextcloud, where i > successful login, and redirected to postorius > But i'm not logged in postorius. > > what I'm missing? > Have anybody a howto? > > Thanks > Falk > _______________________________________________ > 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 jered(a)convivian.com

1 year, 6 months

Re: Ann: Postorius 1.3.6 is now out

by Mark Dadgar

On Sep 29, 2021, at 9:28 AM, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > On Wed, Sep 29, 2021 at 6:28 AM Abhilash Raj <maxking(a)asynchronous.in> > wrote: > >> Hey Everyone, >> >> I just tagged and released Postorius 1.3.6. This release includes both bug >> fixes and >> new features. >> >> Some of the notable features include >> - Ability to list and handle un-subscription requests to the list >> - Option to choose delivery mode and delivery_status directly when >> subscribing to a list >> - Addition of a user management interface, which allows updating a users >> password, >> manually verifying their email addresses, update user’s Display Name >> etc. >> - Expose a number of Bounce processing related options in List’s settings >> >> A full list of changes is available here >> >> >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 >> >> You can install this release using pip >> >> $ pip install postorius django-mailman3 mailmanclient —upgrade >> > > root@svr:/usr/local/mailman # pip install postorius django-mailman3 > mailmanclient —upgrade > ERROR: Invalid requirement: '—upgrade' > > Why do you think I got this? I had this issue too. I think some mail clients are turning a double-dash into an emdash. It should be: --upgrade - Mark ----- mark(a)pdc-racing.net | 408-348-2878

3 years, 8 months

per domain SITE_ID views?

by David Newman

Using FILTER_VHOST, I have two domains set up and working with MM3, Postorius and Hyperkitty. However, because SITE_ID in settings.py points to one of the domains, that domain name always appears on Postorius and Hyperkitty pages. The FAQ says there's a way to edit the SITE_ID used by a domain: https://docs.mailman3.org/en/latest/faq.html#id2 But I think that's just for which SITE_ID is associated with each domain, and not what's displayed. I already have 'dom1.tld' and 'dom2.tld' set as the display names for each site (under Postorius/Domains/Edit or admin/Sites/Site). The issue is that Postorius and Hyperkitty show 'dom1.tld' for all pages, even those in dom2.tld. Presumably this is because of the SITE_ID value in settings.py. How to get the correct domain to appear on that domain's Postorius and Hyperkitty pages? Thanks. dn

3 years, 5 months

Postorius 1.1.2 security release

by Abhilash Raj

Hi Everyone, I am pleased to announce that Postorius 1.1.2 is released and is up on PyPI[1]. This release fixes a security bug that sets the password of a user in Core to their display name. It is recommended that you upgrade to this version. Postorius (Django) and Mailman Core both have different notion of "user" and "password". When a user account in created in Postorius, it creates a user in Core using the REST API. This bug, causes the password of user created in Core to be set to their display name instead. However, as of now, there are no use cases of the user password in Core and it is present only for historical reasons. So, while this bug is a serious one, it wouldn't result in any real-world exploit. Along with the bug-fix, this release includes a new command that resets *all* user passwords in Core to a random value. Again, there are no use cases of these passwords so resetting *all* of them isn't going to cause any inconvenience to users. This command should be run after the upgrade: $ cd mailman-suite/mailman-suite_project/ $ python manage.py reset_passwords Python 2.7 is the only supported Python version for this release. All versions of Django <=1.11 is supported. For more information about GNU Mailman and Postorius, please see our website: http://list.org The source code is available on Gitlab: https://gitlab.com/mailman/ [1]: https://pypi.org/project/postorius -- thanks, Abhilash Raj

7 years, 5 months

Mailman-users search results for query "Postorius"