search for: imaps_listen

I am running Dovecot and wanted to make sure that to disable POP3 access on the MDA is as simple as removing the POP lines: protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * imaps_listen = * pop3s_listen = * Do I need to modify anything else or am I looking in the totally wrong section: -- Man your battle stations...

Hi, Trying to setup dovecot in a test environment. I need to run it on an alternate port for imaps. it doesn't seem like I can specify it on the listen line. any ideas? -sv

Noticed that some configuration settings like imap_listen appear to have been removed. Any way to accomplish this ? -kim __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

I can connect using imap, but when I try using ssl (imaps) I get a can not connect to server error. I have in my dovecot.conf protocols = imaps imap imap_listen = * imaps_listen = * I DO get a connection when I telnet to port 993 of my server (both localhost and remote work). Any help much appreciated.. Jay

...93 and it said only CONNECTED(00000003). A time ago when everything was OK, the listing after connection was "a bit" longer than it is now. I remember there was "OK, dovecot ready" or something like that. Now, there is none. Of course in /etc/dovecot.conf: protocols = imaps imaps_listen = * ssl_disable = no So, what's the problem?

...http://www.linuxquestions.org/questions/showthread.php?t=441062 But i'm not having a lot of luck, a question about dovecot, what kind of mail box am i using? mbox? if so does anyone know if procmail can use mbox? /etc/dovecot.conf protocols = imap pop3 imap_listen = [::] pop3_listen = [::] imaps_listen = pop3s_listen = log_path = /var/log/dovecot.log login = imap login = pop3 default_mail_env = mbox:/home/CATHEDRAL/%u/mail:INBOX=/var/spool/mail/%u auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root -- Paul Matthews I.T Trainee | The Cathedral School P...

...pop3 using thunderbird it always says authentication failed when i try to login using squirrelmail, it always says username and password incorrect but i know for sure the username and password are correct dovecot conf file is as folows -------imap_listen = [::] -------pop3_listen = [::] -------imaps_listen = [::] -------pop3s_listen = [::] -------ssl_cert_file = /etc/pki/dovecot/dovecot.pem -------ssl_key_file = /etc/pki/dovecot/private/dovecot.pem -------mbox_locks = fcntl -------auth = default -------auth_mechanisms = plain -------auth_userdb = passwd -------auth_passdb = pam -------# i've tri...

...): unable to connect to 192.xx.xx.xx:993 in /usr/share/squirrelmail/functions/imap_general.php on line 445 ERROR Error connecting to IMAP server: tls://192.xx.xx.xx. 111 : Connection refused Go to the login page The port numbers of the imap server are as follows: imap_listen 143 pop3_listen 110 imaps_listen 993 pop3s_listen 995 Squirrelmail and the dovecot imap server are running on different machines, so it is essential to enable tls support. All the machines are running Debian Sarge. Can anyone suggest a solution for the above problem ? Thank you. Srinivas ______________________...

...ectly or something on the pop3 server machine is not right. Anybody has an idea? Thanks in advance. Jun Here are more detailed info: -bash-3.00# rpm -qa | grep dovecot dovecot-0.99.13-3.FC3 /etc/dovecot.conf: ---------------------------- protocols = pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem login_dir = /var/run/dovecot-login login = imap login = pop3 mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = roo...

...c=tld deref = never scope = subtree user_attrs = mail,,,,, user_filter = (mail=%u) pass_attrs = mail,userPassword pass_filter = user_filter = (mail=%u) default_pass_scheme = CRYPT user_global_uid = 5000 user_global_gid = 5000 /etc/dovecot.conf: protocols = imap imaps pop3s imap_listen = 127.0.0.1 imaps_listen = * pop3s_listen = * ssl_cert_file = /etc/ssl/mydomain.tld/Cert.pem ssl_key_file = /etc/ssl/mydomain.tld/PrivateKey.pem disable_plaintext_auth = yes login = imap login_user = dovecot login = pop3 verbose_proctitle = yes first_valid_uid = 5000 last_valid_uid = 5000 first_valid_gid = 5000 last_valid_...

...'t verify everything too carefully yet, so more auditing is still needed before we fully reach that goal. + Implemented several missing tasks / optimizations to index handling. It should now stay fast after longer usage periods. + New configuration file options: log_path, log_timestamp, imaps_listen + "Critical errors" are now hidden from users, ie. any error message that is not a direct reply to user error is written into log file and user gets only "Internal error [timestamp]". + Nonblocking SSL handshaking + Lots of code cleanups - Lots of mbox fixes, it seems...

...ns @UNSAFE tag to make auditing easier. + Support for SORT extension. Originally I thought about not implementing any extensions before 1.0, but too many people want webmails which want SORT. THREAD is another extension which they want, but we don't support it yet. + imap_listen and imaps_listen settings now accept "*" and "::" to specify if we want to listen in IPv4 or IPv6 addresses. "::" may also listen in all IPv4 addresses depending on the OS (Linux does, BSD doesn't) + New setting: default_mail_env can be used to specify where to find us...

...llowing error is reported in /var/log/syslog: imap-login: Login: dk [192.168.0.2] imap(dk): Unknown client workaround: outlook-idle^I### dovecot: child 17653 (imap) returned error 89 What does error 89 signify? My current configuration is: (non-comment lines only) imap_listen = 192.168.0.2 imaps_listen = * login = imap login = pop3 verbose_proctitle = yes client_workarounds = oe6-fetch-no-newmail outlook-idle mailbox_check_interval = 60 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root auth_verbose = yes In my confusion, I blindly tried cha...

...r:1408F455:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac [192.168.1.103] Now I'm not sure if theres any difference here, but I don't have string for 'login = imaps' or 'login = pop3s' to match with my protocols string I also don't have any specific imaps_listen interface defined, but since there's something in the logs, I assume that this is not a problem. SETUP fluffy:~ # egrep "^\w" /usr/local/etc/dovecot.conf base_dir = /var/run/dovecot/ protocols = imap imaps pop3s log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.info...

Hi, I looked through the web and the list archives, but couldn't find how to set up the following: - dovecot with ssl/tls enabled - login from localhost allowed with and without tls - login from remote hosts only allowed via tls Is that possible at all? I'm using debian/unstable so its version 0.99.10.4-3. Thanks, johannes -- http://www.sipsolutions.de/ Key-ID: 9AB78CA5 Johannes

Hi! here is the problem , i have local users some have shadow password, some not, so i must create two auth one to login via shadow , and one via passwd so here is my config file (stripped comments): protocols = imap imaps pop3 pop3s imap_listen = 192.168.0.2 pop3_listen = 192.168.0.2 imaps_listen = 192.168.0.2 pop3s_listen = 192.168.0.2 login = imap login = pop3 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = shadow auth_user = root auth_count = 1 auth_verbose = yes auth = truc auth_mechanisms = plain auth_userdb = passwd auth_passdb = passwd auth_verbose = yes...

...inbox is now pushed or grabbed by my blackberry as new messages when they are not and have been read already (at least most of them). Why is this happening? ## Dovecot 1.0 configuration file base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] log_timestamp = "%b %d %H:%M:%S " login_dir = /var/run/dovecot-login login_chroot = yes login = imap login = pop3 default_mail_env = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = pas...

...r 1 15:37:03 edim dovecot: Auth process died too early - shutting down Apr 1 15:37:03 edim dovecot: child 9593 (auth) returned error 127 Apr 1 15:37:03 edim pop3-login: fd_send(-1) failed: Broken pipe my configuration is : protocols = imap imaps pop3 pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem login_dir = /var/run/dovecot-login login = imap login = pop3 mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_user = root what does it?

...sd system), and now I've to migrate from bincimap. My system uses qmail with vpopmail (uid/gid 89) and Maildir format. Well, now the authentication is ok, but when I try to connect to mailbox I receive an error like "IMAP command SELECT failed". My dovecot.conf: protocols = imaps imaps_listen = 192.168.17.10:993 ssl_disable = no ssl_cert_file = /var/qmail/certs/mail.nesys.it_cert.pem ssl_key_file = /var/qmail/certs/mail.nesys.it_key.pem log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log login_user = dovecot first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89...

Hi, Gentoo updated dovecot to 1.0 beta3 and don't succeed in authentification with pop3. Here is my dovecot.conf 0.99 protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * imaps_listen = * pop3s_listen = * login = imap login = pop3 default_mail_env = maildir:%h/.maildir mbox_locks = fcntl dotlock auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam dovecot auth_user = root auth_verbose = yes auth_debug = yes and here is my translation for dovecot.conf 1....