I am running Exchange 2010 on-prem with a 2013 Hybrid (including a 2013 Edge Transport server for message handling between on-prem and the o365 tenant) connecting to an o365 tenant. I use EMC's SourceOne for archiving running on-prem. The o365 tenant points to a mailbox on my on-prem Journaling server.

What I am seeing is that when o365 forwards emails as attachments from the cloud back to the on-prem Journaling server it is examining the subject line of the message and making a decision to strip the attachment based upon the very end of the subject line.

Example: A simple text message with a subject line of: "Check out the new web site at www.xyz.com"

The Edge transport server is seeing this as being a ".com" attachment and stripping it off before it gets to the Journaling server. So it does not appear to be looking inside the message to see what it actually is and figure out that it is not a ".com" file but a simple text message.

I have seen this with other file extension types as well. Such as ".exe" . It is also stripping off ".zip" attachments as well, but I understand that and not sure how to deal with it.

Has anyone else experienced this and how have you dealt with it? Microsoft wants me to take the Edge out of play and go directly to from the cloud to an on-prem Exchange server. But that is not an option as the on-prem servers are not exposed to the internet.

Thanks, Bob

I have recently migrated from Exchange 2013.  I have several internal IP addresses that I would like to allow to send email from via applications and also a scanner.  I have set up a receive connector and allowed the internal IP range and anonymous access and have verified that it works fine.  

It seems the anti-spam system seems to to block the email as I get a notification on the administrators account of failed delivery. I could allow the spam system to bypass the domain but this would allow any spam with the domain name to come through.

Any ideas?

Hello,

As per the title, I have an issue whereby internal email from a reporting server is being classed as Junk in Outlook 2010 and 2013 for all recipients.

 -The Junk-email filtering level for all users in Outlook is set to "Low" and is applied via group policy.

 -I have anti-spam agents installed on all Exchange mailbox servers, but the "InternalMailEnabled" parameter is set to "false" for all agents.

 -The receive connector used to receive internal email has the "Externally secured" flag set, which allows spam-filtering to be bypassed.

 -The "InternalSMTPServers" parameter of the transport config contains the IP of the sending server.

- The email address has been added to several users "Safe Senders" list in Outlook.

 -I have a transport rule set up to bypass spam filtering for the sending address of the SQLReportingServices@domain.com, yet the email header on any of these messages does not contain the "SCL -1" stamp as per the below:

#↓    Header    Value
1    MIME-Version    1.0
2    From    <SQLReportingServices@domain.com>
3    To    <User1@domain.com>, <user2@domain.com>
4    Date    Tue, 10 Mar 2015 07:35:32 +0000
5    Subject    Report was executed at 10/03/2015 07:35:08
6    Content-Type    multipart/mixed; boundary="--boundary_90_638c99de-c35d-4d06-b992-536e14201c6d"
7    Message-ID    <dacbc167cba2410aa0a0c2088bdff95c@SERVER01.domain.localnet>
8    Return-Path    SQLReportingServices@domain.com
9    X-MS-Exchange-Organization-AuthSource    SERVER01.domain.localnet
10    X-MS-Exchange-Organization-AuthAs    Internal
11    X-MS-Exchange-Organization-AuthMechanism    10
12    X-MS-Exchange-Organization-Network-Message-Id    8d357628-f2e9-48d5-77e2-08d2291beca4
13    X-MS-Exchange-Organization-AVStamp-Enterprise    1.0

Can anyone assist in explaining why these emails are being continually marked as Junk in Outlook, and any further troubleshooting steps.

Thanks

Matt

Exchange 2007

Currently getting an error with StartTLS SMTP. Unable to locate a valid certificate. Here is my Get-ExchangeCertificate output. It indicates my certs are invalid. there are also two on here that are expired.

AccessRules          : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains   : {www.domain.com, domain.com, exch.domain.net, autodiscover.domain.com, webmail.domain.com, mail.domain.com, autodiscover.domain.net}
CertificateRequest   :
IisServices          : {IIS://exch/W3SVC/1}
IsSelfSigned         : False
KeyIdentifier        : xxxxxxxxxxxxxxxxxxxxxxxx
RootCAType           : Unknown
Services             : IMAP, POP, IIS, SMTP
Status               : Invalid
PrivateKeyExportable : True
Archived             : False
Extensions           : {System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, Syste
                       m.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid, System.Security.Cryptography.Oid}
FriendlyName         : Microsoft Exchange
IssuerName           : System.Security.Cryptography.X509Certificates.X500DistinguishedName
NotAfter             : 3/4/2016 11:43:05 AM
NotBefore            : 2/26/2015 3:14:40 PM
HasPrivateKey        : True
PrivateKey           : System.Security.Cryptography.RSACryptoServiceProvider
PublicKey            : System.Security.Cryptography.X509Certificates.PublicKey
RawData              : {48, 130, 5, 166, 48, 130, 4, 142, 160, 3, 2, 1, 2, 2, 8, 70...}
SerialNumber         : XXXXXXXXXXXXXXXXXXXXXXX
SubjectName          : System.Security.Cryptography.X509Certificates.X500DistinguishedName
SignatureAlgorithm   : System.Security.Cryptography.Oid
Thumbprint           : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Version              : 3
Handle               : 509608784
Issuer               : CN=Go Daddy Secure Certificate Authority - G2, OU=http://certs.godaddy.com/repository/, O="GoDaddy.com, Inc.", L=Scottsdale, S=Arizona, C=US
Subject              : CN=www.domain.com, OU=Domain Control Validated

AccessRules          : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains   : {www.domain.com}
CertificateRequest   : XXXXXXXXXXX
IisServices          : {}
IsSelfSigned         : True
KeyIdentifier        : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
RootCAType           : Unknown
Services             : None
Status               : Invalid
PrivateKeyExportable : True
Archived             : False
Extensions           : {}
FriendlyName         : Microsoft Exchange
IssuerName           : System.Security.Cryptography.X509Certificates.X500DistinguishedName
NotAfter             : 2/26/2016 8:53:48 PM
NotBefore            : 2/26/2015 2:53:48 PM
HasPrivateKey        : True
PrivateKey           : System.Security.Cryptography.RSACryptoServiceProvider
PublicKey            : System.Security.Cryptography.X509Certificates.PublicKey
RawData              : {48, 130, 2, 81, 48, 130, 2, 62, 160, 3, 2, 1, 2, 2, 16, 134...}
SerialNumber         : XXXXXXXXXXXXXXXXXXXXXXXXXX
SubjectName          : System.Security.Cryptography.X509Certificates.X500DistinguishedName
SignatureAlgorithm   : System.Security.Cryptography.Oid
Thumbprint           : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Version              : 3
Handle               : 509601504
Issuer               : CN=www.domain.com, O=Company Intl., S=California, L=Irvine, C=US
Subject              : CN=www.domain.com, O=Company Intl., S=California, L=Irvine, C=US

AccessRules          : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains   : {mail.domain.com}
CertificateRequest   : XXXXXXXXXXXXXXXXXXX
IisServices          : {}
IsSelfSigned         : True
KeyIdentifier        : XXXXXXXXXXXXXXXXXXXXXX
RootCAType           : Unknown
Services             : None
Status               : Invalid
PrivateKeyExportable : True
Archived             : False
Extensions           : {}
FriendlyName         : Microsoft Exchange
IssuerName           : System.Security.Cryptography.X509Certificates.X500DistinguishedName
NotAfter             : 2/26/2016 8:49:38 PM
NotBefore            : 2/26/2015 2:49:38 PM
HasPrivateKey        : True
PrivateKey           : System.Security.Cryptography.RSACryptoServiceProvider
PublicKey            : System.Security.Cryptography.X509Certificates.PublicKey
RawData              : {48, 130, 2, 83, 48, 130, 2, 64, 160, 3, 2, 1, 2, 2, 16, 181...}
SerialNumber         : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
SubjectName          : System.Security.Cryptography.X509Certificates.X500DistinguishedName
SignatureAlgorithm   : System.Security.Cryptography.Oid
Thumbprint           : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Version              : 3
Handle               : 509602800
Issuer               : CN=mail.domain.com, O=Company Intl., S=California, L=Irvine, C=US
Subject              : CN=mail.domain.com, O=Company Intl., S=California, L=Irvine, C=US

AccessRules          : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains   : {www.domain.com}
CertificateRequest   : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
IisServices          : {}
IsSelfSigned         : True
KeyIdentifier        : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
RootCAType           : Unknown
Services             : None
Status               : Invalid
PrivateKeyExportable : False
Archived             : False
Extensions           : {}
FriendlyName         : Microsoft Exchange
IssuerName           : System.Security.Cryptography.X509Certificates.X500DistinguishedName
NotAfter             : 2/24/2012 7:57:09 PM
NotBefore            : 2/24/2011 1:57:09 PM
HasPrivateKey        : True
PrivateKey           : System.Security.Cryptography.RSACryptoServiceProvider
PublicKey            : System.Security.Cryptography.X509Certificates.PublicKey
RawData              : {48, 130, 2, 81, 48, 130, 2, 62, 160, 3, 2, 1, 2, 2, 16, 38...}
SerialNumber         : XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
SubjectName          : System.Security.Cryptography.X509Certificates.X500DistinguishedName
SignatureAlgorithm   : System.Security.Cryptography.Oid
Thumbprint           : XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Version              : 3
Handle               : 509601104
Issuer               : CN=www.domain.com, O=Company International, S=CA, L=Irvine, C=US
Subject              : CN=www.domain.com, O=Company International, S=CA, L=Irvine, C=US

AccessRules          : {System.Security.AccessControl.CryptoKeyAccessRule, System.Security.AccessControl.CryptoKeyAccessRule}
CertificateDomains   : {www.domain.com}
CertificateRequest   : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
IisServices          : {}
IsSelfSigned         : True
KeyIdentifier        : XXXXXXXXXXXXXXXXXXXXXXXXXXXX
RootCAType           : Unknown
Services             : None
Status               : Invalid
PrivateKeyExportable : False
Archived             : False
Extensions           : {}
FriendlyName         : Microsoft Exchange
IssuerName           : System.Security.Cryptography.X509Certificates.X500DistinguishedName
NotAfter             : 2/24/2012 7:56:13 PM
NotBefore            : 2/24/2011 1:56:13 PM
HasPrivateKey        : True
PrivateKey           : System.Security.Cryptography.RSACryptoServiceProvider
PublicKey            : System.Security.Cryptography.X509Certificates.PublicKey
RawData              : {48, 130, 2, 81, 48, 130, 2, 62, 160, 3, 2, 1, 2, 2, 16, 178...}
SerialNumber         : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
SubjectName          : System.Security.Cryptography.X509Certificates.X500DistinguishedName
SignatureAlgorithm   : System.Security.Cryptography.Oid
Thumbprint           : XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Version              : 3
Handle               : 509602944
Issuer               : CN=www.domain.com, O=Company International, S=CA, L=Irvine, C=US
Subject              : CN=www.domain.com, O=Company International, S=CA, L=Irvine, C=US

Any help would be appreciated.

We are experiecing delay of emails for users because of the Throttlig on Exchange 2013 servers.

This is causing company wide Delay and users are complaining as it takes a lot of time for the queue to get cleared.

We called in Microsoft and they suggested some values changes to msexchangedelivery.exe.config file

We added the following values, but still we face issues when there is Email flood.

Any one faced this or any suggestions that you have.

mdimthyas

Hi,

I was wonder if anyone has any advice or solution for the below:

I have a situation where we want a single email address in our dns namespace e.g. user@abc.com to be routed to a secondary mail server on our network. The @abc.com portion must be maintained.

I have read a number of article on setting up exchange and other mail server sharing the same namespace,  however I only want a specific email address to be routed, not all addresses not found sent to secondary server.

Thanks in advance.

Peter

Office Server Addict

When the AddressBookPolicyRoutingEnabled attribute is enabled by running Set-TransportConfig -AddressBookPolicyRoutingEnabled $True, I am having an issue with delivery failures for mailboxes that are hidden from the address book. I receive the following undeliverable message:

'532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties'

If I disable the AddressBookPolicyRoutingEnabled attribute by running Set-TransportConfig -AddressBookPolicyRoutingEnabled $False then emails are successfully delivered to the mailbox that is hidden from the address list.

I followed the installation instructions here: http://technet.microsoft.com/en-us/library/jj907308(v=exchg.150).aspx

Below is the status of the ABP Routing Agent on my Hub Transport/Mailbox server:

Enabled: True
Priority: 5
TransportAgentFactory: Microsoft.Exchange.Transport.Agent.AddressBookPolicyRoutingAgent.AddressBookPolicyRoutingAgentFactory
AssemblyPath: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\AddressBookPolicyRoutingAgent\Microsoft.Exchange.Transport.Agent.AddressBookPolicyRoutingAgent.dll
Identity: ABP Routing Agent
IsValid: True
ObjectState: New

Has anyone else run into this issue yet?

We're having an issue where users that are members of various distribution groups are not reliably receiving messages. We have a newsletter that is sent out weekly by one user. They use 4 internal distribution groups (some of them nested) plus external email addresses that add up to around 1170 recipients. We have around 280 internal users. Of those 280, around 100 are delivered, and 170 are not delivered but show as "pending" in the delivery report. External users seem to be receiving messages fine. 

I tried doing a trace on myself, as I didn't receive the newsletter that was sent out yesterday.

$Temp = Search-MessageTrackingReport -Identity lorraine.user -Recipients jsmith@domain.ca

[PS] C:\Windows\system32>$Temp | %{Get-MessageTrackingReport -Identity $_.MessageTrackingReportID -BypassDelegateCheckin
g -ReportTemplate Summary }

The missing message was not in the list. It should have been the first result.

Here is an example of how one of the pending delivery reports look like:

Environment:

Exchange 2013 CU7

2 Servers running Windows Server 2012 in a DAG

Hi

I've inherited an Exchange 2013 server that is acting as an open relay.  I've looked at the connectors for send and receive and I can't see why it would allow relay to happen.  Any hints?

Send Connector:

AddressSpaces                : {SMTP:*;1}
AuthenticationCredential     :
CloudServicesMailEnabled     : False
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut  : 00:10:00
DNSRoutingEnabled            : True
DomainSecureEnabled          : False
Enabled                      : True
ErrorPolicies                : Default
ForceHELO                    : False
Fqdn                         :
FrontendProxyEnabled         : False
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : KRYSTALMX
Identity                     : Internet
IgnoreSTARTTLS               : False
IsScopedConnector            : True
IsSmtpConnector              : True
MaxMessageSize               : 35 MB (36,700,160 bytes)
Name                         : Internet
Port                         : 25
ProtocolLoggingLevel         : None
RequireOorg                  : False
RequireTLS                   : False
SmartHostAuthMechanism       : None
SmartHosts                   : {}
SmartHostsString             :
SmtpMaxMessagesPerConnection : 20
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {KRYSTALMX}
TlsAuthLevel                 :
TlsCertificateName           :
TlsDomain                    :
UseExternalDNSServersEnabled : True

Receive Connectors:

RunspaceId                              : f896b683-39f9-4123-b026-e7c106cf7210
AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {192.168.1.4:2525}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
SmtpUtf8Enabled                         : False
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : krystalmx.krystal.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, Custom
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {0.0.0.0-255.255.255.255}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : KRYSTALMX
TransportRole                           : HubTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : Default Exchange2013
DistinguishedName                       : CN=Default Exchange2013,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=KRYSTALMX,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Krystal,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=krystal,DC=local
Identity                                : KRYSTALMX\Default Exchange2013
Guid                                    : bc55ad7a-6265-4022-96d4-4ab4c48e88d9
ObjectCategory                          : krystal.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 24/01/2015 09:39:43
WhenCreated                             : 24/01/2015 09:39:30
WhenChangedUTC                          : 24/01/2015 09:39:43
WhenCreatedUTC                          : 24/01/2015 09:39:30
OrganizationId                          :
Id                                      : KRYSTALMX\Default Exchange2013
OriginatingServer                       : KrystalDC.krystal.local
IsValid                                 : True
ObjectState                             : Unchanged

RunspaceId                              : f896b683-39f9-4123-b026-e7c106cf7210
AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {192.168.1.4:465}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
SmtpUtf8Enabled                         : False
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : krystalmx.krystal.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, Custom
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {0.0.0.0-255.255.255.255}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : KRYSTALMX
TransportRole                           : HubTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : ClientProxy Exchange2013
DistinguishedName                       : CN=ClientProxy Exchange2013,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=KRYSTALMX,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Krystal,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=krystal,DC=local
Identity                                : KRYSTALMX\ClientProxy Exchange2013
Guid                                    : 2255a890-0067-47ab-b15d-b58519bcccb3
ObjectCategory                          : krystal.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 24/01/2015 09:40:50
WhenCreated                             : 24/01/2015 09:40:49
WhenChangedUTC                          : 24/01/2015 09:40:50
WhenCreatedUTC                          : 24/01/2015 09:40:49
OrganizationId                          :
Id                                      : KRYSTALMX\ClientProxy Exchange2013
OriginatingServer                       : KrystalDC.krystal.local
IsValid                                 : True
ObjectState                             : Unchanged

RunspaceId                              : f896b683-39f9-4123-b026-e7c106cf7210
AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {192.168.1.4:25}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
SmtpUtf8Enabled                         : False
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : KRYSTALMX
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                        : AnonymousUsers, ExchangeServers, ExchangeLegacyServers, Custom
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {0.0.0.0-255.255.255.255}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : KRYSTALMX
TransportRole                           : FrontendTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : Default Frontend Exchange2013
DistinguishedName                       : CN=Default Frontend Exchange2013,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=KRYSTALMX,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Krystal,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=krystal,DC=local
Identity                                : KRYSTALMX\Default Frontend Exchange2013
Guid                                    : 56733f09-ae32-4f45-91be-bf51fb6a3046
ObjectCategory                          : krystal.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 03/02/2015 10:21:30
WhenCreated                             : 24/01/2015 11:12:08
WhenChangedUTC                          : 03/02/2015 10:21:30
WhenCreatedUTC                          : 24/01/2015 11:12:08
OrganizationId                          :
Id                                      : KRYSTALMX\Default Frontend Exchange2013
OriginatingServer                       : KrystalDC.krystal.local
IsValid                                 : True
ObjectState                             : Unchanged

RunspaceId                              : f896b683-39f9-4123-b026-e7c106cf7210
AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {192.168.1.4:717}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
SmtpUtf8Enabled                         : False
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : krystalmx.krystal.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, Custom
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {0.0.0.0-255.255.255.255}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : KRYSTALMX
TransportRole                           : FrontendTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : Outbound Proxy Frontend Exchange2013
DistinguishedName                       : CN=Outbound Proxy Frontend Exchange2013,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=KRYSTALMX,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Krystal,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=krystal,DC=local
Identity                                : KRYSTALMX\Outbound Proxy Frontend Exchange2013
Guid                                    : bd749317-68c5-4b4d-b401-166e7fac3b92
ObjectCategory                          : krystal.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 03/02/2015 13:51:43
WhenCreated                             : 24/01/2015 11:13:12
WhenChangedUTC                          : 03/02/2015 13:51:43
WhenCreatedUTC                          : 24/01/2015 11:13:12
OrganizationId                          :
Id                                      : KRYSTALMX\Outbound Proxy Frontend Exchange2013
OriginatingServer                       : KrystalDC.krystal.local
IsValid                                 : True
ObjectState                             : Unchanged

RunspaceId                              : f896b683-39f9-4123-b026-e7c106cf7210
AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
Banner                                  :
BinaryMimeEnabled                       : True
Bindings                                : {192.168.1.4:587}
ChunkingEnabled                         : True
DefaultDomain                           :
DeliveryStatusNotificationEnabled       : True
EightBitMimeEnabled                     : True
SmtpUtf8Enabled                         : False
BareLinefeedRejectionEnabled            : False
DomainSecureEnabled                     : False
EnhancedStatusCodesEnabled              : True
LongAddressesEnabled                    : False
OrarEnabled                             : False
SuppressXAnonymousTls                   : False
ProxyEnabled                            : False
AdvertiseClientSettings                 : False
Fqdn                                    : krystalmx.krystal.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, Custom
PipeliningEnabled                       : True
ProtocolLoggingLevel                    : None
RemoteIPRanges                          : {0.0.0.0-255.255.255.255}
RequireEHLODomain                       : False
RequireTLS                              : False
EnableAuthGSSAPI                        : False
ExtendedProtectionPolicy                : None
LiveCredentialEnabled                   : False
TlsDomainCapabilities                   : {}
Server                                  : KRYSTALMX
TransportRole                           : FrontendTransport
SizeEnabled                             : Enabled
TarpitInterval                          : 00:00:05
MaxAcknowledgementDelay                 : 00:00:30
AdminDisplayName                        :
ExchangeVersion                         : 0.1 (8.0.535.0)
Name                                    : Client Frontend Exchange2013
DistinguishedName                       : CN=Client Frontend Exchange2013,CN=SMTP Receive
                                          Connectors,CN=Protocols,CN=KRYSTALMX,CN=Servers,CN=Exchange Administrative
                                          Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Krystal,CN=Microsoft
                                          Exchange,CN=Services,CN=Configuration,DC=krystal,DC=local
Identity                                : KRYSTALMX\Client Frontend Exchange2013
Guid                                    : 52f3d6e9-5a79-4055-8d39-61235bf3627e
ObjectCategory                          : krystal.local/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
ObjectClass                             : {top, msExchSmtpReceiveConnector}
WhenChanged                             : 24/01/2015 11:14:23
WhenCreated                             : 24/01/2015 11:14:23
WhenChangedUTC                          : 24/01/2015 11:14:23
WhenCreatedUTC                          : 24/01/2015 11:14:23
OrganizationId                          :
Id                                      : KRYSTALMX\Client Frontend Exchange2013
OriginatingServer                       : KrystalDC.krystal.local
IsValid                                 : True
ObjectState                             : Unchanged

MX>

1, cotonso-c0mi.mail.protection.outlook.com > 213.199.154.87, 213.199.154.23

100, mail.messaging.microsoft.com >207.46.163.247,207.46.163.215,207.46.163.138

Hi,

I would like find out some information and clarification with above MX record setup

1) Do EOP setup always can add mail.messaging.microsoft.com as secondary MX record?

2) What if on premise Exchange not available, do the EOP retry send for 48 hrs?

3) Are the 2 MX record work the same on resending and retry in the event on premise Exchange not available?

4) Is this a recommended way or best practice?

Dear All,

I having a Exchange 2007 migrate to Exchange 2013 issue.

I deploy a all in one Exchange 2013 server.

When telnet it's 25 port, it will show "451 4.7.0 Temporary server error. Please try again later. PRX4"
after enter mail from, rcpt to, data.

Exchange 2013 now can't receive and email and send out any email....

I have read all relating post from fourm, i tried below:

- Revise the DNS issue
- Add hosts file
- Review Receive connector , ensure there have Exchange Server
- Dcdiag also normal
- Get-ServerCompentState HubTransport also is active
- Tried create another receive connector ( Open relay...also get same error...)
- AntiSpam was disabled
- Malware filter also disable and bypass 

Some SMTP Receive Log:

50-Hello [127.0.0.1],
,250-SIZE 37748736,
,250-PIPELINING,
,250-DSN,
250-ENHANCEDSTATUSCODES,
,250-STARTTLS,
,250-X-ANONYMOUSTLS,
,250-AUTH NTLM,
,250-X-EXPS GSSAPI NTLM,
>,250-8BITMIME,
>,250-BINARYMIME,
>,250-CHUNKING,
>,250 XRDST,
<,MAIL FROM: inboundproxy@contoso.com,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
*,08D22B73408371ED;2015-03-13T15:22:46.990Z;1,receiving message
>,<,RCPT TO: HealthMailbox1bcaf8efe11243d0ade60c4d14533685@artapower.com,
,>,250 2.1.5 Recipient OK,
,<,DATA,

,>,354 Start mail input; end with <CRLF>.<CRLF>,
,*,,Proxy destination(s) obtained from OnProxyInboundMessage event
,*,,"Message or connection acked with status Retry and response 451 4.4.0 Primary target IP address responded with: ""421 4.4.1 Connection timed out."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 10.0.182.19:2525"
,>,451 4.7.0 Temporary server error. Please try again later. PRX4 ,
,<,QUIT,
>,221 2.0.0 Service closing transmission channel,
,-,,Local
,+,,

Front END Connect Log:

2015-03-13T18:12:03.069Z,08D22BD02A6B29D2,SMTP,client proxy,>,Established connection to 10.0.182.19
2015-03-13T18:12:03.081Z,08D22BD02A6B29D2,SMTP,client proxy,-,Messages: 0 Bytes: 0 (Retry : Security status InternalError)
2015-03-13T18:12:49.821Z,08D22BD02A6B29D5,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>. Starting outbound connection for inbound session 08D22BD02A6B29D4
2015-03-13T18:12:49.822Z,08D22BD02A6B29D5,SMTP,internalproxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:12:49.823Z,08D22BD02A6B29D5,SMTP,internalproxy,>,Established connection to 10.0.182.19
2015-03-13T18:12:49.833Z,08D22BD02A6B29D5,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : Connection timed out)
2015-03-13T18:12:53.123Z,08D22BD02A6B29D7,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>. Starting outbound connection for inbound session 08D22BD02A6B29D6
2015-03-13T18:12:53.124Z,08D22BD02A6B29D7,SMTP,internalproxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:12:53.124Z,08D22BD02A6B29D7,SMTP,internalproxy,>,Established connection to 10.0.182.19
2015-03-13T18:12:53.134Z,08D22BD02A6B29D7,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : Connection timed out)
2015-03-13T18:14:25.580Z,,Transport,,*,service stopped
2015-03-13T18:14:32.144Z,,Transport,,*,service started; MaxConcurrentSubmissions=240; MaxConcurrentDeliveries=240; MaxSmtpOutConnections=Unlimited
2015-03-13T18:15:16.903Z,,Transport,,*,service stopped
2015-03-13T18:15:23.699Z,,Transport,,*,service started; MaxConcurrentSubmissions=240; MaxConcurrentDeliveries=240; MaxSmtpOutConnections=Unlimited
2015-03-13T18:16:40.566Z,08D22BD0E053AA0E,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>. Starting outbound connection for inbound session 08D22BD0E053AA0D
2015-03-13T18:16:40.793Z,08D22BD0E053AA0E,SMTP,internalproxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:16:40.886Z,08D22BD0E053AA0E,SMTP,internalproxy,>,Established connection to 10.0.182.19
2015-03-13T18:16:40.903Z,08D22BD0E053AA0E,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : Connection timed out)
2015-03-13T18:17:03.076Z,08D22BD0E053AA11,SMTP,client proxy,+,Client proxy session for HealthMailbox6c592afa20d245b6b1bde8e7179ada20@artapower.com. Proxied session id 08D22BD0E053AA10
2015-03-13T18:17:03.077Z,08D22BD0E053AA11,SMTP,client proxy,>,ARTAEX13SV.artapower.com[10.0.182.19]
2015-03-13T18:17:03.078Z,08D22BD0E053AA11,SMTP,client proxy,>,Established connection to 10.0.182.19
2015-03-13T18:17:03.090Z,08D22BD0E053AA11,SMTP,client proxy,-,Messages: 0 Bytes: 0 (Retry : Security status InternalError)

Hi,

A user has just realised that only some of our emails from any user in our domain have been delivered to an external domain for the last month and a half.

We haven't had any reports from any other domains regarding the same issue. Just this one.

There doesn't seem to be any pattern to the emails that deliver and those that don't at the moment.

I have been shown an email that we know was not delivered to the external address in question.

I have checked the transport logs and it shows; EventId: HARedirectFail Source: SMTP

In the event viewer at the same time I have an information message with; Event ID: 103Source: ESENT

Running on MS Windows Server 2012, Exchange 2013, sophos pure message 4.0.

I would very much appreciate any input or help on this matter big or small.

Thanks

JCronies

Hello everyone,

I was wondering if someone can help me with resolve a problem. I recovered the exchange 2013 and now I'm receiving a message error when I try to open the admin ECP page, Email flow, Rules.I get the message error: "Your request couldn't be completed. Please try again in a few minutes."

below is what I get on the file log:

Current user: 'mydomain.local/MyBusiness/Users/Admin'

Web service call 'https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)' failed with the following error:

System.Security.SecurityException: Request for principal permission failed.

at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()

at System.Security.Permissions.PrincipalPermission.Demand()

at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)

at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)

at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )

at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)

at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)

at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)

at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

The action that failed was:

Demand

The type of the first permission that failed was:

System.Security.Permissions.PrincipalPermission

The first permission that failed was:

<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

The demand was for:

<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

The assembly or AppDomain that failed was:

mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()

at System.Security.Permissions.PrincipalPermission.Demand()

at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)

at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)

at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )

at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)

at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)

at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)

at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

First Failed Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

Url: https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)

Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.GlobalCriminalCompliance, False],[Global.MultiTenancy, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration, True],[Eac.AllowRemoteOnboardingMovesOnly, False],[Eac.BulkPermissionAddRemove, True],[Eac.CmdletLogging, True],[Eac.CrossPremiseMigration, False],[Eac.DevicePolicyMgmtUI, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryPFSearch, False],[Eac.DiscoverySearchStats, False],[Eac.DlpFingerprint, False],[Eac.EACClientAccessRulesEnabled, False],[Eac.GeminiShell, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroups, False],[Eac.Office365DIcon, False],[Eac.OrgIdADSeverSettings, False],[Eac.RemoteDomain, False],[Eac.UCCAuditReports, False],[Eac.UCCPermissions, False],[Eac.UnifiedAuditPolicy, False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedPolicy, False],[Eac.UnlistedServices, False],], Flights:[], Constraints:[[LOC, EN-US],[MACHINE, EXCHANGESERVER],[MODE, ENTERPRISE],[PROCESS, W3WP],[USER, TECHSUPPORT@],[USERTYPE, BUSINESS],], IsGlobalSnapshot: False

flavio

I was going through message tracking, external user may not be receiving emails from us, and I ran into these two errors I had not seen before, Hard Direct Fail and No Suitable Shadow Servers.

the email in question is being forwarded from an AS400 through our Exchange 2013 through a relay connector, also we have two Exchange 2013 servers and a witness server to form a DAG group.

does the shadow server refer to the 2nd exchange in the DAG group?

I ran several status checks on the DAG group, and status appears to be ok.

Dear Team,

we are using Microsoft Exchange 2003 & 2010 Server for Emails, now we have both servers are connected, we want to raise new Single incident request for doing this activity, we want disconnect 2003 server from 2010 server so accordingly need support, we are ready to pay for this incident, 

pls do the needful,

Thanks & regards

Anteshwar Bhosale

Hello everyone,

I recovered the exchange 2013 C7 and now I'm receiving a message error when I try to open the admin ECP page, Mail flow, Rules.I get the message error: "Your request couldn't be completed. Please try again in a few minutes." If I try to create a new rule, I get an error message "access denied". However, I'm able to created a new transportule through powershell.

I'm accessing ECP from IE. All services are started and running.Im also accessing Exchange server with Domain\Administrator account and the administrator have the following group membership:

Domain Admins

Schema Admins

Enterprise Admins

Organization Management

below is what I get on the file log:

Current user: 'mydomain.local/MyBusiness/Users/Admin'

Web service call 'https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)' failed with the following error:

System.Security.SecurityException: Request for principal permission failed.

at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()

at System.Security.Permissions.PrincipalPermission.Demand()

at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)

at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)

at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )

at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)

at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)

at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)

at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

The action that failed was:

Demand

The type of the first permission that failed was:

System.Security.Permissions.PrincipalPermission

The first permission that failed was:

<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

The demand was for:

<IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

The assembly or AppDomain that failed was:

mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

at System.Security.Permissions.PrincipalPermission.ThrowSecurityException()

at System.Security.Permissions.PrincipalPermission.Demand()

at Microsoft.Exchange.Management.ControlPanel.WebServiceParameters.set_Item(String cmdletParameterName, Object value)

at Microsoft.Exchange.Management.ControlPanel.ResultSizeFilter.set_ResultSize(Int32 value)

at ReadTransportRuleFilterFromJson(XmlReaderDelegator , XmlObjectSerializerReadContextComplexJson , XmlDictionaryString , XmlDictionaryString[] )

at System.Runtime.Serialization.Json.JsonClassDataContract.ReadJsonValueCore(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.Json.JsonDataContract.ReadJsonValue(XmlReaderDelegator jsonReader, XmlObjectSerializerReadContextComplexJson context)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator reader, String name, String ns, Type declaredType, DataContract& dataContract)

at System.Runtime.Serialization.XmlObjectSerializerReadContext.InternalDeserialize(XmlReaderDelegator xmlReader, Type declaredType, DataContract dataContract, String name, String ns)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)

at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)

at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader, Boolean verifyObjectName)

at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.PartInfo.ReadObject(XmlDictionaryReader reader, XmlObjectSerializer serializer)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameterPart(XmlDictionaryReader reader, PartInfo part)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeParameters(XmlDictionaryReader reader, PartInfo[] parts, Object[] parameters, PartInfo returnInfo, Object& returnValue)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBodyCore(XmlDictionaryReader reader, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.DataContractJsonSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)

at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DemultiplexingDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.UriTemplateDispatchFormatter.DeserializeRequest(Message message, Object[] parameters)

at Microsoft.Exchange.Management.ControlPanel.DiagnosticsBehavior.SerializationPerformanceTracker.DeserializeRequest(Message message, Object[] parameters)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.DeserializeInputs(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

First Failed Demand: <IPermission mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"

version="1">

<Identity Authenticated="true"

Role="Get-TransportRule?ResultSize@R:Organization"/>

</IPermission>

Url: https://exchangeserver.mydomain.local:444/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.(https://remote.mydomain.com/ecp/RulesEditor/TransportRules.svc/GetList?msExchEcpCanary=p2Zp1y_1kESsrueBkDB6T1r0z46NLdII4Q_D6294gRCkKBixfp0OnWr9OfSQ9SO205BuS7NQnns.)

Flight info: Features:[[Global.DistributedKeyManagement, False],[Global.GlobalCriminalCompliance, False],[Global.MultiTenancy, False],[Global.WindowsLiveID, False],[Eac.AllowMailboxArchiveOnlyMigration, True],[Eac.AllowRemoteOnboardingMovesOnly, False],[Eac.BulkPermissionAddRemove, True],[Eac.CmdletLogging, True],[Eac.CrossPremiseMigration, False],[Eac.DevicePolicyMgmtUI, False],[Eac.DiscoveryDocIdHint, False],[Eac.DiscoveryPFSearch, False],[Eac.DiscoverySearchStats, False],[Eac.DlpFingerprint, False],[Eac.EACClientAccessRulesEnabled, False],[Eac.GeminiShell, False],[Eac.ManageMailboxAuditing, False],[Eac.ModernGroups, False],[Eac.Office365DIcon, False],[Eac.OrgIdADSeverSettings, False],[Eac.RemoteDomain, False],[Eac.UCCAuditReports, False],[Eac.UCCPermissions, False],[Eac.UnifiedAuditPolicy, False],[Eac.UnifiedComplianceCenter, False],[Eac.UnifiedPolicy, False],[Eac.UnlistedServices, False],], Flights:[], Constraints:[[LOC, EN-US],[MACHINE, EXCHANGESERVER],[MODE, ENTERPRISE],[PROCESS, W3WP],[USER, TECHSUPPORT@],[USERTYPE, BUSINESS],], IsGlobalSnapshot: False

flavio

Hello,

using AD Windows PKI I assigned a certificate EKU (1.3.6.1.5.5.7.3.4) to sign emails and get this withautoenrollment also to my CERT Store PSCERT:\CurrentUser\UserDS\ or the certificate could found via MMC / certificates in the store structur under "Active Directory User Object".
Signed messages (red icon) to send as S/MIME message using Outlook 2010 is not a problem.

Using PowerShell cmdlet Send-MailMessage to be sent company notification for a new passwordpolicy some days before pwd expired?! I use the cmdlet already successfully to filling HTML bodies with variables and send to individuals accounts.

Reduced simplified PS code:

#
$SMTPBodyHtmlTemplate = Get-Content "C:\PS\Template\HTMLBody.html" | Out-String
#
Function SendEmailNotification # /* SEND E-MAIL Notification to User */#
{
#
[string] $SMTPServer = "mail.domain.local"
#
$CurrentUser = "$env:username"
[string]$SMTPFrom = (Get-ADUser $CurrentUser -properties mail).mail
#
[string[]] $SMTPTo = $($Obj.EmailAddress)
#
[string]$SMTPSubject = "Notification!"
#
[String]$SMTPBodyHtml = $SMTPBodyHtmlTemplate.Replace("UserDisplayname","$($UserDisplayname)")
#
Send-MailMessage -From $SMTPFrom -To $SMTPTo -Subject $SMTPSubject -BodyAsHtml $SMTPBodyHtml -dno OnFailure -SmtpServer $SMTPServer -encoding ([System.Text.Encoding]::UTF8) -ErrorAction Continue
#
}
#

How can I use the PSDrive own CERT and using PowerShell cmdlet Send-MailMessageto send a signed message, without development experience?

Thanks in advance for cooperation.

Manfred Schüler