|
|
| Line 6: |
Line 6: |
|
| |
|
| Please test config information before submitting it, if at all possible (although untested data is better than no data). You are probably in the best position to try this, as other project participants won't have accounts with this ISP. | | Please test config information before submitting it, if at all possible (although untested data is better than no data). You are probably in the best position to try this, as other project participants won't have accounts with this ISP. |
|
| |
|
| |
| = Some details =
| |
|
| |
| == Enable URL ==
| |
|
| |
| Some providers do not provide IMAP or POP service by default, but require it to be enabled via a web UI. Paste the URL that a logged-in user would use into this field, and the application can prompt the user to visit it.
| |
|
| |
| == Secure Auth ==
| |
|
| |
| 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></code> (preferred) or <code>telnet <i>hostname</i> <i>port</i></code> as "client".
| |
|
| |
| * 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 <code>* OK mwinf2j04 IMAP4 server ready</code> or similar, enter <code><b>1 CAPABILITY</b></code>, hit return.
| |
| * 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 <code>CRAM-MD5</code> or <code>DIGEST-MD5</code> or (for POP) <code>APOP</code> in the response, the server should support "secure auth". If you <i>only</i> see <code>AUTH</code> <code>LOGIN</code> and/or <code>PLAIN</code>, the server probably does not support secure auth.
| |