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

Best Affordable Linux and WordPress Services For Your Business
Outsource Your Linux and WordPress Project and Get it Promptly Completed Remotely and Delivered Online.

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.45/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Gabriel Cánepa

Gabriel Cánepa is a GNU/Linux sysadmin and web developer from Villa Mercedes, San Luis, Argentina. He works for a worldwide leading consumer product company and takes great pleasure in using FOSS tools to increase productivity in all areas of his daily work.

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

11 Responses

  1. Alex Wieder says:

    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?


  2. Eric Evans says:

    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.

  3. Ganski says:

    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.

  4. Anonymous says:

    In the you commented out:

    # smtp inet n - n -- smtpd

    This will stop postfix from listening on port 25. Resulting in the machine no longer accepting email coming in on the standard email port and it will no longer receive email from external.
    The should look more like this:

    # ==========================================================================
    # service type  private unpriv  chroot  wakeup  maxproc command + args
    #               (yes)   (yes)   (yes)   (never) (100)
    # ==========================================================================    inet n - n - 30 smtpd
      -o content_filter=
      -o local_recipient_maps=
      -o relay_recipient_maps=
      -o mynetworks=
      -o mynetworks_style=host
      -o smtpd_restriction_classes=
      -o smtpd_client_restrictions=
      -o smtpd_helo_restrictions=
      -o smtpd_sender_restrictions=
      -o smtpd_data_restrictions=
      -o smtpd_recipient_restrictions=permit_mynetworks,reject
      -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks
      -o smtpd_use_tls=no
    smtp      inet  n       -       n       -       -       smtpd 
  5. Eric Evans says:

    When I make the changes to the it shuts email down. As soon as I undo those changes, email works perfectly.

    It seems there is something needed or missing from the config. This is a “real world” email server and I can’t have it down.

    I need some direction to get sagator integrated with postfix and the email flowing properly.

    Any suggestions would be greatly appreciated.

  6. Eric Evans says:

    This may be a dumb question nut here goes; Should I be able to use Sagator and spamassasin together or chose on or the other?

    I have spamassasin working, but when I try to config Sagator, it stops everything.
    Just need some clarification.

  7. Florian says:

    Sorry to my english, i’m french.
    Sagator can not send me the emails received. No error message, it is as if I did not receive it when I send it. Gmail / Live tells me this error message: The recipient server did not accept our requests to connect. Learn more at [ XXX.XXX.XX.XXX: generic :: failed_precondition: connect error (0): error]
    An idea ? If I remove the changes in postfix, all messages reach me.

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.