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

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 4:08 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 3:33 PM, Mark Dadgar wrote: >> >> Any thoughts on how to salvage ~20 years of list archives? > > > The archives shouldn't be an issue. I don't think they are involved in > the corruption, but anyway, hopefully you still have the archive mbox > you imported. Then for the messages since then, you should be able to > get a mbox from hyperkitty with something like > > https://example.com/hyperkitty/list/listname@example.com/export/arbitrary-n… > > with the obvious substitutions and appropriate start and end dates. > > The list is trickier. If you are going to start over with a clean > install, and if you have a config.pck that you imported from MM 2.1, I > suggest the following: > > Use the `mailman members` command to get a list of all members. Then > depending on how much work you want to do, also get separate lists of > plaintext and mime digest members and members with delivery disabled. > > Then on the new install, import the config.pck with `mailman import21` > and import the archive mboxes with hyperkitty_import. > > Run `mailman members --sync` with the full current membership list, and > record the [ADD]s. Then you can match the [ADD]s against the plain and > mime digest members and those with delivery disabled and set their options. > > That's a lot to do, but it should get you close. I would probably be satisfied with just exporting the current list of member email addresses + names and letting people go back and change their list settings to switch to digest, etc. if necessary. > On the other hand, if you can wait, we might be able to figure out how > to fix this, and it's even possible the underlying issue isn't database > corruption. Sure - I can wait. Thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: API timeout for one list

by Abhilash Raj

On Wed, Sep 23, 2020, at 6:33 AM, Seth Seeger wrote: > > > On Sep 22, 2020, at 4:30 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > On 9/22/20 12:45 PM, Seth Seeger wrote: > >> I apologize, because I think this was talked about before, but I could not find it in the archives. > >> > >> For one list, the REST API times out. Doesn’t seem to matter which page I try to go to. The uwsgi-error.log entry: > >> > > ... > >> The other lists work fine. > > > > This can happen on lists with lots of members. > > > > Try increasing the timeout. See <https://wiki.list.org/x/17892072> > > Thank you - that did solve my timeout problem. > > However, each page for this list takes between 40 and 80 seconds to > load. The list has 465 members, and it’s running (via Docker) on a 2 > core, 4 GB RAM Linode VM. I’ve watch htop during the load - one CPU > is around 20%, and the other hovers around 80%, mostly with the process > “runner”. > > Is there a way to optimize this list? There are no held messages, no > subscription requests, no templates. Are there any subscription requests pending confirmation from the User. If you go to Subscription Requests -> Pending Confirmation from list's admin page, you'll see the list there. In the past, I've noticed this caused a significant delay in every list page. This has since been fixed in the master branch, but yet to be released. > > The next biggest list has 438 members, and all those pages load very > quickly (0-2 seconds). I can’t figure out what the difference between > the two lists. > > Thanks, > Seth > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years, 2 months

[MM3-users] Re: EMWD/Affinity/Empathy in 2023

by Stephen J. Turnbull

Mark Sapiro writes: > I have had some contact [with EMWD], but not much. As far as I > know, they are still in business and offering list hosting > including Mailman 3 lists with Affinity and Empathy. They no longer > offer support for installation and maintenance of Mailman on other > people's servers. That exactly describes my experience. To jaboyib556, I recommend you contact them directly and make your own judgment. I do not know the current operators of EMWD, but I do know that the Carpenter family carefully vetted several bids. And their concentration on servers they run suggests they know what they're good at and have focus. I think they're a good bet, but only you can judge. > As far as I know, it was only EMWD that did this and for business > reasons, kept it proprietary. I corresponded with Brian about this.[1] He said that a third-party consultant (not sure if they're related to the current operators) built the Affinity and Empathy applications in PHP on a limited budget, and he felt that he needed to keep them proprietary as a temporary "no competition" measure until they could build up a nest egg to support on-going development. He said, and I have no reason to disbelieve him, that he thought it would take a year to build the reputation, another year to recoup the investment, and within that time frame he planned an open source release. I suspect he planned a Aladdin Ghostscript-like strategy: with the publication of release N, he would release N-1 as open source. He made no commitments, but I believe that was his aspiration. He was always a great supporter of Mailman, giving generously of his time and expertise to people on our lists including those hosting with other businesses. We miss him a lot. Footnotes: [1] On friendly terms: "hope for an open-source release" is not a matter of moral imperative with me, and I believe I speak for all Mailman developers on that.

2 years, 10 months

[MM3-users] Re: MTA setup

by Arte Chambers

Is the mailman lmtp runner a cron job? Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Tue, Dec 24, 2024 at 12:31 PM Arte Chambers <paul.m.robey(a)gmail.com> wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> > > > > ``` > $mailman qfile > /opt/mailman/mm/var/archives/hyperkitty/spool/1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck > [----- start pickle -----] > <----- start object 1 -----> > Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com > [209.85.208.182]) > by list.louisvillecommunitygrocery.com (Postfix) with ESMTPS id 3E36381ED2 > for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec 2024 > 17:02:48 +0000 (UTC) > Received: by mail-lj1-f182.google.com with SMTP id > 38308e7fff4ca-3003e203acaso44323081fa.1 > for <testing(a)list.louisvillecommunitygrocery.com>; Mon, 23 Dec > 2024 09:02:48 -0800 (PST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=gmail.com; s=20230601; t=1734973367; x=1735578167; darn= > list.louisvillecommunitygrocery.com; > h=cc:to:subject:message-id:date:from:in-reply-to:references > :mime-version:from:to:cc:subject:date:message-id:reply-to; > bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; > > b=SFr5MsvE4S5GUIy9pEuqDHdEW5nW16briFnXG6ARqjLiFgAX12TU5ozUgw5NCJobcx > > RQWkL64TyXv2C2CTKHjcBH26jiLo1p7h2edLXSBCmd374QbRYQPbv5yZb4jmwX5kfMzr > > fc/I3pSk6ruN/j+JPGLVxBJBreyLRDV+YL0rDJts83a8hcPHghGMkRTmi2Z1vLYgqThA > > 2fV/IYwrOe/q4c2+/AwlKQFUuClaxFN4AniNi++Hk7eql7q4ceDtURp1pHW/h4+8UXgJ > > 2DQ+zwPapOiU5POtfka1fAHTJgykuOoMCmO0YiwfP9p51lXmr4GmdFjFgDOiQwzhx8dH > vAEw== > X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > d=1e100.net; s=20230601; t=1734973367; x=1735578167; > h=cc:to:subject:message-id:date:from:in-reply-to:references > > :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id > :reply-to; > bh=s882asm7tHdBcEIXrLEFEIU3397InleNrytAF0sRzBA=; > > b=IwucO1D8XfIbWVT6dQ/LdKNsesrSsiekzj0khFI38CLd6WryQGJOQftxOLR5AvneNs > > 9gUbVvFAe0VENzTbMrelFr4H5DTI9HrKbNVYEbleeMrbuPypsTdtqWTrjizGhMQROhvs > > vOxl3T+UfRjDywLj9OuYBiWKTDIIaTpeQ7rR4u1lT8iMGTUre0V8kikm1BsFXwRRzl+U > > e0ghdIaZYN5kfu/bfR5veCCQhU0l0IF+DvoZzdJCgLkYgImIPhB/X7Zv0wQiUnKoebJo > > h1UFAEQIrVx2iMFHzLsHiqBhKHvJqG72PAa1bMiG0K3EsYvSJHu5zjrkTjoHXazAci4c > trXg== > X-Gm-Message-State: > AOJu0Yz8oZOnap/9jvXAOcFZnjYoReVHBQrfUnC9u6Mi6M2Ea7dkofrs > 4mAlHtOuQYGEyFxJZIOdFybTI20qdBoQBJAPF7FHL6d4mAGrLbPMgTZy3/hWFtmXfOo93a74CSu > YsRCZKH5ixK5jPHn4Vye0i/h0oilWXQ== > X-Gm-Gg: > ASbGncsYG3zr9300F+iwV6VLqHlMKoLuiS2mnT5tGiid8o6Ojd4JIrOBQI0BVNx1aeO > FVisNFC7AKewms0adY+Ug4HLKEtg8GwSIz0i32IOtPNA+tNxEAac47wHBGkcv+H2EfTOMsD/p > X-Google-Smtp-Source: > AGHT+IFNyfqXALTZ0zcO0GJZfpIf/4WT9IZ2EG3oThjt5aoZP3sdPhxjN2UOMTqwI2axiu9io1WSiFszsjxPLHtLIs8= > X-Received: by 2002:a05:6512:1190:b0:53e:37e4:1457 with SMTP id > 2adb3069b0e04-54229550e25mr4737922e87.33.1734973365282; Mon, 23 Dec 2024 > 09:02:45 -0800 (PST) > MIME-Version: 1.0 > References: < > 77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> > In-Reply-To: < > 77112962-9e9b-4692-bc81-05f1957fb823(a)smtp-relay.sendinblue.com> > From: Arte Chambers <paul.m.robey(a)gmail.com> > Date: Mon, 23 Dec 2024 12:02:08 -0500 > Message-ID: <CAM05vAepJnJQengX825dZ4E1PVVxeEgv4ogUcmifP9tqh1i= > mg(a)mail.gmail.com> > To: Arte Chambers <paul.m.robey(a)gmail.com> > Content-Type: multipart/alternative; > boundary="00000000000021f3da0629f2f7aa" > Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG > X-Message-ID-Hash: T3RQI2JNPUFO4WGGVSJTMYLTHPGOXOAG > X-MailFrom: paul.m.robey(a)gmail.com > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; > banned-address; emergency; member-moderation; nonmember-moderation; > administrivia; implicit-dest; max-recipients; max-size; news-moderation; > no-subject; digests; suspicious-header > CC: testing(a)list.louisvillecommunitygrocery.com > X-Mailman-Version: 3.3.10 > Precedence: list > Subject: [Testing] Re: test 12.23.24 11.57 > List-Id: For testing mailing list software < > testing.list.louisvillecommunitygrocery.com> > Archived-At: <> > List-Archive: <> > List-Help: <mailto:testing-request@list.louisvillecommunitygrocery.com > ?subject=help> > List-Owner: <mailto:testing-owner@list.louisvillecommunitygrocery.com> > List-Post: <mailto:testing@list.louisvillecommunitygrocery.com> > List-Subscribe: <mailto:testing-join@list.louisvillecommunitygrocery.com> > List-Unsubscribe: <mailto: > testing-leave(a)list.louisvillecommunitygrocery.com> > > --00000000000021f3da0629f2f7aa > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Thank you, > Paul 'Arte Chambers' Robey > 502-408-6922 > > > On Mon, Dec 23, 2024 at 2:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/23/24 09:01, Arte Chambers via Mailman-users wrote: >> > Output from mailman log after sending a test message to the list: >> > >> > Dec 23 16:52:23 2024 (684048) Traceback (most recent call last): >> > File >> > >> "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", >> > line 158, in _archive_message >> > url = self._send_message(mlist, msg) >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> > File >> > >> "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", >> > line 228, in _send_message >> > raise ValueError(result.text) >> > ValueError: >> > <!doctype html> >> > <html lang="en"> >> > <head> >> > <title>Bad Request (400)</title> >> > </head> >> > <body> >> > <h1>Bad Request (400)</h1><p></p> >> > </body> >> > </html> >> >> mailman_hyperkitty is sending the message to hyperkitty to be archived >> and receiving the 400 response. Presumably it has previously requested >> and received the list_url and the permalink to put in the message >> headers. This can be confirmed by the presence of List-Archive: and >> Archived-At: headers with values in the messages from the list. So the >> configuration seems to be correct to allow mailman_hyperkitty to >> communicate with hyperkitty. It is not clear why, but this code >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… >> is getting the ValueError. That can come from one of three places in >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming…. >> >> The lack of a Message-ID: is not it because Mailman's lmtp runner will >> add one. Most likely it is the non-ascii sender address from >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming… >> >> What do you get from >> ``` >> mailman qfile var/archives/hyperkitty/spool/xxx.pck >> ``` >> where xxx.pck is one of the (hopefully smaller) files. In particular, >> what is the From: header in that? >> >> -- >> 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/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to paul.m.robey(a)gmail.com >> >

11 months, 1 week

[MM3-users] Re: Problem with digests not being sent daily

by Mark

On 6/21/24 02:07, Mark wrote: >> ...The mmdf files don't exist in the list's directory although there >> have been many posts to the list throughout the day. On 2024-06-21 15:55, Mark Sapiro wrote: > Assuming your mailman/app/digests.py is unmodified, there is some race > condition. The code beginning at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > finds the file and size is > 0, but by the time it gets to > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/digests.py… > the file is gone. > > What other crons run at the same time? The digest.py file is out-of-the-box and unmodified. ls -la /opt/mailman/venv/lib/python3.11/site-packages/mailman/app/ ... -rw-r--r-- 1 mailman mailman 4642 Jan 30 08:06 digests.py The /var/log/cron.log shows the crons running at the same time as digest at 22:30 hours. # tail -f cron.log ... 2024-06-21T22:30:01.368407+00:00 deu CRON[3422196]: (root) CMD (sh /templates/mailman_custom_templates.sh > /dev/null) 2024-06-21T22:30:01.369050+00:00 deu CRON[3422197]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs quarter_hourly) 2024-06-21T22:30:01.371586+00:00 deu CRON[3422198]: (mailman) CMD (/opt/mailman/venv/bin/mailman notify) 2024-06-21T22:30:01.371878+00:00 deu CRON[3422199]: (mailman) CMD (/opt/mailman/venv/bin/mailman digests --periodic) 2024-06-21T22:30:01.372190+00:00 deu CRON[3422202]: (mailman) CMD (/opt/mailman/venv/bin/mailman-web runjobs minutely) /////////////////////////////////////////////////////////////////////////////////////////////////////////////// The mailman crons are more or less out-of-the-box: MAILTO=imark(a)posteo.net 30 22 * * * /opt/mailman/venv/bin/mailman digests --periodic 30 22 * * * /opt/mailman/venv/bin/mailman notify #@daily /opt/mailman/venv/bin/mailman digests --periodic #@daily /opt/mailman/venv/bin/mailman notify # * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly # The root cron just runs a bash script every 5 minutes to copy custom templates from the mailman and mailmanweb databases and write them to files. ...

1 year, 5 months

[MM3-users] Re: ARC signing outgoing mails

by Wolfgang Bock

Hello, thanks for these hints. Now it works and outgoing mails from my lists are no longer greylisted. .... ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=xx.de ... .... ARC-Seal: i=1; s=dkim; d=xx.de .... Here my mailman.cfg (debian buster/dovecot/postfix/rspamd/mysql/mailman3) quote [ARC] enabled= yes selector= dkim privkey: /path/to/rspamd/dkim/{conf.ARC.domain}.{conf.ARC.selector}.key unquote The below mentioned hash should be deleted. In the above mentioned directory the dkim key-files are saved in following style [domain].[selector].key Regards Wolfgang Am 02.11.2019 um 01:19 schrieb Mark Sapiro: > On 11/1/19 4:04 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> in >> https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/arc_sign… >> I found this hint >> >> "It is highly recommended that Mailman maintainers configure ARC siging >> of their outgoing email. ..." >> >> So I added in my mailman.cfg: >> " >> [ARC] >> privkey: /path/to/private.key >> " >> >> >> But I don't understand the meaning of >> >> >> "... and located at: >> " >> #{config.ARC.selector}._domainkeys.#{config.ARC.domain} –ex.– >> test._domainkeys.example.com >> " > This doesn't seem correct. The DNS TXT record should be added to > #{config.ARC.selector}._domainkey.#{config.ARC.domain} (note _domainkey, > not _domainkeys) > > I.e., this is a normal DNS TXT record containing the public key for DKIM > signing. > >> Where can I find this string or where do I have to place it. I am using >> bind9 as dns-handler. > > Read the entire ARC section beginning at > <https://gitlab.com/mailman/mailman/blob/master/src/mailman/config/schema.cf…>. > You have to configure more than just privkey. > > Once you have configured > > enabled: yes > privkey: /some/location/yourprivatekey.pem > selector: test (or whatever you want) > domain: your_domain.com > > The substitutions for #{config.ARC.selector} and #{config.ARC.domain} > should be more clear. >

6 years

[MM3-users] Re: Connection lost during _handle_client()

by Alain D D Williams

On Wed, Nov 27, 2024 at 08:47:38PM -0800, Mark Sapiro wrote: > On 11/27/24 5:58 PM, Alain D D Williams wrote: > > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) connection lost > > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) Connection lost during _handle_client() > > > > I am concerned about the connection lost message above. > > > It is normal and not a concern. > > > > Mailman sees it, the message ID matches that at the end of the first line > > in the exim log (above): > > /var/log/mailman3/mailman.log > > Nov 28 00:59:45 2024 (1268377) ACCEPT: <Z0fAe9xODd2y33N8(a)phcomp.co.uk> > > > So Mailman got the message and accepted it. > > > > Is there any more logging that I can look-at/switch-on to see what is happening ? > > Is there anything else in mailman.log? Does the message get archived? > Is there anthing in any of Mailman's var/queue/* directories? /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck The process doing this is a 'qrunner' I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) Yes: the mail list is chat(a)bray.phcomp.co.uk /var/lib/mailman3/queue/shunt/ contains 4 .pck files. > Is Mailman core running? Systemctl says so & ps shows me one 'master', several 'runner' & 2 uwsgi > Does `mailman members --nomail enabled` list any members? Yes: it gives the list that I expect. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year

[MM3-users] Re: Auth question

by David Krantz

On Sat, Apr 1, 2017 at 6:36 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > No, I'm using Django 1.9.9. I suppose that means it will quit working if > I upgrade to Django 1.10. > > So, I updated my urls to > > url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), > > and updated the attached files at > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. Very good. That will be helpful. Now everything works for me except the archiver. There I get strange errors where it requires authentication. I _have_ set MAILMAN_ARCHIVER_KEY (in production.py) and api_key in mailman_hyperkitty.conf to the same value within single quotes. This is probably something extremely silly that my jetlagged brain cannot see. [mailman.log] Apr 09 19:10:42 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:44 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:44 2017 (14388) HyperKitty failure on https://example.com/archives/api/mailman/urls: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:45 2017 (14383) HyperKitty failure on https://example.com/archives/api/mailman/archive: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> (401) Apr 09 19:10:45 2017 (14383) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> Apr 09 19:10:45 2017 (14383) Traceback (most recent call last): File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages/mailman_hyperkitty-1.0.2-py3.4.egg/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html> No big deal for me currently, but as I have an archiver I must find out either how to activate it or how to completely remove it. I like having the option, for some kinds of lists archives are useful. Cheers // David

8 years, 7 months

[MM3-users] Re: Bottom line of message footer

by Brian Carpenter

On 2/14/21 9:05 PM, Mark Sapiro wrote: > On 2/14/21 5:40 PM, Tom Stoddard wrote: >> Here's another question that I have. A regular message just came into my >> email from one of the lists I'm a member of and it had a 3 line footer. >> The first two lines are fine, they just include the list's email address >> and an address to send unsubscribe requests to. The third line is this: >> >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> It looks to me like it should be a link to the group's list info page. >> Is this a bug or is there something I can do to fix it? It looks like it >> might be missing a forward slash after the first "s". > This is a list whose msg_footer was imported by The Mailman 3 process > that imports Mailman 2.1 lists. This import process will recognize the > default msg_footer and not create a list specific template for it, but > other things in the footer result in a list specific template which > needs to be reviewed for issues like this. > > The way for you to fix it is to create a list:member:regular:footer (and > maybe a list:member:digest:footer) template in your web UI which will > then override the existing list specific template. The available > replacements are listed at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. > In templates they are all $ strings, e.g. $name. The %(name)s > replacements are Mailman 2.1 and won't work. Also, there is no > replacement for web_page_url because Mailman Core doesn't know what that > is, so you have to include the actual 'https://.../' value if you want > to include a web link. Thank you Mark. @Tom the templates you want to modify to add a Mailman 3 footer to replace the above are: Regular Message Footer Digest Footer -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 9 months

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

See, that's the oddness. There appears to be SOME weird mail loop here where $ORIGIN (MS365/Exchange) hands it once, then there's back-and-forth between SMTPPROXY and Mailman. IT's really odd how it behaves, and I have no explanation for it. Right now I'm away from the office where this happens, but when I'm back there I'll grab logs from both sides. Thomas On 12/5/23 17:54, Mark Sapiro wrote: > On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >> We use a multi-hop SMTP system to go from the inside of our network >> out to the Internet at the domain test.lists.example.com. >> >> The setup is this way for ingress: >> >> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >> Connector) -> Mailman for delivery to listserv >> >> Egress is this: >> >> Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET >> >> -- >> >> When a message is sent an invalid list (we'll call it >> invalid(a)test.lists.example.com) we end up with a nasty side effect in >> the system. The "no such recipient" response gets sent to the >> smtpproxy machine and then *it gets redelivered back to Mailman* as a >> redelivery as if it isn't accepting a permanent-failure condition code. > > > I don't understand why this is happening. Whatever MTA is seeing the > "no such recipient" status and creating the response DSN should be > sending it to the envelope sender of the original message so it should > not be sent to the invalid mailman address. Is one of the MTAs in the > delivery chain to Mailman rewriting the envelope sender? > > What are the MTA log messages from all the MTAs whos logs you have > access to? >

1 year, 11 months

Search results for query "sapiro"