Warren,

While I am not an expert on DNS (I know enough to usually get 
myself out of the troble I get myself into). I think the 
problem maybe easier to solve that it appears right now.

Here is a "dig" of the mindcorral.com domain.

---


dig  mindcorral.com soa 2>&1

; <<>> DiG 9.1.3 <<>> mindcorral.com soa
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9687
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, 
ADDITIONAL: 3

;; QUESTION SECTION:
;mindcorral.com.                        IN      SOA

;; ANSWER SECTION:
mindcorral.com.         43243   IN      SOA     ns1.mdcclxxvi.com. 
hostmaster.mdcclxxvi.com. 2002052101 10800 3600 604800 86400

;; AUTHORITY SECTION:
mindcorral.com.         172586  IN      NS      NS2.mdcclxxvi.com.
mindcorral.com.         172586  IN      NS      EAGLECREST.JURISDATA.com.
mindcorral.com.         172586  IN      NS      ns1.mdcclxxvi.com.

;; ADDITIONAL SECTION:
ns1.mdcclxxvi.com.      172586  IN      A       209.145.196.198
NS2.mdcclxxvi.com.      172586  IN      A       209.145.196.197
EAGLECREST.JURISDATA.com. 172586 IN     A       65.101.224.90

;; Query time: 407 msec
;; SERVER: 208.146.240.249#53(208.146.240.249)
;; WHEN: Fri Jul 12 13:15:21 2002
;; MSG SIZE  rcvd: 208



---

What the above tells me is the solution is to update YOUR DNS 
records and remove EAGLECREST.JURISDATA.com as a secondary DNS 
server.

Since it appears that your DNS server is the authoritve name 
server, once the TTL period passes for this domain no one will 
even know about that secondary DNS server and hence the emails 
will stop.

Also, based on the SOA info (which may be different from how I 
serialize my zone files) it looks like this zone file was last 
updated on May 21st 2002 .


Here is a dig showing MX info from the other DNS server:

---

dig  mindcorral.com mx 2>&1

; <<>> DiG 9.1.3 <<>> mindcorral.com mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5947
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, 
ADDITIONAL: 3

;; QUESTION SECTION:
;mindcorral.com.                        IN      MX

;; ANSWER SECTION:
mindcorral.com.         86400   IN      MX      100 smtp.az.net.
mindcorral.com.         86400   IN      MX      10 mail.mdcclxxvi.com.

;; AUTHORITY SECTION:
mindcorral.com.         172300  IN      NS      EAGLECREST.JURISDATA.com.
mindcorral.com.         172300  IN      NS      NS1.mdcclxxvi.com.
mindcorral.com.         172300  IN      NS      NS2.mdcclxxvi.com.

;; ADDITIONAL SECTION:
NS1.mdcclxxvi.com.      172300  IN      A       209.145.196.198
NS2.mdcclxxvi.com.      172300  IN      A       209.145.196.197
EAGLECREST.JURISDATA.com. 172300 IN     A       65.101.224.90

;; Query time: 158 msec
;; SERVER: 208.146.240.249#53(208.146.240.249)
;; WHEN: Fri Jul 12 13:20:08 2002
;; MSG SIZE  rcvd: 209

---

and lookie here, here is a DIG of the MX records using your 
DNS server

---

dig  mindcorral.com mx 2>&1

; <<>> DiG 9.1.3 <<>> mindcorral.com mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44687
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, 
ADDITIONAL: 3

;; QUESTION SECTION:
;mindcorral.com.                        IN      MX

;; ANSWER SECTION:
mindcorral.com.         86349   IN      MX      10 mail.mdcclxxvi.com.
mindcorral.com.         86349   IN      MX      100 smtp.az.net.

;; AUTHORITY SECTION:
mindcorral.com.         172249  IN      NS      NS2.mdcclxxvi.com.
mindcorral.com.         172249  IN      NS      EAGLECREST.JURISDATA.com.
mindcorral.com.         172249  IN      NS      NS1.mdcclxxvi.com.

;; ADDITIONAL SECTION:
NS1.mdcclxxvi.com.      172249  IN      A       209.145.196.198
NS2.mdcclxxvi.com.      172249  IN      A       209.145.196.197
EAGLECREST.JURISDATA.com. 172249 IN     A       65.101.224.90

;; Query time: 4 msec
;; SERVER: 208.146.240.249#53(208.146.240.249)
;; WHEN: Fri Jul 12 13:20:58 2002
;; MSG SIZE  rcvd: 209
---

Looks like you haven't disbale the MX records after all - this 
is why you are getting the emails.

I would suggest first killing the MX records and also kill the 
secondary for this domain. That should solve the problem for 
good.

Hope this helps

Dale


On Thu, 11 Jul 2002 16:40:02 -0700
  Warren Michelsen <[EMAIL PROTECTED]> wrote:
> At 6:40 PM -0400 07/11/2002, Neil Herber wrote:
> >
> >Unfortunately the SIMS log uses the term "relay" when it 
> >really means "deliver". It is not saying that it will 
> >operate as an open relay for mx1.deals4recruiters.com, it is 
> >saying that it will deliver the message from 
> >mx1.deals4recruiters.com to an account (client) on your 
> >server.
> 
> Whether it's "deliver" or "relay", it's a distinction 
> without a difference. There's no such client on this mail 
> host. Why does it think that there is?
> 
> >
> >Flogging the dead horse yet again:
> >
> >     mindcorral.com = error
> >
> >and kiss these things goodbye.
> >
> >Unfortunately, an error routing returns a message like this:
> >
> >     Diagnostic-Code: SMTP; 592 address is blacklisted.
> 
> Exactly. I'd rather bounce mail addressed to these folks so 
> they'll (maybe) stop sending it.
> 
> 
> -- 
> "President Bush said the 9-11 terror strikes were an attack 
> on our freedoms.
> 
> "John Ashcroft has decided that it's better to destroy those 
> freedoms
>   than to leave them exposed as such an easy target."
> 
>   - Pauly & Maury, Weakly Politics newsletter
> 
> #############################################################
> 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]>
> 


#############################################################
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]>

Reply via email to