Bug 290886

Summary:	kmail2/composer: Add field for 'In-Reply-To'
Product:	[Applications] kmail2	Reporter:	Johannes Obermayr <johannesobermayr>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist	CC:	arthur, montel, winter
Priority:	NOR
Version:	Git (master)
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Johannes Obermayr 2012-01-07 15:07:29 UTC

Version:           Git (master) (using Devel) 
OS:                Linux

Because there are some issues related to In-Reply-To when opening an 'mailto:' URL in web browsers (e.g. Bug 141552) there should be an option in composer to input it manually.

Reproducible: Always

Steps to Reproduce:
...


Expected Results:  
...

Comment 1 zless 2013-02-03 20:36:00 UTC

This is fixed in KDE 4.10.

Comment 2 Allen Winter 2013-02-03 22:07:47 UTC

thanks for the feedback.
resolving then

Comment 3 Johannes Obermayr 2013-02-03 22:40:24 UTC

It has not been fixed because <Menu noMerge="1" name="view" > or any other menu does not contain a <Action name="show_inreplyto" /> or sth. similiar:
http://quickgit.kde.org/?p=kdepim.git&a=blob&f=kmail/kmcomposerui.rc

<Action name="show_reply_to" /> is meant to show the receiver to which email address should be responded.

Comment 4 Laurent Montel 2013-02-04 06:41:22 UTC

 <Menu noMerge="1" name="view" >
   <text>&amp;View</text>
   <Action name="show_all_fields" />
   <Separator/>
   <Action name="show_identity" />
   <Action name="show_dictionary" />
   <Action name="show_fcc" />
   <Action name="show_transport" />
   <Separator/>
   <Action name="show_from" />
   <Action name="show_reply_to" />

So there is this entry no ?

Comment 5 Johannes Obermayr 2013-02-04 15:20:37 UTC

(In reply to comment #4)
>    <Action name="show_reply_to" />
> 
> So there is this entry no ?

No. There is no entry: see last line of comment #3 ...

in_reply_to is the unique message id which is used to follow a thread ...

Comment 6 Laurent Montel 2013-02-04 15:30:07 UTC

screenshot please.
For me it works.

Comment 7 Laurent Montel 2013-02-04 15:30:20 UTC

what is your kmail version ?

Comment 8 Johannes Obermayr 2013-02-04 16:06:32 UTC

I don't need a screenshot for it. Current git master:

http://quickgit.kde.org/?p=kdepim.git&a=blob&f=kmail/kmcomposewin.cpp:
  mEdtReplyTo = new MessageComposer::ComposerLineEdit( true, mHeadersArea );
  mEdtReplyTo->setObjectName( "replyToLine" );
  mEdtReplyTo->setRecentAddressConfig( MessageComposer::MessageComposerSettings::self()->config() );
  mEdtReplyTo->setToolTip( i18n( "Set the \"Reply-To:\" email address for this message" ) );

I assume we are speaking about different things ...

I want to specify a "In-Reply-To:" (note: 'In-' prefix) to tell which mail ID is predecessor of the mail I am writing and build up a new message in a thread this way - not to tell the recipient to which email address to answer (your assumption).

If you open mail header you see it in sth. like:
Message-ID: <bug-290886-118838-J2QOT9E3bX@http.bugs.kde.org/>
In-Reply-To: <bug-290886-118838@http.bugs.kde.org/>

If I am answerring to this mail: In-Reply-To = Message-ID 
Message-ID: <new_Message-ID>
In-Reply-To: <bug-290886-118838-J2QOT9E3bX@http.bugs.kde.org/>

If you can really input/change my requested 'In-Reply-To:' please provide a screenshot. I cannot find it on git master.

Comment 9 Laurent Montel 2013-02-04 16:44:27 UTC

Ah "in-reply-to"!
But who customize it ?
it's an advanced feature no ?
I didn't see a mailer which allows to customize it.

Comment 10 Johannes Obermayr 2013-02-04 17:39:40 UTC

(In reply to comment #9)
> Ah "in-reply-to"!
> But who customize it ?

I want to do it sometimes:
Mailing list example:
1. Person A -> Person B, mailing list
2. Person B -> Person A
3. Person A -> Person B, mailing list (new thread starts on mailing list because 2. is not there)

> it's an advanced feature no ?
> I didn't see a mailer which allows to customize it.

Comment 11 Laurent Montel 2013-10-03 07:51:32 UTC

For me it's an advanced feature for expert user.
Will not implement it.