Advertisement

12.05.2007 at 12:12PM PST, ID: 23004220
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

Exchange routing issue

Asked by johan_strange in Exchange Email Server, Email Software, Email Servers

Tags: , , ,

Hi, Can I get some thoughts please with an Exchange routing/permissions issue I have.
I have an SBS 2003 box that I am scaling out to a full 2003 domain. I have 2
additional DCs now plus a Member Server with Exchange 2007 on. Exch 2007
installed , I made a point of running preparelegacyexchangepermissions and
all installed fine. The legacy routing group is working great for internal
users. I have some external users using SMTP relay with SMTP authentication
which is hitting the 2003 box and then being delivered to external recipients
via the 2007 box without issue. I do however have one office that has to send
mail on TCP:26 because the ISP blocks 25. It worked fine with 2003 , I
created an SMTP connector using 26 and it was fine but with 2007 in the
equation I get a 550 5.7.1. I have checked permissions on the receive
connectors and all looks ok , the exchange 2003 box accepts mail on 26 and
then sends it on 25 so I am at a loss as to why this is happening. Any
thoughts would be great.

The NDR is #5.7.1 smtp;550 5.7.1 Unable to relay for " "
Start Free Trial
[+][-]12.06.2007 at 12:14PM PST, ID: 20422815

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]12.28.2007 at 04:30AM PST, ID: 20541242

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 30-day free trial to view this Administrative Comment or ask the Experts your question.

 
[+][-]12.28.2007 at 05:04AM PST, ID: 20541397

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]01.01.2008 at 08:17AM PST, ID: 20560468

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Exchange Email Server, Email Software, Email Servers
Tags: Microsoft, Exchange Server, 2007, Message routing
Sign Up Now!
Solution Provided By: Computer101
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-44 / EE_QW_2_20070628