I'm trying to set up a qmail front-end smtp server to scan all mail for
seacove.net using qmail-scanner (scan4virus).
I was hoping to direct all mail for seacove.net to the front-end
machine(vscanner1.seacove.net) using an MX.record then route the mail on to
my primary server (mail.seacove.net) using control/smtproutes
The virus scanner and qmail is running fine on the front-end machine. Both
the front end and primary mail hosts are running qmail-1.03 under tcpserver.
My MX record for seacove.net looks like this:
IN MX 10 vscanner1.seacove.net
vscanner1 has seacove.net in its rcpthosts, but not in its locals, and it
scans the mail and sends it on to mail.seacove.net because of an entry:
seacove.net:mail.seacove.net
in control/smtproutes. Now mail.seacove.net has seacove.net is in locals,
so it accepts the mail and sends it to the maildirs. So this setup works
just as I had envisioned it except for local mail from seacove.net to
seacove.net
I can't think of any way to route the local mail first to vscanner1 then
accept it the second time around when it comes back from vscanner1. If I
remove seacove.net from control/locals on mail.seacove.net, I believe qmail
will use the MX record and send local mail for seacove.net on to vscanner1,
which creates a looping route, because mail.seacove.net will never accept
the mail. Same if I use control/smtproutes, because I believe it will just
keep routing it back to vscanner1. In my case, changing the MUA settings to
use vscanner1 for outgoing mail is not a viable option.
Basically, I'm looking for a way for mail.seacove.net to send local mail
for seacove.net to vscanner1.seacove.net then have it sent back to
mail.seacove.net where it will be treated as a local.
Am I just wasting my time trying to do this or overlooking some obvious way
of treating this problem? Any suggestions?
Thanks in advance,
Dennis Duval
