Facebook
Twitter- Server operating system version
- Ubuntu 22.04
- Plesk version and microupdate number
- latest
When using modern blacklists for SMTP servers, the RBL return codes can differ and depending on the return code, different actions shall be taken (in particular not all mails should be rejected in case a wrong return code is presented).
Issue A: Different return codes
For instance, SPAMHaus recommends the following postfix configuration: Spamhaus Project Public Mirrors using Postfix — Spamhaus Technology Documentation 2.0 documentation. Looks like the default Plesk settings do not consider such detailed return codes yet?
Issue B: Hide custom RBL domain names
In addition, when using personalized services such as Spamhaus DQS (Data Query Service (DQS) | Real-Time DNSBLs | Spamhaus Technology), the custom domain names used to query the RBLs should not be returned in error messages (to avoid overusage). Details on how to configure this are listed here: Configuring DQS on Postfix — Spamhaus Technology Documentation 2.0 documentation
Would be great if this is automatically included in Plesk (and if configuration changes in main.cf would be respected by Plesk).
@IgorG any ideas with that regard, in particular how Plesk treats issue A right now?
Issue A: Different return codes
For instance, SPAMHaus recommends the following postfix configuration: Spamhaus Project Public Mirrors using Postfix — Spamhaus Technology Documentation 2.0 documentation. Looks like the default Plesk settings do not consider such detailed return codes yet?
Issue B: Hide custom RBL domain names
In addition, when using personalized services such as Spamhaus DQS (Data Query Service (DQS) | Real-Time DNSBLs | Spamhaus Technology), the custom domain names used to query the RBLs should not be returned in error messages (to avoid overusage). Details on how to configure this are listed here: Configuring DQS on Postfix — Spamhaus Technology Documentation 2.0 documentation
Would be great if this is automatically included in Plesk (and if configuration changes in main.cf would be respected by Plesk).
@IgorG any ideas with that regard, in particular how Plesk treats issue A right now?
