You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Markus Müller <dj...@yahoo.com> on 2010/01/23 12:05:01 UTC
others than PLAIN
Hello,
if is possible that the passwort which crossed the internet to logon via POP3, IMAP or SMTP_AUTH is secured instead PLAIN ?
as example: CRAM MD5, SHA, etc. ?
greets,
Markus
__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com
Re: others than PLAIN
Posted by Norman Maurer <no...@googlemail.com>.
+1,
looking forward to contributions ;)
Bye,
Norman
2010/1/23 Stefano Bagnara <ap...@bago.org>:
> 2010/1/23 Markus Müller <dj...@yahoo.com>:
>> Hello,
>>
>> if is possible that the passwort which crossed the internet to logon via POP3, IMAP or SMTP_AUTH is secured instead PLAIN ?
>> as example: CRAM MD5, SHA, etc. ?
>
> Unfortunately the fact that we store password encrypted does not allow
> use to support more secure authentication types. In order to support
> different authentication methods we would need to change much more in
> internal code.
> Contribution is welcome, in the mean time use of ssl is the best choice.
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: others than PLAIN
Posted by Stefano Bagnara <ap...@bago.org>.
2010/1/23 Markus Müller <dj...@yahoo.com>:
> Hello,
>
> if is possible that the passwort which crossed the internet to logon via POP3, IMAP or SMTP_AUTH is secured instead PLAIN ?
> as example: CRAM MD5, SHA, etc. ?
Unfortunately the fact that we store password encrypted does not allow
use to support more secure authentication types. In order to support
different authentication methods we would need to change much more in
internal code.
Contribution is welcome, in the mean time use of ssl is the best choice.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org