Search results for "Postorius" - Mailman-users

Re: [Mailman-Developers] Countdown to the 3.1 release

by Simon Hanna

> Please take a look at any other bugs not assigned to milestone 3.1 and let me > know if you think any are serious enough to block the 3.1 release. I'll say > in advance that I'm going to be brutal in assessing them, because 3.1 really > needs to be released soon! I guess https://gitlab.com/mailman/mailman/issues/219 should be fixed in the next release. If 3.1 find its way into repositories, we will get lot's of issue reports for this I suppose. > Note too that there may be blockers for Postorius, Hyperkitty, and > mailman.client, but I haven't looked at those subprojects yet. How close are > they to being release ready? Terri was working on this one, it's not critical but nice to have for usability https://gitlab.com/mailman/postorius/merge_requests/159 I have a mr pending for mailmanclient that should be included in the next release https://gitlab.com/mailman/mailmanclient/merge_requests/10 Postorius has a number of merge requests open. I'm not sure which of them should be merged before the next release Does your template branch in core need any immediate modifications to mailmanclient and/or postorius? cheers, Simon

9 years, 5 months

Re: setup of URLs

by Abhilash Raj

On Sun, Jan 28, 2018, at 12:24 PM, Peter Münster wrote: > Hi, > > I would like to point "https://my-domain.org/" to the list of > mailing-lists of this domain. How should I setup my Apache configuration > and/or the urlpatterns please? > > With my actual configuration, the above URL is always rewritten to > https://my-domain.org/postorius/lists/ > > These are my urlpatterns: > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), ^ This is responsible for re-writing your URL to `/postorius/lists/` as Redirect from `/`. This patch should do what you want: ``` index a5ea108..bff54f3 100644 --- a/example_project/urls.py +++ b/example_project/urls.py @@ -25,11 +25,10 @@ try: except ImportError: from django.urls import reverse_lazy from django.views.generic import RedirectView +from postorius.views.list import list_index urlpatterns = [ - url(r'^$', RedirectView.as_view( - url=reverse_lazy('list_index'), - permanent=True)), + url(r'^$', list_index), url(r'^postorius/', include('postorius.urls')), ``` Just as an FYI, my browser would always re-direct me to /posotrius/lists, even after I applied this patch, not sure if it was some sort of caching or something else. I tried it from an incognito-mode and it seemed to work. -- Abhilash Raj maxking(a)asynchronous.in

7 years, 11 months

Re: integrate subscribe form in Website -> CSRF-token

by Mark Sapiro

On 6/21/21 11:58 AM, Jens Günther wrote: > > We wanted to do the same with Mailman3 (Docker, 3.3.3, Postorius 1.3.4): > > <form method="POST" > action="https://$domain/postorius/lists/$short_lisname.$domain/anonymous_subscribe"> > > <input name="email" value="" type="text"><br> > <input name="email-button" value="Anmelden" type="submit"> > </form> > > When I now enter a mailaddress, the quoted error occurs. This is Django protecting against CSRF. You need to GET the for with the (hidden) CSRF token before you can POST it. > Checking another answer directly to me, there seems to be another hint :-) > > > I believe you are attempting to use the MM Core API via http > GET/POST, rather than via Postorius? That you have tried and get the > CSRF error reported? > > > > Typically this is because you need to add a token to the request to > indicate to the MM Core that your request isn't a forgery. Typically > this token is requested from Core and then presented with subsequent > requests. Have you tried this? > > > > Therefor it is needed to send also a token!? Or use another URL, not > postorius in order to subscribe!? How can I submit such a token? To submit the Token, you need to first GET the form which will have the token. Then you can include it in the POST data. This is not a satisfactory solution for your case. As hinted above, you need to use the REST API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Re: Are the gitlab repositories kept in sync?

by Abhilash Raj

On 9/13/21 1:56 PM, Brett Delmage wrote: > See > https://gitlab.com/search?search=mailman&group_id=&project_id=&snippets=fal… > > > I see that core is update frequently but other packages such as Mailman > web have not been. Mailman-web is less frequently updated, that's right. It is essentially a python package which packages all the web fron-tends together, so doesn't need updating frequently. > mailman-suite is two weeks old. Mailman-suite is a pre-cursor of mailman-web, so it follows the same philosophy. It will retired at some point in favor of mailman-web. > > Mailman Web has not been updated for wo weeks. > > Does that mean I can download that Postorius and it will work with the > latest mailman core updated in the past day? We run the git master branches of all the components on this server, so it should be compatible, yes. Although, if you are planning to run them in production, I'd recommend using released versions from PyPI (or git tags) instead of git master branch. > > I expect that most changes don't break interfaces. Is that correct? That is true as a general statement ;-) We support compatibility between the latest version of each components only. So, an older version of Postorius may not be fully compatible with latest Mailman Core, although, in theory, it shouldn't break. We'll bump versions in the REST API of Mailman Core if some breaking change in made and older versions of Postorius _should_ be able to talk to the old API version to function. This hasn't been tested very well in practice though since we haven't made a huge breaking change in the API so far, so YMMV. -- thanks, Abhilash Raj (maxking)

4 years, 3 months

Re: Verification Failed Error

by Stephen J. Turnbull

Abhilash Raj writes: > You probably have > > verify = sender > > somewhere in your exim.conf, which is causing this. No, that seems unlikely. This is in the default exim.conf. > You can either modify the > > DEFAULT_FROM_EMAIL > > in your settings_local.py so that it is a real address that Exim can verify, He's already modified that, since the default in settings.py is "postorius(a)localhost.local" (which is a bug: this should default to a mailbox, and the domain should be added automatically if only a mailbox is given). It seems likely that what needs to be done is to set up a mailbox for Postorius, which can be done in several ways. When does Postorius receive mail? I guess it *sends* mail for the mailbox owner confirmation dialogs on subscription or password reset, but that confirmation is normally done by a web transaction, right? If <postorius> rarely gets mail, the obvious thing to do would be to alias to site owner or postmaster. (It looks like Django doesn't know how to receive mail, so any facility for postorius to receive mail would have to be configured in the MTA.) If it's not that, then the problem likely has something to do with the containerization, and the MTA getting confused about which host is which. > or, you can remove verify = sender from your Exim configuration. Don't do this. If you set up a separate Exim router for "postorius" (to do something fancy like a autoreply bot or delivery to /dev/null ;-), you can put the no_verify option in the Requires stanza for it. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

7 years

Re: Problem with redirection when entering alias without a / at the end

by Jens Günther

Am 19.03.21 um 23:04 schrieb Mark Sapiro: > On 3/19/21 2:55 PM, Jens Günther wrote: >> >> When I want to get to Mailman Starting Page now I need to Enter the >> following URL: https://mailman.xyz.de/mailman3/ to be directly >> redirected as expected to >> https://mailman.xyz.de/mailman3/postorius/lists/ -> works. >> >> Problem: When leave out the slash at the end and I ONLY enter the >> following URL: https://mailman.xyz.de/mailman3 -> then I'm wrongly >> redirected to a page, taht does not exist: >> https://mailman.xyz.de/mailman/postorius/lists/ -> 404 > > > Huh? that is the same URL as the one above that you say works. Do you > mean https://mailman.xyz.de/mailman/postorius/lists without the slash or > what. Here is the difference: https://mailman.xyz.de/mailman3/ https://mailman.xyz.de/mailman3 -> the first one works and leeds to https://mailman.xyz.de/mailman3/postorius/lists -> the second one redirects to https://mailman.xyz.de/mailman/postorius/lists -> which does not exist, since Apache-alias is only for mailman3 >> Where can I change this misbehaviour? In Apache-conf everything seems as >> it's in the docs, for the vHost I do not have any other custom settings. > > > What is the exact content of your RedirectMatch or ReweriteRule or > whatebver you are using? > I only use the apache-conf given in the documentation: <code> Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> </code>

4 years, 9 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > But postorius and hyperkitty are dependencies of mailmanweb so only Are they? I'm pretty sure that in my current project which has a pre-existing archiver they wish to keep using I only installed postorius, not hyperkitty. ... oops, HyperKitty *is* there. OK, need to uninstall that. That's actually a bit annoying, since mailmanweb is a friendlier interface for control of either of HyperKitty and Postorius than the underlying Django utilities even if you don't want the other and its unique dependencies (such as Whoosh). (Issue #32 created) OK, so your two-venv approach should actually work. I still don't think it's much of a win since to finish setup you still have to do a lot of work as root and a lot of work outside of pipx's control. Basically it saves one "python3 -m venv", at the cost of "pipx run" to run each program in its own venv. Note, it doesn't save me any venv activationss because I put that in the mailman user's shell .rc. Wikinaut asks: > Has anyone tried that already? Why not you? Steve

1 year, 11 months

Re: Splitting hosts: mta&core vs postorius

by Andrew Hodgson

Stephen J. Turnbull wrote: >Ruth Ivimey-Cook writes: > > On 21/06/2020 04:52, Mark Sapiro wrote: > > > Change that to greyarea-post > > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 >I don't understand. I'm not in a position to test with Mailman itself right now, but the standalone gunicorn[1] does the right thing (takes an IP address and binds to the corresponding interface, or takes a domain name, resolves it to >the IP address, and binds that to the corresponding interface). It does not substitute localhost. Sorry not to reply to ruth on this before, my main experience of this issue was running in a Kubernetes cluster using Docker, using https://github.com/maxking/docker-mailman as the basis for the images. What follows is my own research on this issue and it may be completely wrong. Taking the default Mailman Core setting: [webservice] hostname: localhost This makes Mailman-Core listen on the loopback address (via name lookup) on the configured port for incoming REST requests. When it responds to these requests, it sends out in the response a self_link address which matches the [webservice] hostname Parameter. Connecting clients (such as Postorius) need to connect to Mailman-Core on the given hostname (eg http://localhost in the default case where Mailman Core and Web components are installed to the same machine. However if the [webservice] hostname: parameter is set to something like 0.0.0.0, then although you can direct Postorius (via DNS lookup or IP address) at the Mailman Core instance, it fails to work properly because the resulting response sent back from Mailman Core will include self_links pointing at 0.0.0.0 which will not be usable as a URL by the REST client. A fix for this issue is to set the [webservice] hostname parameter to a FQDN or IP address which can be resolved by the machine running the Web components, and as long as the base URL that Postorius tries to use for the Mailman Core access is the same as in the [webservice] hostname parameter, you are good to go. It appears that when specifying a FQDN in the [webservice] hostname parameter, that the system will look up the IP address for that host using the systems name resolution function. This has the side affect of potentially listening on the wrong interface (localhost) if the system hosts file is set such that the machine's FQDN points to 127.0.0.1. In my case my containers were behind CoreDNS and this wasn't an issue for me, but had I tried this for example on a Debian system I would have come against the same issue that Ruth has as it will automatically set the FQDN of the system to resolve to 127.0.0.1 by way of the Hosts file. Adding the network IP address of the system with the FQDN in the hosts file should fix this issue. > > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed >hosts to get the right connectivity, too. >I'm not clear on what you're saying. An address is a rendezvous point; if you're not listening on the address that others are using, you won't meet. What good does it do to split them up? I agree with this, we need a setting for which interface for Gunicorn to listen on, and what Mailman Core sends out in the self_link attribute when responding to REST requests. Thanks. Andrew.

5 years, 6 months

Re: Starting new thread in Postorius -> disappears

by Abhilash Raj

Hi Thor, On Tue, 2017-11-21 at 10:53 +0100, 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. When you say nothing happens, you just mean that you don't see anything in the UI or you don't see anything in the logs? Logs for mailman-web are in /opt/mailman/web/logs/mailmanweb.log (on the host). > > 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: > > mailman:10000:65536 This ideally shouldn't affect anything, I haven't tried running this way though. > > > and in /etc/docker/daemon.json: > > { > "userns-remap": "mailman" > } > > So I get the following ownership in /opt/mailman: > > > drwxrwsr-x 3 10100 10000 4096 nov. 21 09:00 core > drwx------ 19 10070 10000 4096 nov. 21 09:27 database > drwxr-sr-x 5 10100 10101 4096 nov. 21 09:24 web > > (I have created a user named mailman with uid 10100 so, in reality, it says > "mailman" there instead of 10100 but I guess that is irrelevant here) If would be interesting to see what processes are running inside each containers and who their owners are, in case this is at all relevant to the issue, which I am not so sure about. > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 1 month

Re: Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

On 5/1/22 21:50, Mark Sapiro wrote: First, thanks a lot Mark for your guidance. >> >> HINT: Configure the DEFAULT_AUTO_FIELD setting or the >> SocialAccountConfig.default_auto_field attribute to point to a >> subclass of AutoField, e.g. 'django.db.models.BigAutoField'. > > This is from Django >=3.2 can be fixed by adding > > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > > to your settings. This has been done in HyperKitty's > example_project/settings.py for the not yet released 1.3.6 version. > > These warnings are only warnings, they aren't fatal. I thought so. I've added it in the settings.py file. In the last part of your suggestions you wrote: "I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0" But this is exactly what made me fall in this mess: I realized that the versions of hiperkitty and mailman-hiperkitty in that server were outdated.. and I tried update them separately, forgetting the saying "if it works, don't touch it" (si funciona, no lo toques). In my first message I listed the versions of all the items, but to refresh it, as they are now: (from pip list) ... gunicorn 20.1.0 HyperKitty 1.3.5 ... mailman 3.3.5 mailman-hyperkitty 1.2.0 mailmanclient 3.3.3 ... mistune 2.0.1 ... mod-wsgi 4.7.1 ... postorius 1.3.6 (end of pip list) I did the upgrade of all of it. The "migration" process output the same warning as before about to doing a "makemigration" (I did not this time) Thinking that the problem in the "migrate" and "makemigration" process could be that I touched the mistune/scanner.py to add escape and escape_html imports, I deleted that two lines. Then all went bad: the postorius list page didn't show anymore. The error.log form the apache server shows django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'hyperkitty.templatetags.decorate': cannot import name 'escape_html' from 'mistune.scanner' (/usr/local/lib/python3.7/site-packages/mistune/scanner.py) So I tried to put them back (but I had problems with, I believe, the __pychache__). I had to reinstall mistune and write back this lines that I found in a previous thread from William Oliver last 12/28/21 I've finally came back to administering the lists via postorius. I created a new list to do the tests without disturbing the rest. And now I am at the exact same point: No message is archived and the log shows: ERROR 2022-01-06 12:38:45,574 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,586 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,801 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,832 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,847 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:45,867 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. ERROR 2022-01-06 12:38:46,075 39059 hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. As this server has very low traffic, the emails are distributing well, and the only thing that fails is the archiving of new messages, I will wait until a more complete upgrading process is needed for mailman, postorius or hiperkitty. Thanks, again, for your support. P.S.: One thing that make me curious is the "mistune" package... I don't see it installed in the other servers that are working flawlessly with mailman3. > > ... >> Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows >> the same warning listed before and some new errors: >> >> *-*-*-*-*-*-* >> >> Migrations for 'postorius': >> /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py >> >> - Alter field name on emailtemplate >> Traceback (most recent call last): >> File "manage.py", line 10, in <module> >> execute_from_command_line(sys.argv) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", >> line 419, in execute_from_command_line >> utility.execute() >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", >> line 413, in execute >> self.fetch_command(subcommand).run_from_argv(self.argv) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 354, in run_from_argv >> self.execute(*args, **cmd_options) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 398, in execute >> output = self.handle(*args, **options) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", >> line 89, in wrapped >> res = handle_func(*args, **kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", >> line 190, in handle >> self.write_migration_files(changes) >> File >> "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", >> line 228, in write_migration_files >> with open(writer.path, "w", encoding='utf-8') as fh: >> PermissionError: [Errno 13] Permission denied: >> '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' >> >> >> *-*-*-*-*-*-* >> >> The file >> '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' >> does not exist at all > > > makemigrations is trying to create that migration and you don't have > permission to create the file. I don't know why it's trying to do > that. Postorius 1.3.6 has migrations through > 0016_auto_20210810_2157.py and shouldn't need more. To you have > modificationd to Postorius? > > >> Despite the error, I did a 'su -m mailman3 -c "python3 manage.py >> compress"' and the subsequent "django-admin compilemessages" in >> >> /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and >> ../django_mailman3 >> >> And the log continues showing the same error when trying archive a >> new message. >> >> ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The >> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > > > These messages come from some HyperKitty version between commit > b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 > -0700 and > commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 > 2021 +0000 > > They do not come from HyperKitty 1.3.5 but from something later than > 1.3.4 which makes be think your mailman-hyperkitty version is not > 1.2.0 either. > > I suggest you do > > pip install --upgrade hyperkitty mailman-hyperkitty > > and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

4 years

Mailman-users search results for query "Postorius"