Latest version of IMAP Proxy has been out about one month. It's also been in
production use on our heavily loaded (lots of logins every second) servers
ebuild requires no modifications, simply rename the ebuild file to be
up-imapproxy-1.2.4.ebuild. Please upgrade. :)
Steps to Reproduce:
Created attachment 70539 [details]
An ebuild for up-imapproxy v1.2.4 (actually just renamed v1.2.3 ebuild). Since
there seems to be a significant lag in up-imapproxy ebuild maintenance, I'm
willing to take over it's maintenance. I need to keep myself and our servers
up-to-date with up-imapproxy, so I might as well keep it up-to-date in Portage.
Created attachment 73191 [details, diff]
Fix for string format specifier bug
Please add this fix to portage tree!
Since this is a security-related bug and a trivially fixed one, this should be fixed ASAP.
Thanks for the bug report.
1.2.4 with fix commited.
@security: haven't seen this bug before. Please, do what's needed.
Cleaning up so that it doesn't fall in the cracks
x86 please test and mark 1.2.4 stable
Has been working for me since last September... :-)
This really isn't working for me. I set up the config file, started the server, it said "OK", then just died. I tried from console and it didn't do anything. It provides no debug or log messages, so I can't tell exactly what the problem might be..
(In reply to comment #7)
> This really isn't working for me. I set up the config file, started the
> server, it said "OK", then just died. I tried from console and it didn't do
> anything. It provides no debug or log messages, so I can't tell exactly what
> the problem might be..
please post your /etc/imapproxy.conf .
Do you have an imap server listening on the port that you have set in server_port ?
funky configuration for what it actually want's as the server name..quite odd...I had the same issue as chris but tried something and it worked.
Stable on x86 (X_X) <---gets that for the funky config server name
Removed old versions and reopened this bug.
Ready for GLSA