• 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.

Qmail instances to manage greylisting

N

neusagudo

Guest
Hi everyone!

I wanted to know how to make double qmail instances like this:

mailin.domain.com (SMTPIn,POP,IMAP conections only), listening on standard port
mailout.domain.com (SMTP Out conections with SMTP-AUTH Only) sending through non-standard port

So that I can put mailin.domain.com under qgreylisting.

I have used qgreylisting before but it doesn't really work with SMTP-AUTH, and I cannot stop using that nor either change to another method like Pop before SMTP.

I have tried to search for information on this subject, but didn't really find much. I think separating the 2 services would be a nice solution for people wanting to use qgreylisting and not stopping using smtp-auth.

Any ideas on that??

Thanks,
 
Back
Top