• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Safe to enable postgrey with free Plesk Email Security (Amavis + SpamAssassin + ClamAV)?

Jürgen_T

Regular Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian v18.0.68_build1800250319.12 os_Ubuntu 22.04
Hi everyone,
I'm running a Plesk server using the free Plesk Email Security extension, which includes Amavis and SpamAssassin. I’ve also installed ClamAV manually, and it's working perfectly within the current mail pipeline.
To further reduce spam and bot traffic, I now plan to add Greylisting via postgrey.
Here’s the setup:
  • Mail server: Postfix
  • Content filter: smtp-amavis:[127.0.0.1]:10024 (unchanged)
  • No Rspamd in use
  • Greylisting configuration (planned):
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
check_policy_service inet:127.0.0.1:10023,
reject_unauth_destination

postgrey will be limited to unauthenticated external traffic, and I’ll monitor logs closely. Everything else, including Amavis and ClamAV, should remain untouched.


Are there any known conflicts or caveats when using postgrey alongside Plesk’s free mail security stack (Amavis + SpamAssassin + ClamAV)?
Any experience or advice would be much appreciated before I go ahead.


Thanks a lot in advance!
 
caveats?
long delivery delays for inbound messages and you'll need to closely monitor the mail flow and manage the ever increasing whitelist for your Postgrey daemon.
the practical benefit of greylisting is also pretty much non-existing nowadays...

IMHO you're better off implementing Postscreen on your server.
Similar approach and usefulness as greylisting, but less intrusive and with near zero caveats.
 
Back
Top