530 5.7.1 relay restricted

David H. · Joined: 06 Aug 2007 Posts: 6

We use Exchange 2003, client uses Outlook 2000. Both client and their
computer are full, normal members of our domain. Yet this one client, when
sending mail to valid Internet addresses, is told:
The following recipient(s) could not be reached:
emailaddress on 3/21/2007 3:07 PM
You do not have permission to send to this recipient. For
assistance, contact your system administrator.

Our SMTP Virtual Server has relay restrictions, but it says to allow all
computers which authenticate to relay.
Is there something else I should be checking?

Archived from group: microsoft>public>exchange2000>clients

Lanwench [MVP - Exchange] · Joined: 05 Aug 2007 Posts: 191

David H. wrote:
> We use Exchange 2003, client uses Outlook 2000. Both client and their
> computer are full, normal members of our domain. Yet this one
> client, when sending mail to valid Internet addresses, is told:
> The following recipient(s) could not be reached:
> emailaddress on 3/21/2007 3:07 PM
> You do not have permission to send to this recipient. For
> assistance, contact your system administrator.
>
> Our SMTP Virtual Server has relay restrictions, but it says to allow
> all computers which authenticate to relay.
> Is there something else I should be checking?

How are your users accessing your Exchange server? If they're just opening
their Exchange mailbox in Outlook/OWA, they aren't relaying. If they're
using POP/IMAP accounts in Outlook for some reason, and specifying your
Exchange server for SMTP, they need to authenticate to it - but I don't
think that's your issue. Try sending a message to the same recipient from
someone else and I imagine you'll see the same thing. If so, what's the
recipient's domain name, and have you talked to the systems admins who
manage their mail server?

David H. · Joined: 06 Aug 2007 Posts: 6

User was using the MS Exchange Server service in Outlook 2000. (Maybe using
Mailbox, maybe using a local PST file to hold data.) Definitely not POP or
IMAP.

It may be relevant that the message was being forwarded (rather than simply
written and sent), and that it was sent to a whole "Committee" of people.
(Initially they were using a personal distribution list; when that failed
they tried adding recipients directly from their Contacts folder). They sent
the message to about 20 recipients, at a wide range of recipient domains.
The message itself was small, with no files or graphics embedded or attached.
The Non-delivery report listed all the recipients, each with the same error
message as previously described. It didn't seem to me that the rejection was
coming from the recipient admins, but from our own server.

Is there any circumstance in which a computer -- apparently normally and
fully connected to the network -- could be perceived by Exchange as trying to
relay?

> How are your users accessing your Exchange server? If they're just opening
> their Exchange mailbox in Outlook/OWA, they aren't relaying. If they're
> using POP/IMAP accounts in Outlook for some reason, and specifying your
> Exchange server for SMTP, they need to authenticate to it - but I don't
> think that's your issue. Try sending a message to the same recipient from
> someone else and I imagine you'll see the same thing. If so, what's the
> recipient's domain name, and have you talked to the systems admins who
> manage their mail server?

David H. · Joined: 06 Aug 2007 Posts: 6

Some additional data:
Other users in our domain report similar problems when sending messages to
multiple (outside) addresses. Non-delivery reasons vary, for example:

_______@sbcglobal.net on 3/22/2007 4:27 PM
The message cannot be delivered due to a configuration error on
the server. Please contact your Administrator.
...
Addressee unknown, relay=[64.18.3.92]>

_______@sbcglobal.net on 3/22/2007 4:27 PM
The e-mail system was unable to deliver the message, but did not
report a specific reason. Check the address and try again. If it still
fails, contact your system administrator.
connection>

Any ideas what this could mean? Thanks!

"David H." wrote:

> User was using the MS Exchange Server service in Outlook 2000. (Maybe using
> Mailbox, maybe using a local PST file to hold data.) Definitely not POP or
> IMAP.
>
> It may be relevant that the message was being forwarded (rather than simply
> written and sent), and that it was sent to a whole "Committee" of people.
> (Initially they were using a personal distribution list; when that failed
> they tried adding recipients directly from their Contacts folder). They sent
> the message to about 20 recipients, at a wide range of recipient domains.
> The message itself was small, with no files or graphics embedded or attached.
> The Non-delivery report listed all the recipients, each with the same error
> message as previously described. It didn't seem to me that the rejection was
> coming from the recipient admins, but from our own server.
>
> Is there any circumstance in which a computer -- apparently normally and
> fully connected to the network -- could be perceived by Exchange as trying to
> relay?
>
> > How are your users accessing your Exchange server? If they're just opening
> > their Exchange mailbox in Outlook/OWA, they aren't relaying. If they're
> > using POP/IMAP accounts in Outlook for some reason, and specifying your
> > Exchange server for SMTP, they need to authenticate to it - but I don't
> > think that's your issue. Try sending a message to the same recipient from
> > someone else and I imagine you'll see the same thing. If so, what's the
> > recipient's domain name, and have you talked to the systems admins who
> > manage their mail server?
>

Lanwench [MVP - Exchange] · Joined: 05 Aug 2007 Posts: 191

David H. wrote:
> User was using the MS Exchange Server service in Outlook 2000.
> (Maybe using Mailbox, maybe using a local PST file to hold data.)
> Definitely not POP or IMAP.

Try having the user use OWA and see.
Any reason they're still on Outlook 2k?

>
> It may be relevant that the message was being forwarded (rather than
> simply written and sent), and that it was sent to a whole "Committee"
> of people. (Initially they were using a personal distribution list;
> when that failed they tried adding recipients directly from their
> Contacts folder). They sent the message to about 20 recipients, at a
> wide range of recipient domains. The message itself was small, with
> no files or graphics embedded or attached. The Non-delivery report
> listed all the recipients, each with the same error message as
> previously described. It didn't seem to me that the rejection was
> coming from the recipient admins, but from our own server.
>
> Is there any circumstance in which a computer -- apparently normally
> and fully connected to the network -- could be perceived by Exchange
> as trying to relay?

No, not if it's just opening the mailbox.
>
>> How are your users accessing your Exchange server? If they're just
>> opening their Exchange mailbox in Outlook/OWA, they aren't relaying.
>> If they're using POP/IMAP accounts in Outlook for some reason, and
>> specifying your Exchange server for SMTP, they need to authenticate
>> to it - but I don't think that's your issue. Try sending a message
>> to the same recipient from someone else and I imagine you'll see the
>> same thing. If so, what's the recipient's domain name, and have you
>> talked to the systems admins who manage their mail server?

Unable to relay Experts, Running Windows Server 2003 SP1. Exchange SP2 and IIS 6.0. Exchange has the SMTP server enabled. But I cannot send any email out from my server. Can't send to my Hotmail, Gmail, or work email address. All reject me with the same unable to rel

unable to relay Hi all I have two mail server in my office 1) exchange 2000 server ( domain name 2) Visnetic ver6 mail server ( domain name when i try to send mail from visnetic mail server to exchnage server shiva@ab

Trying to relay thru Exchange IMC Hi all, We use Exchange 5.5. Our website has several pages where vistors can request information sent to their email address. The code on the website points to the SMTP server. It works sending to an internal email address but not external. The SMTP se

allow relay receiveconnector Hello I am trying to setup a recieve conenctor on my exchange 2007 server, to allow relay for one domain. I have created a conenctor on my 2003 exchange server and told it to use the exchaneg 2007 server for relaying emails sent to mydomain.com The exchan

SMTP Relay Server Question Guys, Quick question for you all. I have been using Exchange 2007 Edge Transport server as my SMTP Relay out to the internet. To be honest, I find it pants! The rules engine for example is just doesn't do what I need. Can anyone recommend an alternati