hi Tom
A lot happens. There are actually four different virtual fields for handling different scenarios. In each case, you map a text field that has a MIME encoded email to the virtual field. Inaport will parse the MIME text and extract various fields from the message header (date, subject, to, from, cc, bcc) and the message body (message text, attachments) then seek to set up one or more history records and attachment records. Ata a minimum, a history record will be created for the parent account or contact matched by the profile.
-
vf_MimeEmail - map a mime encoded email to this field
Inaport will scan the email addresses found in the to/from/cc/bcc fields, and try to identify matching contacts. A history record will be created for each contact found, with the body of the email and the attachements.
-
vf_GoldMineMimeEmail - for handling MIME emails from a GoldMine database
As for vf_MimeEmail, but customised to handle the non-standard elements of a GoldMine email. In particular, HTML email text is converted to plain text, and attachments are handled correctly. In a GoldMine email, the attachments are not stored in the body of the email; instead, a link is provided to a file on disk.
-
vf_MimeEmailSingle - only create one history record
As for vf_GoldMineMimeEmail, but only create a single history record linked to the parent account or contact matched by the profile, instead of creating a history record for each of the to/from/cc/bcc email contacts.
-
vf_MimeEmailSingleNoError
As for vf_MimeEmailSingle, but if there is an error when parsing the email, write a history record with the error message instead of logging an error and throwing the email away.
Hope that helps. Any further questions, please ask.
Regards
Admin