On 27 May 2013 08:40, Vit Dua <[email protected]> wrote: > > The log also said: > > May 27 14:39:11 localhost haproxy[1278]: Proxy ft_postfix started. > May 27 14:39:11 localhost haproxy[1278]: Server ft_postfix/postfix01 is DOWN, > reason: Layer7 invalid response, info: "220-mail.mydomain.com ESMTP Postfix > (Ubuntu)", check duration: 1ms. 0 active and 0 backup servers left. 0 > sessions active, 0 requeued, 0 remaining in queue. > May 27 14:39:11 localhost haproxy[1278]: proxy ft_postfix has no server > available!
This is just a guess (it's been a while since I've run SMTP in anger!) but: You see the layer 7 response is "220-..."? Well, that hyphen in the 4th character usually means that this is a response that's going to spill over to the next line. Check out the example in http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol#Optional_extensions - see the difference between the 220 and the 250 responses? Only the /last/ 250 response is without a hyphen. I wonder if using the PROXY protocol is making the server respond with >1 line, which is making the smtpchk fail because the first reply it sees doesn't match "[0-9][0-9][0-9]<space>..." any more. Is the server definitely set up to accept the PROXY protocol? Remember that it's generally an SMTP protocol violation for the client to talk before receiving an SMTP banner - which is what (I /believe/) the PROXY protocol does. Which would suggest the server has to explicitly support the PROXY protocol. Either way - if it's just something being tickled in the postfix code which replies with a multi-line response or if it doesn't understand PROXY messages entirely - I'm afraid I don't have any suggestions for fixing it. You might need to dig further and let us know what you find! HTH, Jonathan -- Jonathan Matthews // Oxford, London, UK http://www.jpluscplusm.com/contact.html
