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

[MM3-users] Re: spanish localization

by Victoriano Giralt

On Thu, 2021-02-11 at 11:15 -0800, Mark Sapiro wrote: > For Mailman core you need to run > > ``` > cd mailman/messages/es/LC_MESSAGES > msgfmt -o mailman.mo mailman.po > > ``` > to compile the mailman.po file for gettext. Mark, I'd say the Mailman core message files taht get installed by pip are "a bit outdated" (source files dates point to a nightly build) ... proof here: [root@isoc-es messages]# pwd /usr/local/lib/python3.6/site-packages/mailman/messages [root@isoc-es messages]# ll */LC*/ ca/LC_MESSAGES/: total 164 -rw-r--r-- 1 root root 66479 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 95099 Oct 30 17:30 mailman.po de/LC_MESSAGES/: total 184 -rw-r--r-- 1 root root 81693 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 104049 Jan 17 20:41 mailman.po en/LC_MESSAGES/: total 172 -rw-r--r-- 1 root root 74350 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 97233 Oct 30 17:30 mailman.po eo/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 321 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55254 Oct 30 17:30 mailman.po es/LC_MESSAGES/: total 184 -rw-r--r-- 1 root root 80741 Feb 12 09:18 mailman.mo -rw-r--r-- 1 root root 102963 Nov 7 01:50 mailman.po fr/LC_MESSAGES/: total 124 -rw-r--r-- 1 root root 42261 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 81452 Jan 17 20:41 mailman.po he/LC_MESSAGES/: total 180 -rw-r--r-- 1 root root 79940 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 101264 Jan 17 19:20 mailman.po hu/LC_MESSAGES/: total 72 -rw-r--r-- 1 root root 9500 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 59290 Feb 3 02:44 mailman.po it/LC_MESSAGES/: total 180 -rw-r--r-- 1 root root 78543 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 100864 Jan 17 20:41 mailman.po ja/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1296 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55755 Oct 30 17:30 mailman.po ko/LC_MESSAGES/: total 164 -rw-r--r-- 1 root root 66668 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 94598 Oct 30 17:30 mailman.po nb_NO/LC_MESSAGES/: total 68 -rw-r--r-- 1 root root 6263 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 57744 Jan 17 19:20 mailman.po pl/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1933 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 56068 Oct 30 17:30 mailman.po pt/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 1734 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55963 Oct 30 17:30 mailman.po ru/LC_MESSAGES/: total 80 -rw-r--r-- 1 root root 12651 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 62127 Oct 30 17:30 mailman.po sq/LC_MESSAGES/: total 60 -rw-r--r-- 1 root root 321 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 55227 Oct 30 17:30 mailman.po tr/LC_MESSAGES/: total 168 -rw-r--r-- 1 root root 73537 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 96452 Jan 17 20:41 mailman.po zh_Hans/LC_MESSAGES/: total 64 -rw-r--r-- 1 root root 4945 Feb 3 02:47 mailman.mo -rw-r--r-- 1 root root 57269 Jan 17 19:20 mailman.po -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 3 months

[MM3-users] Re: OS upgrade - anything to take care of?

by Ruth Ivimey-Cook

On 13/05/2021 20:06, Mark Sapiro wrote: > On 5/13/21 11:28 AM, Ruth Ivimey-Cook wrote: > Yes, I overlooked some aspects of virtualenv. Actually, the Python in > the virtualenv is mostly symlinks to the Python it was built with, so > whether it continues to work after a Python upgrade depends on what the > symlinks are and how the Python upgrade installs. Correct. > >> I would therefore appreciate some guidance on performing the upgrade >> from 3.6 to 3.8 with the minimum of fuss. >> >> [I am not sure, but it could be possible to install python3.8 while >> using Ubuntu 18, so that the dist upgrade never breaks anything. Worth >> exploring.] > I haven't tested any of this, but I suspect if Python is for example, > /usr/bin/python3.6 and /usr/lib/python3.6 the upgrade removes those and > installs /usr/bin/python3.8 and /usr/lib/python3.8, that you could just > create symlinks from /usr/bin/python3.6 and /usr/lib/python3.6 to > /usr/bin/python3.8 and /usr/lib/python3.8 respectively and it would work. It would be nice if that worked, and I tried it, but it doesn't work because the python system and site directories under ./lib are also versioned (eg ./lib/python3.6/site-packages), so you would have to additionally create symlinks for those and/or rebuild those. > On the other hand, if the symlinks in the venv are to things like > /usr/bin/python3 and /usr/lib/python3 which used to point to 3.6 > versions and after upgrade point to 3.8 versions, it should just work. Sadly they aren't - they link to python3.6 or whatever... and even if not, the /lib/ naming gets you as well. And even if that can be worked around (eg by renaming the mailman /lib/python3.6 folder to /lib/python3.8), the python .pyc files are /also/ versioned, so you then have to find & delete them all to force the new interpreter to rebuild them or python falls down in a heap. > As far as installing Python3.8 on Ubuntu 18.04 goes, the machine I'm > typing this on is Ubuntu 18.04 and has 6 different Python3 versions > > mark@msapiro:~$ /usr/bin/python3.5 --version > Python 3.5.2 > mark@msapiro:~$ /usr/bin/python3.6 --version > Python 3.6.9 > mark@msapiro:~$ /usr/local/bin/python3.6 --version > Python 3.6.12 > mark@msapiro:~$ /usr/local/bin/python3.7 --version > Python 3.7.9 > mark@msapiro:~$ /usr/local/bin/python3.8 --version > Python 3.8.7 > mark@msapiro:~$ /usr/local/bin/python3.9 --version > Python 3.9.1 > > and /usr/bin/python3 is a symlink to /usr/bin/python3.6 and > /usr/local/bin/python3 is a symlink to /usr/local/bin/python3.9, so take > your pick... Indeed... and it would be lovely if it was that simple, but my experience was that even if you got a good python executable running, the other versioned elements of a python install caused it to mess up. What worked for me in the end was a combination of forcing a complete rebuild/reinstall with the mailman3 python3.8 install, followed by a bit of rejigging of file permissions and settings (probably because I'd messed something up, but maybe not). Regards Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years

[MM3-users] Re: configuring postfix local recipient table

by Stephen J. Turnbull

Alexander Inzinger-Zrock writes: > It seems i set both *facepalm* while doing [1] and then adding > changes according to [2]: It's OK to set both. But you need to coordinate "layout: LAYOUT" and "[paths.LAYOUT]" if you are going to set any paths such as var_dir. > so i have empty logs at /opt/mailman/mm/var/logs > and populated log files under /var/tmp/mailman/logs "var_dir: /var/tmp/mailman" is a good setting for experimenting with Mailman 3 before you're ready for production. But you don't want /var/tmp for production. Your logs and any queued messages will get deleted when the system reboots (for most system configurations). > Now - before changing the /etc/postfix/main.cfg - there is the > question that brings us almost back to the start: For the production system you want main.cf as it is, but change mailman.cfg to [mailman] layout: local [paths.local] var_dir: /opt/mailman/mm/var For an experimental system where you don't care if stuff disappears on reboot, you can comment out the two lines for [paths.local], and change the prefix in the *_maps variables in main.cf from /opt/mailman/mm/var/ to /var/tmp/mailman/. > **what is the recommended place to put the files to?** Wherever is convenient for you! There are four predefined "selectable layouts", paths.local, paths.dev, paths.here, and paths.fhs based on paths.master. paths.master defines the configurable names, and some more or less convenient defaults. In particular, it chooses a non-destructive (because temporary) var_dir: /var/tmp/mailman, and puts all of Mailman's data in a flat structure underneath. paths.local is just an alias for paths.master (defined in schema.cfg). paths.dev and paths.here are aliases for paths.master with var_dir set relative to mailman.cfg and the current directory respectively (two configurations some developers find convenient). paths.fhs pretty much ignores paths.master (except that it must use the same directory names) to put the various components in places that conform to the Filesystem Hierarchy Standard (FHS), which makes Debian and Ubuntu packagers happy. You can select any of those by using the "[mailman] layout" setting (I'm not sure if you can use "layout: master", but you're not supposed to). You can further modify them by using the "[paths.LAYOUT] SOME_dir" settings. In production, you almost certainly want either paths.fhs (as is) or paths.local with a var_dir setting either in /opt or in /var. > and that the above specific /opt/mailman -part is just a leftover "/opt" is not a "leftover", it's a convention where the whole package, including programs and resources, is placed in its own hierarchy (like a macOS application). The "var_dir: /opt/mailman/mm/var" setup is a configuration that Mark Sapiro found convenient and continues to use. I prefer a different layout, but if I were you I'd stick with layout: local, var_dir: /opt/mailman/mm/var because everybody who answers questions is familiar with it. > If my assumption is correct i would create an issue + merge-request > for the docs. No, the docs are generally fine. I'll check some details later. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 1 day

[MM3-users] Re: How to delete non-users

by Allan Hansen

Hi Mike, Yes, the users can be subscribed, but they think that they can't because it seems they are until the moderator accepts them. I tried your script again, with nothing happening. So I tried this: >>> >>> a = 1 >>> b = 1 >>> for l in lm: ... print(a) ... a = a+1 ... for nm in l.nonmembers.members: ... print(b) ... b = b + 1 ... nm.unsubscribe() ... >>> commit() >>> print(a) 1 >>> print(b) 1 It appears that lm can't see the lists (I have 50+ of them). Yours, Allan On 9/16/22, 15:01 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 9/16/22 11:19, Allan Hansen wrote: > Hi all, > > This is a bit of an emergency: > > I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. > For individuals I have been able to delete their non-membership and they then could subscribe properly. I don't understand. the fact that an address is a non-member of a list should not impact subscribing that address as a member. > I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. What is actually happening when the non-member attempts to subscribe as a member? What do they do and what it the result? > I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). > > Can anyone help me find out how to > a. delete all non-members of all my lists If you have access to `mailman shell` you could do: ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for l in lm: ... for nm in l.nonmembers.members: ... nm.unsubscribe() ... >>> commit() ``` > b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) nonmembers are an integral part of Mailman 3's architecture. The basic idea is a nonmember has a moderation action and setting a nonmembers moderation replaces MM 2.1's adding that address to one of *_these_nonmembers (The legacy *_these_nonmembers attributes still exist, but only to support regexps). It would require extensive modification to not create nonmembers. However, I still don't understand why the presence of a nonmember record is an issue. -- 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/

2 years, 7 months

[MM3-users] Re: How to hide sender completely

by Roland Miyamoto

Dear Mark and everyone, On 09/05/2023 17:12, Mark Sapiro wrote: > Anonymous lists should be removing any X-MailFrom: or > X-Envelope-From: headers from delivered mail. The envelope-from in > the outgoing mail should be the list-bounces address, not the > original sender. > If you are seeing this information in mail from an anonymous list, it > is a bug and I would like to see a raw message as received from the > list with this information. Thank you very much for replying so quickly. At the end of this email, I include a message's header received from one of my Mailman3 lists (renamed to ourlist here) with the following settings in the web interface: Alter Messages • Filter content =Yes • Collapse alternatives= No • Convert html to plaintext=No • Anonymous list= Yes • Include RFC2369 headers= Yes • Include the list post header = No • First strip reply to = Yes • Reply goes to list = Explicit Reply-to set; no Cc added • Pipeline = default-posting-pipeline DMARC Mitigations • DMARC mitigation action = No DMARC mitigation • DMARC Mitigate unconditionally = No As you can see, the header contains the sender's address sender(a)otherdomain.tld twice. Thanks for all your effort, Roland ---------------------------- (edited) list header follows ---------------------------- From - Fri Apr 21 23:18:21 2023 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <ourlist-bounces(a)list.timebrain.org> Received: from mail.timebrain.org by mail.timebrain.org with LMTP id Ph5sJ0XzQmSxBQAAMe3UBQ (envelope-from <ourlist-bounces(a)list.timebrain.org>); Fri, 21 Apr 2023 22:34:13 +0200 Received: from timebrain.org (localhost [IPv6:::1]) by mail.timebrain.org (Postfix) with ESMTP id 9110FC0082; Fri, 21 Apr 2023 22:34:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=list.timebrain.org; s=202205; t=1682109253; bh=KEcouWpeNLb32k6bFssIJDhe16IGlOZEsBeJOIigkLs=; h=Date:To:In-Reply-To:References:From:Reply-To:Subject:List-Id: List-Help:List-Post:List-Subscribe:List-Unsubscribe:From; b=MmI/E0AHnIway3V//e0KNbYj06VBWcDKGMlK4yA+tPGmgCAnje4NwZM9YXbZk/hc7 FKM8O1RRkfUhC6iCUHMQa28XK4Nr9+45G/Yxl7Tgr8h6qt1B/1myOCLS8Mb+4XSwpm CuShRI812x7GkCWVqpLoRBKwq4CP8j8BdDgN4rmrUF18Mdh0J/kkccV13dJvG9xapB XzUkpqcJICWNyQ/1+GY59VEISP3EBQxUzg6Qkd6a4BXkPKNPCRzVUVM0irvQ0nLi8Z nAKnV7iutn5nKMXOkEfX5K+8HuFm2Ixd1cWnSIfPY7gd0WK0DyjLVgsZIINA6Hnwt5 9fABm1Dsr6YeQ== Received: from mail.timebrain.org (localhost [127.0.0.1]) by mail.timebrain.org (Postfix) with ESMTP id C912FC0082 for <ourlist(a)list.timebrain.org>; Fri, 21 Apr 2023 22:34:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=demonetize.it; s=201907; t=1682109251; bh=799sMT9Q1QA5X8QRdz/ErDUnITC5MNct/qLMzA5zPSA=; h=Date:From:To:Subject:In-Reply-To:References:From; b=KKp8OdYRcEStg4A3qhDgKm4fJQg8U6xPL9w1jbcNJ3BozX8QKqg3NqVC6cbcptHtr 9tUzsc1WBCYy1UHH7UOCFXowfNtRu+KlvT8YpBNeGgsa12nZ4Ljhw7IRuENcp1sqyj tnZWWRW8T+wcsJlftOhcCudT59gq1LilZIEPpDNGJ63jgJIX5838IBaz2cXZyHQAWd XMF6uTz/xc5sRutPHWOUtRETHySK0PEI59cpkRz1UvHwDu1opliv4ILZmR4BW32T6a OeK06uv6uhRfH8Gc420zhkp+tYSgUc28Z4G93uDC12MypmKshnsZiR52MUFZp1JM8X eJGEpnGP7xHew== Received: from [IPv6:::1] ([2a02:560:4ca5:ea00:5c9f:6282:e0ec:582]) by mail.timebrain.org with ESMTPSA id zuaKLUPzQmSnBQAAMe3UBQ (envelope-from <sender(a)otherdomain.tld>) for <ourlist(a)list.timebrain.org>; Fri, 21 Apr 2023 22:34:11 +0200 Date: Fri, 21 Apr 2023 22:31:08 +0200 To: Ourlist Ourtown <ourlist(a)list.timebrain.org> User-Agent: K-9 Mail for Android In-Reply-To: <a8c92d51-66c2-2588-f00c-31146bee2f54(a)timebrain.org> References: <3e35f420-a766-095e-b79a-afb8e795f011(a)timebrain.org> <a8c92d51-66c2-2588-f00c-31146bee2f54(a)timebrain.org> Message-ID: <7AB6FFA2-BDA7-4484-BF14-4CF512A4B8E8(a)demonetize.it> MIME-Version: 1.0 Message-ID-Hash: 7IYNX33ESBTJZ3M4FGHGGVDBTZ3HGL2B X-Message-ID-Hash: 7IYNX33ESBTJZ3M4FGHGGVDBTZ3HGL2B X-MailFrom: sender(a)otherdomain.tld X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header From: Our List <ourlist(a)list.timebrain.org> X-Mailman-Version: 3.2.1 Precedence: list Reply-To: Ourlist Ourtown <ourlist(a)list.timebrain.org> Subject: [Ourlist] Re: whatever was the topic List-Id: Our List <ourlist.list.timebrain.org> List-Help: <mailto:ourlist-request@list.timebrain.org?subject=help> List-Post: NO List-Subscribe: <mailto:ourlist-join@list.timebrain.org> List-Unsubscribe: <mailto:ourlist-leave@list.timebrain.org> Content-Type: multipart/mixed; boundary="===============6841522137146215921==" --===============6841522137146215921== Content-Type: multipart/alternative; boundary=----F0JANJPGLDOAM8SUMOY3TD9QT0ZRGF Content-Transfer-Encoding: 7bit ------F0JANJPGLDOAM8SUMOY3TD9QT0ZRGF Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable

2 years

[MM3-users] Re: old usernames appearing in mailman.log

by Ken Alker

--On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 11:04 AM, Ken Alker wrote: >> >> I've just taken on the project so I'm new to all of this, and one thing >> I noticed that caught my eye, and has left me curious, is that for the >> first a couple of seconds starting just after midnight every night (just >> after log rotation) mailman.log would have many (dozens, or hundreds) of >> lines entered in it just like this one: >> >> Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET >> /3.0/users/old-user(a)domain.tld HTTP/1.1" 404 58 >> >> where "old-user(a)domain.tld" is the email address of a user who either >> had unsubscribed or changed their email address (I don't know which, I >> just know they are no longer a member/subscriber to the list). Each >> successive entry in the log would have a different "old username" in it. >> I don't understand why these entries would be in the log and what they >> mean. Can someone shed some light on this for me? This is merely a >> question of curiosity, and not one of import. (Since migrating from >> 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.) > > > This is the Django hyperkitty sync_mailman job which is one of the django > admin jobs run daily. It goes through the HyperKitty 'sender' database > table and tries to find the Mailman core user id for each sender address > to add/update its mailman_id field with core's user_id. > > The 404s are addresses im HyperKitty's sender table for whih there is no > corresponding Mailman user. There are multiple possible reasons for this. And that is OK, right? > If the behavior has stopped it's probably because the periodic Django > jobs are not being run - this is bad. I see this in the logs from just after midnight: Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list found Jun 25 00:13:04 2023 (386086) ACCEPT: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> Jun 25 00:13:04 2023 (386090) HyperKitty failure on https://lists.netlojix.com/hyperkitty/api/mailman/urls: Followed by a huge amount of HTML (strange). I'm not sure if the first and last (third) lines in the log excerpt above are due to the same thing. I know why the public suffix list is not found; when I was migrating all my queues from the Debian layout to the "source install" layout, I could not figure out where it should go in the new world order. Can you tell me where it would normally be found on a fresh source install? I'll move it there. Is there a way to kick it into re-running whatever it does at midnight so I can test this again after putting the public suffix list back? I assume I can just execute "mailman-web runjobs daily", but will this mess things up, or is it OK to run it mid-day without stopping anything first? Is the last (third) log line excerpt simply a result of the first, or do I have something else messed up? Thank you! Ken

1 year, 10 months

[MM3-users] Re: mm3 installation question

by Odhiambo Washington

On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Odhiambo Washington writes: > > > Mark Sapiro writes: > > > > Some of the `path` settings are probably not in the same order as > > > in that file. The > > > > > > ``` > > > path('mailman3/', include('postorius.urls')), > > > path('archives/', include('hyperkitty.urls')), > > > ``` > > > settings should come after the > > > ``` > > > path('postorius/', include('postorius.urls')), > > > path('hyperkitty/', include('hyperkitty.urls')), > > > ``` > > > settings (unfortunately, mailman-web 0.0.8 has these in the wrong > > > order). Or you can just delete the 'postorius/' and 'hyperkitty/' > > > ones or you can add > > > ``` > > > ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" > > > ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" > > > ``` > > > to your Apache config. > > > The odd thing is that the HOWTO that he followed never involves the > > manipulation of any urls.py at all - it's not even mentioned at any > > point. So obviously the issue is caused by something else and I > > suspect something within Apache needs to be re-evaluated in the > > guide. > > I believe this is the Apache configuration the OP is using: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/admin" "http://127.0.0.1:8000/admin" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > </IfModule> > > Note that Apache doesn't know about the "/postorius" and "/hyperkitty" > URI paths. It is quite unclear to me how this works at all with > either the > > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > > version of urls.py or the reverse order version > > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > path('mailman3/', include('postorius.urls')), > path('archives/', include('hyperkitty.urls')), > > I think Mark must have a configuration with > > ProxyPass "/" "http://127.0.0.1:8000/" > > in the Apache configuration in mind? Or an alias or rewrite rule. > Otherwise I don't see how "/postorius" and "/hyperkitty" paths ever > get transmitted to the WSGI server. > My thinking then is that the documentation at https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration needs to be fixed by adding the missing bits, or a urls.py be provided for inclusion in /etc/mailman3/ and which sysadmins can edit to their liking. For example, I'd prefer to have /mm3 instead of /mailman3 to save on transmitted bytes and not clog the Internet pipes :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 2 months

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Thank you for the clarification! Am 19.03.21 um 18:48 schrieb Abhilash Raj: > > >> On Mar 19, 2021, at 6:38 AM, Jens Günther <jens.guenther(a)posteo.de> wrote: >> >> Thank you for your answer. I should have seen that in the Docs, but somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > You seem to have landed on a very old version of the docs that I didn’t unfortunately knew > was even available. I have disabled that page now. > > The settings are documented in https://docs.mailman3.org/en/latest/config-web.html > >> >> I set it in the corresponding file, but unfortunately it doesn't work :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS works, changed here from '*' to 'localhost' and my example-domains, this works). It seems to be the same as this user describes (a while ago): https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> How could I check, that the setting is used!? >> >> But maybe some additional information: >> - I use the Debian installation on a stable buster, so mailman is version 3.2.1 >> - I use apache2 as my web-server and use the given alias-conf-file >> - Python is version 3.7.3 >> - Postorius is Version 1.2.4 >> - HyperKitty is version 1.2.2 >> >> -> In Django admin-Panel (/mailman3/admin/) I added 2 Websites test1.xyz.de and test2.xyz.de >> -> In Postorius (/mailman3/postorius/domains/) I added 2 Domains as Mail Hosts test1.xyz.de and test2.xyz.de with the corresponding Web hosts as stated above >> -> I added 1 list (/mailman3/postorius/lists/) for each Mail Domain as follows: test1(a)test1.xyz.de and test2(a)test2.xyz.de >> -> then created a vhost in apache2 with SSL-cert and added the Domains in ALLOWED_HOSTS: test1.xyz.de and test2.xyz.de >> -> When I go to the 2 Testdomains (corresponding web hosts), I see on each both lists for the different Mail domains >> >> What do I miss? Or where to investigate? >> >> Thank you in advance, best regards. >> >> By the way: what'S the difference in the 2 docs? https://docs.mailman3.org/en/latest/index.html and https://mailman.readthedocs.io/en/latest/README.html > > Mailman Suite consists of several individual projects including Mailman Core, Postorius (Web UI) and > Hyperkitty (Archiver). The first URL is the landing page for the entire suite and should direct you to > individual projects. The second one is the individual Mailman Core project. Historically, Core was the > only project and hence claims the name “mailman” in most places. > >> >> Am 18.03.21 um 21:52 schrieb Mark Sapiro: >>> On 3/18/21 9:20 AM, jens.guenther(a)posteo.de wrote: >>>> Is it possible, to only show publicly (if advertised) these lists on a certain url, that are corresponding to the web host the url I accessed mailman through? >>> Set FILTER_VHOST = True in your settings_local.py or where ever you put >>> your site Django settings. >> _______________________________________________ >> 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/ >

4 years, 1 month

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Thomas Ward

On 10/18/23 20:25, Mark Sapiro wrote: > On 10/18/23 15:06, Thomas Ward via Mailman-users wrote: >> Is there a way to oerhaps custom-plugin my way through to set this up >> as an integration into Core? And specify the custom handler process >> or such to allow that integration? I see that there are ways to code >> plugins into existence so it may be a custom-processor plugin or such >> for this purpose. > > > The issue is Mailman core would have to keep track of the message-ids > and thread number of all prior posts to know whether the current post > is a reply to some other post or not. > > You would need a new database table or some other mechanism to keep > track of this and then you may need to keep everything forever because > you can't know that there won't be a future post in reply to some very > old post. > I think this is doable in our (read: Employer) use case, but without needing to modify Mailman Core much beyond a custom plugin and some fussing around. This is a side effect of a custom implementation of "Tagging" data by thread ID in a separate data / intel tagging system that reads from received emails in a custom intel processing mailbox. That has zero care as to how Mailman or Hyperkitty index items, and actually is pretty trivially implemented with `PREFIX` format being [ListName-NNNNNNN]: 1. If subject does not match `PREFIX` format: * Get next thread number from DB (In postgres, this is a serial matched to {list_id}_thread we call with nextval()) * Add subject prefix as [ListName-{ZeroPaddedThreadNumFromDB}] 2. If subject matches `PREFIX` form: * Do nothing As for how HyperKitty handles this, it replies entirely on RFC 5322 fields (see section 3.6.4 in that RFC) for identifying reply to, etc. to identify replies to things, which in turn it seems is fully capable of handling that. We simply need the message to be sent *with* a thread ID that members can hit reply to and keep the prefix in the subject line. We don't care how that's done in the Hyperkitty side of things, we only care about it being sent in the subject line. I noticed that Mailman3 has the capacity for external / custom plugins, and with some work I believe I can achieve this with a customized pipeline with a custom handler of `thread-prefix` instead of `subject-prefix`, otherwise calling the other handlers done by the traditional system, and just handle prefix differently in the thread-prefix handler in the custom pipeline. I'm following this attempt currently, but will keep it internal to employer. It'll also be kept internal to our use-case because it isn't easily exportable to other Mailman3 implementations. But yes, you're right it needs additional DB table to map list_id <--> thread_id and then would need some kind of "Subject prefix uses thread IDs instead of Post IDs config option", or only handle based on a custom pipeline. I"m going to deep dive into this on my end and see if I can come up with a solution that relies direct on the DB calls. Which hopefully should be safe to do, but we'll see in testing. Thomas

1 year, 6 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Guillermo Hernandez (Oldno7)

El 3/4/23 a las 1:25, Mark Sapiro escribió: > On 4/2/23 03:57, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I'm NOT blaming any of the parts involved... Sure, most probably is >> my fault. But the last upgrade shows that the process that fail is >> involved with mailman upgrade. The last server was working smoothly >> and it has higher traffic than the first I tried. It cannot be that I >> missed that something was not working for weeks (since the last >> upgrade of the OS) > > It depends on what you did. Mailman's lmtp runner would only encounter > this issue at startup, so unless you restarted Mailman or rebooted the > server, lmtp runner would have continued without issue even if there > was an underlying OS problem. I thought I said it: I reboot this server everyday at 06:40 CEST time. That's why I'm sure it's not an undetected problem for weeks. The lists in this last upgraded server are with daily traffic. I'm suscribed to all. > > Also, I don't think the problem is with Mailman per se. The underlying > issue is in the Python library socket module. Try the following in a > Python 3 shell > ``` > $ python3 > Python 3.9.16 (main, Dec 11 2022, 12:49:23) > [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock > >>> sock = makesock(AF_INET6, SOCK_STREAM) > >>> sock.bind(("::1", 0)) > >>> sock.close() > ``` > This is essentially what aiosmtpd does and I expect that `sock = > makesock(AF_INET6, SOCK_STREAM)` will throw the `OSError: [Errno 43] > Protocol not supported` exception. > And you are right (ther is more down of this): Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.9/socket.py", line 232, in __init__ _socket.socket.__init__(self, family, type, proto, fileno) OSError: [Errno 43] Protocol not supported Buuuuuut, if I do the same in the "father" server: Python 3.9.16 (main, Dec 15 2022, 09:41:07) [Clang 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a on freebsd13 Type "help", "copyright", "credits" or "license" for more information. >>> from socket import AF_INET6, SOCK_STREAM, socket as makesock >>> sock = makesock(AF_INET6, SOCK_STREAM) >>> sock.bind(("::1", 0)) >>> sock.close() File "<stdin>", line 1 sock.close() IndentationError: unexpected indent >>> sock.close() >>> The server can open a socket without problem. As I though previously it has to be something with the jailed envviroment. Your test had probe me right (and wrong in my jail tests). It's very valuable. I know now where I can dig more. Thanks a lot -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 1 month

Search results for query "sapiro"