On my Exchange 2013 servers Im getting these alerts.

Any idea of the cause?  6 servers CU9.

Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed. 

This could indicate that the mailbox submissions are taking too long or not progressing at all.
SequenceNumber: 635749917011392749

Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635749917011392749. First Run? = False. Previous mail submission to store was successful. Results - # of previous results: 0. Could Not Find stages that ran. Previous SendMail failure - Mail submitted to Store during the previous run never reached SendAsCheck. 
This may indicate a latency from Store to Submission Service. Investigating. Found lower SA latency. Indicates an issue in Submission service. 
Investigate. In SendMail - NotificationID=00000047-0000-0000-0000-00006172b8ed Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail failure. 

get-serverhealth shows:

RunspaceId              : 7d86a0bf-c2cb-44e9-a7bf-f3d3c05cdeb0
Server                  : servername
CurrentHealthSetState   : NotApplicable
Name                    : Mapi.Submit.Monitor
TargetResource          : MailboxTransport
HealthSetName           : MailboxTransport
HealthGroupName         : ServiceComponents
AlertValue              : Unhealthy
FirstAlertObservedTime  : 2015-08-12 08:00:44
Description             :
IsHaImpacting           : False
RecurranceInterval      : 0
DefinitionCreatedTime   : 2015-08-12 06:51:49
HealthSetDescription    :
ServerComponentName     : None
LastTransitionTime      : 2015-08-12 08:00:44
LastExecutionTime       : 2015-08-14 10:06:33
LastExecutionResult     : Succeeded
ResultId                : 37263684
WorkItemId              : 229
IsStale                 : False
Error                   :
Exception               :
IsNotified              : False
LastFailedProbeId       : 49
LastFailedProbeResultId : 21630588
ServicePriority         : 2
Identity                : MailboxTransport\Mapi.Submit.Monitor\MailboxTransport
IsValid                 : True
ObjectState             : New

I'm also getting the error below on some servers.

The connector with port 587 is only for clients so I guess the server cant authenticate?

Following is selected: TLS, Basic, Integrated windows, Exchange users.

The client submission probe failed 3 times over 15 minutes.
Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 421 4.3.2 Service not available
.
Probe Exception: 'System.Exception: Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 421 4.3.2 Service not available
.
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Failure Context: 'Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 421 4.3.2 Service not available
.'
Execution Context: ''
Probe Result Name: 'OnPremisesSmtpClientSubmission'
Probe Result Type: 'Failed'
Monitor Total Value: '3'
Monitor Total Sample Count: '3'
Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '2015-08-12 16:09:28'


Knowledge: http://technet.microsoft.com/en-us/library/ms.exch.scom.FrontendTransport(EXCHG.150).aspx?v=15.0.1104.5

perhaps I should make an override?

Hi Harmankdon,

Thank you for your question.

We could check the space of disk on the OS disk if there is a alter, if that, we could solve this alter then restart the Microsoft Exchange transport service.

We could refer to the following link:

https://social.technet.microsoft.com/Forums/office/en-US/fa12be4a-65b6-4f2b-9516-50a19d6bb255/receive-connector-error-452-431-insufficient-system-resources-no-back-pressure-event?forum=exchangesvrsecuremessaging

If not, we could re-create the receive connector to check if the issue persist.

Port 587 is the SMTP client submission port, for example: the port where POP and IMAP client connect to send email, so we suggest you use telnet to check if port 587 is opened on the firewall, telnet it from internal and external, then use following cmdlet to check if the Frontend Transport service is started. If not, please start the service.

Test-ServiceHealth Identity <MailboxName>

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi!
There is a lot of free space on all of the servers.

When it comes to the recieve connector it is up and running but the connector is for client use only. So I guess that the server cant authenticate but gives another error.

Any ideas of the first error?