Search results for "Postorius" - Mailman-users

Re: Delete Django profiles not signed up to a list

by Brian Carpenter

On 1/1/21 7:41 PM, Andrew Hodgson wrote: > I have noticed recently I have around 2000 bogus sign-ups that have created accounts in Django. Looking through the logs these have come from the Postorius sign-up pages. I checked and email confirmation is required before the accounts are created and the email addresses that have been used do seem like they could respond to these requests. > > I don't want to add captchas to the form right now but is there any way to clean out these users from the database perhaps periodically based on whether the accounts are subscribed to any list? I can't help with this but I want to say a bogus sign up will usually have a first/last name filled with randomly generated upper/lowercase letters eg. HiedfURW FHIUEYde. That was what we saw. I also implemented a server wide block against Russia and that cut bogus signups by 75%! What we did with our Affinity system is to auto-remove all unverified user accounts after 36 hours. You can perhaps put in a feature request for something similar with Postorius/Django on their Gitlab page. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 10 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 10:37 AM, Jim Popovitch via Mailman-users wrote: > On Sat, 2021-02-13 at 08:01 -0500, Brian Carpenter wrote: >> Features are not the only thing about a modern UI, UX design plays a >> MAJOR role in the modern UI. Postorius should have at least matched MM2 >> in features in regards to something as important as Member management >> but instead it took a step back into the dark ages. > I'm gonna be a dick and remind you that less than 1 year ago you were > trying to convince me that MM3 was a gift from god and that it was time > for me to jump from MM2 to MM3 because it was sooo easy and such a time > saver.. or something like that. The point being, you yourself just > still aren't happy with MM3. Welcome to the club. I am very happy with MM3 just not with Postorius. MM3 allowed me to come up with my own admin interface. Mailman 2 would never allowed me to do that. So please leave your Mailman 2 bondage and come over to Mailman 3. We have cookies! -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

Stephen J. Turnbull wrote: > 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. The localhost address is coming in via the hosts file, which is a relatively standard practice IMO. I could change it, but then perhaps other things would not work. I would prefer to be able to specify what I need. There are also things like systemd-resolvd which will do the localhost-substitution for you even if /etc/hosts doesn't. I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and changing the cfg file hostname back to the full name of the host, and that now works!! -- in that the problem I showed earlier is gone. However I then get another issue. From the mailman.log file I now see in the last few lines. For clarity I've numbered them like this "{1}": {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" "GNU Mailman REST client v3.3.1" {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" {3} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" At this point the browser screen reports "Something went wrong" and the message "HTTP Error 404: {"title": "404 Not Found"}" Previously, the process stopped at line {1}. Now that and line {2} is executed (AFAIK) correctly, but then line {3} is isssued. I have no idea why something is looking for "domains/greyarea-web1": - Only the "ch-bc.org.uk" domain is listed in the reply to line {1}, as expected; - "greyarea-web1" doesn't appear in any lists I can show with the "mailman" cli command (and I think I tried them all); - "greyarea-web1" doesn't appear anywhere in the source or config other than as the name of the host its running on or as an ALLOWED_HOST; - I tried using "curl -X DELETE" (from the api docs) to delete a domain called that and it says no such list exists. My only possible clue is that I think, at some point in the journey of configuring mailman, I might have created a list called that on the host. However since then I have wiped the install files and reinstalled. I cannot make sense of this being the answer given the checks just listed. I went looking through the python source and can see that the get() function does indeed throw a 404 exception if the domain isn't found, but I cannot see which code is parsing the reply from the first line So I have two questions: 1) How can I fix this problem? 2) why does getting an 404 reply here cause the postorius web page to produce a "something went wrong" /404 and nothing else, when it could have simply reported that something had gone wrong with one specific domain; > I'd rather not enable the complexity of a multihomed application > unless there's an important use case. (I don't make the final > decision, but I am listened to by Those Who Do.) You wonder about multihome hosts, but should a host have more than one interface (as several of my VMs and physical hosts do), being able to specify which of the possible addresses to listen on could be very useful in the case that "all of them" is the wrong answer. There is no complexity for the developers beyond what is already supported and working. The only point I can see wrong here is the mailman3-core is using one hostname value for two distinct purposes, and IMO it shouldn't. Ideally, and this is icing on the cake, a listen address specification should allow multiple IPs to be passed in, in which case the server listens on all of them. I expect the python libraries already support this. Thanks to all for the help so far, Ruth

5 years, 4 months

Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Mark, Actually all this stuff happens inside the container after it's started and initialized without errors. I didn't amend the image anyhow. Also I have the configuration based on docker-compose.yaml provided in the repository which works just fine for mailman-web image. The very same config with postorius image (+ UWSGI_STATIC_MAP param) fails with 500 error... Now answering your questions: ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > do you have django-q in INSTALLED_APPS in your Django settings and what > is set for Q_CLUSTER? > I've checked settings.py inside the container and I haven't found any of the mentioned configurations there. Does the manage.py that's being run here point to the right settings.py? > No clue. Also I wonder why we have some Hyperkitty-related cronjobs in non-HK configured image? https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… Danil > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 8 months

Re: Splitting hosts: mta&core vs postorius

by Stephen J. Turnbull

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. It could be a Mailman bug (Mailman 3 is usually configured with all components running on the same host, and that's how it's tested), but first, does greyarea-post resolve to a routable address on the relevant network when queried from that host? > 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? It's not clear to me why you think Mailman might want to be multihomed (which is different from the host wanting to be multihomed). I don't object to the work to make it so. But my paranoia says it's best if Mailman is cordoned off into the DMZ with webservers and other hazmat. By design, Mailman core doesn't need to talk to the Internet or to the secure internal network -- Internet functions are delegated to the MTA and the webapps, and local configuration is via shell access which in principle could be console. I'd rather not enable the complexity of a multihomed application unless there's an important use case. (I don't make the final decision, but I am listened to by Those Who Do.) Footnotes: [1] gunicorn is the Python module that manages web services for the REST interface.

5 years, 4 months

Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Mark Sapiro

On 1/2/22 4:24 PM, Seth Seeger wrote: > > Ah hah! Right you are. I removed the offending fancy apostrophe. What about that traceback pointed to the template? (Is it something I could have figured out?) The key is this entry in the traceback. > File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process > text = MIMEText(expand(template, mlist, substitutions), This says we are trying to make a MIME text message part based on expanding the substitutions in a template. A look at the source at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/hold.py… says the template is list:admin:action:post. > Is it possible to filter out UTF-8 chars from the templates when they are saved in Postorius? Not really. Postorius would have to know the character set of the list's preferred_language in order to filter anything from the template that wasn't a valid character in that character set, and I don't think it has a way to get that information from Mailman core. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

New year releases!

by Abhilash Raj

Hello Everyone, Happy new year! I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.8 [1] 2. Postorius 1.3.8 [2] 3. Hyperkitty 1.3.7 [3] 4. Mailmanclient 3.3.5 [4] 5. Django-mailman3 1.3.9 [5] 6. Mailman-hyperkitty 1.2.1 [6] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of change logs are available below: [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. Thanks to all the contributors for making this release possible! If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/ Installation documentation is available at https://docs.mailman3.org/en/latest/install/install.html and if you are upgrading an existing virtualenv install you can refer https://docs.mailman3.org/en/latest/upgrade-3.2.html -- thanks, Abhilash Raj (maxking)

2 years, 10 months

New Mailman Releases

by Abhilash Raj

Hi, I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 [1] 2. Postorius 1.3.7 [2] 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of changelogs are available below: [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2 -- Something weird is going on with the page missing the bullets. [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-6 [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Finally, the minimum Python version required is 3.7 although, 3.9 is recommended if you are doing a new install for longest support. 3.10 is supported for Django apps, but Mailman Core is missing that due to one of the core dependencies not support 3.10 yet (aiosmtpd). Thanks to all the contributors for making this release possible and apologies on my end for delayed releases. If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/ -- thanks, Abhilash Raj (maxking)

3 years

Re: Help request, almost got it going, but ....

by Claus-Justus Heine

Oh well. Am 01.09.2017 um 23:44 schrieb Mark Sapiro: > On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >> >> Seemingly, at some point in the deep dungeons of the source code the >> "Acceptable aliases" Text-Box is not interpreted correctly. >> >> Specifically, at the start it contains the string >> >> [] > > > See <https://gitlab.com/mailman/postorius/issues/58>. there they talk about fancy "uni-code thinks" (email addresses?) where the task is to convert a new-line separated text-field into an array. Oops. Kind thanks anyway. > > In order to set things on this page, you need to clear the Acceptable > aliases box before submitting changes. You can't actually set Acceptable > aliases via Postorius until this is fixed. The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh. Thanks Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

8 years, 2 months

Re: Mass unverified subscriptions end up as pending user confirmation instead.

by Mark Sapiro

On 2/25/20 2:34 PM, hansen(a)rc.org wrote: > After mass subscribing with these settings: > > Pre confirm: Yes, Pre approved: Yes, Pre Verified (sic): No > > the addresses appeared in the list's 'Pending user confirmation' list. They were pre-confirmed. > The addresses did not appear in the Django Admin's non-verified addresses list. They were not verified. It is actually pending verification, not confirmation. Postorius can't tell the difference. It only knows that it's waiting for some action either by a moderator (pending approval) or the user (pending confirmation or verification, but just called 'confirmation') This verification is for Mailman core to verify it's a valid address that the user wants to use with this mailman installation. Once this address is verified, it can be subscribed to other lists without further verification. This has nothing to do with Django verified addresses which are addresses associated with Django log-in that have been verified to Django. > Also why does Postorius lists just 'Pending Approval' and 'Pending Confirmation' but not 'Pending Verification'? As I said, it doesn't know the difference between 'Pending Confirmation' and 'Pending Verification'. You should note that the user you subscribed in this way received a 'verification' request like > Email Address Registration Confirmation > > Hello, this is the GNU Mailman server at example.com. > > We have received a registration request for the email address > > user(a)example.org > > Before you can start using GNU Mailman at this site, you must first confirm > that this is your email address. You can do this by replying to this message, > keeping the Subject header intact. > > If you do not wish to register this email address, simply disregard this > message. If you think you are being maliciously subscribed to the list, or > have any other questions, you may contact > > listname-owner(a)example.com and not a subscription confirmation request. Also, if any of the addresses had been already verified, they would have been subscribed immediately without confirmation or approval. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

Mailman-users search results for query "Postorius"