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

[MM3-users] Re: Mailman3 breaking DKIM signatures

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/23/25 12:53 AM, Danil Smirnov via Mailman-users wrote: > > Doesn't this parameter fits better? > > > > https://docs.python.org/3/library/email.policy.html#email.policy.EmailPolic… > > That would be better except Mailman uses the legacy > email.message.Message class whose policy is Compat32 and the Compat32 > policy doesn't accept refold_source. I would welcome a patch, especially if (a) tested on a system offering lists to the general public (or some organization large and diverse enough to support the span of the MUAs cat(1), mutt, Thunderbird, and Outlook), and (b) enabling owners at some level to select policy. I don't promise to apply (it's not my call), but I've personally been interested in a number of issues that can probably be addressed via email.policy tweaks. Steve

1 year, 8 months

[MM3-users] Re: 500 Internal Server Error on specific list pages

by Johnny Cison

The Mailman logs contain the following: Jul 30 10:32:11 2020 (26190) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 346, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 135, in __call__ adapter = self.__adapt__(obj) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 151, in __adapt__ adapter = hook(self, obj) File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 353, in queryAdapter return self.adapter_hook(provided, object, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 363, in adapter_hook result = factory(object) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2793, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() On Thu, Jul 30, 2020 at 1:46 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/20 9:55 PM, Johnny Cison wrote: > > I have a new Mailman 3 server set up and am having a strange issue with > > just one particular list. > > > > Accessing the list's Info page URL or it's Archiving Settings page URL > > returns a 500 Internal Server Error, but its other pages work correctly. > > Also, the Info and Archiving pages on the other lists are working > correctly. > > > > When I access the info page for the problem list, I get these errors in > the > > log: > > > > Traceback (most recent call last): > > File > > "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", > line > > 41, in inner > > response = get_response(request) > ...> line 103, in call > > raise HTTPError(url, response.status, content, response, None) > > HTTPError: HTTP Error 500: A server error occurred. Please contact the > > administrator. > > > > > > When I access the Archiving page in Settings, I get these: > > > > Traceback (most recent call last): > > File > > "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", > line > > 41, in inner > ... > > line 103, in call > > raise HTTPError(url, response.status, content, response, None) > > HTTPError: HTTP Error 500: A server error occurred. Please contact the > > administrator. > > > These messages are from Django's log. What's in Mailman's mailman.log? > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 2 months

[MM3-users] Re: Template's encoding setup

by Ugnius S

Mark, You were 100% right for fixing. I was not sure what the language setting were on list creating, but one of the lists was created a day ago and I was doubt about it a little. So I made test: I have checked that default language is lt, and then I created the new list for testing. I had language issues with the HTML as well. Your recipe helped to resolve the issue. :) I fixed all my lists. I have stopped the mailman (just in case), than executed as You had told: $ mailman shell -l test(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the test(a)example.com mailing list >>> m.preferred_language <Language [en] English (USA)> >>> m.preferred_language = 'lt' >>> <Ctrl>+D Thank You very much. This fix made magic. Kind regards Ugnius 2019-09-14, št, 20:20 Mark Sapiro <mark(a)msapiro.net> rašė: > On 9/14/19 4:06 AM, Ugnius S wrote: > > > Yes, I have made several tests. I have set charset: iso-8859-13 > > and default_language: lt in mailman.cfg. > > If you created the list before you set default_language: lt in > mailman.cfg, the list's preferred_language is possibly 'en;' with > character set us-ascii. > > > > (Also I have set LANGUAGE_CODE = 'lt' in the settings_local.py, but I > think > > it is not related to this case.) > > > Yes, LANGUAGE_CODE in settings_local.py is not relevant to this. > > > > I have tried to set utf-8 as well in mailman.cfg as well. And I can > > confirm - in all tested cases > > text characters are correct (in footer as well) if sender sends text > only. > > OK > > > > If sender sends message in HTML (mostly all users send) then no > > matter what the encoding is set in my mailman's > > configuration or iso-8859-13, or utf-8 message body looks correct, but > in > > footer all national characters are replaced with > > question marks " ? ". > > > The addition of the footer is done by mailman/handlers/decorate.py. In > the plain text case the message body is converted to unicode, the > unicode footer is appended to the body and the new body is encoded for > transmission. The encoding is the first of the list's character set, the > incoming message's character set or utf-8 which produces no error. > > > In the case where the incoming message is not a single plain text > message part, the footer is added as a separate MIME part with the > unicode footer encoded in the list's character set with > errors='replace'. This is what produces the '?' characters. I suspect > this happens because the list's preferred_language is 'en' with > character set us-ascii. > > try running Mailman's > > bin/mailman shell -l your_list@domain > > at the prompt enter > > m.preferred_language > > if the response is not > > <Language [lt] Lithuanian> > > do > > m.preferred_language = 'lt' > > and then control-D to exit. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 1 month

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

Hi Mark, thanks for your inputs. I am making progress. On January 2, 2023 9:15:59 PM GMT+01:00, Mark Sapiro <mark(a)msapiro.net> wrote: >On 1/2/23 11:56, Onyeibo wrote: >> On Mon, 2 Jan 2023 09:57:45 -0800 >> Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>> curl -urestadmin:restpass http://localhost:8001/3.1/lists >>> >>> It should return JSON with information about your lists. >>> >> >> I get the following: >> {"start": 0, "total_size": 0, "http_etag": >> "\"678678567346533573674563786538\""} > >That is the expected response if you have no lists yet. So connection to >Mailman's REST API works via curl, so why doesn't it work via >mailmanclient? If Mailman core was running, it should work. I don't know >why it doesn't. Perhaps you have some kind of firewall that's blocking it. > It turns out to be a fault from my settings. Postfix was not happy with the default email for the admin (<root@localhost>) since I had an operational virtual map for users. That connection error disappeared when I added a functioning admin email address. There are other issues, however. (1) Mailman refuses to resolve to a preferred subdomain. If the server's domain is "website.tld", I'd like mailman's homepage to be at "list.website.tld". Mailman insists that I add "website.tld" to the ALLOWED HOSTS, whereas "lists.website.tld" is already there as an ALLOWED HOST (same VPS/IP address nonetheless). The result is that the homepage ends up at "https://website.tld/mailman3/lists" when the desired url is "https://lists.website.tld/mailman3/lists". This is a conflict because the main domain is intended for another service. How do I approach this? (2) See the traceback below: ERROR 2023-01-03 07:40:32,078 27926 django.request Internal Server Error: /mailman3/lists/ Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib64/python3.10/site-packages/postorius/views/list.py", line 980, in list_index return render(request, template, File "/opt/mailman/venv/lib64/python3.10/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/backends/django.py", line 62, in render return self.template.render(context) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/base.py", line 173, in render with context.bind_template(self): File "/usr/lib64/python3.10/contextlib.py", line 135, in enter return next(self.gen) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/context.py", line 254, in bind_template updates.update(processor(self.request)) File "/opt/mailman/venv/lib64/python3.10/site-packages/django_mailman3/context_processors.py", line 32, in common context["site_name"] = get_current_site(request).name File "/opt/mailman/venv/lib64/python3.10/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/contrib/sites/models.py", line 59, in get_current return self._get_site_by_id(site_id) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/contrib/sites/models.py", line 30, in _get_site_by_id site = self.get(pk=site_id) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/query.py", line 650, in get raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. It seems a migration is missing. How should I approach this?

3 years, 9 months

[MM3-users] Google Summer of Docs

by Terri Oda

On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >Ralph Seichter writes: > > * Mark Sapiro: > > >> > If you post an issue at ><https://gitlab.com/mailman/mailman/issues>, > > > one of our GSOC aspirants may pick it up. > > > > Done, although I wonder if any GSOC participant would want to write > > documentation instead of code... ;-) > >For their actual, Google-supported, project, Google explicitly >excludes documentation. > They do for Google Summer of **Code** but they've just announced Google Summer of **Docs** which sounds really neat and we might want to participate. (It's my personal opinion that our docs have really suffered since I finished my PhD and stopped using them as a warmup exercise when I was procrastinating on writing my thesis. *grin*)

7 years, 6 months

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Seth Seeger

> On May 8, 2020, at 11:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > It should show the display name corresponding to the domain name that > matches the domain in the URL that you go to. If this doesn't seem > correct, perhaps there is some issue with the way you are proxying in > your web server. Here is my proxy entry in Nginx: location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8080; uwsgi_read_timeout 300; } My uwsgi_params file: uwsgi_param QUERY_STRING $query_string; uwsgi_param REQUEST_METHOD $request_method; uwsgi_param CONTENT_TYPE $content_type; uwsgi_param CONTENT_LENGTH $content_length; uwsgi_param REQUEST_URI $request_uri; uwsgi_param PATH_INFO $document_uri; uwsgi_param DOCUMENT_ROOT $document_root; uwsgi_param SERVER_PROTOCOL $server_protocol; uwsgi_param REQUEST_SCHEME $scheme; uwsgi_param HTTPS $https if_not_empty; uwsgi_param REMOTE_ADDR $remote_addr; uwsgi_param REMOTE_PORT $remote_port; uwsgi_param SERVER_PORT $server_port; uwsgi_param SERVER_NAME $server_name; Is there something I’ve missed? I followed a tutorial for this (which is no longer available). Seth

6 years, 5 months

[MM3-users] Re: Server error,An error occurred while processing your request. - SITE_ID

by Flo

On 6/22/26 1:39 AM, Mark Sapiro wrote: > On 6/21/26 2:19 PM, Flo via Mailman-users wrote: >> >> I created a new site (my.site.net) in Django, deleted example.com and >> changed SITE_ID to 0 in /etc/mailman3/settings.py . >> >> After restarting mailman3 and mailmanweb services I get >> Server error,An error occurred while processing your request. >> when I call https://my.site.net/admin again. >> >> Even if I change SITE_ID back to 1 there is no change. > > Do this database query on Mailman's database > ``` > SELECT * FROM django_site; > ``` > Then set SITE_ID to number associated with your domain. > It turned out that 2 is the value to be assigned to SITE_ID. Thank you for your help. Flo

3 months, 3 weeks

[MM3-users] Re: Welcome message template errors

by Mark

> On 2024-04-24 03:58, Mark Sapiro wrote: > >> What do you get if you do >> ``` >> sudo -u mailman curl >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… >> ``` >> with the template set in Postorius? > ******************* > The welcome message is returned. > > root@hel:~# sudo -u mailman curl > https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… > Test Welcome message for new subscribers.root@hel:~# ******************* Making progress... I edited settings file again, replacing the domain name with the IP address () POSTORIUS_TEMPLATE_BASE_URL = 'http://12.34.56.78' (no SSL) The URI in the template table now has this. http://12.34.56.78/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/list… Now, when Mass subscribing a new member, a Welcome email is sent to the new member with the correct Subject and From, but the message is blank.

2 years, 5 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Stephen J. Turnbull

Mark Sapiro writes: > Not if we're collapsing alternatives. If we're collapsing a > multipart/alternative part with text/plain and text/html > alternatives to just the first alternative we don't keep the > text/html part. I understand that's what we currently do. But I think that when the MUA provides an empty plain text part and a non-null HTML part, that's a mark of lazy MUA developers, not author intent. I think that it's very likely that the author would prefer the reader get converted HTML rather than a blank. Of course if the list owner wants to inhibit conversion, that's fine. But I would expect that list owners who enable conversion would also want to present a converted alternate rather than the blank plain text. Steve

1 year, 8 months

[MM3-users] Re: Unknown attribute: max_message_size

by Alexander Klotz

Hi, unfortunately we still have problems configuring a list so that it allows a message size larger than 40 KB. Neither the workaround described here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24… (required was already set to false) nor this docker setup by yova https://gitlab.com/mailman/postorius/issues/246 worked. Are there any other options we could try? Thanks! Regards, Alex Klotz (CultureBase editorial staff) Am 28.05.18 um 17:16 schrieb Mark Sapiro: > On 05/28/2018 08:05 AM, Alexander Klotz wrote: >> Hi, >> >> just encountering the same problem in postorious, how are the chances of >> a fix being released soon? > > > It is fixed in the current branch heads. We plan a new release very > soon. There are still a few things we want to get in the release, so > it's not quite ready yet, but we're working on it. >

8 years, 3 months

Search results for query "sapiro"