We have a mixed environment with Exchange 2003 and 2007. When running telnet with Exchange 2003 bridghead it will resolve an alias. When running telnet on a hub transport in Exchange 2007 an alias will not resolve. Any ideas on the setting that allows alias' to resolve in Exchange 2003 but is not in Exchange 2007? Exchange 2003 output mail from:alias 250 2.1.0 alias@exchange.domain.com....Sender OK Exchange 2007 output mail from:alias 501 5.1.7 Invalid address

2003 appends the domain by default, 2007 doesn't. To configure 2007 to do so configure the receive connector to specify the default domain parameter. Set-receiveconnector DefaultDomain Optional Microsoft.Exchange.Configuration.Tasks.AcceptedDomainIdParameter This parameter specifies the domain name to append to values that are submitted to MAIL FROM: or RCPT TO: in the message envelope by a sending server if no domain name is provided. James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Great stuff! After a default domain is supplied - how does one remove it to a blank default? I have tried many entries I thought would do the trick.

Great stuff! After a default domain is supplied - how does one remove it to a blank default? I have tried many entries I thought would do the trick. What did you already try? Typically setting to $null will work. You could always try removing the entry in adsiedit under the properties of the receive connector for that server msExchSMTPReceiveDefaultAcceptedDomainLink sounds like it would be the attribute to check.

I tried $null, null, $false, false, [ ], 0, blank, $blank All of the errors look like it is expecting me to add one of the names from the get-accepteddomain cmdlet and not a null value it was at default. Here is an error Set-ReceiveConnector "HTSSERVER\internalrelay" -defaultdomain "$null" Set-ReceiveConnector : Cannot bind parameter 'DefaultDomain'. Cannot convert value "" to type "Microsoft.Exchange.Confi guration.Tasks.AcceptedDomainIdParameter". Error: "The parameter value of this type Microsoft.Exchange.Configuration.Ta sks.AcceptedDomainIdParameter cannot be empty. Parameter name: identity" The property you show up above does contain the attribute I am looking for. In the environment I have not made this change in has this value "<not set>". In adsiedit I just changed this back to the default setting (not set) and I am seeing the behavior I expect now. Thanks for the tip!

On Fri, 8 Apr 2011 19:32:24 +0000, Hoosie2 wrote: > > >I tried $null, null, $false, false, [ ], 0, blank, $blank > >All of the errors look like it is expecting me to add one of the names from the get-accepteddomain cmdlet and not a null value it was at default. > >Here is an error > >Set-ReceiveConnector "HTSSERVER\internalrelay" -defaultdomain "$null" > >Set-ReceiveConnector : Cannot bind parameter 'DefaultDomain'. Cannot convert value "" to type "Microsoft.Exchange.Confi guration.Tasks.AcceptedDomainIdParameter". Error: "The parameter value of this type Microsoft.Exchange.Configuration.Ta sks.AcceptedDomainIdParameter cannot be empty. Parameter name: identity" > >The property you show up above does contain the attribute I am looking for. In the environment I have not made this change in has this value "<not set>". In adsiedit I just changed this back to the default setting (not set) and I am seeing the behavior I expect now. Thanks for the tip! You can use ADSIEDIT or LDP.exe to clear the property value, or you can use the bit of Powershell code below to do it: $r=[ADSI]("LDAP://"+(get-receiveconnector <name>).distinguishedname) $r.psbase.properties.msExchSMTPReceiveDefaultAcceptedDomainLink.clear() $r.psbase.CommitChanges() --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP