On 11/21/2007 07:40 AM, Jean-Paul van de Plasse wrote:
Hi Adam,
This seems to work :
Change the /bin/true to /bin/false in your /var/qmail/supervise/smtp/run
JP
What I am trying to do is block unencrypted authentication requests from
users trying to send outbound mail. I want to force them to have to use
the SSL service I've setup on port 465. As it stands, customers could
use unencrypted authentication even though I've provided a secure
option. I want to make that unavailable to them.
JP,
Thanks for your suggestion.
So I just tried "/bin/false", and you are right in that it causes
authentication to fail on port 25. However, smtpd still advertises "250
AUTH LOGIN PLAIN CRAM-MD5" which is verified by telnetting to port 25.
This means that MUA's will still try to auth and send credentials
unencrypted over the wire AFAICT. This is verified by tailing
/var/log/maillog while trying to auth (I can see the connection attempts).
Setting AUTH=0 on my qmailrocks machine causes smtpd to no longer
advertise auth at all, and MUA's detect this and drop the connection
with an error before any credentials are sent. This is the setup I am
trying to replicate with QMT: to get smtpd on port 25 to not advertise
auth at all.
Any other ideas by anyone?
Adam
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
