No mail flow Public folders

Hi. I'm migrate to Exchange 2013. I moved mailbox, moved public folders ( 20 folders in one pf-mailbox). I can see structure public folders, but when i send mail to public folders, i see error: this recepient not found
Формирующий сервер: EXCHANGE2013.polikomm.local
Remote Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'
Can you help me

Hi,
Please use the Get-PublicFolderStatistics command to check result.
Please disable this affected public folder and re-enable it to check result.
Please create a new public folder and mail-enable it, then send message to this new folder to check result.
And please check if this issue persists in OWA.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Similar Messages

  • Mail-enabled Public Folders not accepting email from external users after migrating from Exchange 2003

    We are in the process of trying to decommission our Exchange 2003 server, all of the replicas have been moved to the Exchange 2010 SP3 servers. However, each time we dismount the public folder store on the 2003 server (just to see what won't work) nobody
    from outside the company can send mail to the mail-enabled public folders (we use these to communicate with vendors and customers).....they sit in the 2003 mail queue until I remount the store.
    I have mail disabled them on the 2010 PF server, waited a few hours and then mail enabled them again. Same issue. Interesting to note is that when the PF store on the 2003 server is dismounted people inside
    the company can still send to the mail-enabled PFs (which is good). I am stumped.
    HDL

    Hi,
    There is similar issue in the below post.
    https://social.technet.microsoft.com/Forums/exchange/en-US/20dc0f53-41c2-4275-a391-fd9b0907a7e1/after-move-all-replicas-to-exchange-2010-mail-enable-public-folder-stops-receiving-external-emails?forum=exchangesvrdeploylegacy

  • Mail-enabled Public Folders not showing as enabled in PFMC or EMS

    Good morning
    I have some PF's that are mail enabled, but running the Get-PublicFolder cmdlet shows "mailenabled" attribute as False. Also, in the PF Management Console, the folder shows as not mail enabled (with an option to enable it).
    I found this thread that seems to be related:
    http://social.technet.microsoft.com/Forums/exchange/en-US/918aad03-c96f-4023-89cc-ec2c66e51b93/mailenabled-public-folders-not-showing-as-mailenabled?forum=exchangesvrgenerallegacy
    I'd like to do some testing, but recreating this issue with a test PF is actually really hard.
    Does anyone know a way to force that "mailenabled" attribute to False after mail-enabling a PF? I can't find any ADSI attribute that is obvious. I changed MsExchRecipientTypeDetails to <not set> but that didn't do it...
    **UPDATE** I just found out that msExchMailboxGuid is missing from that object. Does anyone have any kind of suggestion for how I can find the Guid of the mailbox that is no longer associated with this PF?
    **UPDATE 2** I have found other PF's that are missing this attribute, but they are not displaying any symptoms. They are showing as mail enabled in the EMS and PFMC. So I guess this isn't a required attribute.
    Could anyone explain the purpose of this attribute for mail-enabled public folders? I just assumed it was required.
    Thanks!

    Hi,
    Do you migrate these mail-enabled public folders from previous Exchange server to Exchange 2010?
    Please check if you can see the SMTP address for mail-enabled public folders via Properties of Public folders.
    Please check if they show in the Microsoft Exchange System Objects in ADUC.
    Besides, I recommend you mail disable the public folder and then mail enable it again to check the result in the Public Folder Management Console.
    For a mail-enabled recipient, a minimum set of attributes is required to make all Exchange components work properly. For example, a mail-enabled entry (a user, contact, group, or public folder) has to have at least these attributes: mailNickname, legacyExchangeDN,
    and displayName. Without the mailNickname attribute, an object is not considered mail-enabled.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • SPAM and Exchange 2010 Mail-enabled Public Folders

    Is there a way to determine if mail sent to our Exchange 2010 mail-enabled Public Folders by our customers is ever rejected because it was tagged as spam? The concern is that we might not be receiving some email. We rely on the mail-enabled PF's
    heavily, but since they aren't a mailbox there is no Junk E-mail folder to check. We do not have the resources to check EOP on a regular basis throughout the day, and the customer would not get an NDR or anything like that.
    HDL

    Hi,
    You can consider to use Message Tracking tool under EMC -> Toolbox to track these messages.
    Understanding Message Tracking
    https://technet.microsoft.com/en-us/library/bb124375%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
    Search Message Tracking Logs
    https://technet.microsoft.com/en-us/library/bb124926(v=exchg.141).aspx
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Collect name, Identity, parentpath and PrimarySmtpAddress of all mail enabled public folders.

    Hi,
    I’m trying to collect the name, Identity, parentpath and PrimarySmtpAddress of all mail enabled public folders. PrimarySmtpAddress returns empty whatever I do. If I use this same cmd-line then it works fine.
    What am I doing wrong? Here is the powershell code I'm using:
    Get-PublicFolder \ -Recurse  -resultsize unlimited  | ? {$_.MailEnabled -eq $true} | Select-Object Name,Identity,parentPath, `
    @{label='PrimarySmtpAddress';expression={"$((Get-MailPublicFolder '$_.Identity').PrimarySmtpAddress)"}}
     Thanks in advance!
    win_builder

    The ps code next is getting the info i want to collect:
    Credit goes to travis5150 and Chris Dent from expert exchange
    cls
    $publFolders = get-publicfolder -resultsize unlimited  -recurse | ? {$_.MailEnabled -eq $true}
    @(foreach ($publFldr in $publFolders){
    $objProp = "" | Select Name,Alias,Identity,ParentPath,PrimarySmtpAddress
    $objProp.name = $publFldr.name
    $objProp.Identity = ($publFldr.Identity)
    $objProp.parentpath = $publFldr.parentpath
    $objProp.Alias = (get-mailpublicfolder -id $publFldr.identity | select -exp Alias)
    $objProp.PrimarySmtpAddress = (get-mailpublicfolder -id $publFldr.identity | select -exp PrimarySmtpAddress)
    $objProp
    Thanks for your help and time!!
    win_builder

  • Mail-enabled Public Folders Not showing as Mail-enabled

    We have completely migrated from Exchange 2003 to Exchange 2007 (SP1 Rollup 5).  Many, but not necessarily all, of our mail-enabled public folders do not appear to be mail enabled in either the 2007 PF Management Console or the Shell, yet they are mail-enabled in the 2003 System Manager and we can send email to them.  If we mail-enable a folder in the EMC, it blows away any previous email addresses and creates a new one.
    Any reccomendations on how to get 2007 to accurately display the properties of these folders??

    Issue description: Mail-enabled public folders can’t show as mail-enabled status in the EMC and EMS after migrated from exchange 2003 to exchange 2007, right?
    Troubleshooting:
    1.       Please use “Get-PublicFolder” to check the output of a migrated problematic public folder, see if the value of “MailEnabled” is “True”
    Get-PublicFolder -Identity "\problematic public folders name"
    2.       Please find out where migrated problematic public folder objects exist in the AD. By default, mail-enabled public folders should stay in the “Microsoft Exchange System Objects” container. You can use ADUC or ADSIEditor to verify their current location
    3.       I assume that link between mail-enabled public folder and its AD object has been broken during the migration. So, I suggest you to create a test mail-enabled public folder, and compare the attributes of its AD objects with the problematic one with ADSIEditor. This will tell us if there are any incorrect values in the attributes of the problematic public folder objects
    a.       Launch the ADSIEditor (Start->run-> ADSIEditor.msc)
    b.      Locate problematic mail-enabled public folder object and the new created one
    c.       Right-click the objects and select “Properties”. Then, compare their attributes in the “Attribute Editor” tab
    Notes: Please select all three checkboxes in the “Attribute Editor” tab, it will save more time during the comparison

  • Cannot delete mails in public folders using OWA after applying SP3 RU5

    Hello,
    we recently applied service pack 3 rollup 5 to our Exchange 2010 server (before it was running rollup 4).
    Ever since, when we try to delete a mail in a public folder using OWA we get the message "An unexpected error occurred and your request couldn't be handled". Each attempt also causes error 108 in the application log (Outlook Web App couldn't
    connect Exchange Web Services due to a configuration error. Response code = "500".) which is not accompanied by any other errors.
    Neither uninstalling the rollup nor restoring the server's system state to a point before installation of RU4 could fix the error. Deleting mails in a mailbox still works fine, it's only within public folders and only in OWA.
    Any ideas?

    Hi,
    Please refer to the following article:
    http://support.microsoft.com/kb/2249852/en-us
    The issue occurs when the Internet Information Services (IIS) website that hosts the Exchange Web Services (EWS) virtual directory contains a site binding that binds to an IPv6 address.
    Note It is a known issue that this configuration may cause an exception .
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Mail delivery to Public Folders stops when Public Folder database dismounted from old server. Old server to be decommisioned.

    I have 2 Exchange 2010 SP3 RU6 servers.  All Mailboxes and Public Folders have been moved from the old server to the new one.  If I dismount the Public Folder database from the old server, delivery to mail enabled Public Folders stops.  I
    believe resolving this is the last step before decommissioning this old server and uninstalling Exchange from it. 
    Before I delete the Public Folder database and/or uninstall Exchange from my old server, what do I need to do to setup routing/transport of email to Public Folders on my new server?
    I've used the MoveAllReplicas.PS1 script successfully and believe nothing remains on the old server.  Do I simply need to remove all mail enabled Public folders now with the Remove-PublicFolder EMC command?  Or is it a background kind of task that
    automatically updates after some period of time and then messages just start delivering directly to the new location of my Public Folders?

    Hi and thanks for your suggestion, but Get-PublicFolderMoveRequest  is an Exchange 2013 command.  I first ran the MoveAllReplicas script, probably a month ago.  I've also used the RemoveReplicaFromPFRecursive script and
    still it says that Replicase still exist within the Public Folder Database that I woul like to remove from my old server to be decommissioned.  I've read of other people trying to uninstall Exchange from an old server that have encountered this error,
    causing the uninstall to fail.   Get-PublicFolderStatistics -Server "oldserver" | Format-List returns:
    RunspaceId               : 97d4eaaa-68e5-4c5f-ab61-f56de58fc01e
    AdminDisplayName         : Nntp Control Folder
    AssociatedItemCount      : 0
    ContactCount             : 0
    CreationTime             : 6/18/2002 8:42:31 AM
    DeletedItemCount         : 0
    EntryId                  : 000000001A447390AA6611CD9BC800AA002FC45A0300F020D914C926D011A40900C04FD7BD87FFFFFFFF00020000
    ExpiryTime               :
    FolderPath               : Nntp Control Folder
    IsDeletePending          : False
    ItemCount                : 0
    LastAccessTime           : 8/11/2014 9:28:20 PM
    LastModificationTime     : 11/28/2012 5:41:45 AM
    LastUserModificationTime :
    LastUserAccessTime       :
    Name                     : Nntp Control Folder
    OwnerCount               : 0
    TotalAssociatedItemSize  : 0 B (0 bytes)
    TotalDeletedItemSize     : 0 B (0 bytes)
    TotalItemSize            : 0 B (0 bytes)
    ServerName               :
    StorageGroupName         :
    DatabaseName             : Public Folder Database 1
    Identity                 : 000000001A447390AA6611CD9BC800AA002FC45A0300F020D914C926D011A40900C04FD7BD87FFFFFFFF00020000
    MapiIdentity             : 000000001A447390AA6611CD9BC800AA002FC45A0300F020D914C926D011A40900C04FD7BD87FFFFFFFF00020000
    OriginatingServer        : oldserver
    IsValid                  : True
    Here it shows the size and count are 0 (zero), so I should be good to go.  But, I am unable to remove it due to the Replicas Exist error.
    Elsewhere, I found a suggestion to clear the checkmark in the OAB 'Distribution' settings regarding Public Folders, but that didn't help.  I've also seen posts saying to dismount the Public Folders, rename them and when mounting,
    take the option to create a blank or empty Public Folder database.  When I did that, the mail enabled Public Folders did not resolve when sending emails.  I had to quick mount the saved copy of my Public Folder database.
    So, regarding your suggestion, does Disabling and then Enabling mail enabled folders re-associate or register them with the current Public Folder database structure? 
    One more thing I found is that the get-mailpublicfolder command returns an error stating a folder is corrupt.
    WARNING: The object ci.walla-walla.wa.us/Microsoft Exchange System Objects/Library Vacation Calendar has been corrupted, and it's in an inconsistent state. The following validation errors happened:
    WARNING: Property expression "Library Vacation Calendar" isn't valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One
    or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII
    string in the e-mail address, which is generated from such an alias.
    I don't see anything in the name of the folder, unless it actually has the " character embedded in it.  But what is also odd is that I don't have a folder called "Library Vacation Calendar".  It may be the remnant of something in the
    past of a failed attempt.  I do have a folder called VacationCalendar that the Library uses, and have even exported to PST and recreated without any impact to this problem.  I do not know how to clear this condition, and assume it is responsible
    for the Active Replicas error I get when trying to remove the PF database. 

  • Exchange 2010 - visibility of items in Public Folders

    Hello all,
    I already posted this question to the German Exchange 2010 forum, but have not gotten an answer yet. So I hope to be more lucky in the English forum.
    Environment: Exchange 2010 SP3 RU4, 2 replicas for Public Folders, Outlook 2007 cache Mode
    Problem:
    Some of our users have a phenomenon when working with mail enabled Public Folders:
    User has the focus set to Public Folder A, an email is sent there (and correctly delivered) but remains invisible to the user. When he changes the focus to point to his inbox or to Public Folder B and directly changes back to folder A he can see the email.
    Other users can see the email directly on delivery without leaving the folder first.
    When an affected user adds Public Folder A to his Public Folder Favorites he can see that an email is delivered from the change in numbers of unread mails (number in brackets behind folder name).
    I already checked the Exchange server to see if there is a replication related problem (though the default Public Folder DB is the same for all mailbox databases). Even after a successful replication an effected user does not see the email unless he leaves
    the folder and re-opens it.
    As the problem does not affect all users having permissions to this folder I picked one affected user and tried to remedy the issue as follows:
    - deleted the existing Outlook profile and re-created it => without success
    - deleted the user profile and re-created it => without success
    We use Outlook Cache Mode (set by policy, so the user cannot deactivate it) but there is no Public Folder data downloaded.
    When I create a new mail enabled Public Folder to test the scenario with an affected user everything works without problems, he can see an email on delivery.
    As far as I know this problem occurs with only two folders (and for both folders only a few users are affected - different users for each folder) I do not know what else to do. Can someone please give me a hint where to look at? Thanks in advance.
    Kind regards,
    Klaus

    The user is caching the public folder.  When he changes the focus and goes back, it tells Outlook to update.  In my experience, I've seen that Outlook only gets the update notices for the primary mailbox, so cached shared mailboxes are generally
    rarely updated.  We have stopped caching shared mailboxes for this reason and others.  Think of the following scenario:
    Ten different users perform actions on items in a shared mailbox
    When they first get the message, they move it to a subfolder in the mailbox (so it won't be there for other users)
    Since users are working in Cached mode, they will see an out-of-date image of the mailbox - they will move the item in their copy of the mailbox, but that won't be reflected in the other mailboxes until their copy updates to the server, then the server updates
    the other copies.  Talk about being lagged ...

  • User Access to Public Folders Disappearing (Outlook 2013)

    I have one particular user who is losing access to public folders in Outlook 2013.  I have found that going to
    File > Account Settings > Account Settings > Email [TAB] > Repair... and then following through that dialog temporarily restores public folder access after restarting Outlook.  However, once Outlook is restarted
    for 30-60 seconds, the public folders disappear again. This is only happening for this one user.  They receive their public folder permissions via group membership.  Other group members report no such issue. I had another user with identical permissions
    log into the same workstation and they again had no issue.
    What could be causing this? This is a particularly bothersome problem since this user happens to be the office scheduler and the calendar they schedule on is public (which, thanks to reduced functionality in Exchange 2013, is no longer accessible in OWA).
    Tech specs: Exchange 2013 CU5 accessed from Outlook 2013 running on Windows 8.1 Update.  Outlook did not log any events during the time when public folders were dropped, nor are there any network connectivity issues being logged.
    Any ideas for resolving this?

    Hi,
    Please check the connection status for Outlook.
    Press the CTRL key and right-click the Outlook icon in the notification area, then select Connection Status.
    Please run the command get-mailbox administrator | fl defaul* to check the default public folder mailbox for this affected user.
    Do you have mail-enabled public folders? If you have mail-enabled public folders, you can check if this user can view public folders in OWA.
    If possible, please re-add the public folder permissions for this user to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 delivery reports for mail enabled public folder

    How can I get delivery reports for mail enabled public folders? Would I search the related public folder mailbox?

    Hi,
    When you track messages using Delivery Reports, you can only choose user mailbox when you select mailbox to search. Under the option "Mailbox to search", there is no mail-enabled public folder listed there for you to select from
    the address book.
    But you can search messages sent to or received from mail-enabled public folder.
    Track messages with delivery reports
    http://technet.microsoft.com/en-GB/library/jj150554(v=exchg.150).aspx
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Migrating email-enabled public folders corrupted

    We migrated our public folders from EX 2010 to 2013 but currently face 2 issues with the import:
    a.  All public folders/subfolders became email disabled - about 300 + folders
    b. More importantly there is a mismatch between folder name and assigned smtp addess.
    For example imported folder name is qa1  smtp associated with the folder is [email protected]
    is there a powershell script we can run to fix these issues ?
    alex serdyukov

    Hi,
    A. If you use serial migration to migrate public folders, then Mail-enabled public folders that are created after a public folder migration is started won't be mail-enabled in the destination organization. You'll need to manually mail-enable
    these public folders manually when the migration is complete. This also applies to public folders that existed prior to migration starting, but were mail-enabled after migration started.
    Refer from
    https://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
    B. After these public folder are enabled, then check these mail-enabled public folders’ SMTP address.
    If they are also mismatched, please check if the emailaddresspolicy is assigned to them with the following command
    Get-MailPuclicFolder “PF path” | fl EmailAddressPolicyEnabled
    If the value is true, then set this value to false and use the following command to correct them (or check email address policy)
    $allPF = Get-MailPublicFolder -Resultsize unlimited
    Foreach ($PF in $allPF)
    {Set-MailPublicFolder -Identity $PF.identity -PrimarySmtpAddress ($PF.alias+’@company.com’)}
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Mail Enabled Public Folder Issues after migration online

    Hi
    We have recently migrated our Legacy (Exchange 2010) Public Folder Infrastructure to Exchange Online - we have a hybrid setup, SSO and DirSync.
    We initially had an issue where some of our mail enabled public folders had lost their link with the associated MailPublicFolder objects and as such could not receive email. 
    We resolved this issue ourselves however we are now experiencing a different issue which i believe should be easily resolvable however this isn't the case at the minute.
    The issue is that when a user emails a Mail Enabled Public folder Exchange online is attempting to relay the email back to our onPrem servers.  This is occuring for the bulk of our Mail Enabled Public Folders - we have ~1200 of these.  The only
    folders that are working as expected are those that had the initial issue above and for which we had to remove and re mail enable these folders.  We also had to recreate any secondary smtp address for these folders.  This accounts for 88 of our total
    MEPFs.
    I have checked the attributes on the MailPublicFolder objects for those that are not working and those that are functioning as expected.  The only difference in these that I can see is that the MEPFs with the issue have a value set in the ExternalEmailAddressAttribute.
    I have tried to programatically set this value to $Null however i receive the following error:
    The external e-mail address $null is not an SMTP e-mail address.
    I have also tried the following : set-mailpublicfolder -Identity "MEPF"-ExternalEmailAddress "<not set>"
    with the same resultAttempting to use the following syntax -externalemailaddress @{remove=$oldAddress} returns the following error:
    Cannot process argument transformation on parameter 'ExternalEmailAddress'.Cannot convert the "System.Collections.Hashtable" value of type"System.Collections.Hashtable" to type "Microsoft.Exchange.Data.ProxyAddress".
    At present the only fix that I have for this is to take a copy of the email addresses for an affected public folder, Mail disable it, wait for the object to be cleared, re-enable the public folder as a mail public folder and then re-add the email addresses. 
    This is ok on an adhoc basis but not for the ~1200 folders that are affected.  Especially when from what i can see it should be relatively straightforward to resolve this with a simple PowerShell script.
    I do have a case open with MS for this but I am hoping that somebody here can help also.
    Thanks
    Joe

    Ok so i fixed it myself.
    The thinking here is that the ExternalEmailAddress was set using the Primary SMTP address while the Public Folders were on premises.
    In order to get the required information we ran a script to export all the MailPublicFolder objects which had a value in the ExternalEmailAddress attribute.  We exported the Name, ExternalEmailAddress and GUID
    We then ran a second script to export the Identity, MailRecipientGuid from Get-PublicFolder -recurse. 
    The MailRecipientGUID is what ties the Mail Enabled Public folder to the MailPublicFolder object.
    Using Excel I then matched the two up and created a csv file with the Identity Attribute from the get-PublicFolder command and the ExternalEmailAddress Attribute from Get-MailPublicFolder.
    The following script then used this csv file to first Mail Disable the Public Folder, then Mail Enable the Public Folder.
    Once these steps have been completed the final stage is to add the SMTP address back in to the Public folder.
    To do this it is necessary to retrieve the new MailRecipientGUID and use it to return the MailPublicFolder for the Set-MailPublicFolder command.
    I was happy to use this script after i tested with a small subset of the data.  It is provided as is with no guarantee that it will be suitable for you to use and any use of this script is at your own risk.
    Script to Automatically fix brokenn Public Folder Objects
    Created By: Joe McGrath
    Created On: 18/02/2014
    $Path = "C:\PublicFolders.csv"
    import-csv -Path $Path | ForEach-Object `
        Disable-MailPublicFolder -identity $_.Identity -Confirm:$False
    Write-Host "Broken Public Folders Now Mail Disabled"
    Write-Host "Waiting for commands to be fully processed online - the script will continue in 5 minutes"
    Start-Sleep 300
    Write-Host "Re MailEnabling Public Folders"
    import-csv -Path $Path | ForEach-Object `
        Enable-MailPublicFolder -identity $_.Identity
    Write-host "Broken Public Folders now enabled"
    Write-Host "Now waiting to allow online service to catch up - script will continute in 5 minutes"
    Start-Sleep 300
    Write-Host "Updating email addresses for broken public folders"
    import-csv -Path $Path | ForEach-Object `
        $NewPF = get-publicfolder -identity $_.Identity
        Write-Host $NewPF.Identity
        Write-host $newPF.MailRecipientGuid
        $EmailAddresses = $_.AdditionalEMailAddresses
        $NewMailPF = get-MailPublicFolder -resultsize unlimited | Where-Object {$_.Guid -eq $NewPF.MailRecipientGuid}
        Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$FALSE
        Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddresses $EmailAddresses -EmailAddressPolicyEnabled:$FALSE
        Set-MailPublicFolder -identity $NewMailPF.identity -EmailAddressPolicyEnabled:$TRUE
        $EmailAddresses = ""
    Write-Host "Completed!"

  • Migrating public folders to exchange 2013 hebrew issue

    I am migrating public folders to exchange 2013. half of them a named in hebrew.
    The migration fails, the error is character  related. 
    Is it possible at all to migrate hebrew named public folders?

    Hi,
    Did you got the error message mentioned in the following thread?
    http://social.technet.microsoft.com/Forums/exchange/en-US/8b383a46-b710-4fc0-aa0b-e52f288cf93d/e2010-to-e2013-public-folders-migration-failed?forum=exchangesvrdeploy
    If so, please check if they are mail-enabled public folders. If they are mail-enabled public folders, please make sure there are no invalid characters in alias.
    Based on the description, you couldn't migrate public folders named in Hebrew, other public folders could be moved successfully. If I misunderstood your concern, please let me know.
    If the issue persists, I'm afraid you need to rename these public folders in English.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange Online Protection and Public Folders

    Hi,
    We have just been migrated to Exchange Online Protection from FOPE and although users can now manage their own quarantines, they cannot do this for Mail Enabled Public Folders. Is this possible?
    Many Thanks

    Hi Paul,
    I replied to a post from you in another thread. It's easy to miss though, so here's what I said:
    "You should tell mail2web that there is an option in Exchange to hide public folders from IMAP clients. I'm an IT manager at a large software company with 50% of our users on Macs. We turned on the option to hide public folders from IMAP clients a while ago, long before the iPhone. It's worked very well and continues to work for iPhone people (like me!).
    There was no reason for us to make public folders viewable via IMAP, so hopefully the same will be true for mail2web."
    I'm actually really glad that Apple made this change. I want to see most of the folders at the inbox level in Exchange and with the Exchange switch turned on to hide public folders, there's no downside.
    Regards,
    fh

Maybe you are looking for