Quantcast
Channel: Exchange Server 2013 - Mail Flow and Secure Messaging forum
Viewing all articles
Browse latest Browse all 3660

Mail stuck in Outlook outbox

$
0
0

Hi,

 i have a exchange 2013 environment giving me this problem. I did not install this env. This environment was earlyer a DAG with

 two exchange servers both servers having all roles installed. Now I have removed the DAG and there i only one exchange server 

 with all roles. This problem started after I removed the DAG. I have increased the memory so I do not think this is because of

 lack of resources. The system will recover after ca 30 min. Restarting the transport service. There is nothing in eventlogs.

 So what is the best thing I can do regarding this. I have seen someone mention to delete receive connector and recreate them

 again not using the HubTransport but use FrontendTransport insted??

 His is how this looks,

PS] C:\Windows\system32>Get-ReceiveConnector

Identity                                Bindings

--------                                --------

EXCH03\Default EXCH03                           {0.0.0.0:2525, [::]:2525}

EXCH03\Client Proxy EXCH03              {[::]:465, 0.0.0.0:465}

EXCH03\Default Frontend EXCH03          {[::]:25, 0.0.0.0:25}

EXCH03\Outbound Proxy Frontend EXCH03   {[::]:717, 0.0.0.0:717}

EXCH03\Client Frontend EXCH03           {[::]:587, 0.0.0.0:587}

EXCH03\AnonSMTPRelay                      {0.0.0.0:25}

EXCH03\Comendo reinjection             {0.0.0.0:25}

EXCH03\RR-SCWEB01 Relay                 {0.0.0.0:25}

EXCH03\ScanReley                                  {0.0.0.0:25}

C:\Windows\system32>netstat -aon | find ":25 "

  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       6840

  TCP    10.141.1.32:25         192.168.250.251:54771  TIME_WAIT       0

  TCP    [::]:25                [::]:0                 LISTENING       6840

 pls adv



Erro


Viewing all articles
Browse latest Browse all 3660

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>