From jhgandhi at yahoo.com Thu Feb 12 14:03:08 2009 From: jhgandhi at yahoo.com (jignesh gandhi) Date: Thu, 12 Feb 2009 11:03:08 -0800 (PST) Subject: [imapproxy-info] re : using the admin cmds... Message-ID: <252275.74490.qm@web52707.mail.re2.yahoo.com> Hello, I just installed up-imapproxy-1.2.7rc2 and started to play with it a bit. When I issue the admin cmds such as " A1 XPROXY_VERSION", I get an error back instead of the version info. Below is the output... [root at lite1 scripts]# telnet localhost 144 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK vav-um-001 IP Unity IMAP4 service (version 1.0) A1 XPROXY_VERSION A1 BAD Please login first A2 XPROXY_DUMPICC A2 BAD Please login first As you can see it is passing these cmds to the IMAP server, instead of answering it. Below is my imapproxy.conf file. Any help is apprecitated. [root at lite1 scripts]# cat /etc/imapproxy.conf ## imapproxy.conf ## ## This is the global configuration file for imapproxy. ## Lines beginning with a '#' sign are treated as comments and will be ## ignored. Each line to be processed must be a space delimited ## keyword/value pair. ## # ## server_hostname ## ## This setting controls which imap server we proxy our connections to. # server_hostname mereon.glenatl.glenayre.com # ## cache_size ## ## This setting determines how many in-core imap connection structures ## will be allocated. As such, it determines not only how many cached ## connections will be allowed, but really the total number of simultaneous ## connections, cached and active. # cache_size 3072 # ## listen_port ## ## This setting specifies which port the proxy server will bind to and ## accept incoming connections from. # listen_port 144 # ## listen_address ## ## This setting specifies which address the proxy server will bind to and ## accept incoming connections to. If undefined, bind to all. ## Must be a dotted decimal IP address. # listen_address 127.0.0.1 # ## server_port ## ## This setting specifies the port that server_hostname is listening on. ## This is the tcp port that we proxy inbound connections to. # server_port 143 # ## cache_expiration_time ## ## This setting controls how many seconds an inactive connection will be ## cached. # cache_expiration_time 300 # ## proc_username ## ## This setting controls which username the imap proxy process will run as. ## It is not allowed to run as "root". # proc_username service # ## proc_groupname ## ## This setting controls which groupname the imap proxy process will run as. # proc_groupname sadmin # ## stat_filename ## ## This is the path to the filename that the proxy server mmap()s to ## write statistical data to. This is the file that pimpstat needs to ## look at to be able to provide his useful stats. # stat_filename /var/run/pimpstats # ## protocol_log_filename ## ## protocol logging may only be turned on for one user at a time. All ## protocol logging data is written to the file specified by this path. # protocol_log_filename /var/log/imapproxy_protocol.log # ## syslog_facility ## ## The logging facility to be used for all syslog calls. If nothing is ## specified here, it will default to LOG_MAIL. Any of the possible ## facilities listed in the syslog(3C) manpage may be used here except ## LOG_KERN. # syslog_facility LOG_MAIL # ## syslog_prioritymask ## ## This configuration option is provided as a way to limit the verbosity ## of imapproxy. If no value is specified, it will default to no priority ## mask and you'll see all possible log messages. Any of the possible ## priority values listed in the syslog(3C) manpage may be used here. ## By default, I've left this commented out so you will see all possible ## log messages. # #syslog_prioritymask LOG_WARNING # ## send_tcp_keepalives ## ## This determines whether the SO_KEEPALIVE option will be set on all ## sockets. # send_tcp_keepalives no # ## enable_select_cache ## ## This configuration option allows you to turn select caching on or off. ## When select caching is enabled, up-imapproxy will cache SELECT responses ## from an imap server. # enable_select_cache no # ## foreground_mode ## ## This will prevent imapproxy from detaching from his parent process and ## controlling terminal on startup. # foreground_mode no # ## force_tls ## ## Force imapproxy to use STARTTLS even if LOGIN is not disabled. # force_tls no # ## chroot_directory ## ## This allows imapproxy to run in a chroot jail if desired. ## If commented out, imapproxy will not run chroot()ed. If ## a directory is specified here, imapproxy will chroot() to that ## directory. # #chroot_directory /var/empty # ## enable_admin_commands ## ## Used to enable or disable the internal imapproxy administrative commands. # enable_admin_commands yes # ## Various path options for SSL CA certificates/directories # #tls_ca_file /usr/share/ssl/certs/ca-bundle.crt #tls_ca_path /usr/share/ssl/certs/ #tls_cert_file /usr/share/ssl/certs/mycert.crt #tls_key_file /usr/share/ssl/certs/mycert.key --thanks Jignesh Gandhi From dave64 at andrew.cmu.edu Thu Feb 12 14:30:29 2009 From: dave64 at andrew.cmu.edu (Dave McMurtrie) Date: Thu, 12 Feb 2009 14:30:29 -0500 Subject: [imapproxy-info] re : using the admin cmds... In-Reply-To: <252275.74490.qm@web52707.mail.re2.yahoo.com> References: <252275.74490.qm@web52707.mail.re2.yahoo.com> Message-ID: <499478D5.8090905@andrew.cmu.edu> jignesh gandhi wrote: > Hello, > > I just installed up-imapproxy-1.2.7rc2 and started to play with it a bit. > > When I issue the admin cmds such as " A1 XPROXY_VERSION", I get an error back > instead of the version info. Below is the output... > > [root at lite1 scripts]# telnet localhost 144 > Trying 127.0.0.1... > Connected to localhost.localdomain (127.0.0.1). > Escape character is '^]'. > * OK vav-um-001 IP Unity IMAP4 service (version 1.0) > A1 XPROXY_VERSION > A1 BAD Please login first > A2 XPROXY_DUMPICC > A2 BAD Please login first > > As you can see it is passing these cmds to the IMAP server, instead of answering it. > Below is my imapproxy.conf file. Any help is apprecitated. That's still imapproxy responding directly. No commands are passed through to the imap server until after you've authenticated. Did you edit imapproxy.conf to set "enable_admin_commands yes" after imapproxy was already running? Thanks, Dave -- Dave McMurtrie, SPE Email Systems Team Leader Carnegie Mellon University, Computing Services From jhgandhi at yahoo.com Thu Feb 12 16:33:17 2009 From: jhgandhi at yahoo.com (jignesh gandhi) Date: Thu, 12 Feb 2009 13:33:17 -0800 (PST) Subject: [imapproxy-info] re : using the admin cmds... Message-ID: <268692.43646.qm@web52708.mail.re2.yahoo.com> Hello Dave, I saw your reply when I was browsing through the archives. Funny, I did not get an email on my jhgandhi at yahoo.com. Anyway. I have enabled internal admin cmds... startup syslog pasted below.... ----------------------------- Feb 12 11:51:11 lite1 in.imapproxyd: main(): Using default configuration file '/etc/imapproxy.conf'. Feb 12 11:51:11 lite1 in.imapproxyd: main(): Using default configuration file '/etc/imapproxy.conf'. Feb 12 11:51:11 lite1 in.imapproxyd: Using syslog facility 'LOG_MAIL' for logging. Feb 12 11:51:11 lite1 in.imapproxyd: Using syslog facility 'LOG_MAIL' for logging. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: No syslog priority mask specified. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: main(): SELECT caching is disabled Feb 12 11:51:11 lite1 in.imapproxyd[14312]: main(): Internal admin commands are enabled Feb 12 11:51:11 lite1 in.imapproxyd[14312]: main(): Allocating 3072 IMAP connection structures. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: ServerInit(): Using '/var/log/imapproxy_protocol.log' for global protocol logging file. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: ServerInit(): proxying to IMAP server 'mereon.glenatl.glenayre.com'. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: ServerInit(): Proxying to IMAP port 143 Feb 12 11:51:12 lite1 in.imapproxyd[14312]: IMAP_Line_Read(): connection closed prematurely. Feb 12 11:51:12 lite1 in.imapproxyd[14312]: SetBannerAndCapability(): IMAP_Line_Read() failed on LOGOUT -- Ignoring Feb 12 11:51:12 lite1 in.imapproxyd[14312]: main(): Binding to tcp *:144 Feb 12 11:51:12 lite1 in.imapproxyd[14312]: main(): socket() failed: Address family not supported by protocol Feb 12 11:51:12 lite1 in.imapproxyd[14312]: main(): Using global statistics file '/var/run/pimpstats' Feb 12 11:51:12 lite1 in.imapproxyd[14312]: Daemonize(): Configured to run in background mode. Feb 12 11:51:12 lite1 in.imapproxyd[14315]: BecomeNonRoot(): Process will run as uid 503 (service) and gid 500 (sadmin). Feb 12 11:51:12 lite1 in.imapproxyd[14315]: main(): Launched ICC recycle thread with id -1218843728 Feb 12 11:51:12 lite1 in.imapproxyd[14315]: main(): imapproxy version 1.2.6 normal server startup. ----------------------- any help is appreciated. thanks, Jignesh Gandhi > Hello, > > I just installed up-imapproxy-1.2.7rc2 and started to play with it a bit. > > When I issue the admin cmds such as " A1 XPROXY_VERSION", I get an error back > instead of the version info. Below is the output... > > [root at lite1 scripts]# telnet localhost 144 > Trying 127.0.0.1... > Connected to localhost.localdomain (127.0.0.1). > Escape character is '^]'. > * OK vav-um-001 IP Unity IMAP4 service (version 1.0) > A1 XPROXY_VERSION > A1 BAD Please login first > A2 XPROXY_DUMPICC > A2 BAD Please login first > > As you can see it is passing these cmds to the IMAP server, instead of answering it. > Below is my imapproxy.conf file. Any help is apprecitated. That's still imapproxy responding directly. No commands are passed through to the imap server until after you've authenticated. Did you edit imapproxy.conf to set "enable_admin_commands yes" after imapproxy was already running? Thanks, Dave -- Dave McMurtrie, SPE Email Systems Team Leader Carnegie Mellon University, Computing Services ----- Original Message ---- From: jignesh gandhi To: imapproxy-info at lists.andrew.cmu.edu Sent: Thursday, February 12, 2009 2:03:08 PM Subject: re : using the admin cmds... Hello, I just installed up-imapproxy-1.2.7rc2 and started to play with it a bit. When I issue the admin cmds such as " A1 XPROXY_VERSION", I get an error back instead of the version info. Below is the output... [root at lite1 scripts]# telnet localhost 144 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK vav-um-001 IP Unity IMAP4 service (version 1.0) A1 XPROXY_VERSION A1 BAD Please login first A2 XPROXY_DUMPICC A2 BAD Please login first As you can see it is passing these cmds to the IMAP server, instead of answering it. Below is my imapproxy.conf file. Any help is apprecitated. [root at lite1 scripts]# cat /etc/imapproxy.conf ## imapproxy.conf ## ## This is the global configuration file for imapproxy. ## Lines beginning with a '#' sign are treated as comments and will be ## ignored. Each line to be processed must be a space delimited ## keyword/value pair. ## # ## server_hostname ## ## This setting controls which imap server we proxy our connections to. # server_hostname mereon.glenatl.glenayre.com # ## cache_size ## ## This setting determines how many in-core imap connection structures ## will be allocated. As such, it determines not only how many cached ## connections will be allowed, but really the total number of simultaneous ## connections, cached and active. # cache_size 3072 # ## listen_port ## ## This setting specifies which port the proxy server will bind to and ## accept incoming connections from. # listen_port 144 # ## listen_address ## ## This setting specifies which address the proxy server will bind to and ## accept incoming connections to. If undefined, bind to all. ## Must be a dotted decimal IP address. # listen_address 127.0.0.1 # ## server_port ## ## This setting specifies the port that server_hostname is listening on. ## This is the tcp port that we proxy inbound connections to. # server_port 143 # ## cache_expiration_time ## ## This setting controls how many seconds an inactive connection will be ## cached. # cache_expiration_time 300 # ## proc_username ## ## This setting controls which username the imap proxy process will run as. ## It is not allowed to run as "root". # proc_username service # ## proc_groupname ## ## This setting controls which groupname the imap proxy process will run as. # proc_groupname sadmin # ## stat_filename ## ## This is the path to the filename that the proxy server mmap()s to ## write statistical data to. This is the file that pimpstat needs to ## look at to be able to provide his useful stats. # stat_filename /var/run/pimpstats # ## protocol_log_filename ## ## protocol logging may only be turned on for one user at a time. All ## protocol logging data is written to the file specified by this path. # protocol_log_filename /var/log/imapproxy_protocol.log # ## syslog_facility ## ## The logging facility to be used for all syslog calls. If nothing is ## specified here, it will default to LOG_MAIL. Any of the possible ## facilities listed in the syslog(3C) manpage may be used here except ## LOG_KERN. # syslog_facility LOG_MAIL # ## syslog_prioritymask ## ## This configuration option is provided as a way to limit the verbosity ## of imapproxy. If no value is specified, it will default to no priority ## mask and you'll see all possible log messages. Any of the possible ## priority values listed in the syslog(3C) manpage may be used here. ## By default, I've left this commented out so you will see all possible ## log messages. # #syslog_prioritymask LOG_WARNING # ## send_tcp_keepalives ## ## This determines whether the SO_KEEPALIVE option will be set on all ## sockets. # send_tcp_keepalives no # ## enable_select_cache ## ## This configuration option allows you to turn select caching on or off. ## When select caching is enabled, up-imapproxy will cache SELECT responses ## from an imap server. # enable_select_cache no # ## foreground_mode ## ## This will prevent imapproxy from detaching from his parent process and ## controlling terminal on startup. # foreground_mode no # ## force_tls ## ## Force imapproxy to use STARTTLS even if LOGIN is not disabled. # force_tls no # ## chroot_directory ## ## This allows imapproxy to run in a chroot jail if desired. ## If commented out, imapproxy will not run chroot()ed. If ## a directory is specified here, imapproxy will chroot() to that ## directory. # #chroot_directory /var/empty # ## enable_admin_commands ## ## Used to enable or disable the internal imapproxy administrative commands. # enable_admin_commands yes # ## Various path options for SSL CA certificates/directories # #tls_ca_file /usr/share/ssl/certs/ca-bundle.crt #tls_ca_path /usr/share/ssl/certs/ #tls_cert_file /usr/share/ssl/certs/mycert.crt #tls_key_file /usr/share/ssl/certs/mycert.key --thanks Jignesh Gandhi From jhgandhi at yahoo.com Thu Feb 12 19:04:54 2009 From: jhgandhi at yahoo.com (jignesh gandhi) Date: Thu, 12 Feb 2009 16:04:54 -0800 (PST) Subject: [imapproxy-info] re : using the admin cmds... Message-ID: <432622.59665.qm@web52704.mail.re2.yahoo.com> Hello Dave, Never mind... I was running the wrong executable.. Sorry for the trouble... --Jignesh Gandhi ----- Original Message ---- From: jignesh gandhi To: imapproxy-info at lists.andrew.cmu.edu Sent: Thursday, February 12, 2009 4:33:17 PM Subject: Re: re : using the admin cmds... Hello Dave, I saw your reply when I was browsing through the archives. Funny, I did not get an email on my jhgandhi at yahoo.com. Anyway. I have enabled internal admin cmds... startup syslog pasted below.... ----------------------------- Feb 12 11:51:11 lite1 in.imapproxyd: main(): Using default configuration file '/etc/imapproxy.conf'. Feb 12 11:51:11 lite1 in.imapproxyd: main(): Using default configuration file '/etc/imapproxy.conf'. Feb 12 11:51:11 lite1 in.imapproxyd: Using syslog facility 'LOG_MAIL' for logging. Feb 12 11:51:11 lite1 in.imapproxyd: Using syslog facility 'LOG_MAIL' for logging. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: No syslog priority mask specified. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: main(): SELECT caching is disabled Feb 12 11:51:11 lite1 in.imapproxyd[14312]: main(): Internal admin commands are enabled Feb 12 11:51:11 lite1 in.imapproxyd[14312]: main(): Allocating 3072 IMAP connection structures. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: ServerInit(): Using '/var/log/imapproxy_protocol.log' for global protocol logging file. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: ServerInit(): proxying to IMAP server 'mereon.glenatl.glenayre.com'. Feb 12 11:51:11 lite1 in.imapproxyd[14312]: ServerInit(): Proxying to IMAP port 143 Feb 12 11:51:12 lite1 in.imapproxyd[14312]: IMAP_Line_Read(): connection closed prematurely. Feb 12 11:51:12 lite1 in.imapproxyd[14312]: SetBannerAndCapability(): IMAP_Line_Read() failed on LOGOUT -- Ignoring Feb 12 11:51:12 lite1 in.imapproxyd[14312]: main(): Binding to tcp *:144 Feb 12 11:51:12 lite1 in.imapproxyd[14312]: main(): socket() failed: Address family not supported by protocol Feb 12 11:51:12 lite1 in.imapproxyd[14312]: main(): Using global statistics file '/var/run/pimpstats' Feb 12 11:51:12 lite1 in.imapproxyd[14312]: Daemonize(): Configured to run in background mode. Feb 12 11:51:12 lite1 in.imapproxyd[14315]: BecomeNonRoot(): Process will run as uid 503 (service) and gid 500 (sadmin). Feb 12 11:51:12 lite1 in.imapproxyd[14315]: main(): Launched ICC recycle thread with id -1218843728 Feb 12 11:51:12 lite1 in.imapproxyd[14315]: main(): imapproxy version 1.2.6 normal server startup. ----------------------- any help is appreciated. thanks, Jignesh Gandhi > Hello, > > I just installed up-imapproxy-1.2.7rc2 and started to play with it a bit. > > When I issue the admin cmds such as " A1 XPROXY_VERSION", I get an error back > instead of the version info. Below is the output... > > [root at lite1 scripts]# telnet localhost 144 > Trying 127.0.0.1... > Connected to localhost.localdomain (127.0.0.1). > Escape character is '^]'. > * OK vav-um-001 IP Unity IMAP4 service (version 1.0) > A1 XPROXY_VERSION > A1 BAD Please login first > A2 XPROXY_DUMPICC > A2 BAD Please login first > > As you can see it is passing these cmds to the IMAP server, instead of answering it. > Below is my imapproxy.conf file. Any help is apprecitated. That's still imapproxy responding directly. No commands are passed through to the imap server until after you've authenticated. Did you edit imapproxy.conf to set "enable_admin_commands yes" after imapproxy was already running? Thanks, Dave -- Dave McMurtrie, SPE Email Systems Team Leader Carnegie Mellon University, Computing Services ----- Original Message ---- From: jignesh gandhi To: imapproxy-info at lists.andrew.cmu.edu Sent: Thursday, February 12, 2009 2:03:08 PM Subject: re : using the admin cmds... Hello, I just installed up-imapproxy-1.2.7rc2 and started to play with it a bit. When I issue the admin cmds such as " A1 XPROXY_VERSION", I get an error back instead of the version info. Below is the output... [root at lite1 scripts]# telnet localhost 144 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK vav-um-001 IP Unity IMAP4 service (version 1.0) A1 XPROXY_VERSION A1 BAD Please login first A2 XPROXY_DUMPICC A2 BAD Please login first As you can see it is passing these cmds to the IMAP server, instead of answering it. Below is my imapproxy.conf file. Any help is apprecitated. [root at lite1 scripts]# cat /etc/imapproxy.conf ## imapproxy.conf ## ## This is the global configuration file for imapproxy. ## Lines beginning with a '#' sign are treated as comments and will be ## ignored. Each line to be processed must be a space delimited ## keyword/value pair. ## # ## server_hostname ## ## This setting controls which imap server we proxy our connections to. # server_hostname mereon.glenatl.glenayre.com # ## cache_size ## ## This setting determines how many in-core imap connection structures ## will be allocated. As such, it determines not only how many cached ## connections will be allowed, but really the total number of simultaneous ## connections, cached and active. # cache_size 3072 # ## listen_port ## ## This setting specifies which port the proxy server will bind to and ## accept incoming connections from. # listen_port 144 # ## listen_address ## ## This setting specifies which address the proxy server will bind to and ## accept incoming connections to. If undefined, bind to all. ## Must be a dotted decimal IP address. # listen_address 127.0.0.1 # ## server_port ## ## This setting specifies the port that server_hostname is listening on. ## This is the tcp port that we proxy inbound connections to. # server_port 143 # ## cache_expiration_time ## ## This setting controls how many seconds an inactive connection will be ## cached. # cache_expiration_time 300 # ## proc_username ## ## This setting controls which username the imap proxy process will run as. ## It is not allowed to run as "root". # proc_username service # ## proc_groupname ## ## This setting controls which groupname the imap proxy process will run as. # proc_groupname sadmin # ## stat_filename ## ## This is the path to the filename that the proxy server mmap()s to ## write statistical data to. This is the file that pimpstat needs to ## look at to be able to provide his useful stats. # stat_filename /var/run/pimpstats # ## protocol_log_filename ## ## protocol logging may only be turned on for one user at a time. All ## protocol logging data is written to the file specified by this path. # protocol_log_filename /var/log/imapproxy_protocol.log # ## syslog_facility ## ## The logging facility to be used for all syslog calls. If nothing is ## specified here, it will default to LOG_MAIL. Any of the possible ## facilities listed in the syslog(3C) manpage may be used here except ## LOG_KERN. # syslog_facility LOG_MAIL # ## syslog_prioritymask ## ## This configuration option is provided as a way to limit the verbosity ## of imapproxy. If no value is specified, it will default to no priority ## mask and you'll see all possible log messages. Any of the possible ## priority values listed in the syslog(3C) manpage may be used here. ## By default, I've left this commented out so you will see all possible ## log messages. # #syslog_prioritymask LOG_WARNING # ## send_tcp_keepalives ## ## This determines whether the SO_KEEPALIVE option will be set on all ## sockets. # send_tcp_keepalives no # ## enable_select_cache ## ## This configuration option allows you to turn select caching on or off. ## When select caching is enabled, up-imapproxy will cache SELECT responses ## from an imap server. # enable_select_cache no # ## foreground_mode ## ## This will prevent imapproxy from detaching from his parent process and ## controlling terminal on startup. # foreground_mode no # ## force_tls ## ## Force imapproxy to use STARTTLS even if LOGIN is not disabled. # force_tls no # ## chroot_directory ## ## This allows imapproxy to run in a chroot jail if desired. ## If commented out, imapproxy will not run chroot()ed. If ## a directory is specified here, imapproxy will chroot() to that ## directory. # #chroot_directory /var/empty # ## enable_admin_commands ## ## Used to enable or disable the internal imapproxy administrative commands. # enable_admin_commands yes # ## Various path options for SSL CA certificates/directories # #tls_ca_file /usr/share/ssl/certs/ca-bundle.crt #tls_ca_path /usr/share/ssl/certs/ #tls_cert_file /usr/share/ssl/certs/mycert.crt #tls_key_file /usr/share/ssl/certs/mycert.key --thanks Jignesh Gandhi From japc at co.sapo.pt Mon Feb 23 12:18:58 2009 From: japc at co.sapo.pt (Jose Celestino) Date: Mon, 23 Feb 2009 17:18:58 +0000 Subject: [imapproxy-info] imapproxy-1.2.7rc2 available for download In-Reply-To: <497F69C8.2020502@andrew.cmu.edu> References: <497F69C8.2020502@andrew.cmu.edu> Message-ID: <20090223171858.GA8236@co.sapo.pt> Words by Dave McMurtrie [Tue, Jan 27, 2009 at 03:08:40PM -0500]: > Good afternoon, > > up-imapproxy-1.2.7rc2 is now available for download at: > > http://www.imapproxy.org/downloads/up-imapproxy-1.2.7rc2.tar.gz > > This release candidate is identical to the 1.2.7rc1 candidate, but > includes a patch by Michael Slusarz to fix an issue that came up with > CAPABILITY response strings in 1.2.7rc1. > There's a possible ICC starvation issue with clients closing the connection immediatly after they issue the login. The connection to the server will be closed but the ICC is kept with logouttime 0 and is never recycled. It's a matter of a few minutes until you start getting out of free ICC structs. Attached is a patch that works around that (with the bonus of removing some contention from logout by backreferencing the ICC from the ICD). There are also some security issues of simply closing the server connection but leaving it referenced on the ICC as it may become the descriptor for another client server connection and being reused by the first client it will actually grant him access to the second user account. That's why it is set to ?1. -- Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc ---------------------------------------------------------------- "One man?s theology is another man?s belly laugh." -- Robert A. Heinlein -------------- next part -------------- A non-text attachment was scrubbed... Name: up-imapproxy-icc_invalidate.diff Type: text/x-diff Size: 4416 bytes Desc: not available Url : http://lists.andrew.cmu.edu/pipermail/imapproxy-info/attachments/20090223/5f770c3a/attachment.bin