Confirmed users
596
edits
m (→Secure Auth) |
m (→Secure Auth) |
||
| Line 29: | Line 29: | ||
This is whether the password must be sent in clear or can be encrypted (hashed via MD5). | This is whether the password must be sent in clear or can be encrypted (hashed via MD5). | ||
To find out manually, you can contact the server directly and talk the POP/IMAP/SMTP protocol manually. Use <code>netcat -v <i>hostname</i> <i>port</i> (preferred) or <code>telnet <i>hostname</i> <i>port</i> as "client". | To find out manually, you can contact the server directly and talk the POP/IMAP/SMTP protocol manually. Use <code>netcat -v <i>hostname</i> <i>port</i></code> (preferred) or <code>telnet <i>hostname</i> <i>port</i></code> as "client". | ||
* POP3: when you see | * POP3: when you see <code>+OK WEB.DE POP3-Server</code> or similar, enter <code><b>CAPA</b></code>, hit return. | ||
* IMAP: when you see | * IMAP: when you see <code>* OK mwinf2j04 IMAP4 server ready</code> or similar, enter <code><b>1 CAPABILITY</b></code>, hit return. | ||
* SMTP: when you see | * SMTP: when you see <code>220 mail.gmx.net GMX Mailservices ESMTP</code> or similar, enter <code><b>EHLO example.net</b></code>, hit return. | ||
In all cases, if you see | In all cases, if you see <code>CRAM-MD5</code> or <code>DIEGST-MD5</code> in the response, the server should support "secure auth". If you only see <code>AUTH</code> <code>LOGIN</code> and/or <code>PLAIN</code>, the server probably does not support secure auth. | ||
==== Test ==== | ==== Test ==== | ||