date:20170313

Re: AIM login

2017-03-13 Thread Adium

Just got a response from him this afternoon. Following up.

-Eric

Sent from my iPhone

> On Mar 13, 2017, at 4:38 PM, Robert Vehse  wrote:
> 
> Hi,
> 
> […]
> 
>> By the way, slogin.oscar.aol.com is down but login.oscar.aol.com isn't. I 
>> thought slogin.oscar.aol.com was supposed to die at the end of this month. I 
>> think that's breaking adium (mac OS X pidgin derivative) and we still 
>> haven't managed to contact their devs to fix it. So what is the fate of 
>> slogin supposed to be?
> 
> As far as I know Eric, Adium's Project Manager 
> (https://trac.adium.im/wiki/edr1084), has tried to contact Donald Le via 
> email on multiple occasions but hasn't received a response yet.
> 
> Regards,
> Robbie
> ___
> Devel mailing list
> de...@pidgin.im
> https://pidgin.im/cgi-bin/mailman/listinfo/devel

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

2017-03-13 Thread Robert Vehse

Hi,

[…]

> By the way, slogin.oscar.aol.com is down but login.oscar.aol.com isn't. I 
> thought slogin.oscar.aol.com was supposed to die at the end of this month. I 
> think that's breaking adium (mac OS X pidgin derivative) and we still haven't 
> managed to contact their devs to fix it. So what is the fate of slogin 
> supposed to be?

As far as I know Eric, Adium's Project Manager 
(https://trac.adium.im/wiki/edr1084), has tried to contact Donald Le via email 
on multiple occasions but hasn't received a response yet.

Regards,
Robbie
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: Pidgin acting strange

2017-03-13 Thread Shannon Mead


Eion,

Hi there, ok so yes Alex's computer is the one that we cannot get 
messages through. She does not appear on our buddies windows yet she can 
see us. I did notice in the debug windows that there are two errors 
appearing. I attached Alex-purple-debug for you to view. Also I attached 
the Working-purple so you could see the working message between two of 
the workstations that are not having issues.


Thank you so much for your help with this,

Shannon Mead
Production Dept.
West Valley View Inc.
sm...@westvalleyview.com
623-535-8439 ext. 170

On 3/13/2017 1:41 PM, Eion Robb wrote:

Hi again,

Thanks for the log.  :)

Is the Alex computer the one that's not seeing the messages? Can you 
also get a debug log of trying to send and receive a message from a 
computer that works and one that doesnt?


Cheers,
Eion

On 14 March 2017 at 09:18, Shannon Mead > wrote:


Eion,

Thank you so much for your email. I have attached the log with the
disable and re-enable of the bonjour account. I hope this helps. I
am honestly wondering if perhaps it is a bonjour issue. We used to
have an apple (mac) server and last year we integrated to a
windows server and upgraded all of our computers to Windows 10.

Thank you,

Shannon Mead
Production Dept.
West Valley View Inc.
sm...@westvalleyview.com 
623-535-8439 ext. 170

On 3/13/2017 12:28 PM, Eion Robb wrote:

Hi Shannon,

Unfortunately those logs weren't enough to work with.  Ideally we
need a captured log when you reconnect to the Bonjour account. 
The easiest way to do this is to open the debug window, then

disable and reenable the Bonjour account and then save the log to
file after that.

(Also, make sure to cc the support@ list so that others can help)

Cheers,
Eion

On 14 March 2017 at 07:32, Shannon Mead mailto:sm...@westvalleyview.com>> wrote:

Eion,

I apologize I sent you the wrong info we are all running in
the IPV4 not 6

thanks,

Shannon Mead
Production Dept.
West Valley View Inc.
sm...@westvalleyview.com 
623-535-8439 ext. 170

On 3/11/2017 12:25 AM, Eion Robb wrote:

Hi there,

Are there any other differences besides architecture?  
Like, are they on a different subnet, or using ipv6/4 when

the others arent?

Are you able to get a debug log from Pidgin (from the buddy
list, Help->Debug Window) as one of the failing computers
tries to connect to Bonjour?

Cheers,
Eion

On 11 March 2017 at 07:24, Shannon Mead
mailto:sm...@westvalleyview.com>>
wrote:

Good morning,

Our company uses pidgin in combination with bonjour to
provide inter office messaging. I have two computers out
of 30 that just will not work. The pidgin installs and
they can send messages but other workstations cannot see
them nor can they respond to them. These two computers
are running Windows 10 32 bit system. The other stations
are running Windows 10 64bit and have no issues with
Pidgin. Is this a bug or do we need to perhaps consider
updating our bonjour software?

Thank you,

-- 
Shannon Mead

Production Dept.
West Valley View Inc.
sm...@westvalleyview.com 
623-535-8439 ext. 170

___
Support@pidgin.im  mailing list
Want to unsubscribe? Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support











Pidgin Debug Log : 3/13/2017 2:14:44 PM
(14:14:25) util: Writing file prefs.xml to directory 
C:\Users\Alex\AppData\Roaming\.purple
(14:14:25) util: Writing file C:\Users\Alex\AppData\Roaming\.purple\prefs.xml
(14:14:25) gtkspell: Failed to setup GtkSpell: enchant error for language: en
(14:14:25) gtkconv: setting active conversation on toolbar 06580FC8
(14:14:25) gtkconv: setting active conversation on toolbar 06580FC8
(14:14:25) prefs: /pidgin/conversations/toolbar/wide changed, scheduling save.
(14:14:25) win32placement: Window RECT: L:610 R:966 T:120 B:569
(14:14:25) win32placement: Working Area RECT: L:0 R:1280 T:0 B:984
(14:14:25) gtkconv: setting active conversation on toolbar 06580FC8
(14:14:26) accels: saving accels to C:\Users\Alex\AppData\Roaming\.purple\accels
(14:14:31) util: Writing file blist.xml to directory 
C:\Users\Alex\AppData\Roaming\.purple
(14:14:31) util: Writing file C:\Users\Alex\AppData\Roaming\.purple\blist.xml
(14:14:31) util: Writing file prefs.xml to directory 
C:\Users\Alex\AppData

Re: Pidgin acting strange

2017-03-13 Thread Eion Robb

Hi again,

Thanks for the log.  :)

Is the Alex computer the one that's not seeing the messages?  Can you also
get a debug log of trying to send and receive a message from a computer
that works and one that doesnt?

Cheers,
Eion

On 14 March 2017 at 09:18, Shannon Mead  wrote:

> Eion,
>
> Thank you so much for your email. I have attached the log with the disable
> and re-enable of the bonjour account. I hope this helps. I am honestly
> wondering if perhaps it is a bonjour issue. We used to have an apple (mac)
> server and last year we integrated to a windows server and upgraded all of
> our computers to Windows 10.
>
> Thank you,
>
> Shannon Mead
> Production Dept.
> West Valley View inc.sm...@westvalleyview.com
> 623-535-8439 ext. 170
>
> On 3/13/2017 12:28 PM, Eion Robb wrote:
>
> Hi Shannon,
>
> Unfortunately those logs weren't enough to work with.  Ideally we need a
> captured log when you reconnect to the Bonjour account.  The easiest way to
> do this is to open the debug window, then disable and reenable the Bonjour
> account and then save the log to file after that.
>
> (Also, make sure to cc the support@ list so that others can help)
>
> Cheers,
> Eion
>
> On 14 March 2017 at 07:32, Shannon Mead  wrote:
>
>> Eion,
>>
>> I apologize I sent you the wrong info we are all running in the IPV4 not 6
>>
>> thanks,
>>
>> Shannon Mead
>> Production Dept.
>> West Valley View inc.sm...@westvalleyview.com
>> 623-535-8439 ext. 170
>>
>> On 3/11/2017 12:25 AM, Eion Robb wrote:
>>
>> Hi there,
>>
>> Are there any other differences besides architecture?   Like, are they on
>> a different subnet, or using ipv6/4 when the others arent?
>>
>> Are you able to get a debug log from Pidgin (from the buddy list,
>> Help->Debug Window) as one of the failing computers tries to connect to
>> Bonjour?
>>
>> Cheers,
>> Eion
>>
>> On 11 March 2017 at 07:24, Shannon Mead  wrote:
>>
>>> Good morning,
>>>
>>> Our company uses pidgin in combination with bonjour to provide inter
>>> office messaging. I have two computers out of 30 that just will not work.
>>> The pidgin installs and they can send messages but other workstations
>>> cannot see them nor can they respond to them. These two computers are
>>> running Windows 10 32 bit system. The other stations are running Windows 10
>>> 64bit and have no issues with Pidgin. Is this a bug or do we need to
>>> perhaps consider updating our bonjour software?
>>>
>>> Thank you,
>>>
>>> --
>>> Shannon Mead
>>> Production Dept.
>>> West Valley View Inc.
>>> sm...@westvalleyview.com
>>> 623-535-8439 ext. 170
>>>
>>> ___
>>> Support@pidgin.im mailing list
>>> Want to unsubscribe?  Use this link:
>>> https://pidgin.im/cgi-bin/mailman/listinfo/support
>>
>>
>>
>>
>
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: Pidgin acting strange

2017-03-13 Thread Shannon Mead


Eion,

Thank you so much for your email. I have attached the log with the 
disable and re-enable of the bonjour account. I hope this helps. I am 
honestly wondering if perhaps it is a bonjour issue. We used to have an 
apple (mac) server and last year we integrated to a windows server and 
upgraded all of our computers to Windows 10.


Thank you,

Shannon Mead
Production Dept.
West Valley View Inc.
sm...@westvalleyview.com
623-535-8439 ext. 170

On 3/13/2017 12:28 PM, Eion Robb wrote:

Hi Shannon,

Unfortunately those logs weren't enough to work with. Ideally we need 
a captured log when you reconnect to the Bonjour account.  The easiest 
way to do this is to open the debug window, then disable and reenable 
the Bonjour account and then save the log to file after that.


(Also, make sure to cc the support@ list so that others can help)

Cheers,
Eion

On 14 March 2017 at 07:32, Shannon Mead > wrote:


Eion,

I apologize I sent you the wrong info we are all running in the
IPV4 not 6

thanks,

Shannon Mead
Production Dept.
West Valley View Inc.
sm...@westvalleyview.com 
623-535-8439 ext. 170

On 3/11/2017 12:25 AM, Eion Robb wrote:

Hi there,

Are there any other differences besides architecture?   Like, are
they on a different subnet, or using ipv6/4 when the others arent?

Are you able to get a debug log from Pidgin (from the buddy list,
Help->Debug Window) as one of the failing computers tries to
connect to Bonjour?

Cheers,
Eion

On 11 March 2017 at 07:24, Shannon Mead mailto:sm...@westvalleyview.com>> wrote:

Good morning,

Our company uses pidgin in combination with bonjour to
provide inter office messaging. I have two computers out of
30 that just will not work. The pidgin installs and they can
send messages but other workstations cannot see them nor can
they respond to them. These two computers are running Windows
10 32 bit system. The other stations are running Windows 10
64bit and have no issues with Pidgin. Is this a bug or do we
need to perhaps consider updating our bonjour software?

Thank you,

-- 
Shannon Mead

Production Dept.
West Valley View Inc.
sm...@westvalleyview.com 
623-535-8439 ext. 170

___
Support@pidgin.im  mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support








Pidgin Debug Log : 3/13/2017 1:13:31 PM
(13:12:22) util: Writing file prefs.xml to directory 
C:\Users\Alex\AppData\Roaming\.purple
(13:12:22) util: Writing file C:\Users\Alex\AppData\Roaming\.purple\prefs.xml
(13:12:25) gtkutils: gdk_pixbuf_new_from_file() returned nothing for file : 
Failed to open file '': Invalid argument
(13:12:28) account: Disconnecting account Alex Trujillo (01DFED98)
(13:12:28) connection: Disconnecting connection 03AE3AF8
(13:12:28) connection: Destroying connection 03AE3AF8
(13:12:34) util: Writing file accounts.xml to directory 
C:\Users\Alex\AppData\Roaming\.purple
(13:12:34) util: Writing file C:\Users\Alex\AppData\Roaming\.purple\accounts.xml
(13:12:34) util: Writing file blist.xml to directory 
C:\Users\Alex\AppData\Roaming\.purple
(13:12:34) util: Writing file C:\Users\Alex\AppData\Roaming\.purple\blist.xml
(13:12:37) account: Connecting to account Alex Trujillo.
(13:12:37) connection: Connecting. gc = 09FD5AC8
(13:12:37) bonjour: Attempting to bind IPv6 socket to port 5298.
(13:12:37) bonjour: Bound IPv6 socket to port 5298.
(13:12:37) bonjour: Attempting to bind IPv4 socket to port 5298.
(13:12:37) bonjour: Bound IPv4 socket to port 5298.
(13:12:37) bonjour: Registering presence on port 5298
(13:12:37) bonjour: Received new record for 'Shannon Mead@SHANNONM' on iface 13 
(_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Plate Room@DOTTIFF' on iface 13 
(_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Julie Sargent-Helm@ADVERTISING-PC' 
on iface 13 (_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Rene Hartmann@RENE-PC' on iface 13 
(_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Erica Evans@SCHNEIDERW7B' on iface 
13 (_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Ron Sellmeyer@UF-PC' on iface 13 
(_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Glenn Gullickson@EDITORIAL001' on 
iface 13 (_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Shane McOwen@SHANE-PC' on iface 13 
(_presence._tcp., local.)
(13:12:37) bonjour: Received new record for 'Rachael Freireich@RACHAEL-PC' on 
iface 13 (_presence._tcp., local.)
(13:12:37) bonjour:

Re: Pidgin acting strange

2017-03-13 Thread Eion Robb

Hi Shannon,

Unfortunately those logs weren't enough to work with.  Ideally we need a
captured log when you reconnect to the Bonjour account.  The easiest way to
do this is to open the debug window, then disable and reenable the Bonjour
account and then save the log to file after that.

(Also, make sure to cc the support@ list so that others can help)

Cheers,
Eion

On 14 March 2017 at 07:32, Shannon Mead  wrote:

> Eion,
>
> I apologize I sent you the wrong info we are all running in the IPV4 not 6
>
> thanks,
>
> Shannon Mead
> Production Dept.
> West Valley View inc.sm...@westvalleyview.com
> 623-535-8439 ext. 170
>
> On 3/11/2017 12:25 AM, Eion Robb wrote:
>
> Hi there,
>
> Are there any other differences besides architecture?   Like, are they on
> a different subnet, or using ipv6/4 when the others arent?
>
> Are you able to get a debug log from Pidgin (from the buddy list,
> Help->Debug Window) as one of the failing computers tries to connect to
> Bonjour?
>
> Cheers,
> Eion
>
> On 11 March 2017 at 07:24, Shannon Mead  wrote:
>
>> Good morning,
>>
>> Our company uses pidgin in combination with bonjour to provide inter
>> office messaging. I have two computers out of 30 that just will not work.
>> The pidgin installs and they can send messages but other workstations
>> cannot see them nor can they respond to them. These two computers are
>> running Windows 10 32 bit system. The other stations are running Windows 10
>> 64bit and have no issues with Pidgin. Is this a bug or do we need to
>> perhaps consider updating our bonjour software?
>>
>> Thank you,
>>
>> --
>> Shannon Mead
>> Production Dept.
>> West Valley View Inc.
>> sm...@westvalleyview.com
>> 623-535-8439 ext. 170
>>
>> ___
>> Support@pidgin.im mailing list
>> Want to unsubscribe?  Use this link:
>> https://pidgin.im/cgi-bin/mailman/listinfo/support
>
>
>
>
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

2017-03-13 Thread dequis

Hi, can confirm that finch is fixed now, thank you!

That issue with pidgin 2.12.0 is really odd! I just tested both windows
installers (online and offline) and they seem fine. We did have one user
reporting a similar issue, but we couldn't reproduce it or explain it.

Please verify the version with buddy list -> help menu -> about, the first
line should say "Pidgin 2.12.0 (libpurple 2.12.0)" followed by "unknown".
Also, help menu -> plugin information should say 2.12.0 for the AIM plugin.
That kind of mixup is rare but who knows!

You can also enable extra debug by opening cmd.exe and doing "set
PURPLE_UNSAFE_DEBUG=1" before executing pidgin.

Then open help menu -> debug window and connect the account. This is what I
get:

[...]
> (12:27:52) certificate: Successfully verified certificate for
> api.screenname.aol.com
> (12:27:52) util: Request: 'POST /auth/clientLogin HTTP/1.0
> Connection: close
> Accept: */*
> Content-Type: application/x-www-form-urlencoded; charset=UTF-8
> Content-Length: 85
>
> devId=do1UCeb5gNqxB1S1&f=xml&pwd=[password]&s=dx%40dxzone.com.ar'
> (12:27:53) util: Response headers: 'HTTP/1.1 200 OK
> [...]
> (12:27:53) util: requested to fetch (
> https://api.oscar.aol.com/aim/startOSCARSession?a=[access
> token]&distId=1715&f=xml&k=do1UCeb5gNqxB1S1&ts=1489418868&useTLS=1&sig_sha256=[signature]),
> full=1, user_agent=((null)), http11=0
>

So as far as I can see everything is fine. I hope that helps narrow it down.

By the way, is the message supposed to be shown on every login from a
legacy auth method? I don't see it when I intentionally set pidgin to
connect to "login.oscar.aol.com" with "don't use encryption" and
"MD5-based" - it just succeeds without complaining.

By the way, slogin.oscar.aol.com is down but login.oscar.aol.com isn't. I
thought slogin.oscar.aol.com was supposed to die at the end of this month.
I think that's breaking adium (mac OS X pidgin derivative) and we still
haven't managed to contact their devs to fix it. So what is the fate of
slogin supposed to be?

Thanks.

On 13 March 2017 at 09:38, Donald Le  wrote:

> Hi again,
>
> I download Pidgin 2.12.0 and test login.
>
> The "new" distID and devID were not used, and I received the upgrade
> message.
> The client is still on the old distID and NO devID.
> Could you double-check?
>
> LSI: PLOT  4224.   150210.172.189.32   Mon Mar 13 08:02:11 2017  
> bos_srv-l014bMon Mar 13 08:20:19 2017 bos_srv-l014b
> LSI: PLOT  4224.   150210.172.189.32   Mon Mar 13 07:43:23 2017  
> bos_srv-l014bMon Mar 13 07:49:22 2017 bos_srv-l014b
>
>
> Thanks,
>
>
> *Donald Le*
> *Product Management and Support AIM Platform*
> *O*: 703-265-5645 | *M*: 703-678-1073
> *AIM*: donald...@teamaol.com
> *AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*
>
> On Mon, Mar 13, 2017 at 7:33 AM, Donald Le  wrote:
>
>> Hi,
>>
>>
>> *The third said in the original email "No usage since August 2014 so no
>> need new DistID and DevID", which is clearly wrong. There's also that
>> "another libpurple" with distid 1502 which doesn't match any client we own,
>> and we don't know how you found that one.*
>> I can't explain but you did the right thing to use 1718 for Finch.
>>
>>
>> *Did the 1718 distid get invalidated? Can you re-enable it so that we
>> don't have to make another release?*
>> Please try again now and let me know, I correct a typo in the devID just
>> now.
>>
>> Thanks,
>>
>>
>> *Donald Le*
>> *Product Management and Support AIM Platform*
>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>> <%28703%29%20678-1073>
>> *AIM*: donald...@teamaol.com
>> *AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*
>>
>> On Sun, Mar 12, 2017 at 1:25 PM, dequis  wrote:
>>
>>> Hey Donald!
>>>
>>> As you may have heard we already released pidgin 2.12.0 (together with
>>> libpurple and finch 2.12.0), updating the distid/devids.
>>>
>>> Here's what we used:
>>>
>>> Pidgin:
>>> Distid: 1715
>>> Devid: do1UCeb5gNqxB1S1
>>>
>>> Libpurple:
>>> Distid: 1717
>>> Devid: ma19CwYN9i9Mw5nY
>>>
>>> Finch:
>>> Distid: 1718
>>> Devid: ma18nmEklXMR7Cj_
>>>
>>> The first two are normal.
>>>
>>> The third said in the original email "No usage since August 2014 so no
>>> need new DistID and DevID", which is clearly wrong. There's also that
>>> "another libpurple" with distid 1502 which doesn't match any client we own,
>>> and we don't know how you found that one.
>>>
>>> So for the sake of avoiding a roundtrip in our communication and getting
>>> the release packaged ASAP, we went ahead and used the remaining 1718 distid
>>> for finch.
>>>
>>> This looks like it was a mistake, since we're now getting "Method not
>>> allowed - clientLogin Not Allowed for this devId" errors in finch.
>>>
>>> Did the 1718 distid get invalidated? Can you re-enable it so that we
>>> don't have to make another release?
>>>
>>> Thanks
>>>
>>> On 27 January 2017 at 01:54, Donald Le  wrote:
>>>
 All,

 My comments are inline.

 Thanks,


>>

Re: AIM login

2017-03-13 Thread Donald Le

Hi again,

I download Pidgin 2.12.0 and test login.

The "new" distID and devID were not used, and I received the upgrade
message.
The client is still on the old distID and NO devID.
Could you double-check?

LSI: PLOT  4224.   150210.172.189.32   Mon Mar 13 08:02:11
2017  bos_srv-l014bMon Mar 13 08:20:19 2017 bos_srv-l014b
LSI: PLOT  4224.   150210.172.189.32   Mon Mar 13 07:43:23
2017  bos_srv-l014bMon Mar 13 07:49:22 2017 bos_srv-l014b


Thanks,


*Donald Le*
*Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*

On Mon, Mar 13, 2017 at 7:33 AM, Donald Le  wrote:

> Hi,
>
>
> *The third said in the original email "No usage since August 2014 so no
> need new DistID and DevID", which is clearly wrong. There's also that
> "another libpurple" with distid 1502 which doesn't match any client we own,
> and we don't know how you found that one.*
> I can't explain but you did the right thing to use 1718 for Finch.
>
>
> *Did the 1718 distid get invalidated? Can you re-enable it so that we
> don't have to make another release?*
> Please try again now and let me know, I correct a typo in the devID just
> now.
>
> Thanks,
>
>
> *Donald Le*
> *Product Management and Support AIM Platform*
> *O*: 703-265-5645 <(703)%20265-5645> | *M*: 703-678-1073
> <(703)%20678-1073>
> *AIM*: donald...@teamaol.com
> *AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*
>
> On Sun, Mar 12, 2017 at 1:25 PM, dequis  wrote:
>
>> Hey Donald!
>>
>> As you may have heard we already released pidgin 2.12.0 (together with
>> libpurple and finch 2.12.0), updating the distid/devids.
>>
>> Here's what we used:
>>
>> Pidgin:
>> Distid: 1715
>> Devid: do1UCeb5gNqxB1S1
>>
>> Libpurple:
>> Distid: 1717
>> Devid: ma19CwYN9i9Mw5nY
>>
>> Finch:
>> Distid: 1718
>> Devid: ma18nmEklXMR7Cj_
>>
>> The first two are normal.
>>
>> The third said in the original email "No usage since August 2014 so no
>> need new DistID and DevID", which is clearly wrong. There's also that
>> "another libpurple" with distid 1502 which doesn't match any client we own,
>> and we don't know how you found that one.
>>
>> So for the sake of avoiding a roundtrip in our communication and getting
>> the release packaged ASAP, we went ahead and used the remaining 1718 distid
>> for finch.
>>
>> This looks like it was a mistake, since we're now getting "Method not
>> allowed - clientLogin Not Allowed for this devId" errors in finch.
>>
>> Did the 1718 distid get invalidated? Can you re-enable it so that we
>> don't have to make another release?
>>
>> Thanks
>>
>> On 27 January 2017 at 01:54, Donald Le  wrote:
>>
>>> All,
>>>
>>> My comments are inline.
>>>
>>> Thanks,
>>>
>>>
>>> *Donald Le*
>>> *Tech Director | Product Management and Support AIM Platform*
>>> *O*: 703-265-5645 <(703)%20265-5645> | *M*: 703-678-1073
>>> <(703)%20678-1073>
>>> *AIM*: donald...@teamaol.com
>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>
>>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le 
>>> wrote:
>>>
 All,

 Quick update: we had to delay AIM client upgrade due to other
 integration, the date is tbd.
 I will answer your questions in the coming weeks.


 Thanks,


 *Donald Le*
 *Tech Director | Product Management and Support AIM Platform*
 *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
 <%28703%29%20678-1073>
 *AIM*: donald...@teamaol.com
 *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166

 On Fri, Oct 14, 2016 at 2:58 AM, dequis  wrote:

> Hi, I have a couple of questions, since there may have been a
> misunderstanding here.
>
> Pidgin currently supports three auth methods for AIM:
>
> - MD5 using slogin.oscar.aol.com. Uses the DistID, does not use the
> DevID
>

>>>  All DistID used for login.oscar.aol.com and
>>> slogin.oscar.aol.com will be blocked. The date is tbd and AIM client
>>> upgrade will start Feb 24th 2017.
>>>

> - clientLogin aka OpenAuth using
> api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
> been the default setting for pidgin releases since 2009
>

>>>  This login path will stay but you need to update the DistID and
>>> DevID. We will give you a new set.
>>>

> - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced in
> pidgin 2.11.0, released four months ago.
>

>>>  Same as above with OpenAuth.
>>>

> If I'm understanding this right, the first method is being
> discontinued and the other two will continue working. It's possible a
> lot of users are using that - the account setting is a bit too
> visible, so users might just switch to it for the sake of changing
> settings. But as far as I can see, pidgin with the default
> configuration won't stop working.
>

>>>  If Pidgin uses DistID = 1502 or 0, the log

Re: AIM login

2017-03-13 Thread Donald Le

Hi,


*The third said in the original email "No usage since August 2014 so no
need new DistID and DevID", which is clearly wrong. There's also that
"another libpurple" with distid 1502 which doesn't match any client we own,
and we don't know how you found that one.*
I can't explain but you did the right thing to use 1718 for Finch.


*Did the 1718 distid get invalidated? Can you re-enable it so that we don't
have to make another release?*
Please try again now and let me know, I correct a typo in the devID just
now.

Thanks,


*Donald Le*
*Product Management and Support AIM Platform*
*O*: 703-265-5645 | *M*: 703-678-1073
*AIM*: donald...@teamaol.com
*AOL Inc**. 22070 Broderick Drive Dulles, VA 20166*

On Sun, Mar 12, 2017 at 1:25 PM, dequis  wrote:

> Hey Donald!
>
> As you may have heard we already released pidgin 2.12.0 (together with
> libpurple and finch 2.12.0), updating the distid/devids.
>
> Here's what we used:
>
> Pidgin:
> Distid: 1715
> Devid: do1UCeb5gNqxB1S1
>
> Libpurple:
> Distid: 1717
> Devid: ma19CwYN9i9Mw5nY
>
> Finch:
> Distid: 1718
> Devid: ma18nmEklXMR7Cj_
>
> The first two are normal.
>
> The third said in the original email "No usage since August 2014 so no
> need new DistID and DevID", which is clearly wrong. There's also that
> "another libpurple" with distid 1502 which doesn't match any client we own,
> and we don't know how you found that one.
>
> So for the sake of avoiding a roundtrip in our communication and getting
> the release packaged ASAP, we went ahead and used the remaining 1718 distid
> for finch.
>
> This looks like it was a mistake, since we're now getting "Method not
> allowed - clientLogin Not Allowed for this devId" errors in finch.
>
> Did the 1718 distid get invalidated? Can you re-enable it so that we don't
> have to make another release?
>
> Thanks
>
> On 27 January 2017 at 01:54, Donald Le  wrote:
>
>> All,
>>
>> My comments are inline.
>>
>> Thanks,
>>
>>
>> *Donald Le*
>> *Tech Director | Product Management and Support AIM Platform*
>> *O*: 703-265-5645 <(703)%20265-5645> | *M*: 703-678-1073
>> <(703)%20678-1073>
>> *AIM*: donald...@teamaol.com
>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>
>> On Thu, Oct 27, 2016 at 8:45 AM, Donald Le  wrote:
>>
>>> All,
>>>
>>> Quick update: we had to delay AIM client upgrade due to other
>>> integration, the date is tbd.
>>> I will answer your questions in the coming weeks.
>>>
>>>
>>> Thanks,
>>>
>>>
>>> *Donald Le*
>>> *Tech Director | Product Management and Support AIM Platform*
>>> *O*: 703-265-5645 <%28703%29%20265-5645> | *M*: 703-678-1073
>>> <%28703%29%20678-1073>
>>> *AIM*: donald...@teamaol.com
>>> *AOL Inc*. 22070 Broderick Drive Dulles, VA 20166
>>>
>>> On Fri, Oct 14, 2016 at 2:58 AM, dequis  wrote:
>>>
 Hi, I have a couple of questions, since there may have been a
 misunderstanding here.

 Pidgin currently supports three auth methods for AIM:

 - MD5 using slogin.oscar.aol.com. Uses the DistID, does not use the
 DevID

>>>
>>  All DistID used for login.oscar.aol.com and slogin.oscar.aol.com
>> will be blocked. The date is tbd and AIM client upgrade will start Feb 24th
>> 2017.
>>
>>>
 - clientLogin aka OpenAuth using
 api.screenname.aol.com/auth/clientLogin. Uses DistID and DevID. Has
 been the default setting for pidgin releases since 2009

>>>
>>  This login path will stay but you need to update the DistID and
>> DevID. We will give you a new set.
>>
>>>
 - Kerberos using kdc.uas.aol.com. Uses DistID and DevID. Introduced in
 pidgin 2.11.0, released four months ago.

>>>
>>  Same as above with OpenAuth.
>>
>>>
 If I'm understanding this right, the first method is being
 discontinued and the other two will continue working. It's possible a
 lot of users are using that - the account setting is a bit too
 visible, so users might just switch to it for the sake of changing
 settings. But as far as I can see, pidgin with the default
 configuration won't stop working.

>>>
>>  If Pidgin uses DistID = 1502 or 0, the login will be blocked.
>>
>>>
 What I don't understand is why we're changing the DistID and DevID.
 I'm 90% sure that clientlogin sends both in the same way as the
 official client. Did the previous ones get invalidated?

>>>
>>  Yes.
>>
>>>
 We're currently using these:

 Pidgin
 DistID: 1550
 DevID: ma1cSASNCKFtrdv9

>>>
>>  I reached out to Pidgin, see below.
>>
>> From: Donald Le 
>> Date: Thu, Sep 22, 2016 at 6:20 PM
>> Subject: Re: AIM login
>> To: Richard Vickery , pid...@alexoren.com, Pidgin Support
>> List 
>>
>> new DevID = do1UCeb5gNqxB1S1
>> new distID = 1715
>>
>>
 Finch:
 DistID: 1552
 DevID: ma19sqWV9ymU6UYc

>>>
>>  No usage since August 2014 so no need new DistID and DevID.
>>
>>>
 Libpurple:
 DistID: 1553
 DevID: ma15d7JTxbmVG-RP

>>>
>>  new DistID = 1717, new DevID = ma19CwYN9i9Mw5nY
>>
>> I found another Libpurple
>

Re: Unable to login in Pidgin

2017-03-13 Thread vaibhav chavan



Thank you so much David.

On 13-Mar-17 3:54 PM, David Woolley wrote:

On 13/03/17 10:15, vaibhav chavan wrote:


I am not able to login to pidgin ,which is saying wrong password .
Could you please help me with resetting password .


Pidgin is not something to which you can login.  It is something that 
you can use to login to many different things.  In your case, it is 
probably Oracle's internal messaging server, to which no-one on this 
list has access.


However, we understand that people with access to the Oracle VPN can 
get more information from 
, however we have no way 
of independently verifying this.


It generally surprises how many of the Oracle staff are unable to find 
the correct place to get IT support.




___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: Unable to login in Pidgin

2017-03-13 Thread David Woolley


On 13/03/17 10:15, vaibhav chavan wrote:


I am not able to login to pidgin ,which is saying wrong password .
Could you please help me with resetting password .


Pidgin is not something to which you can login.  It is something that 
you can use to login to many different things.  In your case, it is 
probably Oracle's internal messaging server, to which no-one on this 
list has access.


However, we understand that people with access to the Oracle VPN can get 
more information from  , 
however we have no way of independently verifying this.


It generally surprises how many of the Oracle staff are unable to find 
the correct place to get IT support.


___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Unable to login in Pidgin

2017-03-13 Thread vaibhav chavan


Hi ,
I am not able to login to pidgin ,which is saying wrong password .
Could you please help me with resetting password .

User name: chavan.vaibhav
Domain: oracle.com

Please let me know if any other info needed .

Thanks,
-Vaibhav
___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: AIM login

Re: AIM login

Re: Pidgin acting strange

Re: Pidgin acting strange

Re: Pidgin acting strange

Re: Pidgin acting strange

Re: AIM login

Re: AIM login

Re: AIM login

Re: Unable to login in Pidgin

Re: Unable to login in Pidgin

Unable to login in Pidgin

12 matches

Site Navigation

Mail list logo

Footer information