Search results for "Postorius" - Mailman-users

Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/27/20 11:12 PM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > > > What version of Postorius is this? It appears to be >1.3.3. If you > > install Postorius from unreleased code on GitLab, you have to install > > all of mailman, mailmanclient and django-mailman3 as well. > > Shouldn't Postorius's setup.py be checking for this? Perhaps, but we're talking about an unreleased development version of Postorius requiring a specific unreleased commit of mailmanclient -- 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: Http/Https

by Simon HANNA

You are supposed to force https in the webserver, serving postorius and hyperkitty. Especially in postorius almost all pages contain sensitive information. On June 14, 2017 10:05:59 PM GMT+02:00, Bill <bill3(a)uniserve.com> wrote: >Hi folks, > >We're setting up Mailman 3.1 and so far installation has been good and >we're now in the testing phase. > >We've run into a snag with the account signup function on Postorius. > >When Postorius sends an email to the user to confirm their address, it >displays a link using the https protocol. This doesn't work. But, if we > >manually change the protocol to http it will work, confirm the address >and take us back to Postorius. > >Is this a known bug or have we committed a configuration error? > >All assistance appreciated. > > Bill >-- >Sent using Icedove on Debian GNU/Linux. >_______________________________________________ >Mailman-users mailing list >mailman-users(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.

8 years, 2 months

Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-02-15 18:35:35 -0800 (-0800), Mark Sapiro wrote: > On 2/15/23 07:52, Jeremy Stanley wrote: > > > > Thanks, I'm still doing my best to wrap my brain around how Django > > uses database migrations to create sites (seems like a very strange > > use of a migration, I'm only accustomed to seeing them applied for > > database schema updates). > > I don't think it does. There are a couple of migrations at > django/contrib/sites/migrations, but these are only the initial creation of > the model and an update to make the domain field unique. > > Why do you think it creates sites in this way. [...] Clearly a total misreading on my part of the Django documentation to which you referred earlier. It talks about having to feed Django multiple settings.py files with different SITE_ID values and running migrate to configure them, then links to the document on migrations which starts out explaining how to use makemigrations to create them. I took that to mean creating and configuring Django sites from the command line required supplying customized database migrations. The particularly misleading bits are where it says: "To set the correct name and domain for your project, you can use a data migration." "In order to serve different sites in production, you’d create a separate settings file with each SITE_ID" It doesn't seem to talk about using django_admin at all (or if it does, it's not mentioned by name, maybe assuming the reader knows to use it in order to perform the necessary steps). Thanks for the clear examples! If these are available somewhere in Django's documentation, I did a terrible job of searching for them. > you need to create a domain in Postorius. Look at the code behind > Postorius add new domain. Or you can create the domain in core via > REST, but you then have to modify it in Postorius to associate the > correct site. [...] Much appreciated, this was the other bit that was non-obvious to me. I guess you're saying Postorius's view of domains is independent from what's in Mailman Core, and there's no documented CLI/API for manipulating that in Postorius so I'll need to write one based on a reverse-engineering of its source code? Sounds doable now that I know where to look. Thanks again! -- Jeremy Stanley

2 years, 6 months

Re: So, why are css & js files only served with "DEBUG = yes" ?

by Simon HANNA

js and css files are static and should be served by your web server of choice. In a development environment you usually don't have a web server running, so django serves the files itself. Your webserver can serve these static files much faster than django can, so django doesn't serve them in production by default. You can find instructions on how to do so online (Google is your friend) but since that's not incouraged there is no point in including these in the repos. Simon Am 7. Mai 2017 16:06:17 MESZ schrieb Simon Liebold via Mailman-users <mailman-users(a)mailman3.org>: >Hello List, > >I did see this discussed in #180 ><https://gitlab.com/mailman/postorius/issues/180>, but I didn't quite >understand if this is an issue or not. > >Why is it that I can run the development server just fine. > > [07/May/2017 13:23:47] "GET > /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/postorius/css/style.css > HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/django-mailman3/js/main.js > HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/django-mailman3/css/main.css > HTTP/1.1" 304 0 > [07/May/2017 13:23:47] "GET /static/postorius/js/script.js HTTP/1.1" > 304 0 > [07/May/2017 13:23:47] "GET > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 304 0 > >And as soon as I comment out > > # SECURITY WARNING: don't run with debug turned on in production! > # DEBUG = True > >in mailman-suite/mailman-suite_project/settings.py and restart it 404s >on me. > > [07/May/2017 13:41:36] "GET >/static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 >127 > [07/May/2017 13:41:36] "GET /static/django-mailman3/css/main.css > HTTP/1.1" 404 109 > [07/May/2017 13:41:36] "GET /static/postorius/css/style.css > HTTP/1.1" 404 104 > [07/May/2017 13:41:36] "GET /static/django-mailman3/js/main.js > HTTP/1.1" 404 107 > [07/May/2017 13:41:36] "GET > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 404 125 > [07/May/2017 13:41:36] "GET > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 404 123 > [07/May/2017 13:41:36] "GET /static/postorius/js/script.js HTTP/1.1" > 404 103 > [07/May/2017 13:41:36] "GET > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 404 123 > > >So the choice is insecure vs. ugly? Neither of those sounds very >tempting. > >I guess, I am missing something, or no? > >Simon > >_______________________________________________ >Mailman-users mailing list >mailman-users(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.

8 years, 4 months

Re: Header and footer templates in MM3

by Mark Sapiro

On 1/19/20 1:15 AM, Gila Halpern wrote: > I read the earlier message from Peter Mueller about message decoration, and > where the templates are in the file system. However, when I edit the > header and footer templates in Postorius, those templates do not appear in > the location specified. Should I be looking somewhere else? The templates created in Postorius are created in the postorius_emailtemplate table in Mailman's database and referenced via URLs like 'https://example.com/mailman3/api/templates/list/<list-id>/<template-name>'. I.e., they are not stored in the file system. > (I intend to > write a program to rotate though several headers/footers, so I need to know > where to have it write to.) If Postorius has set a template for a list, it has set the URI for that template and list to one similar to that above and that URI ultimately references the template in the database. You have choices. You can set the templates in Postorius and your program can do database queries to rotate the template text, or you can set the template URIs via Mailman's TemplateManager to file system paths or not set them and use the default paths (deleting them in Postorius will leave them unset). See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Re: Postorius password resets

by Andrew Hodgson

Mark Sapiro wrote: >On 10/15/20 9:24 PM, Andrew Hodgson wrote: >> Mark Sapiro wrote: >> >>> On 10/14/20 11:11 AM, Andrew Hodgson wrote: >> >>>> I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: >>>> >>>> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' >> >>> This is not relevant. >> >> Does it need resetting back to http://localhost:8000? Not if it works. Most likely either one is OK, but localhost:8000 avoids a DNS lookup an proxying through the web server. Ok I have reset this value now. >>>> However emails are still coming through with the wrong URL. >> >>> I'm not sure offhand, but it's either domains in Postorius or sites in the django admin UI. >> >> I've checked both and cannot see any errors (I just have the one site lists.hodgsonfamily.org) and nothing is empty which seems as though it needs filling in. >What's in `sites` and what's in `Mail domains` in the django admin UI https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/: <Mailman domain lists.hodgsonfamily.org> https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/1/change/ Site: lists.hodgsonfamily.org Mail domain: lists.hodgsonfamily.org https://lists.hodgsonfamily.org/admin/sites/site/1/change/ Domain name and display name: lists.hodgsonfamily.org >and what's in Web Host in the Postorius domains view - in particular, if you have Postorius 1.3.3, what's the SITE_ID, and what's SITE_ID in settings(_local).py. https://lists.hodgsonfamily.org/postorius/domains/ Mail Host Description Alias Domain Web Host lists.hodgsonfamily.org lists.hodgsonfamily.org (lists.hodgsonfamily.org) SITE_ID = 1 Site ID is 1 in settings.py (not overridden in settings_local.py) > Also, when you go to the archive UI, whats the domain at the top left of the pages. Lists.hodgsonfamily.org I have overridden the following settings relating to this in settings_local.py: USE_X_FORWARDED_HOST = True ALLOWED_HOSTS = [ 'localhost', 'lists.hodgsonfamily.org' ] Settings.py is from the latest commit from the Mailman Suite Gitlab project. Thanks for helping me with this. Andrew.

4 years, 10 months

Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 1/30/23 10:32, Jeremy Stanley wrote: > > 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. Domains can be created via Postorius or via the Mailman Core REST API that postorius uses or implicitly by the `mailman create` command when creating a list in a new domain. However, none of this can create a new site. You can do this through the Django admin site at sites/site/add/. See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you can use to do this programmatically. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Re: Http/Https

by Abhilash Raj

Excerpts from Simon HANNA's message of June 14, 2017 1:06 pm: > You are supposed to force https in the webserver, serving postorius and hyperkitty. Especially in postorius almost all pages contain sensitive information. > > On June 14, 2017 10:05:59 PM GMT+02:00, Bill <bill3(a)uniserve.com> wrote: >>Hi folks, >> >>We're setting up Mailman 3.1 and so far installation has been good and >>we're now in the testing phase. >> >>We've run into a snag with the account signup function on Postorius. >> >>When Postorius sends an email to the user to confirm their address, it >>displays a link using the https protocol. This doesn't work. But, if we >> >>manually change the protocol to http it will work, confirm the address >>and take us back to Postorius. >> >>Is this a known bug or have we committed a configuration error? I agree to Simon's suggestion that you should use HTTPS for all communications for Postorius. However, if you really want to, it is possible to change the behavior using a configuration parameter in django-allauth which is what controls the user signup and email verification. ACCOUNT_DEFAULT_HTTP_PROTOCOL (=”http”) If you set the above to "http" in your django's settings.py, it should then generate urls with http. [1]: https://django-allauth.readthedocs.io/en/latest/configuration.html Message-ID: <draft-878tktptc9.fsf(a)gmail.com> Date: Thu, 15 Jun 2017 01:07:18 -0700 X-Notmuch-Emacs-Draft: True -- thanks, Abhilash Raj

8 years, 2 months

Re: Confirm and Moderate Unsubscribe Requests

by Abhilash Raj

On Wed, Oct 21, 2020, at 3:35 PM, Brian Carpenter wrote: > > On 10/21/20 5:39 PM, Mark Sapiro wrote: > > On 10/21/20 12:14 PM, Brian Carpenter wrote: > >> > >> Well I can't dictate that to my list owners and there is no confirm > >> token sent with the moderation notice. Why include this option in > >> Postorius when it can't be properly handled? > > > > Postorius is still a work in progress. The unsubscription policies are > > in core and are exposed in Postorius. Certainly the ability to moderate > > an unsubscription should be in Postorius, but it isn't yet. We are an > > all volunteer project and there aren't that many of us, and perhaps I'm > > overreacting, but the tone of some of your recent posts seems a bit > > demanding. > > I apologize. I didn't think I was coming across demanding but I am > somewhat exasperated at some of these issues. I have a list owner who is > now going to get a moderated request notice everyday that he can't do > anything about it. > > But my question still remains: why is this option in Postorius when it > can't be handled properly? Surely the option can be easily removed, right? I added the option in my drive to expose every possible Mailinglist settings via Postorius and missed the fact that we weren't actually able to moderate those requests. Yes, this option can be hidden if it doesn't work until the next stable release. I hid one of the list settings in Postorius exactly because it didn't work, but this one slipped. > > Is the ability to list (via the pending moderation notices tab) and > handle (as in the List owner can decide a moderation response) an > unsubscribe moderation request there in Mailman core so that I can > properly address it via Affinity? Unfortunately no, there is a bug report open for it though and I have some done some analysis on root cause[1]. The bug turned out to be a more than a trivial one and I haven't been able to get to it yet. [1]: https://gitlab.com/mailman/mailman/-/issues/768 > > -- > > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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, 10 months

Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Abhilash, Thank you for the quick resolution, but I'm still unable t start the container: https://github.com/maxking/docker-mailman/issues/309 DB migrations are failing. Danil вс, 17 февр. 2019 г. в 12:21, Danil Smirnov <danil(a)smirnov.la>: > Hi Abhilash, > > Thank you for the explanation, I've created a report: > https://github.com/maxking/docker-mailman/issues/307 > > Danil > > > > сб, 16 февр. 2019 г. в 18:40, Abhilash Raj <maxking(a)asynchronous.in>: > >> On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote: >> > Hi, >> > >> > I'm interesting in Mailman3 deployment with archiving feature completely >> > disabled. >> > >> > I've tried to deploy Core + Postorius using this docker-compose >> > template: >> > >> https://github.com/maxking/docker-mailman/blob/master/docker-compose-postor… >> > >> > Unfortunately Postorius version came with this template is quite >> outdated: >> > 1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker >> image I >> > see version 1.2.3. >> > >> > I've also checked image maxking/postorius:rolling but it seems >> > irrelevant/broken (container exits with error). >> > >> > Are there newer Postorius docker image I can use? >> >> No, but if you could report the failure and error that you, maybe the >> Maintainer can help >> fix that issue you have? >> >> P.S. I maintain those images. The Postorius image is kind of neglected >> since there are >> fewer people using it, but I'd be happy to fix any error that you see. >> >> Package ugprades are merely a version number bump in Dockerfile :) >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >

6 years, 6 months

Mailman-users search results for query "Postorius"