Sent Items Update
In this article you will learn more about the Sent Items Update service of CodeTwo Email Signatures for Office 365.
- How to turn on Sent Items Update
- Updating sent items for users with delegate (Send As / Send on Behalf) permissions
As signatures/disclaimers are added to sent emails directly by the CodeTwo Email Azure Service, they are not visible in the mailboxes' Sent Items folders. To let you see the signatures in the sent mail folders, we have equipped CodeTwo Email Signatures for Office 365 with the Sent Items Update (SIU) feature that updates your sent messages with signatures after processing by the program. The Sent Items Update works as a separate service and it is installed along with the CodeTwo Email Azure Service.
Sent Items Update is hosted on MS Azure servers. The service is totally independent of your mail flow and the functioning of your Office 365 tenant, which means it has no influence on your email processing and delivery time. Your emails are not stored anywhere. Moreover, Sent Items Update does not require any service accounts to operate as the entire authentication and authorization process uses OAuth 2.0.
By default, the Sent Items Update service is disabled and needs to be enabled by an admin in the CodeTwo Admin Panel to start updating sent emails.
The Sent Items Update works per tenant, i.e. you have to turn it on for each tenant separately.
To enable the Sent Items Update:
- Log in to your CodeTwo Admin Panel.
- Enter the management pages of a chosen tenant by clicking the Manage tenant () button next to the tenant's name.
- Go to the Sent Items Update section (Fig. 1.) and click Turn on.
If you do not see the Sent Items Update section, contact CodeTwo Support.
|Fig. 1. Enabling SIU in CodeTwo Admin Panel.|
- Log in using your Office 365 tenant global admin credentials.
- Accept the permissions required for the CodeTwo SIU installer.
- The Sent Items Update should start working within a few minutes.
Be aware that the updating process starts after an email is passed to EOP, so it may take from a few to over a dozen seconds before a user sees an updated message in the Sent Items folder.
Also, note that the SIU service only updates messages in the original Sent Items folder. If a user has any OWA/Outlook rules enabled that instantly move messages from the Sent Items folder somewhere else (including the subfolders of the Sent Items folder), the SIU service will not be able to find and process them. If possible, execute such rules manually or with a delay, to allow some time for the SIU service to update your sent emails.
SIU updates messages in the Sent Items folder of a person who appears to be the sender:
- If User A has the Send As permission to the User B's mailbox, and when sending a message User A enters User B's email address into the From field, the message will be considered as sent by User B. Therefore, the rules covering User B will be executed and the SIU service will update the message in the Sent Items folder of User B.
- If User A has the Send on Behalf right on User B's mailbox and when sending a message User A enters the email address of User B into the From field, the message will be considered as coming from User A, and the rules covering User A will be executed. The SIU service will update the Sent Items folder of User A.
If you already enabled the Sent Items Update service and the messages are not updated, follow the steps below.
- Check with the recipient if the sender's emails are stamped with signatures at all, to rule out improper signature rules or connectors' configuration as a source of the problem. Also, check the service's status.
- Log in to Outlook on the web (OWA) to access your Sent Items folder directly on the server. If you see that messages are updated in the Sent Items folder in OWA, this means the service is working properly and the problem lies in your email client.
If you use Microsoft Outlook, emails in your Sent Items folder might not always be refreshed and displayed correctly. This is usually caused by Outlook's default behavior in the Cached Exchange mode, and is not related to the SIU service. See this article to learn how to solve this problem.