The only issue we encountered using the nginx Mail auth api was in finding
out what encoding is used for the header values. In Java we currently use
the following to decode the password

password = URLDecoder.decode(password.replaceAll("\\+", "%2b"), "UTF-8");

My understanding is that nginx encodes some characters in the typical %XX
form (where X is a hexadecimal character) but leaves + as +, so when
decoding, + is incorrectly decoded to space. That’s what the code above
resolves.

On Wed, Nov 13, 2019 at 7:37 PM Patrick <201904-nginx@jslf.app> wrote:

> On 2019-11-13 20:00, nsclick@gmx.de wrote:
> > I would like to setup a Nginx mail proxy which handles IMAP and SMTP for
> two different mail domains and two different backend servers (one server
> for each of the domains).
>
> The docs have a good example at:
>
> https://www.nginx.com/resources/wiki/start/topics/examples/imapauthenticatewithapacheperlscript/
>
> Users need to login with "username@foo.com" or "username@bar.com"
> otherwise name collisions will occur...
>
> `Auth-User' will have the username, so match on the domain part to route
> the user to the correct server.
>
>
> Patrick
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx