Re: Help with hacking Nautilus



On Mon, 2007-10-22 at 00:43 +0200, Bogdan Butnaru wrote:
> On 10/21/07, Karsten Br�elmann <guenther rudersport de> wrote:
> > Bogdan, please keep list posts on the list.
> 
> Sorry, I was just hitting reply

No problem. Someone just had to point it out. :)

> and I didn't notice that the reply-to
> address was set to the user instead of the list. Is that normal?

No. And in fact, that has not been done either. ;)  The Reply-To header
simply is *not* set (neither added, nor changed) by the mailing list
server.

> Shouldn't the mailing list be reconfigured to set the reply-to address
> to itself rather than the poster? Or is there a setting I'm missing?

You're opening a can of worms here. Don't do this. ;)  It's a flame-bait
for religious discussions...


IMHO, not setting (forcing) a Reply-To header is correct behavior. Every
half-decent MUA offers (plain) Reply as well as Reply To List and To
All. This way, it is up to you to post your reply to the list and
contribute to the public discussion -- or, if there is a need for it,
reply to the sender.

Anyway, you'll find that almost all gnome.org mailing lists [1] do not
touch the Reply-To header. As do most lists I am subscribed to. However,
you will also find lists that do set this header, trying to enforce a
reply-to-list policy. As is, you will always have to carefully check
yourself, which replying method is appropriate for a particular list.


Just for a quick explanation of the topic. Hope it helps.

(Please, folks, no flame wars, no discussion to change this. This is how
it has been handled on gnome.org for years, and I don't expect this to
change anytime, no matter how much oil one might try to throw on the
fire... ;)

  guenther


[1] except for some rare, moderated announce lists

-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]