Best practices for the mail fetching

Best practices for the mail fetching

1.  Please do have a dedicated mailbox for the application, the same mailbox should not be configured for any other application.

2. Always set the email  to be deleted automatically once created as a ticket in the application because it will avoid looping of emails and hence duplicate tickets wont be created.

3. Make sure network connectivity is good and the mailbox is always reachable and accessible.

4. Do set the spam filter in the mailbox rather than in the application which will increase the efficiency of mail fetching.


                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • Mail fetching - deleted flag issue

                        This message will be thrown, when you have provided a shared mailbox. The concept here is, SDP MSP reads the mail from the configured mailbox and adds it as a request. During the time, if some other application fetches the mail from the same mailbox ...
                      • Monitor Mail Fetching schedule

                         We have a workaround for checking the status of mail fetching (start or stopped). However, we do not have an option to start or stop fetching remotely.  We can integrate "Applications Manager" with SDP MSP and we can do regular monitoring (as per ...
                      • Best practices for managing old accounts and sites.

                        When dealing with old accounts/sites in Service Desk Plus MSP (SDP MSP), it's essential to follow best practices to maintain a clean and organized database. Managing old accounts/sites efficiently can help improve performance, reduce clutter, and ...
                      • Mail fetching issue: Fetching stops when mail sent from unapproved user (with huge description)

                        Issue : Mail fetching stops when mail sent from an unapproved user Issue found in Build number : 14200 Issue fixed in Build number : 14300 Issue ID: 20438 Error trace: ...
                      • EWS Mail fetching issue - Proxy not enabled for ews. isIncoming: true

                        Issue: EWS Mail fetching issue using different tenants Error trace 1: [23:30:20:701]|[01-23-2023]|[com.adventnet.servicedesk.common.MailUtilities]|[INFO]|[73]: Proxy not enabled for ews. isIncoming: true| ...