Is there an Exchange 2013 DoD/Federal Message Clean/Spill Procedure?

I have seen DoD/Federal procedures to clean a message from early versions of Exchange (i.e. leakage/spill), but these procedures would not work for Exchange 2013.
I know that in the past Microsoft has worked with DISA & NSA to develop a message clean procedure for older versions of Exchange.
Is there a published procedure or best practice to clean a message from Exchange 2013 that meets DoD/Federal standards?
Thanks
Tom
Thomas Talley

Hello,
At present, there is no a published DoD/Federal procedure to clean a message from Exchange 2013. If there is any information about this, related technet article and exchange team blog will be published.
If you want to delete messages from a mailbox, you can use Search-Mailbox cmdlet with the DeleteContent switch to search and delete messages.
If you want to remove messages from mail queues, you can use Remove-Message cmdlet to delete a message from a queue on a Mailbox server or an Edge Transport server.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Similar Messages

Exchange 2013 Non Deliverable Messages do not show correct information

I tried looking around for a solution for this but have been unable to.
We have a new (1 month old) single-server installation of Exchange 2013 CU5, running on server 2012. It's in coexistence with an Exchange 2007 box. All users, groups, and everything have been migrated, we actually just shut down 2007 today. However, Exchange
2013 never seems to give accurate or helpful NDRs.
When someone sends an email to, let's say, a user who has left the company, so their mailbox is gone, the user who sent the email will receive an NDR. However, the NDR will not tell you the user who the email failed to. It shows the sender's account and
says "command not allowed". This happens only to internal recipients. When sending to an external domain, we receive the NDR from the other domain with the explanation that the user does not exist or whatever. But within our domain, we never get
a "helpful" NDR. It's just "command not allowed" and the email doesn't get to ANY of the recipients that it was sent to. Any ideas or help would be greatly appreciated!
Delivery has failed to these recipients or groups:
[email protected] Your message wasn't delivered due to a permission or security issue.
It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
Diagnostic information for administrators:
Generating server: mailserver.ourdomain
[email protected] Remote Server returned
'550 5.7.1 Command not allowed'
Original message headers:
Received: from mailserver.ourdomain ([removed]) by mailserver.ourdomain ([removed]) with mapi id 15.00.0913.011; Thu, 17 Jul 2014 10:18:03 -0500 MIME-Version: 1.0 Content-Type:
text/plain Date: Thu, 17 Jul 2014 10:18:03 -0500 Message-ID: <removed > Subject: RE: ASAP

I just tested, and yes, it happens when sending to any invalid SMTP address within our domain. I also tried sending an email to a non-existant user in our domain from my gmail account and received the same message with "command not allowed". We
are running GFI MailEssentials for spam filtering (on the same server), and I also have content filtering and recipient filtering enabled on exchange. For GFI, we exported the config we had for GFI on our 2007 server and imported it into the GFI installation
on our Exchange 2013 server. Should I try disabling content and/or recipient filtering on Exchange? Should I try shutting off GFI and send a test email?
I appreciate your time and effort on this!!
I did a message trace on the test email I sent to a non-existent SMTP address on our domain and this is what I got... Not sure how helpful this is :(
Sorry, my account isn't "verified" yet so I can't post pictures. I put the output up here for now. http://andyslights.com/trace.jpg

Exchange 2013 SP1: messages still stuck in Drafts folder

Hello!
The second question on Exchange 2013SP1 that I asked when I was working with Exchange 2013:
New lab setup: a Windows 2012R2 DC (server1) + Exchange 2013SP1 (server2). Exchange 2013SP1 installation completed successfully. I created three mailboxes: [email protected], [email protected], [email protected]
Now when I'm trying to send a message (from user1 to user, for example) it gets stuck in the Drafts folder.
I manually set up my DNS server in ECP:
as described here: http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages - but the problem persists.
And this problem
"On every single installation / that I’ve done of Exch 2013 in multiple labs, when set as a single mailbox server, messages have never been able to leave the “drafts” folder. Not a single instance where it worked correctly. Messages
leaving a mailbox, destined to the exact same server do not route, let alone use any send-connector to leave the organization.
Now, take it to the next step, and install a second mailbox server. The very second that services finish installing, and AD replication (if using multiple sites) settles down, mail-flow on the first server starts working absolutely flawlessly. Whatever
changes are done to AD from the second mailbox server being installed in regards to mailflow, it completely resolves the issues of the first server holding onto the messages."
...is exactly the same as mine...but in Exchange 2013 SP1 ( Messages leaving a mailbox, destined to the exact same server do not route).
Can anybody from MS tell me if it's a bug or by design??? I've NEVER had an Exchange installation without this issue...
Thank you in advance,
Michael

Hi,
I have never come across such a situation in my labs(all roles install in a single server), and there is no Microsoft documentation mentioned this issue.
In addition, Microsoft does not oppose the Exchange installed on a single server(although not recommend).
I recommend you check if all the exchange services are running, and try to restart Exchange Mailbox Transport Submission & Exchange Mailbox Assistants services.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 - Quota notifications problem

Hello,
First of all I want to express mild disappointment with the way quota notification alerts are documented on Technet for Exchange 2013. The only reference I could find is that QuotaNotificationSchedule parameter of the Set-MailboxDatabase cmdlet no longer
does anything: "This parameter has been deprecated in Exchange 2013 and it no longer does anything.".
The only other reference I could find is this forum post:
http://social.technet.microsoft.com/Forums/exchange/en-US/f30bb2ca-91ab-4e69-a8b6-720e6a8a5b83/exchange-2013-quota-notification-message-not-sent-during-schedule?forum=exchangesvrgeneral
where it says: "Quota messages are generated once the user log in to mailbox in exchange 2013."
However, Microsoft Press published a book in 2013 "Inside Out: Microsoft Exchange Server 2013: Mailbox and High Availability" where QuotaNotificationSchedule parameter is being referenced as a working parameter which controls when Quota notification
are being sent.
My experience says that the forum post is correct.
Now onto the problem.
While our customer was still on Exchange 2010 they were the victims of this issue:
http://support.microsoft.com/kb/2480474/en-us which could easily be fixed with
CheckWarningQuota registry key.
Now we have migrated those mailboxes to Exchange 2013 and again, users are not receiving quota notification e-mails. Only a few users receive quota notifications e-mails and those are users that got their mailbox created on the new Exchange 2013 system.
Migrated users do not receive notifications. We have tried CheckWarningQuota on Exchange 2013 but it does nothing. Our theory is that mailbox flag introduced in Exchange 2010 SP1 is migrated with the mailboxes to Exchange 2013 and is the
reason why we are not receiving quota notifications again.
I appreciate thoughts and comments.
Regards,
Dinko

CU8 addresses this issue, however, only for mailboxes not yet moved to 2013: https://support.microsoft.com/en-us/kb/303695
Mailboxes already moved will have to be manually fixed. The issue is they are missing their lcid (location ID). For whatever reason, the attribute does not make it across from 2010 to 2013. However, if you move the mailbox again to another 2013 database,
it fills in the lcid automatically. That is one workaround, but not necessarily a good one for people who have migrated a ton of their users already. So what do you do?
In the KB article, it shows you how to identify the users who are missing their LCID by doing the following in the exchange management shell:
#first load in the ManagedStoreDiagnosticFunctions, you will need this for the get-storequery cmdlet to work.
. .\'C:\Program Files\Microsoft\Exchange Server\V15\Scripts\ManagedStoreDiagnosticFunctions.ps1'
#then generate the list of all mailboxes with an LCID of 0.
$mbxs = get-mailbox –resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
$mbxsq = $mbxs | %{Get-StoreQuery -Database $_.database -query "select * from Mailbox where Mailboxguid = '$($_.ExchangeGuid)'"}
$mbxsq | ? {$_.lcid -eq 0} |fl displayname, mailboxguid, lcid
You can modify the script to dump the list to a text file if you need to.
Now, to address this, I simply populated the lcid for all my mailboxes. All of mine were en-US or lcid 1033, so it was easy to set them all at once. I just grabbed all Exchange 2013 mailboxes and applied the language (en-US) and DateFormat (MM/dd/yyyy) to
them (replace DOMAIN with your domain name) which in turn sets the lcid to 1033:
$mailboxes = get-mailbox -resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
($mailboxes).SamAccountName| %{set-MailboxRegionalConfiguration "DOMAIN\$_" -Language en-us -DateFormat MM/dd/yyyy} | FT -a
Incidentally, if you have already migrated all of your 2010 mailboxes, and you are on at least Exchange 2013 CU6, that script will resolve the issue whether you apply CU8 or not. CU8 fixes it for any other mailboxes that have not yet been migrated to 2013.
Hopefully this help you out.
Chris Allen
Microsoft Support Escalation Engineer

Exchange 2013 Server ECP Not Loading

Running Exchange 2013 (with all roles installed). I tried going to the ECP via https://servername.domain.com/ecp/
It keeps loading on and on forever (in a loop, never fully loads the page). Any help?
Running Windows Server 2012 DataCenter RTM with Exchange 2013
Thanks!

Hi,
Before we can go further, I'd like to confirm the following information and recommen the troubleshooting:
1. Is there only Exchange 2013 server in your environment? If there is other Exchange server, the proper URL is as following:https://CASServerFQDN/ecp?ExchClientVer=15
2. Please try to access the ECP URL with your CAS server IP address.
3. Check if there is any error about ECP in your IIS log.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Get error messages for those procedures in some system tables

Hi expert,
when I ran a procedure by schedule or on the front end. is there any approach to get error messages for those procedures in some system tables?
Many Thanks,

>
when I ran a procedure by schedule or on the front end. is there any approach to get error messages for those procedures in some system tables?
>
No - there is no system log table.
You need to create your own logging package and log table and modify your procedure code to call your own logging procedures to log into your own log table.
The procedures in the log package would typically be defined with PRAGMA AUTONOMOUS_TRANSACTION so that the exceptions get logged even if your procedure performs a ROLLBACK.
See AUTONOMOUS_TRANSACTION in the PL/SQL Language Reference
http://docs.oracle.com/cd/B28359_01/appdev.111/b28370/autotransaction_pragma.htm
Here is an Oracle-Base article that shows how to use the pragma to perform logging.
http://www.oracle-base.com/articles/misc/autonomous-transactions.php

Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%).
The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
configured threshold.”
There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20).
From what I can tell, all of the IP addresses are from Taiwan.
The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014).
From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening.
The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
The Error reads:
The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
Recent changes to the system:
About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

Hi,
Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 CAS-MBX recipient validation rejects entire message if any of recipients are invalid

Hi,
How can I enable recipient validation work in this design:
2 Exchange 2013 servers with CAS and MAILBOX roles both, DAG and Hardware Load balancer for HTTP and SMTP traffic.
From Exchange documentation:
http://technet.microsoft.com/en-us/library/bb125187%28v=exchg.150%29.aspx
Although the Recipient Filter agent is available on Mailbox servers, you shouldn't configure it. When recipient filtering on a Mailbox server detects one invalid or blocked recipient in a message that contains other valid recipients, the message is rejected.
If you install the anti-spam agents on a Mailbox server, the Recipient Filter agent is enabled by default. However, it isn't configured to block any recipients. For more information, see
Enable Anti-Spam Functionality on Mailbox Servers.
If You have a setup like this:
Install antispam agents:
Identity Enabled Priority
Transport Rule Agent True 1
Malware Agent True 2
Text Messaging Routing Agent True 3
Text Messaging Delivery Agent True 4
Content Filter Agent True 5
Sender Id Agent True 6
Sender Filter Agent True 7
Recipient Filter Agent True 8
Protocol Analysis Agent True 9
Have Recipient validation enabled:
Name Enabled RecipientValidationEnabled---- ------- --------------------------RecipientFilterConfig True True
Have AcceptedDomain AddressBook enabled:
DomainName DomainType AddressBookEnabled
contoso.com Authoritative True
Then You have a situation, where a single invalid recipient on an incoming email message would reject the entire message! I guess this is because the recipient filtering happens on the mailbox server.
So .. HOW? Is it possible without Edge servers? Have I missed something?
I hope this feature isn't "missing by design", because it will be very difficult to explain to the client, that such an expensive product cannot do what any mail server can - reject unknown recipients before taking E-Mail data. There are a lot
of issues with this feature missing (possible DDOS with max attachments, or spoofed sender e-mail address that is a spamtrap, so NDR from Exchange would get You to SBL, etc.).
Sincerely,
Vince

Hello Vince,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

#550 4.4.7 QUEUE.Expired; message expired ## With LastError "A storage transient failure has occurred during content conversion." In submission Queue. (Exchange 2013)

Greetings,
We seem to be having a problem with some users who are attempting to send e-mails from within the organisation to an external domain. Not all users are affected, and not all outgoing e-mails have this issue.
Some e-mails get stuck in the submission queue. This is the error message in Last Error : "A storage transient failure has occurred during content conversion."
Days later, the internal user who send the message gets a #550 4.4.7 QUEUE.Expired; message expired ## NDR.
We did have some initial configuration issues, but these were fixed more than a week ago :
- The external FQDN during EHLO was set to the wrong address, now pointing to the correct one.
- SPF record was updated with new IP adress.
Here is some additional information on the issue :
- Not on any blacklists - checked using dnsbl.info
- Telnet to remote servers works from exchange server, connections are accepted and can send mail.
- Outbound SMTP test ran using Microsoft Remote Connectivity Analyser : Passed with both External (Static) and Smarthost IP.
- This seems to happen only with emails that have an attachment and that are transfered, but only for the affected users.
- If content from these e-mails is manually copied over to a new email, email is sent to destination without problem.
Configuration information :
- Exchange 2013 running on Windows 2012 Datacenter with all latest updates.
- Outgoing e-mail is sent via smarthost. Only one outbound transport rule is active.
- Using internal DNS server.
- There is only one mailbox database.
Thank you for taking the time to read this!

On Wed, 16 Jan 2013 15:31:14 +0000, Ipigi wrote:
>Sorry, I often get some terms mixed up when I explain things as our users use the French version of outlook.
>
>E-mails are not transferred, but forwarded manually from their outlook. Message format in outlook is set to HTML and not Rich Text when they foward the e-mail.
Do they forward the message as an attachment?
>When forwarded internally, this is in the internet headers :
>
>Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary
Within your organization I'm prety sure that messages will use TNEF.
What does the message contain at the external recipient's side?
>It really seems to me that Exchange is not converting RTF to Plain Text. The first link you provided states in it's final paragraph that Exchange should be doing this conversion.
If you can, try creating a mail-enabed Contact for one of the external
recipients and set the message format on that.
>If I disabled TNEF as that link suggests, offending messages will get stuck in the submission queue again.
>
>I thank you for your help so far. This is not an issue I've had with any previous installations/migrations of Exchange that I have done.
>
>Please let me know if you need any additional information.
Have you tried UNsetting TNEF on the remote domain?
Set-RemoteDomain Default -TNEFEnabled $null
That should leave it up to the client to determine the format. It's
probably not what you're after, but see it makes a difference in the
format.
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

How to modify Exchange 2013 TXT(SMS) notifications to not include the subject line or any of the message body of emails

We have a group of users who are not permitted to download/save any emails they receive onto public or personal devices, they are only allowed to log in manually and view their mail through OWA (I realize there are ways to use OWA to download mail, however
the users are explicitly forbidden from doing this, and any countermeasures that can be put in place, are/will be).
With our new Exchange 2013 server, it seems it has the built in capability to send TXT(SMS) notifications instantly when a user receives mail. We would like to allow our users to utilize this feature, however currently, the notification includes not
only the sender of the email, but also the subject line and part of the message body. As it stands, we can't have this as part of the email would then be saved on their device.
I am wondering if there is a way to modify Exchange 2013 to not include the subject or message body, so that our users could at least get an instant notification 1-that they have a new email and 2-who it's from?
Any information would be appreciated, thanks!

We can configure SMS Text Message Notification for various situation like Calendar notifications, Voice mail notifications, Email notifications if your user's Mailbox hosted in Exchange Server 2013
To set up your phone to receive text messages when you want to have Calendar notifications, Voice mail notifications, Email notifications use the steps as follows
Note: Text message fees are applicable and it will appear on your phone bill.
Login to Outlook Web App, click Options > See All Options > Phone > Voice Mail tab.
In the Notifications section, choose one of the following options:
Calendar notifications...
Voice mail notifications...
Email notifications using an Inbox rule...
Turn On Notification
First step is to turn on the notification of text messaging. Click Turn on Notifications
Select Setup Notification: Need to select your operator,
It will request to provide your Mobile Operator.
Note: As of now Exchange Server 2013 supports only the below list of operators.
Locale: United State
Mobile Operator: AT & T, Sprint PCS, T-Mobile, Verizon Wireless
Locale: Canada,
Mobile Operator:Bell Telus Mobility
Locale: Romania
Mobile Operator:Orange Romania
Provide your telephone number. It will send you the passcode on your mobile number.
Type the passcode for confirmation
Calendar Notifications:
On Selecting Calendar Notification: Select the option based upon your requirement.
Email Notification Using Inbox Rule:
Similarly for the text messaging for the email notification, select the option based upon your requirement and setup them up
Exchange Queries

Exchange 2013 federation

Hi guys,
Im strugling with the following scenario:
We try to setup Exchange federation between Exchange 2010 sp2 and Exchange 2013. Everything is setup as described on Technet.
The problem I'm having is the following:
WHen i run test-organizationrelationship i get this.
RunspaceId : 09496e7f-2a7c-4e3a-b15d-0c8d6a1a867b
Identity    :
Id          : ApplicationUrisDiffer
Status      : Error
Description : The TargetApplicationUri of the remote organization doesn't match the local ApplicationUri of the
              Federation Trust object. The remote URI value is
http://fydibohf25spdlt.aldum.co.za/. The local URI
              value is FYDIBOHF25SPDLT.aldum.co.za.
IsValid     : True
ObjectState : New
RunspaceId : 09496e7f-2a7c-4e3a-b15d-0c8d6a1a867b
Identity    :
Id          : VerificationOfRemoteOrganizationRelationshipFailed
Status      : Error
Description : There were errors while verifying the remote organization relationship Aldum.
IsValid     : True
ObjectState : New
For the life of me the application uri on Exchange 2010 is FYDIBOHF25SPDLT.aldum.co.za
Here is the proof:
RunspaceId            : e58ad1c2-2910-42c7-a624-748dd0ffbb57
DomainNames           : {aldum.co.za}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : False
DeliveryReportEnabled : False
MailTipsAccessEnabled : False
MailTipsAccessLevel   : None
MailTipsAccessScope   :
TargetApplicationUri : FYDIBOHF25SPDLT.aldum.co.za
TargetSharingEpr      :
TargetOwaURL          :
TargetAutodiscoverEpr :
https://autodiscover.aldum.co.za/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled : False
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : Aldum
DistinguishedName     : CN=Aldum,CN=Federation,CN=Onesys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onesys,D
                        C=local
Identity              : Aldum
Guid                  : 7e806cf3-69d3-40ca-bd29-4ebbecb6e2f9
ObjectCategory        : onesys.local/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 2013/05/16 12:45:12 PM
WhenCreated           : 2013/05/16 12:44:57 PM
WhenChangedUTC        : 2013/05/16 10:45:12 AM
WhenCreatedUTC        : 2013/05/16 10:44:57 AM
OrganizationId        :
OriginatingServer     : isdc01.onesys.local
IsValid               : True
I allready deleted the federation trust and organization relationship and recreated it but the problem persists.
Your help will be appreciated.
Regards

Hi
Check xxxxxxx1234's reply on that link
I would just like to add that I encountered the same problem, but
Get-WebServicesVirtualDirectory | fl was already showing WSSecurity enabled:
So I figured this wasn't going to help me... However, after trying other things without success, i decided it wouldn't hurt to run the
Set-WebServicesVirtualDirectory –identity "EWS (default web site)" –WSSecurityAuthentication $true command. As soon as I did it, the cloud users started to be able to see the free/busy information
of on-premise users.
So just have a try
Cheers
Zi Feng
TechNet Community Support

Remote Admin message to users on Exchange 2013

Hello,
I am currently working with a client post Exchange 2013 migration and we have noticed that when a user configures activesync on their personal device, they are no longer notified that the IT department has the ability to remote wipe.
Here's a link to an sample image of a similar message that they used to receive.
http://www.slsmk.com/wp-content/uploads/2012/08/as-error1.jpg
Is there a way to re-enable this message in Exchange 2013? We also have a device policy that has been set up. Could the policy be the reason that the message no longer appears? If this is no longer available in Exchange 2013, is there some
sort of notification that can be set up to inform the user?
Thanks,
Dean

Weird, I just verified that I get the popup in my organization and we don't do anything crazy out of the ordinary for ActiveSync policies. What CU/SP are you running in your organization? Can you check the phone to see if the activesync account
is already a device administrator? Maybe that has something to do with it.

Exchange 2013 OWA IM to federated users

Hi I configured Exchange 2013 OWA IM for Lync server and everything is working fine except that I can't IM federated Lync users when the conversation is initiated from OWA. When I start an IM conversation from the federated user to my OWA, everything is
working fine. Also the replies arrive then! So it must be something with initiating the session. I don't have issues with federated users form normal Lync desktop clients or mobile clients.
In the lync logs I notice the following when starting the conversation from OWA:
1027;reason="Cannot route this type of SIP request to or from federated partners";
I also notice there's a KB2977259 (http://support.microsoft.com/kb/2977259) that discusses similar things but I'm not working with contacts like that and I guess they don't mean that you have to do this for every federated contact a Lync user has.
Does somebody else also experience this issue?
Update: following this KB I tried to add a new outlook contact in owa and add my sip address as "sip:[email protected]". When doing this it actually work to IM this federated user. But this is actually a workaround you can't expect your users
to implement. I can't believe nobody else has issues with this.

Hi DS_Kevin,
Please post a little more log information. It seems that IM from OWA can’t locate the federated user’s SIP address without the sip prefix.
Best Regards,
Lisa Zheng
Lisa Zheng
TechNet Community Support

Exchange 2013 Content filter agent quarantined message: wrong address appears when I click "Send Again"

Hello,
This is a strange one. I have Exchange 2013 and outlook 2013 and I have been using the content filter agent as a layer of spam protection since we were on 2008 and 2007. I redirect all my spam to a quarantine mailbox and examine it daily for false positives.
When I find one I click "Send Again" from the message in the quarantine mailbox to forward it on to the original sender. Normally Oulook automatically populates it with the original recipient. Today I noticed one that, for some reason, inserted "groupwise-"
in the front of the address(so for example "[email protected]:3:1") This concerns me as there is no such address and I have no idea where it is pulling this address from. I don't
use groupwise software. The quarantine mailbox has info in a postmaster and abuse reporting email. It shows the address correctly as "[email protected]" Only when you click "Send Again" does it
insert this groupwise address. Any ideas why?
This has only happened on one email so far.
Thanks.

Hi,
I noticed that the issue happened when you released quarantined messages to their intended recipients by using the Send Again feature in Microsoft Outlook.
Does the issue happen to all quarantined mailboxes. Please confirm if the messages have been sent to the intended recipients successfully or sent failed with NDR returned because of the wrong email address.
Please try to
disable the mailbox quarantine then enable to check whether the issue persists. Also make sure there is no third-party program installed in Exchange server and local machine for quarantine mailboxes.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 - Some messages net being delivered with shared SMTP Address Space

Hi
I am having a problem with some internal messages intermittently not being delivered. When I go to the Exchange ECP -->Mail Flow -->Delivery Reports I can see the following error with the message:
Submitted
2013-03-07 11:36 AM EXCHANGE
The message was submitted to exchange.******.local.
Pending
2013-03-07 11:36 AM exchange.******.local
Message was received by exchange.******.local from Exchange.******.local.
Failed
2013-03-07 11:36 AM exchange.********.local
The domain name in the email address is incorrect. Check the address.
554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain
However, usually just waiting a few minutes and then sending to the same recipient, the message will be delivered:
Submitted
2013-03-07 11:41 AM EXCHANGE
The message was submitted to exchange.******.local.
Pending
2013-03-07 11:41 AM exchange.******.local
Message was received by exchange.******.local from Exchange.******.local.
2013-03-07 11:41 AM exchange.******.local
The message has been transferred from exchange.******.local to Exchange.******.local.
Delivered
2013-03-07 11:41 AM exchange.******.local
The message was successfully delivered.
I have setup an Accepted Domain as Internal Relay, with a Send Connector to deliver any mails if the user is not found in Exchange server.

Hi All
I had this issue as well.
Here is the solution i used to fix this once for all:
My Environment:
AD server with private and public NICs
Exchange Server with Private and Public NICs
Used a dummy domain (Not owned by me) (ex: corp.com) on Private Network.
Created accepted domains for the domains that i own on exchange server.
Issue Cause:
When an external user (Gmail, hotmail.. etc) sends an email to my accepted domain, as the MX record is pointed to my exchange server on the public IP, the mail flows till my exchange server. Now the transport service on the CAS, hand's over the email to
Transport Service on the Mail box server. There it goes to the categorizer. Here the DNS look up happens and the next SMTP send service will either hand over the mail to the Mail box or send a Non delivery report stating that a mail box, domain name is not
found with in itself.
The issue here is caused by our private DNS where it fails to resolve the internal dummy domain that i used because the resources on the DNS server was completely utilized my memory ballooning in VMware. Ignore the ballooning thing if you do not understand.
Resolution:
I created an entry in the C:\Windows\System32\Drivers\etc\hosts file of the exchange server as below:
mail01.corp.com 192.168.80.132 .i.e., <host name of the exchange server>.<domain prefix>.<domain suffix> <Private IP address of the exchange server>
I change the secondary DNS on the Private NIC of the exchange server to itself .i.e., 192.168.80.132 and forced it look within itself when the primary DNS does not respond at times.
Now my exchange server is absolutely stable. It worked for me !
Hope this post helps you fix the issue or at least help you think a bit ahead.
To understand more about your scenario, i would suggest you look up the logs at C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs (if you have not changed the default drectory while instalation) and Frontend Connectivity logs and Mailbox
connectivity logs. I am sure those logs will help you understand whats going wrong behind the scenes.

Is there an Exchange 2013 DoD/Federal Message Clean/Spill Procedure?

Similar Messages

Maybe you are looking for