Event id 1025 SMTP rejected a (P1) mail from 'HealthMailbox...@domain.local' with 'Client Proxy SRVEXCHANGE01' connector and the user authenticated as 'HealthMailbox...'. (Network Steve Forum)

Event id 1025 SMTP rejected a (P1) mail from 'HealthMailbox...@domain.local' with 'Client Proxy SRVEXCHANGE01' connector and the user authenticated as 'HealthMailbox...'.

I have Exchange 2010 and 2013 co-existance and on the 2013 server I'm getting an event id 1025 every 5 minutes saying:

SMTP rejected a (P1) mail from 'HealthMailbox21b2b04b53c34b6fae8a64de76ebb6d7@domain.local' with 'Client Proxy SRVEXCHANGE01' connector and the user authenticated as 'HealthMailbox21b2b04b53c34b6fae8a64de76ebb6d7'. The Active Directory lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError

I have deleted the health mailbox account on ADUC and restarted the Exchange health service. The accounts are recreated but I still get the same error. The UPN is correct as it is using the internal domain name and the account exists on the "Monitoring Mailboxes" OU.

I also get another error regarding a monitoring mailbox on "Microsoft->Exchange->ManagedAvailablity->Monitoring":

System.ApplicationException: monitoring mailbox HealthMailbox579c83137cc4455ba58139de9b4fb539@domain.local not found!

Any ideas?

Edited by Antuanfff Tuesday, March 17, 2015 2:31 PM

March 17th, 2015 2:30pm

I have enabled the verbose logging level on the connectors involved here. "Client Proxy SRVEXCHANGE01" and "Client Frontend SRVEXCHANGE01". The first one is not logging anything but I can see this error en the client frontend connector exactly at the same time that I get the error posted when I started this thread. The health mailbox authenticates but something happens afterwards when I get the Remote(SocketError). Any clue?

2015-03-24T14:21:44.426Z,SRVEXCHANGE01\Client Frontend SRVEXCHANGE01,08D2344906ADEFC9,46,127.0.0.1:587,127.0.0.1:15874,*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-03-24T14:21:44.426Z,SRVEXCHANGE01\Client Frontend SRVEXCHANGE01,08D2344906ADEFC9,47,127.0.0.1:587,127.0.0.1:15874,*,HealthMailbox4fee4b7cd8a14c47bfcfe045333e539e@siu.domain,authenticated
2015-03-24T14:21:44.473Z,SRVEXCHANGE01\Client Frontend SRVEXCHANGE01,08D2344906ADEFC9,48,127.0.0.1:587,127.0.0.1:15874,*,,Proxy session was successfully set up. Session forHealthMailbox4fee4b7cd8a14c47bfcfe045333e539e@siu.domain will now be proxied
2015-03-24T14:21:44.473Z,SRVEXCHANGE01\Client Frontend SRVEXCHANGE01,08D2344906ADEFC9,49,127.0.0.1:587,127.0.0.1:15874,>,235 2.7.0 Authentication successful,
2015-03-24T14:21:44.473Z,SRVEXCHANGE01\Client Frontend SRVEXCHANGE01,08D2344906ADEFC9,50,127.0.0.1:587,127.0.0.1:15874,-,,Remote(SocketError)

I've also checked the connectivity log and I get another error. Maybe IPv6 is messing around? I have verified that the IPv6 being used here (2002:9e25:...) is the tunnel adapter 6to4 adapter.

2015-03-24T14:21:44.441Z,08D2344906ADEFCA,SMTP,client proxy,+,Client proxy session for HealthMailbox4fee4b7cd8a14c47bfcfe045333e539e@siu.domain. Proxied session id 08D2344906ADEFC9
2015-03-24T14:21:44.441Z,08D2344906ADEFCA,SMTP,client proxy,>,"srvexchange01.siu.domain[2002:9e25:a459::9e25:a459, 158.37.164.89]"
2015-03-24T14:21:44.441Z,08D2344906ADEFCA,SMTP,client proxy,>,Established connection to 2002:9e25:a459::9e25:a459
2015-03-24T14:21:44.473Z,08D2344906ADEFCA,SMTP,,-,Messages: 0 Bytes: 0 (Remote error from proxy client)

Edited by Antuanfff 16 hours 4 minutes ago

Free Windows Admin Tool Kit Click here and download it now

March 24th, 2015 10:31am

I've also checked the connectivity log and I get another error. Maybe IPv6 is messing around? I have verified that the IPv6 being used here (2002:9e25:...) is the tunnel adapter 6to4 adapter.

Edited by Antuanfff Tuesday, March 24, 2015 3:18 PM

March 24th, 2015 2:29pm

Hi,

From your description, "FrontendTransport" is unhealthy. I recommend you check if the Microsoft Exchange Frontend Transport service is running normally. If no, please start it and check the result.

Hope this can be helpful to you.

Best regards,

Free Windows Admin Tool Kit Click here and download it now

March 25th, 2015 2:37am

The transport service is working fine. ALthoug there are only 2 mailboxes running on the Exchange server. I'm about to migrate the mailboxes from Exchange 2010 to 2013 but I'm not sure because of these errors.

The transport service crashed once some days ago (one week after the installation) and I had to restarted. Now it's been almost a week more and it haven't crashed again.

March 25th, 2015 4:35am

Hi,

In your case, it is recommended to run ExBPA against your Exchange 2010 server health before doing the migration from Exchange 2010 to Exchange 2013.

Best regards,

Free Windows Admin Tool Kit Click here and download it now

March 26th, 2015 2:41am

Hi,

Any update?

Best regards,

March 29th, 2015 10:04pm

This topic is archived. No further replies will be accepted.