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

[MM3-users] Re: Removing the option to delete a list on the Postorious interface

by Mark Sapiro

On 6/14/22 13:43, Wong, Wesley wrote: > Hi, I have a question on the Postorious web interface in Mailman 3. I have found that a list owner can delete a list through the Postorious interface if they have the role of owner to the list. I wanted to have it either disabled or removed but I am not sure where to look to make changes to it. I would rather remove it from the interface totally so it would be done from the command line. Any help would be greatly appreciated. The simplest change would be to edit postorius/templates/postorius/menu/list_nav.html and remove the line. ``` <li role="tab" class="nav-item"><a href="{% url 'list_delete' list.list_id %}" class="{% nav_active_class current 'list_delete' %} nav-link">{% trans 'Delete' %}</a></li> ``` In addition to the above, you could edit postorius/urls.py and remove the line ``` re_path(r'^delete$', list_views.list_delete, name='list_delete'), ``` or in older Postorius versions ``` url(r'^delete$', list_views.list_delete, name='list_delete'), ``` to render the `delete` URL unknown. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Trying to understand the mailman.cfg from the virtualenv installation guide

by Mark Sapiro

On 9/8/24 01:04, unite42--- via Mailman-users wrote: > Hello, > > I'm trying to install Mailman3 following the Virtualenv Installation guide. I would like to understand why the configurations in the displayed mailman.cfg are recommended. > > Especially the following two: > > [archiver.prototype] > enable: yes > > "The prototype archiver stores messages individually in > var/archives/prototype/LIST_NAME/." > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > Do I need this, when using hyperkitty? Is this a fail-safe recommendation? The prototype archiver is separate from and independent of HyperKitty. If you are using HyperKitty as an archiver, you don't need the prototype archiver. Note however that if the prototype archiver is not enabled, it can't be used at all, but if it is enabled, it can still be enabled or disabled on a per-list basis. > [mta] > verp_confirmations: yes > verp_personalized_deliveries: yes > verp_delivery_interval: 1 > > What is the background of these recommendations? These settings enable VERP for all list messages. This results in more reliable bounce processing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Cannot Create New List

by Mark Sapiro

On 11/1/25 10:20, dap1--- via Mailman-users wrote: > I'm trying to create a list (on Ubuntu) and I'm getting this: > > <venv> $ python3 > Python 3.12.3 (main, Aug 14 2025, 17:47:21) [GCC 13.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. >>>> owners = ['xxxx(a)ddddddddd.net'] >>>> from mailman.app.lifecycle import create_list >>>> ant = create_list('llllllllllllll(a)dddddddd.net', owners) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 74, in create > _list > getUtility(IEmailValidator).validate(fqdn_listname) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", line 180, in getUtil > ity > raise ComponentLookupError(interface, name) > zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.address.IEmailVa > lidator>, '') I'm not sure why this doesn't work, but it probably will if you do it in `mailman shell` which defines a lot of things for you. However, it is much simpler to just use the `mailman create` command to create a list. See `mailman create --help` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Hyperkitty download mbox

by Mark Sapiro

On 4/30/21 1:00 PM, Andrew Hodgson wrote: > > I tried this but get the same error, hope I did the modification correctly. > > [2021-04-30 19:56:31 +0000] [22104] [ERROR] Error handling request > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request > for item in respiter: > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox > msg = email.as_message() > File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message > msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') This is the change I suggested, so you did it correctly. > File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ > self._headers.append(self.policy.header_store_parse(name, val)) > File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse > raise ValueError("Header values may not contain linefeed " > ValueError: Header values may not contain linefeed or carriage return characters I don't understand why that change didn't work, but you could try replacing that line with ``` msg["Message-ID"] = "<%s>" % re.sub('[ <>\r\n]', '', self.message_id) ``` -- 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: mailman3 postorius cannot retrieve template

by Mark Sapiro

On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to a > suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because django > is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 (175334) > Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is impossible to > configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command which > includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as 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

4 years, 1 month

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

3 years, 11 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

3 years, 8 months

[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

1 month, 1 week

Search results for query "sapiro"