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

[MM3-users] Re: hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header

by Mark Sapiro

On 12/28/22 12:22, Odhiambo Washington wrote: > On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/27/22 22:00, Odhiambo Washington wrote: >>> I worke up to 959 such entries in my mailmanweb.log: >>> >>> ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The >>> MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. >> ... >>> >>> What might have been the cause of this? >>> >> >> Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= >> 1.3.5 requires mailman-hyperkitty>=1.2.0. Actually, HyperKitty>=1.3.5 with mailman-hyperkitty<1.2.0 produces a different message so that isn't it. There is an issue with Apache. If you search the archives of this list for the log message you'd find it, but see the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… But why these messages all of a sudden? Did you just change something? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: applying patch 1130

by Mark Sapiro

On 8/21/23 9:00 PM, David Newman wrote: > > On 8/21/23 7:57 PM, Mark Sapiro wrote: >> >> Since !1130 is merged, just `pip install` from the gitlab head. >> ``` >> pip install git+https://gitlab.com/mailman/mailman@head > > > Perhaps something else is needed first? This is on a Debian 12 system > upgraded from 11, with MM3 3.3.8 installed in a venv. > > (venv) mailman@x12:~$ pip install > git+https://gitlab.com/mailman/mailman@head > Collecting git+https://gitlab.com/mailman/mailman@head > Cloning https://gitlab.com/mailman/mailman (to revision head) to > /tmp/pip-req-build-wjge_v67 > Running command git clone --filter=blob:none --quiet > https://gitlab.com/mailman/mailman /tmp/pip-req-build-wjge_v67 > warning: redirecting to https://gitlab.com/mailman/mailman.git/ > WARNING: Did not find branch or tag 'head', assuming revision or ref. > Running command git checkout -q head > error: pathspec 'head' did not match any file(s) known to git > error: subprocess-exited-with-error It worked for me in a virtualenv with pip 23.2.1, but try ``` pip install git+https://gitlab.com/mailman/mailman@master ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: Gmail/Fetchmail in Mailman3?

by Mark Sapiro

On 06/23/2018 10:49 PM, Bill Christensen wrote: > On 6/23/18 5:01 PM, Mark Sapiro wrote: >> >> Delivery to Mailman is different in Mailman 3. What are you currently >> doing with Fetchmail? > the general syntax we're using is: > > poll imap.gmail.com protocol IMAP username "<list address>" > there with password "<password>" is "mailman" here nofetchall keep ssl > sslcertck sslcertpath /path/to/share/ssl/certs > mda "/path/to/mail/mailman post <listname>" set daemon 900 >> >> If you are doing something like getting the mail from google and >> delivering it via SMTP to an MTA on the Mailman server, that should >> still work for MM 3. > I think that's what the above is doing. Right? No. what the above is doing is piping the mail to "/path/to/mail/mailman post <listname>" That is what won't work for Mailman 3. I am not familiar with Fetchmail configuration, but what you need to do is forward the mail via LMTP to localhost:8024 with recipient listname@domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Welcome message template errors

by Mark Sapiro

On 4/22/24 19:23, Mark wrote: > > > On 2024-04-23 11:33, Mark Sapiro wrote: >> On 4/22/24 17:06, Mark wrote: >> >>> Then, as site-owner, creating a new custom Welcome template (again >>> via the WebUI) I can see it correctly added to the database in >>> mailman.template.uri >>> >>> - >>> https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… > > That URI should have been; > > https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… I think you are saying the what you reported originally was not correct and the URL in the template table was in fact the latter URL. > If I go to the above URL, the text of the list's Custom welcome message > displays on an otherwise empty webpage. And that's what is expected. So you can go to that URL and get the template, but when Mailman Core tries to do the same thing, it gets a timeout. Is there some firewall or other security software blocking this access? -- 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: FILTER_VHOST fix - was: Postorius & multi domain

by Mark Sapiro

On 4/22/20 11:52 AM, Mark Sapiro wrote: > > I'm currently working on a better fix. I'll post here on my progress. I've got a tentative fix at <https://gitlab.com/mailman/postorius/-/merge_requests/500/>. You can see the changes there to the file src/postorius/views/list.py. This fix is limited in that it should enable FILTER_VHOST work in an environment where there are domains with web host different from mail host, but if there are multiple domains with the same web host but differing mail hosts, going to that domain's Postorius lists view will show all domains as if FILTER_VHOST is False. I.e. consider the following set of domains: mail host web host example.com lists.example.com example.net example.net example.org lists.example.org example.edu lists.example.org With the fix installed and FILTER_VHOST = True https://lists.example.com/postorius/lists/ will show only the example.com lists https://example.net/postorius/lists/ will show only the example.net lists but https://lists.example.org/postorius/lists/ will show all lists, not just the example.org and example.edu lists. -- 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: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/22/22 13:07, Onyeibo Oku wrote: > On Sat Oct 22, 2022 at 7:44 PM WAT, Mark Sapiro wrote: >> The specific error you reported refers tp >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO >> >> what does >> ``` >> ls -l >> /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO >> ``` >> show? >> > > See below: > > command: > ls -lh /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO > > output: > -rw-r--r--. 1 mailman mailman 7.8K Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO This is actually strange. What does `pip --version` in your venv show? Did you do anything to install mailman and other packages in your venv other than `pip install`. I ask because I don't think there should be *egg-info directories in /opt/mailman/venv/lib/python3.10/site-packages/ at all. In particular, in addition to the actual code directories, I only see files and directories with names ending in nspkg.pth and dist-info. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: not correct language in subject(s)

by Mark Sapiro

On 5/23/23 08:19, Mark Sapiro wrote: > On 5/23/23 06:24, Jens Günther wrote: >> >> But also other examples: >> - bounce-mail for the user that moderator approval is necessary (there >> the text is in german, but the reason is in english) >> - approval-mail for moderator (also text is in german, but subject and >> reason in english) > > > I'll look into these. If you don't have the > mailman/messages/de/LC_MESSAGES/mailman.mo file, this could be the > reason, but there may be a bug. I just tested, and the notice to the moderator of a held message is in the list's preferred language including the Subject: and the moderation reason, and the notice to the user sending a held message is in the User's preferred language for that list including the Subject: and the moderation reason. I suspect your issue is you don't have the compiled mailman.mo German message catalog. The text is in German because it comes from templates and you presumably do have German language templates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: problem with Python's stdlib email module (was: Re: mailman break DKIM signature by modifying body)

by Mark Sapiro

On 6/5/23 10:07, Peter Münster wrote: > On Mon, Jun 05 2023, Mark Sapiro wrote: > >> Changes like those above are due to Python's stdlib email module. > > Could you point me to the code please, where the module is called? Basically, all over. https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/message.… defines a mailman.email.message.Message class which is a subclass of Python's email.message.Message class. https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… makes a mailman.email.message.Message object from the incoming bytes. This object is passed around through many Mailman modules and ultimately https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi… calls the delivery function which has multiple paths which all wind up at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/mta/connection… to send the message. and current code (Mailman >=3.3.6) will actually pass the message object to Python's smtplib <https://docs.python.org/3/library/smtplib.html#smtplib.SMTP.send_message> to send it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Bug in email.generator:_handle_text? [was: store/export existing Mailman lists ...]

by Mark Sapiro

On 9/15/22 12:09, Mark Sapiro wrote: > > This apparently confuses the Python email package so that the > get_payload() method returns a list of strings rather than a list of > message objects. Actually, that's not correct. The get_payload() method is returning a list of message objects. It only appears to be a list of strings because this is a mailman.email.message.Message object whose __repr__() method returns the content as a string. The real issue is the missing Content-Type: header which implies the content is text/plain. What I think is happening is the original message is parsed into a multipart/alternative Message object with payload of the text/plain and text/html subparts. Then something deletes the top level Content-Type: header which makes the message appear to be text/plain, yet get_payload() still returns the list of two subparts. So the real issue is what's removing all those headers from the anonymized message. I think there must be some issue with the configured anonymous_list_keep_headers or the code in mailman/handlers/cleanse.py is somehow corrupted. -- 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: Moderation Action Changed After Import

by Mark Sapiro

On 2/12/21 1:02 PM, Brian Carpenter wrote: > On 2/12/21 3:14 PM, Mark Sapiro wrote: >> It seems you imported to an existing list with import21. This is >> probably not a good idea. >> >> Those members who were moderated members of the MM 2.1 list will have >> their moderation action set to Hold, Reject or Discard based on the 2.1 >> list setting. > > I don't understand. Does not the import21 script require the Mailman 3 > list to be created first? The Mailman 3 list was new with no members > when I ran the import script. Yes, You did the right thing. I was mislead by "He said the previous moderation was the list's default which was hold for moderation." which is Mailman 3 terminology. The list does need to be created first, but it should be a new list with no members, owners, etc., not an operational Mailman 3 list. So, it seems that most of the members of the MM 2.1 list were moderated and the list's member_moderation_action was Reject. Is this not the case? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Search results for query "sapiro"