← Back to team overview

launchpad-dev team mailing list archive

Re: RFC: One True Way of addressing notification emails.

 

Thanks Graham for this explanation.

So given this, IMHO, I'd like to preserve the current genre of thinking of 
conversation (answers, code, bugs) as mailing list and such have comments be 
sent using the current form of From: Me <my.preferred.email@xxxxxxxxxxx>

Now, status changing and other such notifications are probably not 
conversation but should be thought as a status notification and as such should 
probably use a robot address (so bug@xxxxxxxxxxx is probably appropriate).

Now, what about the case where we batch changes together, we should probably 
inspire ourselves from mailing digest then. And that's probably a robot adress 
again.

But I'd really like that we keep using the poster email for comments, which 
makes sense given that those can be triggered by an email in the first place.

Cheers

-- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx

On June 11, 2010, Graham Binns wrote:
> On 11 June 2010 15:53, Francis J. Lacoste <francis.lacoste@xxxxxxxxxxxxx> 
wrote:
> > Can somebody explain me this address book crap?
> > 
> > Is it that some some address book software harvest emails automatically?
> > For example, if I have Graham Binns in my address book and there is
> > another Graham Binns emailing me with a different address, it will at
> > some point automatically add that different email to the record?
> > 
> > Am I the only one thinking such behavior is broken, or at least not
> > thought through properly. I can see that being useful in some cases, but
> > annoying in a lot of others.
> 
> Some MUAs (Gmail, Thunderbird, Mail.app, etc.) will automatically add
> an address to your addressbook whenever you email that address for the
> first time. If I look in my Gmail addressbook, for example, I can see
> several Bug $foos in there, because the Reply-to address for all bug
> mail is "Bug $foo <$foo@xxxxxxxxxxxxxxxxxx>".
> 
> We're not proposing to change the Reply-to header, however, so we're
> not going to end up with "Graham Binns <$foo@xxxxxxxxxxxxxxxxxx>"
> entries in peoples' address books (unless their MUA is very broken,
> and I'm inclined to not worry too much about such an edge case). The
> problem of the bug email addresses going in there is something you can
> do nothing about.
> 
> This functionality can be turned of in most cases, by the way. Or you
> can use Mutt, where it's never turned on in the first place. But
> remember, all mail clients suck; it's a basic specification of the
> application genre.

Attachment: signature.asc
Description: This is a digitally signed message part.


Follow ups

References