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

different SASL_username and Sender Addresses --- lot of spam originating from system

busyboy

New Pleskian
hi,


Currently we are facing a lot of email spam originating from our system. This is mainly happening as a legitimate spam as the SMTP Authenticated user is valid but the Actual difference is between the Sasl_username and the sender addresses. This ends up in a situation that we have to eliminate the actual sasl_username form our system after a long time spent on troubleshooting..

I have just seen some configs on plesk 11.5.30 which are used to allow the authenticated user but there is no rule to match the sasl_username and the sender address.

Code:
 # egrep "smtpd_sender_restrictions" *
main.cf:smtpd_sender_restrictions = check_sender_access hash:/var/spool/postfix/plesk/blacklists, permit_sasl_authenticated, check_client_access pcre:/var/spool/postfix/plesk/non_auth.re
master.cf:submission inet n - n - - smtpd -o smtpd_enforce_tls=yes -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination


it should be something like this ?

smtpd_sender_restrictions = reject_authenticated_sender_login_mismatch

please suggest.

Regards,
 
Back
Top