• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

force SMTP authentication

B

Brugnara

Guest
It is possible to force SMTP auth. ?

We use different connection for public servers (MX record) on different IP and We use dedicated ports of Plesk-Qmail for our Client SMTP Relay server.

But for a Spammer is possible to connect and sent SPAM to local domains.

With a forced authentication this problem will to resolve.

Is there a method?

best regards
Brugnara
 
No, if you use different ports of incoming call and the filter control the incoming port (TCPLOCALPORT).

For example:
# File /etc/services
smtp25025 25025/tcp mail

# File /etc/inetd.conf
smtp25025 stream tcp nowait.1000 root /var/qmail/bin/tcp-env tcp-env -Rt0 /usr/sbin/rblsmtpd -b -r sbl-xbl.spamhaus.org -r your.rbl /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true

Plesk qmail implements qmail-spp (http://qmail-spp.sourceforge.net/doc/) and I was experiment the plugin authrequired pathed with control of env TCPLOCALPORT, but environment variable SMTPAUTHUSER is non every time filled, because the program /var/qmail/bin/relaylock, I think, it use a database of client's IP and authentication is performed only once in a range of some connection period.

best regards
Brugnara
 
Back
Top