I've seen something similar when the permissions are changed on the mail directory in the wwwroot folder.  Not sure if it'll help here, but worth a look.
Simon

Thanks Guys, it is was a problem with the firewall and not having a smarthost mail server setup.

Now I'm forwarding my mail (using smarthost) to a mail server that is allowed through the firewall.  

And a queue of 1890 items is now 0 :-)

The remote server did not respond to a connection attempt....

 http://support.microsoft.com/support/misc/kblookup.asp?ID=827363

Sorry the link above doesn't work

You need this security patch

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=51184D09-4F7E-4F7B-87A4-C208E9BA4787

Tidydave,

How did you get around the firewall problem and forward your mail (using smarthost)?  




---------------

Thanks Guys, it is was a problem with the firewall and not having a smarthost mail server setup.

Now I'm forwarding my mail (using smarthost) to a mail server that is allowed through the firewall.  

And a queue of 1890 items is now 0 :-)

What did you with the Firewall ??

Open ports 25, 110 or something else...

I had this same issue. Almost all of our mail was in queue to popular domains like aol.com, hotmail.com, etc.

The eliminate the immedeate problem, I used a smarthost to relay our mail for us. That got the mail out of queue, but didn't solve why WE couldn't send our own mail out (instead of going through a third party).

When I tried to connect to AOL manually, I received this message:
220-rly-ye01.mx.aol.com ESMTP mail_relay_in-ye1.7; Sun, 06 Jun 2004 20:38:23 -04
00
220-America Online (AOL) and its affiliated companies do not
220-     authorize the use of its proprietary computers and computer
220-     networks to accept, transmit, or distribute unsolicited bulk
220-     e-mail sent from the internet.  Effective immediately:  AOL
220-     may no longer accept connections from IP addresses which
220      have no reverse-DNS (PTR record) assigned.

I'm guessing that our failure to connect was possibly a result of this "no reverse-DNS PTR Record" item. I have no idea how to get a PTR record established for the IP we sent mail from though...

I had the same problem and the resolution was to make sure my PTR and MX records were published properly.  epaschal, contact your ISP and they should be able to get the PTR published properly.

Scott

After upgrading from Exchange 2000 to 2003, I also had the problem with AOL, Yahoo, etc sticking in the Queue.  I resolved the problem by making sure that under Default SMTP Virtual Server Properties - Delivery Tab - Advanced - Configure External DNS servers, I  Added our ISP's DNS server addresses in here. Once I did that all of the emails went through after that.  
-- Frank

I am using IIS 2000.  I am under Default SMTP Virtual Server Properties - Delivery Tab - Advanced.

But I do NOT have a "Configure External DNS servers" tab!!

Please help.

FrankTaylor617,

Can you help?  I am having the same problem and need to figure out a solution asap.  You can also contact me directly at {{email address removed for member's protection - 3-Aug-05 --alimu/Page Editor IIS}}

I appreciate your help.  Thank you in advance.

You might trying calling your ISP. If it is SBC you will want to ask for 2nd teir support and unblock port 25 on your system. You will need to reboot your router or reset

Thanks,

Rich

Rich,

What is port 25 used for?  Will SBC unblock this port?

I am currently not using SBC to send emails ...

I believe my problem is similar to FrankTaylor617 but I am using IIS 2000.  The problem is that under Default SMTP Virtual Server Properties - Delivery Tab - Advanced, there isn't a Configure External DNS servers button.

Port 25 is for smtp (Simple Mail Transfer Protocal)

Call them or log into help.sbcglobal.net .

There is a form to fill out and they will unblock it. Everything will just go back to working. Very Bizare.

Thanks,

Rich

Were you using CDONTS and SMTP Virutal Server?  What platform?

SMTP Virtual Server

I just dealt with this problem and it was a result of not having our PTR record setup properly. Our ISP didnt have our reverse DNS setup in the PTR record. and as I found out, some mail servers dont accept connections from servers if they cant lookup their DNS name, such as some AOL servers, gmail, and others.

newbie

{{email address removed for member's protection - 3-Aug-05 --alimu/Page Editor IIS}}

I think my problem is only with SBC. Sbc started blocking port 25 accross thier network.

Do you know what RBLs are?

NO, sorry.

guys - this question is closed.  you may want to open a new thread to start a new discussion.

Cheers.