(*** This bug was imported into bugs.kde.org ***) Package: kmail Version: 1.2 (using KDE 2.1.0 ) Severity: normal Installed from: compiled sources Compiler: gcc version 2.95.2 19991024 (release) OS: Linux 2.4.2 i686 OS/Compiler notes: Hello All the kmail has got a little problem to my mind. Let's write 1 mail and send it later. Let's write 1 mail and send it now. Both mail have been sent .... The send now button of the send dialog sends all mail in outbox not only the one that made the menu popped. Steff (Submitted via bugs.kde.org) (Called from KBugReport dialog)
On Monday 19 March 2001 21:02 s.nicolas@videotron.ca wrote: > Package: kmail > Version: 1.2 (using KDE 2.1.0 ) > Severity: normal > Installed from: compiled sources > Compiler: gcc version 2.95.2 19991024 (release) > OS: Linux 2.4.2 i686 > OS/Compiler notes: > > Hello All > > the kmail has got a little problem to my mind. > Let's write 1 mail and send it later. > Let's write 1 mail and send it now. > Both mail have been sent .... > > The send now button of the send dialog sends all mail in outbox not only > the one that made the menu popped. Yes I can confirm this. However it might be best to use the "drafts" folder if you don't want things sent right away. The idea of "send it later" is for people who are writing emails before they connect to the internet to send. That way they can all be queued up in the outbox and sent as soon as the network connection is established. -- George Staikos
I agree with George use of the drafts folder is a sensible method of completing this task. Don. On Tuesday 20 March 2001 04:07 George Staikos wrote: > On Monday 19 March 2001 21:02 s.nicolas@videotron.ca wrote: > > Package: kmail > > Version: 1.2 (using KDE 2.1.0 ) > > Severity: normal > > Installed from: compiled sources > > Compiler: gcc version 2.95.2 19991024 > > (release) OS: Linux 2.4.2 i686 > > OS/Compiler notes: > > > > Hello All > > > > the kmail has got a little problem to my mind. > > Let's write 1 mail and send it later. > > Let's write 1 mail and send it now. > > Both mail have been sent .... > > > > The send now button of the send dialog sends all mail > > in outbox not only the one that made the menu popped. > > Yes I can confirm this. However it might be best to > use the "drafts" folder if you don't want things sent > right away. The idea of "send it later" is for people who > are writing emails before they connect to the internet to > send. That way they can all be queued up in the outbox > and sent as soon as the network connection is > established.
Was asked to reopen this.
George, if you think this is a bug then mark it as one. As long as this is just a wish we'll most likely ignore it (It's just one of currently 690 (!) wishes.) especially because it was yourself who told the original reporter what he should do.
*** Bug 72629 has been marked as a duplicate of this bug. ***
IM(humble)O ths 'bug' should be marked INVALID and closed: the described behaviour is nothing else than the desired behaviour. The "send later" just is /not/ a replacement for the Drafts folder but just a little convenience method to avoid the "Could not send." complaint when you were not online when pressing the send button. Just my 2 pence.
Subject: Re: "send now" causes all email in outbox to be sent > IM(humble)O ths 'bug' should be marked INVALID and closed: the described > behaviour is nothing else than the desired behaviour. I disagree, and also this should be marked BUG, not wishlist. For a very simple reason: a button should do the obvious thing. Think about it. When you press "send now" in a window containing *only* a single mail, is it obvious that all pending mails will be sent? No, it's not. The main kmail window might even be minimized or something. Very non-obvious. If a 3d modeler had a "save" button, would it be obvious that that button also started rendering your scene? No. And then it's the "oh yeah, I should change that last mail before I send it. I'll do it right after I send this one,.. nooooooo!!" - --------- typedef struct me_s { char name[] = { "Thomas Habets" }; char email[] = { "thomas@habets.pp.se" }; char kernel[] = { "Linux 2.4" }; char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt" }; char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" }; char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" }; } me_t; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFABuKmKGrpCq1I6FQRAirYAJ9/iJOh173fyNeu7SlWV5/xPCvTSACggjeO PotYXOpWDDK/Dku9W1uqyLs= =PK61 -----END PGP SIGNATURE-----
Sorry I added a duplicate - checked the list but didn't see this. This is how we use kmail here (for many years, thanks!): 1) Drafts are drafts - i.e. work in progress, might be working on these on and off over a long time. 2) We use "send later" if we're going to be thoughtful - ever sent an email in haste and regretted it as soon as its gone? So "send later" and just quickly review your important emails before committing - especially useful if your co-ordinating a few people/messages. 3) Don't most distros install an SMTP server? Even on dialup while disconnected pressing "send" works as the mail is queued locally. I had no idea this was the reason for "send later". Reason I raised it: I clicked on an email link in a web page, kmail wasn't running, composer fired up and I sent the web page author a quick one-liner. When I next ran kmail the outbox was empty. Changing "send" to "send all" would help, especially on the composer "file" menu. Or is "save in drafts folder" meant to move all your outbox messages into drafts? ;)
*** Bug 35908 has been marked as a duplicate of this bug. ***
I agree with Paul Harris' comments. While reading various mailing lists, I like to queue my written messages until I am ready to flush the queue in case my response ends up being a duplicate later on in the thread, etc. Since these are completed messages I don't really consider them to be drafts. Rarely I will want to send a message immediately (e.g., I just committed some big patch and want to reply to it to send out a HEADSUP or some such) and it is very astonishing to have the send now button send everything. It is perhaps more astonishing to me as the previous MUA I used (xfmail) would only send the current message and not the entire queue when I did a 'send now'.
I agree with Paul Harris, John Baldwin and even with Thomas Habets: This wishlist item should be made a bug report. I learned it the hard way. Please spare other users the embarassing moments I had! How can one change the status? Or, better question perhaps, WHO can? George Staikos? Hans Pseudinger
The menu item in the main window has been changed ince. However in the composer there you still cannot see that all messages waiting in the outbox are sent as well if you gonna send the composed message.
I vote for being this a bug, too. I learned it the hard way, too. The button is called "Send later" not "Send when KMail thinks you have a network connection". I set Settings -> Configure KMail -> Accounts -> Sending -> Common Options: "Send messages in outbox folder" to "Never automatically". That made me think I have complete control over it when the email is sent. Nevertheless the email in outbox filder was sent when I sent another email (via "Send now"). I would be glad if that would be changed.
I agree this is a bug - this has annoyed me for years! :-) (That's a back-handed compliment - I've loved kmail enough to use it for years).
Hi I agree with the other guys. The button "send later" should simply "send later" when **you** want not "send later" when **kmail** wants (or think that there's connection). If I write a mail and click on the send button it means that I want to send <<that>> mail not all the others that are in the outbox folder. Stefano
I agree with complaints. This is a bug. It breaks the rule of the least surprise. The menu item in composer says "send _mail_" and it is placed in menu "_message_". Another thing, it is design flaw, a "subprogram" /and I think that composer is a subprogram/ should not be able to change the state of the main program /and in this case it does/. Composer should be able to send only THIS message -- now or later. That's it.
I agree with both points in comment #16. This is both a bug and a design flaw.
*** Bug 129044 has been marked as a duplicate of this bug. ***
Another vote for this being a bug and a design flaw! The implementation right now is just not straigtforward. I was also surprised to see my whole outbox being sent. Luckily, it happened before I was pre-writing an application e-mail last week. This would have been really embarrassing. The save to drafts button is not even a standard in Suse. You would have to search for it somewhere in the menu. Best solution would be a separate "send whole outbox" button and NOT let kmail send all messages in the outbox on startup.
I agree: or the behaviour will be corrected or (maybe better and easier) the string should be changed.
In my humble opinion this is not a bug, and should be marked as invalid. The best way to actually fix the OP problem, is to place another button next to Send Now/Later with the option Save to Draft. That new button should actually be in the next version
It is a bug in that there is an inconsistency about the menu entries and the shortcuts assigned to these entries. 1. In menu > File > Send Outbox, no shortcut assigned 2. In message editor > Message > Send now, we have the shortcut Ctrl+Enter However, Ctrl+Enter in message editor triggers Send Outbox (as in 1.) but not Send Message (as in 2., mark it does not say "Send Message_s_"). And, Ctrl+Enter, which apparently is about sending the outbox, does not work, when there is no active message editor open. I am not happy with the present behaviour, but if you do not want to change this, at least change the menu entries so that they correspond with what will happen if you use them.
*** Bug 121735 has been marked as a duplicate of this bug. ***
Works as expected in KMail2. the message to send later remains in the outbox.