« Previous | Next»

Making the Same Errors.

Posted by coldtobi | 2 Aug, 2007, 07:46 My old hoster had a problem with his smtp-configuration: Using a smart-host-setup, the server needs authentification, to avoid being misued as a spam relay. And that is good that way.

My mail server (@ localhost), on the other side, refuses to authenticate against a server if the server is using some authentification method on which a plaintext password is transfered unencrypted. And that is good that way.

Anzeige

It took some mails and posts in the forum, till the old hoster reacted and solved the problem. I suggested to him using TLS or at least CRAM-MD5, and he was going for the TLS. And that was good that way.

Unfortunatly, since the move, the security and pricacy of my password is gone again. The new hoster did the same misconfiguration as the old one:

~$: telnet coldtobi.de smtp
Trying 80.190.144.123...
Connected to coldtobi.de.
Escape character is '^]'.
220 sv13.net-housting.de ESMTP Postfix (Debian/GNU)
EHLO frost.de
250-sv13.net-housting.de
250-PIPELINING
250-SIZE 30102400
250-VRFY
250-ETRN
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN

No STARTTLS is offered, and the (only) advertised AUTH mechanism are "login" and "plain", both sending unencrypted passwords.

I asked them to fix this, but got no response up to now. Hopefully, this time, this is not gonna need multiple mails to convince them to use secure logins.

 

 



<—&mdash Showing ERROR? Click here!


Blog and Website | Comments (0) | Trackbacks (0)

Related Articles:

0 Comments | "Making the Same Errors." »

Add comment

 

 This is the ReCaptcha Plugin for Lifetype

Due to German legislation, all comments are moderated. If you get NO error message, your comment is accepted by the system and will be released at the earliest opportunity. Sorry for the inconvenience this might cause.

Inappropiate comments might be edited or not accepted.