Ex2007 - Ex2013 Migration - Change in Send Connector = Transport.ServerCertMismatch.Monitor

I am in the final stages of a 2007->2013 migration that has gone very well. I was just about to move my Send Connector over to the Exchange 2013 side when my monitors alarmed that "Transport.ServerCertMismatch.Monitor" had gone unhealthy.
There is not a whole lot of information out there, but I did find this in each of the MBX logs:
Microsoft Exchange could not find a certificate that contains the domain name mail.domain.com in the personal store on the local computer. Therefore, it is unable to support
the STARTTLS SMTP verb for the connector Internet e-mail with a FQDN parameter of mail.domain.com. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there
is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
I checked my SAN and I do have mail.domain.com in it. I also confirmed that the Send Connector was using mail.domain.com as its HELO/EHLO reply. I have cycled the service and that did not seem to help either. Mail will still flow in my
testing, but I do not like unhealthy statuses so I would prefer to fix it.
Thoughts?

Did you install and enable an SSL certificate with the "mail.domain.com" SAN on the Exchange 2013 CAS for the available Exchange services?
Normally, when migrating from Exchange 2007, you need to request a new SSL certificate which includes the legacy namespace in the SAN field and install it both on the new Exchange 2013 and the legacy Exchange 2007 servers.
Step by Step Screencasts and Video Tutorials

Similar Messages

Changing FQDN for Send Connector

I have Exchange 2013 CU3 here, all is working fine, as far as i see.
Recently i used DNSStuff for checking thing and discovered that SMTP Abuse results give me:
EHLO dnsstuff.com host.domain.local
and not host.domain.com
Checked my Send Connector - Internet settings in Scoping section
FQDN:
Specify the FQDN this connector will provide in response to HELO or EHLO.
is set to host.domain.com not local.
Should i also change the same on Receive connectors?
If so, how? Because it gives me:
error
If the AuthMechanism attribute on a Receive connector contains the value
ExchangeServer, you must set the FQDN parameter on the Receive connector
to one of the following values: the FQDN of the transport server
"HOST.domain.local", the NetBIOS name of the transport server "HOST", or
$null.

Sorry for late replies..
it is still unclear to me. I made new domain company.local and installed Exchange 2013, All is working good.
One thing bothers me.. for example NDR from my server includes company.local server, for example NDR to non existing user:
Diagnostic information for administrators:
Generating server: SERVER.company.local
Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
Original message headers:
Received: from SERVER.company.local (10.0.0.69) by SERVER.company.local (10.0.0.69)
with Microsoft SMTP Server (TLS) id 15.0.775.38; Mon, 14 Apr 2014 14:41:20
+0200
Received: from mail-wi0-f174.google.com (209.85.212.174) by SERVER.company.local
(10.0.0.69) with Microsoft SMTP Server id 15.0.775.38 via Frontend Transport;
or SPF check from the same NDR
Received-SPF: Pass (SERVER.company.local: domain of GMAIL_ADDRESS
designates 223.85.333.111 as permitted sender) receiver=SERVER.company.local;
client-ip=223.85.333.111; helo=mail-wi0-f174.google.com;
Is it all OK?
Thank you

Remove legacy Send connectors from Exchange 2010 after migration

Hello.
I have just removed the last legacy exchange 2003 server form our organisation.
I followed the official MS documentation for this and the remove went to plan with no errors.
The only issue I now have is that I have 2 legacy exchange send connectors in the Hub Transport view.
I have tried to disable and remove them but I get an undocumented error. The warning I get in the exchange server event logs is as follows
Process w3wp.exe () (PID=8148). Object [CN="Connector name",CN=Connections,CN="Organisation Name",CN=Routing Groups,CN="Group Name",CN=Administrative Groups,CN="Org Name",CN=Microsoft Exchange,CN=Services,CN=Configuration,DC="Domain
Name",DC="local"]. Property [HomeMtaServerId] is set to value ["Domain Name"/Configuration/Deleted Objects/Microsoft MTA
DEL:1bfa936f-c57e-4b7d-ad03-258acb560ad3], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.
Is ADSI edit the best way to remove these entries or is there another way to disable and remove?
Regards
Lee Gregory

Hi,
If the legacy send connector is no longer needed, it is ok to remove it from ADSIEdit.
For reference: select configuration as Connection point > domain > Services > MS Exchange > organizaiton name > Administrative Groups > Exchange Administrative Group > Routing Groups > First Routing Group > Connections
Regards,
Rebecca Tu
TechNet Community Support

Send connector for forwarded emails not being used by Exchange 2013

Hi we have 3 Exchange 2013 CU5 servers in a DAG setup and need to forward emails for some of the users to another domain. The problem is our outgoing spam filter seems to quarantine a lot of these emails which are not spam. The problem is that I
created a send connector for the domain we are forwarding to (say contonso.com for illustrative purposes). Gave the send connector the name contonso.com, selected use MX record (didn't select Use the external DNS lookup settings on servers with transport
roles) and added contonso.com in the address space gave it cost of 1. Added all the exchnage servers under source server. And clicked save. I then changed the cost to 2 on the main send connector with the domain as * which goes trhough our oput bound spam
filter yet email I send to one of the recipients with a forward inplace still go through that connector. Can anyone tell what i'm doing wrong or explain why this wouldn't work as expected ?

Easy question, did you enable the connector? :)
Do you have more than one site in your org?
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

Send connector with smart host redirection for particular domain

Hello,
We have quite big environment with Ex2007 CCR cluster with 2x CAS/HUB and 2x Edge servers with few accepted authoritative domains for several countries. Currently all mails from these are routed through one send connector.
We're moving to a different mail filtering service and I wanted to setup one of our domains to send through the new service to get it all setup and working correctly before moving the other domains over to it.
So i have configured dedicated new custom send connector ( in accordance with techent article: http://technet.microsoft.com/en-us/library/aa998814%28v=exchg.80%29.aspx) for one of our domains let's say contoso.com with priority 1, and in next step i have
entered smart host ip's and at the end source servers (2x edge servers).
I have spotted that mail would still not send through my new send connector for those with email addresses with that domain. I turned on verbose logging but still all emails are not going through new connector. I checked that changes were replicated succesfully
on Edge servers and I restarted on Cas/Hub machines "EdgeSync" service but still no luck.
Please help me did I forgot to check/change something?

Let me be sure I understand how you have your new send connector configured, so I don't give you the wrong information. You said you configured the new send connector with the contoso.com email domain. From how you said it, though ("one of
our domains"), it appears that email domain is one of your internal email domains. If this is the case, this is why this send connector isn't being used - the send connector will send only to those email domains listed in the address
space tab. If I am right, it will never send to any external recipients with an contoso.com email address - those mailboxes are internal. If you have an external SMTP domain in that list (such as hotmail.com), you should see messages sent to recipients
on that system through this connector.
If I am not right in how I read your posting, let me know so we can figure out how to get your send connector working properly.

Exchange 2007 Smarthost send connector backing up

I have seen some similar posts to this but none have had any good answers.
We route all outbound mail through an Barracuda spam/virus appliance. We are a busy college campus with roughly 2k staff banging away at our mail gateways with mass mailings to our students, homework assignments, class schedules, blah blah blah..
At no time is our outbound mail queue empty. The trouble is, is that at any given time the most "Active" delivery status messages I see in queue viewer is 6 messages. Whether there are 30 or 5000 messages stuck in there it never try's to send
more than 6 at a time.
Sometimes the queue viewer shows no "Active" connections just all "Ready's". I never see the status change to "Retry" or anything else other than "Ready" or "Active".
We often have delivery delays of 3 or 4 hours when mass mailing messages that do not exceed more than 10 to 20k.
Here is what we've tried so far:
In Powershell use: get-transportserver | fl   (to view these)
and use: set-transportserver -ConfiguratorName (to change the values)
updated MaxConcurrentMailboxDeliveries to 50
updated MaxConcurrentMailboxSubmissions to 50
updated PickupDirectoryMaxMessagesPerMinute to 200
MaxConnectionRatePerMinute 1200
MaxOutboundConnections 1000
MaxPerDomainOutboundConnections 1000
"...MaxMessageAttachSize" 100MB (For testing only)
use: get-sendconnector | fl    to verify the value of "MaxMessageSize". Ours is set to unlimited.
use: get-transportconfig   to check all the "Max" settings in there particularly the MaxDumpsterSizePerStorageGroup setting. Ours is 125MB.
Protocol logging is set to Verbose on the send connector. There are no error messages in the send or connectivity logs. The "Microsoft MailFlow Troubleshooter" is a joke.
We have no throttling turned on at the Barracuda level, so says their tech support. I of course have no way of verifying this as I do not have access to it.
I guess my question is. Does anyone know how or where we can increase the number of "Active" messages in the queue to more than 6 messages?

On Thu, 16 May 2013 20:19:55 +0000, Elvis P. Johnson wrote:
>We route all outbound mail through an Barracuda spam/virus appliance. We are a busy college campus with roughly 2k staff banging away at our mail gateways with mass mailings to our students, homework assignments, class schedules, blah blah blah..
>
>
>
>At no time is our outbound mail queue empty. The trouble is, is that at any given time the most "Active" delivery status messages I see in queue viewer is 6 messages. Whether there are 30 or 5000 messages stuck in there it never try's to send more than
6 at a time.
You're sending all mail to a single smart host? I'd be looking at that
machine's configuration.
>Sometimes the queue viewer shows no "Active" connections just all "Ready's". I never see the status change to "Retry" or anything else other than "Ready" or "Active".
You have only one queue, for the smart host, right? Is there a "Last
error" value for it?
Are there any "back-pressure" events in the server's application event
log?
>We often have delivery delays of 3 or 4 hours when mass mailing messages that do not exceed more than 10 to 20k.
[ snip ]
>Protocol logging is set to Verbose on the send connector. There are no error messages in the send or connectivity logs. The "Microsoft MailFlow Troubleshooter" is a joke.
>
>We have no throttling turned on at the Barracuda level, so says their tech support. I of course have no way of verifying this as I do not have access to it.
The barracuda has DOS protection. I *think* the default is to limit
the number of "parrallel connections" to 5, but that may be different
on different models. There are probably other "rate limiting"
settings, too.
>I guess my question is. Does anyone know how or where we can increase the number of "Active" messages in the queue to more than 6 messages?
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

Multiple Smart Hosts within a send connector issue

Our organization has 2 smart hosts that our hub transport can use for outbound e-mail. We have created a send-connector that lists both IPs. As expected, if one is unavailable it just uses the other. What I have noticed is that as long
as both Smart hosts are online Exchange uses a round-robin format with the 2 smart hosts for anything going out that send connector. What I am looking for is to somehow disable the round-robin feature. I would like all mail going out this send
connector to always use just 1 of the 2 smart hosts and ONLY use the second if the first is unavailable for some reason. Is this possible?

Our organization has 2 smart hosts that our hub transport can use for outbound e-mail. We have created a send-connector that lists both IPs. As expected, if one is unavailable it just uses the other. What I have noticed is that
as long as both Smart hosts are online Exchange uses a round-robin format with the 2 smart hosts for anything going out that send connector. What I am looking for is to somehow disable the round-robin feature. I would like all mail going out this
send connector to always use just 1 of the 2 smart hosts and ONLY use the second if the first is unavailable for some reason. Is this possible?
Not really possible with the native Exchange capabilities, no.
If you have a load balancer, you might be able to leverage that and have Exchange send to single namespace that is handled by the balancer.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Changing Original System and Transport Target System for Objects

Hi Gurus,
I need to do mass transport of all the Infoobjects to newly defined system. Since these objects have different Original system. Its giving me error. Again, for other objects, Transport Target system is QAS, But we want to change it to NBW (A new system to which we want to send transport) . I am able to change package of Infoobjects. Is there mechanism to change Original System and Transport Target for System? Please let me know ASAP.
Regards,
Harpal
Message was edited by:
Harpalsinh Gohil

If you simply edit your original post, it will go to the top of the list. There's no need to post duplicates.
Subjects with a subject of "Urgent" will be filtered out by a lot of responders.
Why not close this thread and bump the other one?
Rob

Send connector in different costs

Hi,
All my exchange 2010 servers are in 1 single AD site.
It seems not working when I configured item no 2.
1. address => *, source server => hub A, cost => 1
2. address => *, source server => hub B, cost => 100
It is working if I joined Hub A & Hub B under send connector source server. This configuration will send via HUB A or HUB B.
My objective is to send to cost 1 as 1st proity. Any additon configurations are needed?
P/S: I was using this following for DR MBX and DR HUB
Set-MailboxServer -Id: mbxserverA-SubmissionServerOverrideList: htserverB,htserverC
Question: is it for all send and recived connectors?
Please advise. Thanks.
Kelvin Teang

Hi,
Exchange must bind the send connector to a specific hub transport server in your Exchange organization. By default, Exchange chooses the server that you are creating the connector on, but you do have the option of specifying a different hub transport server.
To meet your requirement, you should join both Hub A and Hub B under source server.
About SubmissionServerOverrideList, Exchange Hub transport Server will be automatically load balanced within the Active Directory Site. Hub Transport Servers are load balanced in Round robin fashion within the Site. If you want to force Exchange Mailbox
server to use specific Hub Server you need to make use of SUBMISSIONSERVEROVERRIDELIST.
"Set-MailboxServer -Id: mbxserverA-SubmissionServerOverrideList: htserverB,htserverC"
The command above will set Mailbox Server mbxserverA to use htserverB and htserverC for mailsubmission.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

How do I migrate my old Send Now list of sent files to Adobe Send?

How do I migrate my old Send Now list of sent files to Adobe Send?

Bob...I understand and appreciate what you are doing by suggesting that it is our (consumer) fault that we are not ready for this and that we got e-mails. However, in the busy office, I didn't have time nor the "want to" to start the process of switching over. I don't understand why you had to make it so hard on the consumer and why not just add what services you have added or updated, or whatever you did, to send now. Another aspect of the "new and improved" (which is never improved) is that now I have to type in the addresses whereas in adobe send, we could type in one letter and the addresses that started with that letter all came up and we could choose the one we wanted. This may not be big to you, but is to me and I can imagine a few more people. I'm sorry that I have not embraced this change with open arms. Now I have to decide whether to stay with it or not. Thank you for your reply.

Is send connectors fault tolerant for source servers?

Hi!
I am in the process of applying SP3 on our Exchange 2010 environment. I have two Hubs that are both specified as source servers in our send connector to the internet. I just want to double check that when I'm applying SP3 to one of the server, that the other
server is taking care of sending all emails.
My fear is that it is only load balancing so every other email will fail to be sent because on of the hubs are down.
So can I safely update one of the servers and mail will be still sent from the other? Or should I just remove it as a source server from the send connector?
I will of course redirect incoming emails to the hub that are up at the moment.
Thanks!

Hi ,
Based on my knowledge while doing service pack upgradation on the hub transport severs there is no need to remove that particular server from source server list on the send connectors.
In addition to that mail flow will load balanced across both the hub transport servers listed on the source server list .So on such case if anyone of the server in send connector's source server list is not funtional for the particular point of time then
it will prefer the second funtional server to send emails to internet.Finally i would like to say that there wouldn't be an loss in emails.
Thanks & Regards S.Nithyanandham

Send Connector, Removing one Source Server

I have one send connector. I have two exchange servers not in HA, when I attempt to remove one of the source servers, email backs up in the que and I get this error
451.4.4.0 Primary target IP address responded with 451.5.7.3 cannot achieve exchange server authentication
I then have to add the other server back for email to go out again. Both servers are listed as source servers on the send connector. But leaving the one I want, its not routing email through that server. Do I have to restart any of the services after making
this change?

Here is the output
PS] C:\Users\administrator.PHDMI\Desktop>Get-SendConnector | FL
AddressSpaces : {SMTP:*;1}
AuthenticationCredential :
Comment :
ConnectedDomains : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled : False
DomainSecureEnabled : False
Enabled : True
ErrorPolicies : Default
ForceHELO : False
Fqdn : owa.xxx.com
HomeMTA : Microsoft MTA
HomeMtaServerId : xxxEXCH
Identity : XXX
IgnoreSTARTTLS : False
IsScopedConnector : False
IsSmtpConnector : True
LinkedReceiveConnector :
MaxMessageSize : 10 MB (10,485,760 bytes)
Name : xxx
Port : 25
ProtocolLoggingLevel : None
RequireOorg : False
RequireTLS : False
SmartHostAuthMechanism : None
SmartHosts : {outbounds6.obsmtp.com}
SmartHostsString : outbounds6.obsmtp.com
SmtpMaxMessagesPerConnection : 20
SourceIPAddress : 0.0.0.0
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {xxxEXCH0, xxxEXCH}
TlsAuthLevel :
TlsDomain :
UseExternalDNSServersEnabled : False
I added the xxx to remove our company name. I am trying to remove xxxEXCH0, but when I do email gets stuck in the que for outgoing. Now I didnt restart any services after removing EXCH0 as a source server.

Exchange 2007 send connector does nor respect Maximum message size (sometimes...)

Hi to all
We have 9 email server, 5 Mailboxes, 2 CAS and 2 HT, We began to have problems to send and receive from internet; so I checked the queues and I discovered that some users are sending messages with a size greater than 16 MB, althought internally can send
until 40MB, if they send externally, only until 16MB.
I revised all the configuration:
Organization Configuration/Hub Transport/Global Settings/ Maximum send size (KB):40960
Server Configuration/Hub Transport/HT01/Receive Connectors/Default HT01/Maximum message size(KB): 40960 (only this server can send outside, the other server is in spare)
Organization Configuration/Hub Transport/Send Connector/SendMailOuside/Maximum message size(KB) 16386
We send by an Smart host that is used only by the HT01 to a Symantec server.
With this, we have this situations:
In the queue, I see some users are sending emails with a size more than 16MB outside the organization, I revised their configuration and the "maximun send size" is clear the checkbox (just like my account), the weir is if I try to send an email
with a size more than 16MB, I got the message: "#550 5.3.4 ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##", this is not sense because their account configuration is the same like mine, so the Exchange must not let
them to put the email in the queue...
If between internal users try to send an email with size more than 16MB, this is allowed and it's send without any problem
So I don't know where is the misconfiguration, is permited to send mails with size less than 40MB internally, but externally only until to 16MB, but I din't know why the Exchange system let some users to send (or at least put in the queue) this kind of messages,
my account is in the same DB like the other users...
I hope to be clear in the description of the situation, maybe a patch or some thing, the HT server has the January patch and in april will be applied the last patchs.
Doc MX

Hi DocMX,
Thank you for your question.
We could run the following command:
Get-TransportConfig | FL max*size
Then, we could check the send connector by the following command:
Get-SendConnector | FL Identity,MaxMessageSize
We could run the following command to check an individual user maximum size.
Get-Mailbox <username> | FL Name,Max*size
In my solution, we could rebuild the user profile that those users could send emails more than 16MB to check if the issue persist.
We could also restart the service of “Microsoft Exchange Transport”.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Send Connector

I have a stupid problem with send connector.
My smart server is not accept email without sender address , as you can see on the below logs "From Address " is emty
How can I edit it ? This logs is for auto reply
Identity: Mail\1532\4982162063429
Subject: Automatic reply: Test
Internet Message ID: <41dd480d85d243e2be58f64ad23c54ce@MAIL.*****.com>
From Address: <>
Status: Ready
Size (KB): 3
Message Source Name: SMTP:Default MAIL
Source IP: ******
SCL: -1
Date Received: 2/4/2015 7:38:52 PM
Expiration Time: 2/6/2015 7:38:52 PM
Last Error:
Queue ID: Mail\1532
Recipients: *****@******.com;2;2;[{LRT=};{LED=};{FQDN=};{IP=}];0;CN=SMTP-Yahoo,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=*****,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=*****,DC=com;0

Its perfectly valid to have a null <> FROM address for auto-replies. In fact its required by RFC:
http://www.rfc-editor.org/rfc/rfc3798.txt
The envelope sender address (i.e., SMTP MAIL FROM) of the MDN MUST be
null (<>), specifying that no Delivery Status Notification messages
or other messages indicating successful or unsuccessful delivery are
to be sent in response to an MDN.
You cant change the Exchange behavior, so you will need to fix it on the smarthost server to make it honor the RFC requirement or change what you are using for a smarthost ( Exchange Edge Role perhaps)
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 - Send Connector High Availability

Hi All,
I performed a successful migration a few years back from a single node Exchange 2003 server to a two node Exchange 2010 organisation with a DAG and Kemp load balanced CAS array. The solution works well and when we simulate a site failure
I am able to get the second node to handle all mail functions.
The one problem I have though is that I have to manually disable the send connector on the primary server in order for the one on the secondary server to be in use. I should explain that I have two send connectors as I do not want the secondary server
to be used unless the primary server is down or the route is unavailable. I realise that Exchange 2010 does not know whether the SMTP route is down or not so will just continue trying to use the send connector from the primary server (until I tell it
not to by disabling it).
My question is how do I get this to happen automatically? Does anyone else have an example of how this could be done or use a PowerShell script to achieve this? I guess a script could check the route and disable the send connector on the primary
server if necessary, but how would one do this?
Any help greatly appreciated.
Rob

Hi,
According to your description, your secondary send connector cannot be automatically used when the first one is down. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if the settings of the secondary one is same with the first one and we can check the connectivity logs including diagnostic information for Healthy Server Selector.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff634392(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

Ex2007 - Ex2013 Migration - Change in Send Connector = Transport.ServerCertMismatch.Monitor

Similar Messages

Maybe you are looking for