14740: Mail related fixes
Issue: The fix contains the below fixes
1. The Graph API calls timeout increased to 100s. This has been fixed in 14760 version on upgrading the microsoft SDK to 2.0.21 version.
2. The user thread wait time to semaphore acquire (wait time to acquire lock) is increased from 20s to 60s in this fix (SD-133201)
3. Retry sending system notifications from SDP on any failure. SDP will retry to send the same notification 3 times (SD-132081)
4. Option to configure additional mail senders for any portal (SD-133532)
Regarding fix 4, find the details below (others are self - explanatory)
- After applying the fjar file and xml files, restart the application service. Login as SDAdmin and access the url "/servlet/DebugServlet". Choose your portal and check for "Add account" button. Clicking that button will redirect to Microsoft login page where user can choose an account as additional sender. Once logged in properly, it will get listed under "Configured additional accounts" as below (This button will be shown only to portals that have outgoing configured with Exchange Online using OAuth)
- Here, the "sdpcart" mailbox is the one configured in the Outgoing mail server settings using Graph API. 2 mailboxes - sdpcart1 and sdpcart2 are added as additional senders. For this to work, "Send-On-Behalf" permission should be given to sdpcart1, sdpcart2 mailboxes in the sdpcart mailbox (Refer below - https://admin.microsoft.com/ portal)
- Once configured, if the primary mailbox (sdpcart) exhausts the 10K recipient rate limit in the last 24 hours, SDP will switch the sender to the next available additional sender mailbox (sdpcart1) and starts sending notification mails using that mailbox. Once sdpcart1 exhausts, it will start sending from sdpcart2 mailbox (if configured). Users can configure 'n' number of additional senders according to their need.
- The receiver might find the "From" header as "sdpcart" but, it might get displayed as "SDP Cart1 sent on behalf of SDP Cart" or "SDP cart sent by SDP Cart1" depending upon the receiver's mail client.
1. Download the attached .fjar file
2. Click here for steps to apply the .fjar file.
3. Place the attached xml files under "ServiceDesk/webapps/ROOT/WEB-INF/security/" folder (Replace the existing files with this)
3. Restart the application service.
New to ADSelfService Plus?
Related Articles
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 ...New request is created everytime when a user is sending mail to closed Request
Issue : New request is created everytime when a user is sending mail to closed or Resolved Request. Cause : In some cases, there will be no workorder id mentioned in the subject and that mail is not sent as reply from user for the notification or ...Mail Fetching - Error while processing attachment and inline image.
Issue During the process of fetching emails, attachments are dropped as a result of the presence of directory traversal characters. Furthermore, an issue arises when processing inline images, this particular error related to inline images results in ...Query to show Site and its related settings(MSSQL & PGSQL)
Tested in Build PGSQL (14300) or MSSQL (14306) Go to Reports-New Query Report and execute the query. select adef.org_name "Account Name",sdef.siteid "Site ID", sdo.name "Site Name", siteconf.settingdetail "Related Settings", CASE WHEN ...List of mail fetching issues and solutions
Scenario 1 : Mail fetching issue due to Invalid or No PKIX certificate . Log traces for Mail Fetching issues Exception when connecting to store.|javax.mail.MessagingException: sun.security.validator.ValidatorException: PKIX path building failed: ...