This topic describes how you can set up and convert an unread email from the email server to an event.
The BMC ProactiveNet Server connects to the email server periodically using the configured credentials to retrieve unread emails. These unread emails are then converted into events. The subject of the email received is updated in the Message slot of the event and the content of the email is updated in the Notes slot of the event.
Only an email in plain text format or HTML format can be set as an event. For email in HTML format, only the content is extracted and the tags are removed. If an email has both plain text and HTML formats, then the text of the content that appears first in the email is converted as an event.
The severity of the event is determined from the content of the email, if it has any of the following keywords:
If both the keywords are missing, then the default configured severity value, INFO is used. The following severity values are also supported:
Only unread emails that are in the configured folder of the email server are read. By default, only emails in the Inbox folder are configured in the pronet.conf property file. The following properties can be configured in the pronet.conf property file:
pronet.email2event.mailserver.fqdn=<email server> Example: pronet.email2event.mailserver.fqdn=webmail.bmc.com pronet.email2event.mailserver.port=143 pronet.email2event.protocol=imap pronet.email2event.mailserver.username=<user name> Example: pronet.email2event.mailserver.username=admin pronet.email2event.mailserver.password=<encrypyted password> Example: pronet.email2event.mailserver.password=f39/f39/f39/fwAAAAhR24CYnPkOfQAAAAimhWFrWlxR2gAAABRshU+jLugl4q2TVChVh2ZqKUojUg== pronet.email2event.folder=inbox pronet.email2event.delete.read.messages=true pronet.email2event.mailbox.scan.frequency.mins=5 pronet.email2event.enabled=false pronet.email2event.default.severity=INFO
You can enable this feature by setting the following property value in the pronet.conf property file to "true". By default, this value is set to "false":
pronet.email2event.enabled=true
You can create a folder in the email server and configure rules to direct the email to this folder. To convert unread email in the folder to events, you must configure the folder name in the pronet.conf property file:
pronet.email2event.folder=<unread email folder>
By default, the ProactiveNet Server scans the mail box in every 5 minutes. Emails that are already read, or are in draft or deleted modes are not considered.
Emails, which are already read by the server are marked as "seen" and are deleted from the email server. You can prevent the email from being deleted by disabling the configuration in the pronet.conf property file:
pronet.email2event.delete.read.messages=false
All other Multipurpose Internet Mail Extensions (MIME) content such as attachments, images, and so on are ignored.
You can configure an email as an event through the command line interface by running the pw email2event
command:
pw email2event usage: pw email2event [-y]|[-c]|[-s]|[-e]
The following table lists the parameters available in the pw email2event
command :
Options | Description |
---|---|
-y | Encrypts the mailbox password. |
| Configures email as event. |
-s | Starts scanning email as event. |
-e | Stops scanning email as event |
pw email2event -y
pronet.email2event.mailserver.password
property.Open the pronet.conf file and configure the following properties. Examples provided below:
pronet.email2event.mailserver.fqdn=webmail.bmc.com
pronet.email2event.mailserver.username=admin
pronet.email2event.mailserver.password=f39/f39/f39/fwAAAAhR24CYnPkOfQAAAAimhWFrWlxR2gAAABRshU+jLugl4q2TVChVh2ZqKUojUg==
pronet.email2event.delete.read.messages=false
pronet.email2event.mailbox.scan.frequency.mins=5
pronet.email2event.enabled=true
pw sys start
14 Comments
Tim Bocardo
Why only severity of INFO, MINOR, MAJOR and CRITICAL. Why not OK and WARNING?
OK is especially needed, as it is used to clear older events when the problem is resolved.
Patrick Mischler
Hi there
Is there an answer to the comment of Timothy Bocardo?
WARNING and OK are also the need on our side.
Regards,
Patrick
Panna Hegde
The R&D teams are working on the functionality for the OK and WARNING states. Once the functionality is implemented, I shall update the documentation.
Patrick Mischler
I've got this working. But why is the CLASS of the event "Cell Undefined Class"?
Panna Hegde
Hi Patrick,
The R&D teams are working on this. They plan to release a hotfix for this sometime next week.
Thanks,
Panna
Harshal Pandule
The medium severity is not defined in BPPM/TS 9.5 and onwards, please see below the severity definition in mc_root_internal.baroc file :
ENUMERATION SEVERITY
10 UNKNOWN
20 OK
30 INFO
40 WARNING
50 MINOR
60 MAJOR
70 CRITICAL
END
Therefore Out of the box, the Email to event feature will not create a Medium severity event.
Andy Scholebo
Vandana Ramnani
Hi Panna,
Was there a fix for this? Also is there a limit for number of mailboxes we can scan using this feature? I mean in terms of load how much can we configure for the cell to work well?
Thanks,
vandana
Patrick Mischler
In TrueSight 10.5 the events created by email 2 event are comming with the event class "EMAIL2EVENT".
Harshal Pandule
Correction to Panna's comments above :
The medium severity is not defined in BPPM/TS 9.5 and onwards, please see below the severity definition in mc_root_internal.baroc file :
ENUMERATION SEVERITY
10 UNKNOWN
20 OK
30 INFO
40 WARNING
50 MINOR
60 MAJOR
70 CRITICAL
END
Therefore Out of the box, the Email to event feature will not create a Medium severity event.
Javier Hernandez
Sanjay Prahlad
Javier Hernandez
Sanjay Prahlad