Comments on: How to Use Sagator, an Antivirus/Antispam Gateway, to Protect Your Mail Server

By: Greg G. Villegas

Greg G. Villegas — Sat, 20 Jun 2020 11:20:47 +0000

Hi,

What is the recommended memory for this setup?

By: Jesus Miguel Otero

Jesus Miguel Otero — Sat, 27 Jan 2018 14:45:50 +0000

In reply to Anonymous.

Hello

Not ready….

The first line -o content_filter=

error when I restart the service

any idea?

By: Alex Wieder

Alex Wieder — Tue, 07 Nov 2017 23:36:50 +0000

What is the point of installing Sagator when you can simply use Spamassassing (and also ClamAV) by themselves?

What’s the advantage of adding yet another component into the mix?

Thanks!

By: Eric Evans

Eric Evans — Mon, 13 Feb 2017 09:25:37 +0000

My end solution was to use ScrolloutF1. It’s a Debian flavor and has a downloadable iso that you load as a second machine, either vm or physical. My incoming mail goes through Scrollout then to my mail server. I didn’t feel the need to use it for out going. It seems to be working very well.

You can run outgoing mail through it also but at this point I didn’t feel the need to.

Just an alternative solution I thought I would share.

By: Ganski

Ganski — Sat, 11 Feb 2017 11:39:33 +0000

I tried it in a production server running Slackware. Recompiled from source. Under SCANNERS = [ ….. ] array, it looks that alternatives() is called on with its input parameters, but it is commented out.

It throws me error when I started sagator. So what I did, I comment out #alternatives( and its matching ), below. In your screenshot, you only show ‘buffer2mbox(CLAMAV)’ commented out.