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

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Thank you for your prompt response Mark, Στις 2019-09-18 19:12, Mark Sapiro έγραψε: > Is only one list affected, and is it all messages from this list or > only > some? Just two messages from this certain list. Subsequent messages and other activity seems to work properly > Do some deliveries of the problem message succeed? > I think not, the IndividualDelivery lines list all all recipients (list is small so I was able to check) > Postfix can return a 421 status > and drop the connection if there are too many invalid local recipients, > although I don't know if this would apply in the VERP case. Well there is no connection to postfix at all when the runner starts and the "Cannot connect to SMTP server" log shows up. Otherwise I'd have seen something in the postfix logs or tcpdumps in localhost.

6 years, 5 months

[MM3-users] Re: export/import list?

by Dave McGuire

On 8/22/23 17:59, Mark Sapiro wrote: >> I'm moving from sqlite3 to postgres; I can handle that migration. >> But I'm also moving from Mailman 3.1.1 to 3.3.8; do you (or anyone >> else) know of any schema changes? I spot-checked the first few and >> they looked the same, but before going through all of them I figured >> I'd just ask here. > > Schema changes are handled automatically by alembic. The migrations are > defined in /mailman/database/alembic/versions/. Your current version is > is stored in the database in the alembic_version table. When Mailman > core is started, all migrations from your current version to the latest > version will be applied to bring your database up to date. I.e., you > don't need to be concerned about schema changes upon upgrade. They are > handled automatically. Brilliant! Thank you Mark. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 years, 5 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Odhiambo Washington

On Fri, Apr 26, 2024 at 8:30 AM Thomas Stein <himbeere(a)meine-oma.de> wrote: > Am 2024-04-26 00:52, schrieb Mark Sapiro: > > On 4/25/24 14:01, Thomas Stein wrote: > >> Am 2024-04-25 22:03, schrieb Mark Sapiro: > >>> > >>> I don't know how things are arranged in the Debian/Ubuntu package, > >>> but you may have a settings.py which at the end does something like > >>> ``` > >>> try: > >>> from settings_local import * > >>> except ImportError: > >>> pass > >>> ``` > >>> If that is the case, adding the above snippet to the end of > >>> settings_local.py should work. > >> > >> Yes, that's the case. I added the snippet in question to > >> settings_local.py but this leads to another error: > >> > >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> > >> from settings_local import * > >> File "/usr/share/mailman3-web/settings_local.py", line 194, in > >> <module> > >> x = list(MIDDLEWARE) > >> ^^^^^^^^^^ > >> NameError: name 'MIDDLEWARE' is not defined > >> dpkg: error processing package mailman3-web (--configure): > > > > Yes. I understand. In your case, MIDDLEWARE is only defined in > > settings.py and not in settings_local.py. As I understand it originally > > you added > > ``` > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to settings.py and you say it didn't help. I don't know why that > > wouldn't work as long as there is no setting for MIDDLEWARE in > > settings_local.py and you added that after the MIDDLEWARE setting in > > settings.py. > > When you say it didn't help, do you mean you still get the > > > > django.core.exceptions.ImproperlyConfigured: > > allauth.account.middleware.AccountMiddleware must be added to > > settings.MIDDLEWARE > > > > message or something else? I note that the original post in this thread > > refers to /etc/mailman3/mailman-web.py which is presumably where the > > package ultimately puts the Django settings, and I don't know what > > `dpkg --configure` is doing. > > > > One thing you could try is in settings_local.py, put > > ``` > > from settings import MIDDLEWARE > > x = list(MIDDLEWARE) > > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > > MIDDLEWARE = x > > ``` > > to work around the NameError. > > After that I get: > > File "/usr/share/mailman3-web/urls.py", line 20, in <module> > from django.conf.urls import include, url > ImportError: cannot import name 'url' from 'django.conf.urls' > (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) > dpkg: error processing package mailman3-web (--configure): > installed mailman3-web package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > > I guess I'll wait for the new package for now. > How about adding: MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) in settings_local.py And how about you use the virtualenv method <https://docs.mailman3.org/en/latest/install/virtualenv.html> for more peace of mind in the future? -- 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]

1 year, 9 months

[MM3-users] Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

8 years, 4 months

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 4:29 PM, Mark Sapiro wrote: > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. This is a bug with Affinity which I have scheduled to be fixed. However I am confused. Data is completely removed from Mailman 3 core when you delete the account via Postorius but not when you unsubscribe from a list? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 3 months

[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, 8 months

[MM3-users] Re: Converting discussion list to read-only list (settings)

by Paul Arenson

Mark Sapiro wrote: > Issue is HyperKittyb-when replying to a message in an existing thread instead of >using the 'reply' action on that message, they use the Start a new thread button. So then >If by "read only" you mean the "Announce only mailing list style" as >opposed to the "Ordinary discussion mailing list style" the only >difference is that for the Announce only style the list attribute >allow_list_posts is False and for the Discussion style, it's True. > >This is the setting in Postorius -> Settings -> Alter Messages -> >Include the list post header an all it does is include or not include >the List-Post: header in mail from the list. Ok...there is no specific setting I see "allow_list_posts" but you wrote "Include the list post header " later on. So i set THAT one to NO? Thank you.

6 years, 4 months

[MM3-users] Re: more about spanish translations

by Guillermo Hernandez (Oldno7)

On 19/2/21 18:26, Mark Sapiro wrote: > On 2/19/21 5:09 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I would like to translate it all, but as said, I cannot find where to do >> it. I wonder if it's comes from another package as allauth or something >> like this. > > Yes, it does come from allauth, specifically > allauth/templates/account/email/email_confirmation_message.txt. > > The Spanish allauth message catalog is at > <https://github.com/pennersr/django-allauth/tree/master/allauth/locale/es/LC…>. > I suppose you could submit a pull request to update it. > > Or you could just update your local file in your installation. > I will do both: first translate locally. Test it, and then see if I can share it with the rest of the people (and then I will not have to worry to maintain it when next upgrades come) Thanks a lot, as always, Mark.

5 years

[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, 4 months

[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, 10 months

Search results for query "sapiro"