Difference between revisions of "IPortalDoc External MailServer Integration"
From wiki.IPBRICK.COM
m |
m |
||
| Line 6: | Line 6: | ||
** SMTP route - it is feasible to implement a SMTP route | ** SMTP route - it is feasible to implement a SMTP route | ||
* 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 and download , SMTP route is not an option, it is not feasible to implement a SMTP route |
= INTERNAL - SMTP Route = | = INTERNAL - SMTP Route = | ||
In this scenario we will configure a SMTP route for iPortalDoc. | 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 | # all mails destinated to "@iportaldoc.yourdomain.com" are to be smtp routed to iPortalDoc server | ||
| − | + | ||
| + | == Filters == | ||
Revision as of 18:06, 16 January 2018
This page goal is to demonstrate how to integrate iPortalDoc with another mailserver.
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
- 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 and download , SMTP route is not an option, it is not feasible to implement a SMTP route
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
