04 August 2018

Exchange: How to reliably determine that a user is logged into mailbox?

Sometimes (for example while migration users are from another email system) there is a need for reliable determination that a user is logged into the mailbox (using Outlook or OWA).

The simplest answer is mailbox's lastlogontime (Get-MailboxStatistics). But it turnes out to be not quite true.
Attention! The attribute "LastLogonTime" of user's mailbox filled and updated when another user opens user's calendar.

Finally, I found 4 criterias which help to reliably determine that a user is logged into the mailbox.

  1. "lastlogontime" (Get-MailboxStatistics) - necessary but not sufficient attribute.
  2. "Languages" (Get-Mailbox) - this attribute filled when user entered into OWA and sometimes filled when entered into Outlook.
  3. "WorkingHoursTimeZone" (Get-MailboxCalendarConfiguration) - this attribute filled when user entered into OWA and sometimes filled when entered into Outlook. Deffault value - "Pacific Standard Time", so you can use it only if users are in a different time zone.
  4. "Quick Step Settings" (Get-MailboxFolderStatistics) - this is not an attribute, it is a checking for the presence of a folder "Quick Step Settings" in the mailbox, because it appears only when you open/configure Outlook.

08 July 2018

Exchange 2016: Issue of breaking email address in angle brackets

Recently noticed the unusual behavior (an issue) of Microsoft Exchange 2016 when displaying email addresses.
If in the body of an email (Content/Header section) specify an email address (From, To or Cc headers) twice, where the second time is in angle brackets, the address will be broken. The part of the address after the first character @ moves to the address in brackets, thereby preventing the possibility of an answer to this email.

I assume that the function that should extract the correct email addresses from the headers does not work correctly.

Several tests

Original email address (that used while sending)The final email address (OWA, Outlook)
administrator@test.local <administrator@test.local>"administrator@" <test.local administrator@test.local>
administrator@_ <administrator@test.local>administrator@ <_ administrator@test.local>
administrator@domain<administrator@test.local>administrator@ <domainadministrator@test.local>
administrator@><administrator@test.local><administrator@>
<administrator@><administrator@test.local><administrator@>
<@administrator@><administrator@test.local><@administrator@><administrator@test.local>
administrator@<administrator@test.local><administrator@>
<script>@><administrator@test.local><script>
administrator@test.local@ <administrator@test.local>"administrator@" <test.local@administrator@test.local>

24 January 2018

Windows 10: DNS Client load CPU in case of big hosts file

After installing Fall Creators Update (KB4058043, KB4057247, KB4055237, KB4055994) on Windows 10 Pro 1709 (16299.125) I noticed a long delay in the opening of websites.

Symptoms

  • The DNS Client service load is about 25% CPU.
  • You can't open any website and get access to the internet at all for several minutes.

11 January 2018

Microsoft Office: How to fix double slash autocorrection in links

Some applications (web servers, etc.) support hyperlinks with double-slash (//) after specifying the protocol (http://, ftp://, etc.).
IBM Lotus Domino is such an application. A link "notes://server/1111111111//2222222222/" is correct.

During the migration from the IBM Lotus Domino mail system to Microsoft Exchange, it turned out that all Microsoft Office applications (Outlook in particular) correct links (even in incoming emails) with two empty slashes "//" for a single slash "/" automatically. We failed to find a solution in the Internet to change this behavior.

26 December 2017

Outlook 2013/2016: Types of connections to Microsoft Exchange

In this post, I would like to make out the types of Microsoft Outlook 2013/2016 connections to the Microsoft Exchange Server 2016, depending on the type of mailbox (personal, archive, shared or Public Folders).
There are 2 main types of connections: cached and online. The online mode is simple, but the cache mode is more complex. To learrn more what is Cached Mode go to TechNet.

07 December 2017

Exchange 2016: setup tried to install wrong CU version

Recently faced an interesting feature on the start at installation of Cumulative Update.

When starting CU setup from the command line, the installation of the current version can start.

An example:
[PS] C:\Windows\system32>cd d:\
[PS] D:\>setup /PrepareSchema
Microsoft Exchange Server 2016 Cumulative Update 6 Unattended Setup


15 November 2017

Exchange 2016: How to force it use UTF-8 encoding

In order to minimize the number of possible problems with message encode (e.g. "?" instead of Cyrillic symbols), I recommend to set up an unified universal encoding in the Exchange - UTF-8.

Quotation from the TechNet article regarding choosing encoding for outgoing emails:
"Exchange uses the order of precedence as described in the following list to determine the message encoding options for outgoing messages sent to recipients outside the Exchange organization"

1. Mail user or mail contact settings

There are no specific attributes to determine encoding for MailContact and MailUser.

14 October 2017

Exchange 2016: How many attachments may be in the email?

Have you ever wondered how many files you may attach to an email?
For Microsoft Exchange 2016 (CU6) is 249 (250 MIME parts). And it is an unchangeable parameter. Not so much, isn't it?

MaxBodyPartsTotal
This limit specifies the maximum number of message parts that can be used in a MIME multipart message. The value is 250.
https://technet.microsoft.com/en-us/library/bb397226(v=exchg.150).aspx
In the RFCs I can't find any mention of maximum number of MIME parts or attachments. Also I found information that in Gmail there is no limitation to number of files attached, only message size (300 files was delivered perfectly). Feel free to correct me if I'm wrong.

23 August 2017

Exchange 2016: How to move system mailboxes

Exchange 2016 has 5 types of system mailboxes: Discovery Search (1 mbx), Arbitration (6 mbx), AuditLog (1 mbx), Public Folder (not created by default) and Monitoring (the number depends on the number of databases). All of them are necessary for full-fledged Exchange's work.

You can't delete the first mailbox database (or another one) until all system mailboxes migrate to a new database.

12 July 2017

Brief of email anti-spoofing technologies: SPF, DKIM, DMARC, SIDF, DK, ADSP

For a few years unhurriedly I have been discovering features to protect emails from spoofing. Here I briefly collect information about all current standards, their functionality and an example with one main domain and two subdomains. It is not a complete guide, please read the RFCs and special guides for each standard.

Standards

Acronym
Definition
Official website
RFC
IETF Status
Short description
SPF
Sender Policy Framework
Standards Track RFC
Defines who (which servers) could send emails from domain and what to do with “bad” emails.
Works with «RFC5321.MailFrom» and «HELO» identities.
DKIM
Domain Keys Identified Message
Standards Track RFC
Sign an email by private key to identify the sender.
DMARC
Domain-based Message Authentication, Reporting, and Conformance
Informational RFC, Working Group
The policy that unites the SPF and DKIM to define what should do receivers with «bad» emails.
SIDF
Sender ID Framework
-
Experimental (2006)
Analog SPF, but works with «RFC5321.MailFrom» and «RFC5322.From».
ADSP
Author Domain Signing Practices
-
Historic (2014)
Extension to DKIM allowing domain owner to specify whether or not they signed all outgoing mail.
DK
DomainKeys
Historic
Analog of DKIM. This standard was superseded by DKIM (RFC4871).