search for: imapsecur

Hello. Tried search, no luck, sorry, if this is already answered, but I'm still looking a solution using pam_auth how to define in dovecot which user can access which protocol, for example, default is: protocols = pop3 pop3s imap imaps I'd like to use something like this: exclude_using_pop = user1, user2, @group exclude_using_pops = user1, user2, @group exclude_using_imap = user1,

...7.html Increasing the log level I get this in the log filed: Sep 30 15:04:19 fm dovecot: Dovecot v1.0.rc7 starting up Sep 30 15:04:22 fm dovecot: auth(default): passwd-file /etc/dovecot_user_file: Read 1 users Sep 30 15:05:05 fm dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAPsecured +lip=::ffff:SERVER_IP_HERE rip=::ffff:CLient_IP_HERE resp=LONG_STRING_HERE VDBB Sep 30 15:05:05 fm dovecot: auth(default): passwd-file(user_name,::ffff:CLIENT_IP_HERE): unknown user Sep 30 15:05:07 fm dovecot: auth(default): client out: FAIL 1 user=user_name Sep 30 15:...

...The web gateway is intended to be used from untrusted computers as well, so the IMAP password entered through the Web site must not be the same as the password used on IMAPS. I have solved this problem by using %s%c as part of the LDAP user_filter. When people connect over IMAPS, this becomes imapsecured (%s=imap, %c=secured), while an unencrypted connect becomes imap (%s=imap, %c=) Unfortunately, this works only, if the web interface and the IMAP server are located on different (virtual) machines. But if the web gateway and dovecot are no the /same/ machine, this does not work anymore, since...