Re: Receive connector relay

What i am trying to achieve is force Exchange 2003 to send internet email through the Exchange 2007 server, and not directly out to the internet using the smtp connector on the Exchange 2003 server. I tried rasing the cost on the smtp (2) connector on Exchange 2003, but this didnt work emails sent from Exchange 2003 were still being delivered by the 2003 smtp connector. I then created a custom smtp receive connector on Exchange 2007 and controlled access to this connector to only allow the exchange 2003 servers to access it. With this setup the exchange 2003 servers are able to relay all outbound emails to the internet through the Exchange 2007 server.

If i understand you correctly to achieve the same thing (force Exchange 2003 to use Exchange 2007 for all outbound internet emails) all i need to do is raise the cost on the smtp connector thats on Exchange 2003?

Ok before i sent this post I wanted to do some testing, what i did was

#1deleted the smtp connector on the EX2003 server tried to send emails to the internet, emails bounced (unable to relay) looked at the smtp recieve logs on the 2007 server, emails were trying to go through the recieve connector that was created to accept emails from the internet.

#2 I deleted the "from internet" receive connector on the Ex2007 server that EX2003 was using to send internet email. After deleting this connector, internet email from Ex2003 were succesfully delivered. Checked the smtp receive logs, on the EX2007 server, the email was using the "default receive" connector. Can the "Default Recieve" connector also recieve anonymous internet emails?

Many thanks

wrote in message news:eH96YI7iJHA.3728@xxxxxxxxxxxxxxxxxxxxxxx
- If there's an existing Connector between the 2 Routing Groups (Exchange 2003 and Exchange 2007), created by Exchange setup or manually, you do not need to create a separate Receive Connector on Exchange 2007 Hub Transport servers to allow Exchange 2003 servers to submit outbound internet mail
- From Exchange 2003's perspective, the SMTP/Send Connector in Exchange 2007 Routing Group should have the lowest cost, and should not be a scoped/restricted Connector
- If there's a SMTP Connector for * in the Exchange 2003 Routing Group, you can either raise its cost or remove it.
- Message size limits can be and are enforced on anonymously submitted messages. However, you have to remember that these are in the context of the Anonymous user. Individual limits cannot be respected or enforced in this case.

Exchange 2007 Transport Permissions Model
http://technet.microsoft.com/en-us/library/aa997170.aspx

Exchange Server 2007: Setting Message Size Limits
http://exchangepedia.com/blog/2007/09/exchange-server-2007-setting-message_10.html

--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog

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.
----------------------------




"skip" <shofmann@xxxxxxx> wrote in message news:520B34A4-2341-4E4A-BFD5-73DAA7DF43D1@xxxxxxxxxxxxxxxx
Hello all
I have CAS+HAT on the sam Windows 2008 box, curently i the middle of a transition from EX2003 to EX2007. I have two Exchange 2003 servers, both servers are in the same routing group, the routing group has a smtp connector (to.internet) this connector is used to send emails to the internet. I know want to force both EX2003 servers to send all about emails to the inernet through the EX2007 server. In order to do this is created a new receive connector on EX2007. I controll access to this connector by locking it down to only allow access from the EX2003 servers. The connector type is custom and the authentication is externally secured, the permissions group is exchange servers.

This is working email are being relayed from EX2003 to EX2007. What i am confused about is in order to set this up i had to create a new connector, could i have used the built in "default" connector? also i need to control things like message size and message count when the email originates from the EX2003 server. I read that when an email is sent Anonymously the connector is not able to enforce things like message size restriction. Is this is true is there work around for this? Below is the output of the connector when i run the comamnd "get-receiveconnector -id "conenctor name" |fl


AuthMechanism : ExternalAuthoritative
Banner :
BinaryMimeEnabled : True
Bindings : {10.7.13.242:25}
ChunkingEnabled : True
DefaultDomain :
DeliveryStatusNotificationEnabled : True
EightBitMimeEnabled : True
DomainSecureEnabled : False
EnhancedStatusCodesEnabled : True
LongAddressesEnabled : False
OrarEnabled : False
Fqdn : CAS-HT.kbblab.local
Comment :
Enabled : True
ConnectionTimeout : 00:10:00
ConnectionInactivityTimeout : 00:05:00
MessageRateLimit : unlimited
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize : 64KB
MaxHopCount : 30
MaxLocalHopCount : 8
MaxLogonFailures : 3
MaxMessageSize : 10MB
MaxProtocolErrors : 5
MaxRecipientsPerMessage : 200
PermissionGroups : ExchangeServers
PipeliningEnabled : True
ProtocolLoggingLevel : Verbose
RemoteIPRanges : {10.7.13.174, 10.0.134.168}
RequireEHLODomain : False
RequireTLS : False
EnableAuthGSSAPI : False
Server : CAS-HT
SizeEnabled : Enabled
TarpitInterval : 00:00:05
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : relay externaly secured
DistinguishedName : CN=relay externaly secured,CN=SMTP Re
ceive Connectors,CN=Protocols,CN=CAS-
HT,CN=Servers,CN=Exchange Administrat
ive Group (FYDIBOHF23SPDLT),CN=Admini
strative Groups,CN=KBBLAB,CN=Microsof
t Exchange,CN=Services,CN=Configurati
on,DC=kbblab,DC=local
Identity : CAS-HT\relay externaly secured
Guid : fa3bcf38-c700-4ac6-b841-7834738e1842
ObjectCategory : kbblab.local/Configuration/Schema/ms-
Exch-Smtp-Receive-Connector
ObjectClass : {top, msExchSmtpReceiveConnector}
WhenChanged : 2/4/2009 4:58:13 PM
WhenCreated : 2/4/2009 4:51:43 PM
OriginatingServer : DC1.kbblab.local
IsValid : True






.

Relevant Pages

  • RE: Email failed
    ... Run the CEICW and go through the Internet, firewall and Web Server ... Connector for POP3 Mailboxes" option. ... you could just leave the option unchanged, since your Exchange could ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2007 - Sending to External Domains
    ... Exchange Server auth is checked, ... The other Receive connector is the one Created by default fro Client ... Hosted Services or a third-Party SMTP gateway, ...
    (microsoft.public.exchange.connectivity)
  • Re: Exchange Migration Part II
    ... properties of the migrated user in exchange on the B domain I have both ... I did set up a SMTP connector from Domain B ... using xxx.com in the Address name space and the IP address of the server ... username@xxxxxxxx and attached it as a forward to the exchange account to ...
    (microsoft.public.exchange.setup)
  • Re: Problems sending email in SBS 2008
    ... I had a KM scanner that was upsetting Exchange IMF, IMF properties, ... I work remotely from this client so I can only make changes to the server ... I'm confident the receive connector is ...
    (microsoft.public.windows.server.sbs)
  • RE: Email failed
    ... Microsoft CSS Online Newsgroup Support ... >> A. Run the CEICW and go through the Internet, firewall and Web Server ... >> Connector for POP3 Mailboxes" option. ... you could just leave the option unchanged, since your Exchange ...
    (microsoft.public.windows.server.sbs)