Search results for "Postorius" - Mailman-users

Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark London

Andrew - The script had: DELETE_MAILMAN_USER = False When I set it to True, it got rid of the orphaned email addresses. Thanks! - Mark On 4/25/2023 6:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py > > I have it running in a cronjob. Thread discussing the script can be found here: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > TLDR you end up with orphaned Django users both from when users subscribe/unsubscribe and due to spam signups using the Postorius form which never get confirmed. > > Thanks. > Andrew.

2 years, 6 months

Re: Mailman shell tutorial

by Mark Sapiro

On 6/11/19 6:00 PM, Andrew Bernard wrote: > > I have this going, and it is great. But I recall seeing something called > mmclient or similar which has simple commands like show user, show lists, > and so on. Is that still available? Are you thinking of the mailman command itself? Things like `mailman lists` and `mailman users`. Try running the `mailman` command itself with no arguments to see a list of sub-commands and then `mailman sub-command --help` to get the details of a particular subcommand. > Now knowing how mailman shell works, anybody could write their own commands, > but I don't want to reinvent wheels. I don't know what it is you are trying to accomplish, but yes, you can create scripts which you run via `mailman shell -run ...`, but is there something specific you are trying to do that is not currently available via the `mailman` command or the Postorius wb UI? -- 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: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Fri, Feb 3, 2023 at 6:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 21:25, Odhiambo Washington wrote: > > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > >> See > >> > >> > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > >> for mitigation. > > > > > > What is the danger of replacing my settings.py with this one, seeing as > it > > differs in a number of ways with mine? > > > If your's works, don't do it. The danger is the differences might be > significant and break things. Also, that one is for HyperKitty only and > doesn't include Postorius settings. > So in my case, I should at least increase the value of HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 8 months

Re: Member occur in Subscription Requests when Subscription Policy = Confirm

by Abhilash Raj

On Wed, Feb 27, 2019, at 6:49 AM, Henrik Rasmussen wrote: > When Subscription Policy is set to Confirm (only), new potential > subscriber appears in Subscription Requests until they have confirmed > that they actually want to subscribe. > > As expected, the new potential subscriber receives a mail with a link > to confirm. And also as expected, since moderation is NOT needed, the > admin does not receive a mail about authorisation. > > Why does the new potential subscriber appear in Subscription Requests > until confirmed by the subscriber, when the admin doesn't have to > appove anyway? Is that by design? 1.2.3 release of Postorius[1] should have fixed that and only subscriptions waiting for Moderator approval should now show up. [1]: https://postorius.readthedocs.io/en/latest/news.html#id3 > > /Henrik Rasmussen > _______________________________________________ > 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)

6 years, 7 months

Re: One-click unsubscribe?

by Mark Sapiro

On 2/4/25 20:24, Jered Floyd wrote: > > I'm having a lot of problems with GMail delivery due to lack of "one-click unsubscribe" -- however that is quantified, which is not clear. See the footer of this message which contains To unsubscribe send an email to mailman-users-leave(a)mailman3.org This is produced by To unsubscribe send an email to ${short_listname}-leave@${domain} in the template which is also in the default template. This seems sufficient for Google, as I don't see mail bounced for this reason. You might try adding a link to Postorius. You can't really link to an immediate unsubscribe as that requires the user be logged in (and the user may not even have an account) and it also required POST data, but for Mailman >= 3.3.10, you could add To unsubscribe send an email to ${short_listname}-leave@${domain} or go to $mailinglist_url This requires the domain have a base_url set. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> and this is not yet exposed in Postorius. See https://gitlab.com/mailman/postorius/-/issues/594 > In particular, there is an issue with the fact that Google ignores dots in email addresses. So I have many (MANY!) subscribers who try to use the List-Unsubscribe header target, but because they are subscribed as "idiotsubscriber(a)gmail.com" rather than "idiot.subscriber(a)gmail.com" (which they have since changed their sender to) they get a reject that they are not subscribed. These people are also far too unobservant to read the footer of every message that reads "You are subscribed as idiotsubscriber(a)gmail.com". > > Is there any way to provide personalized List-Unsubscribe header links, or have Mailman ignore dots in gmail.com addresses... or... anything? I'm finding reported spam percentages in the Google Postmaster Dashboard exceeding 0.1%, which causes massive delivery blocking to GMail-based subscribers. The List-Unsubscribe: header is added in the handler pipeline by mailman/handlers/rfc_2369.py. At his point in the process the message is still generic so the header can't be personalized. The mailman/handlers/decorate.py handler can add personalized content so could modify the List-Unsubscribe: header to add the recipient's email address except at least at present this won't work because emails to listname-leave or listname-request with a leave or unsubscribe command currently only look at the sender of the email for the address to unsubscribe. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

Re: changing adverstised status

by Johannes Winter

Am Wed, 22 Aug 2018 13:33:09 +0200 schrieb Simon Hanna <simon(a)hannaweb.eu>: > On 8/22/18 10:27 AM, Alexander Klotz wrote: > > Hi there, > > > > we are trying to set a once public list to private but have trouble > > doing so. In Postorius this doesn't seem to work - you can change > > "show list on index page" via the settings, but the value isn't > > saved. Is there a way to set advertised = False to a specific list > > via the shell? > > What do you mean it isn't saved? Are you getting an error? Is it just > being overwritten to True? > > I use the rest api, using it you can do the following: > > ./manage.py mmclient > > lists = client.lists > > l = <choose your list> > > l.settings['advertised'] = False > > l.settings.save() Using the command line mailman tool the sequence is: $ mailman withlist -l <mailinglist> >>> m.advertised=False >>> commit() >>> quit()

7 years, 2 months

Re: Make archives private by default

by Mark Sapiro

On 5/11/23 12:03 PM, mrl(a)psfc.mit.edu wrote: > Hi - I imported mailman 2 mailboxes which were private. Settings show them to be private, but they are not. It's possible to view them without being logged in. Should that be happening? No. I don't know what the issue is, but if Postorius shows the list's Archive policy as Private archives HyperKitty should not allow a non-logged in user to view that archive. > Can someone point to me the documentation on mailman.cfg features? I.e., I read on this mailing list that one can set archives for new lists to be private using: > > [styles] > default: private-default That's correct. > But where can I find that and other features? Thanks. I don't think there is a good doc on this, but https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… has a fair amount of documentation in comments. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: spanish localization

by Mark Sapiro

On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I did some exploration this morning (Spain time) in the weblate > statistics and archives and I found that the changes done from > Victoriano and me were recorded. I did a screencopy of all that if > someone has any doubt about it. I downloaded this files: > > -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po > -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po > -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po > -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po > > The thing is that they differ from the .po installed via pip upgrade. > Mostly, as said, postorius, hyperkitty and django_mailman3. The latest packages in PyPI (pip) were released on Feb 2 except for django-mailman3 which was released on Jan 15. They don't include updates after those dates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Re: Change 'from' server for outgoing messages

by Mark Sapiro

On 3/11/23 16:44, Benjamin Goldberg wrote: > > BTW the errors that I had been getting were, at first: > response exception: (450, b'The from.email must be verified. The from.email must be verified.') > but later changed to: > response exception: (450, b'Sorry, please try again. 429 Too many requests.') > > I had assumed both errors were being generated by MailerSend but now I'm not sure Yes, they are from your smtp_host which was mailersend Both those are retryable and will be retried by Mailman to a point. I suggest if you want to use mailersend that in Postorius DMARC Mitigations you set DMARC mitigation action to Replace From: with list address and DMARC Mitigate unconditionally to yes. That will ensure all posts are From: the list address and will probably avoid the 'The from.email must be verified. The from.email must be verified.' error. -- 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: nginx configuration on a multitasking server

by David Newman

On 12/10/21 4:48 PM, Mark Sapiro wrote: > On 12/10/21 3:22 PM, David Newman wrote: >> On 12/10/21 12:57 PM, Mark Sapiro wrote: >>> >>> Are you using uwsgi or some other wsgi server. >> >> uwsgi, per the venv and PDF docs. Thanks for the fix. >> >> Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives >> replace the 'proxy_set_header' ones in the venv doc? >> >> Looking at the uwsgi doc, it seems they might do different things. > > > If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working > for you, then I'm satisfied that the docs are OK now and we don't need > to say anything about uwsgi_pass. > > > >> It's not the situation I have to deal with, though. Short of changing >> a long-standing URL, what I'm looking to do is have "/" continue to >> default to roundcubemail, and have users type in longer URLs for MM3 >> and other services. > > > I think you can set the document root to the roundcubemail root and then > set locations for the Mailman destinations as, e.g. > > location /mailman3/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /archives/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /accounts/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /admin/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /user-profile/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > > I haven't tried anything like this, so I'm not sure it will work, but I > think so. Update: The above worked fine until MM3 informed a list owner of pending subscription requests, with a URL like this: https://lists.example.com/mailman/admindb/listname and that URL returned a 404 error. Adding a stanza for 'location /mailman/' to the nginx config above clears the 404 error, but Postorius returns "Page not found" with no entry in the web or MM3 logs, and a 200 OK in the Nginx logs. I think the URL is supposed to go to the list page in Postorius. How to configure this so that list owners and moderators get a valid URL for list management? Thanks! dn

3 years, 10 months

Mailman-users search results for query "Postorius"