Mailing List SIMS@mail.stalker.com Message #6415
From: Cerebus D Aardvark <kreme@kreme.com>
Subject: Re: (not so) Obvious spam address
Date: Thu, 6 Jul 2000 09:31:38 -0600
To: SIMS Discussions <SIMS@mail.stalker.com>
On 7/6/00 at 08:51 -0500, Dave Martin said:
It might be nice if SIMS could do some "Received" backtracking, but that
would require accepting the connection to read headers, and would add to
overhead as each IP address/hostname in the Received path (part of which
may be forged, too) was DNS/revDNS inspected for possible blacklist or
RBL matches. I know when our university "forced" a secondary MX on us,
tons of spam which SIMS would have stopped came through, because the
secondary was a "trusted" host, and it was accepting the spam
unconditionally. If SIMS could have checked the received's (maybe even
just the previous one), and do checks on that, a lot of stuff would have
been blocked.

It would be _so_ nice to have SIMS check the previous path when mail comes in from the secondary.  However, you don't want mail from your secondary being rejected, so SIMS would need to handle it differently.

Maybe mail coming from a client IP for local delivery that fails the spam test could be deposited elsewhere?

maybe a setting to ask sims to perform blacklist checks two levels back to circumvent the unknown open relay?

All options, of coruse.

One question regarding "proper" RFC formatting of messages and
headers...where does the requirement or responsibility for the Message-ID
field lie?

Message-ID: <IntmSCKG280o>

Message-ID is _Optional_ so there is no requirement.

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster