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

[MM3-users] New Mailman Core Release

by Mark Sapiro

We are pleased to announce the release of Mailman core 3.3.7. It is published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ The change log is at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… - please note the `BREAKING CHANGE` documented there and due to our now using SQLAlchemy >-1.4. 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 (aiosmtpd) not supporting 3.10 yet. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Only allow users to subscribe from certain domains

by Mark Sapiro

On 8/23/23 8:33 AM, bob B via Mailman-users wrote: > Does Mailman have anyway to just allow users to subscribe themselves to a list from certain domains... ie any user from test.com or test2.com No. Mailman 2.1 has a feature which when subscription requests require moderator approval, requests from addresses matching regexps like, e.g., '^.*(a)test\.com$' can be automatically approved, but this isn't exactly what you are looking for as requests from other domains would still be held for approval, and any way, this feature has not yet been implemented in MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Hyperkitty href url to css cache files is not correct

by Mark Sapiro

On 10/5/23 08:37, Alexander Maier wrote: > > I recognized that hyperkitty creates for each new access to its website a css CACHE file which is stored at '/static/CACHE/css/'. > The url in the HTML file sets the href to /static/CACHE/css/ but the files are only accessible with '/hyperkitty/static/CACHE/css/'. What are your Django settings for BASE_DIR STATIC_ROOT STATIC_URL STATICFILES_DIRS STATICFILES_FINDERS Also in your web server, you need to alias the STATIC_URL value to the STATIC_ROOT value and finally run the Django admin command `collectstatic --clear --noinput` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark Sapiro

On 6/21/24 02:07, Mark wrote: > > That's the problem. The mmdf files don't exist in the list's directory > although there have been many posts to the list throughout the day. Assuming your mailman/app/digests.py is unmodified, there is some race condition. The code beginning at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… finds the file and size is > 0, but by the time it gets to https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… the file is gone. What other crons run at the same time? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/7/25 17:45, MegaBrutal via Mailman-users wrote: > > So it's even weirder – however, I'm really not sure if this is the address > HyperKitty is checking for, as I have 3 attached to my account! > How may I know which one it's trying to use? If you go to https://example.com/user-profile/ what Primary email and Other emails do you see? Do you see all three? And if you go to https://example.com/mailman3/users and click Manage for your address, do you see all 3 under Addresses? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

[MM3-users] Re: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 11:43, Wikinaut wrote: > CORRECTION > > Didn't I say, that I was not member of the list? I need to double-check, but treating any of n addresses of a user as automatically treating that user as "member" is not very logical behaviour. Of course it is logical. You, the person, are a member of the list so you post to the list should be treated as from a member regardless of which of your addresses it comes from. Why is that a problem? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks, 6 days

[MM3-users] Re: auto-away notices as bounces

by Mark Sapiro

On 8/29/21 10:19 PM, Andreas Barth wrote: > * Mark Sapiro (mark(a)msapiro.net) [210830 04:30]: > >> That said, bounce processing should treat even a VERPed message as >> unrecognized if it doesn't look like some kind of DSN. This may not >> be the case in MM 3. > > Thanks, that's what I also think. Looking at the returned mail, they > definitly don't look like DSNs / bounces to me. > > > Anything I should be doing re this topic? I've created https://gitlab.com/mailman/mailman/-/issues/939 for this. I think this patch will fix it. --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -51,13 +51,18 @@ class BounceRunner(Runner): addresses = StandardVERP().get_verp(mlist, msg) if len(addresses) > 0: # Scan the message to see if it contained permanent or temporary - # failures. We'll ignore temporary failures, but even if there - # are no permanent failures, we'll assume VERP bounces are - # permanent. + # failures. We'll ignore temporary failures, and if there + # are no permanent failures, we'll assume this is a vacation + # response or similar. temporary, permanent = all_failures(msg) if len(temporary) > 0: # This was a temporary failure, so just ignore it. return False + if len(permanent) == 0: + log.info('VERPed bounce message but not a recognized DSN: %s', + msg.get('message-id', 'n/a')) + maybe_forward(mlist, msg) + return False else: # See if this was a probe message. addresses = ProbeVERP().get_verp(mlist, msg) (Watch for wrapped lines) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Subscription requires confirmation when list is set as Open

by Mark Sapiro

On 12/18/24 18:22, Joachim Schrod wrote: > Mark Sapiro writes: >> >> It is not the subscription that requires confirmation. It is the user's >> email address. Even though the list's subscribe policy is open, a >> previously unknown email address has to be confirmed. > > I assume that's the verification that one can turn off in Postorious > `Mass Suscription' with the checkbox "Pre Verified". That is correct. > I maintain a mailing list for a private holiday where people don't > subscribe themselves; I subscribe them. I have vetted their email > address beforehand. (The subscribers are mostly not able to handle a > verification email, nor any email-based workflow at all.) Is there a > configuration option for a mailing list that sets "Pre Verified" to > true as a default? This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was later extended by https://gitlab.com/mailman/postorius/-/merge_requests/945 however these are not available until Postorius 1.3.14 which is not yet released. These add a setting, POSTORIUS_DEFAULTS, which can be used to set these defaults. E.g., setting POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True} will set the default for Pre Verified to True. So far, the only defaults that can be set in this manner are mass_subscription_pre_confirm, mass_subscription_pre_approve, mass_subscription_pre_verify and mass_subscription_invite and those not until Postorius 1.3.14, but more may be added. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: Maximum number of recipients error

by Mark Sapiro

On 3/18/19 10:40 AM, brian(a)emwd.com wrote: > I am unable to modify the "Maximum number of recipients" setting. It generates the following error when I click the "save changes" button: > > "An error occured: Unknown attribute: max_num_recipients" > > I am using the docker version of MM3 and its happening on "Postorius Version 1.2.3". Is this a known bug? It works for me. It was added by <https://gitlab.com/mailman/postorius/merge_requests/358>, but it requires Mailman core >= 3.2.1. What's in the docker image you're using? This may be an issue for <https://github.com/maxking/docker-mailman>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On April 16, 2019 7:09:08 PM CDT, brian(a)emwd.com wrote: >I don't know how do that with a Docker Installation of Mailman. I >believe Python 3 is part of the container. Its not installed natively >on the server. Can you do bin/mailman shell? That would be even better. >I really am starting to hate Mailman 3. Nothing is easy with this >application. I have installed it using Docker, via Ubuntu's repos, and >now I am doing an installation of it from Source (via PiP) and there >are hurdles everywhere. If you're installing via pip you must have Python 3. Your tracebacks show a Python 3 library in /usr/lib/python3.6/ -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

6 years, 5 months

Search results for query "sapiro"