SMTP Archiving Service

Last Updated : Oct 09, 2020 |
Prolog information
Metadata
Keywords:
The SMTP Archiving Service archives Multimedia Messaging conversations to an SMTP server. The archived data includes text messaging and multimedia attachments posted in a conversation session. A Multimedia Messaging conversation is archived as number of conversation snippets. Conversation snippets cover a time interval from the conversation start to the conversation end. A single conversation is archived as multiple conversation snippets that belong to the same conversation and can be aggregated using the conversation ID or thread ID. Each conversation snippet is equivalent for sending an email to the SMTP server. Global Relay Archive is the supported archiving service from the Presence Services SMTP Archiving Service.
An archived email has the following structure:
  • Subject: Contains the conversation ID or thread ID, the number of participants, the number of messages, and the duration of the conversation in minutes.
  • From: Contains the client that created the conversation.
  • To: Contains all participants of the conversation. For more information, see the To: field description in RFC 2822.
  • RCPT TO Header address: The RFC 2821 message envelope recipient. For more information, see configuration of the SMTP RCPT TO Header.
An email that archives a conversation can contain one or more conversation snippets. Each snippet includes the following components:
  • Conversation Summary:
    • Conversation ID.
    • Subject: If the conversation has no subject, this field can be empty.
    • Start Time: If the conversation snippet contains the Conversation started event, then this field shows the timestamp of the Conversation started event. If the conversation snippet has no Conversation started event, the Start Time is the timestamp of the scheduled archiving timestamp.
    • End Time: If the conversation snippet has the Conversation closed event, the End Time is the timestamp of the Conversation closed event.
  • Conversation Events:
    • Conversation started event: Identifies the conversation started event.
    • Message sent event: Identifies the text message or attachment delivery event.
    • User joined conversation event: Identifies that a participant joined the conversation. The event contains information about the inviter and who joined the conversation.
    • User left conversation event: Identifies who left the conversation.
    • Conversation subject change event: Identifies a new conversation subject and the person who changed the subject.
    • Conversation closed event: Identifies the conversation closed event.
  • Conversation Activities:
    • Message sent activity: Contains information about the message sender and the time when the message was sent. This activity also applies to sending multimedia attachments.
    • Message retrieved activity: Contains information about the message recipient and the time when the message was retrieved.
    • Message read activity: Contains information about the message recipient who marked the message as read. The activity also contains information about the time when the message was read.
    • Attachment retrieve activity: Contains information about the person that retrieved the attachment and the time when the attachment was retrieved. The activity also has a reference to the attachments of the archived email.
Note:
Only Avaya Workplace Client clients that participate in a conversation support all the listed events and activities. Other clients might not support certain events or activities.
By default, the SMTP Archiving Service is disabled. For more information about configuration, see Configuring the SMTP archiving service.
Note:
You can only use either SMTP Archiving or Message Archiver. You can not use both Message Archiver and SMTP Archiving services at the same time.
When the SMTP archiving service is enabled, the service temporarily stores the archiving data in the local database. The Archiving Schedule attribute sets the time of day when the archiving is scheduled. On scheduled archiving, conversation snippets are built as archived emails, and then emails are delivered to the SMTP server. If the archived email delivery is successful, all temporary data is cleared. If the archived email delivery is unsuccessful, then Presence Services do the following:
  • Raises a major alarm, SMTP archiving upload failed.
  • All the data is kept for re-delivery of the conversation snippet or email.
If the archived email delivery is successfully delivered during the next scheduled upload, the major alarm is cleared.
If the problem persists for the SMTP Upload Failures Threshold period, Presence Services raises a critical alarm, SMTP archiving service is disabled. In this case, all previously archived conversation snippets are retained. All subsequent conversation events and activities, however, are no longer archived. After the critical alarm is raised, on each scheduled archiving, Presence Services tries to deliver previously archived conversation snippets to the SMTP server. If the delivery is successful, the SMTP Archiving Service resumes normal operation.
Related links
Configuring the SMTP archiving service