Issue
The requester is attempting to set up a Test Email Monitor in their IT Tickets application after creating a test mailbox and its Auth Account in Azure. They have questions regarding the usage of the same TD Username across multiple email monitors, the process for changing the TD Password, and the management of email monitors for testing purposes.
The goal of this test Email Monitor is to experiment with mailbox rules they wish to deploy in their primary mailbox. They are ensuring they have the correct configuration before proceeding.
Environment
The requester is using the IT Tickets application with multiple email monitors previously set up. There have been recent changes involving the creation of a new test mailbox and authentication accounts in Azure.
Resolution
To set up the Test Email Monitor successfully, the following recommendations and clarifications were provided:
- You can use the same TD Username for the Test Email Monitor as you do for existing Email Monitors unless you have a specific reason to create a new one.
- Changing the TD Password via "Click to update existing password" allows for password entry but does not reset it. If you reset the password from the Users section, you will need to update it on all Email Monitors using that TD Username.
- It is advisable to create the Test Email Monitor in a test application to prevent interference with active monitors, as each application can only have one reply monitor.
- Yes, you must generate OAuth 2.0 tokens for your new Test Email Monitor just like any conventional email monitor.
- No limit exists on the number of email monitors you can create, but only one reply monitor is allowed per application.
- For additional setup steps, follow the documentation provided here: Setup Guide for Email Monitors.
Cause (Optional)
The issue arose from the complexities of managing multiple Email Monitors and ensuring proper setup and configurations for testing new mailbox rules without disrupting existing operations.