/permalink.gmane.org/gmane.comp.web.haproxy/8881 /
http://www.postfix.org/postconf.5.html#postscreen_upstream_proxy_protocol)?
Because in that case it would definitely be expected for postfix to be
using the connection information from the frontend.
Mit freundlichen Gruessen,
Lukas Erlacher
--
R
Prompted by the "gmail servers requiring postscreen_access whitelisting" thread
I looked at http://www.postfix.org/postscreen.8.html.
There is an erroneous (right??) double negative:
>The optional "after 220 server greeting" tests involve postscreen(8)'s
>built-in SMTP protocol
Hi,
this is not a postfix problem. Furthermore it is fully covered in the
dovecot docs.
You need to put the dovecot-lmtp socket into /var/spool/postfix/private.
This means the unix_listener must get the path to that. See here:
http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP
Also note tha
Thanks for the prompt support! Will you be merging this?
In the next 3.1 development release, and in a month or so, in the next
stable releases (2.9 .. 3.0).
Wietse
That's great to hear!
Best,
Luke
smime.p7s
Description: S/MIME Cryptographic Signature
Hi,
Please try this.
Wietse
[patch]
Works like a charm! I couldn't just patch our live server of course but I
grabbed the ubuntu 14.04 postfix 2.11.0 source package on a VM, and the
haproxy1.5 from trusty-backports and it works.
Thanks for the prompt support! Will you be merging t
Thanks, I will try that!
Best,
Luke
Hello,
I am trying to put haproxy in front of postfix and utilise the proxy protocol
to get accurate client IPs.
This works fine for all unencrypted / starttls based listeners, but not for
tls-wrapped listeners using smtpd_tls_wrappermode.
This is the haproxy configuration:
frontend ft_smtps
