# Adding imapproxy to improve performance of webmail client

**URL:** <https://discourse.mailinabox.email/t/adding-imapproxy-to-improve-performance-of-webmail-client/11357>\
**Category:** Improvements\
**Created:** [January 9, 2024, 9:47pm UTC](https://discourse.mailinabox.email/t/adding-imapproxy-to-improve-performance-of-webmail-client/11357 "2024-01-09T21:47:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmonty14](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/c/77aa72/32.png) [@cmonty14](https://discourse.mailinabox.email/u/cmonty14)\
**Post date:** [January 9, 2024, 9:47pm UTC](https://discourse.mailinabox.email/t/adding-imapproxy-to-improve-performance-of-webmail-client/11357/1 "2024-01-09T21:47:43Z")

</div>

Hi,  
I came accross this statement in [Debian](https://packages.debian.org/de/sid/imapproxy):  
_IMAP Proxy was written to compensate for webmail clients that are unable to maintain persistent connections to an IMAP server. Most webmail clients need to log in to an IMAP server for nearly every single transaction. This behaviour can cause tragic performance problems on the IMAP server._

If this statement is true, why is Mail-in-a-Box not including this function in its deployment?

THX

---

<div class="post-metadata">

**Author:** ![KiekerJan](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/kiekerjan/32/2339_2.png) [@KiekerJan](https://discourse.mailinabox.email/u/KiekerJan)\
**Post date:** [January 10, 2024, 9:22am UTC](https://discourse.mailinabox.email/t/adding-imapproxy-to-improve-performance-of-webmail-client/11357/2 "2024-01-10T09:22:05Z")

</div>

Well, the simple answer is that no-one did the work to include it 😉

To elaborate a bit on that:

- Are you having issues with IMAP performance? I wonder how many MiaB deployments are out there that are stretching the capacity of the Dovecot software on modern hardware.
- Imapproxy seems to be unmaintained. The latest upstream release is from 2017, and the [home page](http://www.imapproxy.org/) is not reachable.

---

<div class="post-metadata">

**Author:** ![cmonty14](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/c/77aa72/32.png) [@cmonty14](https://discourse.mailinabox.email/u/cmonty14)\
**Post date:** [January 11, 2024, 8:30pm UTC](https://discourse.mailinabox.email/t/adding-imapproxy-to-improve-performance-of-webmail-client/11357/3 "2024-01-11T20:30:12Z")

</div>

I agree to your concerns.  
On the one hand side, the use-case for imapproxy to improve performance of webmail client makes sense.  
On the other hand side, imapproxy is not maintained anymore.

However I would like to address this question:  
How can I modify imap port in Roundcube’s webmail configuration?

---

<div class="post-metadata">

**Author:** ![system](https://discourse.mailinabox.email/uploads/default/original/2X/4/4d0933d13c456b7e57f296aa6cc344525b6f0c70.png) [@system](https://discourse.mailinabox.email/u/system)\
**Post date:** [March 10, 2024, 9:47pm UTC](https://discourse.mailinabox.email/t/adding-imapproxy-to-improve-performance-of-webmail-client/11357/4 "2024-03-10T21:47:52Z")

</div>

This topic was automatically closed after 61 days. New replies are no longer allowed.