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

[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 months, 2 weeks

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

[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

11 months, 3 weeks

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

[MM3-users] Re: Suspend a list temporarily

by Mark Sapiro

On 8/31/19 7:20 PM, Andrew Bernard wrote: > I need a bit of handholding here. What settings do I have to make to reject with a message, and how to make or modify a template with my message containing the reason for temporary list processing suspension? The template to modify is list:user:notice:rejected. This does not seem to be one that can be customized via Postorius so you would need to make a templates/lists/<list.id>/en/list:user:notice:rejected.txt file in Mailman's var/ directory or set a URL for the template as in <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Throttle outgoing emails to a certain rate?

by Mark Sapiro

On 8/21/20 3:24 AM, arvid.teichtmann(a)gmx.de wrote: > Is there a possibility to throttle the sending of outgoing emails to a certain rate, e.g. 100 emails per hour, or to split them up into corresponding chunks? > I run Mailman 2.1.33 on a hosted server and the provider only allows me to send a maximum of 100 emails per hour. This is not the list for Mailman 2.1 questions. The Mailman 2.1 list is mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. That said, for Mailman 2.1 see the FAQ article at <https://wiki.list.org/x/4030607>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 9/10/20 12:12 AM, r.woithe(a)callassoftware.com wrote: > UPDATE > mailman3 woks now under python3 but i still get the nightly email, now with an other file but with the same result: > > File "/usr/lib/python3.8/http/client.py", line 1322, in getresponse > raise ResponseNotReady(self.__state) > http.client.ResponseNotReady: Request-started > ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty) > > anybody can help ? See my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > additionally should i set COMPRESS_OFFLINE to false again? No. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Mark Sapiro

On 10/25/21 9:06 AM, Stefan Bauer wrote: > So i fixed it by myself, just think about it again. > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > Note the trailing slash at the end. > After removing it, the webinterface is up again. > But i have no idea, why this is NOW a problem and was not in the past. > Maybe something has changed in the way, apache is handling this now. The issue is with uWSGI and a recent upgrade to uWSGI is what caused it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Hacking attempts?

by Mark Sapiro

On 7/14/22 5:19 AM, Lists via Mailman-users wrote: > > Also, this error doesn’t appear in the MM or Apache logs, it just gets emailed, so I am going to have to figure out how to turn on the appropriate logging in order to get fail2ban to monitor it. Any pointers in this regard would be gratefully received. This error comes from Django. Django logging is configured in its settings, i.e. settings[_local].py or whereever you have them. I am curently traveling and on my way home and don't have time to provide more details, but if you need help, ask and I or someone will respond. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Search results for query "sapiro"