Issue with Special Characters in Passwords for Get IMAP Mail Messages Activity

[bhavesh_bhanushali]

I am experiencing an issue with the Get IMAP Mail Messages activity in UiPath where passwords containing special characters (such as double quotes " and single quotes ') are not being processed correctly, leading to authentication errors.

Initially, the credentials were being retrieved from Orchestrator, but this approach encountered issues. To work around this, I used a hardcoded password and applied escape characters to handle the special characters.

Is this a known issue with the Get IMAP Mail Messages activity, or is there a recommended way to handle passwords with special characters? I would appreciate any guidance or confirmation on whether this is a bug or if there is a workaround available.

Steps to Reproduce:

Retrieve Credentials from Orchestrator:
UserName - email@email.com
Password - 233"23’adfa (random password)

Activity: Get IMAP Mail Messages
Configuration:
Email: UserName
Password: Password
Server: imap.titan.email
Port: 993

MailFolder: Inbox

Error Message:

MailKit.Security.AuthenticationException: i.2vwtizR ensure all parts are encoded

Resolution Attempted:

Resolved temporarily by hardcoding the password using New System.Net.NetworkCredential(String.Empty, "233"“23’adfa”).SecurePassword to handle the password with special characters.

Environment Details:

UiPath Version: 2024.10.1
Mail Activities Package Version: 1.23.1
IMAP Server: imap.titan.email

[naveen.s]

Try using the simpler password with out using the special character.

[Anil_G (Anil Gorthi)]

@bhavesh_bhanushali

Welcome to the community

If setting password directly is working then try to get credentials and use same parsing

System.Net.NetworkCredential(String.Empty, PasswordVariableFromOrchestrator).SecurePassword

Also check if password retreived is encoded like double quotes are replaced with " if so then first we need to retrive password and then decode and then use

Hope this helps

Cheers

[bhavesh_bhanushali]

Thank you, Naveen and Anil! it turns out the issue was a silly mistake on my side with the variables. I appreciate your support!