It can be done quite easily.
Two options: Preferred: Configure webmail to send messages directly to the appliances. Alternatively: Install a dumb SMTP mailer on "D" that listens on a port other than 25. Configure that dumb-mailer to forward all mail to the appliances. Configure webmail to send messages to the dumb mailer's listening port. webmail -SMTP-> "D" dumb-mailer listening on tcp:125(example) -SMTP-> appliances via static SMTP route -SMTP-> back to "D" tcp:25 via static SMTP route for local deliveries -----Original Message----- From: ISP Lists [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 4:41 PM To: vchkpw@inter7.com Subject: [vchkpw] How to route local delivery through a separate SMTP spam scanner A customer has challenged whether this can be done... Anti-SPAM appliances "A", "B", and "C" are available on an internal LAN via DNS round-robin through SMTP at "appliance.example.com" VPOPMAIL server "D" is on the same LAN. Customer has had a few local accounts that had their password guessed and spammers sent spam through webmail. Soooooooo............ We're considering doing something inline to the delivery process that would 1) accept the authenticated user's email for remote/local delivery, 2) force that delivery off of box "D" to "A-C" over SMTP in ALL cases (not just remote), 3) Scan on "A-C", 4) return the inbound (local) mail back to "D" for further delivery to the locals. I realize this is pretty insane, but the customer isn't excited about adding a local spam daemon to "D" and would like to leverage the investment in the appliances "A-C" to control for local delivery abuses. The appliances are doing a nice job on SMTP scanning, but the vendor says that their appliance does not have a "port listener" (like a spamd daemon) that could answer a stream request - thus only SMTP will do. Ideas? THANKS! Dave. !DSPAM:48225904120501078378401!
