Quanah Gibson-Mount:
> Hi,
>
> We have customers testing our next Zimbra release, which includes support
> for postscreen. 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
> 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]
> 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? Anyone have an idea how to work
> around this? Clearly having their spam appliance be non-functional isn't a
> great start. ;)
Running Postscreen after a spam appliance is pointless. It is a
spambot detector (in more sophisticated words, it implements IP
address-based reputation).
Wietse
