Here is another issue I encountered on my travel to the DAOS universe.
My mailfile is based on mail85.ntf. There are no documents in the database. The DAOS Dir does not contain any NLO files.
No surprise is that. Then I changed the template on the database to ONTF_dwa702. After the design has changed, I found 2 NLO files in the DAOS repository!!
Again I changed the template and used a DWA 7.0.3 template. Now I saw this in the DAOS repository.
Does somebody has any explaination ??
Since design elements are effectively documents, I bet by there are design elements in the templates that show as “files” depending on the template used. I would load up NotesPeek to verify.
As you are performing tests with DAOS, one thing that would be interesting is the following:
Send an email to another user (e.g. from ALPHA to BETA). This email should contain 1 .jpg attachment and lot of text (more than 100 KB in text). The user BETA should have the setting where this user prefers receiving MIME as the email format. Also you should configure the server to receive attachments using base64 encoding. As you can see this is a typical email in a typical environment.
Now my hyphotesis is that there will be 4 new .nlo files in your repository:
1+ For the .jpg file that was saved in the Sent folder of ALPHA.
2+ For the .jpg file that was received by BETA.. this is a different .nlo file since it is encoded in base64 so internally talking the attachment is different
3+ One .nlo file that holds the HTML portion of the MIME message (when you send an email with many text, the HTML portion is stored in an internal attachment)
4+ One .txt file that holds the TEXT portion of the MIME message (when you send an email with many text, the TEXT portion is stored in an internal attachment)
So this is another way to generate 4 .nlo files using a typical email holding only 1 attachment.