Re: dash Debian package - RC bugs
- To: email@example.com
- Subject: Re: dash Debian package - RC bugs
- From: Gerrit Pape <firstname.lastname@example.org>
- Date: Tue, 31 Aug 2010 12:08:39 +0000
- Message-id: <[🔎] email@example.com>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <20100430062857.GC6029@rivendell>
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <20100429171528.GO16821@decadent.org.uk> <firstname.lastname@example.org> <20100429192328.GB3883@rivendell> <email@example.com> <20100430062857.GC6029@rivendell>
On Fri, Apr 30, 2010 at 08:28:57AM +0200, Raphael Hertzog wrote:
> [ It sucks to have to confirm mails for firstname.lastname@example.org ]
I can't help, I don't understand. I yesterday followed up to a mail
that was additionally addressed to the <email@example.com>
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'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 firstname.lastname@example.org works. And for
subscribers, mail is delivered immediately. You didn't subscribe.
With the <email@example.com> 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.