Attached is up-imapproxy-1.2.ebuild and the init script it references. The main use of an IMAP proxy is to cache connections to an IMAP server, so that making many connections in rapid succession does not require constant re-authentication. This yields performance gains (and cleaner logs) for webmail applications and the like. Recommend placing inside net-mail/. The ebuild supports passing --with-krb5 to the configure script, but since none of my machines use Kerberos, this is untested.
Created attachment 18401 [details] up-imapproxy-1.2.ebuild
Created attachment 18402 [details] files/init-script-r1
It's been two and a half weeks, with no response -- not an acknowledgement, not a "this doesn't work because such and such", just silence. Any reason this isn't in the Portage tree yet?
delta407: don't take this the wrong way, we appreciate every ebuild submission, but we are hugely understaffed to bring in every submission as quickly as we would like to. Leave it, keep it in your local portage overlay for now, and keep this bug up to date with new releases, and we'll get to it in time.
*** Bug 31622 has been marked as a duplicate of this bug. ***
I added a different (my own/cleaner) version of the ebuild for this project into portage. Thanks for the submission!