Exch2k13 - What I´m missing??? Msg stuck on Draft or do not send and register logs

Exch2k13 - What Im missing???

I so frustrated right now, I installed a new server running W2k12 STD with all patchs, installed all pre-requisits to Exch2k13 and then the the first test using OWA the msgs stuck on 'Draft' folder, using outlook the msg goes to 'Sent Itens' but the msg indeed to external addres never goes out from mailserver and even if you try to send to your self the messag neve arrive to your inbox folder!
I found some forum/users asking to check DNS resolution like use a custom setting for External and Internal Lookups, I did the recommendation but no success.

If I use the cdmlet 'test-servicehealth' show no problems since all services are running. If I try to use 'mail flow/delivery' from 'server/ecp/' I cannot see any msgs that I tried.
If I use a telnet commands to connect to our server:25 and send a mail test, my mailbox receive normally at my 'inbox' folder.

>>> The simple answer "try using 2 servers that it doesnt happen" is to favorable only to MS due to more License needed!

>>> I cant believe that MS which is a big IT company and owner of Exchange code, cannot fix this issue. I cant believe!



http://social.technet.microsoft.com/Forums/exchange/en-US/21f83593-7f53-4407-a414-309fc44f129d/exchange-2013-preview-mail-stuck-in-drafts
http://blog.c7solutions.com/2012/11/missing-message-tracking-log-explorer.html

I ran the command 'Test-Mailflow' which returns as 'failure', but where is more usefull information? Event using that command with "-verbode | fl" no usefull information is provided.

###################################

How to troubleshooting that and gain the path to fix it?

 
August 28th, 2013 11:11am

You do not need two servers for this to work right.

Are all services running?  Is there anything relevant in the event log?

Free Windows Admin Tool Kit Click here and download it now
August 28th, 2013 11:45am

As my post, all services is running fine. We dont have HW and Windows license to split to 2 servers.

There is no usefull information on EventLog.

August 28th, 2013 11:53am

Ill force the diagnostice level to check

Exchange 2013 Diagnosti Logging 

http://justaucguy.wordpress.com/2013/05/21/exchange-2013-diagnostic-logging/


Free Windows Admin Tool Kit Click here and download it now
August 28th, 2013 11:57am

I said that you do NOT need two servers.

Correction:  The BPA for Exchange 2013 hasn't been released.  I don't have any information whether it ever will.

Thanks, Martina.

Messages stuck in Drafts generally indicates that they aren't being picked up by the mailbox role for delivery to the information store.  Did you remove any receive connectors?

Try a Bing search on "exchange 2013 messages stuck in draft".  There are a lot of hits you ca

August 28th, 2013 12:00pm

Even applying the Exch2013-CU2, the new msgs from OWA goes to 'Drafts' folders.
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2013 4:22pm

Ill force the diagnostice level to check

Exchange 2013 Diagnosti Logging 

http://justaucguy.wordpress.com/2013/05/21/exchange-2013-diagnostic-logging/


  • Edited by 9073241516 Wednesday, August 28, 2013 3:55 PM .
August 28th, 2013 6:55pm

Even applying the Exch2013-CU2, the new msgs from OWA goes to 'Drafts' folders.
  • Edited by 9073241516 Wednesday, August 28, 2013 8:20 PM .
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2013 11:20pm

I removed all receive/send connectors during install since I was using 'script' used for Exchange 2007.

Since Im trying to send an email to my own account/mailbox, do I still need connectors??? I created manually a SMTP Send Connector to my SMTP domain and pointing it to my own server ip address but no success.

August 29th, 2013 10:29pm

I created a new SendConnector to another domain that we host on a Zimbraserver - obviously pointing to this server IP.

No success, thw new msgs keep stuck at 'Drafts' folder, so, it let me think that the problem is not related with connectors itself.


Free Windows Admin Tool Kit Click here and download it now
August 29th, 2013 11:04pm

Ill try to recreate 'receive connectors' as the post http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts.

* I already have messages at 'Drafts' folder that I cant delete them! Anoying!! Ill try this 'tips':

"Just a final note, I resolved the messages that were undeletable in my drafts issue. I created a folder in Outlook/OWA. Then I moved the messages there, then I deleted them. Why I couldn't simply delete them, I don't know, but this worked for a couple accounts I had issues with.
Don't wast your time with migrating the user to another database, or the MFCMAPI tool, none of that worked."

August 29th, 2013 11:16pm

Another curious 'tips'

"Found the issue. I added the Exchange Server IP to it's own HOST file as both FQDN and Friendly name. After that, all email delivered correctly."

from: http://lucky120.blogspot.in/2013/04/messages-stuck-in-drafts-exchange-2013.html

Free Windows Admin Tool Kit Click here and download it now
August 29th, 2013 11:21pm

I created a new SendConnector to another domain that we host on a Zimbraserver - obviously pointing to this server IP.

No success, thw new msgs keep stuck at 'Drafts' folder, so, it let me think that the problem is not related with connectors itself.


  • Edited by 9073241516 Friday, August 30, 2013 3:03 AM .
August 30th, 2013 6:02am

Ill try to recreate 'receive connectors' as the post http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts.

* I already have messages at 'Drafts' folder that I cant delete them! Anoying!! Ill try this 'tips':

"Just a final note, I resolved the messages that were undeletable in my drafts issue. I created a folder in Outlook/OWA. Then I moved the messages there, then I deleted them. Why I couldn't simply delete them, I don't know, but this worked for a couple accounts I had issues with.
Don't wast your time with migrating the user to another database, or the MFCMAPI tool, none of that worked."

  • Edited by 9073241516 Friday, August 30, 2013 3:16 AM .
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2013 6:14am

Hi TX,

Based on my knowledge, the issue that messages stuck in draft folder in Exchange 2013 is usually caused by improper configuration on DNS. Please try to add the host entry of Exchange server in the host file and restart the Transport Service, Submission Service and DNS client.

Besides, protocol logging is much helpful for us to troubleshoot the problem. Here is the reference of Using the EAC to Configure Protocol Logging .

I hope it can help.

Regards,

Rebecca
August 30th, 2013 10:26am

Hi TX,

Based on my knowledge, the issue that messages stuck in draft folder in Exchange 2013 is usually caused by improper configuration on DNS. Please try to add the host entry of Exchange server in the host file and restart the Transport Service, Submission Service and DNS client.

Besides, protocol logging is much helpful for us to troubleshoot the problem. Here is the reference of Using the EAC to Configure Protocol Logging .

I hope it can help.

Regards,

Rebecca
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2013 5:24pm

Rebecca,

I followed this article regarding DNS but without success; that is tha why I reject your post as 'answer'.

http://lucky120.blogspot.in/2013/04/messages-stuck-in-drafts-exchange-2013.html

September 13th, 2013 12:54pm

Exchange 2013 seems to be 'a lot of bugs':

http://anewmessagehasarrived.blogspot.com.br/2013/04/irrational-behavior-of-exchange-2013.html

Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 1:59pm

I followed the article below regarding GPO but without sucess.

http://msexchangeguru.com/2013/09/03/e2013stuckindrafts/

September 13th, 2013 3:03pm

Hi,
You earlier wrote that you had deleted all connectors, but nothing about that you have recreated them (you need to).

This post has information about the the receive connectors that are created during setup and Yes...you need them.

I can also confirm that adding the Exchange Server IP (Netbios + FQDN) to the Host file has helped when messages are stuck in Draft or Exchange stops processing incomming/outgoing messages.


Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 3:37pm

Even changing the 'HOSTS' file as the post below, no sucess:

http://lucky120.blogspot.in/2013/04/messages-stuck-in-drafts-exchange-2013.html

September 13th, 2013 3:43pm

OK, then I think that you haven't successfully been able to recreate the receive connectors. Compare yours with the information in the link I posted above.
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 3:46pm

After create this connector below, msgs sent from my account through OWA to my self, worked fine instead stuck on 'Drafts' folder.

Name             : Default EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port: 2525


Here is my current config:

[PS] C:\Windows\system32>Get-ReceiveConnector | fl


RunspaceId                              : 71554f5c-599b-434b-b943-a795d3a174c4
AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {[::]:2525, 0.0.0.0:2525}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : SERVERNAME.addomain.local
ServiceDiscoveryFqdn                    :
TlsCertificateName                      :
Comment                                 :
Enabled                                 : True
ConnectionTimeout                       : 00:10:00
ConnectionInactivityTimeout             : 00:05:00
MessageRateLimit                        : Unlimited
MessageRateSource                       : IPAddress
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize                           : 128 KB (131,072 bytes)
MaxHopCount                             : 60
MaxLocalHopCount                        : 12
MaxLogonFailures                        : 3
MaxMessageSize                          : 35 MB (36,700,160 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 200
PermissionGroups                        : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : Verbose
RemoteIPRanges                          : {0.0.0.0-255.255.255.255, ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : SERVERNAME
TransportRole                           : HubTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : Default EX2013
DistinguishedName                       : CN=Default EX2013,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=SERVERNAME,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=QuboORG,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=addomain,DC=local
Identity                                : SERVERNAME\Default EX2013
Guid                                    : 3cdb3f18-1305-4c43-98ff-29546baa54b9
ObjectCategory                          : addomain.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 13/09/2013 17:04:09
WhenCreated                             : 13/09/2013 17:02:52
WhenChangedUTC                          : 13/09/2013 20:04:09
WhenCreatedUTC                          : 13/09/2013 20:02:52
OrganizationId                          :
OriginatingServer                       : SERVERNAME.addomain.local
IsValid                                 : True
ObjectState                             : Unchanged


September 13th, 2013 4:15pm

If that is the only Receive Connector you have, you have some more to re-create.

Here is the link again: http://social.technet.microsoft.com/Forums/exchange/en-US/32e13998-a84e-4f10-8557-3f7ce6fdb824/2013-default-receive-connectors

Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 4:32pm

Right now Im able to log on my OWA account and send an email test to my another server (running Zimbra) / another account.

The big question is that the MS Documentation regarding MailFlow (http://technet.microsoft.com/en-us/library/aa996349(v=exchg.150).aspx) is not clear saying the OWA - or even a Client such as Outlook - is so tied with a 'RECEIVE CONNECTOR'.

My previous understand was that since your are trying to SEND, it should use a 'SEND CONECTOR' at first step and a receive connector at the destination side as second step.

But never keep in mind that an Exchange e-mail from internal account to another - or even to myself - could be done in that way and cause too many posts with related issues. Right now I realize that the OWA receive the user request (send an email for example) and the OWA application forward that request to the server using this connector aaaaaaaaaaaaannnnnnnnnnnnndddddddddddddd then the server uses a SEND CONNECTOR in a case to send msg to external servers/account.

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

Hey MS staff, can you clarify the documentation regarding this behavior?? Another interesting point is to say in 'RED' font color: "Do not remove the default connectors".





September 13th, 2013 4:33pm

Another missing information from documentation, Is this communication tied to IPv6 or IPv4??
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 4:41pm

Good Articles to complement understanding about mail flow:

http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-mail-flow-part1.html

http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-mail-flow-part2.html

http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-mail-flow-part3.html


September 13th, 2013 4:51pm

Just to complement the information:

- I removed the static entries on 'C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS' file as recomended on another foruns (I alredy put the links above)

+

- restarted the server

=

>>> Im still able to send e-mail to my self or to my another server/account.

>>> So, the problem of msgs 'stuck in draft' is not related with this!

Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 4:58pm

Just to complement the information:

- I did the reverse of this article (http://thoughtsofanidlemind.wordpress.com/2013/03/25/exchange-2013-dns-stuck-messages/), in a way to put my server to use DNS servers from 'Network Interfaces' instead to use specific settings.


=

>>> Im still able to send e-mail to my self or to my another server/account.

>>> So, the problem of msgs 'stuck in draft' is not related with this!
September 13th, 2013 5:32pm

I created another RECEIVE CONNECTOR to receive email from another servers

Name             : Default Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Porta: 25

>>>

>>>>>>

>>>>>>>>>>>>>>>>>>>>> But do I still need these another ones below??

I suppose that "Client Frontend EX2013" we can use due to printers (multifunctional) send emails for scan docs - as we do using Exch2007.

Name             : Client Proxy EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port: 465


Name             : Outbound Proxy Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Porta:717

Name             : Client Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : ExchangeUsers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port: 587



Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 5:48pm

After create this connector below, msgs sent from my account through OWA to my self, worked fine instead stuck on 'Drafts' folder.

Name             : Default EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port: 2525


Here is my current config:

[PS] C:\Windows\system32>Get-ReceiveConnector | fl


RunspaceId                              : 71554f5c-599b-434b-b943-a795d3a174c4
AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {[::]:2525, 0.0.0.0:2525}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : SERVERNAME.addomain.local
ServiceDiscoveryFqdn                    :
TlsCertificateName                      :
Comment                                 :
Enabled                                 : True
ConnectionTimeout                       : 00:10:00
ConnectionInactivityTimeout             : 00:05:00
MessageRateLimit                        : Unlimited
MessageRateSource                       : IPAddress
MaxInboundConnection                    : 5000
MaxInboundConnectionPerSource           : 20
MaxInboundConnectionPercentagePerSource : 2
MaxHeaderSize                           : 128 KB (131,072 bytes)
MaxHopCount                             : 60
MaxLocalHopCount                        : 12
MaxLogonFailures                        : 3
MaxMessageSize                          : 35 MB (36,700,160 bytes)
MaxProtocolErrors                       : 5
MaxRecipientsPerMessage                 : 200
PermissionGroups                        : ExchangeUsers, ExchangeServers, ExchangeLegacyServers
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : Verbose
RemoteIPRanges                          : {0.0.0.0-255.255.255.255, ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : SERVERNAME
TransportRole                           : HubTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : Default EX2013
DistinguishedName                       : CN=Default EX2013,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=SERVERNAME,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=QuboORG,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=addomain,DC=local
Identity                                : SERVERNAME\Default EX2013
Guid                                    : 3cdb3f18-1305-4c43-98ff-29546baa54b9
ObjectCategory                          : addomain.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 13/09/2013 17:04:09
WhenCreated                             : 13/09/2013 17:02:52
WhenChangedUTC                          : 13/09/2013 20:04:09
WhenCreatedUTC                          : 13/09/2013 20:02:52
OrganizationId                          :
OriginatingServer                       : SERVERNAME.addomain.local
IsValid                                 : True
ObjectState                             : Unchanged


  • Edited by 9073241516 Friday, September 13, 2013 8:14 PM .
September 13th, 2013 11:12pm

Right now Im able to log on my OWA account and send an email test to my another server (running Zimbra) / another account.

The big question is that the MS Documentation regarding MailFlow (http://technet.microsoft.com/en-us/library/aa996349(v=exchg.150).aspx) is not clear saying the OWA - or even a Client such as Outlook - is so tied with a 'RECEIVE CONNECTOR'.

My previous understand was that since your are trying to SEND, it should use a 'SEND CONECTOR' at first step and a receive connector at the destination side as second step.

But never keep in mind that an Exchange e-mail from internal account to another - or even to myself - could be done in that way and cause too many posts with related issues. Right now I realize that the OWA receive the user request (send an email for example) and the OWA application forward that request to the server using this connector aaaaaaaaaaaaannnnnnnnnnnnndddddddddddddd then the server uses a SEND CONNECTOR in a case to send msg to external servers/account.

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

Hey MS staff, can you clarify the documentation regarding this behavior?? Another interesting point is to say in 'RED' font color: "Do not remove the default connectors".





  • Edited by 9073241516 Friday, September 13, 2013 8:34 PM .
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 11:30pm

Another missing information from documentation, Is this communication tied to IPv6 or IPv4??
  • Edited by 9073241516 Friday, September 13, 2013 8:43 PM .
September 13th, 2013 11:39pm

I created another RECEIVE CONNECTOR to receive email from another servers

Name             : Default Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers, ExchangeLegacyServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Porta: 25

>>>

>>>>>>

>>>>>>>>>>>>>>>>>>>>> But do I still need these another ones below??

I suppose that "Client Frontend EX2013" we can use due to printers (multifunctional) send emails for scan docs - as we do using Exch2007.

Name             : Client Proxy EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : HubTransport
PermissionGroups : ExchangeUsers, ExchangeServers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port: 465


Name             : Outbound Proxy Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : AnonymousUsers, ExchangeServers
MaxMessageSize   : 36 MB (37,748,736 bytes)
Porta:717

Name             : Client Frontend EX2013
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
RemoteIPRanges   : {::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
TransportRole    : FrontendTransport
PermissionGroups : ExchangeUsers
MaxMessageSize   : 35 MB (36,700,160 bytes)
Port: 587



  • Edited by 9073241516 Friday, September 13, 2013 9:48 PM .
September 14th, 2013 12:45am

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

Other recent topics Other recent topics