unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully <bjc@spork.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Update to bug 54919 gone missing
Date: Sat, 16 Apr 2022 08:44:43 -0400	[thread overview]
Message-ID: <878rs519c9.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <07583DBD-CB88-4CE4-89DE-D1974817D105@tobias.gr>


Tobias Geerinckx-Rice <me@tobias.gr> writes:

> We don't have easy access to lower-level logs. Do you? You look like you might self-host.
>
> Armed with a log snippet from you with a clear 250 'accepted' I'd feel less bothersome asking the gnu.org folks to investigate.

	You know, I hadn’t even thought to check my mail queue. I can’t
remember the last time I had a delivery problem (or maybe I’ve been
having them the whole time and just not noticed 😉).

	I have my mail server set to require TLS, but it looks as though
debbugs.gnu.org doesn’t support it:

---[snip]---
Apr 16 08:26:10 mx0 postfix/smtp[68543]: 347053CCD: to=<54919@debbugs.gnu.org>, relay=debbugs.gnu.org[209.51.188.43]:25, delay=78497, delays=78497/0.06/0.27/0, dsn=4.7.4, status=deferred (TLS is required, but was not offered by host debbugs.gnu.org[209.51.188.43])
---[snip]---

	This wasn’t an issue for other reports, as I used the
bug-guix@gnu.org address, and eggs.gnu.org offers STARTTLS after the
EHLO.

	I’m not sure what to do here. I’m kind of loathe to remove the
TLS mandate on my server, and it seems to me like the debbugs MX should
offer it for all the standard reasons.

> Thanks for reporting both!

	Thanks for prodding me to dig further on my end. I honestly
thought the mail just disappeared.

-bjc


      reply	other threads:[~2022-04-16 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16 11:36 Update to bug 54919 gone missing Brian Cully
2022-04-16 12:16 ` Tobias Geerinckx-Rice
2022-04-16 12:44   ` Brian Cully [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=878rs519c9.fsf@ditto.jhoto.spork.org \
    --to=bjc@spork.org \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).