Is there any settings in outlook that could possibly prevent mail being delivered to netzero and juno accounts?
Our outlook account here at work are not able to sent emails to juno or netzero account. I am running Exchange 2000 but we are using a cable provider for the internet mail (SMTP). I have no restrictions on the server when it comes to who/where email can be sent to. If I got directly to the smtp provider and use their webmail utility I can send the email just fine.
Now the part that gets me is, we know another person that uses outlook express at home and can not send to a juno/netzero user either, they are not using any exchange server at all, the only common point it outlook.
Now when I send for here, I get a "Delivery Status Notification (Delay)"
Info below (names changed)
Then a day later I get "Undeliverable: test email"Quote:
Reporting-MTA: dns;myservername.mydomain.com
Final-Recipient: rfc822;[email protected]
Action: delayed
Status: 4.4.7
Will-Retry-Until: Tue, 19 Sep 2006 00:16:12 -0700
X-Display-Name: '[email protected]'
Any help would be appreciated, do you think changing the timeout setting on my server would help or maybe I am not looking in the right place? I looked in the queues on the server and after a few minutes I now see "Smallbusiness MSTP connector (SMTP Connector - Remote delivery) - RETRY - (Time of submission) Total number of Msg = 1 Total Msg Size=1. I did try to force it to retry, but I really didn't think that it should be using my exchange server to try to deliver it since we are using "internet mail" not the SMTP on my exchange server. I did look at the properties of this try and it does say "An SMTP protocol error occued".Quote:
Your message did not reach some or all of the intended recipients.
Subject: test email
Sent: 9/18/2006 12:16 PM
The following recipient(s) could not be reached:
'[email protected]' on 9/19/2006 12:17 AM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<myservername.mydomain.com #4.4.7>
But seeing that there is also an outlook express user with the same issue it leads me to believe this is more than just my exchange server.