Topics

With Release 5.0.6, a problem with mail not being delivered when sent disconnected, with encryption, to groups in a Directory Catalog only, has been addressed. This regression was introduced in 5.0.3.

This Release Note outlines the specific circumstances of this issue in releases prior to Release 5.0.6, and the steps to work around the problem.

Problem

While working in local (disconnected) mode, you create and send an encrypted email to a group located in the Directory Catalog. The message appears in your local mailbox. However, when you connect to the server to transfer mail, the e-mail message never arrives.

Solution:

This issue occurs only when all of the following conditions are true:

1. You must be working disconnected from your Domino server.

2. You must create and send an e-mail message.

3. The message must be addressed to a group.

4. The group must reside in the local Directory Catalog.

5. The 'Encrypt' Delivery Option must be selected.

This issue occurs because mail goes through a lookup to resolve addresses when being moved into a mail.box. In disconnected mode, there is a second lookup when the mail is moved to the server. This second lookup mistakenly assumes the address is already fully qualified as a result of the first lookup; however, the address is not already fully qualified in the first lookup when using a group out of a Directory Catalog. DirCat does not have the necessary members list, so this can only be resolved at the second lookup. So, when you connect the group name is not expanded and Notes attempts to encrypt the group name as if it were a user. This is the cause of the failure. No mailbox is opened in the router and the email message is lost. The sender does not receive a Delivery Failure report.

This is a regression that was introduced in 5.0.3. As a workaround for all 5.0.3 - 5.0.4 users that send encrypted mail by default, you can create a separate directory catalog and include the field "members". These 5.0.3 - 5.0.4 users can then use that directory catalog. For 5.0.5 users, please be advised that this problem can exist undetected and can only be fixed by upgrading to the 5.0.6 client.