Paul Theodoropoulos wrote:
you could get away with two stages - run a spam filtering smtpd on an
alternate port on your vpopmail server - i use port 26 - then you can
use smtproutes on the primary/secondary MX to feed to the different
ports, eg:
iwantspam.com:myvpopmailserver.com:25
At 03:38 AM 9/11/2003, Martin Horsley wrote:
Paul Theodoropoulos wrote:
you could get away with two stages - run a spam filtering smtpd on an
alternate port on your vpopmail server - i use port 26 - then you can use
smtproutes on the primary/secondary MX to feed to the different ports, eg:
On Thursday, September 11, 2003, at 08:59 AM, Paul Theodoropoulos
wrote:
i also run a *third* smtpd for customers who are on networks that
block outbound port 25, i also run one called smtpd-2525, which is the
alternate port i offer those customers to use to bypass the blocking.
There's
At 09:54 AM 9/11/2003, Tom Collins wrote:
On Thursday, September 11, 2003, at 08:59 AM, Paul Theodoropoulos wrote:
i also run a *third* smtpd for customers who are on networks that block
outbound port 25, i also run one called smtpd-2525, which is the
alternate port i offer those customers to
Paul Theodoropoulos wrote:
At 09:54 AM 9/11/2003, Tom Collins wrote:
On Thursday, September 11, 2003, at 08:59 AM, Paul Theodoropoulos
wrote:
i also run a *third* smtpd for customers who are on networks that
block outbound port 25, i also run one called smtpd-2525, which is
the alternate
i handle this by using a three stage transport - primary and secondary MX
feed mail that is to be filtered on to a
dedicated spamassassin/viruschecker server via /var/qmail/smtproutes.
Those domains that i don't want to filter i just push the mail directly to
the vpopmail server, also via
