Opened 4 years ago

Last modified 19 months ago

#15187 new defect

Proxy settings for Smarsh using AIM

Reported by: pbrophylight Owned by: MarkDoliner
Milestone: Component: AIM
Version: 2.10.4 Keywords: smarsh aim proxy
Cc:

Description

I am trying to use Pidgin with Smarsh IM archiving using the AIM service as one of my IM mediums.

Smarsh hosted IM proxy information : http://www.smarsh.com/instant-message-archiving Smarsh hosted IM proxy setup for Trillian : https://app.smarsh.com/prinsite/my/c_helpfaq.aspx?pf=1&view=entry&s_faq_id=168 https://app.smarsh.com/prinsite/my/c_helpfaq.aspx?pf=1&view=entry&s_faq_id=301

the settings in Pidgin that I am using are the following for AIM and Smarsh Proxy

These settings work for the first time you log in using them to AIM through Pidgin but after X times logging in and out, it will fail and say :

X times can be from 2 to 5 times but after I get this message, I cannot log back into AIM until I remove the account and then re-add it again to Pidgin.

I do not have these issues when using Trillian but with Trillian I have to use the Port 5192 instead of with Pidgin Port 5191. Is there anything else I can do to get this working or could you suggest for me to try to make this work?

If you need any additional information, please let me know.

Attachments (3)

smarsh_details.docx (84.3 KB) - added by pbrophylight 4 years ago.
Smarsh settings screenshots
Debug.zip (25.9 KB) - added by pbrophylight 4 years ago.
debug files with working and non working connections.
debugnow.zip (5.7 KB) - added by pbrophylight 4 years ago.
new debug file

Download all attachments as: .zip

Change History (8)

Changed 4 years ago by pbrophylight

Smarsh settings screenshots

comment:1 Changed 4 years ago by datallah

  • Status changed from new to pending

Please follow the instructions to get a debug log and attach it to this ticket.

Changed 4 years ago by pbrophylight

debug files with working and non working connections.

comment:2 Changed 4 years ago by pbrophylight

  • Status changed from pending to new

Attachment (Debug.zip) added by ticket reporter.

comment:4 Changed 4 years ago by pbrophylight

Attached are the debug logs of when it did and did not work.

I had 2 AIM accounts that I was testing with. Light8223 was used to connect directly to the AIM servers as normal and the Paul.brophy@… AIM account was setup to work through the Smarsh server for archiving.

Debug log called "working log.txt" : This is the first connection of the day and worked as normal. You maybe able to see the connections and all the access going through the system. This may be a good log as a marker as to how it should work.

Debug log called "debug1.txt" This is after I disconnected from the first connection and reopened the application and tried to work again.

Debug log called "debug failed" This should show that it disconnected but then allowed me to reconnect again.

Debug log called " debug failed2" This is when I tried the pidgin application from another computer and connected fine. I then tried to connect from computer 1 and it failed again.

Please let me know if there is anything else I can do or change or if there is anything else you need to help diagnose or understand where the problem could be.

Any help is greatly appreciated.

Changed 4 years ago by pbrophylight

new debug file

comment:5 Changed 4 years ago by pbrophylight

The debugnow.zip has the exact problem that i cannot connect to aim anymore with pidgin through the smarsh proxy. please let me know if there is anything else you need. thx

comment:6 Changed 19 months ago by kakaroto

Hi @pbrophylight,

I know it's a 3 years old issue, but if you're still interested, I've submitted a fix for it here : https://developer.pidgin.im/ticket/14917#comment:7

Your settings must be :

  • Host: improxy.smarsh.com
  • Port: 5191
  • Disable "Use clientLogin"

That should make smarsh work with pidgin and it won't disconnect you after you login.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!