Re: dash Debian package - RC bugs
Gerrit Pape writes ("Re: dash Debian package - RC bugs"):
> I can't help, I don't understand. I yesterday followed up to a mail
> that was additionally addressed to the <firstname.lastname@example.org>
> mailing list and got an automatic reply telling me that the mail cannot
> be delivered because I'm not subscribed. Not a bounce, but an automatic
> reply to the address in the From: header, not the envelope sender
> address. How do you call this?
I would call it a "bounce".
> I'd be happy if it would've been a delivery notification giving me the
> opportunity to easily confirm the mail to have it finally delivered,
> and, as a bonus, all subsequent mails I send, without subscribing.
> That's how the email@example.com works. And for
> subscribers, mail is delivered immediately. You didn't subscribe.
I don't know whether (a) lists.debian.org supports this and
(b) whether in practice it works well for addresses which attract a
lot of spam. If so it would be worth looking into changing the TC
list configuration IMO.
> With the <firstname.lastname@example.org> mailing list, I now need to
> guess whether the From: address needs to be subscribed or the envelope
> sender address, subscribe with that address, re-send the message, losing
> information about the cross-posting, and maybe do the same again if I
> guessed the address wrong. I don't do that.
Well, we appreciate the problem and are sorry for the inconvenience.
But TC members tend to get the mails in their main inbox to try to
treat them as important, and so a good level of spamfiltering is
needed. Sorry that this tradeoff has inconvenienced you.
(TC member, but not writing officially on behalf of the TC)