Large Mail.que database in Exchange 2013

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
 And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

[Background]
Since Exchange 2013 is released, some user may come across the following situations:
The space of disk C is used up.
The transport service stops processing messages.
The Mailbox server is crash.
In this case, the issue can be resolved with checking with the mail.que file which is in the following path on the Mailbox server:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue
[Symptom]
The Mail.que file on all Exchange 2013 servers grows very large and it’s even over 20 GB.
[Cause]
It’s a by design behavior.
Different from the previous Exchange server, Safety Net which has the same function with the Transport dumpster in Exchange 2013 takes up the volume of the mail.que file and
it’s the feature which is responsible for the large size of the mail.que in Exchange 2013.
 And here is a reference about the feature Safety Net in Exchange 2013:
http://technet.microsoft.com/en-us/library/jj657495(v=exchg.150).aspx
[Workarounds]
1. Allocate large space for the Exchange 2013 installation or increase the volume for Exchange 2013.
These articles will also provide further detail of size calculating:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
(See section: “Transport storage requirements”)
2. Moved queue database to another drive by using
Move-DatabasePath
3. Reduce the SafetyNetHoldTime and MessageExpirationTimeouton values to one day (default values are 2 days). And these commands can be in use:
Set-TransportConfig SafetyNetHoldTime 1.00:00:00
Get-TransportService | Set-TransportService -MessageExpirationTimeout 1.00:00:00
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.
You cant move the queue database with move-databasepath. You have to follow this method:
http://technet.microsoft.com/en-us/library/bb125177(v=exchg.150).aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

  • How can I script out automatic mail profile connection to Exchange 2013

    We use a program called Desktop Authority 9.1 that is a fully featured kixstart based logon user profile customization tool.  It does a full gamout of things like map drives, folder redirection, import registry edits, run silent application installers,
    and of course create the Outlook profile.
    There's no issues with this tool creating an outlook profile internally to mail.domain.com, and even detecting laptops and configuring it for outlook anywhere to webm.domain.com and cached mode.
    Issue I'm having is trying to roll out Exchange 2013.  This tool simply does not seem to create the mail profile.  On a test computer I have the hosts file pointed to the new 2013 server from these names: webm, mail, autodiscover.  At log
    on I simply get an error "The name cannot be resolved.  The name cannot be matched to a name in the address list."  When you click OK you get a little confusing dialog box with the exchange server name: mail  and the mailbox: windows
    user ID.
    So I tried to do this manually in the Mail (32-bit) control panel applet.  It doesnt matter if I put in mail, mail.domain.com, webm, webm.domain.com, email (the netbios name of exchange 2013), etc.. I get the same error.  I went into More settings
    > Connection > connect to microsoft exchange using HTTP and in the proxy settings I have webm.domain.com, connect SSL Only, only connect to proxy servers that have the name: msstd:webm.domain.com, and the rest is checked and NTLM Authentication is checked.
    I simply CANNOT manually create an outlook profile at all.  I can surely delete this one, start outlook, click next through the wizard taking all the default options and get Outlook configured that way (via Autodiscover service), but I need a way to
    do it manually so I can have Desktop Authority do it manually.  Why?  Two major reasons:
    1.  If our end users are greeted with an Outlook startup wizard every time they go to a different computer, and have to click next through it, our help desk is going to be overwhelmed with "what is this outlook startup wizzard?" questions.
    2.  Desktop Authority also attaches additional mailboxes.  We need the outlook profile passed through DA's scripting so different users departmental voice mailboxes are attached in their outlook.  IE) Mailbox VM_FAX_Accounting is attached
    to all of the accounting associates Outlook.

    Ok I found another way to get autodiscover to work..
    In Group Policy go to User Configuration > Administrative Templates > Microsoft Office 2010 (and 2013 in my case) > Miscellaneous > Suppress recommended settings dialog > Change to ENABLED.
    Now go to User Configuration > Administrative Templates > Microsoft Outlook 2010 (and 2013 in my case) > Account Settings > Exchange > Automatically configure profile based on Active Directory Primary SMTP address > Change to ENABLED.
    Now for the shared mailboxes,  I guess when we plan to migrate a department, their shared mailbox MUST be migrated from 2007 to 2013 on the same evening, and then we must go into that shared mailbox and ensure each individual user has "Full access
    permissions" to it.
    Now in Desktop Authority we publish this reg file: 
    Windows Registry Editor Version 5.00
    [HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover\RedirectServers]
    "autodiscover-s.outlook.com"=hex(0):
    "autodiscover.outlook.com"=hex(0):
    "autodiscover.domain.com"=""
    [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover\RedirectServers]
    "autodiscover-s.outlook.com"=hex(0):
    "autodiscover.outlook.com"=hex(0):
    "autodiscover.domain.com"=""
    [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover\RedirectServers]
    "autodiscover-s.outlook.com"=hex(0):
    "autodiscover.outlook.com"=hex(0):
    "autodiscover.domain.com"=""
    Why that?  Well it turns out further testing when I added full permission to a new 2013 test shared mailbox, yet another nag screen was presented in Outlook which states "Allow this website to configure [email protected] server settings?  autodiscover.domain.com/autodiscover/autodiscover.xml
    - Your account was redirected to this website for settings.  You should only allow settings from sources you know and trust.  (Allow) (Cancel).  If end users see this, you can bet our helpdesk calls will be out of control.  We undergo security
    awareness training and they will question ANYTHING resulting in redirect or dialog boxes asking about trust, and really that's a good thing.
    That registry should I think handle Outlook 2007, 2010, 2013, and we will just have to maintain it for future versions.
    We maybe have, I dont know less than 5 Outlook 2007 installs and they are on spare laptops, so If I want to cover it all I just have to download the Office 2007 ADMX templates for Group Policy so I can change those two settings above as well.
    The other way I thought was to use powershell and script something out to pull from Exchange the GUID, append the @domain.com and put that into a variable that our Desktop Authority application can plug in at startup.  But thats a little too much custom
    programming whereas I think using GPO's and documented registry keys may be a better fit.
    I just have to do testing to figure out what's going to happen to the users profile if it already exists on 2007, then its migrated to 2013.  Will it be deleted?  Will they lose all of their signatures?  I know for many on network
    PC's they will be going from direct mapi connection to Cached mode.  Is that a good thing?  I would imagine less load on the server and network once the mail is downloaded.
    We would plan on a slow migration on a departmental basis.  Luckily our departments have their own user OU's so applying this group policy can be done in the same manor.

  • What is the best backup plan for Archive Databases in Exchange 2013?

    Hi,
    We have Exchange 2013 with Hybrid setup with O365.
    We have On premise exchange 2013 servers with 3 copies of primary Database & Single Copy of Archival DBs.
    Now we have to frame backup policy with Symantec Backup Exec which has to backup our primary & Archival DBs
    In 2007 exchange, before migration to 2013, we had policy of DBs - Weekly Full backup & Monthly Full Backup
    Please suggest what would be the best possible backup strategy we can follow with 2013 DBs.
    That too, especially for Archiving DBs
    Our Archiving Policy are - 3 category - Any emails older than 6 month OR 1 Year OR 2 Year should go to Archive mailbox.
    Keeping this in mind how to design the backup policy ? 
    Manju Gowda

    Hi Manju,
    you do not find best practice different from the common backup guidelines, as there is no archive db specific behaviour. Your users may move items to their archive at any time as well as your retention policies may move items that machted the retention policies
    at any time. The result is frequently changing content to both, mailbox and archive mailbox databases, so you need to backup both the same way. You also may handle archives together with mailboxes together in the mailbox db 
    Please keep in mind that backup usually means data availability in case of system failure. So you may consider to do a less frequent backup with your archive db with dependency to the "keep deleted items" (/mailboxes) setting on your mailbox database.
    Example:
    keep deleted items: 30 days
    backup of archive db: every 14 days
    restore procedure:
    * restore archive DB content
    * add difference from recover deleted items (or Backup Exec single item recovery) for the missing 14 days.
    So it depends more on your process than on a backup principle.
    Regards,
    Martin

  • How to get a summarized mail traffic report in exchange 2013

    Hi all
    How to calculate the exchange 2013 SMTP mail traffic in terms of hour,day,month,top senders,largest message and top recipients list . Same time we would like to have those summarized mail traffic report for all the mailbox servers in the form of graphical
    view as well as in a csv file  ?
    Please all of us share your thoughts and possibilities .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

    You may calculate hourly email traffic using "Message Tracking Logs and Log Parser".
    I would like to refer you on this well explained article that will assist you step-wise to implement in your working environment : http://exchangeserverpro.com/calculate-hourly-email-traffic-using-message-tracking-log-parser/
    Moreover, if you wish to achieve this goal automatically, you may also consider on this automated application (http://www.exchangereports.net/) that provides a deep-view of email traffic report in real time at
    granular level.

  • MailboxInSiteFailoverException - OWA session error on database *over (Exchange 2013 SP1)

    Hi all, I have noticed an issue with OWA when database(s) are failed over between DAG members.  The environments in question (issue can be reproduced in separate implementations of 2013 SP1 all-role servers) are 2 or more DAG members within the same
    AD site/subnet.  These are also fresh implementations with SP1 and not upgraded.  Exchange servers are load balanced via Netscaler. 
    So to the issue - OWA users experience the below "..MailboxInSiteFailoverException" message when the database copy is activated.  Exchange does not immediately proxy the requests to the active database.  You can wait several minutes and
    the issue is resolved by refreshing the browser or if you recycle the MSExchangeOWAAppPool on both DAG members, the issue is resolved immediately (OWA session re-established on refresh).
    Testing so far involved opening multiple OWA sessions and activating a database copy.  At that point, upon refresh of the browser the below error is shown (in all test browsers/sessions below) where I would expect any DAG member to be able to proxy
    the client request to the active database server immediately (and not after several minutes).
    https://netscaler_LB/owa
    https://ex2013server-1/owa
    https://ex2013server-2/owa

    Hi Simon, I have tested with no firewall on the exchange servers and on client machines within the same subnet as the servers.  All with the same results.
    I can see many ASP.NET 4.0.30319.0 Event ID 1309 logs similar to this and other threads (http://social.technet.microsoft.com/Forums/windowsserver/en-US/c938dda0-b3bc-4544-851e-f27b503cf4ed/exchange-2013-event-id-1309-source-aspnet-40303190).
    IIS logs show similar monitoring mailbox issues but I am still currently looking through the logs.  Thanks for your input.
    2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
    2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
    2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
    2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
    2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_3ce57cd622aa4655a ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
    - 302 0 0 47
    2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_2891f9d41af2422e8 ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
    - 302 0 0 47

  • Maximum database size Exchange 2013 Standard

    Hi,
    Does anybody is aware of database size limitation for Exchange 2013 Standard. I remember in older version there was a registry tweak to increase database limits.
    Thank you 
    alfa21

    Hi,
    This is the official answer :
    Supported: Approximately 16 terabytes.
    Best practice:
    2 terabytes or less.
    Provision for 120 percent of calculated maximum database size.
    https://technet.microsoft.com/en-us/library/ee832792%28v=exchg.150%29.aspx
    Cordialement,
    Mickaël LOPES
    Blog : http://lopes.im 
      

  • Getting EOP to send mail to On premises Exchange 2013

    one of may clients has Office 365 Enterprise E1 for Nonprofits and on premise exchange 2013 server which I'm trying to implement the EOP service.
    but i cannot get the exchange online outbound connector to forward on the emails to the on premise server.
    i have active directory sync working.
    i.e when i add a new user on premises it creates it online.
    could anybody let me know how to get this service to work.
    what i would like is
    1 mx record to point to eop service and collect and filter email.
    (which i have done by adding mx records as per dns instructions. checks show as fine.but changed back to on premises server because emails where only staying in online inbox. the on premises domain name has been setup within office 365 as default domain and
    in accepted domains within exchange online.both exchange online and on premises default domain name our the same.)
    2 filter mail to be forwarded to correct mail box to on premises server.
    ( which i have setup outbound connector with exchange online to point to our on premises exchange server but does not receive any emails they are received in office 365 online mailbox and not forwarded on)
    3 on premises server to forward mail to EOP service
    ( which i have done by creating inbound connector in exchange online and adding it as smart host to on premises outbound connector and appears to be working fine.)
    am i missing something?
    any help would be gratefully appreciated
    Many Thanks
    Stephen
    1 first server (AD,AD CS,DC,Dhcp,dns servers and Hyper V)
    setup physical server with windows server 2012 r2 standard Essentials Experience Role installed and hyper v role
    2nd server server (exchange 2013)
    VM with windows server 2012 r2 with exchange server 2013 installed and all updates done including exchange cu1 update.

    Matthew thank you your reply but No it is set for Authoritative. would this be the problem.
    many thanks
    Stephen

  • Public Folder Mailbox causes database failover Exchange 2013

    Hi , we are completing a migration from Exchange 2007 to Exchange 2013.  All was going swimmingly until we migrated our legacy public folders.  Now every now and again ( once a day generally ) the Exchange Database hosting the Public Folder Mailbox
    crashes and fails over to another DAG member.
    We are using CU5 and our old 2007 server is offline but not removed from the organization yet.
    The error message is as follows :
    Event ID 1013
    The mailbox with mailboxguid "xxxxxxxxxxxx" caused crash or resource outage on database (GUID="xxxxxxxxxxx")
    along with :
    Event ID 1001
    Microsoft Exchange Server Information Store has encountered an internal logic error. Internal error text is (Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?) with a call stack of (   at Microsoft.Exchange.Server.Storage.Common.ErrorHelper.AssertRetail(Boolean
    assertCondition, String message)
    and :
    Event ID 1002
    Unhandled exception (Microsoft.Exchange.Diagnostics.ExAssertException: ASSERT: Unable to apply maintenance GetNonKeyColumnValuesForPrimaryKey-norow, index corruption?
    The Mailbox Guild matches the Public Folder Mailbox GUID and the Database GUID matches the Database where the mailbox is mounted.
    The error seems to be the same as this question :
    https://social.technet.microsoft.com/Forums/office/en-US/7e823810-29f4-48f2-ad60-37e6ac147d3e/exchange-2013-database-dismounts-unexpectedly
    However I'm after a bit more concrete information as to what actually causes this and if an upgrade to CU6 is required.  This link appears to suggest moving the mailbox will help.  Has anyone else come across this with CU5 and will a mailbox move
    correct it ?
    http://blogs.technet.com/b/exchange/archive/2014/10/03/those-pesky-lazy-indices.aspx

    Hello,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • OWA receives mail long before Outlook (Exchange 2013 with Outlook 2010 and 2013)

    I recently upgraded my Exchange environment to Exchange 2013 SP1. The Outlook users are now experiencing a delay when receiving email. When they do arrive they appear in batches, often 20-45 minutes after they were sent, from a mailbox on the same server.
    Additionally, the mail appears instantly when you monitor the inbox using OWA. The users are experiencing this on both Outlook 2010 and 2013 clients configured in both cached and non-cached modes. This appears to be a problem with Outlook connecting to Exchange.
    Any suggestion about how to correct this would be greatly appreciated. Thanks!

    Hi,
    From your description, when users use OWA, they can receive emails normally. But if they use Outlook 2010 or Outlook 2013, there is a delay in receiving emails.
    I recommend you use the Outlook safe mode to determine whether the problem is caused by add-ins. Also, please make sure users have installed the Outlook latest Service Pack.
    If the issue persist, please create a new profile and check the result.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Mail flow problem between Exchange 2013 and 2010

    Hi,
    we have 4 exchange 2010 servers, 2 mailbox and 2 hubcas. we are migration to 4 exchange 2013 servers, 2 mailbox and 2 hubcas.
    exchange 2013 user can send and receive emails  from/to internet without problems, but when i try to send email to internal users located to 2010 server i have no success.
    i also can receive from exchange 2010, so the problem is only i cannot sent emails to exchange 2010 users.
    is this a problem with receive connector of exchange 2010 or something else ???

    one more thing, when i open exchange queue i got this error:
    451 5.7.3 cannot achieve exchange server authentication. attempted failover to another host but that did not succeed. either there are no alternate hosts, or delivery fail
    For this error refer to the following article:
    http://support.microsoft.com/kb/979175
    Thanks, MikeV MCSE 2012

  • Mavericks Mail won't update Exchange 2013 email

    I see people have written about this already but there doesn't seem to be a solution posted in these forums and it seems like a major bug.
    I use Apple Mail to connect to my work Exchange email. We use Server 2013.
    Mail worked perfectly under Mountain Lion.
    I updated my office iMac as well as my home iMac and MacBook Pro Retina Display to Mavericks on Tuesday and after doing that my Exchange email on all three devices would update with new mail very slowly -- maybe every half hour or when I started and re-started Mail. Mail updated on my iPhone and iPad instantly as well as through my office's WebMail portal. That is, this isn't a server-based issue.
    Also, I have a Gmail account that updates normally.
    Searching for answers online, there was a suggestion to change "check new mail" in preferences from "Automatically" to "Every 1 minute." That didn't work, even after I restarted Mail.
    I tried reseting Mail on my office iMac by following instructions I found online. It involved going into the Library folder and deleting four or five Mail-related subfolders. After that, it was as though I was using Mail for the first time.
    That didn't work either.
    The only other thing I can think of is a clean install of Mavericks but that seems extreme.
    Does anyone have an answer to this? 
    The same problem on three devices makes it seem like this is more of a serious OS bug than a client-side issue.

    Donna did anyone ever help you get this fixed? I am having the same problem!!

  • Unable to move mailbox to newly created database in exchange 2013

    Hi, i created a new database in our existing exchange server 2013 sp1 and i was trying to move my mailbox to the newly created one using the EAC. But the mailbox is not getting moved and i am not receiving any errors. Is there anything else i need to do
    after creating the database.
    Please advise.

    Hello
    lets play again:
    new-moverequest -identity useremailaddress -targetdatabase new database
    after two minute get move req log
    get-moverequest -identity useremailaddress |get-moverequeststatistics -includereport |fl
    or if have got more DC specified one Dc with -domincontroller DCname
    sorry my english

  • Moderation Mail Not Work in Exchange 2013

    Hello All,
    I facing difficulties regarding Moderation Mail. The Moderation mail not send to moderator. also i found that the arbitration mailbox also corrupted.
    Error:
    WARNING: The object abc.com/Users/Migration.8f3e7716-2011-43e4-96b1-aba62d229136 has been corrupted, and
    it's in an inconsistent state. The following validation errors happened:
    WARNING: Database is mandatory on UserMailbox.
    WARNING: Database is mandatory on UserMailbox.
    Please suggest

    Hi,
    To recreate this arbitration mailbox, you can follow the steps below.
    Start the Active Directory Users and Computers snap-in.
    Click Users, and then find the following account:
    Migration.8f3e7716-2011-43e4-96b1-aba62d229136
    Remove this account.
    Run the following cmdlet:
    setup /preparead/IAcceptExchangeServerLicenseTerms
    Run the following cmdlets:
    Enable-Mailbox -Arbitration -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136"
    Set-Mailbox "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration –Management:$true
    Here is an article about re-creating the Discovery system mailbox, it is the same process to recreate the arbitration mailbox mentioned in the error message above.
    http://technet.microsoft.com/en-gb/library/gg588318(v=exchg.150).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • How to configure users for internal mail routing only in exchange 2013

    Hi Guys!
    I have a scenario here that i have three (3) group of users, one group is able to have an inbound and outbound mail, meaning they can send and recieved emails from internal and external.The second group of users should have inbound mail(local mail) only
    (cannot send and recieved mails from internet), and the third (3) user is they can recieved an outbound mail but they are not allowed to send mail directly to the client,(Ex.
    [email protected],[email protected],[email protected]) instead they will use the
    [email protected] as the reply to the client. Please let me know how to configure group user 2 and 3.
    Thank you.
    regards,
    Paul

    Hi Paul,
    Great advice from Maganti, just elaborating steps:
    Prevent Group 2 send e-mail to internet by transport rule:
    1. Login EAC with administrator, Mail Flow---> Rule, click “Create a new rule, then give a name “Group2 - No Internet Mail”.
    2. Conditions: select "From a member of a distribution list" & select group "Group2"
    3. Select another condition "Sent to users inside or outside the organization" & Select Outside.
    4. Actions: select "send bounce message to sender with enhanced status code" & write your custom message like “You are not authorized to send mails to internet”.
    Prevent Group 3 directly send e-mail to internet, however it can send message as group:
    We also can create a transport rule which is same with Group2, then open Active Directory Users and Computers to add send as permission with another group (contain same users as group3).
    Best Regards,
    Allen Wang

  • Exchange 2013 - Removing a database and deleting folders but they still reappear!!

    Hi
    I created a new database and moved all the user mailbox's plus discovery mailbox;s over and all went well, i then unmounted and deleted the old database in ECP and stopped all the exchange services and deleted the old database files and folders from the
    C:, i noticed i was still getting some errors with windows backup and after looking around i notice for some reason under program files/microsoft/exchange server/v15/mailbox the old db folder appears with the sub folders 'indexmeta', 'journal' and 'ms', it
    seems that the last trace of the old databases is still being used because the date is always todays date! everytime i delete these foldersers they come back!!
    I think this is the reason why the windows backup is failing with 'this application will not be available from this backup'
    any help would be appreciated!

    Hello,
    If you want to remove the old database, you can follow this document to do that:
    Manage Mailbox Databases in Exchange 2013
    http://technet.microsoft.com/en-us/library/jj150580.aspx
    Did you enable journal on the old database?
    Thanks,
    Evan Liu
    TechNet Subscriber Support
    in forum
    If you have any feedback on our support, please contact
    [email protected]
    Evan Liu
    TechNet Community Support

Maybe you are looking for