• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Configure Plesk hosted domain for use with Postini

A

Andrew R. Grant

Guest
Hi,

We are looking into using Postini mail filtering service with a Plesk hosted domain.

The inbound routing is trivial (simply change the MX records). The outbound side of things seems to be complicated. Does anyone know how to do this?

From the Postini documentation, this involves:
1) Allowing their servers to re-inject mail on our server
2) Setting up a Qmail smart host for the domain in question

Postini documentation:
http://www.postini.com/webdocs/outbound/en/outbound_config_en.pdf

Notes:
- Qmail documentation starts at page 133

Thanks,
Andrew
 
I too am curious if you ever got this working.

Also, what was your pricing structure with Postini? Could you run all mailboxes through it at one price or did you have to pay per-mailbox?

Thanks
DC
 
Back
Top