Re: Re[4]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Darin Cox
You can do that either in the IIS SMTP configuration as Craig suggested below, or in the Computer's network identify, giving it a FQDN for the machine.  IIS SMTP will inherit this info if nothing else is specified. Darin.     - Original Message - From: Craig Edmonds To: declude.jun

Re[6]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Sanford Whiteman
> Thanks to all for the replies. I use Enom registrar for customer > domains and their DNS tools. Instead of DNS MX setting to the simple > IP (65.57.241.194) of the email server, if I change to the MX to the > hostname of the server (sneezy.xerocom.net) would this solve this > roundtrip fa

RE: Re[4]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread William Stillwell
Have you setup Reverse DNS on your DNS Servers? If so, Have them Delegate your subnet to your DNS Servers, this way You control the Reverse DNS for your IP Subnet. If not, Setup your Reverse DNS on your server, and have them Delegate the subnet. IF they will not delegate your subnet, then hav

RE: Re[4]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Craig Edmonds
Not sure if this is any help, but if its cdonts mail that's going out and getting bounced you will also need to set the FQDNS within the IIS cdonts advanced delivery panel with the same domain you have in your reverse dns pointing back to your server sending the cdonts mail out. So if your ip

RE: Re[4]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Don Schreiner
SpiderHost is our Data Center co-locator (Level3 facility). Below is beyond my DNS expertise. What would I have them do? Thanks. -Don Don Schreiner CompBiz, Inc. www.CompBiz.net 407-322-8654 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Stillw

RE: Re[4]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Don Schreiner
Thanks to all for the replies. I use Enom registrar for customer domains and their DNS tools. Instead of DNS MX setting to the simple IP (65.57.241.194) of the email server, if I change to the MX to the hostname of the server (sneezy.xerocom.net) would this solve this roundtrip failure issue and st

RE: Re[4]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread William Stillwell
Ahh, I see your problem now.. Asking d.root-servers.net for 194.241.57.65.in-addr.arpa PTR record: d.root-servers.net says to go to indigo.arin.net. (zone: 65.in-addr.arpa.) Asking indigo.arin.net. for 194.241.57.65.in-addr.arpa PTR record: indigo.arin.net [192.31.80.32] says

Re[4]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Sanford Whiteman
> Set the MX to point to the server reported by the HELO statement > Holisticmoms.org MX sneezy.xerocom.net That doesn't solve the roundtrip failure. If the receiving server checks the roundtrip, it needs an IP-PTR-HELO-A sync. It doesn't care what the MX is for the purposes of that

RE: Re[2]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread William Stillwell
Set the MX to point to the server reported by the HELO statement Ie, Holisticmoms.org MX sneezy.xerocom.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanford Whiteman Sent: Tuesday, August 08, 2006 12:43 PM To: Don Schreiner Subject: Re[2]: [

Re[2]: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Sanford Whiteman
> We have the customer (holisticmoms.org) set-up as a Virtual Domain > under IMail. The DNS for their MX record we have set-up pointing to > our e-mail server IP number which is 65.57.241.194 (our mail server > name = sneezy.xerocom.net, however our router at the data center > replies vaca

RE: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Don Schreiner
I was wondering the same thing about the reverse DNS.   We have the customer (holisticmoms.org) set-up as a Virtual Domain under IMail. The DNS for their MX record we have set-up pointing to our e-mail server IP number which is 65.57.241.194 (our mail server name = sneezy.xerocom.net, ho

RE: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Craig Edmonds
I used to have these problems too on a mass scale. I have my server set to try every 30 minutes for a 48 hour period to delievr email. There is no way their "resources" are busy for that long. When I got my reverse dns sorted out properly on all my servers sending cdonts emails, coincidenta

Re: [Declude.JunkMail] Fw: New ClamAV "scam" database

2006-08-08 Thread Nick Hayer
Thanks much Bill, -Nick Bill Landry wrote: For anyone that is possibly running ClamAV for virus scanning, and is already taking advantage of the added "phish" detection provided by Steve Basford's phish.ndb, he has put together another database geared to tagging "scam" e-mails, including th

RE: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Shayne Embry
We see this happening frequently on very small lists. On a 1,400 user mailing last week, 272 out of 280 Yahoo addresses bounced. We tried the next day with the same results. According to their site, the "resources temporarily unavailable" message is a 421, yet these are all returned with a 451 c

RE: [Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Don Schreiner
Found my own answer here at http://help.yahoo.com/help/us/mail/defer/defer-03.html. Unfortunately, I have seen this Yahoo.com resources unavailable before which accounts for hundreds of undeliverable on a bulk mail list of a few thousand. Thanks.   -Don From: [EMAIL PROTECTED] [m

[Declude.JunkMail] Yahoo.com Resources temporarily unavailable

2006-08-08 Thread Don Schreiner
We handle some small bulk mails for our clients on occasion. Has anyone seen the following response from Yahoo before and know what may be the cause? We are receiving thee back on what appear to be legitimate yahoo.com e-mail addresses. Running IMAIL 8.22 and Declude 1.82. Thanks.   -Don