Dale I know close to nothing about DNS, but what I have been trying to convince Warren in my emails (which must sound tedious to the list) is that his problem had very little to do with SIMS - it was just handling mail that was delivered to its IP and destined for an IP which was also itself.
The only way this could be true was if a DNS server somewhere mapped his client's domain name to his server's IP number. He stated that he had removed all of the DNS records related to this client - hence my assumption that there was a rogue DNS (his secondary?) that was still pointing to his server. It is rumored that on or about 2002-07-12 1:36 PM +0000, dale wrote as follows: >Hi, > >>If you look at the SIMS documentation here: >> >> http://www.stalker.com/SIMS/AntiSpam.html#Relay > >Not really related to the problem here. It is very related because Warren couldn't understand why SIMS would accept mail for a domain not listed in the SIMS router. It is because SIMS doesn't care what the domain name is - it compares IPs when deciding if mail is from or for a "stranger", and his client is still getting mapped to his IP (and so is NOT a stranger). Until he fixes the DNS entries, a simple routing to error will get rid of the stuff. -- Neil Neil Herber, RGD Corporate info at http://www.eton.ca/ Eton Systems, 15 Pinepoint Drive, Nepean, ON, Canada K2H 6B1 Tel: (613) 829-4668 ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
