unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Subject: Re: About "Undelivered Mail Returned to Sender" when trying to respond to debbugs issues
Date: Tue, 19 Nov 2024 16:50:15 +0000	[thread overview]
Message-ID: <84D990DB-6A68-45DC-B10E-C468DB60988C@tobias.gr> (raw)
In-Reply-To: <7905a97f-c347-48e5-b4a9-cede2b446b03@posteo.de>

Hi Zephir,

On 19 November 2024 11:27:51 UTC, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
>I am guessing that debbugs does not support TLS

Somewhat to my surprise, this is indeed the case!

GNU Debbugs uses/is its own MX without STARTTLS support.  Other gnu.org {,sub}domains such as this list use eggs.gnu.org, which supports TLS just fine.

We (Guix) aren't responsible for any of the debbugs infra so it's not something we can change directly.  One could try asking <owner at debbugs dot gnu dot org> or, if that fails, <sysadmin at gnu dot org>.

> and that I have somewhere configured to always send via TLS and then posteo tells me, that the target mail server does not support it.
>
>Correct?
>
>Or is it the Posteo server that demands TLS and debbugs does not offer it?

Well, both really.  You've asked (or defaulted) Posteo to deliver only over TLS.  See <https://posteo.de/en/help/activating-tls-sending-guarantee>.

I've never myself used Posteo, so I hope that's the cause.


Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.


      reply	other threads:[~2024-11-19 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241119011601.7810E1A00D2@mout01.posteo.de>
2024-11-19 11:27 ` About "Undelivered Mail Returned to Sender" when trying to respond to debbugs issues Zelphir Kaltstahl
2024-11-19 16:50   ` Tobias Geerinckx-Rice [this message]

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=84D990DB-6A68-45DC-B10E-C468DB60988C@tobias.gr \
    --to=me@tobias.gr \
    --cc=guix-devel@gnu.org \
    --cc=zelphirkaltstahl@posteo.de \
    /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).