You do not have permission to send to this recipient. For assistance, contact your system administrator.

Our user would like to send to an outside domain username@freenet.edmonton.ab.ca .

It seems this error message comes up and bounces the email:

From: System Administrator
Sent: November 13, 2008 4:52 PM
To: sender
Subject: Undeliverable:RE: test

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

      Subject:  RE: test

      Sent:     11/13/08 4:52 PM


The following recipient(s) could not be reached:

      'Username' on 11/13/08 4:52 PM

            You do not have permission to send to this recipient.  For assistance, contact your system administrator.

            <SERVER #5.7.1 smtp;551 5.7.1 Invalid HELO. For more information go to http://www.tera-byte.com/mail/invalid-helo.html?SERVER>

I can't seem to figure out how to allow out-going messages.  It seems that incoming is working.

Thanks in advance!
Keeran NetworksAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dfxdeimosCommented:
Run your domain through this MX record test utility and post the results (or any that seem relevant).

http://www.mxtoolbox.com/
0
JascotCommented:
The invalid HELO sounds like your Exchange server is announcing its name to the receiving server with an invalid name, probably its local AD name. You will need to go into the Exchange System Manager program, then into the "Default SMTP Virtual Server" properties. Go to the Delivery tab at the top, then hit the Advanced button. There is an entry blank for the Fully Qualified Domain Name. It may be set to something like exchsvr.domain.local. It needs to be set to a valid name on the Internet. Probably the same thing as your MX record in DNS.

Let us know if you need more details.
0
Keeran NetworksAuthor Commented:
Jascot: Thank-you for the in-depth answer. The FQDN is set to the correct domain.ca...

Any other thoughts?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

dfxdeimosCommented:
Did you run your domain through the link I posted? If so, can you post the results?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keeran NetworksAuthor Commented:
Here are the MX link results:
RESULT: DOMAIN.ca 
Banner: ***************************************************************************************************************** [78 ms]  
Connect Time: 0.078 seconds - Good 
Transaction Time: 5.5 seconds - Warning 
Relay Check: OK - This server is not an open relay. 
Rev DNS Check: OK - IP resolves to dsl-vlan472-IP.nucleus.com 
GeoCode Info: Geocoding server is unavailable 
Session Transcript: HELO please-read-policy.mxtoolbox.com 
250 DOMAIN.ca Hello [64.20.227.131] [78 ms] 
MAIL FROM: <test@mxtoolbox.com> 
250 2.1.0 test@mxtoolbox.com....Sender OK [78 ms] 
RCPT TO: <test@mxtoolbox.com> 
550 5.7.1 Unable to relay for test@mxtoolbox.com [5109 ms] 
QUIT 
221 2.0.0 DOMAIN.ca Service closing transmission channel [78 ms]

Open in new window

0
Keeran NetworksAuthor Commented:
The error seems to keep coming up as:

RCPT TO: <test@mxtoolbox.com> 
550 5.7.1 Unable to relay for test@mxtoolbox.com [5062 ms] 

Open in new window

0
Keeran NetworksAuthor Commented:
Upon further investigation, the emails are sitting at the SmallBusiness SMTP connector.  They are stuck in Retry status and do not seem to unfreeze....Any thoughts?
0
Keeran NetworksAuthor Commented:
Thank-you for your assistance.  This had something to do with the correct name in the MX record field.  Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.