When migrating mailboxes to Exchange 2013, you can run into an error the regarding maximum number of bad items. This causes the import to fail:
Error code: -2146233088
This mailbox exceeded the maximum number of corrupted items that were specified for this move request.
The message exceeds the maximum allowed size for submission to the target mailbox.
A bad item can be one whose size is a bit large. The New-MailboxImportRequest commandlet can be called with the -BadItemLimit option, specifying a number of items> when using that option you must also specify the -AcceptLargeDataLoss option. For example, to import a mailbox called john.doe using a pst of john.doe.pst, the command would look as follows:
New-MailboxImportRequest -Mailbox john.doe -FilePath "\\myserver\E$\john.doe.pst" -BadItemLimit 1000000 -AcceptLargeDataLoss
If you have a number of mailboxes that have already failed, use the Get-MailboxImportRequest commandlet and pipe the items that match the Failed Status setting to a Set-MailboxImportRequest option defining a larger -BadItemLimit setting as follows:
Get-MailboxImportRequest -Status Failed | Set-MailboxImportRequest -BadItemLimit 1000000
krypted April 30th, 2014
Posted In: Microsoft Exchange Server
baditemlimit, Exchange 2013, Microsoft Exchange
There are a lot of environments that standardize mail signatures. In Exchange 2010 you can now automatically assign users a signature based on a user’s Active Directory information, thus allowing en masse standardization of signatures. To do so is pretty straight forward, first open the Exchange Management Console and browse to the Organization Configuration. Then click on Hub Transport and then on Transport Rules. Next, click New to create a new transport rule. Here you can build an organizational signature based on user’s Active Directory attributes.
You can provide some text and then any of the attributes that you see fit by wrapping them in the standard double percentage signs (%%). In the following, we provide displayName, Title and Department:
Or, if display names are not correctly formatted (in some organizations they aren’t), you can use first name followed by last name and then a line with the email address (%%mail%%):
To see a list of all of the attributes available, use ADSI Edit. You can access ADSI Edit by opening adsiedit.msc (Start > Run > adsiedit.msc). In 2008, ADSI Edit is installed automatically when the Active Directory Domain Services role is installed, so simply run it from any existing domain controller. Once open, browse to the domain and then to CN=Users. From here, you’ll see the attributes defined in the schema.
krypted April 23rd, 2011
Posted In: Microsoft Exchange Server, Windows Server
Active Directory, attributes, default, exchange management console, hub transport, mail signatures, Microsoft Exchange, standard email signatures, transport rules
So ordb.org has been dead for awhile. If you had an inactive server that was using ordb.org as your Realtime Black-List server on that box and you bring it back up then you won’t accept email from anyone any more. Reason being is that every time your server goes to receive an email and does a lookup on an RBL if it cannot reach the RBL then it will receive no email. Furthermore if your server cannot communicate with the RBL server then you will reject mail. So while RBLs will save you from massive amounts of spam they can actually be used to attack your server. For example, the DNS server you use as a lookup – if someone were to put a man-in-the-middle or poison your capacity to communicate with that server – and you were using the DNS name of an RBL then you would essentially stop receiving mail. It’s a back-handed way of performing a Denial of Service attack, but still a way to do so. So your ability to receive mail becomes contingent upon the security of all up-stream RBLs since each message gets checked against each RBL database…
krypted September 5th, 2008
Posted In: Mac OS X Server, Microsoft Exchange Server, Windows Server
Mac OS X Server, Mail Server, Microsoft Exchange, MTA
I originally posted this at http://www.318.com/TechJournal
Entourage 2004 has more options than Outlook 2001 but also does not communicate over MAPI but instead over WebDAV (OWA).
The Graphical User Interface (GUI) level changes are too numerous to review. A conversion from Outlook 2001 to Entourage 2004 requires retooling the workforce for the new application. Schedules, cached email addresses, signatures and other settings will be lost during the migration, but mail, contacts, calendars, to-do items and tasks should survive the migration.
Once common theme across the two is wasted resources. Outlook 2001 required OS 9 to run in OS X. Entourage 2004 requires Rosetta to run in OS X. Both waste a considerable amount of resources. However, both are the only supported clients for Microsoft Exchange for the Mac platform. One note about a possible Exchange 2007 upgrade is that you will loose your free CAL licensing for Entourage. If you read the EULA you no longer receive free Entourage licenses per CAL of Exchange 2007.
krypted May 27th, 2005
Posted In: Mac OS X, Microsoft Exchange Server
Entourage 2004, Exchange, Microsoft Exchange, Microsoft Exchange Server