Bug 257828 - Urgent functionality not implemented
Summary: Urgent functionality not implemented
Status: CLOSED NOT A BUG
Alias: None
Product: KMail Mobile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-24 22:08 UTC by Sabine Faure
Modified: 2010-12-05 21:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Faure 2010-11-24 22:08:23 UTC
Version:           unspecified (using Devel) 
OS:                Linux

Whether the user activates the 'Urgent' functionality or not does not seem to make any difference so I am guessing that this functionality is not implemented yet.

Reproducible: Always

Steps to Reproduce:
- Launch Kmail-mobile
- Click on 'Write new email' button
- Enter a recipient, a subject and a few words in the text editor
- Open the 'Actions' tab
- Click on 'Options'
- Click on 'Urgent'
- Click on 'Send' button

Actual Results:  
When received the email looks exactly as any other emails. Nothing shows that
it is urgent.


Expected Results:  
An urgent email should be different visually from a regular one.



Note: 

- Click on the email once it has been received on the N900
- Open the 'Actions' tab
- Click on 'View'
- Click on 'Show Source'
- Scroll down

The Urgent header are properly set since the following lines can be read:
X-PRIORITY: 2 (High)
Priority: urgent

N900, 4:4.6~20101123.1199921-1maemo1.1199914
Comment 1 Tobias Koenig 2010-12-02 12:51:02 UTC
Hej Sabine,

the X-PRIORITY and Priority headers are an MS-Outlook only thing, which is not supported by KMail/KMail-Mobile at all, so you won't see any indicator.
This feature was just requested to let users with Kontact send "urgent" messages to users on Windows with Outlook, not the other way around :)

Ciao,
Tobias
Comment 2 Sabine Faure 2010-12-05 21:59:07 UTC
Hi Tobias!

Thx for the explanation ;o)

Since this is not a bug I am closing this report.

4:4.6~20101203.1203110-1maemo1.1202581