Search results for "Postorius" - Mailman-users

Re: Time Zone Problem In Postorius

by Mark Sapiro

On 1/12/22 7:34 PM, Alan So wrote: > I notice that the template was updated to add the code. However, I still observe an issue. > > If the correct hold date is: 2022-01-13 10:16 GMT+8 or 2022-01-13 02:16 GMT > If I select my time zone as Asia/Hong_Kong, it is displayed as Jan. 13, 2022, 2:16 a.m. > If I select time zone as GMT, it is displayed as Jan. 12, 2022, 6:16 p.m. > > There is a shift of -8 hours when displaying the time in Postorius. I cannot find the detail of the held message from database tables yet. Not sure how the hold date was stored at this moment. As you note later, the hold time is stored in UTC. It should be rendered in Postorius held message view in the timezone that you have set in your user-profile. The timezone conversion is in Django. It is defined in the template as ``` {{ msg.hold_date|datetime_parse|localtime|date:"DATETIME_FORMAT"}} ``` where msg.hold_date is the time in UTC. I think the issue is that while msg.hold_date in in UTC, it is a naive datetime.datetime object (see https://docs.djangoproject.com/en/4.0/topics/i18n/timezones/#interpretation…) so if your Django setting for TIME_ZONE is Asia/Hong_Kong it is interpreted as UTC +0800 so that subtracts 8 hours and then conversion to your profile timezone if Asia/Hong_Kong adds 8 hours back. I think if you set `TIME_ZONE = 'UTC'` you will get the behavior you expect. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2022-12-14 17:26:59 -0800 (-0800), Mark Sapiro wrote: > On 12/14/22 13:40, Jeremy Stanley wrote: > > > > Once these entries are automatically added by visiting that page, > > they're all associated with the one "web host" ("site" in Django) we > > have for the server, and now the list filtering functionality in > > Postorius breaks and any of the vhosts all display the full set of > > mailing lists on the server rather than only those associated with a > > particular vhost (note that this seems to only be confusing > > Postorius, Hyperkitty has them correctly filtered still). > > See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > and also below. [...] While this does appear to solve the problem on my test deployments, a challenge that I'm left with is how to automate it. Our community takes an "infrastructure as code" approach to all the services we run for our projects, and we make sure that we can automatically bootstrap every system from scratch into a working state. Unfortunately, I'm not having any luck finding an API or CLI which I can use to create sites and domains rather than manually doing it in the Django admin WebUI. Does such a thing exist, or an I going to need to resort to directly performing database inserts (which I'd rather avoid since it could break if the schema changes). It appears there's a foreign key relationship involved, which could make DB manipulation like this even more fragile. -- Jeremy Stanley

3 years, 9 months

Re: Postorius permissions granularity

by Odhiambo Washington

On Thu, Dec 11, 2025 at 12:07 PM Liam Reilly <l.reilly(a)ucl.ac.uk> wrote: > The issue is we don't want first line support staff to have superuser > permissions, just the ability to assist end user list owners by being able > to administer all lists. So something that is lower level than full > superuser would be ideal. > > I'm considering a cron job that adds a web account as Owner to all lists > but this feels like a bit of a bodge. > I see. The permissions that can be granted in relation to Postorius are quite limited. PS: Is it possible that you could retain content that comes in the form of responses to your posts, so the hierarchy is maintained? You seem to be deleting everything, which make your post look like a new one, except for the subject. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months

Re: Starting new thread in Postorius -> disappears

by Thor Atle Rustad

I go with the workaround from Cameron Smith: sudo docker-compose exec mailman-web ./manage.py runjobs yearly makes messages appear However, there was "something" else that caused my messages not only NOT to show up in Hyperkitty, but also caused them not to be sent in the first place. I believe the reason was wrong subdomain in SERVE_FROM_DOMAIN in docker-compose.yaml. 2017-11-22 0:38 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 11/21/2017 01:53 AM, Thor Atle Rustad wrote: > > I have had this working before, so I guess it's a simple setup error. > > > > When I send a message from the Postorius interface, it is neither sent > out > > or stored. I briefly see this message: "Your reply has been sent and is > > being processed.", and then nothing happens. > > > I assume you mean HyperKitty. Postorius has no facility for posting > messages to a list. > > > > I have installed maxking's docker-mailman and copied my old setup with > > basic stuff like passwords and such. The only new thing is that I'm now > > running in userspace by putting in /etc/subuid and subguid: > > > When you post from HyperKitty, HyperKitty creates a > django.core.mail.EmailMessage() instance and calls it's send() method > which causes Django to send the message to the list address. It then has > to be received and processed by Mailman the same as any email post > before it will appear in the archive. > > Are you running with DEBUG = True. If so, Hyperkitty won't send the mail. > > If DEBUG = False and normal posting is working, perhaps there is some > Postfix issue in delivery of the message from Django to Mailman. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 11 months

Re: footer template priority

by Sam Darwin

Thanks. That fixed it. Comments: 1. In the docs, the instructions say "POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'. As a reader, you are thinking, I'm running both hyperkitty and postorius. Hyperkitty is at /archives/ and postorius is at /mailman3/ . What about the path '/mailman3/ for postorius? The doc could mention the path even if it's to explain why it's not needed. (The reason perhaps it's not needed is root will redirect to '/mailman3/'.) 2. This all seems very self-referential. The setting goes into settings.py which is the website for postorius itself. It is accessing itself. Given that's the case do you really need to tell Django about it's own URL? Doesn't it know it's own URL already? Could Django just contact itself without being configured? 3. Logging... when it can't find the templates, does it log an error anywhere? 4. The server had been up for a year. After I rebooted, the problem vanished, even after removing the new setting. So either it's caching the setting in Redis, or else the problem is really gone. Very strange. Anyway, that was it. thank you.

1 year, 4 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 5:41 PM, Ruth Ivimey-Cook wrote: > >>> My reason for thinking, in my original post, that the wrong host >>> address is being used is that the ConnectionError above contains >>> 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only >>> present as >>> the listen address on the core web service and does not appear in >>> the >>> config for postorius. >> The ConnectionError above comes from requests.request (docs at >> <https://requests.readthedocs.io/en/master/>). Client only provides a >> URL in the call to request and the URL is the baseurl + the path and the >> baseurl is MAILMAN_REST_API_URL which you have as >> http://greyarea-post:8870. Entries above have >> http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? >> >> I suspect a DNS lookup issue. How does greyarea-web1 resolve >> greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS >> rather than relying on /etc/resolv.conf and/or /etc/hosts. > > No, ignore that... I edited the FQDN down to the hostname in the email > for simplicity, but even if it was in the log the hostname does map > properly (i.e. host greyarea-post and host greyarea.cam.ivimey.org > return the same thing). Is the above a typo. You are saying greyarea.cam.ivimey.org. Did you mean that or greyarea-post.cam.ivimey.org as in the http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 log messages? > In referring to the ConnectionError from: > > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > > if you reconstruct the url passed in it was presumably: > > "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk" I don't think so. I think it was http://greyarea-post:8870/3.1/domains/ch-bc.org.uk and requests.request couldn't resolve that to the correct IP. If you look at Mailman client <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/re…> you'll see it makes the URL from the baseurl passed to the instantiation of the Connection class which occurs at <https://gitlab.com/mailman/mailmanclient/-/blob/master/src/mailmanclient/cl…> which in turn is called from Postorius at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…> which makes the baseurl argument from '%s/3.1' % settings.MAILMAN_REST_API_URL. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Mark Sapiro

On 1/26/24 07:06, Stephen J. Turnbull wrote: > > I'm pretty sure it will install dependencies. I think (everything I > say below is based on reading the README.md from pipx's pypa.io repo, > so caveat installer) that the complexity that will arise is that (for > example) a naive approach like > > $ pipx install mailman > $ pipx install mailmanweb > $ pipx install postorius > $ pipx install hyperkitty > > will create 4 separate venvs with 3 copies of mailmanclient, 3 copies > of django-mailman3, and two copies of Django. But postorius and hyperkitty are dependencies of mailmanweb so only $ pipx install mailman $ pipx install mailmanweb should be required. This should put core in one venv and everything else in another without redundancy. > Besides the space > waste, there's also the small problem that mailmanweb won't have copies > of postorius and hyperkitty in its venv. But it will because they are dependencies of mailmanweb. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

Re: Hyperkitty performance problem

by Mark Sapiro

On 11/22/24 00:37, Odhiambo Washington via Mailman-users wrote: > On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: >> >> Are Mailman3/Postorius and Hyperkitty supposed to run in separated >> databases, or are they supposed to use the same database? ... > > The official documentation specifies two DBs - one for Mailman Core and the > other for Mailmanweb. > As far as I know, there are no conflicts in the tables so you could use the > same DB for both. And the mailmanweb DB is for HyperKitty and Postorius. I know of no doc suggesting separate databases for HyperKitty and Postorius and in fact accomplishing that would require separate Django instances for HyperKitty and Postorius. I.e., Postorius, HyperKitty and django-mailman3 are all Django applications and use the database configured in Django's settings. Mailman core is separate and uses the database configured in mailman.cfg. As Odhiambo says, there are no table conflicts between these databases so they can be either the same database or separate databases as you wish. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Mailman 3 Status Update Please?

by Barry Warsaw

On Feb 01, 2017, at 04:39 PM, Simon Hanna wrote: >Correction: Neither Postorius nor Hyperkitty currently support Python 3. >The only thing blocking Postorius is django-mailman3. >(I have a mr for the changes needed to the Postorius' code) >I'm not sure about the status of hyperkitty. Thanks Simon. I'd love to see Python 3 throughout the Mailman stack! -Barry

9 years, 9 months

Editing "automatic responses" tab i Postorius does not work

by David Krantz

Hi, I am trying to change e.g. the value of "notify admin on membership changes" through postorius. This is not possible as I have no URLs for the various templates (all templates are using defaults stored on the server). Is this something that can be circumvented or fixed? I can of course change admin_notify_mchanges in the "mailman withlist" interface, but this is less than ideal. best regards // David

9 years, 5 months

Mailman-users search results for query "Postorius"