Hello, Thank you for your reply. Here are a few relevant header lines from the automatic reply to the confirm-mail. From: "...-bounces@..." <...-bounces@...> Subject: The results of your email commands Thread-Topic: The results of your email commands Thread-Index: AQHcDbcweN2u9TaeIUuaSKMeW/w4cg== List-Help: <mailto:...-request@...?subject=help> List-Subscribe: <mailto:...-join@...> List-Unsubscribe: <mailto:...-leave@...> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64
This response was generated by Mailman itself. The original email with the “confirm” was sent by Outlook/Exchange. There are only Postfix servers between Exchange and Mailman. From: "..." <...@...> To: "'...-request@...'" <...-request@...> Subject: AW: confirm a041af0edea02cb5abddbd13573cabf9f4e37d6e Thread-Topic: confirm a041af0edea02cb5abddbd13573cabf9f4e37d6e Thread-Index: AQHcDbqe99uAxf3J10mtfFl3lR2QmbRjXzkA The end user has not set a preferred language; the list was sometimes in English and sometimes in German. Our Docker-based Mailman installation (maxking/mailman-web and maxking/mailman-core 0.5.2) does not include its own Postfix. The coupling of the server's Postfix with Mailman works as described in https://asynchronous.in/docker-mailman/#setting-up-your-mta. There is nothing interesting in the log files in the Mailman container. “mailman.log” only contains accesses to the web interface, while “smtp.log” shows that the confirmation email has arrived: Aug 15 08:19:45 2025 (30) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 15 08:19:45 2025 (30) Peer: ('172.19.199.1', 41378) Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) handling connection Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) >> b'LHLO ...' Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) >> b'MAIL FROM:<...> SIZE=2941 BODY=7BIT' Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) sender: ... Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) >> b'RCPT TO:<...-request@...>' Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) recip: ...-request@... Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) >> b'DATA' Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) >> b'QUIT' Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) connection lost Aug 15 08:19:45 2025 (30) ('172.19.199.1', 41378) Connection lost during _handle_client() Aug 15 08:19:47 2025 (31) <175524598592.28.16365298611951392309@mailman-core> smtp to ...@... for 1 recips, completed in 0.008934497833251953 seconds Aug 15 08:19:47 2025 (31) <175524598592.28.16365298611951392309@mailman-core> post to ...@... from ...-request@..., 1634 bytes Aug 15 08:19:47 2025 (31) <175524598592.28.3372336952020627757@mailman-core> smtp to ...@... for 1 recips, completed in 0.005883455276489258 seconds Aug 15 08:19:47 2025 (31) <175524598592.28.3372336952020627757@mailman-core> post to ...@... from ...-bounces@..., 2493 bytes How can I enable further debugging? Then I could try to reproduce the problem. Thanks Frank Der LWL im Überblick: Der Landschaftsverband Westfalen-Lippe (LWL) arbeitet als Kommunalverband mit mehr als 20.000 Beschäftigten für die 8,4 Millionen Menschen in der Region. Der LWL betreibt 35 Förderschulen, 21 Krankenhäuser, 18 Museen, zwei Besucherzentren und ist einer der größten deutschen Hilfezahler für Menschen mit Behinderung. Er erfüllt damit Aufgaben im sozialen Bereich, in der Behinderten- und Jugendhilfe, in der Psychiatrie und in der Kultur, die sinnvollerweise westfalenweit wahrgenommen werden. Ebenso engagiert er sich für eine inklusive Gesellschaft in allen Lebensbereichen. Die neun kreisfreien Städte und 18 Kreise in Westfalen-Lippe sind die Mitglieder des LWL. Sie tragen und finanzieren den Landschaftsverband, dessen Aufgaben ein Parlament mit 125 Mitgliedern aus den westfälischen Kommunen gestaltet. Der LWL auf Facebook: http://www.facebook.com/LWL2.0 _______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@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/UIYQH7AFBPODAT3DIQARBPZZKLA6DFRL/ This message sent to arch...@mail-archive.com
