Re: Issues with postscreen and barracuda spam firewall

2016-04-01 Thread Wietse Venema
Quanah Gibson-Mount: > --On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema > wrote: > > >> 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. ;) >

Re: Issues with postscreen and barracuda spam firewall

2016-04-01 Thread Viktor Dukhovni
On Fri, Apr 01, 2016 at 10:36:17AM -0700, Quanah Gibson-Mount wrote: > --On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema > wrote: > > >>Is this a known issue with Barracuda? Anyone have an idea how to work > >>around this? Clearly having their spam appliance be

Re: Issues with postscreen and barracuda spam firewall

2016-04-01 Thread Quanah Gibson-Mount
--On Friday, April 01, 2016 11:36 AM -0700 Quanah Gibson-Mount wrote: --On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema wrote: Is this a known issue with Barracuda? Anyone have an idea how to work around this? Clearly having their spam

Re: Issues with postscreen and barracuda spam firewall

2016-04-01 Thread jasonsu
> > Running Postscreen after a spam appliance is pointless. It is a > > spambot detector (in more sophisticated words, it implements IP > > address-based reputation). > > Ok. But I still would like to know where in the stack the problem is. > Right now, they are simply testing a release

Re: Issues with postscreen and barracuda spam firewall

2016-04-01 Thread Quanah Gibson-Mount
--On Thursday, March 31, 2016 9:15 PM -0400 Wietse Venema wrote: 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

Re: Issues with postscreen and barracuda spam firewall

2016-03-31 Thread Wietse Venema
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

Re: Issues with postscreen and barracuda spam firewall

2016-03-31 Thread Quanah Gibson-Mount
--On Thursday, March 31, 2016 6:57 PM -0500 "/dev/rob0" wrote: Anyone have an idea how to work around this? Try adding the client to postscreen_access_list? I asked them if it was in mynetworks, but they haven't responded yet. I'll ask again. ;) Clearly having their

Re: Issues with postscreen and barracuda spam firewall

2016-03-31 Thread /dev/rob0
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

Issues with postscreen and barracuda spam firewall

2016-03-31 Thread 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