Opened at 2009-02-03T00:46:23Z
Closed at 2014-07-07T10:33:22Z
#481 closed enhancement (wontfix)
Patch for supporting variable msn host/port.
| Reported by: | eddieparker | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BitlBee | Version: | 1.2.3 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: |
Description
Hi!
I'm using SimpServer [1] on my linux box for encrypting MSN traffic. SimpServer sets up a SOCKS proxy, as well as a fake 'direct connection' for MSN traffic, and different ones per protocol.
I couldn't find a way of making this work, and found that msn.c had the hostname/port hardcoded. This patch fixes that.
The only thing about this patch, now that I think about it, is that it doesn't modify the default .conf file to include the appropriate section heading. It should look like this:
# [msn] # host=messenger.hotmail.com # port=1863
Attachments (1)
Change History (4)
Changed at 2009-02-03T00:47:38Z by
| Attachment: | bitlbee-msn_host[1].patch added |
|---|
comment:2 Changed at 2009-03-11T23:25:39Z by
Sorry, but that patch is absolutely unsuitable. Why make the MSN server name a server-wide setting? That way, all users on the BitlBee server will be able to use just that MSN server.
Instead, you could make it a per-account setting (actually easier to implement than a global setting) so users can even have both a normal MSN account and one on the usual server, at the same time.
comment:3 Changed at 2014-07-07T10:33:22Z by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
This might have made a little bit of sense before MSNP13, but now it has way too many servers in different addresses for something like this to work.
And simpserver is dead.
(Sorry for having this ticket open for so long and suddenly closing it now!)
Bitlbee patch for supporting a variable host and/or port for MSN connections.