The list is slow because there is several days of messages queued up for
delivery to a veldy.net address, and I cannot seem to get an MX OR an
SOA for this domain.

Anyone else?

$ whois veldy.net

   Domain servers in listed order:

   DNS3.REGISTER.COM                                 209.67.50.253     
   DNS4.REGISTER.COM                                 209.67.50.254    

$  dig  veldy.net soa
; <<>> DiG 8.2 <<>> veldy.net soa 
;; res options: init recurs defnam dnsrch
;; res_nsend to server default -- 206.10.252.1: Connection timed out


Puch! Timeout?

$ dig  @209.67.50.25 veldy.net soa
; <<>> DiG 8.2 <<>> @209.67.50.25 veldy.net soa 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_nsend to server 209.67.50.25: Connection timed out

Double ouch.

All 10 queues are clogged with outgoing email to this person.


-- 
Bob Tanner <tanner at real-time.com>       | Phone : (952)943-8700
http://www.mn-linux.org                 | Fax   : (952)943-8500
Key fingerprint =  6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9