Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.project > #13468

Re: Lack of replies

From Daniel Gröber <dxld@darkboxed.org>
Newsgroups linux.debian.project
Subject Re: Lack of replies
Date 2024-01-04 16:00 +0100
Message-ID <HSxmp-KZ5-1@gated-at.bofh.it> (permalink)
References <HSd4l-xZ2-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi Scott,

On Wed, Jan 03, 2024 at 05:10:43PM +0000, Scott Kitterman wrote:
> >At least people could be warned that because of the domain they send
> >from their mail might not get through.
> >
> My guess is that such a warning email (which is the only way we'd have to
> do it) would also cause a lot of complaints.  

> I think we [...] will need to have the BTS send all emails from
> bugs.debian.org role addresses and not use the sender's email in From
> anymore.

Just to make sure I understand the constraints: we can determine at sending
time whether a particular domain is going to cause trouble or not, right?
If so could this rewrite scheme be applied only for recipients where it's
absolutely necessary?

That way DDs, who are likeley to care more about their BTS email workflow
than the average user, don't have to deal with the negative consequences of
the address rewriting if they're already behind a polite mailserver.

Further if this discrimination is possible I wonder if it might not also be
possible to accomodate the subset of BTS users who are behind broken mail
providers but use sensible mail clients (mutt and such).

Specifically I think when you embedd an message/rfc822 part mutt allows me
to autoview the message inline, see the (pretty set) of headers, and reply
to this message instead of the "envelope".

So when BTS sees a broken domain it could generate the usual message with
address rewriting applied, but also attach in an multipart/alternative the
untouched version for this set of users to use.

Not sure that all works out, just a crazy idea,
--Daniel

Back to linux.debian.project | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Lack of replies Steven Robbins <steve@sumost.ca> - 2023-12-29 23:50 +0100
  Re: Lack of replies Andrey Rakhmatullin <wrar@wrar.name> - 2023-12-30 11:00 +0100
  Re: Lack of replies Steven Robbins <steve@sumost.ca> - 2024-01-02 19:40 +0100
    Re: Lack of replies Scott Kitterman <debian@kitterman.com> - 2024-01-02 20:30 +0100
      Re: Lack of replies Sam Hartman <hartmans@debian.org> - 2024-01-03 04:10 +0100
        Re: Lack of replies Scott Kitterman <debian@kitterman.com> - 2024-01-03 18:20 +0100
          Re: Lack of replies Colin Watson <cjwatson@debian.org> - 2024-01-03 19:40 +0100
          Re: Lack of replies Daniel Gröber <dxld@darkboxed.org> - 2024-01-04 16:00 +0100
            Re: Lack of replies Scott Kitterman <debian@kitterman.com> - 2024-01-04 16:20 +0100
            Re: Lack of replies Jeremy Stanley <fungi@yuggoth.org> - 2024-01-04 16:20 +0100
              Re: Lack of replies Daniel Gröber <dxld@darkboxed.org> - 2024-01-04 17:00 +0100
                Re: Lack of replies Jeremy Stanley <fungi@yuggoth.org> - 2024-01-04 17:30 +0100
                Re: Lack of replies Colin Watson <cjwatson@debian.org> - 2024-01-04 18:10 +0100
            Re: Lack of replies Colin Watson <cjwatson@debian.org> - 2024-01-04 16:30 +0100
              Re: Lack of replies Scott Kitterman <debian@kitterman.com> - 2024-01-04 17:00 +0100
      Re: Lack of replies Michael Neuffer <neuffer@neuffer.com> - 2024-01-03 06:10 +0100
        Re: Lack of replies Scott Kitterman <debian@kitterman.com> - 2024-01-03 18:10 +0100

csiph-web