Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
SBS 2003The recipient could not be processed because it would violate the security policy in force
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login | |
|
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
SBS 2003The recipient could not be processed because it... - 11.May2008 1:49:08 PM
|
|
|
hookie
Posts: 2
Joined: 11.May2008
Status: offline
|
Dear All, I have been researching this problem for problemthe last two days, although i have come across a close match there is nothing that i can find that nails this to the wall. That problem is as follows, SBS 2003 SP2, Exchange up to date. All existing exchange users can send and receive mails ok, however any newly created users with a newly created mail boxes can send mails but never receive any. If i sent a user on this exchange server an e-mail below is what i would receive back. Your message did not reach some or all of the intended recipients. Subject: test 1234 Sent: 5/11/2008 5:27 PM The following recipient(s) could not be reached: test@testdomain.co.uk on 5/11/2008 5:27 PM The recipient could not be processed because it would violate the security policy in force <sergenta.co.uk #5.7.0 smtp;550 5.7.0 <test@testdomain.co.uk>... Local Policy Violation - invalid user> As i say existing users can send fine and no policys have been updated recently and i have looked to see if any filtering has been setup on the exchange server but none exists. I can find close matches to this problem but nothing that points directly to the message. I have looked up the 550 message and this seems to suggest an underlying problem with SMTP, if that was the case would not all users have an issue or atleast have this same problem? Thank you very much for your time and direction. Hookie
|
|
|
|
RE: SBS 2003The recipient could not be processed becaus... - 11.May2008 4:51:39 PM
|
|
|
jveldh
Posts: 647
Joined: 12.Apr.2008
From: The Netherlands
Status: offline
|
Hookey, I think you have activated recipient filtering which bounces messages who do not exist in your environment. Try to disable this and check again if it works.
_____________________________
Best regards, Johan Veldhuis Visit my website
|
|
|
|
RE: SBS 2003The recipient could not be processed becaus... - 13.May2008 7:59:29 PM
|
|
|
Sembee
Posts: 3583
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline
|
That isn't an Exchange message. Therefore it is not Exchange that is rejecting the email. Do your emails come direct to Exchange or through something else? Another server at your ISP, an appliance, antispam or antivirus? It certainly is recipient filtering of some kind, but it isn't Exchange recipient filtering. It is something else. Simon.
_____________________________
Simon Butler, Exchange MVP Blog: http://www.sembee.co.uk/ Web: http://www.amset.info/ In the UK? Hire me: http://www.amset.co.uk/
|
|
|
|
RE: SBS 2003The recipient could not be processed becaus... - 17.May2008 6:24:09 AM
|
|
|
hookie
Posts: 2
Joined: 11.May2008
Status: offline
|
Hi Simon, I agree because i could telnet to port 25 on the mail server and send that user an e-mail. What i eventually found out was the company had recently introduced a form of antivirus and spam filtering similar to message labs, this meant they divert the mx record to the message scanning compant who then rely that back to the mail server where my customer is located. Part of this process is that all users have to be listed with the message scanning company, if not it wont get through. Also this would also explain why i could never find any error messages in the log files. I hope this will be useful to anyone that find it because this has been driving me up the garden wall. It also goes to show find out what your cusromer has also changed before you go looking for answers... Thank you very much indeed to both of you for your help i appreciate the effort in helping me. Best regards to you. quote:
ORIGINAL: Sembee That isn't an Exchange message. Therefore it is not Exchange that is rejecting the email. Do your emails come direct to Exchange or through something else? Another server at your ISP, an appliance, antispam or antivirus? It certainly is recipient filtering of some kind, but it isn't Exchange recipient filtering. It is something else. Simon.
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|