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

Bug: DNSBL checks supersede SMTP-AUTH

G

goebelmeier

Guest
Hey folks,

i just migrated from Plesk 8.6.0 to 9.2.1 (and from qmail to postfix too) and had to recognize that every incoming email is checked against DNSBL. In my opinion this should only be done if there is no AUTH request sent by client. I had to remove all DNSBL blocking dynamic IPs to let my customers send email again.

Are there any other fixes yet, which allow me to enable my favourite blacklists again?

Regards, Timo
 
Hi,

I don't think that this is a bug. I also came across this when using SSL (I'm using qmail with tcp-env) and told my users to either:
a) Use their ISP mail relay host.
b) Get a fixed IP address or stop sending spam from their fixed IP address.

This is a very useful feature as it helps stop the flow of spam across the internet. Consider this... you have a customer who signs up with you and all is well for a few days.... They become infected with a trojan and are turned into a spam bot. All mail from their IP address is blocked except via your server. You get a rep as a spam relay.

If you want to examine further the arguments that are passed to tcp-env by xinetd see (for example) /etc/xinet.d/smtps_psa

As the post above also states, using the SMTP submission port also negates the DNSBL checks.
 
Last edited:
Back
Top