: When others click "Reply" on their mail clients do they see it going to dev@?
if i was right baout #3, then i am in the exact same situation as you, and i se the exact same thing i just described. most list messages have the Reply-To header set, and hitting reply goes to the list -- but if i send the original message, or if the message was CC'ed directly to me, then gmail only keeps one copy of it and hitting reply may not go to the list (when i sent it - never has Reply-To header; if someone else, like jenkins, sent it and i was CC'ed on it: then it is entirely dependent on which copy got deleviered ot gmail first) (of course, i have my mail clinet configured to default to Reply-To-All, so i neer really notice) : : On Thu, Sep 4, 2014 at 12:09 PM, Chris Hostetter : <[email protected]> wrote: : > : > : BTW, Uwe, how come the reply-to for these failures is : > : [email protected]? It almost bit me ... (i.e. I must remember to do : > : "reply all" not just "reply"). : > : > Are you sure that's not a quirk of your client? : > : > : > 0) the normal Reply-To 'list' header is added by ezmlm (documented) : > : > 1) as recent committer the mail was CC'ed directly to you by jenkins : > (observed) : : Hmm I suspect Uwe's Jenkins instance sends the email directly to : whoever had committed a recent change for this build; this is why it : was sent directly to me. : : (Apache's Jenkins instance doesn't seem to do this). : : > 2) you use gmail as your MTA (suspected) : : Yes, I use the gmail web ui. : : > 3) you recieved 2 copies of the email, one direct from jenkins and one via : > the mailing list (implied by #1) : > : > 4) gmail ignores dup messages, even if they've been modified by a mailing : > list and/or you sent the original message (documented) : > : > 5) gmail got the direct mail first, which didn't have the Reply-To set by : > the list. (conclusion drawn from #3 + #4) : : OK I think this explanation makes sense! : : So if you had committed before a build that failed then be extra : careful to reply-all! : : Thanks for explaining it Hoss, : : Mike McCandless : : http://blog.mikemccandless.com : : --------------------------------------------------------------------- : To unsubscribe, e-mail: [email protected] : For additional commands, e-mail: [email protected] : : -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
