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

[MM3-users] Re: invalid parameter response of the rest-api

by Mark Sapiro

On 9/21/22 16:14, gioklr71(a)gmail.com wrote: > Hi Mark. > I put a > print_dict(email_D) > and ALL records are > email; (name surname) > and no empty values are present. To be sure I've modified code... > > for mail, nom in email_D.items(): # Loop over Dictionary items (Email, Name) > if (mail) and (nom): > print(info.subscribe(mail, nom, pre_verified=True, pre_confirmed=True, send_welcome_message=False, pre_approved=True)) What are actually passing. mail may not be empty, but it is not a valid email address as checked by https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/validate… -- 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: Django: An error occurred while processing your request.

by Mark Sapiro

On 5/26/25 12:08 PM, Florian Sukup wrote: > > When I received emails from postorius, then it came from example.com > which is nonsense as I worked with the real lists. So I deleted > example.com. Set DEFAULT_FROM_EMAIL and SERVER_EMAIL appropriately in your Django settings. > When I call https://.../mailman3/admin or any of the lists, the result is: > Server error > An error occurred while processing your request. You need to set SITE_ID appropriately in your Django settings. See https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 8/16/25 7:30 PM, Wikinaut wrote: > File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/connection.py", line 160, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR 2025-08-16 19:26:03,720 6588 django.request Internal Server Error: /mailman3/lists/mylist.myserver.tld > > > Can anyone help? Other things do work, including archives, users, domains etc. Is there an associated message in mailman.log? -- 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: How to upgrade to 3.10

by Mark Sapiro

On 3/7/26 08:45, Paul Tomblin via Mailman-users wrote: > >> pip install git+https://gitlab.com/mailman/mailman-client@master > > This one is asking for a userid and password. I signed into gitlab with my github sign in, and that userid and password don’t work. I created an auth token on gitlab, and that didn’t work either. Sorry, that should be pip install git+https://gitlab.com/mailman/mailmanclient@master without the hyphen. Also, I didn't explicitly say before but I think you also need to do pip install git+https://gitlab.com/mailman/mailman-web@master to pick up changes to mailman_web/settings/mailman.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: list footer web customization procedure

by Mark Sapiro

On 12/10/21 10:03 AM, dancab(a)caltech.edu wrote: > Mark, > > Is there a mailman-web command that could be used on a specific list to expire cached entries? The cache is a Mailman core function, not a mailman-web function. If you have Mailman core >= 3.3.5, the task runner deletes expired cache entries every hour or at intervals defined by the `run_tasks_every` setting in the `[mailman]` section of mailman.cfg. For older versions you could run in an interactive `mailman shell` ``` getUtility(ICacheManager).evict_expired() ``` in a script, you'd also need ``` from mailman.interfaces.cache import ICacheManager from zope.component import getUtility ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: All messages to a new list/domain shunted from "in" queue with no logged exceptions

by Mark Sapiro

On 11/25/23 8:01 AM, Jered Floyd wrote: > > I was able to resolve this by going to the "List Settings"->"DMARC Mitigations" config page for the affected list, making no changes, and then clicking "Save Changes". > > This suggests that new lists in 3.3.9 may be getting mlist.dmarc_addresses set to None rather than an empty list (which seems to be expected). You beat me to it, but your analysis is correct. I'll need to fix that. -- 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: Installing Mailman3 under a Python Virtual environment running on RHEL9

by Mark Sapiro

On 5/22/24 11:16 AM, Andy Macheta wrote: > Hi Odhiambo, > Well; looks like I'm much further on thanks to your tips - thanks!! > > So now I can get my local web browser pointing at http://localhost:8000/mailman3/lists/ and I can see my test list. > But, the webpage does not seem right, i.e. the text has loaded but not the images and wondering if anyone has any tips on how to resolve. Did you do the 4 steps beginning at https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Spam from non list members

by Mark Sapiro

On 8/19/25 12:14 PM, Odhiambo Washington via Mailman-users wrote: > Hello Team, > > I have received spam in the last few days, posted to one of my lists. > The spam is from non-subscribers. I am wondering how this spam makes it to > the list in the first place, and how to stop them. > Below are the headers from one such spam: > ... > X-Mailman-Rule-Hits: header-match-kictanet.lists.kictanet.or.ke-18 What is the action associated with the 18th Header Filters rule for this list? This message matched that rule and I suspect the action is Accept. -- 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: 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

5 years, 1 month

[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

1 year, 10 months

Search results for query "sapiro"