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

[MM3-users] Re: message duplication and an NNTP related error

by Mark Sapiro

On 2/27/26 07:17, Laurens Kils-Hütten wrote: > > So thanks a lot for clarifying. There's only one issue left I'm seeing > right now. Mailman does not rewrite the Newsgroups: header. Thus mua's > like Thunderbird which also talk NNTP offer to reply to the newsgroup > instead of to the list. Arguably this might be called a bug in > thunderbird, but I think it would be reasonable if mailman would change > "Newsgroups:" to "X-Newsgroups:" to avoid these kinds of pitfalls. Mailman has a couple of settings in the [nntp] section that control this. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…>. You can't use rewrite_duplicate_headers to do this because it onle rewrites the duplicates and not the original, but you can use remove_headers to remove the Newsgroups header. If you want to do this you could add ``` [nntp] remove_headers: nntp-posting-host nntp-posting-date x-trace x-complaints-to xref date-received posted posting-version relay-version received newsgroups ``` to your mailman.cfg to continue to remove the defaults and also remove the Newsgroups header. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 1 week

[MM3-users] Re: Moderation of held emails vs. spam

by Mark Sapiro

On 7/25/20 12:33 AM, David Krantz wrote: > Hi, > > I now run Mailman 3.3.1, installed from pip. Is there now any way to > prevent Mailman from forwarding the contents of the held message when > notifying moderators of held messages? There is not now any configuration setting for this. > In my case these messages often > are spam messages and if the entire contents are forwarded it triggers > spam handling in the recipient address(es) which over time risks > classifying all moderation emails as spam or even classifying the list > domain or server as a spam source. > > Even my own outgoing filter classifies it as spam, which I will fix. So if you can recognize them as spam, why are you delivering them to to list in the first place? > I guess that this would be a simple change to make as a kludge but a > proper implementation as a setting would be a lot better. I'd like it > as a global setting but that might be too coarse. You can submit an issue at <https://gitlab.com/mailman/mailman/-/issues>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Postorius web issues after upgrading mailman 3

by Mark Sapiro

On 10/12/21 8:38 AM, Tibor Molnar wrote: > Hello, > > I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 > I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. > The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated. These are all HyperKitty pages, not Postorius. Did you run all the post-upgrade tasks mentioned at <https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade> after upgrading? Also, it is possible, but not the likely cause of this, that there is an incompatibility between the latest hyperkitty and django-mailman3 in PyPI. See <https://gitlab.com/mailman/django-mailman3/-/issues/48>. You could try ``` pip install -U git+https://gitlab.com/mailman/hyperkitty.git ``` and see if that helps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: restricting public lists per virtual domain

by Mark Sapiro

On 12/16/21 12:25 PM, David Newman wrote: > Can lists set to be viewable on the index page be limited to the virtual > domain they are a part of? > Have you set FILTER_VHOST = True in your Django settings? This works for HyperKitty and works partially for Postorius. For Postorius, it doesn't work if there are multiple domains with different email hosts which have the visiting host as their web host[1] but works otherwise. See https://gitlab.com/mailman/postorius/-/merge_requests/500 and https://gitlab.com/mailman/postorius/-/issues/394 In your case, as long as the domains lists.dom1.tld and lists.dom2.tld have different mail hosts, this should work. [1] An example of what doesn't work in Postorius is the following: Visit https://lists.example.com/mailman3/lists. If there are 2 domains with web host lists.example.com, one of which has mail host example.com and the other has mail host lists.example.com, all lists will be shown regardless of domain. On the other hand, if all the domains with web host lists.example.com have the same email host, say example.com, then only lists with email host example.com will be shown. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Dealing with email bounces from web signups

by Mark Sapiro

On 3/16/22 12:07, Andrew Hodgson wrote: > > What I would ideally like is if we get a bounce from one of these confirmation mails we delete the user from the database but that is probably a future request. We don't get too many of these, around 20-30 a week. Since you are already directing these to a mailbox, you could do a couple of things. You could instead pipe them to a command or via cron run a command which reads the mailbox. In either case, this command could use flufl.bounce <https://pypi.org/project/flufl.bounce/> to extract the bounced address from the email message and then do whatever your current process does to remove the user. > What are other people doing with these messages? I basically do nothing. The issue of more concern to me is when the subscription uses a deliverable address. The owner of that address receives this unwanted confirmation email which is bad enough, but then sometimes reports it as spam to her ISP which affects my server's reputation. But, so far, I don't do anything about that either. -- 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: FW: lists.arun@gmail.com's bounce score incremented on Degrowcali

by Mark Sapiro

On 11/6/25 07:38, Christian Stalberg via Mailman-users wrote: > Whenever I post to this list I get quite a few of these bounce score > messages. How can I obtain a list of actual unsubcribes based on bounce > scores to remaining subscribers please? What can I do to stop this behavior > please? The sending of bounce score incremented notices is controlled by the list's bounce_notify_owner_on_bounce_increment setting exposed in Postorius as Settings -> Bounce Processing -> Notify owner on bounce increment. All bounce processing settings are in Postorius' Settings -> Bounce Processing section. The Users -> members list in Postorius displays the current bounce score for all members. The head of the GitLab branch, not yet released, also displays the member's delivery status, see https://gitlab.com/mailman/postorius/-/merge_requests/953. Disabling delivery due to bounces is logged in Mailman's bounce.log with messages like Disabling delivery for user(a)example.com on list mailman-users.mailman3.org by bounce Members whose delivery is disabled by bounce will normally be removed from the list after (Bounce disabled warnings interval)*(Bounce disable warnings) days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/24/21 10:00 AM, dancab(a)caltech.edu wrote: > Thanks Mark. I can't see the held messages view at all for this list. > I don't think there's any sensitive info so I'm posting the entire message I get to the server admin email. Thanks for that, but it's not helpful, at least for me. I'm looking for a Traceback leading to the error, but it isn't there. > One more note... > We were attempting to test modifying the template for the footer in non-digest messages. So the user/owner of the list had created a template with a modified footer based on the template: "list:member:regular:footer" That shouldn't affect access to the held messages view. Is there anything in Mailman's mailman.log that might be helpful, such as a "GET /3.1/lists/cpa-announcement(a)caltech.edu/held/..." message with a non 200 status. Also, are there "GET /3.1/lists/cpa-announcement(a)caltech.edu/..." messages with 200 status? Also, you didn't answer my > Is it only this list that has an issue? Can you visit other pages for > this list? questions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: very few moderation capabilities for moderators

by Mark Sapiro

On 9/16/21 2:39 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to provide the list moderators a way to change the moderation > flag for users from whichever it is (normally "list default processing") > to "hold for moderation" and viceversa (to "list default" or to "accept") > > I understand that it could be done via console script (That's the way I > did on mailman2: I made two commands using "withlist", one to hold, > moderar.py, and other one to accept, desmoderar.py. I show you below) Are you asking what the equivalent MM 3 scripts would be? > But I think I'm not the only one that could use as an improvement a way > to do this on postorius/web. Postorius allows a list owner or site admin to set Moderation for list members and non members at e.g. https://www.example.com/mailman3/lists/list.example.com/members/(non)member/. Currently, a list moderator who is not an owner cannot do this, but a moderator can set Moderation for the sender of a held post when handling the post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Moderation request email from a non existing user

by Mark Sapiro

On 6/1/22 00:45, David Lopez via Mailman-users wrote: > I'm on postorius 1.3.4 so I tried to do via shell but after logging it shows a syntax error. > > mailman shell -l mylist@mydomain(dot)com > pendingsdb = getUtility(IPendings) >>>> for token, data in pendingsdb.find(m, pend_type='unsubscription'): > ... ... if data['token_owner'] == 'moderator': > File "<console>", line 2 > ... if data['token_owner'] == 'moderator': > ^ > IndentationError: expected an indented block >>>> ... pendingsdb.confirm(token) > File "<console>", line 1 > ... pendingsdb.confirm(token) You are entering the `... ` prompts that I showed in my example. You show ``` ... ... if data['token_owner'] == 'moderator': ``` the first `... ` is the actual prompt from mailman shell. The second `... ` is the prompt from my example which you shouldn't enter. You should only be entering ``` pendingsdb = getUtility(IPendings) for token, data in pendingsdb.find(m, pend_type='unsubscription'): if data['token_owner'] == 'moderator': pendingsdb.confirm(token) commit() ``` Indentation is important. After `pendingsdb.confirm(token)` enter an empty line at the last `... ` prompt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: including a template failed

by Mark Sapiro

On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the following > errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max retries > exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member > :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to establish > a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member:regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.l… on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Search results for query "sapiro"