Sunday, 11 November 2018

Domino 10 - New Administration Feature: Document Deletion Logging (2)


As I mentioned in my blog post Domino 10 - New Administration Feature: Document Deletion Logging there is a new server compact option available in Domino 10 to enable logging of data about deleted documents in databases that can be specified. The deletion logging data is logged to entries in deletion log files added to the IBM_TECHNICAL_SUPPORT directory on the Domino Server. In my previous blog post I did not mention the possibility to log (field) items. Administrators can log up to four field values in a deleted document to help identify these documents. The items are specified when Administrators enable deletion logging for a specific database. Although Administrators can specify more than four field values only the first four that are found are shown in the log entries. Below an example enabling deletion logging in a mail database including four items.


The results of enabling deletion logging is that when documents are deleted from a specific database entries are added to the current deletion log file, delete.log. When the server is restarted a new deletion log file is created. Old deletion log files are renamed to delete_<servername>_yyyy_mm_dd@hh_mm_ss.log. As mentioned before the log files are stored in the IBM_TECHNICAL_SUPPORT directory. Below some examples from the log file including the logged (field) items.


delete_ICEDEARTH_2018_11_09@18_15_18.log
"20181109T183422,40+01","mail\joldenbu.nsf","C125832B:005DADBF","nserver","CN=Johnny Oldenburger/O=ALM","SOFT","0001","5CED9FCF:EF17A075C1258340:006074A4","Form","4","Memo","Subject","22","Items Deletion Logging","DeliveredDate","19","09-11-2018 18:33:33"
"20181109T183427,71+01","mail\joldenbu.nsf","C125832B:005DADBF","nserver","CN=Johnny Oldenburger/O=ALM","SOFT","0001","54060598:74EB0F79C1258340:00606893","Form","4","Memo","Subject","16","Deletion Logging","DeliveredDate","19","09-11-2018 18:33:02"

Next I will setup the nshDelLog - Domino Deletion Log Annotation and Backup V 0.9.0 database by IBM Champion Daniel Nashed. For more information see the blog post nshDelLog - Domino Deletion Log Annotation and Backup V 0.9.0. In one of my next blog post, I will describe my experience of this database. Thanks for sharing Daniel!

Friday, 9 November 2018

Domino 10 - Synchronize Database Replicas - New Option Replicate Command


This last blog post concerning the new IBM Domino 10 Administrator features  is meant purely for my own documentation in case I need the new replicate command in the near future. In IBM Domino 10 there is a new option for the Replicate command for Domino Administrators, -F, to force a full database replication when replicas of a database get out of sync. The replication takes place on the side and allows users to continue to see replication updates during the full replication. Administrators can use  the -L argument to log information about the documents (notes) that would replicate if the new option -F is used but without actually performing the replication. Until now the only option for Administrators to perform a full replication of content was by clearing the replication history. Be aware that for large databases a full replication can take time and delay the replication of new updates until it is complete. For example if the replication history of a mail file is cleared the mail user might not see new mail until the full replication completes.

To force a full replication Administrators can now use the following server command: replicate <server> <database> -F.
Example: replicate MS-DOMINO10/ALM mail\jdomino.nsf -F

Administrators can use the -L option to log details about the documents (notes) that would replicate if the -F option is used but without actually performing the replication. For example: replicate MS-DOMINO10/ALM mail\jdomino.nsf -L

Since I currently not have any replica's out of sync I don't get all the output as mentioned in the IBM documentation as shown below. Based on the new replicate command -F and the -L option to log details the output will look something like this on the Domino console.

[17F8:0002-1028] NoteRepl: CN=Mail\O=MSDOMINO10!!mail/jdomino.nsf to mail/jdomino.nsf Since 07/27/2018
 Replicating from remote replica (jdomino) to local replica (pull). Since = The replication history from 
[17F8:0002-1028]  07-11-2018 08:28:57 Starting replication with server Mail\MSDOMINO10
[17F8:0002-1028]  07-11-2018 08:28:57 Pulling mail\jdomino.nsf from Mail\MSDOMINO10 mail/jdomino.nsf
[17F8:0002-1028] NoteRepl: UNID 7235FD43:BB0874BA:852582A2:0052CF6C Cls 1
UNID and Cls = NoteClass
[17F8:0002-1028] Src: NID A96 SN 2 ST 07-11-2018 08:15:07  Mod: 07-11-2018 8:15:07
Source note info (in this case the source is the remote replica), NID = NoteID, SN = Sequence number
[17F8:0002-1028] Dest: NID 0 SN 0 ST Did not repl
Destination note info. "Did not repl" means that it should have replicated in the past, but the [17F8:0002-1028] NoteRepl: mail/jdomino.nsf to CN=Mail\O=MSDOMINO10!!mail/jdomino.nsf Since 07-11-2018 Replicating from local to remote. Since = Replication history from last push
[17F8:0002-1028] 07-11-2018 08:28:57  Pushing mail/jdomino.nsf to Mail\MSDOMINO10 mail/jdomino.nsf
[[17F8:0002-1028] NoteRepl: UNID 29BD9D7B:04808407:852582A2:0052CF6E Cls 1
[17F8:0002-1028] Src: NID A9E SN 2 ST 07-11-2018 08:28:43  Mod: 07-11-2018 08:28:43
[17F8:0002-1028] Dest: NID A9E SN 1 ST 12-10-2018 11:04:35 Waiting to repl
"Waiting to repl" means that this note will replicate the next time the databases replicate. [17F8:0002-1028] 07-11-2018 08:28:57 Finished replication with server Mail\Renovations
[17F8:0002-1028] 07-11-2018 08:28:57 AM Database Replicator shutdown

Another great new IBM Domino 10.0 Administrator feature. In my next blog post more about advanced search capabilities and query definitions in Notes databases using LotusScript.

Tuesday, 6 November 2018

Domino 10 - Programatically Schedule Mail Using LotusScript


In my previous blog post Domino 10 - New Administrator Feature to Push to Notes Clients: Scheduled Messages I described the new Domino 10 feature scheduled delivery of mail messages. As mentioned in the blog post the new Domino 10 Mail Servers supports scheduled delivery of mail messages. For example a user can compose a new mail message during the weekend and schedule the delivery of the email to be sent during the next work week. Scheduled messages are stored in mail.box on the sender's Mail Server. The router delivers or routes the messages at the scheduled time. Scheduled mail is enabled on a Domino 10 Server by default. In the Server Configuration Settings document in the Domino directory it can be disabled by the Administrator.
Scheduled messages are supported for Notes client users with mail files that are upgraded to he Notes 10 Mail Template (mail10.ntf). The feature is not supported for IBM iNotes, IBM Verse or IBM Traveler clients.
In this blog post I will describe how you can programatically schedule mail using LotusScript.


Scheduling mail programatically
To programatically schedule mail messages you must use the Summary DateTime item $SendAt to cause a message to be scheduled. Below a basic example using a simple function which is called form an Action Button on a Notes form.

A. Function ScheduledMail
In the Funtion ScheduledMail I use a Variant sendTime which indicates when the mail should be sent. The value of the Variant sendTime in the Function ScheduledMail is replaced in the field $SendAt to cause the message to be scheduled on the Domino Server.

Function ScheduledMail(note As NotesDocument)
Dim session As New NotesSession
Dim db As NotesDatabase
Dim memo As NotesDocument
Dim body As NotesRichTextItem
Dim sendTime As Variant
Dim linkDoc As NotesDocument
Dim sendTo As String
Set db = session.CurrentDatabase
Set memo = db.CreateDocument
Call memo.ReplaceItemValue("Form", "Memo")
Call memo.ReplaceItemValue("Subject", "Review IT Ticket Solution")
sendTo = note.mailuser(0)
sendTime = Today + 8 + TimeNumber(8, 0, 0)
Call memo.ReplaceItemValue("$SendAt", sendTime)
Call memo.ReplaceItemValue("SendTo", sendTo)
Set body = memo.CreateRichTextItem("Body")
Call body.Appendtext("Please review this IT Ticket: ")
Call body.Appenddoclink(linkDoc, "", "")
body.Update
Call memo.Send(False)
End Function

B. Mail.Box
If the user selects the Action Button on the Notes Form the function ScheduledMail is called and the mail is not send immediately but is placed in the Mail.Box on the Server as a Pending Message.


By using sendTime = Today + 8 + TimeNumber(8, 0, 0) in the Function ScheduledMail the Scheduled Time for the Mail Message is set on 14-11-2018 08:00:00.


The above function can be easily adjusted so that the users can enter the scheduled date and time themselves. Another great new feature in Domino 10. In my next blog post more about scheduling messages using @Formula.

Friday, 2 November 2018

Getting Started with IBM Domino Mobile Apps 1.0


As most of you may already know since a few days IBM Domino Mobile Apps 1.0 Beta is available for testing. IBM Domino Mobile Apps is the Notes client that you already know for working with your applications – but on, and optimized for, the iPad. For getting started with IBM Domino Mobile Apps 1.0 Beta see this IBM Support Document to quickly get up and running with IBM Domino Mobile Apps 1.0 Beta. For more information see also IBM Domino Mobile Apps - IBM Notes Applications on your iPad.
There are already some very interesting blog post regarding first impressions and tips. I recommend to read the blog posts IBM Domino Mobile Apps BETA is available and Quick-Tip: Remove Tile from IDMA Recent Apps by Oliver Busse.



I will add more info to this blog post as soon as more information becomes available regarding IBM Domino Mobile Apps.

Notes 10 - Forward Multiple Messages as EML Attachments


One of the cool new mail features in IBM Notes 10.0 concerns the EML attachments feature. In Notes 10.0 users can select multiple messages in their Notes Inbox and forward them as .eml attachments. EML is a file extension for an e-mail message saved to a file in the MIME RFC 822 standard format. The primary purpose of creating a .eml file is for storing the files offline and to allow forwarding of e-mail messages and their content.
This new feature in Notes 10.0 allows users to keep multiple messages separate rather than having them run together in the forwarded message.

Forward messages as .eml
To use the new Notes 10.0 feature open the Inbox and select one or more messages to forward. Next select Forward - Forward as Attachments.


Next a new IBM Notes Email message is opened with the emails attached as .eml attachments.


Result
When the recipients of the email with the attached .emal attachments receive the message  and open the attachments in the email the formatting and structure of the IBM Notes Email message stays in tact regardless of the mail client the recipients use.


If an Email message that a user is forwarding contains attachments, the attachments are also included in the .eml attachment for the Email message. I tested this an it works like a charm. Another great feature in Notes 10.

Notes 10 - Default Enabled Notes Client Preferences


Today I started to look at the new features in Notes 10 in more detail. Initially a number of preferences are enabled by default for new installations of IBM Notes 10. As an IBM Domino Administrator I am not a big proponent of standard enabled features in new releases or installations. I prefer to decide myself, based on our company policies, which (new) preferences should be enabled for the users in the Notes Client. However, to be more specific, there are three preferences enabled by default in Notes 10. A small remark applies here, namely these enhancements do require the IBM Notes 10 mail template (mail10.ntf). Below a shot description of these preferences.

Cancelled Meetings
By default canceled meetings are now shown as canceled in the calendar rather than removed. This by default enabled preference is is set in File - Preferences - Calendar & To Do - Display - Views.

Administrators can change this default setting by using a Mail Policy. Select Calendar and To Do - Display - Process cancelled meetings automatically and select the desired setting.

Delete Calendar Document
By default, when a user deletes a calendar document from their mail the calendar document is deleted automatically without asking the user to confirm the deletion. This by default enabled preference is set at File - Preferences - Mail - Basics.

Administrators can also change this default setting by using a Mail Policy. Select Mail - Basic - When user deletes a calendar document from any view or folder and select the desired setting.

Mail Rules
By default mail rules run on existing messages. This by default enabled preference is set at File - Preferences - Mail - Basics.

Finally Administrators can change this default setting by using a Mail Policy. Select Mail - Basic - Enable Run Rules on existing mail and select the desired setting.

In my next blog post more about the new Notes 10 features.

Thursday, 1 November 2018

Domino 10 - Automatic Archiving of User ID Vault Documents to Restart ID File Synchronization


In this blog post a small addition to my previous blog post, Domino 10 - ID Vault Scanning. Enabling ID vault scanning allows Administrators to use the query vault console command or the Domino Administrator to add or update ID vault assignments and user ID vault document modification times in Person documents in the Domino directory. Enabling scanning also allows Administrators to manage archived ID vault user documents. When ID passwords on Notes clients and the ID vault become different synchronization of ID information between clients and the ID vault stops.
In Domino 10.0 Administrators can now, as a new Administrator feature, configure automatic archiving of ID vault user documents when this situation occurs for longer than seven days. Archiving renames user documents in the ID vault allowing ID files on clients to be uploaded again to the ID vault. This ensures that the most recent information stored in the local ID file is stored in the ID in the vault. Important is always to have a good backup of the ID Vault.

Enabling automatic archiving of ID vault user documents
Administrators can add the following setting to the server notes.ino to automatically replace the ID file in the ID vault with the current ID on the Notes client when synchronization remains stopped for longer than seven days.
ENABLE_AUTORECOVERY_FROMBADPASSWORD=1


Results of the new notes.ine setting
In case a Notes Client ID vault synchronization fails based on mismatched passwords the mismatch is flagged in the user's ID vault document. Next if more than seven days occur without successful ID vault synchronization the user's ID vault document is archived by renaming it to begin with a tilde (~). Finally at the next ID vault synchronization attempt the ID file is uploaded again from the Notes Client to the ID vault and the passwords are again in sync. The ID file is uploaded to the ID Vault again because the user's ID vault document isn't found due to the previous archiving.

Remark: Mismatched passwords that stops ID synchronization can occur in the situation when an administrator resets a user's password in the ID vault but the user doesn't use the new password on the client. Further the synchronization also stops in case a user changes the password on the client ID and the ID successfully is synchronized to the ID vault. Next the user then uses an older ID file on the same or a different computer that has a different password.

In my next blog post more about the new features in Domino 10.

Monday, 29 October 2018

Domino 10 - ID Vault Scanning


During the past weekend I have looked at some new Administrator features in Domino 10.0. Another new Administrator feature in Domino 10.0 is ID Vault scanning. Enabling ID vault scanning allows Administrators to use the query vault console command or the Domino Administrator to add or update ID vault assignments and user ID vault document modification times in Person documents in the Domino directory. Enabling scanning also allows Administrators to manage archived ID vault user documents.

Enable ID Vault scanning
To enable ID Vault scanning on the Domino server add the following notes.ini setting on the ID Vault administration server: IDV_Enable_Vault_Scan=1.

1. Open the Domino Administrator Client.
2. Select Configuration - Configurations to open the Configurations Document.


3. Select Edit Server Configuration.
4. Select the Tab NOTES,INI Settings
5. Select Set/Modify Parameters
6. Enter the parameter IDV_Enable_Vault_Scan=1 and select Add/Update
7. Select OK.
8. Save the Configurations document.


Scanning the Vault from the command line
Administrators can now use the query vault (qvault) console command to scan ID vaults and update Person documents in the Domino directory with ID vault assignments and last user ID vault document modification time. (The modification time indicates when the last successful ID synchronization occurred). You can also use the command to manage archived user documents in an ID vault.
From the ID Vault Administration server Administrators can use load qvault command with the following optional switches. Without adding switches the command scans all ID Vaults on the server and updates the Person documents of the users found with their ID Vault name and the time the users' ID vault documents were last modified.



Switch Description
-x <vaultname> Scan all documents in specified ID vault and
update directory Person documents with
vault assignments and the time the users' ID
vault documents were last modified.
-x <vaultname> -u <username> Scan specific user document in specific ID
vault and update directory Person document
with the user's vault assignment and the
time the user's ID vault document was last
modified.
-x <vaultname> -u <username> - a Archive a user's ID vault document by
renaming it so that an ID can be uploaded
again from the client to the vault. Used to
resume client-to-vault ID synchronization
that has stopped.
-x <vaultname> -u <username> - r Revert a user's archived ID vault document
to its original name.
-x <vaultname> -u <username> - d Delete a user's archived ID vault document
-x <vaultname> - d Delete all archived user ID vault documents
in a specific ID vault.

Scanning the ID vault from the Domino Administrator
Administrators can also use the Domino Administrator to scan an ID vault to update ID vault assignments and synchronization information in Person documents in the Domino directory. Administrators can update one Person document of update all Person documents.
Remark: Make sure you are registered as Vault Administrator. A vault Administrator assigned to the Auditor role in the Vault database Access Control List can extract an ID from a vault to gain access to a user's encrypted data and can scan the Vault.

Update one Person document
1. From Domino Administrator select People.
2. Select a Person document.
3. Select Tools - ID Vaults - Scan Vault.


Update all the Person documents of users in a specific ID vault
1. From Domino Administrator select Security - ID Vaults.
2. Select the ID Vault document.
3. Click Tools - ID Vaults - Scan Vault

In my next blog post more about the new Domino 10.0 Administrator features.

Saturday, 27 October 2018

Domino 10 - Upgrade ODS Notes Client Local Databases


As a follow up to my previous blog post Domino 10 - Upgrade ODS on Notes Databases, Templates And Mail.Box Files a short addition regrading the upgrade of the ODS of the local database in the Notes 10 Client. By default local databases are not updated when the Notes client is upgraded. Using either the Notes Client, Domino Administrator Client or the Domino Designer Client you can force the client to perform ODS upgrades of all local databases. For most non-essential databases the ODS upgrade will take place in a background process and while a database is upgraded, the end user will not be able to use the database. For essential databases that are in use at the point that an upgrade is attempted the ODS upgrade will be done at the next first time open which will typically occur at client restart. The following NOTES.INI setting performs the upgrade: NSF_UpdateODS=1. With this setting the client will do a one time pass to upgrade local databases using the compact task. In addition,the specific ODS level that is desired can be set. If none is set, ODS53 will be forced.
The steps below for the upgrade of the ODS are based on the use of a Desktop Policy.

1. Desktop Policy
A mentioned, for clients we need to set NSF_UpdateODS=1 in combination with CREATE_R10_DATABASES=1 which lets the client convert to the new ODS. These settings can easily be distributed to all users through a Desktop Policy.
Open the Domino Directory on the Domino server (names.nsf).
Click the People & Groups Tab and open the Settings view.
Click Add Settings, open the Desktop Settings dialog and select the Custom Settings Tab or select and open an existing Desktop Policy and select the Custom Settings Tab.
Select NOTES.INI.


Click Edit List to open the panel that enables you to create a notes.ini variable name and value pair.
Add NSF_UpdateODS=1 and include Enforce.


Next add CREATE_R10_DATABASES=1 and also include Enforce


2. Deploy Policy
Users receive updates to the desktop settings the next time users authenticate with the home server in case the policy settings change and the desktop policy settings are enforced.
In the NOTES.INI file (Notes Program Directory) the new Desktop Policy Setting are added.


Next time the Notes Client is started the upgrade of the local databases to the new ODS will be executed. In the log you can see the following message : 27-10-2018 13:21:33   15 databases had an older NSF ODS version.  11 of those databases were successfully upgraded to a later NSF ODS.


Remark: Another possibility is to set the field Enable upgrade of all local NSFs to latest ODS version in the Desktop Policy document on the Mail Tab under Client Settings if you always want to upgrade to the latest ODS version.


Wednesday, 24 October 2018

Domino 10 - Upgrade ODS on Notes Databases, Templates And Mail.Box Files


The maximum size of databases allowed in Domino 10 has increased to 256 GB. Previously this was 64 GB. In addition the maximum size of folders has increased significantly. To take advantage of the increased database and folder size capacity I upgraded the Notes databases to the Domino 10 On-Disk Structure, ODS 53. There are some points of attention regarding the upgrade to ODS 53. After upgrading the notes databases to ODS 53 an IBM Notes 10 client can open the database on the IBM Domino 10 server and access all the content regardless of database or folder size. An IBM Notes 9 client can open the database without issue only if the database and folder sizes are within the IBM Notes 9 size limits (64 GB). Further up to 64 GB of database data can replicate to a target replica on any version of an IBM Domino server or IBM Notes client. To replicate more than 64 GB of data the target replica must be on an IBM Domino 10 server or IBM Notes 10 client and must be upgraded to ODS 53. Therefore it is very important to upgrade the ODS to ODS53. Below the steps I performed to upgrade all databases, templates and mail.box files to ODS53 after the upgrade to Domino 10. I used the compact switch "-upgrade". "-upgrade" Upgrades databases created with older DB classes to the most recent class.

1. Domino Server - NOTES.INI
First I added the parameter Create_R10_Databases=1 to the NOTES.INI file.


In addition it is extremely important that the Transaction Logging is enabled on the Domino server! Enabling transaction logging can improve server performance in most cases. Transaction logging saves processing time because it allows Domino to defer database updates to disk during periods of high server activity. Transactions are recorded sequentially in the log files, which is much quicker than database updates to random, non-sequential parts of a disk. Because the transactions are already recorded, Domino can safely defer database updates until a period of low server activity.

In case Transaction Logging is not enabled on the Domino Server you can enable Transaction Logging by following the steps below.

Ensure that all databases to be logged reside in the Domino data directory, either at the root or in subdirectories.
From the Domino Administrator, click the Configuration tab.
In the "Use Directory on" field, choose the server's Domino Directory.
Click Server Configuration, and then click Current Server Document.
Click the Transaction Logging Tab.
Complete all fields on the Transaction Logging Tab and then save the document.


For more information regarding Transaction Logging on Domino Server see the IBM Support document Transaction Logging on Domino Servers.

2. Upgrade ODS
Next shut down the Domino Server en start the Command Prompt. Navigate to Program Directory of Domino and enter the following command: ncompact -ODS -* -upgrade.


Remarks: In this case I use -ODS -* instead of compact -c because I want to upgrade all Notes databases, Templates and Mail.Box files and not just the Notes databases. -ODS -* will upgrade Notes databases, Templates and Mail.Box files which have an older ODS and compact -c will only compact / upgrade all Notes database except the Templates and Mail.Box files. The upgrade can take some time but runs without any problems on an IBM Domino 10 server. Below an example of an upgrade for one database.


Yesterday, based on a conversation on Twitter, I also received this tip from from HCL CWP Support using ndbmt.

Sunday, 21 October 2018

Domino 10 - New Administrator Feature - Automatic Dead Mail Processing


In my previous blog posts I described already some really cool new Administrator features in Domino 10. In this blog post a brief description of the new Domino 10 Administrator feature Automatic Dead Mail Processing. Dead mail occurs when the router can't deliver or transfer a message to the intended recipient or a non-delivery report to the sender. Before Domino 10, if administrators wanted to retry sending dead mail, they had t perform this manually in the Administrator Client. Further dead mail stayed in mail.box until an administrator deleted it. Now in Domino 10 administrators can configure the router to automatically retry delivery of dead mail and if unsuccessful delete it from mail.box after a specified number of retry attempts.
Remark: In other to enable automatically dead mail processing on the Domino Mail server it is necessary to upgrade the Domino Directory to the Domino 10 template.

If automatically dead mail processing is enabled on the Domino 10 server and the router detects a dead message in mail.box the following steps will be performed:
  1. If the allowed number of delivery attempts has been reached the router deletes the dead message and processing ends. If the administrator has set allowed delivery attempts to 0, the dead message is deleted without retrying delivery. 
  2. The router attempts to deliver the original message to the recipient. If successful processing ends. Note: Step 2 is skipped when the intended recipient is from an external domain outside of your company. 
  3. The router attempts to deliver a non-delivery report to the sender. If successful processing ends.
  4. The router waits the specified retry interval then begins with step 1 again.
Configure automatically dead mail processing
Follow the step below o configure automatically dead mail processing on the Domino mail server.
Open the Domino directory. 
Select Configuration - Servers >-Configurations.


Edit the Configurations document associated with the mail server.
Select Router/SMTP  - Advanced - Controls.
In the section Undeliverable Mail select Enabled in the field Automatically process dead mail.


Next in the field Dead mail delivery attempts allowed, enter the number of times to
allow the router to try to deliver dead mail before deleting it. Default value after enabling is 12. Maximum value for this field is 1000. The count is maintained across router and server restarts. If and Administrator enters the value 0 in this field there is no delivery retry attempt and dead mail is deleted immediately.


In the field Time between dead mail delivery attempts enter the number of minutes between delivery attempts. The default value after enabling automatically process dead mail  is 360 (6 hours). The minimum value for this field is 15 and maximum value is 1440 (24 hours).
In case there are mail servers in more than one internet domain within a company administrators can specify each internet domain in the field Internal internet domains tseparated by commas. This field should be blank if there is only one internet domain.
Monitoring dead mail processing
The router logs information about whether dead mail is successfully transferred and when dead messages are deleted. The following show stat commands are available.

Command Description
Show Stat Mail.Dead.RetryCount Number of dead messages retried since server startup. For example, if message 1 was retried once and message 2 was retried hree times, count is 4. 
Show Stat Mail.Dead.DeletedCount Number deleted dead messages since server startup. Dead messages are deleted when Dead mail delivery attempts allowed value has been reached or is set to 0. Deletion also occurs in some error cases, such as when server is unable to determine the address to retry.

Remarks
For monitoring purposes I changed the DebugRouterDeadMail setting to 3. This setting let administrators view the dead mail processing logging for each attempt. On the Domino console enter: Set config DebugRouterDeadMail=3.


Furthermore there is another setting that affects the processing of Dead Mail messages. In the Configuration document - Router/SMTP - Restrictions and Controls - Transfer Controls there is a setting for the Expired message purge interval. The default value for this setting is 15. So the first attempt for processing the Dead Mail Messages can be delayed up to the value in the field Expired message purge interval in relation to the setting in the field Time between dead mail delivery attempts.


Below the configuration on our server.

For more information see also Managing undeliverable mail in MAIL.BOX. In the next blog post more about some other new very cool administrator features in Domino 10.0. 

Friday, 19 October 2018

Plotting a Path Forward for Your IBM Domino (10) Applications


On November 13 there will be a very interesting IBM Jump Session, Plotting a path forward for your IBM Domino Applications with panagenda ApplicationInsights and IBM DAC. Below a brief description of the content of this IBM Jump Session.

Content
Topic:  Plotting a path forward for your IBM Domino Applications with panagenda ApplicationInsights and IBM DAC
Date: Tuesday, November 13, 2018
Time:  11:00 AM EST (16:00 UTC/GMT, UTC-5 hours) for 60 minutes

Are you looking for immediate cost savings across your IBM Notes and Domino infrastructure while planning your path forward? Do you know which
applications are even being used?
Join this IBM Jump Session and learn how the FREE panagenda ApplicationInsights can help organizations like yours identify the business value of your existing infrastructure. Find out what applications you’re paying for that aren't being used, learn what’s worth your time to retain, how to identify dependencies. See what is ideally suited towards a move to IBM Domino Applications Cloud and watch the new panagenda ApplicationInsights "IBM Cloud Readiness" ruleset in action.
Whether you are happy where you are, looking at Domino 10 or facing the challenge of migration, this webinar will show you something that can make your life easier and save your company money.

About JUMP Sessions
IBM Collaboration Solutions (Lotus) Support wants to help you take full advantage of your products. Join us for our JUMP Session series as technical experts share their knowledge and answer your questions.  These webcasts are designed to address specific topics and provide an in-depth and focused technical exchange in a convenient online webcast format.  For more information about our webcasts, visit the IBM Collaboration Solutions Support JUMP Sessions page.