Error: insufficient authorization

Maxim Dounin mdounin at
Tue Feb 8 17:25:03 MSK 2011


On Tue, Feb 08, 2011 at 09:05:44AM -0500, HajoLOcke wrote:

> i do some tests with nginx and the mail proxy modules. running imap/pop3
> seems to work. Now i try with smtp.
> My auth-server is a little php-script:
> <?
> header("HTTP/1.0 200 OK");
> header("Auth-Status: OK");
> header("Auth-Server:");
> header("Auth-Port: 25");
> header("Auth-Protocol: smtp");
> header("Auth-User: myusername");
> header("Auth-Pass: mypass");
> ?>
> When testing smtp by telnet i got: 451 4.3.2 Internal server error after
> auth login.
> and in log:
> 2011/02/08 14:04:42 [error] 27740#0: *23 upstream sent invalid response:
> "550 5.7.0 Error: insufficient authorization" while reading response
> from upstream, client: ip.ip.ip.ip, server:, login:
> "myusername", upstream:
> what else is needed?

nginx doesn't attempt authentication against SMTP backends.  You 
have to allow unauthenticated access from nginx on your SMTP 

> i have 2 more questions.
> how to provide a basic log for mail-proxying? i only got server-errorlog
> to work.

That's the only logging available.

> i read that nginx in smtp-proxy mode wants to do the complete auth-stuff
> and needs an "open" smtp-engine behind. This is not what i like. I would
> like that nginx is just transfering sessions to assigned host and let
> the real smtp-engine(postfix) let do the auth stuff. with pop/imap proxy
> ngingx is working like this but not with smtp. is this possible with
> nginx? 


Maxim Dounin

More information about the nginx mailing list