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

Plesk / Postfix / SPF / DNSRBL

C

cwathan

Guest
Well, here's another one to the ***kers at sw-soft. I have sworn to myelf to be off this software within the next year due to lousy QC/QA, support & costing policies. But, until then I am stuck with their poorly written & test software & pay for support for items that shouldn't have even existed. Case in point, with 9.0.x.x & postfix, SPF & DNSRBL is ran against SASL authorized clients. Now, I had already corrected this one (I do love postfix). But, each update has included an update to Plesk mail support. Guess what? Each update nullified my fix. This is EXTREMELY annoying. I am tired of paying sw-soft for the privilege of being one of their suckered beta testers. I guess I'll be moving over to virtualmin sooner than I had expected if all of this continues. (And we know sw-soft, it's going to get worse.)

Oh well, that was my rant.
 
Forgot to post the fix...

I forgot to post the fix to the problem for any of you that may have ran across the same problem. In essence, the swsoft developers don't seem to know that the ORDER of configuration keys AND the ORDER of their options make a difference in postfix. (The options were put in the wrong order.)

smtpd_client_restrictions = permit_sasl_authenticated, reject_rbl_client zen.spamhaus.org


That will fix the problem with authenticated mail users being blocked by spamhaus' dynamic IP block list.

Regards,
Chris
 
Back
Top