Page MenuHome GnuPG

mailing list address confusion (lists.gnupg.org shown, but does not work)
Closed, ResolvedPublic

Description

In several places the mailman software shows and responds with
@lists.gnupg.org email addresses, which do not work.

@gnupg.org works.

original report

Hello,

gcrypt-devel (at) lists.gnupg.org seems to be down/broken:

From: Mail Delivery System <Mailer-Daemon@lists.gnupg.org>
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1nGOiD-0005Xr-9w@lists.gnupg.org>
Date: Sat, 05 Feb 2022 18:19:01 +0100
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

gcrypt-devel@lists.gnupg.org
  Unrouteable address

[...]

Update 2021-02-08:
I am reopening since it seems to unfixed:
~~~
Received: from lists.gnupg.org ([217.69.76.57])

by vsrv21575.customer.vlinux.de with esmtps  (TLS1.2) tls
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
(Exim 4.95)
id 1nHUX6-008NZs-Lz
for xx@yy;
Tue, 08 Feb 2022 17:44:05 +0000

Received: from Debian-exim by lists.gnupg.org with local (Exim 4.84_2 #2

(Debian))
id 1nHUX6-000393-4H
for <xx@yy>; Tue, 08 Feb 2022 18:44:04 +0100

X-Failed-Recipients: gcrypt-devel@lists.gnupg.org
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@lists.gnupg.org>
To: xx@yy
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1nHUX6-000393-4H@lists.gnupg.org>
Date: Tue, 08 Feb 2022 18:44:04 +0100

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

gcrypt-devel@lists.gnupg.org
  Unrouteable address

~~~

cu Andreas

Event Timeline

werner claimed this task.
werner added a subscriber: werner.

disk full. Fixed. Thanks.

ametzler1 updated the task description. (Show Details)

Try gcrypt-devel@gnupg.org, i.e. without the lists subdomain.

Recently, the gnupg.org mailing list manager started to prepend the lists. subdomain to the List-Id (which caused my email filters to fail) and to everything else. Probably due to an accidentally changed configuration.

Try gcrypt-devel@gnupg.org, i.e. without the lists subdomain.

Recently, the gnupg.org mailing list manager started to prepend the lists. subdomain to the List-Id (which caused my email filters to fail) and to everything else. Probably due to an accidentally changed configuration.

I see. Not only List-Id but @lists is now the advertised address:
https://gnupg.org/ --> Documentation --> Mailinglists links to https://lists.gnupg.org/pipermail/gcrypt-devel/ and "more information about this list" yields gcrypt-devel@lists.gnupg.org as list address.

Actually is was/is a chain of bugs due to changing some URLs in confirmation mails from http to https.

This still seems to be a problem:

At 12:42:40 UTC+0100, I sent a subscription confirmation request to gcrypt-devel-request@lists.gnupg.org. At 12:58 UTC+1, GMail gave up trying to deliver this message:

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

 gcrypt-devel-request@lists.gnupg.org
   Unrouteable address

At 14:29:27 +0100, I tried sending a message to gcrypt-devel@lists.gnupg.org, which also failed with the same error message right away.
At 14:38:43 +0100, I re-sent this message to gcrypt-devel@gnupg.org as mentioned in this ticket, and while I did not yet receive a delivery failure notification, the message also hasn't shown up in the public archives, or my colleague's inbox.

The mails from these days still contain the following header:

List-Post: <mailto:gnupg-devel@lists.gnupg.org>

which is probably causing the mail client directing the mails to this address. Is there a way to change or or make it an alias so it is easier for people to use the mailing list without finding this issue?

it was noted that this also affects other ML hosted there like those of freie-software.org

My email to gnupg-devel@gnupg.org was accepted and is visible in the archives https://lists.gnupg.org/pipermail/gnupg-devel/2022-May/035063.html
Cool

I propose to correct the web page https://lists.gnupg.org/mailman/listinfo/gnupg-devel to update the mailing list address, i.e. remove the "lists." part from gnupg-devel@lists.gnupg.org.

bernhard renamed this task from gcrypt mailing list is down to mailing list address confusion (lists.gnupg.org shown, but does not work).Sep 5 2022, 4:24 PM
bernhard updated the task description. (Show Details)

@werner
Can you take a look at the host_name setting at the [General Options] configuration page for the lists in question,
e.g. https://lists.gnupg.org/mailman/admin/gnupg-devel

@werner also I suggest to check the default setting for this, see https://www.list.org/mailman-install/customizing.html and you can use the scripts mentioned there to check the configuration of several mailinglists at once and change it, if you know, which one is to blame, e.g. the host_name value.

Fixed for 3 lists. I can't remember the details but quite some time ago someone requested some changes and while applying them the host_name must have changed / I changed it. The problem with Mailman is that it does not use plain config files to keep under etckeeper. At least not with some effort.

bernhard changed the task status from Open to Testing.Sep 5 2022, 4:58 PM

https://lists.gnupg.org/mailman/listinfo/gnupg-devel has `To post a message to all the list members, send email to gnupg-devel@gnupg.org." now, which seems fine, it was wrong before.

https://lists.gnupg.org/mailman/listinfo/gcrypt-devel also seems fine.

https://lists.gnupg.org/mailman/listinfo/gnupg-users also fine.

Wating for feedback until we should close

Or better:

  • If it is was broken for you and works now, let us know here.
  • if "lists." still is there in email addresses somewhere, please also list.

Thanks!

bernhard added a comment.Mon, Sep 5, 6:05 PM

If it is was broken for you and works now, let us know here.
if "lists." still is there in email addresses somewhere, please also list.

Looks good to me now. - Thank you!

@ametzler1 thanks for the feedback!

A test post to gnupg-devel@ also looks fine (see below)
https://lists.gnupg.org/pipermail/gnupg-devel/2022-September/035113.html
thus closing the issue.

To: gnupg-devel@gnupg.org
Subject: [ML Admin] Test for Mailinglist
Date: Tue, 6 Sep 2022 14:19:58 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20141209.518c4af)
MIME-Version: 1.0
Message-Id: <202209061419.58523.bernhard@intevation.de>
X-BeenThere: gnupg-devel@gnupg.org
X-Mailman-Version: 2.1.35
Precedence: list
List-Id: GnuPG development <gnupg-devel.gnupg.org>
List-Unsubscribe: <https://lists.gnupg.org/mailman/options/gnupg-devel>,
 <mailto:gnupg-devel-request@gnupg.org?subject=unsubscribe>
List-Archive: <https://lists.gnupg.org/pipermail/gnupg-devel/>
List-Post: <mailto:gnupg-devel@gnupg.org>
List-Help: <mailto:gnupg-devel-request@gnupg.org?subject=help>
List-Subscribe: <https://lists.gnupg.org/mailman/listinfo/gnupg-devel>,
 <mailto:gnupg-devel-request@gnupg.org?subject=subscribe>

Errors-To: gnupg-devel-bounces@gnupg.org
Sender: "Gnupg-devel" <gnupg-devel-bounces@gnupg.org>