Fix for #8731818 : The from address isn't a proper email address.
Issue:
The from address is "Spam Report" for the problematic email. While parsing this, we are getting an error and the mail fetching has been stopped.
Workaround:
This exception while parsing the "From" header is catched so that mail processing isn't stopped. Such mails will have the Requester as "Not Provided" since the "From" header isn't a proper email address
Steps to apply the fjar
1. Download the attached 14201_8731818.fjar file.
2. Click here on steps to apply the fjar file.
3. Restart the application service.
4. Check for the issue. If it occurs again, kindly share us the logs for analysis. If the size of the log file is huge, you can send it to us using our FTP link https://bonitas2.zohocorp.com/. Select the product as "ServiceDesk Plus" and ticket number as 8731818.
Jar compatibility:
Build version | Attached fjar filename |
14201 | 14201_8731818.fjar |
14300 | 14300_8731818.fjar |
14303 | 14303_8931408.fjar |
New to ADSelfService Plus?
Related Articles
Fix: Failed to parse To/Cc address while fetching mails using Graph
Issue: If the To / Cc address contains the email address in the format "Test, SDP" <test@sdp.com> (containing "," character in the email address itself), then parsing of such addresses using Microsoft Graph fails in SDP. If such address is a support ...FAFR script to validate email address
Script var field = "WorkOrder_Fields_UDF_CHAR1"; var emailID = $CS.getValue(field); if (!ValidateEmail(emailID)) { alert('Please enter a valid email address example@abc.com'); $CS.stopFormSubmission(); } /*A function which takes email and validate ...Fix: Email sending failed when one of the email address is invalid (throws 550 error code)
Issue: Mail sending failed when one of the recipients is invalid and mail server throws 550.xx error codes. [14:00:18:856]|[08-08-2023]|[SYSOUT]|[INFO]|[800]: DEBUG SMTP: Sending failed because of invalid destination addresses| ...Custom Script to Trigger an Alert if there is no email address associated with Requester (using FAFR)
Working on Builds: 14500 too Scenario: Request should not be created if there is no email address associated with the requester. Instead it should prompt and alert stating there is no email address associated with the requester. The above requirement ...Email id already exists issue
It wont allow you to create a contact, says 'email already exists'.But wont be listed in contact list view,support list view,Acc manager list view select * from aaacontactinfo where emailid='email@email.com'; This will give you the contactinfo_id , ...