unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: 47980@debbugs.gnu.org
Subject: bug#47980: guix patches debuggs not supporting TLS?
Date: Fri, 23 Apr 2021 19:40:14 +0000	[thread overview]
Message-ID: <878e62c8-a2bf-9465-bb45-9f9fc86729ae@posteo.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

Hello Guix developers,

I am not sure, this is the correct list to write to about this.

When I send an e-mail to the guix bug list, the debbugs backend assigns a number
and so on. But whenever I reply to the debbugs address, I get an error:
"Undelivered Mail Returned to Sender" from my mail provider. The diagnostics
code is:

~~~~
Reporting-MTA: dns; mout02.posteo.de
X-Postfix-Queue-ID: ADDDE1A00BE
X-Postfix-Sender: rfc822; zelphirkaltstahl@posteo.de
Arrival-Date: Fri, 23 Apr 2021 21:32:12 +0200 (CEST)

Final-Recipient: rfc822; 47545@debbugs.gnu.org
Original-Recipient: rfc822;47545@debbugs.gnu.org
Action: failed
Status: 5.7.4
Diagnostic-Code: X-Postfix; TLS is required, but was not offered by host
    debbugs.gnu.org[209.51.188.43]
~~~~

To me it seems that guix bug initially offers TLS, but that the debbugs backend
somehow does not and since my e-mail client is set to always use TLS, the e-mail
cannot be properly sent. This makes it impossible to stick to debbugs threads
identified by the bug numbers.

Can anything be done to accept TLS there or is there some reasoning, for it
having to not be enabled? Or perhaps I am getting the error completely wrong and
it means something different?

Best regards,
Zelphir

-- 
repositories: https://notabug.org/ZelphirKaltstahl


[-- Attachment #2: Type: text/html, Size: 1934 bytes --]

             reply	other threads:[~2021-04-23 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 19:40 Zelphir Kaltstahl [this message]
2022-03-18  1:50 ` bug#47980: guix patches debuggs not supporting TLS? Maxim Cournoyer
2022-12-28 13:59 ` Elias

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878e62c8-a2bf-9465-bb45-9f9fc86729ae@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=47980@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).