Author Topic: avastrelay for outgoing mail?  (Read 6052 times)

0 Members and 1 Guest are viewing this topic.

bbell2000

  • Guest
avastrelay for outgoing mail?
« on: September 18, 2004, 03:19:41 PM »
I just installed Avast on my Linux server and have it configured as follows:

    qmail running on port 25 relays inbound mail to avastrelay listener
    avastrelay relays scanned mail to second instance of qmail

In my previous configuration using a different mail scanner, I configured internal mail clients to use the av port as their outbound SMTP server... e.g., I want to scan both inbound and outbound mail.  Since installing avastrelay, mail clients are getting connection errors when they try to send mail.

The mailscanner section of avastd.conf contains the following line:

    listen = /var/run/avast4mailscanner.sock

The switches variable in /etc/init.d/avastrelay looks like this:

    -i 192.168.2.66:725 -I 192.168.2.66:825 -a /var/run/avast4mailscanner.sock -l var/log/avast4/avastrelay -u avrelay -t 60

The SMTP port for mail clients is 725.

What do I need to change to ensure that outbound mail is scanned?

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31118
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re:avastrelay for outgoing mail?
« Reply #1 on: September 18, 2004, 03:24:55 PM »
There is another thread about a relay problem, have you already checked there? It may have some usefull info/suggestions.
http://forum.avast.com/index.php?board=5;action=display;threadid=6509

bbell2000

  • Guest
Re:avastrelay for outgoing mail?
« Reply #2 on: September 18, 2004, 06:56:08 PM »
I saw that post and I don't think it's related.  Seems like the OP figured out that particular problem was caused by the size of an attachment.

I did run the telnet test, though... and it works ok.

But when I configure my email client to use the same IP/port for SMTP, the connection is refused.

At that point, the problem gets worse... avastrelay stops relaying completely... I had to restart the daemons to get everything working again.

Sure would like to figure out how to solve this problem.