From spamassassin-talk-admin@lists.sourceforge.net Fri Aug 2 16:36:22 2002
Return-Path: <spamassassin-talk-admin@example.sourceforge.net>
Delivered-To: yyyy@localhost.netnoteinc.com
Received: from localhost (localhost [127.0.0.1])
by phobos.labs.netnoteinc.com (Postfix) with ESMTP id B0792440FF
for <jm@localhost>; Fri, 2 Aug 2002 11:35:32 -0400 (EDT)
Received: from phobos [127.0.0.1]
by localhost with IMAP (fetchmail-5.9.0)
for jm@localhost (single-drop); Fri, 02 Aug 2002 16:35:32 +0100 (IST)
Received: from webnote.net (mail.webnote.net [193.120.211.219]) by
dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g72EkRn01237 for
<jm-sa@jmason.org>; Fri, 2 Aug 2002 15:46:27 +0100
Received: from usw-sf-list2.sourceforge.net (usw-sf-fw2.sourceforge.net
[216.136.171.252]) by webnote.net (8.9.3/8.9.3) with ESMTP id PAA03896 for
<jm-sa@jmason.org>; Fri, 2 Aug 2002 15:25:01 +0100
Received: from usw-sf-list1-b.sourceforge.net ([10.3.1.13]
helo=usw-sf-list1.sourceforge.net) by usw-sf-list2.sourceforge.net with
esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 17adLZ-0002Mk-00; Fri,
02 Aug 2002 07:24:05 -0700
Received: from [63.88.78.2] (helo=[63.88.78.2]) by
usw-sf-list1.sourceforge.net with smtp (Exim 3.31-VA-mm2 #1 (Debian)) id
17adLG-0006gT-00 for <spamassassin-talk@lists.sourceforge.net>;
Fri, 02 Aug 2002 07:23:47 -0700
Received: from no.name.available by [63.88.78.2] via smtpd (for
usw-sf-lists.sourceforge.net [216.136.171.198]) with SMTP; 2 Aug 2002
14:11:33 UT
Received: by mail_server.Commonwealth.com with Internet Mail Service
(5.5.2653.19) id <PNLC6ZFX>; Fri, 2 Aug 2002 10:21:10 -0400
Message-Id: <FD5D2B1760DD594DA0B0C419E8DC809D04D4E7@omega.Commonwealth.com>
From: Jake Mohnkern <JMohnkern@COMMONWEALTH.COM>
To: "'spamassassin-talk@example.sourceforge.net'" <spamassassin-talk@example.sourceforge.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [SAtalk] Protect individual MS-Exchange mailboxes
Sender: spamassassin-talk-admin@example.sourceforge.net
Errors-To: spamassassin-talk-admin@example.sourceforge.net
X-Beenthere: spamassassin-talk@example.sourceforge.net
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
List-Help: <mailto:spamassassin-talk-request@example.sourceforge.net?subject=help>
List-Post: <mailto:spamassassin-talk@example.sourceforge.net>
List-Subscribe: <https://example.sourceforge.net/lists/listinfo/spamassassin-talk>,
<mailto:spamassassin-talk-request@lists.sourceforge.net?subject=subscribe>
List-Id: Talk about SpamAssassin <spamassassin-talk.example.sourceforge.net>
List-Unsubscribe: <https://example.sourceforge.net/lists/listinfo/spamassassin-talk>,
<mailto:spamassassin-talk-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://www.geocrawler.com/redir-sf.php3?list=spamassassin-talk>
X-Original-Date: Fri, 2 Aug 2002 10:21:07 -0400
Date: Fri, 2 Aug 2002 10:21:07 -0400
I rigged this up for testing before I commit to a sitewide rollout of
Spamassassin as an SMTP relay.
It is more work, but it avoids sitewide changes in mail delivery during the
early stages of testing.
On the Exchange server... (mail.yourdomain.com)
Create a new, private SMTP address (nomorespam@yourdomain.com) for the
mailbox you want to protect. Remove the old address.
Create a "custom recipient" with the old SMTP address
(spammedalot@yourdomain.com). Create another custom recipient pointing at a
local user on the Spamassassin box (killspam@filtermail.yourdomain.com).
Set the first custom recipient to forward all mail to the second custom
recipient. (must forward to another address in the Exchange directory)
On the Spamassassin box... (filtermail.yourdomain.com)
Set up a dummy user, in this case "killspam"
Give killspam a .forward file pointing to the final recipient's new, private
smtp address back on the Exchange server.
So the message flow is like this:
Mail arrives on the Exchange server mail.yourdomain.com for
spammedalot@yourdomain.com
spammedalot@commonwealth.com forwards it to
killspam@filtermail.yourdomain.com
Following the .forward file, the e-mail is then forwarded to
nomorespam@yourdomain.com
Wowie Zowie it works. The first address I protected was myself, the second
one I protected was postmaster.
As you can see, you must create two custom recipients in Exchange and one
dummy account with a .forward file on the spam filter box for each address
you want to protect. Like I said, it is more work, but until I am done
load-testing, this is the way it will stay.
-jake
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
Spamassassin-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk