We have an E2K3 and an E2K7 server. The E2K3 will be retired soon after all
maiboxes moved to the E2K7.
I setup a send connector on the E2K7 Hub Transport server (we don't have
Edge transport setup), and the configuration is identical to send connecot
on the E2K3 server.

I can send email out of all internet email addresses with the send connector
on E2K7 but NOT to an internal email address, that is email with our mail
domain @jaco.com. I have no problem on the send connector on the Exhange
2003 server.

Since I will need this send connector to work properly before I can retire
the E2K3 server, please let me know how to get it setup properly.

Thanks

Bill

Re: Exchange 2007 Send Connector problem with Internal email address by Bharat

Bharat
Tue May 06 13:34:42 CDT 2008

Not sure what you're trying to accomplish.
- Are you in a shared address-space scenario?
- If not, and Exchange has all recipients for your own address space (that
is, an address space/domain that exists as an Accepted Domain of type
Authoritative), a Send Connector is not used to deliver such messages.
- In other words, Send Connectors are only required/used for address spaces
that Exchange isn't authoritative for.

--
Bharat Suneja
Microsoft Corporation
------------------------
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.


"Bill Nguyen" <billn@jaco.com> wrote in message
news:A70C1B44-EC77-439B-94BB-05D8F1F56DC0@microsoft.com...
> We have an E2K3 and an E2K7 server. The E2K3 will be retired soon after
> all
> maiboxes moved to the E2K7.
> I setup a send connector on the E2K7 Hub Transport server (we don't have
> Edge transport setup), and the configuration is identical to send connecot
> on the E2K3 server.
>
> I can send email out of all internet email addresses with the send
> connector
> on E2K7 but NOT to an internal email address, that is email with our mail
> domain @jaco.com. I have no problem on the send connector on the Exhange
> 2003 server.
>
> Since I will need this send connector to work properly before I can retire
> the E2K3 server, please let me know how to get it setup properly.
>
> Thanks
>
> Bill
>
>
>


Re: Exchange 2007 Send Connector problem with Internal email address by Bill

Bill
Tue May 06 17:53:23 CDT 2008

Bharat;

I am not sure if I need this Send Connector. I do have the need to send
email to internal and external email addresses from various .NET application
using SMTP. Since I plan to remove the E2K3 server soon, I need to setup the
E2K7 as an SMTP server to send out email. I also have the need for
sending/receiving email for Sharepoint Enterprise server.
I looked into Send connector properties and all accepted domains are there
(internal users will have 1 or more email addresses with these domain
names - for example, billn@jaco.com, billn@jacooil.com, billn@whatever.com)

I don't if this make any sense to you!

Thanks again!

Bill

"Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
news:%23c7Vbf6rIHA.3940@TK2MSFTNGP03.phx.gbl...
> Not sure what you're trying to accomplish.
> - Are you in a shared address-space scenario?
> - If not, and Exchange has all recipients for your own address space (that
> is, an address space/domain that exists as an Accepted Domain of type
> Authoritative), a Send Connector is not used to deliver such messages.
> - In other words, Send Connectors are only required/used for address
> spaces that Exchange isn't authoritative for.
>
> --
> Bharat Suneja
> Microsoft Corporation
> ------------------------
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
> "Bill Nguyen" <billn@jaco.com> wrote in message
> news:A70C1B44-EC77-439B-94BB-05D8F1F56DC0@microsoft.com...
>> We have an E2K3 and an E2K7 server. The E2K3 will be retired soon after
>> all
>> maiboxes moved to the E2K7.
>> I setup a send connector on the E2K7 Hub Transport server (we don't have
>> Edge transport setup), and the configuration is identical to send
>> connecot
>> on the E2K3 server.
>>
>> I can send email out of all internet email addresses with the send
>> connector
>> on E2K7 but NOT to an internal email address, that is email with our mail
>> domain @jaco.com. I have no problem on the send connector on the Exhange
>> 2003 server.
>>
>> Since I will need this send connector to work properly before I can
>> retire
>> the E2K3 server, please let me know how to get it setup properly.
>>
>> Thanks
>>
>> Bill
>>
>>
>>
>


Re: Exchange 2007 Send Connector problem with Internal email address by Bharat

Bharat
Tue May 06 18:20:08 CDT 2008

To allow SMTP submissions (and optionally relaying) to application servers,
copiers/scanners, etc., you need to look at 2 things:
- Can these apps/servers authenticate? If yes, they can connect to a Receive
Connector and submit mail by default.
- If they cannot authenticate, setup a Receive Connector with appropriate
permissions (including permission to relay if these apps/servers need to
relay mail to *external recipients*). Make sure the Receive Connector allows
connections to only those app servers or internal hosts that need to
submit/relay mail without authentication.

Exchange Server 2007: How To Allow Relaying
http://exchangepedia.com/blog/2007/01/exchange-server-2007-how-to-allow.html

--
Bharat Suneja
Microsoft Corporation
------------------------
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.


"Bill Nguyen" <billn@jaco.com> wrote in message
news:2AFC4504-ED02-43F8-B765-229959D8EEF1@microsoft.com...
> Bharat;
>
> I am not sure if I need this Send Connector. I do have the need to send
> email to internal and external email addresses from various .NET
> application using SMTP. Since I plan to remove the E2K3 server soon, I
> need to setup the E2K7 as an SMTP server to send out email. I also have
> the need for sending/receiving email for Sharepoint Enterprise server.
> I looked into Send connector properties and all accepted domains are there
> (internal users will have 1 or more email addresses with these domain
> names - for example, billn@jaco.com, billn@jacooil.com,
> billn@whatever.com)
>
> I don't if this make any sense to you!
>
> Thanks again!
>
> Bill
>
> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
> news:%23c7Vbf6rIHA.3940@TK2MSFTNGP03.phx.gbl...
>> Not sure what you're trying to accomplish.
>> - Are you in a shared address-space scenario?
>> - If not, and Exchange has all recipients for your own address space
>> (that is, an address space/domain that exists as an Accepted Domain of
>> type Authoritative), a Send Connector is not used to deliver such
>> messages.
>> - In other words, Send Connectors are only required/used for address
>> spaces that Exchange isn't authoritative for.
>>
>> --
>> Bharat Suneja
>> Microsoft Corporation
>> ------------------------
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is
>> for
>> newsgroup purposes only.
>>
>>
>> "Bill Nguyen" <billn@jaco.com> wrote in message
>> news:A70C1B44-EC77-439B-94BB-05D8F1F56DC0@microsoft.com...
>>> We have an E2K3 and an E2K7 server. The E2K3 will be retired soon after
>>> all
>>> maiboxes moved to the E2K7.
>>> I setup a send connector on the E2K7 Hub Transport server (we don't have
>>> Edge transport setup), and the configuration is identical to send
>>> connecot
>>> on the E2K3 server.
>>>
>>> I can send email out of all internet email addresses with the send
>>> connector
>>> on E2K7 but NOT to an internal email address, that is email with our
>>> mail
>>> domain @jaco.com. I have no problem on the send connector on the Exhange
>>> 2003 server.
>>>
>>> Since I will need this send connector to work properly before I can
>>> retire
>>> the E2K3 server, please let me know how to get it setup properly.
>>>
>>> Thanks
>>>
>>> Bill
>>>
>>>
>>>
>>
>


Re: Exchange 2007 Send Connector problem with Internal email address by Bill

Bill
Wed May 07 17:35:52 CDT 2008

Bharat,
In the shell command, how can I specify a range of internal IP address
instead of a single IP?

New-ReceiveConnector -Name RelayConnector -usage Custom -Bindings
'192.168.1.17:25' -fqdn server.domain.com -RemoteIPRanges
192.168.1.100 -server MYEXCHANGESERVER -permissiongroups
ExchangeServers -AuthMechanism 'TLS, ExternalAuthoritative'

Thanks

Bill

"Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
news:uQDm6%238rIHA.2188@TK2MSFTNGP04.phx.gbl...
> To allow SMTP submissions (and optionally relaying) to application
> servers, copiers/scanners, etc., you need to look at 2 things:
> - Can these apps/servers authenticate? If yes, they can connect to a
> Receive Connector and submit mail by default.
> - If they cannot authenticate, setup a Receive Connector with appropriate
> permissions (including permission to relay if these apps/servers need to
> relay mail to *external recipients*). Make sure the Receive Connector
> allows connections to only those app servers or internal hosts that need
> to submit/relay mail without authentication.
>
> Exchange Server 2007: How To Allow Relaying
> http://exchangepedia.com/blog/2007/01/exchange-server-2007-how-to-allow.html
>
> --
> Bharat Suneja
> Microsoft Corporation
> ------------------------
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
> "Bill Nguyen" <billn@jaco.com> wrote in message
> news:2AFC4504-ED02-43F8-B765-229959D8EEF1@microsoft.com...
>> Bharat;
>>
>> I am not sure if I need this Send Connector. I do have the need to send
>> email to internal and external email addresses from various .NET
>> application using SMTP. Since I plan to remove the E2K3 server soon, I
>> need to setup the E2K7 as an SMTP server to send out email. I also have
>> the need for sending/receiving email for Sharepoint Enterprise server.
>> I looked into Send connector properties and all accepted domains are
>> there (internal users will have 1 or more email addresses with these
>> domain names - for example, billn@jaco.com, billn@jacooil.com,
>> billn@whatever.com)
>>
>> I don't if this make any sense to you!
>>
>> Thanks again!
>>
>> Bill
>>
>> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
>> news:%23c7Vbf6rIHA.3940@TK2MSFTNGP03.phx.gbl...
>>> Not sure what you're trying to accomplish.
>>> - Are you in a shared address-space scenario?
>>> - If not, and Exchange has all recipients for your own address space
>>> (that is, an address space/domain that exists as an Accepted Domain of
>>> type Authoritative), a Send Connector is not used to deliver such
>>> messages.
>>> - In other words, Send Connectors are only required/used for address
>>> spaces that Exchange isn't authoritative for.
>>>
>>> --
>>> Bharat Suneja
>>> Microsoft Corporation
>>> ------------------------
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights. Please do not send email directly to this alias. This alias is
>>> for
>>> newsgroup purposes only.
>>>
>>>
>>> "Bill Nguyen" <billn@jaco.com> wrote in message
>>> news:A70C1B44-EC77-439B-94BB-05D8F1F56DC0@microsoft.com...
>>>> We have an E2K3 and an E2K7 server. The E2K3 will be retired soon after
>>>> all
>>>> maiboxes moved to the E2K7.
>>>> I setup a send connector on the E2K7 Hub Transport server (we don't
>>>> have
>>>> Edge transport setup), and the configuration is identical to send
>>>> connecot
>>>> on the E2K3 server.
>>>>
>>>> I can send email out of all internet email addresses with the send
>>>> connector
>>>> on E2K7 but NOT to an internal email address, that is email with our
>>>> mail
>>>> domain @jaco.com. I have no problem on the send connector on the
>>>> Exhange
>>>> 2003 server.
>>>>
>>>> Since I will need this send connector to work properly before I can
>>>> retire
>>>> the E2K3 server, please let me know how to get it setup properly.
>>>>
>>>> Thanks
>>>>
>>>> Bill
>>>>
>>>>
>>>>
>>>
>>
>


Re: Exchange 2007 Send Connector problem with Internal email address by Bharat

Bharat
Wed May 07 17:51:32 CDT 2008

The -RemoteIPRanges parameter can take:
- IP addresses (such as "1.2.3.4","5.6.7.8")
- or ranges of IP addresses designated by a start and end IP address (such
as "1.2.3.1-1.2.3.100","192.168.2.10-192.168.2.200")
- a mix of the two ("1.2.3.4","5.6.7.8","192.168.2.10-192.168.2.200")

As seen in above examples, multiple values need to be separated by commas.

--
Bharat Suneja
Microsoft Corporation
------------------------
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.


"Bill Nguyen" <billn@jaco.com> wrote in message
news:48CB2C25-9CCE-448C-AE0F-5652C7EFCA6C@microsoft.com...
> Bharat,
> In the shell command, how can I specify a range of internal IP address
> instead of a single IP?
>
> New-ReceiveConnector -Name RelayConnector -usage Custom -Bindings
> '192.168.1.17:25' -fqdn server.domain.com -RemoteIPRanges
> 192.168.1.100 -server MYEXCHANGESERVER -permissiongroups
> ExchangeServers -AuthMechanism 'TLS, ExternalAuthoritative'
>
> Thanks
>
> Bill
>
> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
> news:uQDm6%238rIHA.2188@TK2MSFTNGP04.phx.gbl...
>> To allow SMTP submissions (and optionally relaying) to application
>> servers, copiers/scanners, etc., you need to look at 2 things:
>> - Can these apps/servers authenticate? If yes, they can connect to a
>> Receive Connector and submit mail by default.
>> - If they cannot authenticate, setup a Receive Connector with appropriate
>> permissions (including permission to relay if these apps/servers need to
>> relay mail to *external recipients*). Make sure the Receive Connector
>> allows connections to only those app servers or internal hosts that need
>> to submit/relay mail without authentication.
>>
>> Exchange Server 2007: How To Allow Relaying
>> http://exchangepedia.com/blog/2007/01/exchange-server-2007-how-to-allow.html
>>
>> --
>> Bharat Suneja
>> Microsoft Corporation
>> ------------------------
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is
>> for
>> newsgroup purposes only.
>>
>>
>> "Bill Nguyen" <billn@jaco.com> wrote in message
>> news:2AFC4504-ED02-43F8-B765-229959D8EEF1@microsoft.com...
>>> Bharat;
>>>
>>> I am not sure if I need this Send Connector. I do have the need to send
>>> email to internal and external email addresses from various .NET
>>> application using SMTP. Since I plan to remove the E2K3 server soon, I
>>> need to setup the E2K7 as an SMTP server to send out email. I also have
>>> the need for sending/receiving email for Sharepoint Enterprise server.
>>> I looked into Send connector properties and all accepted domains are
>>> there (internal users will have 1 or more email addresses with these
>>> domain names - for example, billn@jaco.com, billn@jacooil.com,
>>> billn@whatever.com)
>>>
>>> I don't if this make any sense to you!
>>>
>>> Thanks again!
>>>
>>> Bill
>>>
>>> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
>>> news:%23c7Vbf6rIHA.3940@TK2MSFTNGP03.phx.gbl...
>>>> Not sure what you're trying to accomplish.
>>>> - Are you in a shared address-space scenario?
>>>> - If not, and Exchange has all recipients for your own address space
>>>> (that is, an address space/domain that exists as an Accepted Domain of
>>>> type Authoritative), a Send Connector is not used to deliver such
>>>> messages.
>>>> - In other words, Send Connectors are only required/used for address
>>>> spaces that Exchange isn't authoritative for.
>>>>
>>>> --
>>>> Bharat Suneja
>>>> Microsoft Corporation
>>>> ------------------------
>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>> rights. Please do not send email directly to this alias. This alias is
>>>> for
>>>> newsgroup purposes only.
>>>>
>>>>
>>>> "Bill Nguyen" <billn@jaco.com> wrote in message
>>>> news:A70C1B44-EC77-439B-94BB-05D8F1F56DC0@microsoft.com...
>>>>> We have an E2K3 and an E2K7 server. The E2K3 will be retired soon
>>>>> after all
>>>>> maiboxes moved to the E2K7.
>>>>> I setup a send connector on the E2K7 Hub Transport server (we don't
>>>>> have
>>>>> Edge transport setup), and the configuration is identical to send
>>>>> connecot
>>>>> on the E2K3 server.
>>>>>
>>>>> I can send email out of all internet email addresses with the send
>>>>> connector
>>>>> on E2K7 but NOT to an internal email address, that is email with our
>>>>> mail
>>>>> domain @jaco.com. I have no problem on the send connector on the
>>>>> Exhange
>>>>> 2003 server.
>>>>>
>>>>> Since I will need this send connector to work properly before I can
>>>>> retire
>>>>> the E2K3 server, please let me know how to get it setup properly.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Bill
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>


Re: Exchange 2007 Send Connector problem with Internal email address by Bill

Bill
Wed May 07 18:38:12 CDT 2008

Bharat;

I am not sure if I need a receivedConnector. I am trying to send email from
.NET application, and I can embed user authentication in the app.
I don't even need authentication using an IIS SMTP service. The problem is
that it doesn't deliver to any internal mailbox but does deliver to an
external email address such as hotmail.com!

I created the ReceiveConnector on our exhcnafge 2007 server, and below is
the error from my .NET app even I provided user authentication:


1. Err msg from .NET app:
System.Net.Mail.SmtpException: The SMTP server requires a secure connection
or the client was not authenticated. The server response was: 5.7.1 Client
was not authenticated

at System.Net.Mail.MailCommand.CheckResponse(SmtpStatusCode statusCode,
String response)

at System.Net.Mail.MailCommand.Send(SmtpConnection conn, Byte[] command,
String from)

at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender,
MailAddressCollection recipients, String deliveryNotify,
SmtpFailedRecipientException& exception)

at System.Net.Mail.SmtpClient.Send(MailMessage message)


2. ReceiveConnector on out Exchange2007 (Mailserver)

[PS] C:\Documents and
Settings\Administrator.JACOOIL.COM>get-receiveconnector

WARNING: column "Enabled" does not fit into the display and was removed.

Identity Bindings
-------- --------
MAILSERVER\Default MAILSERVER {0000:0000:0000:0000:0000:0000:0.0.0.0:25,
0.0...
MAILSERVER\Client MAILSERVER {0000:0000:0000:0000:0000:0000:0.0.0.0:587,
0....
MAILSERVER\RelayConnector {172.16.1.23:25}


[PS] C:\Documents and Settings\Administrator.JACOOIL.COM>
"Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
news:eHKEmTJsIHA.3604@TK2MSFTNGP03.phx.gbl...
> The -RemoteIPRanges parameter can take:
> - IP addresses (such as "1.2.3.4","5.6.7.8")
> - or ranges of IP addresses designated by a start and end IP address (such
> as "1.2.3.1-1.2.3.100","192.168.2.10-192.168.2.200")
> - a mix of the two ("1.2.3.4","5.6.7.8","192.168.2.10-192.168.2.200")
>
> As seen in above examples, multiple values need to be separated by commas.
>
> --
> Bharat Suneja
> Microsoft Corporation
> ------------------------
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
> "Bill Nguyen" <billn@jaco.com> wrote in message
> news:48CB2C25-9CCE-448C-AE0F-5652C7EFCA6C@microsoft.com...
>> Bharat,
>> In the shell command, how can I specify a range of internal IP address
>> instead of a single IP?
>>
>> New-ReceiveConnector -Name RelayConnector -usage Custom -Bindings
>> '192.168.1.17:25' -fqdn server.domain.com -RemoteIPRanges
>> 192.168.1.100 -server MYEXCHANGESERVER -permissiongroups
>> ExchangeServers -AuthMechanism 'TLS, ExternalAuthoritative'
>>
>> Thanks
>>
>> Bill
>>
>> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
>> news:uQDm6%238rIHA.2188@TK2MSFTNGP04.phx.gbl...
>>> To allow SMTP submissions (and optionally relaying) to application
>>> servers, copiers/scanners, etc., you need to look at 2 things:
>>> - Can these apps/servers authenticate? If yes, they can connect to a
>>> Receive Connector and submit mail by default.
>>> - If they cannot authenticate, setup a Receive Connector with
>>> appropriate permissions (including permission to relay if these
>>> apps/servers need to relay mail to *external recipients*). Make sure the
>>> Receive Connector allows connections to only those app servers or
>>> internal hosts that need to submit/relay mail without authentication.
>>>
>>> Exchange Server 2007: How To Allow Relaying
>>> http://exchangepedia.com/blog/2007/01/exchange-server-2007-how-to-allow.html
>>>
>>> --
>>> Bharat Suneja
>>> Microsoft Corporation
>>> ------------------------
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights. Please do not send email directly to this alias. This alias is
>>> for
>>> newsgroup purposes only.
>>>
>>>
>>> "Bill Nguyen" <billn@jaco.com> wrote in message
>>> news:2AFC4504-ED02-43F8-B765-229959D8EEF1@microsoft.com...
>>>> Bharat;
>>>>
>>>> I am not sure if I need this Send Connector. I do have the need to send
>>>> email to internal and external email addresses from various .NET
>>>> application using SMTP. Since I plan to remove the E2K3 server soon, I
>>>> need to setup the E2K7 as an SMTP server to send out email. I also have
>>>> the need for sending/receiving email for Sharepoint Enterprise server.
>>>> I looked into Send connector properties and all accepted domains are
>>>> there (internal users will have 1 or more email addresses with these
>>>> domain names - for example, billn@jaco.com, billn@jacooil.com,
>>>> billn@whatever.com)
>>>>
>>>> I don't if this make any sense to you!
>>>>
>>>> Thanks again!
>>>>
>>>> Bill
>>>>
>>>> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
>>>> news:%23c7Vbf6rIHA.3940@TK2MSFTNGP03.phx.gbl...
>>>>> Not sure what you're trying to accomplish.
>>>>> - Are you in a shared address-space scenario?
>>>>> - If not, and Exchange has all recipients for your own address space
>>>>> (that is, an address space/domain that exists as an Accepted Domain of
>>>>> type Authoritative), a Send Connector is not used to deliver such
>>>>> messages.
>>>>> - In other words, Send Connectors are only required/used for address
>>>>> spaces that Exchange isn't authoritative for.
>>>>>
>>>>> --
>>>>> Bharat Suneja
>>>>> Microsoft Corporation
>>>>> ------------------------
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights. Please do not send email directly to this alias. This alias is
>>>>> for
>>>>> newsgroup purposes only.
>>>>>
>>>>>
>>>>> "Bill Nguyen" <billn@jaco.com> wrote in message
>>>>> news:A70C1B44-EC77-439B-94BB-05D8F1F56DC0@microsoft.com...
>>>>>> We have an E2K3 and an E2K7 server. The E2K3 will be retired soon
>>>>>> after all
>>>>>> maiboxes moved to the E2K7.
>>>>>> I setup a send connector on the E2K7 Hub Transport server (we don't
>>>>>> have
>>>>>> Edge transport setup), and the configuration is identical to send
>>>>>> connecot
>>>>>> on the E2K3 server.
>>>>>>
>>>>>> I can send email out of all internet email addresses with the send
>>>>>> connector
>>>>>> on E2K7 but NOT to an internal email address, that is email with our
>>>>>> mail
>>>>>> domain @jaco.com. I have no problem on the send connector on the
>>>>>> Exhange
>>>>>> 2003 server.
>>>>>>
>>>>>> Since I will need this send connector to work properly before I can
>>>>>> retire
>>>>>> the E2K3 server, please let me know how to get it setup properly.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Bill
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>


Re: Exchange 2007 Send Connector problem with Internal email address by Bill

Bill
Thu May 08 18:01:05 CDT 2008

Bharat;

I think the error message below may help explain why I can't send email to
an internal email address. Please note that "JACO.COM" is our mail domain
name (MX record is still pointing to the Exchange 2003 server) and host
66.162.xxx.xxx is in fact the new Exchange 2007 server (internal name
mailserver.jacooil.com)

Can you please tell me what's wrong?

Thanks

Bill

-----------------------

Event Type: Warning
Event Source: smtpsvc
Event Category: None
Event ID: 4006
Date: 5/8/2008
Time: 3:54:57 PM
User: N/A
Computer: WEBPORTAL
Description:
Message delivery to the host '66.162.xxx.xxx' failed while delivering to the
remote domain 'jaco.com' for the following reason: The remote server did not
respond to a connection attempt.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d2 02 04 c0 Ò..À

"Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
news:eHKEmTJsIHA.3604@TK2MSFTNGP03.phx.gbl...
> The -RemoteIPRanges parameter can take:
> - IP addresses (such as "1.2.3.4","5.6.7.8")
> - or ranges of IP addresses designated by a start and end IP address (such
> as "1.2.3.1-1.2.3.100","192.168.2.10-192.168.2.200")
> - a mix of the two ("1.2.3.4","5.6.7.8","192.168.2.10-192.168.2.200")
>
> As seen in above examples, multiple values need to be separated by commas.
>
> --
> Bharat Suneja
> Microsoft Corporation
> ------------------------
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
> "Bill Nguyen" <billn@jaco.com> wrote in message
> news:48CB2C25-9CCE-448C-AE0F-5652C7EFCA6C@microsoft.com...
>> Bharat,
>> In the shell command, how can I specify a range of internal IP address
>> instead of a single IP?
>>
>> New-ReceiveConnector -Name RelayConnector -usage Custom -Bindings
>> '192.168.1.17:25' -fqdn server.domain.com -RemoteIPRanges
>> 192.168.1.100 -server MYEXCHANGESERVER -permissiongroups
>> ExchangeServers -AuthMechanism 'TLS, ExternalAuthoritative'
>>
>> Thanks
>>
>> Bill
>>
>> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
>> news:uQDm6%238rIHA.2188@TK2MSFTNGP04.phx.gbl...
>>> To allow SMTP submissions (and optionally relaying) to application
>>> servers, copiers/scanners, etc., you need to look at 2 things:
>>> - Can these apps/servers authenticate? If yes, they can connect to a
>>> Receive Connector and submit mail by default.
>>> - If they cannot authenticate, setup a Receive Connector with
>>> appropriate permissions (including permission to relay if these
>>> apps/servers need to relay mail to *external recipients*). Make sure the
>>> Receive Connector allows connections to only those app servers or
>>> internal hosts that need to submit/relay mail without authentication.
>>>
>>> Exchange Server 2007: How To Allow Relaying
>>> http://exchangepedia.com/blog/2007/01/exchange-server-2007-how-to-allow.html
>>>
>>> --
>>> Bharat Suneja
>>> Microsoft Corporation
>>> ------------------------
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights. Please do not send email directly to this alias. This alias is
>>> for
>>> newsgroup purposes only.
>>>
>>>
>>> "Bill Nguyen" <billn@jaco.com> wrote in message
>>> news:2AFC4504-ED02-43F8-B765-229959D8EEF1@microsoft.com...
>>>> Bharat;
>>>>
>>>> I am not sure if I need this Send Connector. I do have the need to send
>>>> email to internal and external email addresses from various .NET
>>>> application using SMTP. Since I plan to remove the E2K3 server soon, I
>>>> need to setup the E2K7 as an SMTP server to send out email. I also have
>>>> the need for sending/receiving email for Sharepoint Enterprise server.
>>>> I looked into Send connector properties and all accepted domains are
>>>> there (internal users will have 1 or more email addresses with these
>>>> domain names - for example, billn@jaco.com, billn@jacooil.com,
>>>> billn@whatever.com)
>>>>
>>>> I don't if this make any sense to you!
>>>>
>>>> Thanks again!
>>>>
>>>> Bill
>>>>
>>>> "Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
>>>> news:%23c7Vbf6rIHA.3940@TK2MSFTNGP03.phx.gbl...
>>>>> Not sure what you're trying to accomplish.
>>>>> - Are you in a shared address-space scenario?
>>>>> - If not, and Exchange has all recipients for your own address space
>>>>> (that is, an address space/domain that exists as an Accepted Domain of
>>>>> type Authoritative), a Send Connector is not used to deliver such
>>>>> messages.
>>>>> - In other words, Send Connectors are only required/used for address
>>>>> spaces that Exchange isn't authoritative for.
>>>>>
>>>>> --
>>>>> Bharat Suneja
>>>>> Microsoft Corporation
>>>>> ------------------------
>>>>> This posting is provided "AS IS" with no warranties, and confers no
>>>>> rights. Please do not send email directly to this alias. This alias is
>>>>> for
>>>>> newsgroup purposes only.
>>>>>
>>>>>
>>>>> "Bill Nguyen" <billn@jaco.com> wrote in message
>>>>> news:A70C1B44-EC77-439B-94BB-05D8F1F56DC0@microsoft.com...
>>>>>> We have an E2K3 and an E2K7 server. The E2K3 will be retired soon
>>>>>> after all
>>>>>> maiboxes moved to the E2K7.
>>>>>> I setup a send connector on the E2K7 Hub Transport server (we don't
>>>>>> have
>>>>>> Edge transport setup), and the configuration is identical to send
>>>>>> connecot
>>>>>> on the E2K3 server.
>>>>>>
>>>>>> I can send email out of all internet email addresses with the send
>>>>>> connector
>>>>>> on E2K7 but NOT to an internal email address, that is email with our
>>>>>> mail
>>>>>> domain @jaco.com. I have no problem on the send connector on the
>>>>>> Exhange
>>>>>> 2003 server.
>>>>>>
>>>>>> Since I will need this send connector to work properly before I can
>>>>>> retire
>>>>>> the E2K3 server, please let me know how to get it setup properly.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Bill
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>