Bug 63443

Summary:	warn on sending message to offline user
Product:	[Unmaintained] kopete	Reporter:	Dik Takken <kde>
Component:	Chat Window	Assignee:	Till Gerken <till.gerken>
Status:	RESOLVED WAITINGFORINFO
Severity:	wishlist	CC:	lamarque
Priority:	NOR
Version:	0.40.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Dik Takken 2003-08-30 00:39:26 UTC

Version:           0.7.1 (using KDE KDE 3.1.1)
Installed from:    Compiled From Sources
OS:          Linux

When I start to chat to an offline Jabber user, Kopete does not indicate that there is a problem. It just looks like the messages are sent successfully.

Comment 1 Till Gerken 2003-08-30 12:00:41 UTC

Jabber supports offline message relaying. This is actually a feature, not a 
bug. The messages will be delivered to their recipients by the server as soon 
as they go online.

Comment 2 Dik Takken 2003-08-30 16:15:35 UTC

Sorry, I didn't know that. Still, a warning dialog box saying "User currently offline, 
messages will be delivered when he/she logs on again" would be nice. With a "don't 
show again" check ofcourse :)

Comment 3 Till Gerken 2003-08-30 17:11:29 UTC

Agreed, reopening as wishlist item.

Comment 4 Till Gerken 2003-09-22 20:34:04 UTC

Since protocols have a canSendOffline() method, I am reassigning this wish to 
libkopete. libkopete should pop up a warning (configurable to not show up 
again) and probably an error for the protocols that can't send to offline 
contacts.

Comment 5 Nicolas L. 2005-08-23 16:27:35 UTC

we can close this wish as  in the windows there is the message    ( not connected )


WDYT ?

Comment 6 Dik Takken 2005-08-23 17:29:52 UTC

I don't think that message is obvious enough. I would prefer a dialog.

Comment 7 Duncan Mac-Vicar Prett 2005-10-21 01:09:12 UTC

but if you are messaging a offline contact, its because you are looking at the chatwindow in that moment, why a dialog?

Comment 8 Lamarque V. Souza 2011-03-18 00:31:05 UTC

This seems fixed in Kopete from KDE SC 4.6.1, can I close this bug?