Tag Info

Hot answers tagged

11

This has thrown me for a loop in the past as well, as I had read (and experienced) this first hand. The answer is that Microsoft changed the behaviour of store.exe with 2 hotfixes. The 2 hotfixes that modify this behavior is 916783 and 903158. More information on the change can be found : ...


6

Fortunately this is not something you need to worry about. During the migration, there will be short periods where the mailbox is not available, but there is no chance for data loss. Regardless, it's usually a good idea to schedule moves for low-usage times to minimize the user annoyance factor.


6

You can only limit mailboxes by size, not item count in Exchange. Is there any reason you care how many items are there, as long as the quota is maintained? Here is some light reading on Exchange quotas.


6

What you can do about it is to develop a sensible approach and ensure your users do likewise. After discussing the problem with those concerned you may want to impose quotas, which will force your users to start doing some housekeeping. What you don't want to do is to let this runaway situation continue unabated. It's an unfortunate fact that far too many ...


5

You can install a mailbox server (presumably Exchange Server) on any domain joined server.


5

In the managers Outlook or OWA turn off the message Read options. If the manager uses Outlook as their primary email client and doesn't want to turn off the message Read options because it will affect his/her messages then have them use OWA to view the employees mailbox and turn off the message Read options in OWA. EDIT In the OWA options you should have ...


4

Don't do it if you're using Mailbox files. If you were using Maildir you could do at least some of the work without shutting the services down. Every email that is delivered, and every IMAP access, will alter the Mailbox files. You may end up with corrupted files. The best you can do is to shut off IMAP and local delivery, while still allowing postfix to ...


4

If you want to get rid of the user's mailbox you want to use Disable and not Remove. The Remove choice actually deletes the user's Active Directory user account (which won't work w/ the RID 500 Administrator account).


4

That also looks about right to me. Do keep in mind that you won't be using all of that at once, so plan for expansion. You can start smaller, but so long as you can add space when you need it you can grow into that size. Another thing Microsoft recommends is to keep your individual database sizes down. Should any one of them blow up, a 1.9TB DB is going to ...


4

to export them to PSTs and archive... http://msexchangeteam.com/archive/2007/04/13/437745.aspx For earlier versions you need to use a utility called Exmerge. Heres a link that says how to use it on 2007 or 2003. http://www.exchangeinbox.com/article.aspx?i=88


3

Exchange 2003 stores mail and other items in an information store. Information stores are stored in storage groups. An exchange server can have 1 or more storage groups. Under exchange standard, an information store has a maximum size of 75 GB and you can have a maximum of 1 Mailbox store and 1 Public Folder Store per Storage Group. You can only have 1 ...


3

Am sure on the postfix system you are running some sort of imap server, you can use imapsync to migrate the mail across to the exchange server while retaining the message flags.


3

If you want Exchange to automatically enforce a limit, I think you have to resort to monitoring the size of the folders. The Exchange Team Blog has an Article about Finding High Item Count Folders using this PowerShell command: Get-Mailbox | Get-MailboxFolderStatistics | Where {$_.ItemsInFolder -gt 5000} | Sort-Object -Property ItemsInFolder -Descending | ...


3

(About eight years ago I migrated more than 50 000 user accounts from an old mail server (running uw-imapd) to a new server 'farm' consisting three servers and running Cyrus. At that time I used my l337 Perl skills for creating a migration script which would login to old server and copy the mails the new server over IMAP one user account at a time. An ...


3

This doesn't really make sense. But if it's not a mistake and you really need to move from a Windows Server 2008 R2 server running Exchange Server 2010 to a Windows Server 2003 one, then... no way. Sorry. Can't be done. You can't install Exchange Server 2010 on Windows Server 2003.


3

If you don't want to give the user any rights to the live mailbox, you can setup a Transport rule to Bcc a separate mailbox for any incoming or outgoing mail for that user. You could then give the Manager access to the separate mailbox.


3

The documentation from Microsoft seems to suggest that disabling a mailbox is a straightforward operation. Unfortunately, there are a few "gotchas". Mailbox Retention When a mailbox is disabled, it is reclassified as a "Disconnected Mailbox". By default, Exchange will retain disconnected mailboxes for 30 days. This is an attribute of the database where the ...


2

You should place a litigation hold on the user's mailbox. http://technet.microsoft.com/en-us/library/ee861123(v=exchg.141).aspx


2

Ah ha! Forget all of the above. You need the Exchange 2007 SP3 media, which explicitly states that it adds support for Windows 7 and 2008 R2. http://www.microsoft.com/de-de/download/details.aspx?id=24111 This is why the link I originally posted stated support for Windows 7, which I found confusing after reading the info you provided.


2

Please try using the Export-Mailbox command rather than New-MailboxExportRequest Export-Mailbox -Identity <MailboxIdParameter> -TargetMailbox <MailboxIdParameter> -TargetFolder <Target_Folder_Name> -ContentKeywords "<String[]>" -AttachmentFilenames "<String[]>" -StartDate "<Month/Day/Year> <Time>" -RecipientKeywords ...


2

The size limit on import is determined by the max message size settings in Exchange. To import larger mails, you will need to set max sizes using Powershell: Set-TransportConfig -MaxSendSize 100MB -MaxReceiveSize 100MB Get-ReceiveConnector | Set-ReceiveConnector -MaxMessageSize 100MB Get-SendConnector | Set-SendConnector -MaxMessageSize 100MB You then ...


2

reconstruct reconstructs cyrus' indexes. While they may survive a move from one machine to another, nothing guarantees that they will. Reconstruct is also idempotent, non-destructive and non-intrusive, so you can safely run it on migrated mailboxes.


2

It is likely the additional items that are exported, such as the recoverable deleted items (dumpster). I would mount the .PST file in your outlook profile and check each folder to see exactly where the additional mail items are. A mailbox export will export EVERYTHING within the mailbox, including items that aren't viewable to the user.


2

It's trivially easy to do that with a UNIX MTA, eg sendmail, if you don't mind each email address being associated with an actual user on your system (make the user with useradd; put the aliases in /etc/aliases and run newaliases). I applaud your decision to get out from under the thumb of cpanel, and I reckon you should be fine doing this if you're OK with ...


2

Voting to close - this is a place for people that at least looked at the documentation. Still an answer: yes, you must defrag. Like all non-trivial databases exchange does not automagically reoptimize disc space usage as this is assumed to be secondary (as new emails come in anyway and the sapce will be reused anyway). You find the same behavior in pretty ...


2

Have you tried replacing the bookmarks.nsf, you should only need to delete it and as long as bookmark.ntf exists a new one should be created when the client is launched. The notes.ini should have the correct mailfile in it before the client is started.


2

I'd be checking the actual mailbox permissions from Outlook. I suspect someone has been granted Owner privileges, which lets them assign further permissions to their staff / colleagues. Rather annoyingly, I haven't yet found a way to get Outlook privs to propogate down through a mailbox (if anyone knows of a way, please tell). Therefore, our IT Security ...


2

Have you checked to see if there is another client (Outlook ) running with that mailbox.. It could have archiving or a rule on it.


2

If you want to know what permissions has been given on a mailbox: Get-MailboxPermission -Identity "shared mailbox name here" If you want to know what permissions a specific user has on a mailbox, use: Get-MailboxPermission -Identity "Shared mailbox name here" -User "The user with permissions" Last but not least, the special "Send on behalf" privilege is ...


2

A user isn't notified when you do a mailbox export, or if you used exmerge. Either way, for 2010 you need to use the new-mailboxExportRequest cmdlet in the Exchange Management Shell and specify a file path to send the PST. For example: New-MailboxExportRequest jsmith -FilePath "\\server\Psts\jsmith.pst" You also need to give the Trusted Exchange ...



Only top voted, non community-wiki answers of a minimum length are eligible