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.

Thursday, 18 October 2018

IBM Notes 9.0.1 Feature Pack 10 Interim Fix 5 Available for Download on IBM Fix Central

Just after the release of Domino 10 IBM has released IBM Notes 9.0.1 Feature Pack 10 Interim Fix 5 on IBM Fix Central. Below the Fix List and the Download Link.

Fix List IBM Notes 9.0.1 Feature Pack 10 Interim Fix 5

Fix introduced in release SPR Description
Notes 9.0.1 Feature Pack 10 Interim Fix 5


Help > About shows 9.0.1FP10 SHF282
RBJAA7E23Y Fix a Calendar Delegation Error when a delegate has the same common name in the Internet Address as one of the participants
GKSIAYNPVL [Standard Only] When upgrading Notes 901FP9 or earlier with ST 901 embedded, to Notes V10, the Sametime client does not work
RKRYB4ZM5Q [Standard Only] Multi user launch fails with 901
KHLEAWNPZ6 [Standard Only] Fix a Lotusscript corruption when adding declarations



This technote contains download links and fix lists for Interim Fixes for 9.0.1.x versions of Notes, Domino, and iNotes. Also included are Interim Fixes for ICAA and Verse On-Premises. Interim Fixes are cumulative and contain all of the fixes from previous versions.

Domino 10 - New Administrator Feature: Dynamic Indexing of High-Usage Views


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 Dynamic Indexing of High-Usage Views. Domino 10 can now dynamically assign dedicated view indexing threads to views with content that is frequently updated. This feature keeps busy views up-to-date and enables them to be opened more quickly. There is no need to manually identify and manage view indexing for active views. When the feature is enabled on the Domino server the Domino server regularly monitors the level of update activity for all views in all open databases and assigns them an update activity score. The views that are designated as high usage can change as view update patterns change. The benefits of this feature are greatest for views with frequent document updates but relatively infrequent view updates shows an improvement in response time. End users notice this improvement when opening a view from Notes and applications see a performance improvement on UpdateCollection calls. Overall another very cool and very useful feature. Below a short description on how to enable dynamic indexing of high usage views and some commands to monitor indexing of high usage views.

This dynamic indexing of high usage views feature is enabled by default on the Domino server. The feature can be disabled by changing the value of the following setting in the server notes.ini file to 0: NIF_VIEW_USAGE_ENABLED=0


To see which views are designated as high usage use the Show Tasks server console command. In the console output there are new View Indexer lines. See the examples below.

View Indexer  applications\nifnsfndx.nsf "Contact Person\Contact Person by Company Name" 10 sec. high usage read
View Indexer  applications\nifnsfndx.nsf "Company\Company by Category" 10 sec. high usage read
View Indexer  applications\nifnsfndx.nsf "Company\All" 10 sec. high usage read

For monitoring indexing of high-usage views use the Show Tasks and Show Stats commands. For statistics about high-usage views use the following statistics with the Show Stat server console command.

Statistic Description
Database.ViewUsage.Calls Number of calls to update
code that added to the
cumulative update activity
score for views.
Database.ViewUsage.HighUsageDisables Number of times that high
usage views were disabled
(no longer high usage).
Database.ViewUsage.HighUsageEnables Number of times that high
usage views were enabled
(made high usage).
Database.ViewUsage.HighUsageUpdateChecks Number of times dedicated
high usage view threads
checked whether views were
stale.
Database.ViewUsage.HighUsageUpdates Number of times dedicated
high usage view threads
updated views.
Database.ViewUsage.Skipped Number of times that
updating the update activity
scores for views was skipped
to avoid semaphore
contention.
Database.ViewUsage.HighUsageCurrent Current number of high
usage views.
Update.View.<db-file-name>.<view-name>.Score Current score for a view.
Update.View.<db-file-name>.<view-name>.<statistic>
where <statistic> is one of the following:
TotalInserts
TotalRemoves
TotalNew
TotalReplace
TotalNonReplace
TotalNodataReplace
Count of specified NIF
primitive update operations
done by dedicating indexing
for a specific high usage
view. Use to verify specific
actions resulting from
dedicating view indexing of a
view.

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

Wednesday, 17 October 2018

Become an IBM Champion


As everybody knows it's IBM Champion season again. Throughout the last three years I had the privilege to participate in the IBM Champions Program. For this I am very grateful. The IBM Champions Program is an amazing program! I am very committed to our community and try, as good as I can, to contribute to the community through visible activities as blog posts, tweets, running an international community and being a moderator in several communities. Due to the release of Domino 10 the nominations for IBM Champion this year may have faded a little into the background but there is still time enough to submit some nominations.

Who should be nominated as an IBM Champion?
Well, below are the well known detailed criteria, but maybe what would help are some examples of people who might be IBM Champions: The person in your company who knows everything there is to know about your IBM software or hardware and makes it all work together and is always the one answering everyone’s questions. The person writing articles or books about IBM technology. The person with a blog who investigates and covers IBM technology. The person who runs the local meetup or user group covering IBM technology. The person whose Twitter stream is always sharing what they’re building with IBM technology. The person making YouTube videos about developing with IBM technology. The person who has a couple of sessions every year at IBM and user group conferences and events. Those are all people who might be IBM Champions.
The IBM Champion program requires IBM advocacy and influence outside one's own organization or customer engagements.  IBM also seek individuals that have significant contributions in at least 2-3 areas as defined below (significant contributions = a contribution, executed multiple times or for an extended period of time).
This can be blogging regularly, tweeting regularly (on topics relevant to our industry, but not necessarily IBM-specific tweets), speaking at multiple events in a calendar year, User Group Conference Planning Committee member (involves the execution of a conference or a part of the conference over a period of several months) or be a President or Board member of a worldwide or local user group for a period of 1 year.


Take the opportunity to nominate an influencer of IBM Collaboration Solutions now. Nominations for the 2019 IBM Champion program will be accepted through October 22. Say thank you, like I did, and Nominate an IBM Champion!
And remember, you can always nominate yourself!
If you need information about someone you want to nominate then take a look at his or her LinkedIn profile. Concerning the nomination form just fill in what you know and submit the form!
Hopefully this blog post gives some inspiration to submit a IBM Champion nomination if you have not already done so. Why, because they deserve it!
If you think, based on the above,  that you would like to be nominated as IBM Champion please contact me. Let me know what you contributed to the community last year and I will fill out a nomination form. If you would like to nominate me as IBM Champion ICS for 2019, I would highly appreciate it.

Below some usefull links for more information about the IBM Champion Program and the link to the nomination form.
Nominate an IBM Champion : IBM Champion Program
Nomination Form IBM Champion : Nominate an IBM Champion
More information about the IBM Champion Program: IBM developerWorks - Champions

Friday, 12 October 2018

Domino 10 - New Administration Feature: Document Deletion Logging

In my previous blog posts I described already some new Domino 10 Administrator features. In this blog post I will describe the new Administration feature Document Deletion Logging. During 2015 I wrote a blog post about deletion logging based on a solution by Paul Withers, Quick Tip: Easy implement Deletion Logging into your Notes Applications. In Domino 10 there is a new server compact option available 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. Below a short description how to enable deletion logging for specific databases and an explanation of the data in the deletion log entry.


Enable deletion logging for specific databases
First ensure that transaction logging is enabled for the databases. For information see the section on Transaction Logging in the Domino 9.0.1 documentation or the IBM Technote Setting up a Domino server for transaction logging.
Next run compact as follows on the Domino server console:
load compact <database path> -dl on "<comma separated list of items>" where <database path> is a specific database or a directory of databases relative to the data directory. <comma separated list of items> is a list of fields to show in the logs to help you identify deleted documents. The fields must be one of these types: Text, Text_List, RFC822_Text, or Time. See the example below for enabling deletion logging for a specific database in a subdirectory.


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. See for examples the screenshot above. Deleting a document from a database adds an entry to the current deletion log with the following data. This data is provided in a CSV-compatible format.

Data in deletion log entry More information
Date and time of the document deletion
Database from which the document was
deleted.
Relative to the data directory
Replica ID of the database Helps to find multiple replicas of a
database in the log if the database name is
not the same on all servers.
Process that did the deletion For example: server - dbmt - replica
Name of the server or person who deleted
the document
Type of document deletion SOFT -- document is in the trash
HARD -- Stub delete (for example when the
document is deleted from the trash)
RESTORE - (document restored after a SOFT
delete)
Class of document deleted Specified as one of the following hex values: v
0001 (Document - NOTE_CLASS_DATA)
0002 (About Database Document -
NOTE_CLASS_INFO)
0004 (Form - NOTE_CLASS_FORM)
UNID Unique document identifier across replicas

UNDO entries in the deletion log
In specific situations it is possible for a document deletion not to be carried out as a result of a failure of some sort. In that case an UNDO entry is shown in the deletion log with an UNDO flag and the following data.
Date and time of the document deletion
Database from which document was deleted
Replica ID of database
UNDO flag
Type of delete that was undone
UNID for the document

Example of a deletion entry in the deletion log:


Data in deletion log entry Example output
Date and time of the document deletion "20181012T150232,71+02"
Database from which the document was
deleted
"applications\testnifnsf.nsf"
Replica ID of the database "C125830C:00209A44"
Process that did the deletion "nserver"
Name of the server or person who deleted
the document
"CN=JO"
Type of document deletion "HARD"
Class of document deleted "0001"
UNID "A239146D:1E04C3D7C125724B:004FD327"

Disabling deletion logging
To disable deletion logging for specific databases, run the following command at the server console: load compact -dl off where is a specific database or a directory of databases, relative to the data directory. 

Domino 10 - Managing Scheduled Mail in MAIL.BOX


In my last blog post, Domino 10 - New Administrator Feature to Push to Notes Clients: Scheduled Messages, I described the new Administrator feature. In this blog post a short description on how the scheduled messages can be managed.

View Scheduled Mail
To view pending scheduled mail open the Administrator Client and select the Tab Messaging. Next open the mail.box. In the View a clock icon indicates a pending scheduled message.


An Administrator can act on a pending scheduled message. First an Administrator can change the Scheduled Time by opening the scheduled message document and select Edit Message. The Scheduled Date field can be changed.


In case the scheduled message should not be send the Action Button Delete Message can be selected.

Monitoring scheduled mail on the server
The following server console commands are available to monitor scheduled mail

Command Description
tell router list Lists each message in the main message
queue and its state. Now includes Scheduled
as one of the states.
tell router show Includes the following line that shows the
number of scheduled messages waiting to be
sent: Waiting for scheduled send time
show stat
Mail.WaitingForSchedule
Shows the number of scheduled messages
waiting to be sent, for example: > show stat Mail.WaitingForSchedule
[003F68:000007-0000000000000574]
Mail.WaitingForSchedule = 4
[003F68:000007-0000000000000574]
1 statistics found
show stat Mail.TotalScheduledReleased Shows the number of scheduled messages
that have been sent since the server was last
started, for example: > show stat Mail.TotalScheduledReleased
[003F68:000007-0000000000000574]
Mail.TotalScheduledReleased = 1
[003F68:000007-0000000000000574]
1 statistics found
show stat Mail.WaitingNotScheduled Shows the current number of pending
messages excluding scheduled messages
waiting to be sent. > show stat mail.waitingNotScheduled
[003F68:000007-0000000000000574]
Mail.WaitingNotScheduled = 0
[003F68:000007-0000000000000574]
1 statistics found

Disabling scheduled mail on a server
As I mentioned in my previous blog post scheduled mail is enabled on a Domino 10 Mail server by default. Administrators can use the Configuration Settings document in the Domino directory to disable the new feature and / or disable the feature in the Mail Policy (in the Delivery Options section deselect Yes in the field Allow users to schedule when messages are delivered). When this setting is disabled the Mail server sends a non-delivery report to the sender if it receives a scheduled message.
  • Open the Domino directory. 
  • Select Configuration - Configurations.
  • Select Edit Configuration. 
  • Select Router/SMTP - Restrictions and Controls - Transfer Controls. 
  • In the field Allow users to schedule a delivery time for messages, select Disabled.

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

Domino 10 - New Administrator Feature to Push to Notes Clients: Scheduled Messages

In my previous blog post, Domino 10 - New Administrator Feature to Push to Notes Clients: Set Limits for Sending Mail, I described one of the new Administrator features to push to Notes clients in Domino 10. In this blog post I will describe a second new Administrator feature to push to Notes clients, scheduled messages. 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 delevery 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.
Note: Domino Servers running earlier releases do not recognize scheduled message requests and route the messages immediately. Before enabling scheduled mail for users make sure that any Mail Servers that handle the users scheduled messages runs Domino 10.

Enabling scheduled mail on Notes clients
For enabling scheduled mail on Notes clients use a Mail Settings document assigned to a policy in the Domino directory. The Domino Directory must be upgraded to the Domino 10 pubnames.ntf design. The Notes user mail file must be upgraded to the Notes 10 mail template (mail10.ntf).
  • Open the Domino Directory
  • Select Configuration - Policies - Settings
  • Select the Mail Settings document and select Edit Settings. 
  • Select Mail - Basics. 
  • In the Delivery Options section select Yes in the field Allow users to schedule when messages are delivered
  • Select Save & Close.
  • Assign the Mail Settings to a Policy.
  • Depeding on the adminP setting it can take up to 12 hours for the feature to take effect on Notes clients. To push the update to clients immediately enter the following command from the serve console: tell adminp p mailpolicy

After the Mail Policy is deployed the delivery option 'Delay delivery until' is available for the users in which a date and time can be selected on which the mail must be sent.


In my next blog post I will describe how to manange scheduled mail in mail.box on the Domino Server.

Thursday, 11 October 2018

Domino 10 - New Administrator Feature to Push to Notes Clients: Set Limits for Sending Mail

IBM Domino 10 is here. Faster, modern and with lower TCO. IBM Domino is back and better than ever including some great new Administrator features. In the next blog post I will describe some of these great new Domino 10 Administrator features. Really cool stuff. The first new Administrator feature I want to bring forward is a new feature to push to Notes Clients from a Mail Policy, Set Limits for Sending Mail. In Domino 10 it is now possible to set various limits and conditions to alert Notes users of when they send mail. Users will see one prompt alerting them to any limits and conditions that are found when they send messages. This feature requires the Domino 10 Directory template on the Domino server and the Notes 10 Mail template on the Notes client. Below the steps to set the limit and conditions in a Mail Policy on the Domino Server.
  • In the Domino directory select Configuration - Policies - Settings. 
  • Add a Mail Settings Policy document or edit an existing Mail Policy document.
  • Select Mail and select the Basics Tab, 
  • Next select Yes for Set outgoing limits. 
  • Select any of the following limits: 
    • Maximum document size
    • Maximum number of attachments
    • Maximum combined size of attachments
    • Maximum number of individual recipients. This setting limits the number of names allowed in all address fields. While a group name counts as one recipient a message is sent to all members of the group.
    • Internal domains used to specify the domains to allow messages to be sent to.

Next deploy the Mail Policy to all users using the Domino Console command 'tell adminp process mail policy'. 


In case any of the above new limits and conditions are set in the Mail Policy document or other limits such as 'Warn user about blank message subjects' or 'Do not allow users to set return receipt' are set  when users send messages that don't comply with any of the conditions and limits, users will see the errors oand warnings in one prompt as shown in the image below.


In my next blog posts more about the new Domino 10 Administrator features.

Tuesday, 9 October 2018

IBM Domino 10 Documentation and Resources


IBM Domino 10 is here. Domino 10 is back and better than ever. Faster, modern and with lower TCO. So welcome to the next era of rapid application development. After the great launch of IBM Domino 10 today several IBM Domino 10 documents have become available. The documentation is once again excellent. Thanks very much IBM. Below a number of links to the different resources. The overview below will be further expanded in the coming period.

How to download IBM Domino 10.0 from Passport Advantage
This document describes how to download IBM Domino 10.0 using the Passport Advantage Online Web Site.

How to download IBM Notes 10.0 from Passport Advantage
This document describes how to download IBM Notes 10.0 using the Passport Advantage Web site.

Domino Query Language
Domino Query Language (DQL) is a facility running in Domino 10 core allowing for a terse shorthand syntax for finding documents according to a wide variety of complexity of terms. It leverages existing design elements without the need to write detailed code to access them.

DQL Restrictions for Domino 10.0.0
Domino Query Language presents a new syntax for accessing Domino databases in a very powerful way. There are some restrictions and to-be-addressed issues in the 10.0.0 release.

IBM Domino 10.0 documentation
What's new in Domino 10? - Product legal notices, Accessibility features and System Requirements.

For more information about Domino 10 see the Destination Domino site.

How to Download IBM Domino 10.0 - IBM Notes 10.0 from Passport Advantage


Yesterday IBM published two Technotes on how to download IBM Domino 10.0 and IBM Notes 10.0 from the Passport Advantage website.  Below the links to the IBM Technotes. At this moment the downloads are not yet available. IBM Domino 10.0, IBM Notes 10.0 and Notes Traveler 10.0 will be shipped tomorrow.

The link below describes how to download IBM Domino 10.0 using the Passport Advantage Online Web Site.To install IBM Domino 10 locate the appropriate part number and then log into Passport Advantage to obtain the product: How to Download IBM Domino 10.0

Part numbers  IBM Domino 10.0
  • CNW1XEN - IBM Domino 10.0 64 bit for Windows English
  • CNW1YEN - IBM Domino 10.0 64 bit for AIX English
  • CNW1ZEN - IBM Domino 10.0 64 bit for Linux English

The link below describes how to download IBM Notes 10.0 using the Passport Advantage Web site. To Install IBM Notes 10.0 locate the appropriate part number and then log into Passport Advantage to obtain the product: How to Download IBM Notes 10.0 

Part numbers IBM Notes 10.0
  • CNW1REN - IBM Notes 10.0 Basic Configuration for Windows English
  • CNW1SEN - IBM Notes 10.0 for Windows English
  • CNW1WEN - IBM Notes, Domino Designer and Admin Client 10.0 for Windows English

The downloads will be available tomorrow (10 - 10 for Domino 10) on Passport Advantage. So get ready for downloading IBM Domino 10, IBM Notes 10 and Notes Traveler 10.