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

Exchange 2013 CU 18 - Routing based on Sender domain

$
0
0

We have an urgent requirement to route one of the domains in our accepted domain in our Exchange 2013 through EOP.

That is sender domain, for example, is xyz.com which is our internal accepted domain. All our employees whose email domain is xyz.com, their email needs to be routed through <g class="gr_ gr_208 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="208" id="208">EOP .</g>  Other domain users should follow the default path. 

In exchange 2013 CU 18 is it possible to have a connector based on Sender domain ???


ROBIN


Mail stuck in Edge Transport Server

$
0
0

I have setup a lab for exc 2013 and having some issues receiving mail from internet.

I can send to internet OK. I can send internally OK.

My MX records are setup properly

I configured an edge subscription as per Configure Edge subscription

When I send a mail from my gmail account it gets to the edge transport server and then stays there.

I assume its a DNS issue but cant figure out wehre. All firewalls are off and each box can ping the other.

Any help appreciated.


the edge server has 2 nics - 1 connected to my home lab 10.x.x.x., the other connected to my home network that goes through the ISP internet 192.x.x.x

the exchange box is in my home lab 10.x.x.x


Thanks - Joe.


Sending Mail to External INTRANET Domain

$
0
0

I have an on-premise setup consisting of two 2013 Exchange Servers in a clustered DAG.

Recently a sister organization has requested to be able to send mail to us from their mail server, and also have our users be able to email their users back to their mail server.

IMPORTANT - We are in an INTRANET configuration, with direct access between our sites and no INTERNET connectivity. Both sites have their own Domain and their own Mail Servers.

On our domain, our mail domain is the same as our domain name:

Domain name = mydomain.com

Example mailbox = user1@mydomain.com

For our sister domain:

Domain Name = theirdomain.com

Example mailbox = user1@weloveemail.com

I am attempting to set up a Send Connector on our side so that our users can email our sister organization, and the emails keep getting stuck in the queue: "A matching connector cannot be found to route the external recipient"

What I have done:

- Set up an Accepted Domain for "theirdomain.com"

- Set up a Send Connector for *.theirdomain.com

- Restarted Exchange services, as well as Restarted the servers completely

Additional Info - we have a conditional forwarder to our sister domain - "theirdomain.com". I can ping their mailserver mail.theirdomain.com just fine.

What I have also tried:

- Set up an Accepted Domain for "theirdomain.com"

- Set up a Send Connector for *.weloveemail.com

- Restarted Exchange services, as well as Restarted the servers completely

Any help/advice is greatly appreciated! I have looked up multiple articles online including Practical365, etc.

Home lab setup. Mail stuck in OWA client drafts. Exchange 2013

$
0
0

New lab setup with exchange 2013. I have setup edge synchonisation. I can receive email from the internet OK

When i try to send to internal/internet users the mail stays in the Drafts folder.

here is the screenshot from the send connector

"edgeSync - Default-First-NAme to Internet"


Appreciate any help. 

Thanks - Joe.


4.4.0 SMTPSEND.DNS.NoOutboundFrontendServer

$
0
0

I've stood up two new mailbox servers to replace my current pair. After migrating everyone to these new servers, all seems fine. My send connector is still configured with the old mailbox servers to proxy through the CAS. When I swap out the old servers for the new servers in the send connector, mail stops leaving the organization and the queue lists the error "4.4.0 SMTPSEND.DNS.NoOutboundFrontendServers". Sadly, Google isn't helping.

Does anyone have any pointers?

Your message wasn't delivered because of security policies -- Exchange 2013 server and its connect to O365

$
0
0

the group moderator doesn't received any emails for approval , if we doesn't use moderator everything is fine ,we get the replay is mention below . 

Delivery has failed to these recipients or distribution lists:

test@test.com Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.

Diagnostic information for administrators:

Generating server: ******.test.com

test@test.com #< #5.7.1 smtp;550 5.7.1 RESOLVER.RST.AuthRequired; authentication required> #SMTP#

Original message headers:

Received: from ******.test.com (10.**.**.***) by
******.test.com (10.**.**.***) with Microsoft SMTP Server (TLS)
 id 15.0.1367.3; Wed, 24 Oct 2018 14:38:24 +0800
Received: from TEST.LGH (10.**.**.***) by test-02.test.com
 (10.**.**.***) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via TEST
 Transport; Wed, 24 Oct 2018 14:38:24 +0800
Received: from *****.LGH (unknown [127.0.0.1])


SMTP Emails are not delivered to Users

$
0
0

Hello,

We are running a big problem. Some of the automatic emails from application are not reaching the user mailboxes. On the SMTP server  logs, we could see the logs but not passing through to the Hybrid server to reach Office365.

Can someone please help? Thank you

Best Regards,

Sharath Chandra Ayachitham 

"The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook"

$
0
0
I changed the delivery options on the exchange server to automatically forward the user's email to an external email address.  Whenever I do this, the user gets the "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" message and they are not able to receive any messages. Once the user restarts outlook, they are fine.  This happens every time I configure forwarding for a user via the delivery options on Microsoft Exchange.  Does anyone know why the users are getting "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" message whenever forwarding is configured for the user via the delivery options on Microsoft Exchange?

Prohibit sending e-mail from Internet through smtp without password

$
0
0

Dear all,

I have the following issue - anyone can send mail from any existing e-mail account in the organization over smtp without knowing the password of the account from anywhere in the world. For example this script works from anywhere:

Send-MailMessage –From administrator@myorganization.com –To administrator@myorganization.com –Subject “Test Email” –Body “Test E-mail (body)” -SmtpServer mysmtpserver.myorganization.com

How this can be prohibited? Our exchange server is 2013 with hybrid environment, migrated in O365 most of the accounts.

Exchange 2013 TransportRoles\Data\Temp filling up disk

$
0
0

I have a single multi-role Exchange 2013 server and it would appear that it's not properly maintaining the temp files for the transport service.  I still have all those folder locations at their default and the problem folder is c:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Temp

I never had a problem with this in Exchange 2007 but I am used to running a PowerShell script nightly to clean up the IIS log files.  Do I need to do something similar for this temp folder?  Is there a setting I can adjust so that Exchange will limit the size of this folder itself?  If I stop the transport service and delete the files here will I lose anything?

Any suggestions or insight would be greatly appreciated.


2010 to 2013 and Mail Flow Failure

$
0
0

Basically set up a New 2012 server, installed Enterprise Exchange 2013 and Migrated all Users into new Databases.

After restarting the Server, Transport Service would not start, removed two receive connectors.

ECP and OWA access work, but no mail flow and to be honest, though it was like 2010, Nope and now stuck.

The web or outlook client can connect but that's it, no mail flow

This is a new server, nothing added, just need to rebuild the communication fabric.

How can I phishing mail from external with internal email address?

$
0
0

User received phishing email from another internal user. but I checked email header, it is show sender mail server from outside.

How can I reject all email address with internal domain that send from outside?

Exchange 2013 Email Delivery Bounce

$
0
0

Dear all,

Current setup:

Exchange 2013 CAS - 2 units

Exchange 2013 Mailbox - 2 units

Issue: 

User frequently receive notification on Outlook for undeliverable email as below. Previously no issue like this happened:

============================================================

Remote Server returned '554 5.6.0 An unexpected error was encountered during submission of this mail. Error reference number = 18577986.'
Original message headers:
Received: from VMEXMB01.xxx.xxx.my ([fe80::88da:acf7:c7c:b5b0]) by
 VMEXMB01.xxx.xxx.my ([fe80::88da:acf7:c7c:b5b0%16]) with mapi id
 15.00.1395.000; Thu, 8 Nov 2018 17:35:06 +0800
MIME-Version: 1.0
Content-Type: text/plain
Date: Thu, 8 Nov 2018 17:35:06 +0800
X-MS-Exchange-Transport-FromEntityHeader: Hosted
Message-ID: <207c29faeb614e50b19c3f01b6a2eec2@VMEXMB01.xxx.xxx.my>

==================================================

Any clue for the issue?

Regards,

Azanne

Inter site mail routing of large attachment(s) to multiple recipients

$
0
0

Hopefully this is a really easy one for someone but I am struggling to find any reference to the answer to this...

If a user sends an email with a 10MB attachment to 10 recipients who are all homed on Exchange in a different site(s), does this require 100MB of bandwidth or 10MB? I know there is no single instance storage but will exchange send the attachment once or 10 times?

Thanks


**Please don't forget to mark as helpful or answer**

Tracking Spoofed Email

$
0
0

Having an issue resolving spoofing of emails from our Org using Exchange 2013

We use Trend Micro Hosted Email Security, but this seems to bypass that and the SPF record.

Here are some example headers from a received email seemingly from an Internal address to that very same address, yet it seems that it has originated from an IP in Sudan? 

I have replaced our server name, server IP and email address with generic names. 

Received: from SERVER.DOMAIN.local (SERVER IP) by SERVER.DOMAIN.local
 (SERVER IP) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Mailbox
 Transport; Sun, 11 Nov 2018 14:26:01 +0000
Received: from SERVER.DOMAIN.local (SERVER IP) by SERVER.DOMAIN.local
 (SERVER IP) with Microsoft SMTP Server (TLS) id 15.0.847.32; Sun, 11 Nov
 2018 14:26:01 +0000
Received: from [102.181.140.237] (102.181.140.237) by SERVER.DOMAIN.local
 (SERVER IP) with Microsoft SMTP Server id 15.0.847.32 via Frontend
 Transport; Sun, 11 Nov 2018 14:26:00 +0000
From: LOCAL USER <LOCAL.USER@DOMAIN.co.uk>
To: LOCAL USER <LOCAL.USER@DOMAIN.co.uk>
Subject: Account Issue. Changed password.
Thread-Topic: Account Issue. Changed password.
Thread-Index: AQHUecp4+RHqe1LAsk6VrVM5UkpeuQ==
Date: Sun, 11 Nov 2018 15:51:26 +0000
Message-ID: <751565660.201811111739@DOMAIN.co.uk>
Content-Language: en-GB
X-MS-Exchange-Organization-AuthSource: SERVER.DOMAIN.local
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tm-as-user-blocked-sender: No
x-tm-as-user-approved-sender: No
x-tm-as-result: No--17.840300-5.000000-31
x-tm-as-product-ver: SMEX-11.6.0.1051-8.200.1013-24216.004
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

The message seemingly bypasses the hosted Trend filter as the message cannot be traced in the logs, i assume as it is treated as internal. yet i don't see the email when running a mailbox search in EAC>Mail Flow>delivery reports.

If i run  "Get-MessageTrackingLog -MessageID....." using the Management Shell i see the email and using the "Select-Recipients,Sender,ConnectorID" i can see the To and  From addresses are the local email address and connector used was the default connector for the HubTransport role.

I am looking into implementing DKIM and Dmarc records but i fear it would not stop something like this. 

Could anyone offer any insight or assist me in working out how they have done this?

Many thanks



Maintaining mail flow without Contacts or Mail-enabled Users

$
0
0

The Setup

Our company was acquired by a larger organization and we have migrated all of our user mailboxes to their Office365 tenant and in the process changed primary SMTP to their domain. We have an on-premises Exchange system, which is currently used to handle some shared mailbox and SMTP relay for applications in our data center under the former accepted domains. User mail sent to the former accepted domains are routed to the O365 destination mailbox via contacts or Mail-enabled Users. The on-premises Exchange server is version 2010, which is out of support and my organization would like to turn it off.

Going Forward

I am tasked with turning off the on-premises Exchange system. I originally planned to do this after the former domains are configured to point to Office365 and mail flow for the former domains no longer goes through my data center or the on-premises Exchange server. However, there is some need to keep the former domains on-premises, to be used for outgoing SMTP only. The organization is averse to purchasing an updated Exchange License to handle such a task.

The Ask

Is there a way to direct mail sent to one of the former domains to the new destination mailboxes WITHOUT Exchange to host the contacts and MEUs that translate the final recipient address? I have considered a Linux mail server or something to that effect, but I was hoping someone out there had a better idea.

Configuring Cross forest Free Busy (Availability)

$
0
0

Hi, 

I am configuring cross forest co-existence between two Exchange Orgs and I would like to clarify the purpose of a particular setting in Exchange. 

The environment I would like to allow OrgWide Free Busy with my Exchange org is un-trusted from a domain perspective. What I would like to understand is the setting Set-AvailabilityConfig -OrgWideAccount <AccountName>

When I add this account to my Exchange Org, will this allow the other exchange or to see my users availability data (after they have configured a new Availability Address Space (using the -Credential parameter)? 

Could populating this value on my Exchange Org have any impact on other organizations that already have availability sharing setup with my Exchange Org (note the property is currently $Null on our Exchange, therefore I am assuming other organizations are referencing availability using the trusted forest method whereby Exchange servers are given a permission within the environment (cmdlet below))?

Get-MailboxServer | Add-ADPermission -Accessrights Extendedright -Extendedrights "ms-Exch-EPI-Token-Serialization" -User "<Remote Forest Domain>\Exchange servers"

Thanks, 

Mike.

Cross forest mail routing (Basic authentication over TLS)

$
0
0

Hi, 

I am in the process of implementing Cross-Forest routing between two Exchange Organizations (Exchange 2010 and Exchange 2013). 

When I configure the send connector on either side to authentication only after establishing TLS I am getting errors in the SMTP logs stating "cannot validate certificate". I am assuming that this is because it is making the connection on my Default Receive Connector and it cannot validate the certificate because Exchange is configure to use a self signed certificate for TLS (SMTP) by default. 

My questions are: 

  • Is there any way to get Exchange to bypass the validation and establish TLS without verifying the cert? (I believe with opportunistic TLS this occurs and the self signed certificate is used to encrypt the channel).
  • A)If I cannot use the self signed certificate for Basic Authentication over TLS, can I create another receive connector that will allow basic authentication over TLS? If so, I assume I will assign an FQDN to the connector and match the subject name on the TLS Cert to the FQDN property? 
  • B) If I opt to go with a new receive connector and a CA signed certificate for TLS, how do I assign that particular certificate to the new receive connector. As far as I can tell Exchange 2010 does not have this property that can be set on the receive connector to use a specific TLS certificate. One newer versions of Exchange there is a -TlsCertificateName parameter on the Set-ReceiveConnector cmdlet, however this is not available on Exchange 2010.

Thanks in advance. 

Mike.

Getting 550 5.7.1 Unable to relay when sending from internet to my exchange 2013

$
0
0

I have an edge transport server and the exchange serve setup in my lab.

I have configured a subscription OK and its synching fine.

I can send mail out OK, but get therror when I try to send from extenal to internal.

I used to have this working and have no idea whats happened.

The send connectors are the 2 created when you run the command to cerate subscription. they look fine.

Any help appreciated.

Joe.


Thanks - Joe.

External e-mail disclaimer transport rule is being applied to SMTP relay messages from application servers within network

$
0
0

Hi,

I recently implemented a rule to add a disclaimer to emails that are received from outside of our network.  The rule is fairly simple, in it's current state it basically says If an email is sent to either of these 2 users and it came from outside of the network, prepend this disclaimer to it.  The rule works, but, I've noticed that it's adding the disclaimer to email messages from application servers within the network that are using the SMTP relay service on the exchange servers.  My guess is that this is happening because the SMTP relay is set for Anonymous and therefore exchange thinks these messages are originating from outside of the network and therefore applying the disclaimer rule.  In an attempt to get around this, I created an exclusion that says "Except if the message sender ip addresses belong to one of these ranges" and then I've added our network ranges (I've tried adding them in CIDR format as well as listing the starting ip address and the last ip address in the subnet) but it's still applying the rule to these messages.  Any suggestions?  Here is the exchange powershell output of the rule I have created.

RunspaceId                                   : c4d9efe7-7a48-441a-a138-814a58a20adf
Priority                                     : 0
DlpPolicy                                    :
DlpPolicyId                                  : 00000000-0000-0000-0000-000000000000
Comments                                     :

ManuallyModified                             : False
ActivationDate                               :
ExpiryDate                                   :
Description                                  : If the message:
                                                   Is sent to 'user@domain.org' or 'user@domain.org'
                                                   and Is received from 'Outside the organization'
                                               Take the following actions:
                                                   Prepend the message with the disclaimer '<p><span style="color:
                                               #ff0000; background-color: #000000;"><strong>[ WARNING This message
                                               originated from outside of the Company, proceed with
                                               caution.&nbsp; Contact the NOC for further assistance.
                                               ]</strong></span></p>'. If the disclaimer can't be applied, take no
                                               action.
                                               Except if the message:
                                                   sender ip addresses belong to one of these ranges:
                                               '172.17.0.0-172.17.255.255' or '172.18.0.0-172.18.255.255' or
                                               '172.16.0.0-172.16.255.255'

RuleVersion                                  : 15.0.2.0
Conditions                                   : {SentTo, FromScope}
Exceptions                                   : {SenderIpRanges}
Actions                                      : {ApplyHtmlDisclaimer}
State                                        : Enabled
Mode                                         : Enforce
RuleErrorAction                              : Ignore
SenderAddressLocation                        : Header
RuleSubType                                  : None
UseLegacyRegex                               : False
From                                         :
FromMemberOf                                 :
FromScope                                    : NotInOrganization
SentTo                                       : {User@domain.org, User@domain.org}
SentToMemberOf                               :
SentToScope                                  :
BetweenMemberOf1                             :
BetweenMemberOf2                             :
ManagerAddresses                             :
ManagerForEvaluatedUser                      :
SenderManagementRelationship                 :
ADComparisonAttribute                        :
ADComparisonOperator                         :
SenderADAttributeContainsWords               :
SenderADAttributeMatchesPatterns             :
RecipientADAttributeContainsWords            :
RecipientADAttributeMatchesPatterns          :
AnyOfToHeader                                :
AnyOfToHeaderMemberOf                        :
AnyOfCcHeader                                :
AnyOfCcHeaderMemberOf                        :
AnyOfToCcHeader                              :
AnyOfToCcHeaderMemberOf                      :
HasClassification                            :
HasNoClassification                          : False
SubjectContainsWords                         :
SubjectOrBodyContainsWords                   :
HeaderContainsMessageHeader                  :
HeaderContainsWords                          :
FromAddressContainsWords                     :
SenderDomainIs                               :
RecipientDomainIs                            :
SubjectMatchesPatterns                       :
SubjectOrBodyMatchesPatterns                 :
HeaderMatchesMessageHeader                   :
HeaderMatchesPatterns                        :
FromAddressMatchesPatterns                   :
AttachmentNameMatchesPatterns                :
AttachmentExtensionMatchesWords              :
AttachmentPropertyContainsWords              :
ContentCharacterSetContainsWords             :
HasSenderOverride                            : False
MessageContainsDataClassifications           :
SenderIpRanges                               :
SCLOver                                      :
AttachmentSizeOver                           :
MessageSizeOver                              :
WithImportance                               :
MessageTypeMatches                           :
RecipientAddressContainsWords                :
RecipientAddressMatchesPatterns              :
SenderInRecipientList                        :
RecipientInSenderList                        :
AttachmentContainsWords                      :
AttachmentMatchesPatterns                    :
AttachmentIsUnsupported                      : False
AttachmentProcessingLimitExceeded            : False
AttachmentHasExecutableContent               : False
AttachmentIsPasswordProtected                : False
AnyOfRecipientAddressContainsWords           :
AnyOfRecipientAddressMatchesPatterns         :
ExceptIfFrom                                 :
ExceptIfFromMemberOf                         :
ExceptIfFromScope                            :
ExceptIfSentTo                               :
ExceptIfSentToMemberOf                       :
ExceptIfSentToScope                          :
ExceptIfBetweenMemberOf1                     :
ExceptIfBetweenMemberOf2                     :
ExceptIfManagerAddresses                     :
ExceptIfManagerForEvaluatedUser              :
ExceptIfSenderManagementRelationship         :
ExceptIfADComparisonAttribute                :
ExceptIfADComparisonOperator                 :
ExceptIfSenderADAttributeContainsWords       :
ExceptIfSenderADAttributeMatchesPatterns     :
ExceptIfRecipientADAttributeContainsWords    :
ExceptIfRecipientADAttributeMatchesPatterns  :
ExceptIfAnyOfToHeader                        :
ExceptIfAnyOfToHeaderMemberOf                :
ExceptIfAnyOfCcHeader                        :
ExceptIfAnyOfCcHeaderMemberOf                :
ExceptIfAnyOfToCcHeader                      :
ExceptIfAnyOfToCcHeaderMemberOf              :
ExceptIfHasClassification                    :
ExceptIfHasNoClassification                  : False
ExceptIfSubjectContainsWords                 :
ExceptIfSubjectOrBodyContainsWords           :
ExceptIfHeaderContainsMessageHeader          :
ExceptIfHeaderContainsWords                  :
ExceptIfFromAddressContainsWords             :
ExceptIfSenderDomainIs                       :
ExceptIfRecipientDomainIs                    :
ExceptIfSubjectMatchesPatterns               :
ExceptIfSubjectOrBodyMatchesPatterns         :
ExceptIfHeaderMatchesMessageHeader           :
ExceptIfHeaderMatchesPatterns                :
ExceptIfFromAddressMatchesPatterns           :
ExceptIfAttachmentNameMatchesPatterns        :
ExceptIfAttachmentExtensionMatchesWords      :
ExceptIfAttachmentPropertyContainsWords      :
ExceptIfContentCharacterSetContainsWords     :
ExceptIfSCLOver                              :
ExceptIfAttachmentSizeOver                   :
ExceptIfMessageSizeOver                      :
ExceptIfWithImportance                       :
ExceptIfMessageTypeMatches                   :
ExceptIfRecipientAddressContainsWords        :
ExceptIfRecipientAddressMatchesPatterns      :
ExceptIfSenderInRecipientList                :
ExceptIfRecipientInSenderList                :
ExceptIfAttachmentContainsWords              :
ExceptIfAttachmentMatchesPatterns            :
ExceptIfAttachmentIsUnsupported              : False
ExceptIfAttachmentProcessingLimitExceeded    : False
ExceptIfAttachmentHasExecutableContent       : False
ExceptIfAttachmentIsPasswordProtected        : False
ExceptIfAnyOfRecipientAddressContainsWords   :
ExceptIfAnyOfRecipientAddressMatchesPatterns :
ExceptIfHasSenderOverride                    : False
ExceptIfMessageContainsDataClassifications   :
ExceptIfSenderIpRanges                       : {172.17.0.0-172.17.255.255, 172.18.0.0-172.18.255.255,
                                               172.16.0.0-172.16.255.255}
PrependSubject                               :
SetAuditSeverity                             :
ApplyClassification                          :
ApplyHtmlDisclaimerLocation                  : Prepend
ApplyHtmlDisclaimerText                      : <p><span style="color: #ff0000; background-color: #000000;"><strong>[
                                               WARNING This message originated from outside of the Company,
                                               proceed with caution.&nbsp; Contact the NOC for further assistance.
                                               ]</strong></span></p>
ApplyHtmlDisclaimerFallbackAction            : Ignore
ApplyRightsProtectionTemplate                :
SetSCL                                       :
SetHeaderName                                :
SetHeaderValue                               :
RemoveHeader                                 :
AddToRecipients                              :
CopyTo                                       :
BlindCopyTo                                  :
AddManagerAsRecipientType                    :
ModerateMessageByUser                        :
ModerateMessageByManager                     : False
RedirectMessageTo                            :
RejectMessageEnhancedStatusCode              :
RejectMessageReasonText                      :
DeleteMessage                                : False
Disconnect                                   : False
Quarantine                                   : False
SmtpRejectMessageRejectText                  :
SmtpRejectMessageRejectStatusCode            :
LogEventText                                 :
StopRuleProcessing                           : False
SenderNotificationType                       :
GenerateIncidentReport                       :
IncidentReportOriginalMail                   :
IncidentReportContent                        :
RouteMessageOutboundConnector                :
RouteMessageOutboundRequireTls               : False
ApplyOME                                     : False
RemoveOME                                    : False
GenerateNotification                         :
Identity                                     : External E-mail Notification
DistinguishedName                            : CN=External E-mail
                                               Notification,CN=TransportVersioned,CN=Rules,CN=Transport
                                               Settings,CN=Organization,CN=Microsoft
                                               Exchange,CN=Services,CN=Configuration,DC=domain,DC=org
Guid                                         : 2e4fcd6e-4b48-485e-9c70-b7f7b087e740
ImmutableId                                  : 2e4fcd6e-4b48-485e-9c70-b7f7b087e740
OrganizationId                               :
Name                                         : External E-mail Notification
IsValid                                      : True
WhenChanged                                  : 11/20/2018 3:36:20 PM
ExchangeVersion                              : 0.1 (8.0.535.0)
ObjectState                                  : Unchanged


I'm not even supposed to be here today.

Viewing all 4249 articles
Browse latest View live


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