Re: [WISPA] Re-evaluating our anti-spam solution

2010-01-01 Thread John Thomas
What are the issues with your Barracuda? John Ugo Bellavance wrote: On 2009-07-13 20:08, Don Grossman wrote: It seems time to take a look at our anti-spam solution. Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts to work

Re: [WISPA] Re-evaluating our anti-spam solution

2009-12-30 Thread Ugo Bellavance
On 2009-07-13 20:08, Don Grossman wrote: It seems time to take a look at our anti-spam solution. Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts to work with Barracuda can not be resolved. I tend to use a mix of: -

Re: [WISPA] Re-evaluating our anti-spam solution

2009-12-30 Thread Michael Baird
We have a mailfoundry, no failures in the 1.5 years it's served as a gateway, plus no per domain/user fees. Development seems to have stalled on it though, no new OS releases in a year. It is cost effective, reliable and flexible and easily managed, coming from the MailScanner/Spamassassin

Re: [WISPA] Re-evaluating our anti-spam solution

2009-12-30 Thread Randy Cosby
We still love (and beat the heck out of) can-it from Roaring Penguin. http://www.roaringpenguin.com/ On 12/30/2009 2:58 PM, Michael Baird wrote: We have a mailfoundry, no failures in the 1.5 years it's served as a gateway, plus no per domain/user fees. Development seems to have stalled on it

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-24 Thread Blake Covarrubias
We're running the setup (Postfix, SA, amavisd-new, FuzzyOCR) except with Cyrus instead of dbmail. Works great. -- Blake Covarrubias On Jul 20, 2009, at 6:37 AM, Curtis Maurand wrote: I've been running Postfix, amavisd-new, spamassassin, dbmail for many years and its been rock solid. I've

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-20 Thread Eric Rogers
[mailto:wireless-boun...@wispa.org] On Behalf Of Curtis Maurand Sent: Monday, July 20, 2009 9:37 AM To: WISPA General List Subject: Re: [WISPA] Re-evaluating our anti-spam solution I've been running Postfix, amavisd-new, spamassassin, dbmail for many years and its been rock solid. I've also added

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-18 Thread Marco Coelho
We really like Postfix, courier-imap, amavisd-new (includes spamassassin), mailgraph, spamakazi, clam-av combo We have it sitting on a 8 way machine with raid 0+1 15K SCSI drives with spares. Solid. Marco Argon Technologies Inc. On Wed, Jul 15, 2009 at 9:09 PM, John

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-15 Thread John Thomas
Please see my responses inline Jeremy Parr wrote: 2009/7/14 David E. Smith d...@mvn.net: Don Grossman wrote: It seems time to take a look at our anti-spam solution. Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-15 Thread John Thomas
I know of Barracudas that the only time they get rebooted is for firmware updates. They can run for months without a reboot, but usually the firmware updates have useful stuff in 3-6 months that requires a firmware upgrade. John Charles Wyble wrote: David E. Smith wrote: What kind of

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Olufemi Adalemo
-ed.com; WISPA General List Subject: Re: [WISPA] Re-evaluating our anti-spam solution The difference with Postini compared to an in-house box is Postini stops the incoming SPAM before it uses any bandwidth on our backbone. Last time I checked (over a year ago), it was saving us 3-4Mbps of traffic (24x7

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Jason Hensley
: [WISPA] Re-evaluating our anti-spam solution I have rather different anti-spam requirements For a while now I've been looking for a solution to stop users on a network sending spam via web-based email like Hotmail, Gmail and Yahoo by scanning the outgoing HTTP POST command on a proxy server based

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Randy Cosby
: Tuesday, July 14, 2009 5:55 AM To: 'WISPA General List' Subject: Re: [WISPA] Re-evaluating our anti-spam solution I have rather different anti-spam requirements For a while now I've been looking for a solution to stop users on a network sending spam via web-based email like Hotmail, Gmail

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread David E. Smith
Don Grossman wrote: It seems time to take a look at our anti-spam solution. Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts to work with Barracuda can not be resolved. Barracuda is helpful but like to point at other

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Jeremy Parr
2009/7/14 David E. Smith d...@mvn.net: Don Grossman wrote: It seems time to take a look at our anti-spam solution.  Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts to work with Barracuda can not be resolved.  Barracuda is

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Charles Wyble
+1 for postfix and the mentioned add ons. 3k and it's not redundant? Good grief. Though it's not a few hours. https://help.ubuntu.com/community/Postfix Copy/paste from the howtos. Takes like 30 minutes.

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Charles Wyble
Scottie Arnett wrote: Agreed! Been using Postfix since I told Postini to take a hike. They both use a modified version of Postfix and related add-ons. You can make a spam machine out of the cheapest hardware now. I presume you mean anti spam machine? :) I have been doing this for over

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Charles Wyble
Sent: 14 July 2009 05:40 To: sarn...@info-ed.com; WISPA General List Subject: Re: [WISPA] Re-evaluating our anti-spam solution The difference with Postini compared to an in-house box is Postini stops the incoming SPAM before it uses any bandwidth on our backbone. Last time I checked (over

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Charles Wyble
David E. Smith wrote: What kind of problems were/are you having with your Barracudas? On the (exceedingly rare) occasion that ours do anything odd, rebooting them almost always clears it up. One should NEVER have to reboot a mail server, outside of a kernel upgrade (and even then one can

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Mike Hammett
; WISPA General List wireless@wispa.org Subject: Re: [WISPA] Re-evaluating our anti-spam solution I've been a huge fan of Postfix combined with Maia Mailguard (maiamailguard.com I think). Allows users to modify their own settings, white lists, blacklists, see little graphs on blocked spam

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Tom DeReggi
General List' Subject: Re: [WISPA] Re-evaluating our anti-spam solution I have rather different anti-spam requirements For a while now I've been looking for a solution to stop users on a network sending spam via web-based email like Hotmail, Gmail and Yahoo by scanning the outgoing HTTP POST command

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-14 Thread Olufemi Adalemo
To: WISPA General List Subject: Re: [WISPA] Re-evaluating our anti-spam solution Block people from using those sites? Kick them off your network? Are these end users doing this? Or do they have bot infected machines using webmail to send spam in an automated fashion? If so then snort+clamav should do

[WISPA] Re-evaluating our anti-spam solution

2009-07-13 Thread Don Grossman
It seems time to take a look at our anti-spam solution. Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts to work with Barracuda can not be resolved. Barracuda is helpful but like to point at other things like DNS and

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-13 Thread Jeremy Parr
2009/7/13 Don Grossman d...@willitsonline.com: It seems time to take a look at our anti-spam solution.  Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts to work with Barracuda can not be resolved.  Barracuda is helpful but like to

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-13 Thread Jeremy Parr
2009/7/13 Jeremy Parr jeremyp...@gmail.com: 2009/7/13 Don Grossman d...@willitsonline.com: It seems time to take a look at our anti-spam solution.  Currently we are looking to replace out Barracuda due to ongoing issues with the box that after several attempts to work with Barracuda can not be

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-13 Thread reader
- Original Message - From: Jeremy Parr jeremyp...@gmail.com To: WISPA General List wireless@wispa.org Sent: Monday, July 13, 2009 5:28 PM Subject: Re: [WISPA] Re-evaluating our anti-spam solution 2009/7/13 Jeremy Parr jeremyp...@gmail.com: 2009/7/13 Don Grossman d...@willitsonline.com: It seems

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-13 Thread Scottie Arnett
Agreed! Been using Postfix since I told Postini to take a hike. They both use a modified version of Postfix and related add-ons. You can make a spam machine out of the cheapest hardware now. I have been doing this for over 3 years and have a much better customer satisfaction. Scottie

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-13 Thread Adam Kennedy
I've been a huge fan of Postfix combined with Maia Mailguard (maiamailguard.com I think). Allows users to modify their own settings, white lists, blacklists, see little graphs on blocked spam for their specific account in addition to allowing them to help train the system by going through copies

Re: [WISPA] Re-evaluating our anti-spam solution

2009-07-13 Thread Travis Johnson
The difference with Postini compared to an in-house box is Postini stops the incoming SPAM before it uses any bandwidth on our backbone. Last time I checked (over a year ago), it was saving us 3-4Mbps of traffic (24x7). I would guess now it's closer to 7-10Mbps of incoming SPAM flow that never