Link to home
Start Free TrialLog in
Avatar of emerson625
emerson625

asked on

Send Connector in Exchange 2007

What is the best way to setup the send connector in Exchange 2007?I have a single Exchange server on a single domain.
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

The best way?
What do you want the Send Connector to do?
If you are looking to just send email out, then the internet type is the best choice.

Simon.
Avatar of emerson625
emerson625

ASKER

I am not sure however what my smtp server is. I was told in the send connector address space config to simpy put an * . is this correct?
I am looking to just send email via the internet. MY internal email works fine.
When I check the queue the is information i get
Identity: exchange\24\44
Subject: 1217 test
Internet Message ID: <F7B441B0BE7B1342B462B42FE8F9DA0525E1429936@exchange.DIPRETEENG.local>
From Address: Emerson@diprete-eng.com
Status: Retry
Size (KB): 7
Message Source Name: FromLocal
Source IP: 255.255.255.255
SCL: -1
Date Received: 4/27/2007 12:18:38 PM
Expiration Time: 4/29/2007 12:18:38 PM
Last Error: 421 4.4.0 Remote server response was not RFC conformant
Queue ID: exchange\24
Recipients:  satellitepc@cox.net
If you want all email to go out through the connector, then configure the domain as *.
Also check that the FQDN that is being presented matches your external DNS.

Are you using a smart host?

The NDR that you have got above would appear to be an issue with the termination of connection, but a 4.x.x error is a temporary failure.
It could be down to spam traps or other techniques for detecting spam.

Simon.
I have not yet completed the deployment of Exchange for this reason. I contacted Microsoft and they think that the mx record that exists could cause this error. The reason they give is that the mx record is tied to a post ini ip address. My isp says he's not sure that would cause the error however he looks at the fact that my internal network is .local instead of .com. He thinks that because the Exchange server can't be resolved( because it is "excahnge.dipreteeng.local )could also be causing an issue. My question then is this. I have 4 servers at my company. the PDC is .local. First does this matter for exchange and should i change the PDC to .com so that all the servers have that extension? Second should I just go ahead with the deployment and have my isp change the mx record so i can begin to use Exchange? What implications does changing the .com have on the rest of my network?
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you for clearing that up for me and the guy at the ISP. Let me get in touch with him and we will fix it. I will let you know how we make out.
Thanks again.