电子邮件 软件包 updates
- Updated: 2026/02/17
电子邮件 软件包 updates
Review the updates in released versions of the 电子邮件 软件包 such as new and enhanced features as well as fixes and limitations. The page also lists the release dates of each version, and the compatible Control Room and Bot Agent versions.
Versions summary
The following table lists the versions of 电子邮件 软件包 released either with an Automation 360 release or as a package-only release (in descending order of release dates). Click the version link for information about updates in that 软件包 version.
| Version | Release date | Release type | Bot Agent version | Control Room build |
|---|---|---|---|---|
| 3.33.1 | 2026 年 2 月 16 日 | 软件包-only; post Automation 360 v.39 release | 21.210 or later | 13980 or later |
| 3.31.1 | 2025 年 12 月 10 日 | With 软件包 update and Automation 360 v.39 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.31.0 | 2025 年 10 月 15 日 | Package-only; post Automation 360 v.38 release | 21.210 or later | 13980 or later |
| 3.30.0 | 2025 年 9 月 15 日 | With 软件包 update and Automation 360 v.38 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.29.0 | 2025 年 8 月 15 日 | Package-only; post Automation 360 v.37 release | 21.210 or later | 13980 or later |
| 3.28.0 | 2025 年 6 月 4 日 |
随着 Automation 360 v.37（沙盒）版本的发行（与 MacOS 相关的支持） |
21.210 or later | 13980 or later |
| 3.27.2 | 2025 年 3 月 17 日 | Package-only; post Automation 360 v.36 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.26.0 | 2025 年 3 月 5 日 | With Automation 360 v.36 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.24.2 | 13 December 2024 | Package-only; post Automation 360 v.35 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.24.0 | 2024 年 11 月 26 日 | With Automation 360 v.35 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.23.2 | 2024 年 9 月 27 日 | With Automation 360 v.34 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.22.1 | 2024 年 6 月 17 日 | With Automation 360 v.33 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.21.1 | 2024 年 3 月 22 日 | Package-only; post Automation 360 v.32 (Sandbox) release | 21.210 or later | 13980 or later |
| iih1701777089188_00042.html#trw1682768294100__a360.31-email-ga | 2023 年 12 月 6 日 | With Automation 360 v.31 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.18.2 | 2023 年 9 月 6 日 | With Automation 360 v.30 (Sandbox) release | 21.210 or later | 13980 or later |
| 3.17.6 | 2023 年 6 月 6 日 | With Automation 360 v.29 (Sandbox) release | 21.210 or later | 13980 or later |
- To download an individual 软件包 (updated in an Automation 360 release where you want only the 软件包), use this
URL:
https://aai-artifacts.my.automationanywhere.digital/packages/<package-file-name>-<version.number>.jar - For 电子邮件
软件包, the naming convention is:
bot-command-email-<version.number>.jarFor example,
bot-command-email-3.19.2.jar
For detailed steps on downloading a 软件包 and manually adding it to the Control Room, see 将 软件包 添加到 Control Room.
3.33.1
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's changed |
|---|
|
Option to control
where email replies are sent (Service Cloud Case ID: 02140405) The
following 操作 in the 电子邮件
软件包 are now updated to include the optional
Reply To field:
You can use the Reply To field to enter one or more (separated by commas) email addresses. If you set up an automation with any of the mentioned 操作 and configure the Reply To field, any replies or email responses from recipients will be directed to the email address specified in the Reply To field instead of the original sender. This eliminates the possibility of sending email responses to accounts that might not be monitored. |
|
Option to specify importance of an
email (Service Cloud Case ID: 01946828, 01945660, 01986339, 01991658,
02004831) A new Importance drop- down menu is
now available in the following 操作 across all the
three servers (Email server, Outlook and EWS server):This option enables you to set one of the following importance
levels for an outgoing email:
|
| Fixes |
|---|
| After updating to this version,
the Reply and Reply All
操作 now work correctly even when the login ID and
sender/CC address are the same. Service Cloud Case ID: 02284307 |
| The For each mail in
mail box iterator for the 电子邮件
软件包 no longer fails intermittently to read emails and
reliably processes every email in the mailbox, ensuring that no messages are
skipped. Service Cloud Case ID: 02231162 |
3.31.1
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| Fixed security vulnerability issues. For more
information, click the release download link and view the Security &
Compliance reports at A-People Downloads
page (Login required). Service Cloud Case ID: 02216530 |
3.31.0
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's changed |
|---|
|
Filename field in the
Save email 操作
(Service Cloud Case ID:02092205,
02269235, 01918696, 01997247) A new Filename input field is now introduced in the Save email 操作 to give users control over how the saved email files are named. |
| Fix |
|---|
| After updating to this
release, automation can now reliably read all emails from the folder as
expected, improving consistency and accuracy in email-based automations.
Previously, automations would fail intermittently to read all emails from a
folder based on specified conditions. Service Cloud Case ID: 02217976, 02273696, 02273938, 02274805, 02231676 |
3.30.0
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| You no longer encounter any issues when
different sessions to the Outlook client are connected within nested loops.
The
操作 now moves the email correctly to the designated
folder. Service Cloud case ID: 02180642 |
3.29.0
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's new |
|---|
|
Enhancement to 电子邮件
软件包
(Service Cloud case ID: 01981433, 02164783, 02118870, 00710720,
01775444, 01862010, 01864493, 01869940, 01962909, 02084940, 02114985,
02154011)
|
|
Enhancement to Save all attachments action (Service Cloud Case
ID: 02185937) You can now use the From a specific folder (optional) field to specify the folder path from which attachments should be saved, regardless of changes made to the system language. |
| What's changed |
|---|
|
Update to the status of email field options
In email actions (Move all and Save all attachments) that use the Status of email field, the option previously labeled All has been renamed to Both. The available options are now: Both, Read, and Unread. |
| Fix |
|---|
| Fixed an issue where 操作 such as Reply,
Reply All, and Forward
with Control Room Managed OAuth2 authentication no
longer display an unknown sender name. The sender's email address is now
shown correctly when you receive the email. Service Cloud case ID: 02196524 |
3.28.0
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's new |
|---|
|
平民开发者和专业自动化专家现在可以在他们的设备上开发和运行 MacOS 平台上的自动化。 此 软件包 已增强，以支持 MacOS，确保统一的开发和可移植性体验。 |
| What's changed |
|---|
|
Updates to the User interface in 电子邮件
软件包
We have enhanced the help text for
specific fields that display examples for file paths or folder
locations within the following 操作 of the 电子邮件
软件包:
|
| Fixes |
|---|
| Fixed an issue where the selected
Microsoft Outlook email account was not set as the default account, and
the Move email 操作 failed to
execute correctly. Service Cloud case ID: 02134905, 02166158 |
| When you connect to the email server
with IMAP client credentials and use the Save
attachments
操作 within a loop, the Save
attachments
操作 will no longer try to download and save a copy of
an email that does not contain any attachments. Service Cloud case ID: 02136104, 02138853 |
| The Move all
操作 now executes without any issues. Previously, the Move all 操作 failed to move emails correctly if a 操作 preceded it in the automation logic. Service Cloud case ID: 02176513, 02195347 |
3.27.2
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| You no longer encounter issues when connecting to EWS
with ROPC authentication and using 操作 such as
Move or Check if folder
exists. Previously, these actions did not work if the folder count exceeded 1,000 Service Cloud case ID: 02184531 |
3.26.0
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| Fixed an issue connecting to Microsoft
Outlook with multiple email accounts configured under restricted
permissions. When you ran the automation, the mail account you had access to
was not accessible, and an error was displayed due to some
issues. Service Cloud case ID: 02134905, 02166158 |
3.24.2
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's new |
|---|
|
New option to configure connection timeout (Service Cloud case
ID: 02171197) You can now set a connection timeout value when creating automation using the Connect or Send 操作 with the EWS server option for email automation. This new Connection timeout duration (seconds) (optional) field allows you to configure the timeout between 10 seconds and 60 seconds ensuring a successful connection with the EWS server. |
3.24.0
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| Create a 机器人 using the Email
Connect
操作 within a loop and connect to your Gmail account using
IMAP. Select a date/time to retrieve specific
emails on or after a certain date. The emails are now retrieved from the
mail server without any issues. Previously, when the mail server's date changed to the day before the Bot agent device date, emails that came after midnight on the mail server were not read. Service Cloud case ID: 02118382 |
3.23.2
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's new |
|---|
|
Variable support for Microsoft
Outlook client (Service Cloud case ID: 02097136) When you use the 电子邮件 软件包 to connect to the Outlook client, you can now use the Variable option to specify the email address to which you want to connect and perform the email-related operations. |
| What's changed |
|---|
|
Supported special characters in
the subject line of the Save email 操作
(Service
Cloud case ID: 01816076, 01947470, 01955099, 01961876, 02094142,
02092205) The Save email 操作 now supports special characters in the subject line. If the subject line contains a tab character (\), the tab character is replaced with underscore ( _ ) in the filename created to save the email. |
| Fix |
|---|
You no longer encounter issues when you
create a 机器人 using actions such as
Forward, Reply, or
Reply All and perform the following steps to
automate an email-related task.
Service Cloud case ID: 02101446 |
3.22.1
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's new |
|---|
|
Support for Control Room managed
OAuth2 authentication in 电子邮件
软件包
(Service Cloud case ID: 00705009, 01788683, 02082598) Google has announced the deprecation of Less Secure Apps (LSAs) to connect to Google Workspace using a username and password. Starting September 30, 2024, access to LSA will be turned off for all Google Workspace accounts. To help reduce the risk of deprecation, we introduced a new Control Room managed OAuth2 mode of authentication in the 电子邮件 软件包 that allows you to connect to an email server. This authentication mode is secure and uses the centralized access token management from the Control Room. |
|
Introduced encode option in email 操作
(Service
Cloud case ID: 02082334) When you use email 操作 such as
Send, Forward,
Reply, or Reply All, you
can now use the Encoding for email option and
select the following encoding types as per your requirement from the
encoding list to represent information:
|
| Fixes |
|---|
|
When you use the 电子邮件 软件包 and if an attachment is included in the Send action and specified using the List option, you can now see the attachment details in a read-only mode both in the public workspace for checked in 机器人 and in the private workspace for new 机器人. Service Cloud case ID: 02114678 |
|
You can now use 操作 to send emails from Gmail using the 465 port. Previously, the Send 操作 failed with a connection error when you used the 465 port. Service Cloud case ID: 02088546 |
|
You can now establish a connection with an email server using IMAP protocol and use the Save attachment 操作 to save the attachments. Previously, the 机器人 displayed an error on execution if the attachment file name had a special character such as (\t)Tab. Service Cloud case ID: 02067595 |
|
You can now use 操作 to forward emails and attachments to one or more recipients. Previously when you used Forward 操作 within loop to process email, the 机器人 failed to forward emails that were generated using SAP application. Service Cloud case ID: 01995208 |
|
When you loop through each mail in a specified Gmail inbox for more than 30 minutes, the status of the emails now show correctly as Read. Service Cloud case ID: 01998232 |
3.21.1
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| When you establish a connection with
Outlook, you can now use
Move
操作 to move emails from one folder to another in the
mailbox, even if there is more than one account integrated into locally
installed Outlook. Service Cloud case ID: 02109373, 02109838, 02107612, 02112311 |
3.19.2
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fix |
|---|
| When you create a 机器人 using
the 电子邮件
软件包, establish a connection with the
Outlook client, and use Move
all
操作, the 机器人 moves the emails to the
correct destination folder even if the folder names are
similar. Service Cloud case ID: 01973624 |
3.18.2
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| Fixes |
|---|
Create a 机器人 to read emails
that have regular and embedded attachments in the message body and perform
the following steps:
Service Cloud case ID: 01971661 |
| When you use 操作 such as
Reply or Forward and
connect to an email server with authentication type as Client
credentials, the email shows the Sender address
correctly. Previously, the email displayed the Sender's address as unknown. Service Cloud case ID: 01966831 |
| A 机器人 no longer displays an
error and an email is sent in the following scenario: When you use 操作 such as Send,
Forward, Reply,
ReplyAll and connect to the EWS server, choose
OAuth 2 (Client credentials or PKCE) authentication mode, and deselect the
Raise error if the attachments are
missing. Service Cloud case ID: 01955838 |
| Send email now works for locally hosted
SMTP using the email server option. Previously, if you used port 465 for a secured SMTP server and selected Use secure connection (SSL/TLS) option as False, the 机器人 failed and displayed an error message. Service Cloud case ID: 01961465 |
| Known limitation |
|---|
When you connect with the
EWS server and use Loop
操作 to retrieve all the emails from the email server, and
if the email subject contains the following characters, the 机器人 fails to execute and displays an error message.
Service Cloud case ID: 01983181 |
3.17.6
- Compatible Bot Agent version: 21.210 or later
- Compatible Control Room version: 13980 or later
| What's new |
|---|
|
Enhanced error messages displayed during
bot execution (Service Cloud case ID: 01887882) When you create a 机器人 using the Send email 操作 with incorrect attachment logic, the 机器人 execution fails and displays the following more detailed error message: Incorrect inputs are specified for the Attachment field when 机器人 execution fails. |
|
Email ID invalid option added to Send email 操作
(Service Cloud case ID:01823424) A new Raise error if the email ids are invalid option has been added to the Send email 操作 of the 电子邮件 软件包. If you add multiple addresses in the To address section and if any of the user email addresses are deactivated or invalid, the 机器人 will display an appropriate error message. |
| Fixes |
|---|
|
You can create a 机器人 using with OAuth2 PKCE flow, then use Save attachment 操作 in a Loop with an iterator as For each mail in mailbox. Previously, when you used Save attachment 操作 within a loop and if emails contained attachments with a colon character (:) in the attachment name, the 机器人 failed at the loop 操作 with an error. Service Cloud case ID: 01937048, 01911264, 01938122, 01943463, 01952184, 01959982, 01964181 |
|
You no longer encounter any issues when you use the 操作 with the EWS option and can perform email-related operations such as reading or sending emails. Previously, when you used 操作 from the 电子邮件 软件包, it was not working and threw a connection timeout if the proxy was configured. Service Cloud case ID: 01940196, 01937082, 01925438 |
| You can now use the Connect
操作 in the Email
软件包 along with other 操作 (such as
Reply or Forward) from the
same 软件包 in a 机器人 without any
issues. Service Cloud Case ID: 01908595 |