Re: Receive connector relay

- 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: POP3 Connector undisclosed recipients
    ... >connector. ... Also most of the newer email servers like ... No, cost is what I wind up paying for amortized hardware costs, ... >> unoptimized Exchange servers. ...
    (microsoft.public.exchange.admin)
  • Re: Internal routing
    ... Remove MessageLabs from SmartHost on SMTP virtual servers on all Exchange ... SMTP Connector with address space * in each Routing Group, ... Set MessasgeLabs hostas smarthosts on each SMTP Connector. ...
    (microsoft.public.exchange.admin)
  • Re: Receive connector will not send to internet
    ... Actually they'll be in the funny-named Exchange 2007 routing group then. ... > down our old unauthenticated email server (used mostly for internal> server ... > functions) and replaced it by adding another receive connector to our> hub ...
    (microsoft.public.exchange.admin)
  • Re: Routing Groups/Connectors
    ... Microsoft Exchange Server 2003 Transport and Routing Guide ... Now Setup - In the BridgeHead Server selection, I add added all 3 servers. ... them and move the servers into a single Routing Group. ... Routing Group Connector configuration). ...
    (microsoft.public.exchange.admin)
  • Re: Routing Groups and multipe sites/domains
    ... Is the Exchange organization in native-mode? ... steer one towards creating a new routing group and managing another connector ... You can populate the RGs with servers from any AG. ...
    (microsoft.public.exchange.admin)
Loading