Main Page: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
==portMTA Documentation== | ==portMTA Documentation== | ||
<!--*[[portMTA 2.0]]: Documentation for portMTA 2.0 --> | <!--*[[portMTA 2.0]]: Documentation for portMTA 2.0 --> | ||
*[[portMTA 1.5]]: Documentation for portMTA 1.5. Our unique mta now supports warming ip addresses automatically. | |||
*[[portMTA 1.4]]: Documentation for portMTA 1.4. Our state of art core engine now supports On-Disk Message Encryption, Actions and DelOrch (Our unique Deliverability Orchestration) server. | *[[portMTA 1.4]]: Documentation for portMTA 1.4. Our state of art core engine now supports On-Disk Message Encryption, Actions and DelOrch (Our unique Deliverability Orchestration) server. | ||
<!--*[[portMTA 1.3]]: Documentation for portMTA 1.3--> | <!--*[[portMTA 1.3]]: Documentation for portMTA 1.3--> | ||
Revision as of 10:09, 21 July 2019
portMTA is the high-scale robust multi-channel messaging product who can send millions messages in an hour with using the best rules of delivery in order to boost deliverability.
portMTA Documentation
- portMTA 1.5: Documentation for portMTA 1.5. Our unique mta now supports warming ip addresses automatically.
- portMTA 1.4: Documentation for portMTA 1.4. Our state of art core engine now supports On-Disk Message Encryption, Actions and DelOrch (Our unique Deliverability Orchestration) server.
Deliverability Orchestration Server (DelOrch) documentation
- DelOrch 1.4: Documentation for DelOrch