Please complete the details below then remove this line:
Domino/Notes Version: 12.0.2 FP6
Add-on Product
Operating System: Linux
Client irelevant
Problem/Query:
We have a database for employees who have (temporarily) left the company.
This database notifies external email senders that their emails will not be accepted and provides them with the new contact person.
This database is entered as an email database in the personnel file.
Unfortunately, AdminP deletes this database when an inactive employee is deleted.
How can I prevent this database from being deleted?
Does AdminP run in the server context?
Can I remove the “Manager” role from the server in the ACL and assign only “Submitter”? Or is it sufficient to revoke the server’s delete permission? on this specific databse ?
I guess you delete the user, thereby marking their ID in the IDVault as “inactive”?
Instead of pointing directly to that special database in the person document of the “to be deleted” user, you could set a forwarding address in the person document, that refers to the email address of that special database. In that case you would configure your special database as a mail-in database and assign it a special email address.
Thanks for the idea. I’ll give that a try. Currently, we do the following: the user is manually set to inactive in the iDVault and added to a no-access list. In doing so, I configure the database as a mail database in the personnel record.
When the user is deleted, the mail file stored in the personnel document is deleted.
Normally, inactive users are not deleted. This is an area for users who have been absent for a long time.
That doesn’t seem to be working. The email does arrive in the specified database.
However, the senders are not notified. The email is moved from the inbox to the processed messages in the database as usual.
My errorlog shows that an internal mail to “username” the recipient field is changed to “mailin-name” in the target database The agent cant process this.. it looks in the nab to get the manager and returns a mail to sender.
on external mail adresses this dosent happen, but the mail dosent get processed either.
Too much various things in your request. You need to call and let someone who is used to Domino to investigate on your premise.
Adminp does only delete the database you tell him to delete. This is not an issue. Maybe you have a confusion between : user account/email address/mailbox file.
The main question is:
Does that email, that was sent to “the deleted person” and that was forwarded to “the special database” still contain any references to both the sender and to “the deleted person”? If yes, then your agent would still be able to process the message, although you may need to change the logic of your agent.
I still don’t understand your overall workflow and what you’re actually trying to achieve.
If you only want to mark someone as “inactive” then there should be no need to delete anything? If you delete a person, then that persons email address is usually also gone. Why should then someone still be able to send an email to that persons email address?
i Think i look into the agent.
when wi deactivate an user for a specific time, then the process works as intended.
But if HR decides to lay off this user, and pushes a “delete Button” then the user is deleted and also the roaming databases as the mail database. But the assigned maildatabase ist the specified messenger db.
Maybe the delete user job needs a logic that it only deletes databases NOT the messenger db.
The delete job doeas also delete the user in the AD an other applications outside of HCL Notes
Thanx alot, i will look into that.