Unable to send emails in Outlook 2003

[DPM]

Every time I try to send an email, I get this error:

Your message did not reach some or all of the intended recipients.

Subject: XXXX
Sent: XXXX

The following recipient(s) could not be reached:

(e-mail address removed)' on 1/7/2005 10:54 AM
None of your e-mail accounts could send to this recipient.

I've confirmed the outgoing protocol and have no trouble receiving emails.

Any ideas?

 

[Jeff Stephenson [MSFT]]

Every time I try to send an email, I get this error:

Your message did not reach some or all of the intended recipients.

Subject: XXXX
Sent: XXXX

The following recipient(s) could not be reached:

(e-mail address removed)' on 1/7/2005 10:54 AM
None of your e-mail accounts could send to this recipient.

I've confirmed the outgoing protocol and have no trouble receiving emails.

Any ideas?

You probably need to authenticate to the outgoing server for your account,
which you can set up on the "Outgoing server" tab for the account.

 

[DPM]

I have checked the authentication box with use same settings as incoming.
Still have the same problem.

 

[Jeff Stephenson [MSFT]]

I have checked the authentication box with use same settings as incoming.
Still have the same problem.

Try the "logon to incoming server before sending option". If that doesn't
work, could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and post
the OPMLog.log file after you get this error?

 

[Jeff Stephenson [MSFT]]

Here is the log. I replaced my personal info with XXXX.

<snip the log...>

Did you try the "logon to incoming server before sending" option for
authentication? That's the only one that has a chance of working, because
the log shows that the mail server does not support any of the standard
authentication mechanisms.

If you tried that option and it didn't work, you'll need to contact your
ISP for information about how to send - they're the ones that are rejecting
your attempts.

 

[Brian Tillman]

[tx] MAIL FROM: <*****> 2005.01.07 15:49:13 SMTP
(smtp-server.nyc.rr.com): <rx> 250 2.1.0 <*****>... Sender ok
2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): [tx] RCPT TO:
<*****> 2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): <rx> 550
5.7.1 <*****>... Relaying denied
2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): [tx] RCPT TO:
<*****> 2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): <rx> 550
5.7.1 <*****>... Relaying denied

This section clearly shows that either you're not authenticating properly or
that the sender address domain is not a Road Runner domain. It's also
apparent that you're receiving before sending, but who knows if that's
relevent.

Try creating a new account, reentering all the information just like the
first one and modify the Send/Receive group to exclude the first one. If
that doesn't work, create a new mail profile and try again.

 

[Jeff Stephenson [MSFT]]

[tx] MAIL FROM: <*****> 2005.01.07 15:49:13 SMTP
(smtp-server.nyc.rr.com): <rx> 250 2.1.0 <*****>... Sender ok
2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): [tx] RCPT TO:
<*****> 2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): <rx> 550
5.7.1 <*****>... Relaying denied
2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): [tx] RCPT TO:
<*****> 2005.01.07 15:49:13 SMTP (smtp-server.nyc.rr.com): <rx> 550
5.7.1 <*****>... Relaying denied

This section clearly shows that either you're not authenticating properly or
that the sender address domain is not a Road Runner domain. It's also
apparent that you're receiving before sending, but who knows if that's
relevent.

Try creating a new account, reentering all the information just like the
first one and modify the Send/Receive group to exclude the first one. If
that doesn't work, create a new mail profile and try again.

You're right - I had a brain-freeze and didn't notice the recent receive.
A new profile won't help this problem, because it won't change
Road-Runner's behavior. DPM, you'll need to contact Road-Runner about this
- perhaps you'll need to use a different server that supports
authentication (Earthlink, for example, has servers specifically for
authentication).