Difference between revisions of "IPortalDoc External MailServer Integration"
From wiki.IPBRICK.COM
(Created page with "This page goal is to demonstrate how to integrate iPortalDoc with another mailserver. == Scenarios == We will analyse the following scenarios: * INTERNAL - mailserver is in t...") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This page goal is to demonstrate how to integrate iPortalDoc with another mailserver. | This page goal is to demonstrate how to integrate iPortalDoc with another mailserver. | ||
| + | = Introduction = | ||
| + | |||
| + | == iPortalDoc e-mail integration features == | ||
| + | iPortalDoc supports the following email integration features: | ||
| + | * workflows - ''WORKFLOW_NAME@iportaldoc.yourdomain.com'' | ||
| + | ** start a new document workflow using the attached file in the incoming e-mail to the WORKFLOW_NAME | ||
| + | * associated e-mails - default ''REF<document_code>'' | ||
| + | ** all e-mails transported through yourcompany mail server, that have ''REF<document_code>'' in the subject and/or in the body, should be copied, archived in iPortalDoc and associated to the document with ''document_code'' | ||
| + | * DBDOCMAILS module | ||
| + | ** selected emails are to be processed by iPortalDoc - to be used to start a new document workflow | ||
| + | * MAIL ARCHIVING | ||
| + | ** all emails from selected mailboxes are to be processed/archived by iPortalDoc | ||
| + | |||
== Scenarios == | == Scenarios == | ||
We will analyse the following scenarios: | We will analyse the following scenarios: | ||
* INTERNAL - mailserver is in the LAN, or it is in a private routed network, it has connectivity with the iPortalDoc server | * INTERNAL - mailserver is in the LAN, or it is in a private routed network, it has connectivity with the iPortalDoc server | ||
| − | ** SMTP route - it is feasible to implement a SMTP route | + | ** SMTP route - it is feasible to implement a SMTP route, so we will prefer this connection type |
* EXTERNAL - mailserver is not in a private routed network, it does not have connectivity with the iPortalDoc server - generic or cloud scenarios | * EXTERNAL - mailserver is not in a private routed network, it does not have connectivity with the iPortalDoc server - generic or cloud scenarios | ||
| − | ** SMTP route - | + | ** POP Connector / fetchmail - mails are delivered in a specific mailbox, iPortalDoc server will download the messages using fetchmail |
| + | |||
| + | |||
| + | = INTERNAL - SMTP Route = | ||
| + | In this scenario we will configure a SMTP route for iPortalDoc. | ||
| + | # all mails destinated to "@iportaldoc.yourdomain.com" are to be smtp routed to iPortalDoc server | ||
| + | |||
| + | == Filters == | ||
| + | * workflows - this feature is automatically resolved by the smtp routed defined above, no additional settings are required | ||
| + | * associated e-mails - create an e-mail filter for: | ||
| + | ** e-mails that have expression REF< in the subject or in the body are to be BCC copied to "receivedmail@iportaldoc.yourdomain.com" | ||
Latest revision as of 18:38, 16 January 2018
This page goal is to demonstrate how to integrate iPortalDoc with another mailserver.
Contents
Introduction
iPortalDoc e-mail integration features
iPortalDoc supports the following email integration features:
- workflows - WORKFLOW_NAME@iportaldoc.yourdomain.com
- start a new document workflow using the attached file in the incoming e-mail to the WORKFLOW_NAME
- associated e-mails - default REF<document_code>
- all e-mails transported through yourcompany mail server, that have REF<document_code> in the subject and/or in the body, should be copied, archived in iPortalDoc and associated to the document with document_code
- DBDOCMAILS module
- selected emails are to be processed by iPortalDoc - to be used to start a new document workflow
- MAIL ARCHIVING
- all emails from selected mailboxes are to be processed/archived by iPortalDoc
Scenarios
We will analyse the following scenarios:
- INTERNAL - mailserver is in the LAN, or it is in a private routed network, it has connectivity with the iPortalDoc server
- SMTP route - it is feasible to implement a SMTP route, so we will prefer this connection type
- EXTERNAL - mailserver is not in a private routed network, it does not have connectivity with the iPortalDoc server - generic or cloud scenarios
- POP Connector / fetchmail - mails are delivered in a specific mailbox, iPortalDoc server will download the messages using fetchmail
INTERNAL - SMTP Route
In this scenario we will configure a SMTP route for iPortalDoc.
- all mails destinated to "@iportaldoc.yourdomain.com" are to be smtp routed to iPortalDoc server
Filters
- workflows - this feature is automatically resolved by the smtp routed defined above, no additional settings are required
- associated e-mails - create an e-mail filter for:
- e-mails that have expression REF< in the subject or in the body are to be BCC copied to "receivedmail@iportaldoc.yourdomain.com"
