Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 368
  • Last Modified:

Mail sent from a non-Windows server cannot get resolved by sender 's name

Hi

my customer environment has  4 Exchange 2010 server SP1; 2 cas\hub exchange  and 2 Mailbox. Mailflow is ok. I have implement DAG and cas arrary with NBL. The Smtp relay server (exchange 2003).

All the exchange 2010 patched with rollup3 on w2k8R2 SP1.  

Application servers uses the MX record to send system messages to users.
For this account, tpann@XXXXXX, sometimes, the mails can be resolved as internal, showing as Announcement Publisher but sometimes it cannot resolve and show as tpann@XXXXXX (Like an external email).Also I checked SMTP message tracking logs, it seems those mails that go through SMTP-1 can resolved properly and those that go through exchange 2010, could not resolve the names.

In addition i found this  link

http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/77a06e0a-f226-437a-9e51-db528603b516

their problem is similiar to mine but their solution did not resolved my issue.

The users are on outlook 2010.
1. Does the application server reside in the Exchange 2010 organization?
a. No
2. Which Hub server relay email for the application server?
a. It is sending to cas array
3. Does the issue occur randomly or all the time?
a. All the time.
4. Is there an Exchange 2003 server in this organization?
a. Yes there 3 still active  2 BE server and 1 SMTP server 5.  What's the function of it?
a. It is used a SMTP gateway
6. Which server is SMTP-1?
a. Exchange 2003 - SMTP gateway



RunspaceId                              : 0f140c84-a77a-4491-91fd-d14dc752a3a0
AuthMechanism                           : Tls, ExternalAuthoritative
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {0.0.0.0:25}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
AdvertiseClientSettings                 : False
Fqdn                                    : EXCAHUBPRD1.XXXXXXX
Comment                                 :
Enabled                                 : True
ConnectionTimeout                       : 00:10:00
ConnectionInactivityTimeout             : 00:05:00
MessageRateLimit                        : unlimited
MessageRateSource                       : IPAddress
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize                           : 64 KB (65,536 bytes)
MaxHopCount                             : 60
MaxLocalHopCount                        : 12
MaxLogonFailures                        : 3
MaxMessageSize                          : 49.06 MB (51,445,760 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 200
PermissionGroups                        : AnonymousUsers, ExchangeServers
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {XXXXXXXXXX}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : EXCAHUBPRD1
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : App Connector
DistinguishedName                       : CN=App Connector,CN=SMTP Receive Connectors,CN=Protocols,CN=EXCAHUBPRD1,CN=Se
                                          rvers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Gr
                                          oups,CN=TP,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=XXX,DC=XXX,DC
                                          =XXX
Identity                                : EXCAHUBPRD1\App Connector
Guid                                    : b4301985-c49d-4d23-a89f-0e02b56849b2
ObjectCategory                          : XXXXXXXX/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 8/29/2011 9:10:14 AM
WhenCreated                             : 8/26/2011 9:59:57 AM
WhenChangedUTC                          : 8/29/2011 1:10:14 AM
WhenCreatedUTC                          : 8/26/2011 1:59:57 AM
OrganizationId                          :
OriginatingServer                       : stfdc2.XXXXXXXX
IsValid                                 : True

0
ramkumara
Asked:
ramkumara
1 Solution
 
kevinhsiehCommented:
That's the way it works by default, to not resolve addresses to the GAL if they are sent via an anonymous SMTP connection. Check out the article below for how to setup a new connector that will resolve the sender's address to the GAL.

http://exchangeserverpro.com/resolving-anonymous-mail-gal-exchange-server-2010
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now