Hello everyone I am trying to figure out how to do something in exchange 2007 that I was hoping you might be able to hope for. We have two domain names for email (due to purchase of company) that we are authoritative for. People in company A receive and send email as company A email address. People in company B receive and send email and company B, but also have email addresses for company A that will eventually be there default, but company B is there default for now until the integration is complete. But, users in company B, need to send emails as company A for some emails. When I try to set this up, I allow people in company B to send email via POP3/SMTP using the company A email address, but I get a bounce back message saying it is not allowed. In 2003, we had it working by setting the "Allow messages to be relayed via this connection" setting in the send connector to our external provider of email scanning. Now, in 2007, I cannot find a similar sendign to alow this. Do you know of a method to allow this to happen without having to create a second email box for all these users and setting Send As permissions? Any help you can give would be appreciated. Thanks Nick

Hi, Two steps have to be done. One is create the accepted domain for company A, the last is create the corresponding email address policy. Here are the detailed steps to setup a second SMTP domain in Exchange 2007: 1. We need to add a new accepted domain: Open the Exchange Management Console. Expand the Organization Configuration node, and then click Hub Transport. Click the Accepted Domains tab in the results pane. In the action pane, click New Accepted Domain The New Accepted Domain wizard appears. On the New Accepted Domain page, type a name to identify the accepted domain entry. In the Accepted Domain field, type the SMTP domain name. Select Authoritative Domain. E-mail is delivered to a recipient in this Exchange organization. Click New. On the Completion page, click Finish. 2, Create additional email addresses that will be used for a filtered set of recipients. Once this is done, the emails delivered to the Exchange 2007 server, for recipients with email domain name set above, will be accepted, instead of rejected by the server, and Exchange 2007 will distribute these incoming emails. Below link can put as your reference: http://www.petri.co.il/configure-exchange-2007-recieve-email-other-domains.htm Thanks Allen

Allen Thanks for the reply regarding my question above. I have already added the second email domain, and the users can receive email from both the company A and company B email addresses. The problem I am having is I cannot allow people from Company B to send emails from their company A email address since that is not their primary email address in Exchange. Most of the blogs and articles I found recommended creating a second email box for those people and giving them send as permissions to the box, but this will increase our mailbox load significantly. When we had it setup in 2003, we set our outbound connector to allow relaying of all messages since we were just sending the messages to our MTA then it would send it out from there. Not sure if this setting is allowed in 2007, but any help you can give would be appreciated. Thanks Nick

Hi, In fact, we can send the email by using POP3 client from different email address in Exchange 2007, such as Company A or Company B. We need to find the cause why you couldn't. Now I would like to confirm the exact error message that you received when trying this. Additionally, please run get-receiveconnector |fl command in EMS, then post the information on the forum. Thanks Allen

Allen We can send the messages internally to each other using Company A or Company B addresses without problems, so I think our receive connectors are setup correclty to allow clients to send messages into the server with their email addresses using POP3/SMTP, the problem comes in when we try to send it out the send Connector to MTA (hosted). We get a system undeliverable message from the system that says the message cannot be sent to the destination host, but with normal accounts (primary address) the messages are sent fine. Any help you can give would be appreciated. Thanks Nick

Hi, Whether the two domains are integrated with one organization or place in respective organizations? Thanks Allen

Allen The two organizations are integrated in terms of network and use of internal services. The only difference is currently the other organization needs the ability to use their previous domain name as well as the new consolidated name. Like I said, everything internally works fine, but as soon as they try to send outbound using their non-primary address, there is a bounce back message that is sent by the system. Thanks Nick