squirrelmail-imapproxy — SquirrelMail IMAP Proxy Mailing List

Re: [SM-imapproxy] Verification if imapproxy is working as expected

[Paul L. <pa...@sq...>]

On Fri, August 26, 2016 2:41 pm, c....@we... wrote:
> Hello!
>
> I'm running a dedicated IMAP server (mailserver) in a separated network
> (DMZ).
> In addition, I have setup a reverse proxy server (HAproxy) that redirects
> requests to the dedicated server.
>
> On this reverse proxy I installed imapproxy.
>
> Question:
> How can I verify if imapproxy is working as expected?

Log in manually and try a command like this:

a001 XPROXY_VERSION

imapproxy will respond with its own version number if it is what is
getting your requests.

> Should I redirect incoming webmail traffic to imapproxy?
> (Currently the traffic is redirected to the mailserver.)

I don't really understand what you are asking. Your system architecture is
up to you, but I assume you'd want the answer to be "yes", otherwise I
don't understand why you installed it.

[SM-imapproxy] imapproxy using STARTTLS with Let's Encrypt certificate

[<c....@we...>]

Hello!

I want to user imapproxy and STARTTLS with Let's Encrypt certificate.

Imapproxy is running on the mailserver. (This mailserver provides webserver, too.)

I can connect from a Webmail Client to the mailserver using STARTTLS and port 143 w/o issues if imapproxy is stopped.
If imapproxy is started, I can only connect to mailserver when security disenabled.

imapproxy is listening on port 32143, and the relevant port in the firewall is open.

When I test the configuration using STARTTLS, I get this error message:
STARTTLS is not supported.

There's nothing written to /var/log/imapproxy_protocol.log

Any advice?

This is my configuration:
## 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 localhost

connect_retries 10
connect_delay 5

cache_size 3072

listen_port 32143

server_port 143

cache_expiration_time 300

proc_username nobody
proc_groupname nogroup

stat_filename /var/run/pimpstats

protocol_log_filename /var/log/imapproxy_protocol.log

syslog_facility LOG_MAIL

#syslog_prioritymask LOG_WARNING

send_tcp_keepalives no

enable_select_cache no

foreground_mode no

force_tls no

#chroot_directory /var/lib/imapproxy/chroot

enable_admin_commands no

tls_ca_path /var/lib/imapproxy/chroot/
tls_ca_file /var/lib/imapproxy/chroot/mehl.biszumbitterenen.de.pem
tls_cert_file /var/lib/imapproxy/chroot/cert.pem
tls_key_file /var/lib/imapproxy/chroot/privkey.pem

[SM-imapproxy] Imapproxy & ID command

[Jean-Luc W. <ima...@jl...>]

Hi,

I use Imapproxy 1.2.7 between Roundcube & Dovecot. I installed a 
Roundcube plugging that sends the web client's IP address to the IMAP 
server using the ID command. This way log files contain the real IP of 
the user instead of the web server IP address.

Unfortunately, Imapproxy doesn't like that:

* OK [CAPABILITY IMAP4rev1 LITERAL+ LOGIN-REFERRALS ID ENABLE  
XIMAPPROXY] Dovecot ready.
A0001 ID ("x-originating-ip" "24.212.235.245")
A0001 BAD Please login first
A0002 LOGIN user1 "password"


When I by-pass Imapproxy:

* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE STARTTLS AUTH=PLAIN] Dovecot ready.
A0001 ID ("x-originating-ip" "24.212.235.245")
* ID ("name" "Dovecot")
A0001 OK ID completed.
A0002 AUTHENTICATE PLAIN AAAABBBBBCCCCDDD==



This seems like a rather simple command to support, would it be possible 
to add it?

Thanks!
Jean-Luc

[SM-imapproxy] Verification if imapproxy is working as expected

[<c....@we...>]

Hello!

I'm running a dedicated IMAP server (mailserver) in a separated network (DMZ).
In addition, I have setup a reverse proxy server (HAproxy) that redirects requests to the dedicated server.

On this reverse proxy I installed imapproxy.

Question:
How can I verify if imapproxy is working as expected?
Should I redirect incoming webmail traffic to imapproxy?
(Currently the traffic is redirected to the mailserver.)

THX

Re: [SM-imapproxy] Imapproxy times out on Debian testing (Stretch)

[Thomas B. <tb...@tx...>]

Thanks for the trick! No timeout with type simple. It s ok for me. Main 
thing is that it works.


Am 02.08.2016 um 12:45 schrieb Jens Wahnes:
> Thomas Barth wrote:
>
>> The unit file is:
>>
>> /lib/systemd/system/imapproxy.service
>>
>> [Unit]
>> Documentation=man:imapproxyd(8)
>> Description=IMAP proxy
>> After=network-online.target
>> Wants=network-online.target
>>
>> [Service]
>> Type=forking
>> ExecStart=/usr/sbin/imapproxyd -f /etc/imapproxy.conf
>>
>
> I see. So the main difference between my unit file and this one seems 
> to be the "type" of service. Previously, I had tried "Type=forking" as 
> well, but since that didn't work out very well, I went to try 
> "Type=simple". For me, this is doing the trick so far, but as I 
> pointed out before, I'm terribly satisfied with this approch. Well, 
> you still may want to give that a shot anyway and see if it works for 
> you.
>
>
> Jens
>
>
>
>
> ------------------------------------------------------------------------------
>
>
> -----
> squirrelmail-imapproxy mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squ...@li...
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.imapproxy
> List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-imapproxy

Re: [SM-imapproxy] Imapproxy times out on Debian testing (Stretch)

[Jens W. <wa...@un...>]

Thomas Barth wrote:

> The unit file is:
>
> /lib/systemd/system/imapproxy.service
>
> [Unit]
> Documentation=man:imapproxyd(8)
> Description=IMAP proxy
> After=network-online.target
> Wants=network-online.target
>
> [Service]
> Type=forking
> ExecStart=/usr/sbin/imapproxyd -f /etc/imapproxy.conf
>

I see. So the main difference between my unit file and this one seems to 
be the "type" of service. Previously, I had tried "Type=forking" as 
well, but since that didn't work out very well, I went to try 
"Type=simple". For me, this is doing the trick so far, but as I pointed 
out before, I'm terribly satisfied with this approch. Well, you still 
may want to give that a shot anyway and see if it works for you.


Jens

Re: [SM-imapproxy] Imapproxy times out on Debian testing (Stretch)

[Thomas B. <tb...@tx...>]

Hi!

The unit file is:

/lib/systemd/system/imapproxy.service

[Unit]
Documentation=man:imapproxyd(8)
Description=IMAP proxy
After=network-online.target
Wants=network-online.target

[Service]
Type=forking
ExecStart=/usr/sbin/imapproxyd -f /etc/imapproxy.conf



Am 02.08.2016 um 11:20 schrieb Jens Wahnes:
> Thomas Barth wrote:
>
>> I ve upgraded my Debian Jessie to testing (Stretch). Now imapproxy
>> timesout after some time. When the system is waiting for the running
>> state, imapproxy is working normal. I can connect to my mailsystem with
>> webmail client. But it ends after the timeout.
> Ah, so Debian is launching imapproxyd via systemd? What does the unit
> file look like? I've been trying to create a unit file for myself and
> asked for help here, but unfortunately there was to reply yet.
>
> In my setup, imapproxyd is running for about a month now in a systemd
> environment, but this is a very small installation, mainly used for
> testing, with few users. Plus, I am not very much satisfied the way this
> works, with imapproxy claiming it is running in foreground mode and so
> forth.
>
>
> Jens
>

Re: [SM-imapproxy] Imapproxy times out on Debian testing (Stretch)

[Jens W. <wa...@un...>]

Thomas Barth wrote:

> I ve upgraded my Debian Jessie to testing (Stretch). Now imapproxy
> timesout after some time. When the system is waiting for the running
> state, imapproxy is working normal. I can connect to my mailsystem with
> webmail client. But it ends after the timeout.

Ah, so Debian is launching imapproxyd via systemd? What does the unit 
file look like? I've been trying to create a unit file for myself and 
asked for help here, but unfortunately there was to reply yet.

In my setup, imapproxyd is running for about a month now in a systemd 
environment, but this is a very small installation, mainly used for 
testing, with few users. Plus, I am not very much satisfied the way this 
works, with imapproxy claiming it is running in foreground mode and so 
forth.


Jens

[SM-imapproxy] Imapproxy times out on Debian testing (Stretch)

[Thomas B. <tb...@tx...>]

Hello,

I ve upgraded my Debian Jessie to testing (Stretch). Now imapproxy 
timesout after some time. When the system is waiting for the running 
state, imapproxy is working normal. I can connect to my mailsystem with 
webmail client. But it ends after the timeout.

Here are the messages of systemd-devel

● imapproxy.service - IMAP proxy
    Loaded: loaded (/lib/systemd/system/imapproxy.service; static; 
vendor preset: enabled)
    Active: failed (Result: timeout) since Tue 2016-08-02 08:08:13 CEST; 
14s ago
      Docs: man:imapproxyd(8)
   Process: 10514 ExecStart=/usr/sbin/imapproxyd -f /etc/imapproxy.conf 
(code=killed, signal=TERM)

Aug 02 08:06:42 txbweb.de systemd[1]: Starting IMAP proxy...
Aug 02 08:06:42 txbweb.de imapproxyd[10514]: main(): Using configuration 
file '/etc/imapproxy.conf'
Aug 02 08:06:42 txbweb.de imapproxyd[10514]: Using syslog facility 
'LOG_MAIL' for logging.
Aug 02 08:06:42 txbweb.de in.imapproxyd[10514]: Masking syslog priority 
up to LOG_WARNING.
Aug 02 08:08:13 txbweb.de systemd[1]: imapproxy.service: Start operation 
timed out. Terminating.
Aug 02 08:08:13 txbweb.de systemd[1]: Failed to start IMAP proxy.
Aug 02 08:08:13 txbweb.de systemd[1]: imapproxy.service: Unit entered 
failed state.
Aug 02 08:08:13 txbweb.de systemd[1]: imapproxy.service: Failed with 
result 'timeout'.

Do you know how to fix this? Version of imapproxy is 1.2.7-1.2 What is 
imapprox waiting for?

[SM-imapproxy] Launching via systemd

[Jens W. <wa...@un...>]

Hi,

has anyone else tried to launch the in.imapproxyd at startup on a system 
using systemd instead of SysV init? At first sight I thought this should 
be pretty straightforward, but when I tried it, I ran into trouble.

In the systemd unit file I wrote, I tried several things, especially 
using "Type=forking" and "Type=simple", but neither yielded satisfactory 
results. Also, I fiddled with systemd's StandardInput and StandardOutput 
options, but to no avail.

What is most striking, though, is that in the logfile, Imapproxy claims 
"Daemonize(): Configured to run in foreground mode." when it is launched 
by systemd. In /etc/imapproxy.conf, however, I clearly set 
"foreground_mode no" and since the other options from the config file 
(e.g. server_hostname) are in fact picked up, I don't know why Imapproxy 
would be running in foreground mode. I suspect this to have something to 
do with the way systemd starts processes, because when I run 
"/usr/local/sbin/in.imapproxyd -p /var/run/imapproxy.pid" on the command 
line as root, everything is fine. Another strange thing is that the PID 
file given with the "-p" option is not created when Imapproxy is started 
from systemd, but it is created when running from command line. Does 
anyone have an idea how to deal with this? Maybe Imapproxy needs some 
environment variables that aren't set by default when using systemd?

BTW, I'm trying all of this using Imapproxy version 1.2.7, compiled with 
gcc 4.8.5., on a CentOS 7 box.

Here's what my current unit file looks like:

[Unit]
Description=Proxy IMAP server by the Squirrelmail Project
After=network-online.target

[Service]
#Type=forking
Type=simple
PIDFile=/var/run/imapproxy.pid
#StandardInput=null
#StandardOutput=null
ExecStart=/usr/local/sbin/in.imapproxyd -p /var/run/imapproxy.pid
Restart=on-failure

[Install]
WantedBy=multi-user.target



Thanks
Jens

-- 
Jens Wahnes
Universität zu Köln
Regionales Rechenzentrum (RRZK)
Weyertal 121 · 50931 Köln · Lageplan: http://ukoeln.de/BDKS6
Tel. (0221) 470-89614

[SM-imapproxy] [PATCH] remove EGD support

[Loganaden V. <lo...@ha...>]

EGD has largely become legacy now.

OpenSSL disables it by default in its latest release, and LibreSSL has
ripped it out completely.

I took the patch from OpenBSD, from an older version.

Index: src/main.c
===================================================================
--- src/main.c	(revision 14549)
+++ src/main.c	(working copy)
@@ -452,13 +452,8 @@
     /* Set up OpenSSL thread protection */
     ssl_thread_setup(fn);

-    /* Need to seed PRNG, too! */
-    if ( RAND_egd( ( RAND_file_name( f_randfile, sizeof( f_randfile ) )
== f_randfile ) ? f_randfile : "/.rnd" ) )
-    {
-	/* Not an EGD, so read and write it. */
-	if ( RAND_load_file( f_randfile, -1 ) )
+    if ( RAND_load_file( f_randfile, -1 ) )
 	RAND_write_file( f_randfile );
-    }

     SSL_load_error_strings();

Re: [SM-imapproxy] Unable to Receive mail to SquirrelMail Inbox

[Paul L. <pa...@sq...>]

On 3/22/16, jab...@pa... <jab...@pa...> wrote:
> Hi,
>
> SquirrelMail is unable to receive mail that is being sent to my
> SquirrelMail email address.
>
> I need to set it up today. Can you help please?

I think you misunderstand what SquirrelMail is.  It's open source
software that you set up yourself.  If you need help doing that, you
would be well advised to seek out a consultant.  I am personally
available in that capacity (please contact me off list).  Otherwise,
please use the squirrelmail-users mailing list to ask specific
questions about any issues you have with the webmail software.

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-imapproxy] Unable to Receive mail to SquirrelMail Inbox

[<jab...@pa...>]

Hi,

SquirrelMail is unable to receive mail that is being sent to my
SquirrelMail email address.

I need to set it up today. Can you help please?

Thank you,

[SM-imapproxy] Failed connections with "connection closed prematurely"

[Jens W. <wa...@un...>]

Hi,

ever since we upgraded our webmail service (new server, new webmail
version, new PHP version with opcode cache, new Linux version, new
imapproxy version, ...) we've seen an increase of lines like this in
the logfile:

Jun 17 08:34:16 webmail in.imapproxyd[22721]: IMAP_Line_Read(): connection closed prematurely.

We've had that happen in the past, too, but much more infrequently.
With the new environment, it's certain to happen several times a day.

Considering we've got all these new components, figuring out what may
be causing this is a bit difficult, of course.  I've tried upgrading to
the latest SVN version of imapproxy, but that didn't help.  After
looking at the source code for a while, I tried to add some debug
information to the logfile entries in order to better pin down the
exact place where the problem occurs.  (There a two places where
"connection closed prematurely" could happen.) Unfortunately, I'm not
that much of a C programmer and have trouble understanding all the code
that's there, but the code changes I made at least still compile. 
Here's what the code near the end of the function IMAP_Line_Read in
imapcommon.c looks like now:

        Status = IMAP_Read(ITD->conn, &ITD->ReadBuf[ITD->BytesInReadBuffer],
                      (sizeof ITD->ReadBuf - ITD->BytesInReadBuffer ) );

        if ( Status == 0 )
        {
            syslog(LOG_WARNING, "%s: connection closed prematurely. sd [%d]. (line 1788 of imapcommon.c)", fn, ITD->conn->sd);
            return(-1);
        }
        else if ( Status == -1 )
        {
            syslog(LOG_ERR, "%s: IMAP_Read() failed: %s", fn, strerror(errno) );
            return(-1);
        }

So, basically, I added the "ITD->conn->sd" info to the logfile message,
but I'm not certain that this variable can be used in this context. 
Can anyone confirm that this OK?

After putting that code into service, I didn't have to wait long for
the first lines in the logfile with this additional info to appear. 
Based on the output of that log message, I looked for information which
user that specific sd had been assigned before in order to search for
patterns there.  (I've been suspecting this problem to have something
to do with some users having several connections open or cached when
looking around with the XPROXY_DUMPICC command.) To my surprise, in all
cases I found, the sd in question had been expired before and there was
no indication that it has been re-assigned.  So the logfile entries
looked like this:

Jun 21 13:56:37 webmail in.imapproxyd[29720]: Expiring server sd [26]
Jun 21 13:57:31 webmail in.imapproxyd[29720]: IMAP_Line_Read(): connection closed prematurely. sd [26]. (line 1788 of imapcommon.c)

At least in this one case, I was able to gather the info from all the
different logfiles together and match the different entries.  (If the
logfile entries help in debugging this, I can post the anonymized
entries here.)  In the end, it looks very much like the imapproxy
(re-)used an expired connection to the IMAP server instead of the newly
created one for the user that just logged in.

If this is true, it would mean that the problem is not with the
IMAP_Line_Read code that I spent time looking at, but instead with some
other code which actually assigns the sds to user connections.  Do you
agree so far?  Does anyone have suggestions how to further investigate
this?  Or where to look for the problem in the code?

Thanks,
Jens

[SM-imapproxy] [PATCH] Make RAND_egd conditional / fix build with LibreSSL

[Spil O. <spi...@gm...>]

Hi,

The current SquirrelMail IMAP proxy does not build with LibreSSL due
to LibreSSL dropping support for the perl EGD (entropy gathering
daemon). There are currently NO supported operating systems requiring
the perl EGD, all supported OS's have a random device that exceeds the
performance and randomness of the EGD. Most OS's have had proper RNGs
for many years.

To fix build with LibreSSL, I've added a configure check for RAND_egd
and an #ifdef around the line of code preventing building without it.
This is part of a larger effort to make all ports build on FreeBSD
with LibreSSL (see https://wiki.freebsd.org/LibreSSL) and provide the
patches to upstream projects.

Attached patches do not include the changes to config.h.in and
configure as these are regenerated by the FreeBSD port. The FreeBSD
port already contained additional patches to the code which have not
been included in these patches. You can view the original patches at
https://svnweb.freebsd.org/ports/head/mail/up-imapproxy/files/ and the
new patches at https://github.com/Sp1l/ports/tree/master/mail/up-imapproxy

Hope that you'll include these patches into your code!

Kind regards,

Bernard Spil.

Re: [SM-imapproxy] self signed certificates.

[<ma...@ne...>]

<jo...@7l...> wrote:

> Hi,

 I need to run imapproxy with STARTTLS flags, but it seems not to
> work with self signed certificates. 

Did you try providing your own certificate as tls_ca_file? If that does
not work you may have to create your own CA and sign your certificate
with it.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
ma...@ne...

[SM-imapproxy] self signed certificates.

[<jo...@7l...>]

Hi,

 I need to run imapproxy with STARTTLS flags, but it seems not to work with self signed certificates. 

 Is there a way to make it work? 
 Maybe changing the source code, any ideias?

  STARTTLS AUTH=PLAIN AUTH=LOGIN#015#0121 OK Capability completed.#015
 Apr  9 16:04:16 lb1-imap in.imapproxyd[4125]: Attempt_STARTTLS(): Enabling STARTTLS.
 Apr  9 16:04:16 lb1-imap in.imapproxyd[4125]: Doing a peer verify
 Apr  9 16:04:16 lb1-imap in.imapproxyd[4125]: verify error:num=18:self signed certificate
 Apr  9 16:04:16 lb1-imap in.imapproxyd[4125]: ParseBannerAndCapability: Attempting to parse capability string: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN#015#0121 OK Capability completed.#015#012pleted.#015
 running in a centos 6.x 64bits updated box

 up-imapproxy-1.2.8-0.3.20130726svn14389.el6.x86_64
 Thanks!

  

[SM-imapproxy] install squirrelmail with gmail, windows 7

[leandro b. <lea...@bu...>]

When i try to enter on gmail with squirrelmail, this message is appear. I
dont found the solution
i am running windows 7

Re: [SM-imapproxy] Vulnerability for X509 Certificate Verification

[<ma...@ne...>]

Jerry Zhang <jer...@gm...> wrote:

> We are a research group trying to use static analysis to find the unsafe
> usage of APIs. Could you please take a look at vulnerability about
> imapproxy?

I understand the code to verify the certificate is there, but it always
return success, even if it logs something wrong. 

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
ma...@ne...

[SM-imapproxy] Vulnerability for X509 Certificate Verification

[Jerry Z. <jer...@gm...>]

Hello,

We are a research group trying to use static analysis to find the unsafe usage of APIs.
Could you please take a look at vulnerability about imapproxy?
https://bugs.launchpad.net/ubuntu/+source/up-imapproxy/+bug/1374729

Thanks,
Jerry

Re: [SM-imapproxy] compile error on 64 bit RHEL/CentOS

[<ma...@ne...>]

David Severance <se...@uc...> wrote:

> > src/main.c: In function 'main':
> > src/main.c:744: warning: cast to pointer from integer of different size
> 
> I believe the problem has to do with improper casting of the int 
> clientsd to a void pointer. 

Une long. They are 32 bits on i386 and 64 bit on amd64.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
ma...@ne...

[SM-imapproxy] compile error on 64 bit RHEL/CentOS

[David S. <se...@uc...>]

I have noticed that if I try to compile on 64 bit machines (versus 32bit 
systems) I get this warning:

> src/main.c: In function ‘main’:
> src/main.c:744: warning: cast to pointer from integer of different size

I believe the problem has to do with improper casting of the int 
clientsd to a void pointer. It's been awhile since I coded C so I could 
be wrong but I think this needs an adjustment. This is the last thing to 
sort out before I can deploy a fully native 64 bit software stack.

thanks,
David

-- 
David Severance
Enterprise Unix Services
Office of Information Technology

[SM-imapproxy] Fail to start imapproxy on server with two network interfaces ?

[Administrateur s. <sys...@sa...>]

Hi,
I'm trying to start imapproxy on a freebsd-10 server with two network
interfaces. I bind imapproxy to my LAN IP addresses, wich are attached
to one of my network interface.
Unfortunately, imapproxy failed to start with the following error :
ImapProxy[78998]: [DEBUG 78998] setup_listener(): bind() error (m)

I tried to install and run imapproxy on two others freebsd-10 server
with one network interface : it works
I tried to install and run imapproxy on one other freebsd-10 server with
two network interfaces : it failed…

Do you think that imapproxy is not handling corretly the case where
there are more than on network interface ?

Thanks in advance for your help !

Regards,
Stan.

Re: [SM-imapproxy] Can imap proxy be used to reduce/limit number of connections to backend mail server?

[Paul L. <pa...@sq...>]

On Mon, Apr 28, 2014 at 12:03 PM, Nathan Neulinger <nn...@ne...> wrote:
> I'm finding that with a combination of multiple client devices that I'm more and more frequently hitting up against
> google's "maximum number of connections" limits. Thought was that maybe there would be a way to leverage imap proxy to
> do the reverse - take a bunch of attempted connections, and try to round-robin/LRU them in some way.
>
> Even something as ugly as "limit conns to N, if a new connection came in, and last command on one of the other channels
> was IDLE, drop that connection and open new connection to backend server".
>
> Obviously a full-on interleaving would be non-trivial.
>
> Any ideas?

IMAPProxy wasn't really built with that in mind...  Because it holds
connections for each and every client separately, and has no
mechanisms to compare connections, I can't see that it would be
trivial to do what you want.  The only thing I could suggest is trying
it with the select cache turned on to see if that limits the number of
trips to the destination server (although that's more going to help
with webmail clients than desktop/mobile ones).

-- 
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

[SM-imapproxy] Can imap proxy be used to reduce/limit number of connections to backend mail server?

[Nathan N. <nn...@ne...>]

I'm finding that with a combination of multiple client devices that I'm more and more frequently hitting up against 
google's "maximum number of connections" limits. Thought was that maybe there would be a way to leverage imap proxy to 
do the reverse - take a bunch of attempted connections, and try to round-robin/LRU them in some way.

Even something as ugly as "limit conns to N, if a new connection came in, and last command on one of the other channels 
was IDLE, drop that connection and open new connection to backend server".

Obviously a full-on interleaving would be non-trivial.

Any ideas?

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       nn...@ne...
Neulinger Consulting                   (573) 612-1412