Brad Riemann:
> Thanks Viktor, I think I did figure out how to do this, but am
> getting odd pipelining errors when we add the xclient and new
> ehlo/helo headers.
>
> Jan 8 08:14:00 mta01 postfix/smtpd[16360]: connect from
> edge.dc1.domain.com[172.16.###.###]
> Jan 8 08:14:00 mta01 postfix/smtpd[16360]: improper command
> pipelining after EHLO from edge.dc1.domain.com[172.16.###.###]:
> XCLIENT NAME=wsip-98-190-218-47.ga.at.cox.net ADDR=98.190.218.47\r\nEHLO
> wsip-98-190-218-47.ga.at.cox.
>
> I'm not familiar with the pipelining error, I've done some searching
> and usually people have issues with it if the client doesn't
> disconnect at the end of the message, not at the top of the message..
> Any thoughts?
This suggests that the load balancer sends
EHLO something\r\nXCLIENT NAME=wsip-98-190-218-47.ga.at.cox.net
ADDR=98.190.218.47\r\nEHLOwsip-98-190-218-47.ga.at.cox.net\r\n
I don't know what other people do, but you should be able
to send the XCLIENT command without preceding it with EHLO.
The "smtpd_helo_required" applies to MAIL and ETRN.
Wietse
