Search results for "Postorius" - Mailman-users

Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Since I made all the mailman3 enviroment wide server open (not using > venv) I already executed the migration doing a > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > Being mailman3 the user who runs all of mailman3 related stuff > > I had problems doing the migrate part, showing an error of lacking > perms. I solved it running the migration under root (I know it could be > trouble after, but...) It would be much better to identify the problem files/directories and adjust their ownership. It is possible that running stuff as root in the past left things owned by root causing the issue. > > After that the compress part showed errors... but the postorius web > maintenance was working well except for the CSRF error verification. I > will trace the compress errors and will try to find the problem later. Do you have `COMPRESS_ENABLED = True` in your settings? If that's not the issue, it may be in the settings for COMPRESS_PRECOMPILERS -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 6:35 PM, Mark Sapiro wrote: > On 1/14/22 6:11 PM, David Newman wrote: >> On 1/14/22 4:54 PM, Mark Sapiro wrote: >>> >>> It should work. I suspect you need to go to the list's Settings -> >>> Automatic Responses and set `Admin immed notify` to Yes. >> >> >> It's enabled. I think this triggers notifications only for new >> subscription requests, not pending ones. > > > Yes. That will send a single notification at the time of the request > using the `list:admin:action:subscribe.txt` template. Notices of pending > requests are sent by the `mailman notify` command using the > `list:admin:notice:pending.txt` template. > > ... >>> You can test `mailman notify` at any time by running it by hand. >> >> >> Thanks. This still isn't working as intended. I took these steps: >> >> 1. Created the file >> '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' > > > The template name is `list:admin:notice:pending.txt`, not > `list:admin:action:pending.txt`. Thats why it didn't work. Bingo. Thanks -- the template works as intended now. > > ... >> 2. Restarted the mailman3 and mailmanweb services > > > You only needed to restart Mailman core. OK > > > ... >> What I'm trying to do here is replicate a feature from MM2.1, where >> pending notifications had URLs embedded in the message. That's not >> available out of the box in MM3, and if there's a place for feature >> requests I'd be glad to ask that this be made the default. > > > The place for feature requests for Mailman core (which this is) is > https://gitlab.com/mailman/mailman/-/issues, however, this is not > straightforward as Mailman core doesn't know if you even have Postorius > or some other web management UI installed or what the URL to access it > might be. Thus it's not just a simple matter of editing templates. It > would also require a configuration setting for the base URL for the web > admin UI and changes in logic to provide an appropriate replacement > depending on whether or not the base URL was configured. Understood, thanks. Although this distinction is very important for server admins, it's likely not meaningful for many list owners and moderators. For them, MM2.1 sent an email saying "go here" and MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. There is some pending template in use by default, just not one with a URL included. Is this something better handled in the venv and/or Web installation docs? Or should I file a feature request for core, or Postorious or someplace else? Thanks very much! dn > >

2 years, 10 months

Re: Fwd: Re: Removing a mail addresses and users

by Mark Sapiro

On 6/10/20 3:33 PM, Allan Hansen wrote: > > Some dedicated and skilled developers are currently investing heavily in a replacement for Postorius, but I really believe that any work is better spent transforming Mailman Core etc. into a true account-based system. Then, and only then, will it make sense to build new and better interfaces on top, as, without a healthy core, such interface will currently may have to inherit the confusion and disconnect that currently is so aggravating. I think you misunderstand what Mailman Core currently is. I think Mailman Core's concept of User is exactly what you are talking about when you ask for a "true account-based system". The problem is that Mailman Core was intentionally designed without any web UI and a RESTful API for separate web based UIs or whatever to use to communicate with it. Then the people who developed the web based management UI (Postorius) and archive UI (HyperKitty) chose to develop those within a Django framework and Django has its own concept of User separate from Mailman Core and that is where the disconnect occurs. It's not that Mailman Core lacks what you want. It's that Django doesn't use it. -- 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: [Mailman-Developers] Mailman 3.1 beta coming soon

by Florian Fuchs

On Fri, Dec 02, 2016 at 11:07:24AM -0500, Barry Warsaw wrote: >Hello Mailman 3 users and developers! > >It's been a long slog but I think we are finally ready to begin the release >process for Mailman 3.1. I am pretty happy about the state of the Core, and >Florian is going to do some more integration testing with HyperKitty and >Postorius. We still have a few issues and a merge proposal or two to address, I did some manual integration testing today (core+mailmanclient+postorius) which looked fine so far. I didn't get to test HyperKitty and the bundler though, so any help testing those would be very much appreciated. I will have some more time tomorrow. I did all of my testing locally, which has some limitations. So I started setting up a more realistic environment on one of my dev machines. But I'm not done yet. Will report back when I'm done... ;-) >but I am planning to spin a beta of Core this weekend to facilitate testing. I think it's OK to put out a separate beta of the core, because the version pulled from pypi will still be 3.0 if I'm not terribly mistaken. For the real 3.1 we should probably do a coordinated release of all components, once everything's tested a little more thoroughly. Cheers Florian

7 years, 11 months

Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Mark Sapiro wrote: > On 6/25/22 07:54, denis.bitouze(a)univ-littoral.fr wrote: > > > Mark Sapiro wrote: > > The difference between Reject and Discard is Reject notifies the > > sender of the rejection whereas Discard just discards the message > > without notification. > > IMHO, even in English, “Reject” and “Discard” are not > > self-explanatory. > > They seem so to me, but in any case, if you look at Postorius -> > Settings -> Message Acceptance -> Default action to take when a > (non-)member posts to the list, they are described there in much more > detail. OK: not easy to figure out. A tooltip on the corresponding buttons would be helpful. > > BTW, no clue about an automatic banishment of emails from discarded > > messages? > > In the pop-up dialog from clicking the subject of a held post you can > set the sender's moderation status when discarding the post. Sorry but I can only see: - “--- Set member moderation ---” (non selectable, I guess) - “Hold for moderation” - “Reject (with notification)” - “Discard (no notification)” - “Accept immediately (bypass other rules)” - “Default processing” and cannot see how I can at the same time “Discard (no notification)” and “Banish the email of the post's sender”.

2 years, 5 months

[MM3-users]Incorrect URLs

by Mark Sapiro

There are various URLs exposed in various emails from the list, many of which are wrong. The underlying issue is there are generic replacements such as $listinfo_uri and $user_options_uri in various templates such as the welcome.txt list welcome message and the footer-generic.txt message and digest footer. Now that the Mailman 3 core engine has been separated from the web UI, the core doesn't know what these replacements should be and there is not yet an interface to get them from Postorius or whatever the web UI is. In the mean time, I have made list specific versions of welcome.txt (done before announcing the list) and footer-generic.txt (just now) with the correct URLs hard coded. The purpose of this post is two-fold. To explain the issue, and to test the footer. There are probably more of these incorrect replacements and I will fix them as I notice them or they are pointed out to me. Note that I am aware that the https URLs in the List-Subscribe: and List-Unsubscribe: headers added to posts are wrong, but I haven't got a handle on this yet. The mailto: links in those headers are correct as are the Archived-At: and List-Archive: URLs as there is an interface to get those from the archiver. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

Re: Adding user - Error 409 Subscription request already pending

by Kevin Hurtley

Thanks Mark, This is sounding like a case of users will be users. As you suggested, I think my moderator is dealing with a user that can't find their confirmation (or understand they need to reply to it). So the moderator tried to override things by trying to add them in by using the "mass subscribe" operation. It sounded on Github that some opinion was that it wasn't necessary to see these pending requests, but as "users will be users" I think would be useful to see what is in queue for subscription requests, it would be better yet to be able to either clear them out or accept them there. But at very least seeing them there would go a long way helping out my moderators troubleshoot. On another request, user found the confirmation email, replied, and was accepted. However that email was several weeks old. So I'm guessing our default for expiration of requests is not the default of 3 days. But I haven't been able to find that setting. Is that in Postorius somewhere or will I need to change with the shell? I wonder if temporarily changing the Subscription Policy to "open" would allow those in pending to be accepted and clear that queue out? Thanks again for the input, much appreciated! Kevin Hurtley CoastAlaska, Juneau, Alaska

5 years, 7 months

[MM3-users]Re: Installation issues

by Andrew Hodgson

Mark Sapiro wrote: >On 04/19/2016 11:40 AM, Andrew Hodgson wrote: > >> I have often wondered if there was a howto on how this specific mailman3.org server was built, so it gives us a production-like template to follow? >Sort of, but it's not (yet) public. The process I followed is very >convoluted and not what I would recommend anyone follow. Part of the >issue is I started with mailman-bundler not using a venv, but bundler >still installs a lot of stuff in Python 2 and Python 3 venvs. I then >proceeded to install the git master branches of mailman, >mailmanclient, mailman-hyperkitty, hyperkitty and postorius and their >dependencies system wide and ripped out most of the venv stuff. I started off without using venvs and ran into several issues, though one of them I think was due to the bundler pulling down an outdated dependency. My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. My main thing when looking at this is how package managers are likely to package Mailman3, especially from a Debian point of view. I know I can't second guess what is going to be done, but would like to try to build using similar goals if possible. Thanks. Andrew.

8 years, 7 months

Re: Hyperkitty import from mailman2

by Marvin Gülker

Am 24. December 2017 um 22:30 Uhr +0200 schrieb Sten Aus <sten.aus(a)eenet.ee>: > Oh my god. :) That's it! There are no latest messages and front page shows > only last month "activity". Thank you! I did not thought that I should check > some older posts. :D I know that feeling. It took me a while to figure this out as well. Error on OSI Layer 8. > But how did you manage to import all the lists and members from Mailman2 to > Mailman3? As I understand Mailman3 does not "support" (by manual) import > right now? You'll be surprised, but those mailinglists were not managed by Mailman2 before. They were managed by mlmmj[1]. I wrote a script that converted mlmmj's archive into mbox format, and then used the "hyperkitty_import" command as explained by the Hyperkitty manual[2]. This worked surprisingly well. As for the subscribers, Mailman 3's Postorius has a mass-subscription facility in the admin interface. I extracted the list of all subscriber emails from the mlmmj mailinglist and used that mass-subscription facility to subscribe people again. There's an option to disable delivery of the welcome email that should be ticked before this I guess, though. It can be reset afterwards again. Greetings Marvin [1] http://mlmmj.org/ [2] http://hyperkitty.readthedocs.io/en/latest/install.html#importing-the-curre… -- Blog: https://www.guelkerdev.de PGP/GPG ID: F1D8799FBCC8BC4F

6 years, 11 months

Re: A new issue with installation

by Andrew Hodgson

Abhilash Raj wrote: >On Sat, Feb 20, 2021, at 9:28 AM, Abhilash Raj wrote: >> >> >> On Sat, Feb 20, 2021, at 8:51 AM, Brian Carpenter wrote: >> > As usual, a new issue has arisen with installing Mailman 3. It seems >> > Postorius and Hyperkitty want to install a module called cryptography. >> > Which I am unable to install because of this: >> > >> > error: Can not find Rust compiler >> >> You need to install a Rust compiler. Depending on which distro you are >> using, you can run `sudo apt install rustc` or same command with `yum`. [...] >FAQ: https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-wi… > >You can skip the Rust components by setting `CRYPTOGRAPHY_DONT_BUILD_RUST` but that would work just for this release and you won't be able to skip from the next release of cryptography. Its also possible to install an older version of Cryptography before installing Mailman dependencies which doesn't require this. Version 3.3.2 is the version I have been using recently at work. On a side note I have been experimenting with using underlying Debian packages for some of the Python dependencies and using the --system-site-packages option when creating the venv to simplify installation and reduce the number of compilation tools required on the system. Thanks. Andrew.

3 years, 9 months

Mailman-users search results for query "Postorius"