Le mercredi 30 avril 2008, Chani a écrit :
> > > > (In case you wonder, by default, there is no custom displayname. the
> > > > nickname is displayed instead but would not be taken in account for
> > > > metacontact merging. That mean that two guys with the name nick would
> > > > not be in the sam
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=161444
Summary: Kopete can't log into Yahoo, constantly asks for
password and captcha
> > > (In case you wonder, by default, there is no custom displayname. the
> > > nickname is displayed instead but would not be taken in account for
> > > metacontact merging. That mean that two guys with the name nick would
> > > not be in the same metacontact)
>
> What if two differents people a
Le April 29 2008 13:53:04 Olivier Goffart, vous avez écrit :
> I still have that pending patch for few weeks now.
>
> - It remove the (useless) warning before deleting the old empty metacontact
> when you move contact to another metacontacts.
> - It merge automatically contact with the same custom
I still have that pending patch for few weeks now.
- It remove the (useless) warning before deleting the old empty metacontact
when you move contact to another metacontacts.
- It merge automatically contact with the same custom display name (if set)
into the same metacontact
As this is a beha
Le mardi 29 avril 2008, Detlev Casanova a écrit :
> On Tuesday 29 April 2008 17:42:47 Matt Rogers wrote:
> > On Tuesday 29 April 2008 10:35:37 Peter Saint-Andre wrote:
> > > Recently we've had some troubles with support for the legacy SSL port
> > > (5223) at the jabber.org XMPP service. This has e
Le mardi 29 avril 2008, Matt Rogers a écrit :
> On Tuesday 29 April 2008 10:35:37 Peter Saint-Andre wrote:
> > Recently we've had some troubles with support for the legacy SSL port
> > (5223) at the jabber.org XMPP service. This has exposed the fact that
> > some IM clients (including Kopete) do no
Detlev Casanova wrote:
> On Tuesday 29 April 2008 17:42:47 Matt Rogers wrote:
>> On Tuesday 29 April 2008 10:35:37 Peter Saint-Andre wrote:
>>> Recently we've had some troubles with support for the legacy SSL port
>>> (5223) at the jabber.org XMPP service. This has exposed the fact that
>>> some IM
On Tuesday 29 April 2008 17:42:47 Matt Rogers wrote:
> On Tuesday 29 April 2008 10:35:37 Peter Saint-Andre wrote:
> > Recently we've had some troubles with support for the legacy SSL port
> > (5223) at the jabber.org XMPP service. This has exposed the fact that
> > some IM clients (including Kopete
On Tuesday 29 April 2008 10:35:37 Peter Saint-Andre wrote:
> Recently we've had some troubles with support for the legacy SSL port
> (5223) at the jabber.org XMPP service. This has exposed the fact that
> some IM clients (including Kopete) do not yet support the STARTTLS
> feature (upgrade of port
Recently we've had some troubles with support for the legacy SSL port
(5223) at the jabber.org XMPP service. This has exposed the fact that
some IM clients (including Kopete) do not yet support the STARTTLS
feature (upgrade of port 5222 to an encrypted connection) first defined
in RFC 3920 (publish
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=122936
--- Additional Comments From list schweb com ar 2008-04-29 14:43 ---
OK, so i must continue using AMSN. I t
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=122936
--- Additional Comments From aaronw net com 2008-04-29 10:53 ---
As of version 0.12.7 this still is not imp
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=160944
--- Additional Comments From vincent.rubiolo free fr 2008-04-29 09:56
---
I agree on what the patch should
14 matches
Mail list logo
