[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Reply to Author != Reply to Author ?
From:       Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2009-10-18 18:48:08
Message-ID: 200910182048.09328 () thufir ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 12 October 2009, Daniel Black wrote:
> On Monday 12 October 2009 08:40:37 Martin Koller wrote:
> > On Sunday 11 October 2009 22:12:14 Martin Koller wrote:
> > > On Sunday 04 October 2009 23:26:20 Ingo Klöcker wrote:
> > > > "Reply" tries to guess the replier's intention. If KMail
> > > > identifies the message to be a mailing list message, then it
> > > > will do a "Reply to List".
> > >
> > > according to https://bugs.kde.org/show_bug.cgi?id=109069
> > > this seems to be something users do not like.
> > > (Ingo, you have already set another issue as a dup of this one,
> > > so I assume you agree on this beahavior being incorrect, right?)
> > >
> > > I suggest the following patch, which removes the check for a
> > > mailinglist header on a smart-reply:
> >
> > A discussion with Thomas McGuire resulted in keeping the way as it
> > is now,
>
> good

Exactly. Not keeping it would lead to thousands of misdirected replies. 
Due to all those mailing lists setting a Reply-to the user cannot 
expect that using Reply will send the reply to the sender. Therefore 
it's much better to make using Reply for mailing list messages send the 
reply to the mailing list even if Reply-to is not set.


> >  as there are broken mailing list servers, which do not set the
> > Reply-To headers
>
> Its debatable whether this is a 'broken' behaviour.

This behavior isn't broken at all. Setting (or rewriting it in case the 
sender did already set it) the Reply-to header is broken behavior. I 
have explicitly disabled this broken behavior for the kdepim-users 
mailing list.

Mailing lists started to use this broken behavior because of all those 
stupid mail clients that do not handle mailing list messages in a sane 
way.


> There is confusion and mail list developers acknowledge this. The
> beginning of a clarifying standard has just begun.
>
> Please take a read:
> http://mail.python.org/pipermail/mailman-users/2009-October/067391.ht
>ml
>
> follow-ups on the proposal to mailman-users@python.org as requested.

Let's see what comes out of it.


Regards,
Ingo

["signature.asc" (application/pgp-signature)]

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]