Bug 269893
| Summary: | freebsd-status-calls@: Undelivered Mail Returned to Sender | ||
|---|---|---|---|
| Product: | Services | Reporter: | Graham Perrin <grahamperrin> |
| Component: | Mailing Lists | Assignee: | postmaster |
| Status: | Closed FIXED | ||
| Severity: | Affects Some People | CC: | carlavilla, debdrup, pauamma, salvadore, status |
| Priority: | --- | ||
| Version: | unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Graham Perrin
2023-03-01 07:32:13 UTC
(In reply to Graham Perrin from comment #0) The issue here is that freebsd-status-calls@ did not receive the message at all: I received an "Undelivered Mail Returned to Sender" notice. I have already forwarded the notice to postmaster. I would like to remind that on the 15th of March the status team needs to send the first reminder fo status reports calls. Hence, it would be nice if the issue could be fixed before the 15th of March. Thanks. I also edit the bug report summary so that it better explains the problem. I confirm the problem is still there. I have managed to manually forward the two weeks left reminder to the list, but it was not to easy. It seems that the list is called freebsd-status-calls@, but is still active with a freebsd-quarterly-calls@ address only. I tried to forward the undelivered email to freebsd-quarterly-calls@ to see if it would work. I received a reply informing me that I was not subscribed to the list. I tried to subscribe through https://lists.freebsd.org/subscription/freebsd-status-calls and received a confirmation email from freebsd-status-calls@. The email was coming from freebsd-status-calls@ and asked me to confirm by sending an email to freebsd-status-calls+...@. I tried to do it but it failed. I retried by sending the confirmation email to freebsd-quarterly-calls+...@ with the same confirmation code and it worked. Then I tried sending the two weeks later reminder again to freebsd-quarterly-calls@: now it worked and indeed I received a moderation email. The email was coming from freebsd-status-calls+owner@. I was able to accept the email by sending a reply to freebsd-quarterly-calls+owner@ (I have not tried freebsd-status-calls+owner@). The message finally landed and is now visible in the archive. By the way, it seems that freebsd-current@, freebsd-stable@ and devsummit@ are also subscribed to the freebsd-status-calls@ list, but would not receive any email because they do not want any where they are not in the To: or CC: field. Since the sendcalls script sends email directly to those lists, it is not necessary to have them subscribed to freebsd-status-calls@ and they can be removed from there. Ping: we are approaching the month of June and we will need to send calls for status reports that month. It would be nice if it were possible to fix this bug within May. Thanks. This is now fixed. Thanks bapt@. Sorry, I was wrong, this is still broken.
Five days after the sending of the last call for status reports, I have received this:
This is the mail system at host mlmmj.nyi.freebsd.org.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<freebsd.org--status-calls@localhost.mlmmj> (expanded from
<freebsd-status-calls@mlmmj.nyi.freebsd.org>): mail transport unavailable
----------------------------------------------
message/delivery-status
----------------------------------------------
Reporting-MTA: dns; mlmmj.nyi.freebsd.org
X-Postfix-Queue-ID: 4SyLlX46v4z55BjC
X-Postfix-Sender: rfc822; salvadore@freebsd.org
Arrival-Date: Sun, 24 Dec 2023 00:00:40 +0000 (UTC)
Final-Recipient: rfc822; freebsd.org--status-calls@localhost.mlmmj
Original-Recipient: rfc822;freebsd-status-calls@FreeBSD.org
Action: failed
Status: 4.3.0
Diagnostic-Code: X-Postfix; mail transport unavailable
----------------------------------------------
message/rfc822
----------------------------------------------
Return-Path: <salvadore@freebsd.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SyLlX46v4z55BjC;
Sun, 24 Dec 2023 00:00:40 +0000 (UTC)
(envelope-from salvadore@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
client-signature RSA-PSS (4096 bits) client-digest SHA256)
(Client CN "freefall.freebsd.org", Issuer "R3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4SyLlX2RNpz3Ggy;
Sun, 24 Dec 2023 00:00:40 +0000 (UTC)
(envelope-from salvadore@freebsd.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim;
t=1703376040;
h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
to:to:cc:cc; bh=YF66Xbo7DtIymXgG7zxCiG7zwTK4LgD8DcJExWS2xFM=;
b=H+00VfV1kgB+UJDeqWSpOFGdPxVDx1c+y8KBsEMKfhqRhNa36DlkPP+oJN0rgC9+FCGyym
RqxEqN/Y5ghFVu9zWqtgd2QNEy1jfWAmBLEVNr5uMEtu2WrlI5GLsMI/cn8KtE13IFZ/Fn
jApy61BeTLgViHPw7SFlQOCLokfMtQ4wx4llwvogcZ/ucMuSrBmpSatES/EL8GcFGUa8Xh
T1yRxrSYTr0MQQgefwQ29XDwgiaWulltsB/ge+NYYBeBivwpGxtXjwSH4Yj5jUF5SGCvl0
X8VrezUxNs6UV46lM9mfGc0SAZXs5femTpqDuV3JzwgLQJYTYtpT0FV7LWHqzA==
ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1703376040; a=rsa-sha256; cv=none;
b=teltGR8XK+Df6THbcQ5wrtV6WCIjUSCKuysJn2nPWAJLmV9RS9cHdPzBFH25C5jJ1Md1bu
lU04cgI9+IgIHEmXfRUgXEV0mRK4uN8d/f1H0prJtfx+3WOHQgon33XYIjiE+QLiYb3pfP
j91Orpm+EZH9/OeZ+q4nG51xT4Tpt7xRYwcZ4OM0ny93ENnAoqHRnBqBOkvWy4OURcXkRi
ByXVqr3Xpas+YYfge9IWL0/ax928bOw0U0xKDdjWodH7o5JNUHDi7+7s7MHDfeDNkBcOBx
aitkT4x6IDN+EspFmMZTOHT9qjg/kr0ACEBw71Az5uOcpmF1Mk8+NPkHYdNOJg==
ARC-Authentication-Results: i=1;
mx1.freebsd.org;
none
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org;
s=dkim; t=1703376040;
h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
to:to:cc:cc; bh=YF66Xbo7DtIymXgG7zxCiG7zwTK4LgD8DcJExWS2xFM=;
b=syCpB7rFdIQdDDaILETX7N3R1+MuVJzaiggZyzcTZXBNlnOWELsORVp3ZEi76cn5UMdpuD
Oz4QY7mN5vL9bDODRPb1jlkdBegDwTvITPChc5Q8OFRjTjrUHYhNulb0QLIxN+ywRlO1fX
2kRiJy1ii6uDn7d0rhGGTaFLb21oX6cXMz1J+r8kwVmtrYqONMuRoyvByO4h+2wuJmxKoS
zbijX+yt0yc5pX0wAb1ehPv3bIcGc48DOiJcoG+7QGNfhsU6k72hcC5+ziHbKyxfH/d7jp
saHDQYdORNwfxa3tjjS8KvTC7YEer0NzRAN3qlr6OfVsGYy83BQhguxLHOqZiw==
Received: by freefall.freebsd.org (Postfix, from userid 1472)
id 07AE111D15; Sun, 24 Dec 2023 00:00:39 +0000 (UTC)
To: freebsd-status-calls@FreeBSD.org
Subject: [LAST OFFICIAL REMINDER] Call for 2023Q4 status reports
Cc: freebsd-current@FreeBSD.org,freebsd-hackers@FreeBSD.org,devsummit@FreeBSD.org
Message-Id: <20231224000040.07AE111D15@freefall.freebsd.org>
Date: Sun, 24 Dec 2023 00:00:39 +0000 (UTC)
From: Lorenzo Salvadore <salvadore@freebsd.org>
Another typo sorry, I hope it shoukd be fixed now I am sorry, but it seems this is still broken: I have tested resending the last call for status reports, and after more than 24 hours it has not reached freebsd-status-calls@ yet. https://lists.freebsd.org/archives/freebsd-status-calls/2023-December/ If it helps, (In reply to Lorenzo Salvadore from comment #7) > Final-Recipient: rfc822; freebsd.org--status-calls@localhost.mlmmj I see two possible typos: freebsd.org (should that be freebsd (without the .org)?) -- (should be a single - I guess) A postmap was missed after last typo fix |