On 03/16/2011 10:25 AM, Scott Hughes wrote:
-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: Wednesday, March 16, 2011 12:16 PM
To: [email protected]
Subject: [qmailtoaster] Re: IMAP Ports
On 03/16/2011 09:54 AM, Scott Hughes wrote:
-----Original Message-----
From: Eric Shubert [mailto:[email protected]]
Sent: Wednesday, March 16, 2011 11:43 AM
To: [email protected]
Subject: [qmailtoaster] Re: IMAP Ports
On 03/16/2011 09:28 AM, Scott Hughes wrote:
I can telnet in port 143 from inside and outside the server. I just
cannot
get logged in. It is like it is not accepting my password for some
reason.
I
have checked the imap4 and imap4-ssl logs and am not even seeing the
attempt. As soon as I change my port on the client side to 993 it works
perfectly. Here is my dovecot config:
## Dovecot configuration file
# Base directory where to store runtime data.
base_dir = /var/run/dovecot/
imap_client_workarounds = delay-newmail outlook-idle
# Protocols we want to be serving: imap imaps pop3 pop3s
# If you only want to use dovecot-auth, you can set this to "none".
protocols = imap imaps
##
## Logging
##
log_path = /dev/stderr
info_log_path = /dev/stderr
log_timestamp = ""
##
## SSL settings
##
#ssl_disable = no
ssl_cert_file = /var/qmail/control/servercert.pem
ssl_key_file = /var/qmail/control/servercert.pem
ssl_cipher_list = ALL:!LOW
verbose_ssl = yes
##
## Login processes
##
login_dir = /usr/local/var/run/dovecot/login
login_user = dovecot
login_process_per_connection = yes
login_processes_count = 3
login_max_processes_count = 128
login_greeting = Dovecot ready.
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
##
## Mailbox locations and namespaces
##
mail_location = maildir:~/Maildir
namespace private {
separator = .
prefix = INBOX.
inbox = yes
}
##
## Mail processes
##
verbose_proctitle = yes
first_valid_uid = 89
last_valid_uid = 89
##
## Authentication processes
##
disable_plaintext_auth = yes
auth default {
mechanisms = plain login digest-md5 cram-md5
passdb vpopmail {
args =
}
userdb vpopmail {
}
user = vpopmail
count = 1
ssl_require_client_cert = no
}
## END
Thanks,
Scott
Which dovecot version?
There are packages of dovecot-2.0.11 for CentOS/QMT in the QTP repo. You
can install it with yum. If you didn't install dovecot with rpm, you
should "make uninstall" it first.
That being said, I'm guessing that your client doesn't have TLS or
secure logins enabled with port 143. Since you have
"disable_plaintext_auth = yes", dovecot will not allow logins with
passwords that are sent in the clear (which is a good thing). To use
port 143, clients need either secure logins (cram-md5) or TLS enabled.
TLS is preferred, as it will encrypt the entire connection. Note, that
TLS on port 143 is also preferred over IMAP/SSL on port 993.
I realized that I was looking in the wrong log file (I wasn't looking in
the
dovecot log file). Here is what I am getting in the dovecot log file that
I
think is relevant:
@400000004d80ea1a1a57ef44 imap-login: Info: Disconnected (auth failed, 5
attempts): method=DIGEST-MD5, rip=66.255.244.194, lip=66.255.244.196
Should I enable the method of DIGEST-MD5 in my config file?
My version of dovecot is: Info: Dovecot v1.2.3 starting up
Thanks,
Scott
I'm not sure if vpopmail can handle digest-md5 or not. I would try with
plain/TLS. That should work. If it doesn't, I'd try cram-md5.
(FWIW, Outlook'03 cannot do TLS, so SSL or cram-md5 is needed with that).
As I said in the other post, the client is Outlook 2008. I cannot find how
to change the auth method. Outlooks only allows for 'None, TLS, SSL, Auto'.
My goal here is to avoid have to go to each PC and smart phone to change
their settings.
Thanks,
Scott
I realize that you said Outlook'08. I simply included O'03 comment for
posterity, hence the FWIW and (). ;)
I don't have access to an Outlook'08 machine, so I can't be too
specific. IIRC though, in addition to the encryption setting
(None/TLS/SSL/AUTO), there is a "Use Secure Login" checkbox. This box
should be unchecked. I'm not sure which encryption method(s) this uses
(I'm guessing digest-md5), but it's not needed with TLS/SSL.
I realize too that your goal is to avoid having to change client
configurations. The fact is though, you may need to. If the clients are
configured to use digest-md5 and vpopmail/dovecot won't support it
(neither of which I am certain), you're going to need to change the
clients. (note IF).
I do know that vpopmail-toaster is compiled to support plain and md5
passwords (I just checked). What I don't know is if vpopmail's md5
support is only cram-md5 (I'm guessing so) or if that includes
digest-md5 support as well (I'm guessing not). I also don't know if
dovecot can support digest-md5 even though vpopmail does(/may) not.
Again, I would expect not (but I can't say for sure).
I do know that using TLS with plain logins is safe, simple, and it works
well with clients that have TLS capability (FWIW, Outlook'03 does not,
and Outlook'08 does).
Please share with us any knowledge you gain regarding these things.
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
