rom Steve Goodman:

Other links:

In Exchange 2010 there is actually somewhere to publish these settings – and once configured your documentation won’t need to be updated if the server details change. You’ll find these settings by logging into OWA, and choosing Options. The link ”Settings for POP, IMAP, and SMTP access…” should be shown on the default ”My Account” page:

By default, nothing will be listed if you click the link:


To configure these links, it’s a fairly straightforward process. Before you begin, you need to know what the settings should be and in the case of the SMTP settings, which receive connector on which Hub Transport this relates to.

First, you configure the Client Access servers for the POP and IMAP settings, using the Set-POPSettings and Set-IMAPSettings cmdlets with the -ExternalConnectionSettings parameter.

For each protocol you specify a colon-separated list of values for the ExternalConnectionSettings. For POP3 with TLS, this might be ”” or POP3 with SSL might be ””. IMAP with TLS might be ”” and IMAP with SSL might be ””.

Here’s a quick example of the commands against my test setup:

Set-POPSettings -ExternalConnectionSettings "" 
Set-IMAPSettings -ExternalConnectionSettings ""

It’s important to remember, you need to run the command on all Client Access servers users will access.

Next, you need to allow the receive connector that you want ”published” to advertise it’s settings. You do this with the Set-ReceiveConnector cmdlet specifying the -AdvertiseClientSettings:$true parameter and value.

In my example, I want to advertise the port 587 ”client” receive connector on my Hub Transport server:

Set-ReceiveConnector -Identity "hubtransport\Client HUBTRANSPORT" -AdvertiseClientSettings:$true

Finally, run iisreset to restart IIS on each Client Access Server, the log back into OWA (well, ECP) and test the ”Settings for POP, IMAP, and SMTP access…”  link again. It should now show the settings specified:

For further reading check out Set-IMAPSettings, Set-POPSettings and Set-ReceiveConnector.

(Just a footnote- thanks to Jag at Microsoft for providing this information)

Tagged with:

Some IMAP-clients (Thunderbird in some cases) have problem with corrupt attachments using Exchange IMAP.

One possible reason is how Exchange delivers MIME-message to users. In exchange 2003 you could set an option on IMAP – ”Fast message retrieval” and it makes IMAP answer faster to clients with MIME-messages. In Exchange 2010 this option is set thru powershell with Set-imapsettings and it is now called ”EnableExactRFC822Size”. When this is enabled it will give IMAP-clients an exact size of each MIME-message content and not an approximate size as default. Old IMAP-clients can not handle an approximate size of MIME messages and there for shows messages as corrupt. As Marek writes below: ”MS Exchange violates RFC and provides only approximate size of the message for ‘performance reasons'”.

A plot from technet and powershell-command ”set-imapsettings”.

Set-imapsetting -EnableExactRFC822Size $true|$false
The EnableExactRFC822Size parameter calculates the exact size of each MIME message that can be retrieved from the server. When you set this parameter to $true, the exact size of MIME messages stored on the Exchange server is available to POP3 or IMAP4 client programs that rely on knowing the exact size of each MIME message.
This parameter is set to $false by default. If you don’t set this option to $true, the size of each MIME message that the Exchange server returns to POP3 and IMAP4 client programs may be slightly different than the exact size of the message. Because setting this option to $true can negatively affect performance, you should only use this option if many of your users are using a client that requires knowing the exact size of MIME messages.

A post by Marek Vitek 2010-01-28
There are several reasons and also few possible solutions for solving this issue.
– MS Exchange violates RFC and provides only approximate size of the message for ”performance reasons”
– I saw also other mail servers providing incorrect RFC822.SIZE value

So sticking with this value is not a good idea. It is also discouraged by IETF author in RFC 2683 section 3.4.5.

– in Exchange disable ”Fast message retrieval” function/RFC violation. But it will have performance implications. (In exchange 2010 this is same as -EnableExactRFC822Size on set-imapsettings)
– follow RFC 2683 recommendations and in Thunderbird fix the code and use message size provided by ”FETCH RFC822.SIZE” command only for informational purposes. For message size validation and possibly truncation use e.g. size reported by ”FETCH RFC822” as it seems to be correct value all the time.

Thunderbird: E-mail attachments are corrupted and and images partially load

Tagged with:
Exchange 2010, IMAP, Thunderbird


In Thunderbird, there is a problem where attachments on received e-mail messages are corrupted, and images in e-mail messages only partially load. This is caused by Exchange reporting attachment sizes incorrectly, so when Thunderbird breaks the message into chunks it doesn’t download all of them.

Exchange has a bug in the IMAP server implementation that reports the wrong size for messages and attachments. There is a workaround that causes Thunderbird to ignore the erroneous information.

Truncated Attachment Problem
Warning: This may result in any tags you have set disappearing. If you use Thunderbird’s tagging you should back up your profile before doing the following (your profile is in the ~/.mozilla-thunderbird directory by default).

  • From the Edit menu, select Preferences
  • Select the Advanced tab
  • Click the Config Editor button
  • Set the filter to mail.server.default.fetch_by_chunks. The default value should be true
  • Double-click the mail.server.default.fetch_by_chunks preference. It should turn bold, and the value should now read false

Thunderbird will now download attachments as one block, avoiding the bad attachment size problem.

Tagged with:
Mailbox Server Role: 

1.Mailbox\Public Folder Database Status – Get-MailboxDatabase –Server “Name of the Server” –Status | ft Name, Mounted
2.Service Health – Test-ServiceHealth –Server “Name of the Server”
3.Storage group copy status – Get-StorageGroupCopyStatus –Server “Name of the Server”
4.Backup Status – Get-MailboxDatabase –Server “Name of the Server” –Status | ft Name, lastfullbackup, lastincrementalbackup
5.MAPI Connectivity – Test-MapiConnectivity
6.Replication status – Test-ReplicationStatus
7.Cluster Mailbox Status – Get-ClusterMailboxServer 

Client Access Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.OWA Connectivity – Test-OWACConnectivity
3.Active Sync Connectivity – Test-ActiveSyncConnectivity
4.POP3\IMAP4 Connectivity –Test-POP\IMAPConnectivity

Hub Transport Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.Queue Status – Get-Queue –Server “Name of the Server”
3.Mail Flow –Test-Mailflow

Unified Messaging Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.UM Connectivity Test – Test-UMConnectivity -ListenPort 5060/2061
3.Active Call Status – Get-UMActiveCalls

Edge Transport Server:
1.Service Health – Test-ServiceHealth –Server “Name of the Server”
2.Queue Status – Get-Queue –Server “Name of the Server”
3.Mail Flow – Test-Mailflow
4.Edge Synchronization –Test-EdgeSynchronization

Additional Note: Event Log info on corresponding server can be found out by: –Get-EventLog Application\System |Where { $_.Type –eq “erro” }

Tagged with:

Exchange 2010 no longer has the setting. Exchange 2003 IMAP4 client use the streaming store (.stm file) for reading and writing mailbox data that is stored as MIME content. If you use the Move Mailbox functionality in Exchange System Manager or Active Directory Users and Computers to move a mailbox that is accessed by an IMAP4 client, the data in the moved mailbox is promoted into the Extensible Storage Engine store (.edb file), and the content is converted from MIME content to MAPI content. When the IMAP4 client logs on, exact message sizes are calculated, and MAPI-to-MIME conversion of the mailbox data occurs in memory and on the disk of the server.
Fast message retrieval improves performance of the MAPI-to-MIME conversion.

Exchange 2010 no longer use .stm file.

More information

Enable Fast Message Retrieval for IMAP4

Understanding the Exchange 2010 Store

Answer from Jerome Xiong

Support for fast message retrieval

Fetching the body of an e-mail message was also possible in Exchange server 2003 SP2, but has been improved further with Exchange Server 2007. For example, you no longer need to select Mark for download or click Get the rest of this message, instead this will happen automatically in the background and thereby make the end-user experience even better.


Tagged with: