|Latest 7 Posts
| Important Security Fix for IMAP|
Sat, Apr 22nd 2017 8
| NIFNSF Supported Maximum Size above 64 GB!|
Fri, Apr 21st 2017 6
| Disclaimer Attachment Issue not yet fixed in IF1|
Fri, Apr 14th 2017 7
| Get Notes FP Version in @Formulas |
Wed, Apr 12th 2017 10
| Notes/Domino 9.0.1 FP8 IF1 released|
Tue, Apr 11th 2017 16
| Current Information about NIFNSF|
Fri, Mar 31st 2017 9
| CREATE_R9_LOG is not a valid notes.ini parameter and does not exist!|
Fri, Mar 24th 2017 8
| IBM Notes V9.0.1 Mac 64 Bit English (CN6VDEN )|
Tue, Sep 29th 2015 24
| Details about JVM 1.8 Update in Notes/Domino 9.0.1 FP8|
Sun, Feb 5th 2017 23
| Symantec Backup Exec End of Life|
Sat, Dec 5th 2015 22
| Solution for Notes/Domino related process is still running when applying a Fixpack or Hotfix|
Wed, Mar 25th 2015 17
| TLS 1.2 Connection Issues with mail.protection.outlook.COM |
Thu, Jan 7th 2016 16
| Notes/Domino 9.0.1 FP8 IF1 released|
Tue, Apr 11th 2017 16
| Notes 9.0.1 FP7 IF1 released|
Thu, Dec 8th 2016 15
| IBM Notes/Domino 9.0.1 Feature Pack 8 Preliminary Release Notice|
Fri, Jan 27th 2017 14
| Passing a document to an agent without saving it first|
Sun, Apr 6th 2014 10
| DAOS NLO Encryption and Decryption|
Wed, May 28th 2014 10
||Traveler 184.108.40.206 available with some important changes
Traveler 220.127.116.11 has been released with some important fixes and also changes. The Release documentation has some interesting details.
Here is the extract from the release documentation with some comments.
"Device wipe is no longer an option for iOS 10.x devices as support was dropped by Apple. You can still use the Wipe Traveler Data option."
For security reasons Apple disabled wipe over ActiveSync which is understandable. Before that change every server could wipe any device connected via ActiveSync.
With this Apple side change Traveler could not delete the device any more and the status from the device was not interpreted correctly by the server.
Traveler does now check if the device still supports the wipe (running iOS earlier than 10.x) and does only allow the Data Wipe over ActiveSync if the full wipe is not supported on the device.
"Yellow status message if the IBM Traveler server is not listed as a Trusted Server for an end user's mail server. This is required for future security and feature enhancements planned for 2017. The status message will include information about how to correct."
Sounds like IBM is planning a bigger change in 2017 for Traveler. I am curious what this higher security requirements are needed for. Trusted Servers are a quite high requirement which allow the Traveler servers to fully authenticate as any user on the mail server. It's much higher than just granting manager access to an individual mailfile.
I have removed the Trusted Servers entry on my mail-server but I did not yet see the warning.
"Database schema updates to improve data integrity.
Tablerepair tell command to support the above schema updates. A warning message will be displayed at startup if any of the schema updates were not applied with instructions to run the tablerepair command. The server will continue to function properly if no action taken.
NOTE: IBM Traveler 18.104.22.168 does include a database schema update. Action may be required if you manually manage your database schema (this is not common). If you use auto schema updates (default behavior) there is no action required. See Updating the Enterprise Database for more information (http://www.ibm.com/support/knowledgecenter/SSYRPW_9.0.1/UpdatingTheEnterpriseDatabase.dita)"
So this is an important information. This new version requires a schema change. If you are running stand-alone that should not cause any issues.
If you have automatic schema update enabled the schema update should also happen automatically.
And if you are switching from manual schema update to automatic schema update you should be careful. There is one ARPA fixed for DB2 and you should be aware of the default schema name differences for manual and automatic schema configuration.
I guess with this schema change the issue has been discovered and the fix is that the NTS parameter with the schema name will be automatically set.
(See -> http://www.ibm.com/support/docview.wss?uid=swg1LO90497 for details).
The fix-list contains some other important fixes! Check the fixlist link below for details.
My server is already updated but I had not much time to test.
IBM Traveler Fixes 22.214.171.124
IBM Traveler 126.96.36.199 Server Release Documentation
Nov 15, 2016
| Recent Blog Posts
Important Security Fix for IMAP|
Sat, Apr 22nd 2017 9:13a Daniel Nashed
In case you are running IMAP on a server that is reachable over the internet you should look into this fix ASAP. It might not be that critical for internal services. See details about this vulnerability here --> http://www.ibm.com/support/docview.wss?uid=swg22002280 All versions of Domino are affected!
NIFNSF Supported Maximum Size above 64 GB!|
Fri, Apr 21st 2017 9:02p Daniel Nashed
After getting that question offline and having a discussion on my blog, I checked with IBM if they plan support NIFNSF sizes above 64 GB. Since it is kind of a database container and needs a database handle someone could think that the maximum limit is also 64 GB. That would give us at least 64 GB room for the NIF index -- which would be already a big improvement. But from what I recall from some comments at Connect some years ago the maximum limit was not around 64 GB when they designed it
Disclaimer Attachment Issue not yet fixed in IF1|
Fri, Apr 14th 2017 6:28p Daniel Nashed
As Rob Kirkland commented in one of my last blog posted, the fix in IF1 does not solve the iusse. We both checked with IBM and got the reply that the SPR just changes back the default and disables the change introduced in FP8 for Google calender integration. IBM is working on a fix hopefully makes it into FP9. So for now you should keep the notes.ini Parameter MIMEDisclaimersNoEncode=0 disabled. Thanks to Rob to bring this up! -- Daniel TPONAKFJLP After upgrade to FP8, with
Get Notes FP Version in @Formulas |
Wed, Apr 12th 2017 6:19a Daniel Nashed
In C-API and Lotus Script, Java developers the version information already shown for each FP. For example Lotus Script returns the full version string with session.NotesVersion. But if you want to check the version information in @Formulas @Version will still return 405. There is a new optional parameter which returns the Feature Pack version. So you use @Version to check the version and if it is 405 you check @Version(1) which will return 8 for Feature Pack 8. It is used in the new ma
Notes/Domino 9.0.1 FP8 IF1 released|
Tue, Apr 11th 2017 5:06a Daniel Nashed
Notes and Domino 9.0.1 FP8 IF1 has been shipped and there is also a separate fix for iNotes. All those IFs have the same version number but contain different SPRs! The most important IF is for the Domino Server. It fixes the disclaimer issue I reported before. And also the performance fix for the new feature NIFNSF which was introduced in in FP8. Be aware that NIFNSF is a server feature and not a client feature. It requires translog enabled on your server! Translog is not officially
Current Information about NIFNSF|
Fri, Mar 31st 2017 10:42p Daniel Nashed
Domino 9.0.1 Feature Pack 8 introduced "NIFNSF" which allows to separate the view/folder index into a separate file. Let me try to summarized my current experience from my tests and from the field. There are multiple benefits moving the index to a separate file. 1. Backup Storage Reduction First of all having the index in a separate file reduces the amount of data that you need to backup. For mail databases the index is around 10%. If you have DAOS enabled from the remaining dat
CREATE_R9_LOG is not a valid notes.ini parameter and does not exist!|
Fri, Mar 24th 2017 8:29p Daniel Nashed
After hearing this question twice a week I think it is time for a blog entry. There is a notes.ini parameter for the different ODS formats in different releases. The latest one you should use is Create_R9_Databases=1 to create databases with ODS 52. ODS 52 is needed for local databases which are encrypted (there was an underlying ODS issue that has been addressed in ODS 52). Also for hew new LargeSummary (16MB instead of 32KB per document) you need to be on ODS 52. But there is no ne
Traveler 188.8.131.52 Relased with important bug fixes|
Fri, Mar 24th 2017 8:12p Daniel Nashed
As posted before Traveler 184.108.40.206 had one issue that needed urgent attention. Push was not working when the mail-server had a short downtime. If you are on that release you should update asap. There are a couple of other fixes along with that ARPA included in 220.127.116.11. Just back from a couple of days of travel and installed it this morning. Looks good so far. APAR # Abstract LO90889 Invitee status not correct on mobile device if the invitee response is received in a non-syncing
D9.0.1 FP8 Attachment Corruption Issue with Disclaimers|
Tue, Mar 21st 2017 3:27p Daniel Nashed
There is an issue that has been reported about FP8. When using disclaimers attachments might be corrupted. IBM released a technote with details and is working on a fix. Feature Pack 8 contains an enhancement/fix to correctly send Google Calendar files. The fix is enabled by default and causes this corruption. You can still deploy FP8 and disable the feature/fix temporary via Notes.ini MIMEDisclaimersNoEncode=0 on your SMTP outbound server. See this SPR #TPONAKFJLP / APAR #LO91828 fo
Traveler on Domino 9.0.1 FP8|
Tue, Mar 7th 2017 9:51p Daniel Nashed
Domino 9.0.1 Feature Pack 8 has just shipped. If you are intending to update your Traveler Server to Domino FP8 you should be aware that you need at least Traveler 18.104.22.168 (which currently has an issue reconnecting to a mail-server if it wasn't reachable --> see previous blog posts). If you still intend to update your server there are some important requirements. FP8 comes with Java 1.8 and Traveler is using that JVM. So it some changes are needed in the Traveler code to support the