Bug 191986 - timed email sending kmail
Summary: timed email sending kmail
Status: RESOLVED DUPLICATE of bug 50255
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-08 02:52 UTC by christian
Modified: 2010-02-27 16:40 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description christian 2009-05-08 02:52:21 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

My wish :

Implement timed email sending in kmail - if you send an email you can add a time when the email will be sent out...

usages: you are coding @ night and dont want to show that you did your work @ 3:00 in the night and it will send out on 8:00 when the office opens
Comment 1 Jaime Torres 2009-05-14 12:44:38 UTC 
Possibly related to bug 174885 (@comment 5)
Comment 2 ancow 2010-01-18 01:44:44 UTC 
This feature would also be nice for "happy birthday" or similar e-mails if you want to write them ahead of time (for whatever reason) and have them sent later without risking to forget sending them.

(In reply to comment #1)
> Possibly related to bug 174885 (@comment 5)

This is neither related to that wish, nor does that wish have a fith comment...
Comment 3 Björn Ruberg 2010-02-27 00:46:17 UTC 
*** Bug 50255 has been marked as a duplicate of this bug. ***
Comment 4 Tristan Miller 2010-02-27 16:08:29 UTC 
This was wrongly marked as a duplicate of a much older (and much more voted-for) bug, Bug 50255.  It should have been the other way around.
Comment 5 Tristan Miller 2010-02-27 16:10:41 UTC 
Sorry, I meant to say that the older bug was wrongly marked as a duplicate of this one, whereas it should have been vice versa.
Comment 6 Björn Ruberg 2010-02-27 16:40:45 UTC 

*** This bug has been marked as a duplicate of bug 50255 ***