On Thu, Mar 31, 2016 at 03:15:11PM -0700, Quanah Gibson-Mount wrote: > We have customers testing our next Zimbra release, which includes > support for postscreen.
Very nice! Congratulations. > By default, postscreen is not set to take any actions. > However, one tester found that even with this being the case, connections > from their Barracuda Spam Firewall are being rejected thusly: > > Mar 11 11:15:09 webmail postfix/postscreen[5234]: CONNECT from > [X.X.X.X]:38752 to [Y.Y.Y.Y]:25 > Mar 11 11:15:09 webmail postfix/postscreen[5234]: PREGREET 36 after > 0 from [X.X.X.X]:38752: EHLO cabernet.example.com\r\n Yikes. > Mar 11 11:15:10 webmail postfix/smtpd[5235]: connect from > cabernet.example.com[X.X.X.X] > Mar 11 11:15:10 webmail postfix/smtpd[5235]: lost connection after > EHLO from cabernet.example.com[X.X.X.X] "Lost connection", the client hung up on postscreen or the TCP connection was otherwise disrupted. Causality is unknown unless logged on the client side. > Mar 11 11:15:10 webmail postfix/smtpd[5235]: disconnect from > cabernet.example.com[X.X.X.X] ehlo=1 commands=1 > > Is this a known issue with Barracuda? No idea, but yikes, PREGREET? > Anyone have an idea how to work around this? Try adding the client to postscreen_access_list? > Clearly having their spam appliance be non-functional isn't a > great start. ;) I think I'd choose Barracuda OR postscreen, not sure how both of them together could be useful? -- http://rob0.nodns4.us/ Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
