Just to clarify for all:
1) Create the SMTPROUTES file (filename actually all lower-case) that
points to your REAL mail server
2) Add YOURDOMAIN.TLD (again, actually lower case letters) to your
RCPTHOSTS file
3) MAKE SURE that YOURDOMAIN.TLD does NOT appear in your LOCALS file(s)
4) Test with a locally originated message to confirm mail flow
5) Change your DNS NS records to point to the NEW mail "filter" server
6) After a day or so, change your REAL mail host to accept inbound
connections ONLY from the filter server
NOTE: items 4-6 can also be done all-at-once if you're behind a
NAT-Firewall and are still using the same PUBLIC IP for your MX.
Enjoy!
Dan McAllister
PS: A more interesting question I'm working on -- I want to make QMT a
SPAM filter -- only I want the NON-SPAM to be forwarded to the real
server (Exchange), while the SPAM is held back (users can access SPAM
messages via web-mail or a separate IMAP login).
Anyone have any ideas on how to make the forward only apply to HAM?
On 3/11/2013 3:14 AM, Am Am wrote:
Thanks Eric, it uses Xinetd. FYI, it is a very old version of
parallels automation qmail which has been customized, also it is
distributed. It is very risky if I install a third-party application
and this is why I decided to have a mail filter layer.
------------------------------------------------------------------------
*From:* Eric Shubert <[email protected]>
*To:* [email protected]
*Sent:* Sunday, 10 March 2013, 22:23:42
*Subject:* [qmailtoaster] Re: How to use qmail toaster as a Mail
Filter Layer
On 03/10/2013 07:30 AM, Eric Broch wrote:
> On 3/10/2013 1:46 AM, Am Am wrote:
>> Hi,
>>
>> We are using an old customized qmail but receiving too many spam
>> messages recently, I hope to find a way to use a Mail Filter Layer
>> with qmailtoaster with spamdyke and other spam filtering services.
>>
>> Thnaks
> Point all incoming mail from your firewall to the new qmail filter layer
> server and add the proper setting in it's /var/qmail/control/smtproutes
> file. Something like:
>
> mydomain.com:X.X.X.X where X.X.X.X is the ip of your customized
qmail server
>
> Make sure your rcpthosts file doesn't have mydomain.com in it.
Correct me if I'm wrong, but I think you *do* want mydomain.com in the
rcpthosts file for both servers. If you didn't have mydomain.com in
your filtering server, the only way it could receive email is from
authenticated connections. No?
> http://wiki.qmailtoaster.com/index.php/Smtproutes
>
>
Am, while a separate filtering host is possible, I wouldn't go that
route. A somewhat unusual aspect of spamdyke is that it will actually
*reduce* the load on your qmail host, so adding more processing
capacity would be a waste. Spamdyke integrates rather seamlessly with
qmail, and should easily work with any ol' version/configuration of qmail.
You could even give the qtp-install-spamdyke script a try. (Note, many
other tools in the qmailtoaster-plus package will work with non-QMT
hosts as well). The only thing you'll likely need to adjust a bit is
the run file for qmail-smtpd, presuming your qmail configuration uses
supervise and ucspi-tcp which most do. Even if you use xinetd though,
spamdyke can be used directly on your qmail host.
If you have a run file, you can post it here and we'll help you get it
fitted for spamdyke.
-- -Eric 'shubes'
--
IT4SOHO, LLC
PO Box 507
St. Petersburg, FL 33731-0507
CALL TOLL FREE:
877-IT4SOHO
We have support plans for QMail!
