DRAPI: Accessing to Mail-in via /pim-v1

Domino/Notes Version: 14.5 FP1
Domino REST API: 1.1.6


Problem/Query:

Hi all.
I encountered a problem getting a list of incoming messages from the Mail-in database.

Accessing via /pim-v1/inbox?mailboxid= returns an error:
{
“status”: 500,
“message”: “Could not retrive email test@local.org information from server”,
“errorId”: 0,
“location”: “Empty StackTrace”
}

The error occurs only when accessing mail-in.

Is this a DRAPI bug? Will there be a fix?

Workaround: Adding a person document instead works fine.

Yes, I already found a workaround. But I’m specifically interested in mail-in. That’s why I’m asking. Is this a DRAPI bug, and will there be a fix?

1 Like

PIM stands for “Personal Information Management”, so personal mail, calendaring etc. MAIL scope picks up your mailfile location from your person document.

Mail-in databases are only used for mail. The database provides calendaring and todos, but I’ve never seen it used in customer environments. And mail-in databases do not have their own personal contacts database. It has only one element in common with PIM - email. Other aspects of PIM and how it needs to work don’t fit with the PIM concept.

Is it a bug? No, it’s more accurate to say that mail-in databases were not in scope for the functionality. And as I explained, the discovery phase wouldn’t work - there is no mapping from a person document to the mail-in databases they own.

Using a normal schema and scope is the better approach. It should be possible to expose all the data required, and allows you to tightly control access. Using PIM exposes access to all personal mail data as well.

Hello. Everything you wrote seems correct, but how does that tie into your assertion that creating a service account doesn’t reproduce the problem?
So, creating an empty account (without certificates, etc.), which users can’t even use, doesn’t cause any problems, but there is a problem with mail-in. Architecturally, you may be right, but in practice, that’s what we have.