URGENT Relay help - please
Exchange 2003
I have a mailbox called Joe Bloggs (for example)
His Primary SMTP address is joe.bloggs@mydomain.com
I have created a "Contact" to divert his mail to with the SMTP address of joe.bloggs@otherdomain.com
Under the Delivery Option within Exchange General in Active Directory against his account - I have set up the Forward To option to forward to the contact (joe.bloggs@otherdomain.co
I can send email internally to him using the Global Address List - but when I try and sent mail externally (from a mail account such as hotmail etc), I get a delivery failure sent to my hotmail address saying the following:
Status: 5.7.1 (Permanent failure - security: delivery not authorised, message refused)
I thought it might be becuase i did not have a recipient policy for mydomain.com - but i added one the other day and still it does not work.
Please can someone help me.
I have a mailbox called Joe Bloggs (for example)
His Primary SMTP address is joe.bloggs@mydomain.com
I have created a "Contact" to divert his mail to with the SMTP address of joe.bloggs@otherdomain.com
Under the Delivery Option within Exchange General in Active Directory against his account - I have set up the Forward To option to forward to the contact (joe.bloggs@otherdomain.co
I can send email internally to him using the Global Address List - but when I try and sent mail externally (from a mail account such as hotmail etc), I get a delivery failure sent to my hotmail address saying the following:
Status: 5.7.1 (Permanent failure - security: delivery not authorised, message refused)
I thought it might be becuase i did not have a recipient policy for mydomain.com - but i added one the other day and still it does not work.
Please can someone help me.
ASKER
we go through mailsweeper first.
here is the full error message - if it helps more - perhaps this shown in full now is an Exchange meesage.
Reporting-MTA: dns; mailfilter1.XXX.co.uk
Received-From-MTA: dns; XXXXX.com (unverified [xxx.xxx.xxx.xxx])
Arrival-Date: Fri, 30 Jun 2006 00:14:45 +0100
Final-Recipient: rfc822; john.bloggs@mydomain.com
Action: failed
Status: 5.7.1 (Permanent failure - security: delivery not authorised, message refused)
Remote-MTA: dns; {IP address of our Exchange server}
Diagnostic-Code: smtp; 550 5.7.1 Unable to relay for joe.bloggs@mydomain.com
here is the full error message - if it helps more - perhaps this shown in full now is an Exchange meesage.
Reporting-MTA: dns; mailfilter1.XXX.co.uk
Received-From-MTA: dns; XXXXX.com (unverified [xxx.xxx.xxx.xxx])
Arrival-Date: Fri, 30 Jun 2006 00:14:45 +0100
Final-Recipient: rfc822; john.bloggs@mydomain.com
Action: failed
Status: 5.7.1 (Permanent failure - security: delivery not authorised, message refused)
Remote-MTA: dns; {IP address of our Exchange server}
Diagnostic-Code: smtp; 550 5.7.1 Unable to relay for joe.bloggs@mydomain.com
This line is not an Exchange message:
"Permanent failure - security: delivery not authorised, message refused"
The Diagnostic code below is.
I suspect that your mailsweeper application is probably causing the problem. When you use a contact to forward, the messages comes in and goes straight back out again. As such, the message can appear to come from the original address on the message, not from the internal server. I have seen some applications cough over that type of configuration, because the message isn't coming from a domain name that they recognise.
Simon.
"Permanent failure - security: delivery not authorised, message refused"
The Diagnostic code below is.
I suspect that your mailsweeper application is probably causing the problem. When you use a contact to forward, the messages comes in and goes straight back out again. As such, the message can appear to come from the original address on the message, not from the internal server. I have seen some applications cough over that type of configuration, because the message isn't coming from a domain name that they recognise.
Simon.
ASKER
I have totally removed the forward and still get the same error.
I can see the mail coming into our mailsweeper server in the queue. it just does not relay it to Exchange.
All other domains work fine.
I can see the mail coming into our mailsweeper server in the queue. it just does not relay it to Exchange.
All other domains work fine.
Is the mailsweeper application doing any kind of LDAP lookup on the address to see if the account exists?
Simon.
Simon.
ASKER
no - it just sends all the mail to the exchange server using ip address
ASKER
i just figured it out!
in the recipient policy i did not have the "The Exchange Organisation is responsible for all mail delivery to this address" option ticked.
I ticked this option and it started working.
thanks for all your help anyway.
in the recipient policy i did not have the "The Exchange Organisation is responsible for all mail delivery to this address" option ticked.
I ticked this option and it started working.
thanks for all your help anyway.
ASKER
Request made to close this question
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do you route your email via your ISP for example?
Simon.