-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Daniel Castro wrote: > Right! I figured this myself. > > Basically both XMPP accounts where using talk.google.com as the server, > but it could not handle two certificates for different account on the > same server. > So what I did was to use talk.google.com on my @gmail account and > talk.l.google.com on the other @tcd.ie account. > Both names resolve to the same server after DNS but for Pidgin they are > different servers. > This is a bug I think.
You are _not_ the only One experiencing this annoyance. I broached this last week and was re-directed to a bug report that wasn't very helpful and I'm not even sure was on topic. :-\ I use My Gmail Account on GTa;k and another Google Apps Account for that Organization. Ever since 'Upgrading' to 2.5.0 I am asked to 'Accept' the talk.google.com Certificate /every/ time connection is established. :( JOHN ;) Timestamp: Monday 25 Aug 2008, 18:24 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn4815: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: https://www.gswot.org Comment: Homepage: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJIszFIAAoJEBCGy9eAtCsPuHcH/jlYsHg/WQkcbgm/foq0o3li 7FlKOGWoBqr6ChLZNuHYt4IOHwahbWAnlbVpO4wOuUqIMSSf7elLl4j6jpjAlwKz H2P30IINZ9jxRsDAqUftHQPphdQ9e20AzFnm+it/fjO5HwhSb0bFGZ1kgJY7yd2L 4Whm7wj1vEx1vqH/UzjmEJeH7TICsVMgDa2St5DQYRMUkQjp5RuTuUHl8SWOC79M R4RiLhgp7ilTJbCfIglC39boWcBS1mH6Q6WZpbNyPnX3SA9JwrqJaUSnsN0JNsyG Z5UWADbJSYSgeJtlR/wG7pkFEcqnFY89Lutory0fkpI2J94qWl1lhfgHU5dYKQs= =hbm/ -----END PGP SIGNATURE----- _______________________________________________ Support mailing list [email protected] http://pidgin.im/cgi-bin/mailman/listinfo/support
