Randy Martin ( email@example.com )
Mon, 24 Mar 1997 11:08:58 -0600
At 11:58 AM 3/24/97 -0500, you wrote:
>At 06:57 PM 3/23/97 -0600, you wrote:
>>I've been following this post.office spammer thread with some interest.
>>Here's an idea:
>And an EXCELLENT idea at that. Thanks very much, Daryl. I do indeed
>have a spare machine and the time to set that up. It just might work.
>>Set up a machine as a mail forwarder (only), and point MX to it. Use
>>only a hosts file for name resolution (disable DNS) so that the only
>>machine the forwarder can look up by name is the "real" mail server.
>>Make sure the hosts file includes an entry for the domain itself that
>>points to the real mail server. Any SMTP for your system goes through
>>through the forwarder to the real mail host, and any mail hitting that
>>"inbound" mail server for other mail servers dies as undeliverable.
>>Then block tcp:25 in to your "real" mail server. It's kludgy but it may
>>work for some of you with a spare machine and a few hours of time.
>>It does nothing to actually fix the core problem, i.e. buggy software
>>and poor support, but I'm offering this suggestion for those of you
>>pushed against the wall by this.
I'm assuming you also need entries in your hosts file for all the domains
for which you receive mail pointing to the "real" mail server. Correct?
Randy Martin Voice: (512) 335-2368
Partner URL: http://www.austintx.net
Austin Internet Access email: firstname.lastname@example.org