Questions[mailbox](server)

I'm experimenting with Exchange 2013. After importing my mailbox using

 New-MailboxImportRequest -FilePath \\path\import.pst -Mailbox test

I get the message, that importging completed with errors. With

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics -IncludeReport | fl >report.txt

I can see, that TooManyLargeItemsPermanentException is thrown. I have 4 mails, which are too big.

I saw that I can controll how many large items can be skipped by using

-LargeItemLimit -AcceptLargeDataLoss

But does anybody know what I have to do to import everything? I want to have those large eMails in my mailbox.

I'm reading Learning Exchange Server 2003 by Boswell, and there's a section in there that mentions that a disabled account in AD cannot receive email and that it will be bounced back. Currently, what usually happens when a person leaves our company is that the account gets disabled, moved to an archive OU, and the email is forwarded on the Exchange General tab to someone else. It appears to have been working all this time, but I'm wondering why the book would say otherwise... We are using a single Exchange 2003 SP2 server.

Under what circumstances would a disabled user account cease to receive email?

Having a hard time migrating user mailboxes across 2 forests.
I've set up ADMT 3.2, No dns issues and fully route-able between the domains etc.

Have come to migrate user mailboxes and the exchange shell just comes back with ...

[PS] C:>New-MoveRequest -Identity "username" -TargetDatabase "maildb"
-RemoteGlobalCatalog 'gdc.doman.local' -RemoteCredential (get-credential)
-TargetDeliveryDomain 'sourcedomain.local'

Parameter set cannot be resolved using the specified named parameters. + CategoryInfo : InvalidArgument: (:) [New-MoveRequest], ParameterBindingException + FullyQualifiedErrorId : AmbiguousParameterSet,New-MoveRequest

We are running a mixed environment (windows server 2003 and up with exchange 2003 and exchange 2010 (different servers obviously)) as a source domain and full Server 2008 R2 servers in the target domain with only 1 exchange 2010 server.

We have ran this command on the Exchange 2010 server on the target domain and when asked giving the credentials of an admin in source domain in the format : sourcedomain\source_administrator

Any help would be greatly appreciated

Thanks

Rhys

In Exchange 2010 we have found that users are not able to access their mailbox once they hit their storage quota. This is not what we want: we want them to receive a warning, but still be able to get in so that they can clean up their mailbbox, and thus be able to send and receive again.

In the particular instance we encountered today, management approved increasing this user's quota, however once this was done they were unable to access their mailbox. Running the cmdlet Get-MailboxStatistics shows that StorageLimitStatus is MailboxDisabled.

Is there a way to prevent this? Also, now that we've upped the quota, how do we re-enable the maailbox? I read somewhere that you had to wait 2 hours; this is not really acceptable, is there no way to manually re-enable it, without rebooting or restarting any roles? (e.g. without causing a disruption to all the other users).

UPDATE: A colleague has pointed me in the direction of this Technet article. However, I'm not able to determine whether this applies to Exchange 2010, and it still doesn't address the issue of forcing a manual refresh without restarting the mailbox database.

I'm looking for a solution to save automatically attachments of an e-mail for a specific mailbox on an network drive. Mails are stored on cyrus imap server.

Does anyone know a script or something like this. Maybe there is a way to do this with sieve?!?

I searched on the web, but didn't find anything.

Thanks in advance!