Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Mike Wertheim

Thanks for the response. A while back I experimented with enabling verp-probes. The users on the list were confused by the probe emails and sent me a lot of messages asking about them, so I disabled it. There is zero spam on the list. Ill try reducing "bounce info stale after" to "2d". (Actually, would "1d" be even better?) On Fri, Jun 16, 2023 at 7:46 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/16/23 19:20, Mike Wertheim wrote: > > I'm running an email list on mailman3. > > > > My users are getting inundated by messages saying that their > subscriptions > > have been disabled due to their bounce score exceeding the mailing list's > > bounce_score_threshold. > > > > But there is nothing wrong with these users' email accounts. They are all > > perfectly fine. Apparently the issue is somehow related to spam. > > > Is spam being posted to your list? If so, you should ensure that Default > action to take when a member posts to the list is set to Hold for > moderation so that spammers can't subscribe to your list and post > without the post being reviewed by a moderator. Then if the post is on > topic, the moderator can set the user's moderation action to Default > processing when accepting the post so subsequent posts won't be held. > > Also set `verp_probes: yes` in the [mta] section of mailman.cfg. Then > when a user's score reaches threshhold, a probe message is sent and > delivery is only disabled if the probe bounces which it probably won't > if the issue is spam bounces. > > > > Whenever I (as admin) get these emails, I just unsubscribe the user and > > then re-subscribe them. But also, the user gets confused and emails me > > about it, which unnecessarily takes up their time and mine. > > > That should be unnecessary. Just click on the member in the members list > and set the member's Delivery status to Enabled. However, this may not > work because of https://gitlab.com/mailman/mailman/-/issues/1061 which > is not fixed until the next release, but enabling verp_probes will avoid > that issue. > > > > The relevant list settings are currently... > > bounce score threshold: 5 > > bounce info stale after: 7d > > bounce disabled warning interval: 7d > > bounce disable warnings: 5 > > > > What's the best way to fix this? I'm considering reducing "bounce > > info stale after" to "2d" and/or increasing "bounce disabled warning > > interval" to "90d". > > > Increasing "bounce disabled warning interval" or "bounce disable > warnings" won't help because the user's delivery will still be disabled. > It will just take longer for them to eventually be removed. Reducing > "bounce info stale after" to "2d" might help as long as the list gets > good posts more frequently than that, but the best way to deal with this > is to enable verp_probes and then only consider other things if that > doesn't help. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to mike.wertheim(a)gmail.com >

2 years, 4 months

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Stephen J. Turnbull

Mark Sapiro writes: > Filtering by extension only works on message parts that have an > associated file name. Thus, while you can add things like 'exe', 'bat', > 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it > won't be completely effective. > > A better approach is to use MIME types[1] and only allow those you want. > For a discussion list, a reasonable set is what this list uses: I wouldn't say "better" if you're concerned about the executables being malware. There's long history of concealing malware by giving it a MIME type different from what the extension implies, and there was at least one Windows exploit that used this technique to achieve automatic execution of malware simply by displaying the message.

5 years

[MM3-users] Re: Sibling lists in Mailman3

by Markus Grandpre

Is there an equivalent approach to implement sibling lists in Mailman3? Best regards, Markus Grandpré Am 3/28/24 um 16:06 schrieb Markus Grandpré: > Thank you. > > Am 27.03.24 um 17:26 schrieb Mark Sapiro: >> On 3/27/24 08:05, Markus Grandpre wrote: >>> >>> after I migrated a list from Mailman21 to Mailman3 I missed the Mailman21 setting "regular_include_lists" (or >>> something similar) in Mailman3. How are sibling lists treated in Mailman3? >> >> The sibling list features do not exist in Mailman 3. >> > > > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to markus.grandpre(a)uni-konstanz.de -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 6 months

[MM3-users] Re: What's the difference between (purpose of) reject and ignore

by Andy Smith

Hello, On Sat, Jun 25, 2022 at 08:22:31PM -0000, denis.bitouze(a)univ-littoral.fr wrote: > Mark Sapiro wrote: > > 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”. These are actions for all future messages from that member, so "Discard (no notification)" would set it to (silently) discard all future mails from them. Is that not what you mean by "banish"? Cheers, Andy

3 years, 4 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Correct I used list.louisvillecommunitygrocery.com On Wed, Jan 29, 2025, 2:58 PM Arte Chambers <paul.m.robey(a)gmail.com> wrote: > Thanks! Looks resolved however I'm not 100% sure which steps fixed it: > > My Steps: > ``` > cat /etc/hosts > 127.0.1.1 list.louisvillecommunitygrocery.com list > 127.0.0.1 localhost > ``` > > Updated > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' > ``` > Restarted mailman3 AND mailmanweb service > > Updated /etc/mailman3/gunicorn.conf adding workers=9 > > Restarted mailman3 AND mailmanweb service > > Deleted custom template from Postorious > > Created new custom template from Postorious > > Added test user to list > > User was added with no errors and also received the custom Template. > > Thanks Mark, Gerald > > Bonus question: how should I calculate how many workers I should have on > my system? > > > Thank you, > Paul 'Arte Chambers' Robey > 502-408-6922 > > > On Wed, Jan 29, 2025 at 2:36 PM <vogt(a)spamcop.net> wrote: > > > > Sounds somewhat like the problem I have had: > > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > > The problem for me was that I am using gunicorn but did not increase the > number of workers… > > _______________________________________________ > > 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/ > > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > This message sent to paul.m.robey(a)gmail.com > Thank you, > Paul 'Arte Chambers' Robey > 502-408-6922 > > > On Wed, Jan 29, 2025 at 2:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 1/29/25 11:20, Arte Chambers via Mailman-users wrote: > > > Ok I did install using the > > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > > > I added > > > ``` > > > POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' > > > ``` > > > > I hope you didn't add the above literally without replacing > > www.example.com with your actual host name. > > > > It should be > > ``` > > POSTORIUS_TEMPLATE_BASE_URL = 'list.louisvillecommunitygrocery.com' > > ``` > > > > > to /etc/mailman3/settings.py and restarted mailman services > > > > > > However I'm still getting the same error from mailman.log > > > > > > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', > > > port=8000): Read timed out. (read timeout=5) > > > > I don't understand why it should still be trying to connect to > > localhost:8000. Also, I don't understand why localhost:8000 times out. > > What is your setting for localhost in /etc/hosts? it should be > > `127.0.0.1`. If it is `::1` that could be the issue. > > > > > Not sure if I'm editing the correct config file. > > > > /etc/mailman3/settings.py should be correct. > > > > -- > > 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/ > > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > This message sent to paul.m.robey(a)gmail.com >

8 months, 3 weeks

[MM3-users] Re: Moderate first postings of new members

by peter＠chubb.wattle.id.au

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 11/3/22 04:55, c.buhtz(a)posteo.jp wrote: >> >> What I want is that I would like to moderate the messages of new >> subscribed members until I set them to auto-accept all messages. I >> want to see what a new member is posting before it is send/accepted >> to the list. Mark> Set "Default action to take when a member posts to the list" to Mark> "Hold for moderation" Then, in the held messages view, click the Mark> subject and in the resultant dialog, select "Default processing" Mark> from the "set member moderation" dropdown and Accept the Mark> message. If you've set the default processing to 'hold for moderation' won't this just continue to moderate the member? Ive been selecting 'Accept immediately' in the dialog. Peter C

2 years, 11 months

[MM3-users] Re: Migrating to mailman-web and Ubuntu 22.04

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 11/15/22 06:30, Andrew Hodgson via Mailman-users wrote: >> >> I've potentially resolved to use Uwsgi for this and install another package which makes the installation more in line with this: >> https://docs.mailman3.org/en/latest/install/virtualenv.html > >That doc needs to be updated to at least include gunicorn as an alternative to uwsgi. As time permits, I'll work on that. I've managed to complete the install now using that doc using Uwsgi in the venv. I think I used Gunicorn before because Mailman installs it as a dependency so it was something I just used. I also didn't need to install python3-dev on the host with Gunicorn, Uwsgi needed that install to complete the compilation task. I did also try using the packaged version of Uwsgi with Ubuntu but that was a bit of a non-starter. Thanks. Andrew.

2 years, 11 months

[MM3-users] Re: Moving existing lists to a new domain

by Jeremy Stanley

On 2024-09-18 16:36:50 -0700 (-0700), Mark Sapiro wrote: > On 9/18/24 10:13, Jeremy Stanley wrote: [...] > > Since all the lists for the given domain will be moving to the > > same unused new domain on the existing server, and can move at > > the same time, I suppose this could be done through (offline if > > necessary) backend database update queries. [...] > For the mailing list, the only changes needed are to the > mailinglist table; but this leaves the question of list_id. > According to RFC 2919, section 4, the list_id should not change, > but this is problematic in that if it isn't changed, [...] > so to reduce confusion, it may be better to update the list_id > values [...] > For HyperKitty, similar changes need to be made to the > hyperkitty_mailinglist table. [...] Thanks! This looks even more straightforward than I'd hoped. -- Jeremy Stanley

1 year, 1 month

[MM3-users] Re: MM2 to MM3 Archives Loading

by Odhiambo Washington

On Fri, Nov 22, 2024 at 11:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/22/24 11:02, Joshua Bushe wrote: > > Unsure where these hide inactive or hide private boxes are located. > Looked through all settings. > > > They are at the top of the main Hyperkitty overview page. E.g. like > https://lists.mailman3.org/archives/ My lists are public, and I have nothing to hide, so let me expose my issue—which I believe is similar to that of the OP. https://mm3-lists.kictanet.or.ke/archives/ - is empty, but there is this active list, which has archives: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… I have been wondering why. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

11 months

[MM3-users] Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Andreas Vetter

On Montag, 10. Februar 2025 20:26:26 CET Mark Sapiro wrote: > On 2/10/25 01:07, Andreas Vetter wrote: > > That is unfortunately not enough to get rid of the Warning, because > > venv/lib/ python3.11/site-packages/mailman_web/settings/mailman.py > > contains the old ACCOUNT_AUTHENTICATION_METHOD and allauth is complains > > about it. > > In the recommended virtualenv installation, the settings that Django > sees are /etc/mailman3/settings.py. That in turn contains > ``` > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > ``` > but if following those imports you have > ``` > del ACCOUNT_AUTHENTICATION_METHOD > ``` > Django won't see it and won't complain. Did you actually try this? If > so, did you put the `del ACCOUNT_AUTHENTICATION_METHOD` after `from > mailman_web.settings.mailman import *` in /etc/mailman3/settings.py? You are right, it is enough, when one does not have a typo in it. My fault. Thanks a lot, Andreas

8 months, 2 weeks

Search results for query "sapiro"