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

Smtp autentication can't be disabled

musictus

Basic Pleskian
Hello

I run Plesk Panel 11.0.9.

Discovered that email users can authenticate on server and send mail via smtp, while I have both "message submission" disabled and "Relaying" closed.

How to block this smtp authentication server wide, or on a single domain?

Thanks!
 
---------------------------------------------------------------
PRODUCT, VERSION, MICROUPDATE, OPERATING SYSTEM, ARCHITECTURE
Plesk Panel 11.0.9 Update #51, CentOS 5.9, GenuineIntel, Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz

PROBLEM DESCRIPTION
Email users can log into server and send email via smtp, while "Enable message submission" is disabled and "Relaying" closed.

STEPS TO REPRODUCE
Sending email via client from wa@domain.com to walter@domain.it, using SMTP authentication

ACTUAL RESULT
May 22 11:49:55 server6 cmd5checkpw: SMTP connect from ip-244-225.sn1.eutelia.it [xxx.xxx.244.225]
May 22 11:49:55 server6 cmd5checkpw: SMTP user wa@domain.com: logged in from ip-244-225.sn1.eutelia.it [xxx.xxx.244.225]
May 22 11:49:55 server6 spamdyke[32720]: ALLOWED from: wa@domain.com to: walter@domain.it origin_ip: xxx.xxx.244.225 origin_rdns: ip-244-225.sn1.eutelia.it auth: wa@domain.com encryption: TLS
May 22 11:49:56 server6 qmail-queue-handlers[403]: Handlers Filter before-queue for qmail started ...
May 22 11:49:56 server6 qmail-queue-handlers[403]: from=wa@domain.com
May 22 11:49:56 server6 qmail-queue-handlers[403]: to=walter@domain.it
May 22 11:49:56 server6 qmail-queue-handlers[403]: handlers_stderr: SKIP
May 22 11:49:56 server6 qmail-queue-handlers[403]: SKIP during call 'check-quota' handler
May 22 11:49:56 server6 qmail: 1369216196.325540 info msg 3312388: bytes 456 from <wa@domain.com> qp 405 uid 2020
May 22 11:49:56 server6 qmail-queue-handlers[403]: starter: submitter[405] exited normally
May 22 11:49:56 server6 qmail: 1369216196.338452 starting delivery 49815: msg 3312388 to remote walter@domain.it
May 22 11:49:56 server6 qmail-remote-handlers[406]: from=wa@domain.com
May 22 11:49:56 server6 qmail-remote-handlers[406]: to=walter@domain.it
May 22 11:49:57 server6 qmail: 1369216197.625346 delivery 49815: success: 204.15.54.12_accepted_message./Remote_host_said:_250_2.0.0_Ok:_queued_as_3DE5412B0015/

EXPECTED RESULT
We expect that email users cannot login to server and are not permitted to send email via SMTP

ANY ADDITIONAL INFORMATION
--------------------------------------------------------------
 
Thank you. I have forwarded this to developers for investigation. I will update thread with results as soon as I receive them.
 
Sorry for dumb question, musictus, but why do you have email users in the first place? What purpose do they serve? Mail forwarding?
 
Bug has not been reproduced.

Send with auth required:

% msend 10.52.68.129 out auth
Creating connection to host (10.52.68.129:25)
[<-] 220 a10-52-68-129.qa.plesk.ru ESMTP
[->] EHLO test1.domain.com
[<-] 250-a10-52-68-129.qa.plesk.ru
[<-] 250-AUTH=LOGIN CRAM-MD5 PLAIN
[<-] 250-AUTH LOGIN XXXXXXXXXX
[<-] 250-STARTTLS
[<-] 250-PIPELINING
[<-] 250 8BITMIME
[->] XXXXXXXXXX
[<-] 334 UGFzc3dvcmQ6
[->] cmVwb3J0
[<-] 235 go ahead
Authentication succeded [admin@test.domain.com]
[->] MAIL FROM:<admin@test.domain.com>
[<-] 250 ok
[->] RCPT TO:<sov@els23.com>
[<-] 250 ok
Recipient accepted [sov@els23.com]
[->] DATA
[<-] 354 go ahead
[->] Received: by test1.domain.com (nbSMTP-1.00) for uid 1001
[<-] 250 ok 1370405560 qp 17221
[->] QUIT
[<-] 221 a10-52-68-129.qa.plesk.ru
Mail sent for admin@test.domain.com. Closing connection

Send with close relay:

% msend 10.52.68.129 out auth
Creating connection to host (10.52.68.129:25)
[<-] 220 a10-52-68-129.qa.plesk.ru ESMTP
[->] EHLO test1.domain.com
[<-] 250-a10-52-68-129.qa.plesk.ru
[<-] 250-AUTH=LOGIN CRAM-MD5 PLAIN
[<-] 250-AUTH LOGIN XXXXXXXXXX
[<-] 250-STARTTLS
[<-] 250-PIPELINING
[<-] 250 8BITMIME
[->] XXXXXXXXXX
[<-] 502 unimplemented (#5.5.1)
The server rejected the authentication method
Server said: 'unimplemented (#5.5.1)'
Error in send_mail
Mail NOT sent.

That port did you send a message from?
 
Back
Top